EFILive Home Page | Downloads | Support Forum
Home
Up
 

 

 

General

Vehicle definition files directory
Specify the directory in which you would like EFILive to load and save your vehicle definition files.

Vehicle definition files are saved as XML files.

  • Select Auto save to automatically save any changes made to vehicle definition files
  • Select Prompt to have EFILive prompt you to save any changes that may have been made to vehicle definition files.
  • Select Discard to have changes made to vehicle definition files automatically discarded.

Logged data files directory
Specify the directory in which you would like EFILive to load and save your logged data files.

Data files are saved as either ALG or BIN files and their default name is either vvvv_yyyymmdd_hhnnss.alg or ddhhnnss.alg depending on the 8.3 filename checkbox.

If at least 10% of the frames are mode $02 or mode $03 data then the logged data is saved as a BIN file - only the data bytes of the frames are saved. Timestamps, headers and checksums are discarded. The BIN file will contain only the memory bytes dumped from the mode $02 or mode $03 command. BIN files cannot be reloaded into EFILive V4.

  • Select Auto save to automatically save any changes made to logged data files
  • Select Prompt to have EFILive prompt you to save any changes that may have been made to logged data files.
  • Select Discard to have changes made to logged data files automatically discarded.
  • Check 8.3 filename to have EFILive automatically generate 8.3 format filenames.

Help files directory
Specify the directory which contains the EFILive V4 help file "index.htm". For a standard installation this will be:
 C:\Program Files\EFILive\V4\Doc

Comms

Port
Select the serial communications port that is connected to the ALDL via the ALDL cable.

Baud
Select the baud rate that best matches the ALDL.
For the GM 8192 baud protocol the appropriate setting is 8192.

Data
Select the number of data bits per byte.
For the GM 8192 baud protocol the appropriate setting is 8.

Parity
Select the type of parity checking.
For the GM 8192 baud protocol the appropriate setting is None.

Stop
Select the number of stop bits per byte.
For the GM 8192 baud protocol the appropriate setting is 1.

Input
The input buffer size should be at least as large as the largest frame expected from the vehicle.
For the GM 8192 baud protocol the appropriate setting is 256 bytes.

Output
The output buffer size should be at least as large as the largest frame expected to be sent to the vehicle.
For the GM 8192 baud protocol the appropriate setting is 256 bytes.

Max232 echo
Check this box if the Max232 circuit that is in use echoes data that is transmitted from the PC. EFILive will then look for and discard the echo.

Hold DTR line high
If this box is checked, EFILive V4 will hold the DTR (Data Terminal Ready) pin high. This pin can be used to power Max232 circuits.

Hold RTS line high
If this box is checked, EFILive V4 will hold the RTS (Request To Send) pin high. This pin can be used to power Max232 circuits.
 

Speed

Frame capture rate
The frame capture rate is a very accurate real-time data throttle. Because Microsoft Windows® is a pre-emptive, multitasking operating system, EFILive may be interrupted. The timing algorithms employed by EFILive will attempt to recalibrate after any such interruption. This interruption/recalibration can be observed in the frame timestamps.

If for example a setting of 10 frames per second was requested, the first 50 or so frames would be captured at 100ms intervals, then say, EFILive was interrupted by the operating system and didn't get to process frame 51 until 130ms after frame 50. EFILive will attempt to recalibrate the frame timing by only waiting 70 ms so that frame 52 would be processed on the correct 100ms interval.

i.e.

Frame Timestamp
0 12.000
1 12.100
2 12.200
Interruption
3 12.345
Recalibration
4 12.400
5 12.500
... ...

Even though EFILive provides frame timestamps accurate to 1 millisecond, the data in the reply frame was probably NOT generated at that millisecond.

Also, each data byte in the data frame WILL have been generated at different times and in NO particular order.

The only absolute observations that can be made regarding frame timings are:

  • The current frame's data was generated between the previous frame's timestamp and the current frame's timestamp.
  • The last byte of the reply frame was received by EFILive in the millisecond that is the frame's timestamp.

 

Playback speed
Determines the playback speed. For example: to play back logged data at half normal speed, specify 0.5. To play back logged data at twice normal speed specify 2.0.

 

Misc

Rows
When EFILive V4 displays popup menus in response to the right mouse button they can sometimes be too long to fit on the screen. Set this value to determine how many items to display in a popup menu. If there are more items to display then EFILive will create more than one column for the menu.

 


Copyright 1998-2006 EFILive Limited