Is there an option for odometer somewhere somehow?
It is corrupted log frame. I have never seen such an issue but all data in the frame after knock count is corrupted (eg. lambda 1 lambda 2 and so on).
Was the log recorded wit the PC or EDL ?
There is no such option.
It was originally recorded in EDL.
If it’s simply a problem with the SD card, there’s no problem.
In this case, does that mean can’t check the log item “EDL write error”?
it is for sure edl issue. There was no knock at that log frame. I will investigate this.
1 Like
I have set the operating condition of idle airflow custom corr. to AC active, but when I look at the log, sometimes the AC remains ON even when it is OFF (when the evaporator temperature reaches the specified value).
Does this mean that the correction is always on while the AC system is ON? I feel that it would be more correct in terms of control if the correction was turned off when the clutch was turned OFF.
Initially, I thought it would be good to have a parameter that would process the delay when the AC clutch is turned OFF in the same way as when it is turned ON. (I want to suppress the momentary increase in rotation speed due to the loss of load.)
Perhaps the rotation is simply increasing because the correction is always on.
is there a tool to read the oem canbus stream from the stock ecu?
We tried to do what we could with the current situation.
We set the delay by controlling the clutch using a function without selecting an output in the AC clutch parameters.
After all, being able to set a delay when disengaging the clutch will make the transition from ON to OFF smoother.
I would like to see a delay function added in the future (delay from airflow compensation OFF to clutch OFF)
Taking a hint from another topic, I tried to set the AC clutch output to CAN-bus and perform the actual clutch operation with a function.
However, the operation was different from what I imagined.
First, when the clutch is ON, it goes OFF once for some reason. However, this is not always the case.
Furthermore, even though a delay is set, the clutch operation goes ON earlier. And if the OFF delay is made larger, it goes OFF at an earlier timing.
I thought it might be possible to do this with the current specifications, but I couldn’t get it to work properly.
Maybe there’s a problem with my settings.
QNC10_K3VET21.emub3 (69.0 KB)
20250728_2241.emublog3 (790.3 KB)
USB2CAN and LightClient
1 Like
Controlling the AC clutch directly with the function works better, so I changed the setting back, but
the MinEVAPtemp in the air conditioning settings window is somehow affecting it.
Even if you set the hysteresis for the evaporator temperature on the function side, the timing (airflow compensation) will be off if the same setting is not used.
Airflow compensation is set in the function, not the AC.
It seems that the clutch release delay I’m looking for can be achieved by using two functions.
Just sumarizing. What you need is another delay for clutch off.
So the AC clust status will be off but the clutch output will be off after user defined delay ?
This week I plan to release new build, so I can try to add such functionality.
That’s exactly the function I’m looking for.
The above series of comments report some unexpected behavior when attempting to achieve a similar function using the ‘Function’ function.
- When using ‘Custom airflow corr.’ + activation ‘AC’, the correction sometimes doesn’t turn off when the AC clutch is off.
- When using CAN-BUS output in Outputs-ACclutch and controlling the AC clutch with Function, the initial operation sometimes becomes ON-OFF-ON when the AC is turned on.
- The ‘False delay’ in the Function function works in the opposite direction (the conditions are unknown).
Currently, this setting works perfectly.
QNC10_K3VET22.emub3 (69.1 KB)
However, I’m setting the evaporator temperature hysteresis in Function, and if I don’t set it to the same value as the EVAP temperature setting in Outputs-ACclutch, the timing of the AC clutch and correction will be out of sync.
The cause of this issue has not yet been investigated.
I’ve tested haltech V2 on both versions and also comapred to Haltech doucumentation and CAN data looks ok.
Could you write what are the pressures in EMU and what are displayed on the Dash ?
Additional Note:
It said that the evaporator temperature hysteresis set in the ‘Function’ and the AC clutch operation were different, but the reason I checked the log was because it was ‘ACclutch’. I should have compared it with Fn6.
It worked correctly.
The AFR dropped out during a drive and I have no idea why. I turned the ignition off and then back on and roll started the engine. The injector PW spiked causing a ton of backfiring. Again, I can’t figure out why either of these events occurred.
AFR/Lambda drop out: 2:27.16s
Restart: 2:12.32s
EMU Black Porsche V3.053 072625.emub3 (66.6 KB)
20250730_2131 Crop.emublog3 (438.6 KB)
Can you please review??
Looks like external controler reset and suddenly start to show lambda 0.5
At 2:03 there is an ecu reset during engine breaking. And also it is the point the both external lambda controllers stop to work.
Since this update I have noticed the VAG MDI Torque value changing randomly. I am pretty sure i had it set at 420. After some tune revision yesterday it randomly changed to 569.
Can someone please explain this, and the purpose of this value? Ive had and explanation of it from the dealer that sold me the ecu, but I am not totally convinced I have the right information.
Cheers,
Ian
