# ###### ## ## ## ## # ##
#### ## ## ###### ## ####
# ### ## # # # # # # #
#### ## ##### ## ## #####
##### ## ## ## ## ##### ## ##
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: I use VEMS V3.6 on my dragcar powered by a cbr1100xx engine. Until now the engine was running on four carburetors plus nitrous and the performance was very good (8.7sec@402m). I turned to fuel injection and VEMS in order to use all the extra racing features (like launch control, shift cut, etc) and be able to have a more precise engine control. ---- Firing sequence: 1,3,4,2 '''Ignition outputs''' (wasted spark/2 coils): cyl2 EC36-pin36 cyl4 EC36-pin34 cyl3 EC36-pin36 cyl1 EC36-pin34 '''Injector outputs''' cyl2 EC36-pin19 cyl4 EC36-pin20 cyl3 EC36-pin8 cyl1 EC36-pin7 '''Other outputs in use:''' '''fuel pump relay''' EC36-pin15 NO idle air valve because injection bodies have special air valves for idle controled by water temp (almost all injection CBR engines). '''Shifter relay''' EC36-pin4 '''TPS''' original pinout (EC36-pin1/29/AN.GND) '''CLT IN''' original pinout (EC36-pin14) '''Prim. Trigger''' original pinout (EC36-pin27/AN. GND/ Shield) No other inputs/outputs are used. ---- '''SOFT/FIRM''' In the past (1.0.73 firmware) '''I was using MegaTune software with no problem.''' '''answer this questions please''' I configured the ecu myself from the start and it was almost as easy as any other ecu I have used until now. I have not saved the config file (my fault). I used also the VemsTune0.10.20(2010.03.08) and the firmware uploaded on VEMS V3.6 is '''1.0.73.''' * that is good. Stick with 1.0.x because the 12-3 pattern is supported only by 1.0.x firmware. (1.1.x works with N-1 or N-2 but not with N-3 !) ---- '''TRIGGER''' I use the original trigger wheel and VR sensor of the cbr1100xx with no problem. The cbr1100xx (carburated model) uses a 9teeth trigger wheel with one big missing tooth (later injection model had a 12teeth trigger wheel with no missing teeth). http://www.vems.hu/files/AutoVeltiosis/cbr1100_trigger.jpg '''It's a 12-3''' pattern (toothwidth=30 degrees). Unfortunately this is not supported with 1.1.x firmware, you can only use N-2 or N-1 pattern as set in the primary trigger options. You might need to use '''1.0.x firmware for now with this pattern.''' The following Trigger Setting were tested as long as I use the Megatune and were proven to work fine with 1.0.x firmware. It's not a MegaTune / VemsTune issue. '''It's an 1.0.x / 1.1.x issue. 1.1.x times from the last possible tooth. ''' The problem is that the ignition outputs are not firing as they should (I use the test function through VemsTune). Sometimes both coils fire together sometimes they don't fire at all. I belive the config file http://www.vems.hu/files/AutoVeltiosis/v3.3_n002710-2010.03.17-14.28.02.vemscfg should be checked and corrected. Most likely wrong: * h[0]=09 06 00 00 00 00 00 00 ** using 1 separate output driver for each injector ? ** Try to start from h[0]=01 02 04 08 10 20 40 80 * h[2]=68 40 48 58 00 00 00 00 ** using ign (i259), not stepper outputs for spark, right ? * als_launch_input=C1 ** disable launch until you get the basics right and working * knock_conf=F0 ** in 1.0.x knock_conf=00 disables knock '''fuelpump_channel=D7 Seems very wrong !''' This can cause bad output problem. Fill in the wiring info above. I found out that while I was trying to test the InjGroup 7 the shifter was activated. So the outputs are all messed up. I get the '''message OUTPUT COLLISIONS''' - because that is the case ! Fix the collision. * I found out that while I was trying to test the InjGroup 7 the shifter was activated. So the outputs are all messed up. * I believe we have to reassign all the outputs from the start if that's possible. ** yes, that's the way. Fill in above, so we can help ---- '''IMPORTANT information''' Hi Nouchoutidis, * We updated your page (this) * we wrote you what is the problem with the '''LATEST''' config you posted * and sent you email message. '''You neglected our instruction about 8 times before !!!!''' Start filling in the needed info, including the wiring details so we can help. You need to update your page. You need to change the configuration so NO output collision ! * A) Disable outputs and enable the correct ones * B) Save config, upload and update your page (this) so that we can try your config. that. * C) If you write wiring details above, we could even help to approach a valid config, but you have no wiring details so we cannot help you with that THE VEMS WAS FUNCTIONING PROPERLY WHEN SENT TO ME BUT AFTER THE FIRMWARE CHANGE ALL OUTPUTS ARE MESSED UP. '''Now I use Firm 1.0.73 (I have not changed anything in the wiring) and everything works fine. Engine fires up and is tuned very easy. I believe its clear for you now that: 1. Its not the wiring 2. Its not my settings that have messed up the outputs. Probably its the firmware change (I have never faced such problem with new firmwares in my microcontrollers where I write some lines of simple code. Something is wrong in the firmware change from a very old to a very new firm). I have uploaded my working config in the files area. I will try to move on a newer firmware and change to N-1 or N-2 trigger wheel to see if settings remain as set. I wouls also apreciate it if somebody could help with the water temp sensor (ECU is not responding on coolant bins/firm 1.0.73). Stock Water Temp Sensor (CBR1100XX) C Ohm 15 785 20 570 25 440 30 355 40 237 50 157 60 107 70 74 80 55 90 40 100 29 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.