Due to significant changes in the software, most strategies are not compatible with the V2 version strategies. There are plans to create a file importer from V2 to V3 to facilitate the migration for as many users as possible.
We suggest starting the entire configuration from a blank project and setting up everything step by step. The good news is that the ignition table, VE table, and Lambda target table are compatible, and you can copy them from the V2 project using the keyboard shortcuts CTRL+C, CTRL+V. Make sure that the values on the axes of these tables in the V3 software are identical to those in the existing maps.
There have been significant changes in the ignition configuration. You need to define the firing order of your engine and then assign injectors and coils to specific cylinders. This is a much simpler concept than in the V2 version. The Ignition output offset option has also been removed, and the invert phase option has been introduced. In case you have sparks in the right place on the timing lamp, but the engine does not start, you can check the invert phase option, and the ECU will change the engine phase by 360 degrees.
Please also check the ignition configuration using a test lamp after setup.
Thanks, Thats what I had V2 but just thought if it works like this if I select just wasted spark?
Not to able to do any live test yet, maybe at Friday.
Could anyone assist with the nomenclature change on cam 2- previously this allowed the selection of “multitooth”- I assume this has been replaced by “primary teeth window”. Any advice on the specification of the crank tooth min/max values?
Is this the range you would expect to find the cam teeth in in relation to the crank teeth?
Cam 2 has 4 teeth, evenly spaced, and is used for the control/monitoring of vvt angle (honda k20/k24). In this case would I select min 1, max 12 (engine has 12+1 crank teeth)?
Thank you!
Edit: there is more help in the V2 firmware, my understanding is I define the range for a single cam tooth only
It is simple if you look on the scope. If you take a scope trace in V3 software the tooth are numbered.
The help will be updated soon. If you post here your scope I will explain you on your example how to set up.
on older engines they are paired unusual way not “typical” injectors where fired only one per cycle … I think there was video by Andy Wyatt explaining it…
Hello, I still have a problem that I am dealing with. I started my vehicle, set it on the road, etc., I did everything, but dbw still does not work in the idle section, it stops instantly, the installation is like this, is there something I missed?
active air flow is to low in mine opinion you have range from 1-6 and you chose 25% -this is 25% of your range so is 1.25 percent added to 1% minimum throttle is 2.25 i don’t know what is the car and throttle but seems to be low for me
Hi,
i have a problem…EMU doesn’t fire the ignition with V3.
Engine is a simple 1.8t 4 cylinder…running without issues with V2.
Those are the firing order settings:
But it doesn’t fire.
If i set in firing order all 8 to cyl1 it fires. That doesnt make sense for me. I dont understand my problem.
Scope looks good…emu comes also to synced state…no trigger error present.
I am running the TFSI coils with built in amplifiers.
I just went to the vehicle to take a clean log…updated it again to V3 from V2…and now it is working without issues…strange.
I have a log, but exact parameter situation is not clear in it since i was playing a lot with the settings: 20240512_1825_rev7_noIgnition.emublog3 (18.4 KB)
Anyhow…engine directly started after inverting the engine phase
Let u know if it occures again. I already expirienced strange resets of parameters to default after loading a project. Need to observ a lot in the next days.
But thank u for this SW…so much fun to play with a new SW
Other question. I am useing an electric WG. The strategy is not yet implemented completely?
