Difference between revisions of "ElanScan"
m (Added link to new Base Timing page) |
|||
| Line 22: | Line 22: | ||
| − | '''No reply No frame start byte | + | '''No reply No frame start byte received ''' - Probably [TO BE CONFIRMED] caused by having the latency timer setting too high: In device manager, select | USB serial port | Port settings | Advanced | BM option | Latency timer (ms) | and set to 1. See also [http://www.astb91.dsl.pipex.com/USB_Driver_Instructions.html USB driver instructions]. |
| + | |||
| + | |||
| + | == User help == | ||
| + | |||
| + | To change the graph display, select the required parameter from the drop down boxes: | ||
| + | |||
| + | [[Image:ES_Display_Parameters.jpg|thumb|Display parameters]] | ||
== Diagnoses == | == Diagnoses == | ||
| Line 42: | Line 49: | ||
[[Category: ECU]] | [[Category: ECU]] | ||
[[Category: Diagnostics]] | [[Category: Diagnostics]] | ||
| + | [[Category: Incomplete]] | ||
Revision as of 19:35, 15 May 2008
ElanScan is a piece of software which interfaces with the Elan's ECU and can retrieve various real-time stats.
ElanScan is available for download from [ESM's website], information on obtaining or building suitable interfaces is also available at the same place.
Preparation
If you think you have a problem, CHECK THE BASE TIMING. Provided this is correct, then proceed.
Communication errors
The error log reports any bad communications between the pc/ES and then car/ECU :
Comm port inactive - The wrong communications port has been selected for ElanScan. Check in the pc hardware configuration / device manager to see which ports are present. From bitter experience, this may also indicate a broken serial port!
Bad echo (sent: F4 56 01 B5: received: ) - The ECU is not responding, usually because the ignition is not turned on or the interfaces is not properly connected [Note F4 56 01 B5 relates to the Elan turbo engine only]
Bad echo (sent: F4 56 01 B5: received: XX XX XX XX) Indicates noisy communication with the ECU, likely caused by a poor electrical connection [Note XX is the hex representation of a byte of data and there may be between one and four bytes returned depending on the problem]
No reply No frame start byte received - Probably [TO BE CONFIRMED] caused by having the latency timer setting too high: In device manager, select | USB serial port | Port settings | Advanced | BM option | Latency timer (ms) | and set to 1. See also USB driver instructions.
User help
To change the graph display, select the required parameter from the drop down boxes:
Diagnoses
Suggestions and links to LEC until they can be migrated into the Wiki (Geoff)
- Baseline ES run from cold
- Baseline ES run WOT in third gear
- Stuck thermostat
- Stuck wastegate