EFILive 5 on the Dyno...
When revving up to speed on the dyno all readings appeared normal. But when she was slammed to WOT it seems like I lost data... The data logs register fine up to about 2400rpm, but then the next data point shows approx 5500rpm. What happened to all the info in between????
Hmmmm.....
My only suggestion is, monitor less PID's when performing those sorts of WOT sessions. Theres no need for monitoring thinks like VSS or both LTFT's (and especially not STFT's) when dyno'ing.
Keep the monitoring PID count low, and you may see better results. Just a theory, I haven't tried it.
Generic OBDII: which requests data similar to the way AutoTap does. It requests one PID at a time. The speed of this mode is dependant on the number of PIDs selected.
GM Slow Dynamic: which requests up to 6 PIDs at a time. The speed of this mode is dependant on the number of PIDs selected.
GM Medium Dynamic: which requests up to 24 PIDs at a time. The speed of this mode is dependant on the number of PIDs selected.
GM Fast Dynamic: which requests that the PCM sends as much data, as fast as it can. This mode may slow if/when the PCM is busy doing something else.
You can change the scan mode by opening the Properties window and selecting the Logging tab page.
Uncheck Automatically determine scan mode and select the scan mode that you wish to use. There is no need to change the Dynamic Packet ID.
Regards
Paul
Any suggestions?
If you want to scan ONLY 1 PID then use Generic OBDII. You will get 10 samples per second if the Message Throttle is set to 100ms. (i.e. request a PID every 100ms = 10 times per second). You can choose to set the Message Throttle to a lower value for faster scanning. However the SAE recommendations for scan tools is to seperate requests by a minimum of 100ms. so if you do reduce the Message Throttle below 100ms then you may have problems because the scan tool will be flooding the OBDII communications bus with requests and other modules may not be able to communicate properly.
You can set the Message Throttle in Properties on the Advanced tab page.
If you want to scan a set of PIDs that uses 6 or less channels then use GM Slow Dynamic. This mode scans 6 channels per request. The Message Throttle settings is the same as above.
If you want to scan a set of PIDs that uses between 6 and 36 channels then use GM Medium Dynamic. This mode scans between 6 and 36 channels per request. (depending on the number of PIDs selected. The Message Throttle settings is the same as above.
This mode SHOULD be used if the bi-directional control panel is active.
If you want to scan up to 24 channels as fast as possible then use GM Fast Dynamic. This mode does not continuosly request data so the Message Throttle has no effect on this mode. The PCM is requested to send back 24 channels of data as fast as possible - under optimum conditions that is approx 10 times per second.
This mode should NOT be used if the bi-directional control panel is active.
See this page for a discussion of scan modes and update frequencies:
http://www.starrperformance.com.au/e...pdatefrequency
This page differs from the original page in the documentation that is distributed with EFILiveV5. The original page was wrong.
Hope that is not too confusing.
Regards
Paul
Trending Topics
There are a number of issues logged with V5.16 that will be fixed in version 5.17 due out by this weekend.
You can check out the issues here:
http://www.starrperformance.com.au/e...sues_index.htm
We did not see the logging lag that was described at the start of this thread, but we are still testing...
However, it could be related to Report 5.16-03
Anytime something that looks like a bug occurs in EFILiveV5 - please check this page. It will be updated regularly with any known problems and possible workarounds.
Regards
Paul
The Best V8 Stories One Small Block at Time


