That makes sense, especially as it states “invert output”.
For my virtual application re-writing the function solved the issue. Thanks for the help!
I don’t know the reason but when I connected the second oem lambda(bub PnP) the problem of lambda reading is sol ed
But I have two IAT sensor,one near intercooler and the second at the alluminium air intake,in the next is possibile use the second sensor for charge temperatur ?
Sorry for my english
Dear support,
Its not related exactly to 3.057 but I noticed that LOG from EDL starts when engine is olready running.
Also, when Iam trying to tune cold starts. Lambda is preheated when engine is not running.
When Lambda is ready, I start the engine and then no values are given (lambda=1 and status “lambda is not valid” )
Behavior is simillar like when conservative heatup is activated.
For cold starts its useless.
Hi, we were working together on a strategy for Haldex 1st gen. control using an H-bridge for a stepper motor. What does it look like please? I’m looking forward to it!
Even 5 injectors can be opened in your engine simultaneously at the same time (when the DC is high) 
Also the injectors outputs are logged with 25Hz (what is 40 ms). This is more for observing outputs connected to different strategies.
As it was previously mentioned it inverts output not function. It is already fixed and for Virtual output ““Invert output” check box is disabled
Use User switch instead of Function. User switches are evaluated every 2ms
What is a problem with the lock cell function ?
Knock control strategy ignition timing correction, since it works per cylinder, is not visible on the Ignition angle log channel! You should observe the knock strategy ignition correction channels or/and the I.KS correction channel.
Knock ign correction - when the option All cylinders is selected for Knock sensor action / Ignition control type, this channel shows the current ignition correction for all cylinders.
Are you sure you dont turn off ignition before engine start ?
Hello,
customer made some measuremen for me.
Parallel measurement with PC logger → two files from same time range.
The issue is more fun than I expected
PC-measuremen: (firmware updated → fixed version)
During the cranking part of the measurement is missing (measurement starts in 76 executed sparks count)
Logger measurement : (firmware updated)
Beginning of measurement is missing.
Data are visible since crank starts
Lambda issue still the same, during the start the status is “restarted” (I would call it like that).
Please see the measurements in attechment . . .
PC_LOG.emublog3 (1.3 MB)
12184111.BG3 (2.9 MB)
For PC it is normal as Windows needs a time to connect USB device.
For EDL the only explanation is voltage drop below 6V that resets the EDL.
The same with the WBO.
The EDL records continously. Also the WBO will be restarted if the ECU is restarted.
But I never seen this issue before (also on FW v2).
All our coldstarts were done via data from the logger. Also the PC measurements were 100% smooth.
I would say (just guessing) - till 3.050 no problem with PC , EDL or lambda.
Maybe there is cold and your battery voltage drops more on start ?
Regarding the EDL only:
In my environment, logging seems to be possible from key-on. However, starting with this update (3.057), I changed the EDL’s power supply to 12V (it was originally 5V as per the instructions).
However, even when connected to 5V, logging was possible from key-on.
Perhaps there is some other (or multiple) reason.
20251013_1857.emublog3 (3.1 MB)