J2534 pass-thru
-
- Posts: 305
- Joined: Fri Jul 30, 2021 5:49 pm
- cars: 97 Corvette
92 Camaro
2005 Silverado
2001 Savana 2500
1998 c3500hd
1998 tahoe
J2534 pass-thru
So I'm curious, does anyone know if the j2534 protocol means that my gm nano is capable of being used as pass thru for any make for module programming? Or is it still tied to gm and its vpw and CAN protocols? I've been looking and haven't found definitive explanation of function. Example, why can't Ford fjds use my gm nano as pass thru for module programming? Or is it a protocol switch during use for programming?
Re: J2534 pass-thru
Depends if your vx nano supports the require protocol to use with Fords.Cincinnatus wrote:So I'm curious, does anyone know if the j2534 protocol means that my gm nano is capable of being used as pass thru for any make for module programming? Or is it still tied to gm and its vpw and CAN protocols? I've been looking and haven't found definitive explanation of function. Example, why can't Ford fjds use my gm nano as pass thru for module programming? Or is it a protocol switch during use for programming?
This is why allscanner (the manufactures) have different versions of their tool to support different protocols.
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
-
- Posts: 305
- Joined: Fri Jul 30, 2021 5:49 pm
- cars: 97 Corvette
92 Camaro
2005 Silverado
2001 Savana 2500
1998 c3500hd
1998 tahoe
Re: J2534 pass-thru
I know different makes use different comm protocols, but the j2534 is universal among manufacturers, so that's where I'm confused. It must switch from say GM's j1850 vpw to j2534 when the programming event occurs, but only then is the j2534 in use, otherwise it's vpw.
Re: J2534 pass-thru
Oh I see the confusion!Cincinnatus wrote:I know different makes use different comm protocols, but the j2534 is universal among manufacturers, so that's where I'm confused. It must switch from say GM's j1850 vpw to j2534 when the programming event occurs, but only then is the j2534 in use, otherwise it's vpw.
I can answer this.. since well.. I have just made a J2534 DLL for my own OBDX tools.
Ok so we have the following setup:
Dealership software <-> J2534 DLL <-> Scantool <-> Car
The dealership communicates with the standardized J2534 protocol, this is bascially a set of commands that MUST be present in a J2534 DLL made by the scantool manufacture such as allscanner (VX Nano), Bosch, Drewtech ect.
The manufactures J2534 DLL then speaks to its connected scantool (made by that manufacture) to then communicate to the car.
The dealership software then makes commands to the J2534 DLL to change the OBD2 protocol to VPW, or CANbus. The J2534 DLL then communicates to the scantool and commands the scantool to use that protocol, or send a message ect.
So even thought the VX Nano suppports the J2534 compliancy, this does not mean the vx nano will supported the vehicles OBD2 protocol. Hopefully that makes sense!
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
-
- Posts: 305
- Joined: Fri Jul 30, 2021 5:49 pm
- cars: 97 Corvette
92 Camaro
2005 Silverado
2001 Savana 2500
1998 c3500hd
1998 tahoe
Re: J2534 pass-thru
That's what I thought, though I can use my gm nano with forscan on several Ford's so far, though it was only diagnostics and live data (which still wasn't GM's vpw) though it wouldn't work on one vehicle (and I forget which one it was, I think it was an old explorer, and I had to use my elm). I may just try to see if fjds will work and report back.
-
- Posts: 305
- Joined: Fri Jul 30, 2021 5:49 pm
- cars: 97 Corvette
92 Camaro
2005 Silverado
2001 Savana 2500
1998 c3500hd
1998 tahoe
Re: J2534 pass-thru
Doesn't really make sense to call j2534 a pass thru when it's really an intermediary between software and interface, not pass thru between software and module being programmed.
Re: J2534 pass-thru
I gues sit depends how you look at it.Cincinnatus wrote:Doesn't really make sense to call j2534 a pass thru when it's really an intermediary between software and interface, not pass thru between software and module being programmed.
Personally I see "Direct Connection" as Software to scantool.
And a "Passthrough" as the software "Passes" the information through the J2534 API to the scantool.
Well.. thats my interpretation at least!
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
-
- Posts: 305
- Joined: Fri Jul 30, 2021 5:49 pm
- cars: 97 Corvette
92 Camaro
2005 Silverado
2001 Savana 2500
1998 c3500hd
1998 tahoe
Re: J2534 pass-thru
I believe my mistake was thinking the j2534 was between tool and ECU (or between software and ECU, passing thru the tool), but it is between software and tool only.
Re: J2534 pass-thru
That's right!Cincinnatus wrote:but it is between software and tool only.
As the typical whole story flows ...
End user software <--> J2534 DLL <--> VCI DLL <--> VCI <--> VCI Protocol (VPW/CAN/...) <--> Unit that speaks VCI configured protocol (i.e. PCM/TCM/...).
The VCI DLL may have a J2534 API.
-Enjoy
Intelligence is in the details!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!