Sample Rate

**DMaxME** · October 14th, 2007

I've been logging for various conditions, and the "standard" sample rate has been sufficient. Currently I'm tuning for the 1/4 mile, and the sample rate is less than satisfactory. Is there anyway to adjust that?

Also a few other questions I had for the EFI Live crew:

Will there be an update allowing more than 1 controller to be recorded during the same log, mainly ECM and TCM?

What's the status or time frame on the black box logging feature? that was the reason I purchased your product, and am still patiently waiting.

Is there any chance that you could add more external sensor expansion ports, as I would like to run more analog sensors than there are ports available. I know that's a lot to ask, and probably a far way off.

I would also like to say that I do like your product, I find it mostly intuitive and easy to use. I've had great success with it and am getting alot of questions at the track, especially as my ET's keep dropping. Thanks for all your hard work it really shows in your product.

**DMaxME** · October 15th, 2007

I guess there's no way to increase the sample rate? huh... If it's limited by the OBD Port then what about the external inputs?

**eboggs_jkvl** · October 15th, 2007

I believe the sample rate is controlled by the number of pids selected and the "Edit - Properties - Logging settings

Also...

PID data values are transmitted between the PCM and EFILive in messages. EFILive uses the OBDII, SAE J1850VPW protocol which sets limits on the size of the messages. The shortest message is 4 bytes, the longest message is 12 bytes. Up to 6 bytes of the message may be used to transmit PID data from the PCM to EFILive (a byte is a number between 0 and 255). EFILive groups multiple messages together into frames. A frame contains enough bytes to transmit the current values of ALL selected PIDs.

Some PIDs cannot be represented by a single byte (i.e. a value in the range 0 to 255), so they require two, or even four bytes to transmit their value.
EFILive calls these bytes: channels. Different scan modes impose different limits of the number of channels of data that can be transmitted per frame and therefor the number of PIDs that can be transmitted per frame.

General scan mode

This is a general-purpose scan mode supported by all OBDII compliant vehicles. Use this mode if you want to scan data from vehicles that do not support the other, faster scan modes.
All selected PIDs are requested sequentially, using a request/response strategy.
In all but a few cases, this scan mode will be the slowest. However, if you have only one or two PIDs selected, then the General scan mode will be faster than any other method.
EFILive imposes a limit on the maximum number of channels that can be requested per frame using the General scan mode. The limit is 96 channels.

The General scan mode will, in most cases, use up to 80% of the class-2 network bandwith, leaving only 20% for other modules. You can lower the bandwidth usage by increasing the Throttle setting on the Advanced tab page of the Properties window. Increasing the throttle introduces a delay between requests made by EFILive.

General scan mode is not available when using the FlashScan interface cable as a standalone block box data logging device.

**Blacky** · October 15th, 2007