OBDX Development - Developer Tools and Suggestions
Re: OBDX Development - Developer Tools and Suggestions
USA = Canada same stuff !!
The 27 01 28 I first saw in a FCA NGC3 - SCI bus connection . Then I checked NCG4 - CAN and it was there as well .
NGC3
Send 27 01 28
response 67 01 F8 2C 8C => Seed F8 2C
Send Key 27 02 B6 98 77 => Key B6 98
resp 67 02 69 => OK
NGC4
7E0 8 2 27 5 0 0 0 0 0
7E8 8 4 67 5 57 C3 0 0 0
7E0 8 4 27 6 87 14 0 0 0
7E8 8 3 67 6 34 C3 0 0 0
7DF 8 2 3E 2 0 0 0 0 0
Can you check if this is same algorithm as Ford ?
I don't know how to calculate the Key .
The 27 01 28 I first saw in a FCA NGC3 - SCI bus connection . Then I checked NCG4 - CAN and it was there as well .
NGC3
Send 27 01 28
response 67 01 F8 2C 8C => Seed F8 2C
Send Key 27 02 B6 98 77 => Key B6 98
resp 67 02 69 => OK
NGC4
7E0 8 2 27 5 0 0 0 0 0
7E8 8 4 67 5 57 C3 0 0 0
7E0 8 4 27 6 87 14 0 0 0
7E8 8 3 67 6 34 C3 0 0 0
7DF 8 2 3E 2 0 0 0 0 0
Can you check if this is same algorithm as Ford ?
I don't know how to calculate the Key .
Re: OBDX Development - Developer Tools and Suggestions
I'm not good with the seed/key stuff, others here are. It looks like your CAN communication logging is missing stuff.
Re: OBDX Development - Developer Tools and Suggestions
I am also interested in FCA stuff ...
acln99,
Do you (or anyone) know what years have the SBEC3 and NGC? ECM ??
I'm interested in info on 2008-2015 Dodge specifically.
Thanks
-Enjoy
acln99,
Do you (or anyone) know what years have the SBEC3 and NGC? ECM ??
I'm interested in info on 2008-2015 Dodge specifically.
Thanks
-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!
Re: OBDX Development - Developer Tools and Suggestions
Most likely. This was taken from one of my first attempts years ago. I was using Elm327 but it wasn't fast enough to capture all messages.In-Tech wrote:I'm not good with the seed/key stuff, others here are. It looks like your CAN communication logging is missing stuff.
Learned about Ardunio Uno & then ESP32. ESP32 was finally fast enough to capture all msgs. Didn't get much farther at the time - I new nothing !!
Re: OBDX Development - Developer Tools and Suggestions
Generally as follows with overlap as platforms were updatesGampy wrote:I am also interested in FCA stuff ...
acln99,
Do you (or anyone) know what years have the SBEC3 and NGC? ECM ??
I'm interested in info on 2008-2015 Dodge specifically.
Thanks
-Enjoy
1998 - 2001 SBEC3 CCD / PCI SCI bus ( 2 plug)
2002 - 2003 NGC2 PCI SCI - 4 plug
2004 - 2007 NGC3 PCI SCI - 4 plug
2008 - 2012~ NGC4 CAN - 4 plug
2014 + GPEC - too new for me !!
there also was a JTEC - PCI used between SBEC and NGC mainly for Jeeps.
Re: OBDX Development - Developer Tools and Suggestions
See what you did there Gampy? It was bad enough we were talking Ford, now you gotta talk Chrysler?




Re: OBDX Development - Developer Tools and Suggestions
Nope, that's all folks ... At least from me, except this: If only you knew about my association with Chrysler!
-Enjoy
-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!
Re: OBDX Development - Developer Tools and Suggestions
We don't care about your ass ociations, just the pictures,Gampy wrote:Nope, that's all folks ... At least from me, except this: If only you knew about my association with Chrysler!
-Enjoy


Re: OBDX Development - Developer Tools and Suggestions
I hope you all laughed, trying to be funny, lol
- antus
- Site Admin
- Posts: 9017
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: OBDX Development - Developer Tools and Suggestions
Not new information but there seems to be a few people here learning, so just for those the 27 01 security stuff is a standard or at least based on a standard see https://www.automotive.wiki/index.php/ISO_14229
The algorithms are intentionally proprietary, even where its the same OEM for the computer.
Also, since I found it just now while looking for good links, for those of you familiar with the OSI model for computer networks, here is the equivalent for vehicle networks, which also shows which standards to look in to for different layers.
The algorithms are intentionally proprietary, even where its the same OEM for the computer.
Also, since I found it just now while looking for good links, for those of you familiar with the OSI model for computer networks, here is the equivalent for vehicle networks, which also shows which standards to look in to for different layers.
- Attachments
-
- wwh-obd-osi-model-diagnostic-protocols-sae-iso-j1939-uds.svg
- (25.19 KiB) Downloaded 232 times
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396