ScanTool engine results for 95 OBD 1
07-17-2006 | 12:27 AM
#31
Race Car
Joined: May 2003
Posts: 4,045
Likes: 61
From: SoCal
"When the engine is not running or it's running and the 02 sensor hasn't warmed up, there is a substitute voltage on the 02 sensor channel so it should never show 0."
That's basically it!
Remember, the O2 sensor is a voltage source with a farely low impedance output
when hot. The O2 voltage input to the DME is a high impedance input with
a voltage reference of about .45 to .55 volts. When the O2 is not hot it's output
impedance is high (& no voltage), thus DME reference voltage takes effect
(overrides), thereby causing the DME to default to a center point fuel mixture (AFR).
That's basically it!
Remember, the O2 sensor is a voltage source with a farely low impedance output
when hot. The O2 voltage input to the DME is a high impedance input with
a voltage reference of about .45 to .55 volts. When the O2 is not hot it's output
impedance is high (& no voltage), thus DME reference voltage takes effect
(overrides), thereby causing the DME to default to a center point fuel mixture (AFR).
07-17-2006 | 01:52 AM
#32
Thread Starter
Instructor
Joined: Dec 2005
Posts: 132
Likes: 0
Doug,
Have you looked over the Base Ijection Time and base LOAD jpg?
The UINT16 isn't doing anything
Actual Value.Base Injection time=0x3f;;##.### ms;UINT16 gives 3, 2, 2 @ 800, 2120, 2960 RPM.
Actual Value.Base Injection 0x03f=0x3f also gives 3, 2, 2 @ 800, 2120, 2960 RPM.
The UINT16 isn't doing anything Also time should be around 2.6 msec
Actual Value.Base Inj LOAD 0x03e=0x3e gives 33,29,28 @ 800, 2120, 2960 RPM.
33, 29, 28 should be 1.2, 1.3 msec
Ray
Have you looked over the Base Ijection Time and base LOAD jpg?
The UINT16 isn't doing anything
Actual Value.Base Injection time=0x3f;;##.### ms;UINT16 gives 3, 2, 2 @ 800, 2120, 2960 RPM.
Actual Value.Base Injection 0x03f=0x3f also gives 3, 2, 2 @ 800, 2120, 2960 RPM.
The UINT16 isn't doing anything Also time should be around 2.6 msec
Actual Value.Base Inj LOAD 0x03e=0x3e gives 33,29,28 @ 800, 2120, 2960 RPM.
33, 29, 28 should be 1.2, 1.3 msec
Ray
07-17-2006 | 10:10 AM
#33
Advanced
Joined: Jun 2001
Posts: 99
Likes: 0
From: Florida
Ray,
Do you perhaps have a really old version of the software? Look at the date on the scantool.exe file.
You can fetch the latest version here.
You can actually keep multiple versions of the software on your machine--just place them in different folders.
-doug
Do you perhaps have a really old version of the software? Look at the date on the scantool.exe file.
You can fetch the latest version here.
You can actually keep multiple versions of the software on your machine--just place them in different folders.
-doug
Originally Posted by raycm
Doug,
Have you looked over the Base Ijection Time and base LOAD jpg?
The UINT16 isn't doing anything
Actual Value.Base Injection time=0x3f;;##.### ms;UINT16 gives 3, 2, 2 @ 800, 2120, 2960 RPM.
Actual Value.Base Injection 0x03f=0x3f also gives 3, 2, 2 @ 800, 2120, 2960 RPM.
The UINT16 isn't doing anything Also time should be around 2.6 msec
Actual Value.Base Inj LOAD 0x03e=0x3e gives 33,29,28 @ 800, 2120, 2960 RPM.
33, 29, 28 should be 1.2, 1.3 msec
Ray
Have you looked over the Base Ijection Time and base LOAD jpg?
The UINT16 isn't doing anything
Actual Value.Base Injection time=0x3f;;##.### ms;UINT16 gives 3, 2, 2 @ 800, 2120, 2960 RPM.
Actual Value.Base Injection 0x03f=0x3f also gives 3, 2, 2 @ 800, 2120, 2960 RPM.
The UINT16 isn't doing anything Also time should be around 2.6 msec
Actual Value.Base Inj LOAD 0x03e=0x3e gives 33,29,28 @ 800, 2120, 2960 RPM.
33, 29, 28 should be 1.2, 1.3 msec
Ray
07-17-2006 | 09:23 PM
#35
Thread Starter
Instructor
Joined: Dec 2005
Posts: 132
Likes: 0
OK, here are the results for the INPUTS and ACTUAL Values using scantool 4 06/01/06 rev.
This rev. makes Actual Value.Base Injection time=0x3f;;##.### ms;UINT16 work. And check boxes cause updating.
The TEST OUTPUT cycles through tests. My aux heater fan on the engine however prevented me from hearing anything but a couple clicks. I'll redo with cold engine. I've attached a table with results of INPUT & ACTUAL Values. IDLE, driving, & full throttle in low gear. The throttle angle looks nice. Here is scantool.cfg for this test.
Input.1=Throttle Angle:;(n-26)*42;##.##°
Input.2=Battery:;(n*682)/100;##.## Volts
Input.3=Always 0:
Input.4=EnTmpSen:
Input.5=MAF Sensor:;((n*500)/255);#.## Volts
Input.6=Always 0:
Input.7=Ig Tme Chng?:;n*1;#.#°
Input.8=O2 sensor:
Switch.1=?:
Switch.2=?:
Actual Value.Battery (V)=0x36;(n*682)/100;##.## Volts
Actual Value.IATS Int Air Temp 0-40 (°C)=0x37;((((n*115)/100)-26)-32)*5/9;###°
Actual Value.ECTS Cyl Head Temp 0-100 (°C)=0x38;((((n*115)/100)-26)-32)*5/9;###°
Actual Value.Engine Speed 800 idle=0x39;n*40;#### rpm
Actual Value.OLD-Ign Time 0x3a=0x3a;n*1;###.#°
Actual Value.OLD-H02S 0x3b=0x3b;n*1;#### mV
Actual Value.MAF SENSOR = 0x47;((n*500)/255);#.## Volts
Actual Value.0x59=0x59;n*1;###.## ms
Actual Value.Base Injection time=0x3f;;##.### ms;UINT16
Actual Value.Base Injection 0x03f=0x3f
Actual Value.Base Inj 8-bit LOAD=0x3e;((n*50)/2);#.## msec
Seems INPUTS are working. Except I don't know validity of Ing Tme Chng.
Actual Values have issues and good stuff.
Engine maintains 117 degress max throughout my tests. Nice, but I did put a resistor across my oil temp sensor to keep it cooler at autox.
RPM looks good to 6400 RPM. Nice.
MAF Sensor range only 0.8 to 1.45 Volts but does follow INPUTS MAF.
Base Inj Time 0.385 full throttle, 0.777 idle. Supposed to be ~2.6 msec
Base Inj LOAD 7.75 @ idle, 5.00 full throttle. I tried to multipy by 25 and *50/2 but it ignores those changes and reports the same numbers. Should be ~1.2msec.
My guess at timing. INPUTS Ig. Tme. Chng 5.4 to 6.1. Actual Values Ing. Tming 7.8 to 25.5 max. Seems odd 25.5 max which it reaches around 3000 RPM in the garage. HO2S has nice numbers but I don't know if this is the correct location.
I plan on deleting my earlier attachments so as to lower my storage count. I saved those messages in my PC.
Ray
This rev. makes Actual Value.Base Injection time=0x3f;;##.### ms;UINT16 work. And check boxes cause updating.
The TEST OUTPUT cycles through tests. My aux heater fan on the engine however prevented me from hearing anything but a couple clicks. I'll redo with cold engine. I've attached a table with results of INPUT & ACTUAL Values. IDLE, driving, & full throttle in low gear. The throttle angle looks nice. Here is scantool.cfg for this test.
Input.1=Throttle Angle:;(n-26)*42;##.##°
Input.2=Battery:;(n*682)/100;##.## Volts
Input.3=Always 0:
Input.4=EnTmpSen:
Input.5=MAF Sensor:;((n*500)/255);#.## Volts
Input.6=Always 0:
Input.7=Ig Tme Chng?:;n*1;#.#°
Input.8=O2 sensor:
Switch.1=?:
Switch.2=?:
Actual Value.Battery (V)=0x36;(n*682)/100;##.## Volts
Actual Value.IATS Int Air Temp 0-40 (°C)=0x37;((((n*115)/100)-26)-32)*5/9;###°
Actual Value.ECTS Cyl Head Temp 0-100 (°C)=0x38;((((n*115)/100)-26)-32)*5/9;###°
Actual Value.Engine Speed 800 idle=0x39;n*40;#### rpm
Actual Value.OLD-Ign Time 0x3a=0x3a;n*1;###.#°
Actual Value.OLD-H02S 0x3b=0x3b;n*1;#### mV
Actual Value.MAF SENSOR = 0x47;((n*500)/255);#.## Volts
Actual Value.0x59=0x59;n*1;###.## ms
Actual Value.Base Injection time=0x3f;;##.### ms;UINT16
Actual Value.Base Injection 0x03f=0x3f
Actual Value.Base Inj 8-bit LOAD=0x3e;((n*50)/2);#.## msec
Seems INPUTS are working. Except I don't know validity of Ing Tme Chng.
Actual Values have issues and good stuff.
Engine maintains 117 degress max throughout my tests. Nice, but I did put a resistor across my oil temp sensor to keep it cooler at autox.
RPM looks good to 6400 RPM. Nice.
MAF Sensor range only 0.8 to 1.45 Volts but does follow INPUTS MAF.
Base Inj Time 0.385 full throttle, 0.777 idle. Supposed to be ~2.6 msec
Base Inj LOAD 7.75 @ idle, 5.00 full throttle. I tried to multipy by 25 and *50/2 but it ignores those changes and reports the same numbers. Should be ~1.2msec.
My guess at timing. INPUTS Ig. Tme. Chng 5.4 to 6.1. Actual Values Ing. Tming 7.8 to 25.5 max. Seems odd 25.5 max which it reaches around 3000 RPM in the garage. HO2S has nice numbers but I don't know if this is the correct location.
I plan on deleting my earlier attachments so as to lower my storage count. I saved those messages in my PC.
Ray
Last edited by raycm; 08-21-2006 at 08:57 PM. Reason: reduce my attachment storage.
07-18-2006 | 07:08 PM
#36
Thread Starter
Instructor
Joined: Dec 2005
Posts: 132
Likes: 0
I found issue with Actual Value.Base Inj 8-bit LOAD=0x3e;((n*50)/2);#.## msec
The result is greater than 9.99.
Actual Value.Base Inj 8-bit LOADa=0x3e;((n*25)/8);#.## msec
This gives 1.09msec at IDLE. Of course equation is a guess.
O2 sensor, with box checked, varies between 17 & 157. This is probably working correctly since the sensor is supposed to continually hunt around middle value, 93.
TEST OUTPUTS:
This cycles through TEST # 17,16,35,34,5,23,4,33,1 Then reports TEST Complete.
I can hear clicks for all except Test #4.
Based on Dougs description: 17,16,35,34,5,23 are the fuel injectors.
4 is the evap valve and I don't hear anything.
33, 1. Idle control vale and resonance flap. One of these is louder than the rest.
I gather the DME doesn't tell the Scantool any results, the user must verify good/bad result.
Looks like TEST OUTPUTS is working, for the circuits being tested.
This Scantool is really coming along great!
Ray
The result is greater than 9.99.
Actual Value.Base Inj 8-bit LOADa=0x3e;((n*25)/8);#.## msec
This gives 1.09msec at IDLE. Of course equation is a guess.
O2 sensor, with box checked, varies between 17 & 157. This is probably working correctly since the sensor is supposed to continually hunt around middle value, 93.
TEST OUTPUTS:
This cycles through TEST # 17,16,35,34,5,23,4,33,1 Then reports TEST Complete.
I can hear clicks for all except Test #4.
Based on Dougs description: 17,16,35,34,5,23 are the fuel injectors.
4 is the evap valve and I don't hear anything.
33, 1. Idle control vale and resonance flap. One of these is louder than the rest.
I gather the DME doesn't tell the Scantool any results, the user must verify good/bad result.
Looks like TEST OUTPUTS is working, for the circuits being tested.
This Scantool is really coming along great!
Ray
07-19-2006 | 07:38 PM
#37
Thread Starter
Instructor
Joined: Dec 2005
Posts: 132
Likes: 0
I rechecked TEST OUTPUTS.
TEST #4 has a hum or buzz sound that changes pitch. The other test have a more pronounced click. Resonance flap is pretty loud.
I believe test #4 is IACV. Feeling the engine parts the IDLE SPEED POSISTIONER feels like it is buzzing. I read the Diagnostics in shop manual. The signal alternates on/off and that will give a buzz/hum. I'm guessing this is working.
Ray
TEST #4 has a hum or buzz sound that changes pitch. The other test have a more pronounced click. Resonance flap is pretty loud.
I believe test #4 is IACV. Feeling the engine parts the IDLE SPEED POSISTIONER feels like it is buzzing. I read the Diagnostics in shop manual. The signal alternates on/off and that will give a buzz/hum. I'm guessing this is working.
Ray
Last edited by raycm; 07-20-2006 at 01:44 AM. Reason: UPDATE IACV
07-22-2006 | 07:56 AM
#38
Intermediate
Joined: Jun 2004
Posts: 43
Likes: 1
From: Germany
Hi Ray. Read your posts and built an interface based on your drawing. 
I saw you have done some adaption work on the configuration file for the 993.
It would be great if you share your work and post the actual "scantool.cfg"
and "Trouble Codes.txt" files. Many thanks goes also to Doug for his great Software.
So I read all reachable control units on board of my 95 cab.
Climate control has trouble code 45 and I find out, that the
fan on the controllers backside is faulty.
But for one error from the Motronic I have no idea
what is defect: Trouble code 35.
The error occures some time after ignition is on but engine was
not started. Any ideas?
PDriver
I saw you have done some adaption work on the configuration file for the 993.
It would be great if you share your work and post the actual "scantool.cfg"
and "Trouble Codes.txt" files. Many thanks goes also to Doug for his great Software.
So I read all reachable control units on board of my 95 cab.
Climate control has trouble code 45 and I find out, that the
fan on the controllers backside is faulty.
But for one error from the Motronic I have no idea
what is defect: Trouble code 35.
The error occures some time after ignition is on but engine was
not started. Any ideas?
PDriver
Last edited by PDriver; 07-22-2006 at 08:15 AM.
07-22-2006 | 05:00 PM
#39
Thread Starter
Instructor
Joined: Dec 2005
Posts: 132
Likes: 0
"I saw you have done some adaption work on the configuration file for the 993.
It would be great if you share your work and post the actual "scantool.cfg"
and "Trouble Codes.txt" files."
Hi PDriver,
Those files aren't ready for prime time, but I'll attach my most recent in this message.
Since I posted the original for 993, based on the 964, there have been only two
people who've come to work on completing this for 993. And they are both 964 drivers!
One is Doug the kind person who has spent his time to write the code and then share it.
Did you have any problems making the stuff work? Some have apparently had issues with the
immobilizer but no one has told us what fixed it to allow DME to reply to scantool.
The DME returns a number based on it's rev level. Mxx. Hx for Climate Control.
The 964 is generally M00. Doug is looking at displaying that number so the user will
know what fault code list he needs. And what 'list number' scantool is looking for.
"Climate control has trouble code 45 and I find out, that the
fan on the controllers backside is faulty."
I see 45 in H06 trouble list. 45=Inside sensor blower motor
"But for one error from the Motronic I have no idea
what is defect: Trouble code 35."
I have Shop Manual for M04. No 35 fault code in it.
"The error occures some time after ignition is on but engine was
not started. Any ideas?"
Perhaps M06 has a 35. Find a later version of manual. Put message question here.
Or read carefully through the diagnosis and see what is being done prior to start.
Also, perhaps the values you get while running will also show a problem. I've put
some expected values in the new file. My guess and therefore only guidlines.
I've had error code 60. It wasn't real. Caused by me turning off engine while leaving
scantool software running.
The scantool.cfg works. I've constructed the trouble code list but haven't tried it out.
Please report results, good or bad so I may know if it works correctly.
Replace your Trouble Codes.txt with the attached.
Replace your scantool.cfg with the attached. Fix the file name.
Find ScanTool.INI maybe c\windows\ and delete. Scantool will make a new file
based on the new scantool.cfg
Ray
It would be great if you share your work and post the actual "scantool.cfg"
and "Trouble Codes.txt" files."
Hi PDriver,
Those files aren't ready for prime time, but I'll attach my most recent in this message.
Since I posted the original for 993, based on the 964, there have been only two
people who've come to work on completing this for 993. And they are both 964 drivers!
One is Doug the kind person who has spent his time to write the code and then share it.
Did you have any problems making the stuff work? Some have apparently had issues with the
immobilizer but no one has told us what fixed it to allow DME to reply to scantool.
The DME returns a number based on it's rev level. Mxx. Hx for Climate Control.
The 964 is generally M00. Doug is looking at displaying that number so the user will
know what fault code list he needs. And what 'list number' scantool is looking for.
"Climate control has trouble code 45 and I find out, that the
fan on the controllers backside is faulty."
I see 45 in H06 trouble list. 45=Inside sensor blower motor
"But for one error from the Motronic I have no idea
what is defect: Trouble code 35."
I have Shop Manual for M04. No 35 fault code in it.
"The error occures some time after ignition is on but engine was
not started. Any ideas?"
Perhaps M06 has a 35. Find a later version of manual. Put message question here.
Or read carefully through the diagnosis and see what is being done prior to start.
Also, perhaps the values you get while running will also show a problem. I've put
some expected values in the new file. My guess and therefore only guidlines.
I've had error code 60. It wasn't real. Caused by me turning off engine while leaving
scantool software running.
The scantool.cfg works. I've constructed the trouble code list but haven't tried it out.
Please report results, good or bad so I may know if it works correctly.
Replace your Trouble Codes.txt with the attached.
Replace your scantool.cfg with the attached. Fix the file name.
Find ScanTool.INI maybe c\windows\ and delete. Scantool will make a new file
based on the new scantool.cfg
Ray
Last edited by raycm; 08-21-2006 at 08:58 PM. Reason: Reduce attachment files
07-23-2006 | 01:05 PM
#40
Addict
Rennlist Member
Rennlist Member
Joined: Nov 2001
Posts: 554
Likes: 3
From: Herefordshire
[QUOTE=raycm
Since I posted the original for 993, based on the 964, there have been only two people who've come to work on completing this for 993. And they are both 964 drivers!
One is Doug the kind person who has spent his time to write the code and then share it.
Ray[/QUOTE]
Don't know if I'm alone, but I'm madly saving all this stuff ... given a fraction of spare time, I'll try to catch up !
Anyway, just a note to say that this work is greatly appreciated !
Thanks, guys
cheers, Maurice
Since I posted the original for 993, based on the 964, there have been only two people who've come to work on completing this for 993. And they are both 964 drivers!
One is Doug the kind person who has spent his time to write the code and then share it.
Ray[/QUOTE]
Don't know if I'm alone, but I'm madly saving all this stuff ... given a fraction of spare time, I'll try to catch up !
Anyway, just a note to say that this work is greatly appreciated !
Thanks, guys
cheers, Maurice
07-23-2006 | 08:48 PM
#41
Addict
Rennlist Member
Rennlist Member
Joined: May 2001
Posts: 828
Likes: 22
From: Williamsport, MD
I'm also still working on this for my 95. I've built a board per Ray's scematics and I "THINK" I have it all right. Unfortunately I can't get the blasted thing to connect. I know my Com1 is alive but I'm still doing some idiot-proofing of my electrical work. I keep going from really confused to completely "GOT IT" ... but then quickly fall back to really confused. Hopefully soon I'll either have some results to post or else a smashed up little pile of resistors, transistors and diodes of which I will certainly share pictures.
Thanks Doug and Ray and others for laying the groundwork. This has serious cool factor written all over it.
Thanks Doug and Ray and others for laying the groundwork. This has serious cool factor written all over it.
07-24-2006 | 06:29 AM
#42
Intermediate
Joined: Jun 2004
Posts: 43
Likes: 1
From: Germany
Hi Ray, thanks for your post and your files. I will do some work with the tool and if I have changes or new information I will post it here.
One question: is there also a section in the scantool.cfg to name the target for the output test? Doing output tests without knowledge what the control numbers means is like to fish in troubled water...
I posted in the "1995 OBD1 Diag tool" thread a workaround which solved the DME connection problem on my car. After examine the electrical diagrams and doing some measurement to the wiring harness installed in my car I found the problem why scantool does not connect to the DME. In cars with installed immobilizer unit (M530) the K-Line from the DME is NOT directly attached to the OBD connector pin 7. The K-Line from the DME is routed first to the immobilizer W-Pin. The signal is internally switched by a internal signal relais to the K-Line output of the immobilizer. This pin goes then through the Pin 7 of OBD connector. I measured the relais but I didn't find the source of failure which causes the relais not to switch. The relais coil have on both ends 12V power so it won't switch.
My workaround is to shorten the incoming W-Line with the K-Line of the immobilizer unit. The switch is mounted under the seat attached to the control units cover. If I want to scan the DME I have to push the switch on and scantool connects to the DME. In normal mode, when no scantool is attached to the car the switch is off.
There could be two possibilities why the immobilizer doesn't switch the K-line:
- defect immobilizer, may be a transistor, or
- special command to the immobilizer to free/switch the K-line. (this is my preferred)
The W-Line and K-Line inputs of the immobilizer are both connected to the relais. But the K-Line side is also internally routed to some electronics of the immobilizer. So I think the immobilizer has to be setup by the scantool via K-Line on OBD Pin 7 and then switching on the DME via the relais. But this is only my opinion.
Next point is, my DME has the spare part number 993 618 124 04.
I didn't find this number in porsches spare parts catalog or in Adrian's 993 book. This can be also be the source of the connection problem....
Any ideas???
Greetings,
PDriver
One question: is there also a section in the scantool.cfg to name the target for the output test? Doing output tests without knowledge what the control numbers means is like to fish in troubled water...
I posted in the "1995 OBD1 Diag tool" thread a workaround which solved the DME connection problem on my car. After examine the electrical diagrams and doing some measurement to the wiring harness installed in my car I found the problem why scantool does not connect to the DME. In cars with installed immobilizer unit (M530) the K-Line from the DME is NOT directly attached to the OBD connector pin 7. The K-Line from the DME is routed first to the immobilizer W-Pin. The signal is internally switched by a internal signal relais to the K-Line output of the immobilizer. This pin goes then through the Pin 7 of OBD connector. I measured the relais but I didn't find the source of failure which causes the relais not to switch. The relais coil have on both ends 12V power so it won't switch.
My workaround is to shorten the incoming W-Line with the K-Line of the immobilizer unit. The switch is mounted under the seat attached to the control units cover. If I want to scan the DME I have to push the switch on and scantool connects to the DME. In normal mode, when no scantool is attached to the car the switch is off.
There could be two possibilities why the immobilizer doesn't switch the K-line:
- defect immobilizer, may be a transistor, or
- special command to the immobilizer to free/switch the K-line. (this is my preferred)
The W-Line and K-Line inputs of the immobilizer are both connected to the relais. But the K-Line side is also internally routed to some electronics of the immobilizer. So I think the immobilizer has to be setup by the scantool via K-Line on OBD Pin 7 and then switching on the DME via the relais. But this is only my opinion.
Next point is, my DME has the spare part number 993 618 124 04.
I didn't find this number in porsches spare parts catalog or in Adrian's 993 book. This can be also be the source of the connection problem....
Any ideas???
Greetings,
PDriver
Last edited by PDriver; 07-26-2006 at 10:44 AM. Reason: corrected wrong pin number
07-24-2006 | 12:17 PM
#44
Race Car
Joined: May 2003
Posts: 4,045
Likes: 61
From: SoCal
"FYI, I recently had a shop attach a KT300 to my 94 993, and there was no DME information until I disarmed the immobiliser"
Correct! The immobilizer MUST send the "disarmed" command to the DME to allow
both communications AND the running mode.
Correct! The immobilizer MUST send the "disarmed" command to the DME to allow
both communications AND the running mode.
07-24-2006 | 05:46 PM
#45
Intermediate
Joined: Jun 2004
Posts: 43
Likes: 1
From: Germany
Ok. Thats the right way. But I pressed the key fob button to disarm the immobilzer and started the engine. No connection to the OBD-Port was done. This evening I had the chance to test Ray's interface and Doug's software on a '96 993 cab and there exists the same problem: no connection to the DME.
I will do some more tests next days. Thanks for your information.
PDriver
I will do some more tests next days. Thanks for your information.
PDriver