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.
Wiring details needed. FILL THEM IN. The config seems broken but impossible to correct it without these info
Firing sequence: 1,3,4,2 (right ?)
Ignition outputs (from bottom to top):
- cyl2
- cyl4
- cyl3
- cyl1
Without the wiring information we cannot help !
Injector outputs
- cyl2
- cyl4
- cyl3
- cyl1
Other outputs in use:
- VERY Important: fuel pump relay.
- idle air valve (PWM or stepper ?)
- other ...
SOFT/FIRM
In the past (1.0.73 firmware) I was using MegaTune software with no problem.
answer this questions please
- someone else configured the ecu for you before ? (apparently yes)
- where is he ? Why does not he help you now ?
- where is the saved configuration (config / tables dump) that was in use when it worked without problem ????
- why don't you use the same proven configuration that worked ?
- if you don't have it because it was not saved (bad mistake), than it's the same as starting the whole setup procedure again. It can be done, but lots of information needed.
- what did you try to achieve when you messed up the configuration ? (it is messed up now as it is misconfigured: there are output collisions ! and naturally it does not work right)
At the moment I use 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).
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 closest you could go with 1.1.x is N-2 with toothcount=10 (but even that unlikely to work, and extremely unlikely to work well). With N-2 firmware would decide to trig/start dwell from 0..9 (whatever is last) but only 0..8 tooth exist here, so at certain RPM/load it would wait indefinitely for nonexistant tooth, (until reboot).
Trigger Edge: Rissing
Trigger Type: Missingtooth
Missing Tooth Type: N-1
Special Trigger Type: Normal
TDC After The Trigger: 45.0
Number Of Teeth On Wheel: 9
First Trigger Tooth: 1
Next Trigger Tooth: 6
Filtering: Disabled
Advanced Filtering: Disabled
The ignition is DUMMY type. The ignition outputs are set to 01..00 and invert driver output and dual output mode are disabled. One coil is nonnected on ec36-pin34, the other one is connected on ec36-pin36.
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.
But wiring details are needed to correct it. So fill in details above !!!
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
But wiring details are needed to correct it. So fill in details above !!!
But wiring details are needed to correct it. So fill in details above !!!
But wiring details are needed to correct it. So fill in details above !!!
'''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)
- 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
If someone neglects our instructions than we just stop giving him instructions (of course).
So do at least A) and B).
If you do not neglect our instructions repeatedly, and update your page (this), we can help you. Otherwise we cannot.
Do NOT write mails without updating your page!
Hi Nouchoutidis,
> Please have a look at my problem,
we looked at your problem and tried to help as you can see from
the page.
We clearly identified the information needed to proceed.
Just fill them in.
Actually there are 2 methods.
- Starting from the previously working config with (1.0.73 firmware) in the past "with no problem."
- or start from the wiring
Unfortunately you did not fill in any of that.
WHEN (if and only if) you fill in we can continue and most likely help.
> that's the last time I send you a mail (I
> don't have any more time and courage). I have done several ecus
> installations and even though I am decades behind your knowledge over
> software I have done simple c++ projects and I am able to understand some
> simple things and do some simple settings.
that's very nice. but no substitute for the info missing in this project.
> THE VEMS WAS FUNCTIONING PROPERLY
> WHEN SENT TO ME BUT AFTER THE FIRMWARE CHANGE ALL OUTPUTS ARE MESSED UP.
The saved config needs to be uploaded after upgrade.
But, unfortunately the 12-3 pattern will not work with 1.1.x so
the only method is to downgrade to 1.0.7x and upload old saved config (1)
If old config was not saved, method 2) remains - which is more work but should be possible.
We wrote up the likely wrong settings but details about wiring (2) needed to correct them !
> It's not a matter of bad wiring or wrong setting in the software (it was
> working with that wiring and settings with the old firmware).
if you loaded back same firmware and same settings than it will behave same.
Maybe CLT or MAT a few degrees off if other table chosen, but otherwise same operation.
Verify firmware, just in case. If identical, than the problem is narrowed to config (which indeed seems to have problems)
> Please have a
> look on my configuration so I can go further or stop trying at all.
we did. See your page.
> It's
> crazy to have these problems and spend so much time to solve them.
As we stated, without your wiring details we cannot help fix the problem.
It would take less time to fill in ~20 lines instead of wasting so much time - of ours and yours.
> I can see
> the potential of this ecu but how can we commercially stand up and sell to
> clients if we face these problems. Anyway you can see how much I want to use
> the VEMS for my Dragcar and for my Workshop also but if I don't have my car
> tuned till next month I am going to loose the next race of the championship.
Given the wiring (at least outputs please!) I hope we can proceed.
Without that it's likely just wasting more time.
> Sorry for spending your time but you should also understand that in this
> situation something goes wrong with the ecu.
Maybe. Usually config (also most likely in this case. See most suspicios ones on your page).
But to find out, we really need the output wiring details.