Yes but in 3D custom tables you can’t choose ignition its not in the lest check it.
Regards
Thank you Jakub, I feel silly now!
Which manual/menu is that found in? previously I had it working with no multiplier/divider (just checked and I had it coming in on 0x640 which explains it).
Could I ask one favour for the next update, add second inj split to the general fuelling corrections.
And is it okay if async enrich table -100 and enrychment still happend?
Check the log … there is 316 VE value comming from nowhere
Async enrichment is visible only on injectors pw not on acceleration enrichment channel.
Could you provide log file and base map to this file?
The input channels are described at the end of the User defined CAN help.
I add 2nd inj split % to custome axes for the next build.
1 Like
I’m not sure if I understand you correctly.
The correction tables in ignition section modife ignition angle.
There’s an issue when looking at v3 logs with DataMaster, data appears corrupted somehow.
I know it worked fine on around 3.046, not sure what version it stopped working.
I will inform datamaster team.
1 Like
But there is also injector PW on log…there is no enrichment visible but on async enrich chanel are 2 spikes visible…and check the lambda value…2 deep rich spikes happend…coincidence?
Its happend during tuning so i think i cant get the tun file but i have log saved
if you have access to any test car on V3 just try to lock a couple of VE cells and you will see the result…i find this issue on 2 independ cars
Jadzwin_ECUMASTER …is there any room to get trigger error counter chanell in logged values? It will be a big help in checking for trigger errors in long logs
Ok I will test it on the bench.
According log what is a time with the spikes ? I look through the log but I didnt find them.
Yes it is possible to add counter counting trigger errors up to 255.
check on the 54th minute 
i think it will be a very usefull feature
@Jadzwin_ECUMASTER Is this possible for a future release or is there a limitation there?
Default PMU base ID cannot be used as it is already present on the bus from the OEM modules…
