Clear SRS errors without MUT

[Leggie]

Shouldn't matter, but I'll re-write the openport part soon so select the right library, then the x86/x64 part wont matter.

I installed the x86 versions and it was fine for me (Windows 11; 64 bit). Just for some info on that side.

 

[ano1]

Hi All,

I've created a Windows app to read DTCs and clear DTCs for SRS. This negates the need for a MUT to clear errors.
At the moment, it only works with an Openport 2.0 but looking to get FTDI/VAGCOM cables working.

Also, it can clear DTCs but I haven't deciphered the DTCs from the data the SRS computer sends... so that is a work in progress.

Is there anyone who'd be willing to give it a shot?

Cheers,
Bill

Hi,
now I found your post. I have some Mitsubishi cars (VR4 with Group N Ralliart Engine 1989/90, Galant EA2A 1997, Colt CJ1A, Colt CJ4A 1997, Space Wagon N33W 1998, Lancer X 1.8l 2008) and Openport 1.3 and original Tactrix Openport 2.0.
So now I got SRS Lamp on Galant EA2A think about Water entering the SRS ECU, because AC drain was plugged and water came into interior...
I would like to test for reading SRS DTC and delete if possible. According to my schematics SRS Diag Line is on Pin 12 of OBD connector. Will your tool take care about this when using Openport 2.0 or should a special adapter be made ?
regards
ano1

 

[abrunstr]

Hi,
Finally tested with Openport 2.0, used .net 5.0 x86 to run
[10.49.35.720] SRS Selected
[10.49.35.721] J2534 mode...
[10.49.35.723] Connecting...
[10.49.35.744] Determining Number of Devices
[10.49.36.091] Loading Driver DLL
[10.49.36.132] Loading Driver DLL
[10.49.36.134] Putting ECU to Diagnostic Mode
[10.49.36.140] Connecting to ECU
[10.49.36.144] Apply J2534 Filter
[10.49.36.152] Setting Comms Options
[10.49.38.764] Failed to connect

 

[kc427]

OK, finally have some time to connect the spare SRS unit, and can test the program at home.

Yes, same as other people, I got the same error log as below using Openport2.0 Rev.E :

[15:30:53.519] SRS Selected
[15:30:53.530] J2534 mode...
[15:30:53.531] Connecting...
[15:30:53.543] Determining Number of Devices
[15:30:54.047] Loading Driver DLL
[15:30:54.058] Loading Driver DLL
[15:30:54.060] Putting ECU to Diagnostic Mode
[15:30:54.065] Connecting to ECU
[15:30:54.068] Apply J2534 Filter
[15:30:54.074] Setting Comms Options
[15:30:56.681] Failed to connect

Please note that, this SRS is bought from ebay UK, and SRS light is still always ON, when powered ON the IG1 switch. I expected it could only ON for few second and then OFF, but it is not.

 

[BCX]

Looks like you have only pin 12 connected.

You'll need to connect pin 7 (kline) as well as that's how it communicates.

Ill try and get to my srs ecu and see where pin 7 goes.

When I get home, will put up a new version with even more debugging.

 

[kc427]

Looks like you have only pin 12 connected.

You'll need to connect pin 7 (kline) as well as that's how it communicates.

Ill try and get to my srs ecu and see where pin 7 goes.

When I get home, will put up a new version with even more debugging.

Yes please find the pin 7(K LIne) connection. As I also checked UK Galant workshop manual, and there is no information about the K Line pin communication on SRS. FYI, the yellow plug comes with this used SRS and the wires are exactly same as the UK Galant workshop manual, and no extra wire on the plug, therefore:

Pin 5 - Driver's Side Airbag
PIn 6 - Driver's Side Airbag
PIn 7 - Passenger's Side Airbag
Pin 8 - Passenger's Side Airbag
PIn 11 - OBD2 plug pin 12
PIn 13 - IG1 Ignition Switch
Pin 14 - IG1 Ignition Switch
PIn 15 - SRS dashboard light
PIn 20 - GND
Pin 21 - GND

 

[BCX]

It definately uses kline as this is the pin ive been sniffing out using oscilloscope and logic analyser on the obd connector.

i just dont know what pin it goes to on the srs side, but it's not documented/error in the diagrams.
There's a few things like that, other example - im pretty sure the reflash connector doesn't show up nor what pin it goes into on ecu.

 

[BCX]

New version with extra debugging.

 

[kc427]

It definately uses kline as this is the pin ive been sniffing out using oscilloscope and logic analyser on the obd connector.

i just dont know what pin it goes to on the srs side, but it's not documented/error in the diagrams.
There's a few things like that, other example - im pretty sure the reflash connector doesn't show up nor what pin it goes into on ecu.

The reflash connector is C13 pin 26, which connects to the pin 79 on ECU.

BTW, from the second photo attached, the K Line OBD pin7 is connected to both ECU and ABS together, but not others.

 

[kc427]

New version with extra debugging:

Dropbox - File Deleted - Simplify your life

www.dropbox.com

Still fail on my side. Please note that I selected Openport, but the log was still saying FTDI.


[10:10:13.102] SRS Selected
[10:10:13.104] J2534 mode...
[10:10:13.106] Connecting...
[10:10:13.108] Determining Number of Devices
[10:10:13.583] Loading Driver DLL
[10:10:13.604] Loading Driver DLL
[10:10:13.607] Putting ECU to Diagnostic Mode
[10:10:13.612] Connecting to ECU
[10:10:13.614] Apply J2534 Filter
[10:10:13.621] Setting Comms Options
[10:10:16.228] FTDI Connect Failed!
[10:10:16.231] Failed to connect

 

[BCX]

The reflash connector is C13 pin 26, which connects to the pin 79 on ECU.

Must be thinking magna wiring diagrams dont show it even though Magnas have reflash connector.

 

[BCX]

Still fail on my side. Please note that I selected Openport, but the log was still saying FTDI.

Doh, typo... Will fix shortly

You trying this on your car, or bench?

 

[kc427]

Must be thinking magna wiring diagrams dont show it even though Magnas have reflash connector.

no wonder

BTW, just another test I did, connected SRS with OP2(connected to USB already), and then I taped both OBD pin 12(SRS) and pin 7(ECU) with my low end scope. The pin7(ECU) has already have 12V high, but pin12(SRS) is still 0v low, you can see the attached photo, pin12 is red and pin7 is yellow.

I used your VR4Info v0.3 and configured as ECU, and I can see the pin7 is 0v for awhile which is normal. However, I selected SRS on VR4Info, the pin12(SRS) is still 0v, nothing changed at all.

I also use the OP2 only, without SRS, just connect OP2 to USB, and used your software, and configured as SRS, and then "query", but the pin12(SRS) on OP2 signal is still 0v, nothing changed at all, so, maybe pin12 somehow not connected inside OP2, or, somehow the software library not calling a command to send command on pin12.

 

[kc427]

Doh, typo... Will fix shortly

You trying this on your car, or bench?

bench only. Because my car is parked and takes me 10min to get to there, so I test on the bench is easier, assume the SRS is connected correctly.

 

[abrunstr]

Hi, tested with version 0.4:
[22.06.56.589] SRS Selected
[22.06.56.590] J2534 mode...
[22.06.56.592] Connecting...
[22.06.56.593] Determining Number of Devices
[22.06.56.796] Loading Driver DLL
[22.06.56.818] Loading Driver DLL
[22.06.56.819] Putting ECU to Diagnostic Mode
[22.06.56.823] Connecting to ECU
[22.06.56.824] Apply J2534 Filter
[22.06.56.828] Setting Comms Options
[22.06.59.434] FTDI Connect Failed!
[22.06.59.436] Failed to connect

Tested with ECU and got this:
[22.08.53.819] ECU Selected
[22.08.53.821] J2534 mode...
[22.08.53.825] Connecting...
[22.08.53.827] Determining Number of Devices
[22.08.54.144] Loading Driver DLL
[22.08.54.174] Loading Driver DLL
[22.08.54.177] Putting ECU to Diagnostic Mode
[22.08.54.182] Connecting to ECU
[22.08.54.185] Apply J2534 Filter
[22.08.54.193] Setting Comms Options
[22.08.56.528] Five Baud Init
[22.08.56.574] Connected!
[22.08.56.578] Keyword: e7a4
[22.08.56.581] ***SCC***
[22.08.56.605] response: e7
[22.08.56.629] response: a4

Tested also AYC and ABS, both gives same log as SRS

 

[BCX]

New version:

Increased timeout times for J2534.

FTDI probably still doesnt work.

 

[abrunstr]

Tested 0.5 version:
[10.44.12.139] Version: 0.5
[10.44.12.141] SRS Selected
[10.44.12.142] J2534 mode...
[10.44.12.143] Connecting...
[10.44.12.145] Determining Number of Devices
[10.44.12.435] Loading Driver DLL
[10.44.12.457] Loading Driver DLL
[10.44.12.459] Putting ECU to Diagnostic Mode
[10.44.12.464] Connecting to ECU
[10.44.12.466] Apply J2534 Filter
[10.44.12.472] Setting Comms Options
[10.44.15.083]
[10.44.15.086] Failed to connect

 

[BCX]

Thanks for trying.

I'll release another version that logs the openport driver version and firmware version.

Im lost as to why it works on my vr4...

 

[BCX]

New verison:

https://foxbcx.net/files/VR4info v0.6.zip

Should have more luck now.
Got a clean version of windows and was getting the same problem.
Couple of the DLL files I was bundling weren't getting compiled/updated.

Of course works on my desktop and laptop as I run it within Visual Studio, so would always use latest versions of DLL.

Will check this in future, thanks to all that have tried so far!

 

[kc427]

New verison:

https://foxbcx.net/files/VR4info v0.6.zip

Should have more luck now.
Got a clean version of windows and was getting the same problem.
Couple of the DLL files I was bundling weren't getting compiled/updated.

Of course works on my desktop and laptop as I run it within Visual Studio, so would always use latest versions of DLL.

Will check this in future, thanks to all that have tried so far!

I have same problem(please note, it's on my test bench SRS):

[14:34:03.126] Version: 0.6
[14:34:03.198] SRS Selected
[14:34:03.200] J2534 mode...
[14:34:03.201] Connecting...
[14:34:03.237] Determining Number of Devices
[14:34:03.710] Loading Driver DLL
[14:34:03.728] Loading Driver DLL
[14:34:03.731] Putting ECU to Diagnostic Mode
[14:34:03.736] Connecting to ECU
[14:34:03.740] Apply J2534 Filter
[14:34:03.746] Setting Comms Options
[14:34:06.355]
[14:34:06.357] Failed to connect