Will give those changes a go for my cars. The issue with the aem data freezing was purely in pass-through. it seemed to be okay when logging from the v3 device.
Will give those changes a go for my cars. The issue with the aem data freezing was purely in pass-through. it seemed to be okay when logging from the v3 device.
In that case, can you please provide some trace files...Originally Posted by Tre-Cool
In stand alone data logging - where it works, can you log data for about 10 seconds, then stop the log and save a *.xalm trace file directly from the V3 device. (Scan Tool -> F3: Scan Options -> F1: Save Trace File)
In pass-thu mode - where it fails, can you log data until the AEM has stopped sending data, then stop the log and save another *.xalm trace file directly from the V3 device - and save a *.htx trace file from the EFILive Control Panel.
Note: When saving the *.xalm files you have to save them before rebooting the V3 device (i.e. before unplugging from the vehicle).
Can you please create a support ticket here: https://service.efilive.com/new-ticket
and include those trace files.
Regards
Paul
Before asking for help, please read this.
When a scan tool is communicating with a vehicle controller, it periodically sends a keep alive message to let the controller know that it is still connected. If the scan tool is disconnected and the keep alive messages are no longer being transmitted by the scan tool, the controller(s)on the vehicle can correctly assume that the scan tool is no longer present and that the controllers can return to "normal operation" - i.e. no longer transmitting data logging data for the scan tool.
That is what I believe the AEM is doing when it stop transmitting - it is "thinking" that the scan tool has been disconnected because it has not seen a keep alive message from the scan tool for a certain period of time.
The OBDII standards says that the keep alive time should be 5 seconds. I.e. The controller(s) on the vehicle (including the AEM device) can only assume that the scan tool is no longer present, if no keep alive message has been received for more than 5 seconds.
I believe the AEM was using a value much smaller than 5 seconds before timing out and that the firmware update that AEM did was to increase the allowed time between keep alive messages on the CAN bus.
I did just go look at the keep alive poll times of the V3 firmware v's the V8 pass-thru software.
The V3 firmware uses a 900ms poll time, so it sends a keep alive to the AEM within every 1 second.
The V8 pass-thru software uses a 1800ms poll time, so it sends a keep alive within every 2 seconds.
If the AEM is using, say a 1 second timeout, that would explain why the V3 stand alone mode works while the pass-thru does not.
Would you be interested in testing that theory? If so let me know and I will change the V8 software to be the same as the firmware, using 900ms instead of 1800ms.
Regards
Paul
Before asking for help, please read this.
Posting Permissions
