View Full Version : dashboard cutting out after few seconds

May 26th, 2013, 04:01 PM
After some assistance please, i am using professional software which is connecting and working no probs, the only thing is when in the dashboard mode with the engine running it only lasts for a few seconds then you have to hit the green button every time,then a few times latter it stops working all together, when the engine is not running the dash works continuously reading the info.


May 27th, 2013, 05:06 PM
Can you turn on View->Serial I/O and log the data until it cuts out.
Then copy/paste the text into this thread so I can see what is happening.


June 2nd, 2013, 10:00 PM
59:11.510: Finished reading frame
59:11.510: MAX232 echo: $F4,$58,$04,$81,$00,$2F
59:11.510: Wait 10 ms after writing, before reading...
59:11.520: Start reading frame
59:11.521: Aldl frame header byte: $F4
59:11.521: Aldl frame length byte: $56
59:11.521: Recv: $F4,$56,$04,$B2
59:11.521: Finished reading frame
59:11.599: Start writing frame
59:11.599: Send: $F4,$5E,$04,$00,$00,$00,$00,$00,$00,$10,$FF,$9B
59:11.599: Finished writing frame
59:11.599: Wait 10 ms after writing, before reading...
59:11.609: Start reading frame
59:11.609: Aldl frame header byte: $F4
59:11.609: Aldl frame length byte: $5E
59:11.620: Recv: $F4,$5E,$04,$00,$00,$00,$00,$00,$00,$10,$FF,$9B
59:11.620: Finished reading frame
59:11.620: MAX232 echo: $F4,$5E,$04,$00,$00,$00,$00,$00,$00,$10,$FF,$9B
59:11.620: Wait 10 ms after writing, before reading...
59:11.630: Start reading frame
59:11.630: Aldl frame header byte: $F4
59:11.630: Aldl frame length byte: $56
59:11.630: Recv: $F4,$56,$04,$B2
59:11.630: Finished reading frame
59:11.699: Start writing frame
59:11.699: Send: $F4,$57,$01,$00,$B4
59:11.699: Finished writing frame
59:11.699: Wait 10 ms after writing, before reading...
59:11.709: Start reading frame
59:11.710: Aldl frame header byte: $F4
59:11.710: Aldl frame length byte: $57
59:11.710: Recv: $F4,$57,$01,$00,$B4
59:11.710: Finished reading frame
59:11.710: MAX232 echo: $F4,$57,$01,$00,$B4
59:11.710: Wait 10 ms after writing, before reading...
59:11.720: Start reading frame
59:11.720: Aldl frame header byte: $F4
59:11.720: Aldl frame length byte: $8E
59:11.914: Com timeout: Data frame truncated: $F4,$8E,$01,$02,$E8,$03,$00,$AD,$7D,$8D,$70,$F0,$F B,$15,$C8,$00,$74,$00,$01,$25,$8C,$80,$7D,$16,$88, $03,$8B,$FF,$8A,$04,$00,$C6,$3A,$00,$38,$00,$00,$1 C,$06,$72,$00,$00,$00,$80,$00,$00,$00,$00,$00,$00, $20,$00,$15,$00,$00,$00,$00,$00,$A4,$00
59:11.915: Aborting request due to previous error
59:11.916: Start writing frame
59:11.916: Send: $F4,$57,$01,$00,$B4
59:11.916: Finished writing frame
59:11.916: Wait 10 ms after writing, before reading...
59:11.926: Start reading frame
59:11.927: Aldl frame header byte: $F4
59:11.927: Aldl frame length byte: $57
59:11.927: Recv: $F4,$57,$01,$00,$B4
59:11.927: Finished reading frame
59:11.927: MAX232 echo: $F4,$57,$01,$00,$B4
59:11.927: Wait 10 ms after writing, before reading...
59:11.937: Start reading frame
59:11.937: Aldl frame header byte: $F4
59:11.937: Aldl frame length byte: $8E
59:12.132: Com timeout: Data frame truncated: $F4,$8E,$01,$03,$09,$03,$00,$AD,$7D,$8D,$70,$4E,$3 F,$FB,$15,$C8,$00,$6B,$00,$01,$19,$8C,$80,$7D,$16, $88,$E7,$F6,$8A,$04,$00,$E1,$3A,$00,$33,$00,$00,$1 C,$06,$72,$00,$00,$00,$80,$00,$00,$00,$00,$00,$00, $20,$00,$16,$00,$00,$00,$00,$00,$83,$00
59:12.133: Aborting request due to previous error
59:12.134: Start writing frame
59:12.134: Send: $F4,$57,$01,$00,$B4
59:12.134: Finished writing frame
59:12.134: Wait 10 ms after writing, before reading...
59:12.144: Start reading frame
59:12.145: Aldl frame header byte: $F4
59:12.145: Aldl frame length byte: $57
59:12.145: Recv: $F4,$57,$01,$00,$B4
59:12.145: Finished reading frame
59:12.145: MAX232 echo: $F4,$57,$01,$00,$B4
59:12.145: Wait 10 ms after writing, before reading...
59:12.155: Start reading frame
59:12.155: Aldl frame header byte: $F4
59:12.155: Aldl frame length byte: $8E
59:12.350: Com timeout: Data frame truncated: $F4,$8E,$01,$02,$E6,$03,$00,$AD,$7D,$8D,$70,$4F,$3 F,$FB,$15,$C8,$00,$6B,$00,$01,$1E,$8C,$80,$7D,$16, $89,$03,$8A,$FF,$8A,$04,$00,$EA,$3A,$00,$3A,$00,$0 0,$1C,$06,$72,$00,$00,$80,$00,$00,$00,$00,$00,$00, $20,$00,$16,$00,$00,$00,$00,$00,$91,$00
59:12.354: Aborting request due to previous error
59:12.358: Stop macro: Common Dyno Setup: DYNO

June 3rd, 2013, 09:30 AM
Can you please send the *.xml vehicle definition file that you are using to me at paul@efilive.com and also let me know what type of vehicle you are trying to log?


June 3rd, 2013, 12:15 PM
Hi Paul,

I am connecting to a vs v8 commodore, using the file to suit the car thats allready in the efilive software,all functions work except when you start the engine the dashboard wont work, the commands work (eg-fuel pump off , inj off etc) just the dashboard doesnt work.


June 3rd, 2013, 01:02 PM
It looks like the checksum byte (the very last byte - which is always showing as zero in the trace above) is not being transmitted by the PCM before the normal 200ms (i.e. T3) elapses. I'm not sure why it would work with the engine off but fail with the engine on.

Try increasing T3 (on the [Timing] tab page of the vehicle definition) to around 500ms to see if waiting an extra 300ms will help.


June 3rd, 2013, 01:07 PM
Can you also post a trace of the same data (that works) with the engine off?

June 15th, 2013, 10:34 PM
31:45.707: Start macro: ECM Engine Data: Engine Data Table0
31:45.695: Start writing frame
31:45.695: Send: $F4,$57,$01,$00,$B4
31:45.695: Finished writing frame
31:45.695: Wait 10 ms after writing, before reading...
31:45.705: Start reading frame
31:45.706: Aldl frame header byte: $F4
31:45.706: Aldl frame length byte: $57
31:45.706: Recv: $F4,$57,$01,$00,$B4
31:45.706: Finished reading frame
31:45.706: MAX232 echo: $F4,$57,$01,$00,$B4
31:45.706: Wait 10 ms after writing, before reading...
31:45.716: Start reading frame
31:45.716: Aldl frame header byte: $F4
31:45.716: Aldl frame length byte: $8E
31:45.781: Recv: $F4,$8E,$01,$00,$00,$02,$EE,$97,$8D,$60,$89,$FA,$F F,$FB,$15,$C0,$00,$65,$00,$06,$C0,$7B,$80,$74,$04, $63,$03,$7A,$FF,$80,$00,$00,$00,$90,$00,$41,$00,$0 0,$1C,$00,$7E,$00,$00,$00,$80,$00,$00,$00,$00,$00, $00,$20,$00,$00,$00,$00,$00,$00,$00,$AF
31:45.781: Finished reading frame
31:45.795: Start writing frame
31:45.795: Send: $F4,$57,$01,$00,$B4
31:45.795: Finished writing frame
31:45.795: Wait 10 ms after writing, before reading...
31:45.805: Start reading frame
31:45.806: Aldl frame header byte: $F4
31:45.806: Aldl frame length byte: $57
31:45.806: Recv: $F4,$57,$01,$00,$B4
31:45.806: Finished reading frame
31:45.806: MAX232 echo: $F4,$57,$01,$00,$B4
31:45.806: Wait 10 ms after writing, before reading...
31:45.816: Start reading frame
31:45.816: Aldl frame header byte: $F4
31:45.816: Aldl frame length byte: $8E
31:45.881: Recv: $F4,$8E,$01,$00,$00,$02,$EE,$97,$8D,$60,$89,$FA,$F F,$FB,$15,$C0,$00,$65,$00,$06,$C0,$7B,$80,$74,$04, $63,$03,$7A,$FF,$80,$00,$00,$00,$90,$00,$41,$00,$0 0,$1C,$00,$7E,$00,$00,$00,$80,$00,$00,$00,$00,$00, $00,$20,$00,$00,$00,$00,$00,$00,$00,$AF
31:45.881: Finished reading frame

It works fine when the engine is not running.

June 16th, 2013, 02:37 PM
Notice the frames that do not get the "truncated" error, they all end with a non-zero byte. That byte is the checksum byte, its value is calculated so that adding an 8-bit sum of all bytes in the message results in $00.
The frames that do get a "truncated" error are being transmitted one byte short. You can tell because the checksum byte is the second last byte instead of the last byte (the last byte is added by EFILive to make the frame the correct length).

That means when the engine is running something is interfering with the normal data transmission from the ECM. It could be any of (in most to least likely):

A fault in the ALDL interface or cabling that you are using that is triggered by the engine running - maybe the voltage supply to the ALDL interface is unstable.
Bad earth connection(s) in the vehicle.
Electrical noise from the engine or alternator.
A fault in the ECM itself.


June 16th, 2013, 03:53 PM
I've recently come across a wideband powersupply that was so noisy it was screwing with the ALDL data, disconnect the wideband and it was fine. Ran a separate earth for the wideband and it was all good. Some are a lot noiser in their power supplies than others. Never had any issues with Techedge ones but Innovate and AEM appear to be very agressive and noisy in their power supply - probably due to how they drive the wideband heater.