type 1 Consult disconnects ***FIXED***
Posted: Sat Sep 05, 2009 12:52 pm
Hi all,
Thought I'd share this one as it drove me crazy for an Hour.
Symptom: Consult disconnects randomly seemed more frequent in medium traffic condition.
Error condition: consult changes from "red" connected to ECU state to a non connected state, any logging also stops. sometimes "Not receiving data from ECU" error is displayed if consult has dropped for extended periods.
Cause: Customer hooked up an auxillary 15"" thermo to brake switch for cooling intercooler during stop conditions for pits at WSID.
Possible Solutions: 1. Disconect aux fan,. upgrade battery, change alternator pulley to spin it faster. I just removed the fuse for the aux fan.
Everytime i hit the brakes the ECU voltage momentarily dropped below an unknown threshold and Nistune seems to be very sensitive to this condition. I noticed that 13.8 was the lowest voltage recorded in Nistune.
Maybe we could see a fix for the comms timeout increased in the later additions. I would also beg for an improvement to the logging, It mustn't stop after a car stalls. It needs to continue logging after car restarts automatically. the logging improvment would only be a benefit if Nistune Consult didn't disconnect from a short period of no comms or voltage drop.
Thought I'd share this one as it drove me crazy for an Hour.
Symptom: Consult disconnects randomly seemed more frequent in medium traffic condition.
Error condition: consult changes from "red" connected to ECU state to a non connected state, any logging also stops. sometimes "Not receiving data from ECU" error is displayed if consult has dropped for extended periods.
Cause: Customer hooked up an auxillary 15"" thermo to brake switch for cooling intercooler during stop conditions for pits at WSID.
Possible Solutions: 1. Disconect aux fan,. upgrade battery, change alternator pulley to spin it faster. I just removed the fuse for the aux fan.
Everytime i hit the brakes the ECU voltage momentarily dropped below an unknown threshold and Nistune seems to be very sensitive to this condition. I noticed that 13.8 was the lowest voltage recorded in Nistune.
Maybe we could see a fix for the comms timeout increased in the later additions. I would also beg for an improvement to the logging, It mustn't stop after a car stalls. It needs to continue logging after car restarts automatically. the logging improvment would only be a benefit if Nistune Consult didn't disconnect from a short period of no comms or voltage drop.