# # # # ## # # # #
_______ ( ____ ) | ( )| | (____)| | __) | (\ ( | ) \ \__ |/ \__/
## ### ## ## ## ######
_ _ ( ) ( ) | |/'/' | , < | |\`\ (_) (_)
___ ( _`\ | ( (_) | |___ | (_, ) (____/'
IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now. Visit Preferences to set your user name Summary of change: Rob Humphris - Cambridge, UK. http://www.vems.co.uk ---- I find it a little disapointing that the standard Win32 C++ library does not provide an iostream for the serial port. I found this on Source Forge: http://sourceforge.net/project/showfiles.php?group_id=129219 Which might make the beginings of a cross-platform communication abstraction layer which would assist in the development of future tools (such as tuning software config loaders and datalogging) ---- From a VEMS user: "My LCD seems to have taken a s**t. It works fine for about 5 mins then the screen changes to loads of weird characters and jibberish. I turn off the car and restart and it works for 5 mins again, then does the same..." He's running Version 1.0.23 '''A:''' I've seen this on a few cars too, changing to shielded wire (shield attached on LCD side), and not a longer cable than needed, it got much better. Today the problem seems to have stopped, which is in its self rather worrying. Mine does that too sometimes - it all comes back OK when I type the mli command. see MembersPage/DavidBlades/FanTest for my notes on the problem. ---- '''Currently Developing''' UsabiLity UsabiLity/GenBoard/WinTools PIDControlTuning MembersPage/PhatBob/UserGuide MembersPage/PhatBob/ToyotaFitting MembersPage/PhatBob/Marketing VehicleFitment/Toyota VehicleFitment/Honda VehicleFitment/Nissan ---- MembersPage/PhatBob/MagnettiMarelliSensorProblem MembersPage/PhatBob/PurchasePage MembersPage/PhatBob/ConfigProblem ---- The closing times are also needed (it is the function of injector current and flyback voltage). The flyback voltage actually makes a huge difference. The opening times are not (by far) enough to calculate GenBoard/Manual/Config/InjectorOpening parameters. You can start from other's values, make sure * injopen=00 (or very very short for low-voltage flyback, max 100 usec) * battfac=10 (256..700 usec is usually OK) * injocfuel=2C (500..1200 usec usually) * injrampup_battfac=FF (IIRC 4082 ... in MegaTune, it does not have a simple physical unit like "usec" or similar) ---- http://vems.hu/www.vems.co.uk/VEMSWB/VEMSlcdDark.jpg http://vems.hu/www.vems.co.uk/VEMSWB/VEMSlcdLight.JPG http://www.pgmfi.org/twiki/bin/view/Library/EcuSensors ---- v3.2 Assembly documentation: v3.2 How-to power-up a new board. http://vems.hu/www.vems.co.uk/VEMS/ ---- In an attempt to document my installation: * GenBoard/InstallPage/PowerUpToBootloader * GenBoard/InstallPage/PowerUpToBootloader Optional: Add document to category: Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.