J2534 connection issue #56
Comments
|
Does your interface/dll support ISO-9141/ISO-14230 ?
J2534-interfaces never support the SSM1 procotol, but the test result
should contain only a warning about that.
If the interface test dialog really shows an error, please
- compile the software as debug
- start the software from command line with "FreeSSM.exe > mylog.log"
- perform the interface test
- exit the software
- send me the log file
|
|
Thanks for the fast response! I couldn’t find much info about the cables capabilities, it’s a basic xhorse clone cable for Techstream. |
|
ABS will most likely not work, as it's usually SSM1 protocol at that time.
|
|
Is freessm able to read abs module through ssm1 ? I have a compiled version
+ Ftdi cable that reads my93 legacy ecu.
Le jeu. 22 déc. 2022 à 17:33, L1800Turbo ***@***.***> a
écrit :
ABS will most likely not work, as it's usually SSM1 protocol at that time.
—
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATTVWI3TBAKBWM5QFIMXMDWOR7GTANCNFSM6AAAAAATFA7Y4M>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Rafael FOURNERET
Directeur, ZmajaDev Beograd, Zmaja od Nocaja 13a, 11158 Belgrade, Serbia
Téléphone :
France : +33 1 84 25 10 07
Serbie : +381 6 03 56 92 26
Mail : ***@***.***
Skype : rafaelfourneret
|
|
Yes, that's possible.
If the RomID is unknown, it's possible to add it to the xml, but you can
try with connecting to get the RomID.
|
|
Which model year is it ?
IIRC later models use (standard) ISO-14230, which is currently not
supported.
Anyway, if you have a FTDI cable at hand you should try it.
|
|
Looks like you have installed 2 J2534 interface libraries:
Found 2 registered J2534-libraries:
Name: TIS Techstream VIM
Path: C:\Program Files\Toyota
Diagnostics\Techstream\Bin\ComTol32.dll
API-version: 04.04
Protocols: CAN ISO14230 ISO15765 ISO9141 J1850PWM J1850VPW
Name: XHorse - MVCI
Path: C:\Program Files\XHorse Electronics\MVCI Driver for
TOYOTA TIS\MVCI32.dll
API-version: 04.04
Protocols: CAN ISO14230 ISO15765 ISO9141 J1850PWM J1850VPW
Maybe you can try the "TIS Techstream VIM", too.
The J2534 spec leaves room for interpretation in several places and
libraries are often buggy...
The "XHorse - MVCI" interface library for example doesn't follow the
spec concerning the ExtraDataIndex of messages.
That's not a problem, communication looks good.
|
|
The car is not here right now, I'll try this after the holidays. If I want to check the ABS modul a basic VAG cable is the best option? |
|
A VAG cable is usually a K-Line interface, that doesn't work.
If the ABS is using SSM1 you need a 5V level RX and TX. So usually
something like an FTDI adapter from USB to TTL signal.
|
|
How / where to connect the rx tx signals for the abs on a newer car (2003
forester for example)And on an older one (93 turbo legacy) if thats even
supported ?
Le ven. 23 déc. 2022 à 18:53, L1800Turbo ***@***.***> a
écrit :
A VAG cable is usually a K-Line interface, that doesn't work.
If the ABS is using SSM1 you need a 5V level RX and TX. So usually
something like an FTDI adapter from USB to TTL signal.
—
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATTVWO4V2WIUFOOICK5OZDWOXRIFANCNFSM6AAAAAATFA7Y4M>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Rafael FOURNERET
Directeur, ZmajaDev Beograd, Zmaja od Nocaja 13a, 11158 Belgrade, Serbia
Téléphone :
France : +33 1 84 25 10 07
Serbie : +381 6 03 56 92 26
Mail : ***@***.***
Skype : rafaelfourneret
|
|
For the older yellow connector like this: You use pin 2 as TX, pin 3 as RX and pin 9 as GND. On the newer CARB OBD connector you have pins 4/5 for GND, the others should be 12 as TX and 13 RX. |
|
I don't have the manuals on hand, are these ABS specific pins or they are
the same as for ECU comms ?
Le ven. 23 déc. 2022 à 19:02, L1800Turbo ***@***.***> a
écrit :
… For the older yellow connector like this:
[image: image]
<https://user-images.githubusercontent.com/2099915/209385025-acc9db62-f747-4400-9ddd-dfde4e2bc822.png>
You use pin 2 as TX, pin 3 as RX and pin 9 as GND.
On the newer CARB OBD connector you have pins 4/5 for GND, the others
should be 12 as TX and 13 RX.
—
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATTVWJKLAGSOEXK2BSK6L3WOXSKVANCNFSM6AAAAAATFA7Y4M>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Rafael FOURNERET
Directeur, ZmajaDev Beograd, Zmaja od Nocaja 13a, 11158 Belgrade, Serbia
Téléphone :
France : +33 1 84 25 10 07
Serbie : +381 6 03 56 92 26
Mail : ***@***.***
Skype : rafaelfourneret
|
|
They are more SSM version specific. On the 1st gen Legacy you only have SSM1, so that ECU and TCU share the pins 2 and 3 on the yellow connector. ABS doesn't provide any diagnostic connection, you'd have to watch the LED under the passenger seat. Cruise control and Auto A/C use another clocked SSM protocol. |
|
So on which pins should I connect the TTL RX TX on the SG forester to read
the ABS ?
Thx
Le lun. 26 déc. 2022 à 12:03, L1800Turbo ***@***.***> a
écrit :
… They are more SSM version specific.
As for the Forester SG, you have SSM2 for ECU and TCU and (as I would
guess) SSM1 for the ABS module.
So SSM2 is shared on a single K Line pin, while SSM1 uses the RX and TX
lines with 5V level.
The mentioned pins are for communication with SSM1.
On the 1st gen Legacy you only have SSM1, so that ECU and TCU share the
pins 2 and 3 on the yellow connector. ABS doesn't provide any diagnostic
connection, you'd have to watch the LED under the passenger seat. Cruise
control and Auto A/C use another clocked SSM protocol.
—
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATTVWIYSSA5KR74MOT2JGDWPF3RXANCNFSM6AAAAAATFA7Y4M>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
In the OBD2 connector, pins 12 (Tx) abd 13 (Rx) are used.
If these pins are not wired, there is no ECU which uses the old protocol.
|
|
Thx i ll give it a try
Le mer. 15 mars 2023 à 20:54, Comer352L ***@***.***> a écrit :
In the OBD2 connector, pins 12 (Tx) abd 13 (Rx) are used.
If these pins are not wired, there is no ECU which uses the old protocol.
—
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATTVWKVH6K4GVKCQOGBCFTW4IM7PANCNFSM6AAAAAATFA7Y4M>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Rafael FOURNERET
Directeur, ZmajaDev Beograd, Zmaja od Nocaja 13a, 11158 Belgrade, Serbia
Téléphone :
France : +33 1 84 25 10 07
Serbie : +381 6 03 56 92 26
Mail : ***@***.***
Skype : rafaelfourneret
|
|
I get the message that connection is successful but the definition is Not
present. Anyway to add it ?
Le mer. 15 mars 2023 à 20:54, Comer352L ***@***.***> a écrit :
In the OBD2 connector, pins 12 (Tx) abd 13 (Rx) are used.
If these pins are not wired, there is no ECU which uses the old protocol.
—
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATTVWKVH6K4GVKCQOGBCFTW4IM7PANCNFSM6AAAAAATFA7Y4M>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Rafael FOURNERET
Directeur, ZmajaDev Beograd, Zmaja od Nocaja 13a, 11158 Belgrade, Serbia
Téléphone :
France : +33 1 84 25 10 07
Serbie : +381 6 03 56 92 26
Mail : ***@***.***
Skype : rafaelfourneret
|
|
On the main screen (or in the terminal) you should see a RomID. Can you mention it? |
|
No rom ID but here are the IDs present in my dump, one of them is the ABS
and the other one probably the cruise control but not sure which ones :
SG Forester :
---
…---
-----
-----
70 D4 00
-----
-----
-----
73 DB A0
-----
-----
BH LEGACY :
---
---
-----
-----
79 B4 00
-----
-----
-----
72 BB A0
-----
-----
Le sam. 18 mars 2023 à 06:57, L1800Turbo ***@***.***> a
écrit :
On the main screen (or in the terminal) you should see a RomID. Can you
mention it?
—
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATTVWJBANA6HO5BDXEZHD3W4VFDRANCNFSM6AAAAAATFA7Y4M>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Rafael FOURNERET
Directeur, ZmajaDev Beograd, Zmaja od Nocaja 13a, 11158 Belgrade, Serbia
Téléphone :
France : +33 1 84 25 10 07
Serbie : +381 6 03 56 92 26
Mail : ***@***.***
Skype : rafaelfourneret
|
|
Okay, I don't have these RomIDs yet, they're surely similar, but newer than the ones from the '97 version. As for the assignment, it'll propably be like this: |
|
Cool, thanks!
Yea they are 2003. Im pretty familiar with the old ssm1 ecu but have no
info whatsoever on the abs diag so i ll wait, would be awwsome if we can
add definitions for this generation.
Le sam. 18 mars 2023 à 14:03, L1800Turbo ***@***.***> a
écrit :
Okay, I don't have these RomIDs yet, they're surely similar, but newer
than the ones from the '97 version.
I'll have to get them analyzed first.
As for the assignment, it'll propably be like this:
xx xB xx: ABS
xx x4 xx: CruiseControl
—
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATTVWKZ3BOC2KBDFKOLNZDW4WXD3ANCNFSM6AAAAAATFA7Y4M>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Rafael FOURNERET
Directeur, ZmajaDev Beograd, Zmaja od Nocaja 13a, 11158 Belgrade, Serbia
Téléphone :
France : +33 1 84 25 10 07
Serbie : +381 6 03 56 92 26
Mail : ***@***.***
Skype : rafaelfourneret
|
|
The ECUs of the Legacy BH use same definitions which are already present
in the definition files.
Right now, their usage is restricted to ECUs with ID byte 1 = 0x76 (ABS)
and 0x74 (CC).
I'm going to modify the definitons to support ranges for this byte.
If you can't wait, you can modify the lines "<ID_BYTE1 value="0x7y">" in
the corresponding xml files (0x72 for the ABS, 0x79 for the CC) for testing.
The ECUs of the Forester SG are a bit different. It seems like they
support a few MBs/SWs more/less...
|
|
Anyway to get something runing for testing on the forester ? It’s the one
I’m having abs issues to diagnose.
Le dim. 19 mars 2023 à 22:19, Comer352L ***@***.***> a écrit :
The ECUs of the Legacy BH use same definitions which are already present
in the definition files.
Right now, their usage is restricted to ECUs with ID byte 1 = 0x76 (ABS)
and 0x74 (CC).
I'm going to modify the definitons to support ranges for this byte.
If you can't wait, you can modify the lines "<ID_BYTE1 value="0x7y">" in
the corresponding xml files (0x72 for the ABS, 0x79 for the CC) for
testing.
The ECUs of the Forester SG are a bit different. It seems like they
support a few MBs/SWs more/less...
—
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATTVWPY7LHNVAHPDMQTY6DW45Z4HANCNFSM6AAAAAATFA7Y4M>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Rafael FOURNERET
Directeur, ZmajaDev Beograd, Zmaja od Nocaja 13a, 11158 Belgrade, Serbia
Téléphone :
France : +33 1 84 25 10 07
Serbie : +381 6 03 56 92 26
Mail : ***@***.***
Skype : rafaelfourneret
|
|
That’s weird now I get this on the legacy :
I see system type 4mt, the rom id and number of data / switches but also
error message no or invalid answer from ecu.
Le dim. 19 mars 2023 à 22:44, Rafael Fourneret ***@***.***> a
écrit :
Anyway to get something runing for testing on the forester ? It’s the one
I’m having abs issues to diagnose.
Le dim. 19 mars 2023 à 22:19, Comer352L ***@***.***> a
écrit :
> The ECUs of the Legacy BH use same definitions which are already present
> in the definition files.
> Right now, their usage is restricted to ECUs with ID byte 1 = 0x76 (ABS)
> and 0x74 (CC).
> I'm going to modify the definitons to support ranges for this byte.
> If you can't wait, you can modify the lines "<ID_BYTE1 value="0x7y">" in
> the corresponding xml files (0x72 for the ABS, 0x79 for the CC) for
> testing.
>
> The ECUs of the Forester SG are a bit different. It seems like they
> support a few MBs/SWs more/less...
>
> —
> Reply to this email directly, view it on GitHub
> <#56 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AATTVWPY7LHNVAHPDMQTY6DW45Z4HANCNFSM6AAAAAATFA7Y4M>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
--
Rafael FOURNERET
Directeur, ZmajaDev Beograd, Zmaja od Nocaja 13a, 11158 Belgrade, Serbia
Téléphone :
France : +33 1 84 25 10 07
Serbie : +381 6 03 56 92 26
Mail : ***@***.***
Skype : rafaelfourneret
--
Rafael FOURNERET
Directeur, ZmajaDev Beograd, Zmaja od Nocaja 13a, 11158 Belgrade, Serbia
Téléphone :
France : +33 1 84 25 10 07
Serbie : +381 6 03 56 92 26
Mail : ***@***.***
Skype : rafaelfourneret
|
|
Please be patient, I'm busy with other stuff at the moment.
The plan is to get back to this next weekend.
|
|
Please share some details about both vehicles (MY, Engine, MT/AT, VDC
yes/no, market).
Send me a private mail (see "About" dialog in the software), I will
prepare something to test for you with detailed instructions.
|
|
I sent you info in an email just to check you got it.
Le dim. 26 mars 2023 à 14:08, Comer352L ***@***.***> a écrit :
Please share some details about both vehicles (MY, Engine, MT/AT, VDC
yes/no, market).
Send me a private mail (see "About" dialog in the software), I will
prepare something to test for you with detailed instructions.
—
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATTVWIMOXEIHS4ZDWZYVXTW6AWS7ANCNFSM6AAAAAATFA7Y4M>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Rafael FOURNERET
Directeur, ZmajaDev Beograd, Zmaja od Nocaja 13a, 11158 Belgrade, Serbia
Téléphone :
France : +33 1 84 25 10 07
Serbie : +381 6 03 56 92 26
Mail : ***@***.***
Skype : rafaelfourneret
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I compiled FreeSSM on a laptop I use for diagnostics running Windows 7, I have a J2534 cable /like this: https://www.aliexpress.com/item/672381461.html / which I use for Techstream. I wanted to use this cable with FreeSSM on a Forester SG, if I select XHorse MVCI in preferences the interface test fails with the warning that the interface does not support SSM1 protocol but I think it’s not communicating at all. What could be the problem?
The text was updated successfully, but these errors were encountered: