Jump to content
SAU Community

Recommended Posts

Hey all I just ordered and installed a consult port on my car to see if it would help me find where my error 21 is coming from. I installed the application on my laptop and everything seems to be working fine, I did the balance test and played with a few of the settings just to make sure and all is good. Turning the cylinders off one by one changes the note and when turned back on it returns to normal. When I activate the base idle adjustment it seems to get a smoother idle than when I turn it off. Neway I am straying, I did a diagnostic and came up with the 21 cleared it using the consult port with just the ignition on checked it with just ignition on and everything came back 55 but as soon as I start the car the 21 shows back up, on ignition on all is well but as soon as I crank it the 21 appears in the diagnostic. Now I did an idle log and will upload and I would appreciate someone who knows how to read it to give me a hand and tell me what it means cause I have no idea. Also I noticed at idle my timing is at 0btc and then increases with revs, is it suppose to be at zero on idle?

P.S. Well for some reason I cannot attach files so If you want me to send the log just p.m. me and I will send to email or something.

Link to comment
https://www.sau.com.au/forums/topic/256666-consult-port-log/
Share on other sites

Here are the logs I managed to upload them. Can anyone diagnose this or do I need to record a run? Also my turbo timer has mysteriously stopped working, I had not used it for awhile do to the car being parked so I cut it off. Now when I decided to put it to use since I got the car on the road again it doesn't work, the car ignition stays on but the car does not run. Ignition stays on for the allotted time but the car refuses to remain running, can this be because of the 21 error code as well.

idle_log.txt

021020091855.sLog.txt

0211200982925.sLog.txt

all those logs are fairly useless. try get a log with ecutalk and post that (if theres no proper logging for scantech). the cylinder tests dont seem to show much drop at all. with the cylinder tests its often more up to you to work out which cylinder has least differences to engine when its turned off as without a steady idle the logs dont show much

is the engine warm when you get the 0btdc timing? it should generally always be >0 for a normal car, up past 5 most often - but this may just be a symptom of whatever is causing error 21.

all those logs are fairly useless. try get a log with ecutalk and post that (if theres no proper logging for scantech). the cylinder tests dont seem to show much drop at all. with the cylinder tests its often more up to you to work out which cylinder has least differences to engine when its turned off as without a steady idle the logs dont show much

is the engine warm when you get the 0btdc timing? it should generally always be >0 for a normal car, up past 5 most often - but this may just be a symptom of whatever is causing error 21.

Ok will do. I would have done already but when I try to connect with ecu talk it says it is connected the guages don't read anything, but it reads my one fault code the 21. Weird I know but that's just my luck. As soon as I get the ecu talk working I will re-post a log, do you want a log of the car driving normally or just a log of it idling warm for about 5 minutes or so? Also when I got the 0btcd I think the car was warm cause I had just arrived home shut it off and then connected the laptop, I can not be to sure though but I will pay more attention with the next log. Thanks and be on the look out for the next post.

Edited by Daboss

can also try tecu if you want

http://www.ecutalk.com/interface/readme.html

there are instructions for installation there, though only works on COM1 or COM2 (edit the com.dat to COM2 or something, or u double click the port label thing on the main screen, cant remember)

not sure if calumsult has logging or not but thats an option also

try to get log from driving, and try to note when exactly u feel the hesistation or whatever (perhaps try to pull over soon after and stop the log, so you can backtrack roughly how far back in the log and work out roughly where it happened - then u can work out if its gone back to 0btdc at that point or something else funny has happened)

can also try tecu if you want

http://www.ecutalk.com/interface/readme.html

there are instructions for installation there, though only works on COM1 or COM2 (edit the com.dat to COM2 or something, or u double click the port label thing on the main screen, cant remember)

not sure if calumsult has logging or not but thats an option also

try to get log from driving, and try to note when exactly u feel the hesistation or whatever (perhaps try to pull over soon after and stop the log, so you can backtrack roughly how far back in the log and work out roughly where it happened - then u can work out if its gone back to 0btdc at that point or something else funny has happened)

The problem isn't a hesitation its the error 21 I can not get rid of and the problem with my turbo timer keeping the ignition on , but the car does not run it shuts off while all the lights on the dash and everything remain on for the length of the timer. I was asking if seeing 0dbtc at idle was a problem?

0 isnt 'normal', you might hover around 5 perhaps dipping a bit below now and then, but 0 (especially if constantly at 0) isnt normal. but 0btdc timing is most likely just a symptom of whatever is the actual cause (ie the car going into some safe mode due to the 21 error code). i guess get the turbo timer sorted/removed and then see if that was the cause or not

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • perhaps i should have mentioned, I plugged the unit in before i handed over to the electronics repair shop to see what damaged had been caused and the unit worked (ac controls, rear demister etc) bar the lights behind the lcd. i would assume that the diode was only to control lighting and didnt harm anything else i got the unit back from the electronics repair shop and all is well (to a point). The lights are back on and ac controls are working. im still paranoid as i beleive the repairer just put in any zener diode he could find and admitted asking chatgpt if its compatible   i do however have another issue... sometimes when i turn the ignition on, the climate control unit now goes through a diagnostics procedure which normally occurs when you disconnect and reconnect but this may be due to the below   to top everything off, and feel free to shoot me as im just about to do it myself anyway, while i was checking the newly repaired board by plugging in the climate control unit bare without the housing, i believe i may have shorted it on the headunit surround. Climate control unit still works but now the keyless entry doesnt work along with the dome light not turning on when you open the door. to add to this tricky situation, when you start the car and remove the key ( i have a turbo timer so car remains on) the keyless entry works. the dome light also works when you switch to the on position. fuses were checked and all ok ive deduced that the short somehow has messed with the smart entry control module as that is what controls the keyless entry and dome light on door opening   you guys wouldnt happen to have any experience with that topic lmao... im only laughing as its all i can do right now my self diagnosed adhd always gets me in a situation as i have no patience and want to get everything done in shortest amount of time as possible often ignoring crucial steps such as disconnecting battery when stuffing around with electronics or even placing a simple rag over the metallic headunit surround when placing a live pcb board on top of it   FML
    • Bit of a pity we don't have good images of the back/front of the PCB ~ that said, I found a YT vid of a teardown to replace dicky clock switches, and got enough of a glimpse to realize this PCB is the front-end to a connected to what I'll call PCBA, and as such this is all digital on this PCB..ergo, battery voltage probably doesn't make an appearance here ; that is, I'd expect them to do something on PCBA wrt power conditioning for the adjustment/display/switch PCB.... ....given what's transpired..ie; some permutation of 12vdc on a 5vdc with or without correct polarity...would explain why the zener said "no" and exploded. The transistor Q5 (M33) is likely to be a digital switching transistor...that is, package has builtin bias resistors to ensure it saturates as soon as base threshold voltage is reached (minimal rise/fall time)....and wrt the question 'what else could've fried?' ....well, I know there's an MCU on this board (display, I/O at a guess), and you hope they isolated it from this scenario...I got my crayons out, it looks a bit like this...   ...not a lot to see, or rather, everything you'd like to see disappears down a via to the other side...base drive for the transistor comes from somewhere else, what this transistor is switching is somewhere else...but the zener circuit is exclusive to all this ~ it's providing a set voltage (current limited by the 1K3 resistor R19)...and disappears somewhere else down the via I marked V out ; if the errant voltage 'jumped' the diode in the millisecond before it exploded, whatever that V out via feeds may have seen a spike... ....I'll just imagine that Q5 was switched off at the time, thus no damage should've been done....but whatever that zener feeds has to be checked... HTH
    • I think Fitmit had some, have a look on there (theyre Australian as well)
    • Hah, fair enough! But if you learn with this one you can drive any other OEM manual. No modern luxury features like auto rev-matching or hillstart assist to give you a false sense of confidence. And a heavy car with not that much torque so it stalls easily. 
×
×
  • Create New...