SCANTOOL SW OBD II ISSUE
#1
Racer
Thread Starter
Join Date: Apr 2010
Location: italy
Posts: 487
Likes: 0
Received 0 Likes
on
0 Posts
SCANTOOL SW OBD II ISSUE
Hi guys,
I thought ti open a new trd for my problem
I'm trying to fix sw compatibility....
I bought the T-OBD II from Tore,
the hw works fine,but I cannot get in communication with the DME and SRS Airbag part
,the others work fine.
Tore and I have been mailing a lot,and the final thought is a sw issue.
I have to say my '97 C4S euro specs has from factory the X51 option(3800 cc engine with some parts of the RS including the DME ECU I suppose by the increase of the rev limiter and other few things)
So,Doug or whoever developed the sw(such a great man),could help my solving this problem?
I can give the part numbers if needed...
Really would help!
cheers
I thought ti open a new trd for my problem
I'm trying to fix sw compatibility....
I bought the T-OBD II from Tore,
the hw works fine,but I cannot get in communication with the DME and SRS Airbag part
,the others work fine.
Tore and I have been mailing a lot,and the final thought is a sw issue.
I have to say my '97 C4S euro specs has from factory the X51 option(3800 cc engine with some parts of the RS including the DME ECU I suppose by the increase of the rev limiter and other few things)
So,Doug or whoever developed the sw(such a great man),could help my solving this problem?
I can give the part numbers if needed...
Really would help!
cheers
#2
Rennlist Member
I've tried to contact Doug years ago regarding adding features to his scantool sw, but it's like he vanished from the planet.....
The scantool sw uses the scantool.cfg (renamed scantool.txt) file for ecu addresses and baud rate for handshaking - notice for the motronic it's address = 16, baudrate = 9600. The address is sent at 5 baud until the ecu responds at which time the coms speed switches to the baudrate. That's the info on the sw. Make sure your config file is for the 993 - baudrate = 9600 for the993, 8800 for the 964.
Have you ascertained the the K and L lines to the motronic have continuity to the diagnostic port? K and L wires should be common "buss" to all control units - each unit responding to the correct address sent from the diagnostic port. As you know the 993 has it's DME wakeup "K" line from the OBD15 connection - is this the case on your car?
Can you actually connect to the motronic using a porsche diagnostic tool (hammer, etc.)? Is it possible that your motronic ecu is actually OBD2 - '97 is pretty late in the scheme of things and at some point all cars were OBD2. The scantool software is OBD1 even though the plug is shaped as OBD2. Could it be that your motoronic module is OBD2 while the rest of the ecus are OBD1? Try connecting a common OBD2 scanner to the car and see if it responds...
I'm not sure when porsches changed from proprietary OBD1 to the OBD2 standard, maybe someone can chime in.
The scantool sw uses the scantool.cfg (renamed scantool.txt) file for ecu addresses and baud rate for handshaking - notice for the motronic it's address = 16, baudrate = 9600. The address is sent at 5 baud until the ecu responds at which time the coms speed switches to the baudrate. That's the info on the sw. Make sure your config file is for the 993 - baudrate = 9600 for the993, 8800 for the 964.
Have you ascertained the the K and L lines to the motronic have continuity to the diagnostic port? K and L wires should be common "buss" to all control units - each unit responding to the correct address sent from the diagnostic port. As you know the 993 has it's DME wakeup "K" line from the OBD15 connection - is this the case on your car?
Can you actually connect to the motronic using a porsche diagnostic tool (hammer, etc.)? Is it possible that your motronic ecu is actually OBD2 - '97 is pretty late in the scheme of things and at some point all cars were OBD2. The scantool software is OBD1 even though the plug is shaped as OBD2. Could it be that your motoronic module is OBD2 while the rest of the ecus are OBD1? Try connecting a common OBD2 scanner to the car and see if it responds...
I'm not sure when porsches changed from proprietary OBD1 to the OBD2 standard, maybe someone can chime in.
#3
Racer
Thread Starter
Join Date: Apr 2010
Location: italy
Posts: 487
Likes: 0
Received 0 Likes
on
0 Posts
thanks Mojorizing,
mine is a '97 full OBD II car,hammer in PC works perfectly...just got it serviced!
How do I ck if K and L have continuity?
I'll ck baudrate and address.
Cheers
mine is a '97 full OBD II car,hammer in PC works perfectly...just got it serviced!
How do I ck if K and L have continuity?
I'll ck baudrate and address.
Cheers
#4
Racer
Thread Starter
Join Date: Apr 2010
Location: italy
Posts: 487
Likes: 0
Received 0 Likes
on
0 Posts
Here are the settings...look fine to me
[Motronic]
address=16
baudRate=9600
Input.1=Throttle Ang:;(n-0x1a)*42;##.##°
Input.2=Battery:;(n*682)/100;##.## V
Input.4=en-sen220-10:
Input.5=MAF Sensor:;((n*500)/255);#.## V
Input.7=tipIgTmChg:;n*1;##.#°
Input.8=O2sen 5-170:
Switch.1=NO:
Switch.2=NO:
Actual Value.Battery +9V to +14V=0x36;(n*682)/100;##.## Volts
Actual Value.IATS Int Air Tmp 0-80(°C)=0x37;((((n*115)/100)-26)-32)*5/9;###°
Actual Value.ECTS Cyl Hd Tmp 0-180(°C)=0x38;((((n*115)/100)-26)-32)*5/9;###°
Actual Value.Eng Speed 800@idle=0x39;n*40;#### rpm
Actual Value.?Ign Adv Tme 3°@Idle=0x3a;(n*1)/2;###.#°
Actual Value.H02S 150-900mV=0x3d;n*3;#### mV
Actual Value.MAF 1V@IDLE, Cold=0x47;((n*500)/255);#.## Volts
Actual Value.Base Inj time=0x3f;;##.### ms;UINT16
Actual Value.Base Inj 8-bit LOAD=0x3e;n*50;#.### ms
[ABS/Traction Control]
baudRate=9600
address=31
Actual Value.Stop Light SW=0x02
Actual Value.Valve Relay=0x04
Actual Value.Return Pump=0x06
Actual Value.Speed Vehicle=0x08
Actual Value.Front Left=0x10
Actual Value.Front Right=0x1b
Actual Value.Rear Left=0x1d
Actual Value.Rear Right=0x1f
[SRS Air Bag]
address=87
baudRate=9600
[Climate Control]
address=81
baudRate=4800
Input.1=Foot ****:
Input.2=DefroKnob:
Input.3=Blow ****:
Input.4=Temp ****:
Input.6=AirCircSw:
Input.7=DefrostSw:
Input.8=AC Sw:
Switch.1=AC:
Switch.2=ACM:
Actual Value.Voltage Term X (V)=0x02
Actual Value.Inside Temperature (°F)=0x04
Actual Value.Rear Blower Temperature (°F)=0x06
Actual Value.Lt mixing Temperature (°F)=0x08
Actual Value.Rt mixing Temperature (°F)=0x10
Actual Value.Front Oil Cooler Temp (°F)=0x1b
Actual Value.Evaporator Temperature (°F)=0x1d
[Alarm]
address=64
baudRate=9600
Input.1=Door sw:
Input.2=EngineHood:
Input.3=LuggageComp:
Input.4=PositionSw:
Input.6=CentralLock:
Input.7=GloveComp:
Input.8=Radio:
Switch.1=Act:
Switch.2=DeA:
[TIP]
address=41
baudRate=4800
[Motronic]
address=16
baudRate=9600
Input.1=Throttle Ang:;(n-0x1a)*42;##.##°
Input.2=Battery:;(n*682)/100;##.## V
Input.4=en-sen220-10:
Input.5=MAF Sensor:;((n*500)/255);#.## V
Input.7=tipIgTmChg:;n*1;##.#°
Input.8=O2sen 5-170:
Switch.1=NO:
Switch.2=NO:
Actual Value.Battery +9V to +14V=0x36;(n*682)/100;##.## Volts
Actual Value.IATS Int Air Tmp 0-80(°C)=0x37;((((n*115)/100)-26)-32)*5/9;###°
Actual Value.ECTS Cyl Hd Tmp 0-180(°C)=0x38;((((n*115)/100)-26)-32)*5/9;###°
Actual Value.Eng Speed 800@idle=0x39;n*40;#### rpm
Actual Value.?Ign Adv Tme 3°@Idle=0x3a;(n*1)/2;###.#°
Actual Value.H02S 150-900mV=0x3d;n*3;#### mV
Actual Value.MAF 1V@IDLE, Cold=0x47;((n*500)/255);#.## Volts
Actual Value.Base Inj time=0x3f;;##.### ms;UINT16
Actual Value.Base Inj 8-bit LOAD=0x3e;n*50;#.### ms
[ABS/Traction Control]
baudRate=9600
address=31
Actual Value.Stop Light SW=0x02
Actual Value.Valve Relay=0x04
Actual Value.Return Pump=0x06
Actual Value.Speed Vehicle=0x08
Actual Value.Front Left=0x10
Actual Value.Front Right=0x1b
Actual Value.Rear Left=0x1d
Actual Value.Rear Right=0x1f
[SRS Air Bag]
address=87
baudRate=9600
[Climate Control]
address=81
baudRate=4800
Input.1=Foot ****:
Input.2=DefroKnob:
Input.3=Blow ****:
Input.4=Temp ****:
Input.6=AirCircSw:
Input.7=DefrostSw:
Input.8=AC Sw:
Switch.1=AC:
Switch.2=ACM:
Actual Value.Voltage Term X (V)=0x02
Actual Value.Inside Temperature (°F)=0x04
Actual Value.Rear Blower Temperature (°F)=0x06
Actual Value.Lt mixing Temperature (°F)=0x08
Actual Value.Rt mixing Temperature (°F)=0x10
Actual Value.Front Oil Cooler Temp (°F)=0x1b
Actual Value.Evaporator Temperature (°F)=0x1d
[Alarm]
address=64
baudRate=9600
Input.1=Door sw:
Input.2=EngineHood:
Input.3=LuggageComp:
Input.4=PositionSw:
Input.6=CentralLock:
Input.7=GloveComp:
Input.8=Radio:
Switch.1=Act:
Switch.2=DeA:
[TIP]
address=41
baudRate=4800
#5
Rennlist Member
Settings look good.
What do you mean by "hammer in PC works perfectly...just got it serviced!" You took the car to a shop where they used a diagnostic tool to successfully connect to the motronic?
Continuity will between the OBD2 port to the dme connector at the motronic ecu using a VOM and long leads. I don't have the pinout for your car.
What is the part number for your motronic ecu?
What do you mean by "hammer in PC works perfectly...just got it serviced!" You took the car to a shop where they used a diagnostic tool to successfully connect to the motronic?
Continuity will between the OBD2 port to the dme connector at the motronic ecu using a VOM and long leads. I don't have the pinout for your car.
What is the part number for your motronic ecu?
#6
Racer
Thread Starter
Join Date: Apr 2010
Location: italy
Posts: 487
Likes: 0
Received 0 Likes
on
0 Posts
yes
PC = Porsche Center
hammer=hw used by PC
works=they tested and bleeded the brake lines and checked all the car(should have)
what's a VOM?I should have the schematic(does Strather have it?)
Thank again
I'll check the part number...(is the dme ecu under the driver seat?)and let you know
PC = Porsche Center
hammer=hw used by PC
works=they tested and bleeded the brake lines and checked all the car(should have)
what's a VOM?I should have the schematic(does Strather have it?)
Thank again
I'll check the part number...(is the dme ecu under the driver seat?)and let you know
#7
Rennlist Member
VOM = Volt/ohm meter
If the PC was able to connect to our ecu , there's no need to check continuity - it's there!
What is missing is the address/baudrate used to access your ecu.
If the PC was able to connect to our ecu , there's no need to check continuity - it's there!
What is missing is the address/baudrate used to access your ecu.
Trending Topics
#8
Racer
Thread Starter
Join Date: Apr 2010
Location: italy
Posts: 487
Likes: 0
Received 0 Likes
on
0 Posts
Where should I get/insert the address/baudrate?
Streather states that RS engines run on Bosch M 2.10.1 part number 993.618.123.85
instead of M 2.10 as 3600 cc engines.
could this be the prob?
the dme ecu is under the driver seat and is sealed by a metallic plate...
before to break the seal,I'd like to ask you if there's another way to check it...
Streather states that RS engines run on Bosch M 2.10.1 part number 993.618.123.85
instead of M 2.10 as 3600 cc engines.
could this be the prob?
the dme ecu is under the driver seat and is sealed by a metallic plate...
before to break the seal,I'd like to ask you if there's another way to check it...
#9
Rennlist Member
Don't break the seal.
While in the shop, the hammer should have reported the part number after making connection. Did they record that?
Because you were able to connect to your ecu while in the shop, there's nothing wrong with the wiring, ecu. What did they use in the shop as an diagnostic tool....porsche bosche 9288 (hammer) , etc? You'll need to sniff the communications between the car and the tool being used - which is unlikely they'll let you do that. I have a device that I use to monitor the coms. between my car and my hammer to find the protocol being used.
Ultimately, I think you're going to find the address and baudrate through trial and error using the scantool sw and Tore's hw. You can edit the scantool.cfg file and through an iteration process, I think you should be able to link up to the ecu. Give me a few days to suggest changes to the config file.
While in the shop, the hammer should have reported the part number after making connection. Did they record that?
Because you were able to connect to your ecu while in the shop, there's nothing wrong with the wiring, ecu. What did they use in the shop as an diagnostic tool....porsche bosche 9288 (hammer) , etc? You'll need to sniff the communications between the car and the tool being used - which is unlikely they'll let you do that. I have a device that I use to monitor the coms. between my car and my hammer to find the protocol being used.
Ultimately, I think you're going to find the address and baudrate through trial and error using the scantool sw and Tore's hw. You can edit the scantool.cfg file and through an iteration process, I think you should be able to link up to the ecu. Give me a few days to suggest changes to the config file.
#11
Rennlist Member
There's seems to be no rhyme or reason to the addresses of the various control units , so I think it's best to start at one working up. FYI, for the 964 and some 993 control units:
DME
address = 16
baud = 8800
PDAS
address = 61
baud = 4800
CCU
address = 81
baud = 4800
Airbag
address = 87
baud = 9600
TIP
address = 41
baud = 4800
Alarm
address = 64
baud = 9600
So, move the scantool.cfg file out of your scantool folder and then rename (scantool.txt to scantool.cfg) and insert the attached file into the scantool folder. Have Tore's hw setup for DME, start scantool.exe. You see the drop down menu with trial 1 - trial 5. Try each selection to connect to the dme. After trying all trials, edit the scantool.cfg file and increase the addresses by 5, resave as scantool.cfg and do it all over again. ...if and when you connect, scantool will report your model # of the dme. Note the address and edit the original scantool.cfg file. This procedure assumes your DME has baudrate = 9600 which I think is a good assumption.
Let me know if you have any questions....
Kevin
DME
address = 16
baud = 8800
PDAS
address = 61
baud = 4800
CCU
address = 81
baud = 4800
Airbag
address = 87
baud = 9600
TIP
address = 41
baud = 4800
Alarm
address = 64
baud = 9600
So, move the scantool.cfg file out of your scantool folder and then rename (scantool.txt to scantool.cfg) and insert the attached file into the scantool folder. Have Tore's hw setup for DME, start scantool.exe. You see the drop down menu with trial 1 - trial 5. Try each selection to connect to the dme. After trying all trials, edit the scantool.cfg file and increase the addresses by 5, resave as scantool.cfg and do it all over again. ...if and when you connect, scantool will report your model # of the dme. Note the address and edit the original scantool.cfg file. This procedure assumes your DME has baudrate = 9600 which I think is a good assumption.
Let me know if you have any questions....
Kevin
Last edited by mojorizing; 11-10-2011 at 06:07 PM.
#12
Rennlist Member
This is interesting!
Thanks for the test file mojorizing, I haven't thought of doing this for testing purposes.
Cheers,
Tore
Thanks for the test file mojorizing, I haven't thought of doing this for testing purposes.
Cheers,
Tore
#13
I have a similar problem connecting scantool to my 993 C4 cab MY95 via OBDII.
Scantool can connect to the all the modules (ABS/SRS/CCU/ALARM) except for the Motronic.
This seems a known malfunction with 993 equipped with alarm & remote.
A workaround: https://rennlist.com/forums/993-foru...r-here-17.html
See posts #247 & #269.
But installing the proposed switch on my immobilizer unit scares me too much.
01COCCOBET had a long test on his car yesterday: no way to get scantool connected to Motronic and Airbag SRS.
Scantool can connect to the all the modules (ABS/SRS/CCU/ALARM) except for the Motronic.
This seems a known malfunction with 993 equipped with alarm & remote.
A workaround: https://rennlist.com/forums/993-foru...r-here-17.html
See posts #247 & #269.
But installing the proposed switch on my immobilizer unit scares me too much.
01COCCOBET had a long test on his car yesterday: no way to get scantool connected to Motronic and Airbag SRS.
#14
Rennlist Member
What about the tip in post #4 in this thread:
https://rennlist.com/forums/993-foru...orkaround.html
I've never tried my T-OBD in a car with immobilizer myself, so I can't verify this.
Cheers,
Tore
https://rennlist.com/forums/993-foru...orkaround.html
I've never tried my T-OBD in a car with immobilizer myself, so I can't verify this.
Cheers,
Tore
#15
Burning Brakes
The workaround from post #4 in the thread Tore quoted did not work for me.
Something interesting happens, though. When I try to access the DME, the engine compartment fan turns on high.
I am planning to do the jumper on the immobilizer in the future.
Something interesting happens, though. When I try to access the DME, the engine compartment fan turns on high.
I am planning to do the jumper on the immobilizer in the future.