I am asking nearly every new update for the password protection for calibration file - which is mentioned as a functionallity of V3 features from the begining. Understand that I am annoying already.
But for my perspective is absolute grat idea and can solve many problems with customers.
Do you have some rough schedule when we can expect this awsome feature in the FW???
I think there could be some adjustment or more options to the cruise control settings. I have an e36 so I don’t have a I/O or a set/cancel button. I have off, resume, speed + and speed -. With that, I have it set to be always active and just tap the speed + or speed - so set my cruise and in oe configuration that would set my current speed but with the EMU it acts like I press resume and sets it to the last set speed. I have to hold the button to match my current speed or if i’m going slower than it was last set I cant bring the set speed down without the car accelerating while I make the adjustments. It would be nice to have the speed + and speed - set the current speed not resume.
Many idle control issues seem to originate from an incorrectly calibrated Active State Air Flow table. Since this table is the foundation of the idle model, tuning PID values often becomes difficult until the airflow model is correct.
Would it be possible to implement an “Active State Air Flow Auto-Learn” wizard? Based on this data, it could automatically generate the Active State Air Flow table.
This could significantly reduce idle setup time and provide a much better starting point for PID tuning, especially for less experienced users.
Is there any difference in Lambda reception via CAN between versions 3.065 and 3.067?
When receiving data from the AEM X-UEGO via CAN, there is a discrepancy compared to the gauge display.
To be precise, I had previously confirmed that a discrepancy had been fixed in version 3.065, but the same issue has reappeared.
Regarding the data, the received value is supposed to be divided by 10, but multiplying it by 4 and dividing by 39 yields a value that is quite close.
In both cases, the issue appears in the AFR display.
The symptoms occur with data where the received data is lambda, the AEM display is AFR, and the V3 software is also displaying data in AFR.
I have not yet verified the readings by comparing lambda values directly.