Spanner -announcement (electronic diagnostic unit)
#31
Rennlist Member
Thread Starter
Originally Posted by shaaark89
john,
i would love the software updates as well. can be sent to shaaark89@hotmail.com. i also had some variability in its functioning. worked on my '89 s4, not on the '90 gt or '91 gt.
thanks,
i would love the software updates as well. can be sent to shaaark89@hotmail.com. i also had some variability in its functioning. worked on my '89 s4, not on the '90 gt or '91 gt.
thanks,
Files have been sent...
Regards
#32
Rennlist Member
Question: Has anyone ever tried to hook up a 90 or older ECU into a a 91 MJ that is known to "hang"??? The ECU is plug and play just hook it up and there is not even a need to drive it or start the engine. Just let the actuator test run. This would be my first approach to isolate the problem
Last edited by Schocki; 02-06-2006 at 07:38 PM.
#33
Rennlist Member
Thread Starter
Hi Schocki,
There aren't really any differences between MY 90 and MY 91 software.....and a battery disconnect to swap units would wipe any spurious codes that might be inhibiting diagnosis.
Regards
There aren't really any differences between MY 90 and MY 91 software.....and a battery disconnect to swap units would wipe any spurious codes that might be inhibiting diagnosis.
Regards
#34
Rennlist Member
John,
That's correct but by using a different ECU you could figure out if it is an ECU problem after all. People claim that the Spanner "hangs". A MJ 91 car that is known to stop diagnostics should also stop with a MJ 90 ECU!? That would be my approach to isolate the problem. I bet it will hang with a different ECU as well.
It would be also possible to put a non-problem ECU into a problem car and drive it around the block and check. I don't think that the problem is in the ECU's at all, but that's theory.
That's correct but by using a different ECU you could figure out if it is an ECU problem after all. People claim that the Spanner "hangs". A MJ 91 car that is known to stop diagnostics should also stop with a MJ 90 ECU!? That would be my approach to isolate the problem. I bet it will hang with a different ECU as well.
It would be also possible to put a non-problem ECU into a problem car and drive it around the block and check. I don't think that the problem is in the ECU's at all, but that's theory.
Last edited by Schocki; 02-07-2006 at 09:09 AM.
#39
Addict
Rennlist Member
Rennlist Member
John,
About half a year ago, I was using my Spanner (firmware version 0.31, as it still is) for resetting my air bag malfunction fault after having cleaned a connector to a sensor. (It worked great for that, BTW).
However, as I tried other tests (LH diagnostics, EZK diagnostics), it seemed like the Spanner would get out of sync and I'd get a lot of messages like "*6 The Code: xxxx is undefined". I didn't take very good notes, but I did note that this happened during an EZK Test Run and an LH Test Run, and that the undefined codes were 1700, 1300, 1480, 3010, 3310, 3100. I also see that I noted that on a PSD Diag, I got the "The Code: xxxx is undefined" with codes 5670, 6800, 6300, and 1700.
And then at some point, I also noted something completely unforgivable. It actually read, "To Claer EZK...". Of course, I had no idea what it meant, thinking perhaps this was some arcane Britishism.
In all seriousness, is it likely that I might fare better with the latest firmware? I'd be happy to give it a try.
About half a year ago, I was using my Spanner (firmware version 0.31, as it still is) for resetting my air bag malfunction fault after having cleaned a connector to a sensor. (It worked great for that, BTW).
However, as I tried other tests (LH diagnostics, EZK diagnostics), it seemed like the Spanner would get out of sync and I'd get a lot of messages like "*6 The Code: xxxx is undefined". I didn't take very good notes, but I did note that this happened during an EZK Test Run and an LH Test Run, and that the undefined codes were 1700, 1300, 1480, 3010, 3310, 3100. I also see that I noted that on a PSD Diag, I got the "The Code: xxxx is undefined" with codes 5670, 6800, 6300, and 1700.
And then at some point, I also noted something completely unforgivable. It actually read, "To Claer EZK...". Of course, I had no idea what it meant, thinking perhaps this was some arcane Britishism.
In all seriousness, is it likely that I might fare better with the latest firmware? I'd be happy to give it a try.
#41
Rennlist Member
Thread Starter
Hi Ed,
Thanks for your feedback. Yes the foreign word has been changed in Ver 33 :-) I would suggest doing a battery disconnect, then test drive the car, and then try reading the codes. Sprious codes have been known, and for this reason Porsche arrranged for codes to be deleted every so often, automatically.
Ver 33 has strengthened the decode algorithm, and also prevents the Spanner from hanging up on "working" is it can't make sense of what it is receiving. If you send me an emial to my website mail address I will send you the updated files...
Hi Ernest,
Is this with Ver 33 ?
Thanks for your feedback. Yes the foreign word has been changed in Ver 33 :-) I would suggest doing a battery disconnect, then test drive the car, and then try reading the codes. Sprious codes have been known, and for this reason Porsche arrranged for codes to be deleted every so often, automatically.
Ver 33 has strengthened the decode algorithm, and also prevents the Spanner from hanging up on "working" is it can't make sense of what it is receiving. If you send me an emial to my website mail address I will send you the updated files...
Hi Ernest,
Is this with Ver 33 ?
#42
Addict
Rennlist Member
Rennlist Member
Join Date: Oct 2003
Location: Gone. On the Open Road
Posts: 16,498
Received 1,638 Likes
on
1,069 Posts
John, can you give us a description of compatibility between the various years for the ECUs? For purposes of isolating issues with an ECU which units can be swapped from MY to MY? Can I put a '91 LH in to a '94? An '91 in an '89? etc. Note, I'm asking only about diagnostic compatibility not about actually running the cars with 'wrong-year' ECUs.
#44
Rennlist Member
Thread Starter
Hi Dave C.
As far as diagnostics are concerned, all LH ECU MY88 onwards have diagnostic software. Swapping them from car to car isn't a problem for diagnostics.
As the years went by, the diagnostics software in the ECU got a little cleverer all the time in recognising potential fault conditions, and then flagging up a fault code.
e.g. if temp sensor 2 value changes rapidly with later software, it logs a fault code. Earlier software just tells you if temp sensor 2 is open or short circuit for a significant length of time.
BTW while on the subject of temp 2, if any LH logs a fault with temp 2 (open or short circuit), it automatically defaults the LH to the settings at normal enginen temperature. So engine running problems when engine is hot is not likely to be the temp 2 sensor. But cold running/warm up running problems could be due to temp2 sensor.
Hi Ernest,
OK, understood. I don't think Roger has updated his software yet.
As far as diagnostics are concerned, all LH ECU MY88 onwards have diagnostic software. Swapping them from car to car isn't a problem for diagnostics.
As the years went by, the diagnostics software in the ECU got a little cleverer all the time in recognising potential fault conditions, and then flagging up a fault code.
e.g. if temp sensor 2 value changes rapidly with later software, it logs a fault code. Earlier software just tells you if temp sensor 2 is open or short circuit for a significant length of time.
BTW while on the subject of temp 2, if any LH logs a fault with temp 2 (open or short circuit), it automatically defaults the LH to the settings at normal enginen temperature. So engine running problems when engine is hot is not likely to be the temp 2 sensor. But cold running/warm up running problems could be due to temp2 sensor.
Hi Ernest,
OK, understood. I don't think Roger has updated his software yet.