Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unified Diagnostic Services (UDS) - actually ISO15765-2 #214

Open
rusefi opened this issue Jun 9, 2015 · 15 comments
Open

Unified Diagnostic Services (UDS) - actually ISO15765-2 #214

rusefi opened this issue Jun 9, 2015 · 15 comments
Labels
CAN enhancement help wanted

Comments

@rusefi
Copy link
Collaborator

rusefi commented Jun 9, 2015 •
edited by rusefillc
Loading

ISO 15765-4 and SAE J2284

probably https://github.com/openxc/uds-c
@rusefi
Copy link
Collaborator Author

rusefi commented Jun 9, 2015

https://github.com/stanleyhuangyc/ArduinoOBD

http://rusefi.com/wiki/index.php?title=Manual:Hardware:CAN_sniffer

Original comment by: rusefi

@rusefi
Copy link
Collaborator Author

rusefi commented Jun 9, 2015

2015-06-09 19_15: EngineState: SID 7DF/8 2 1 0 99 99 99 99 99
2015-06-09 19_15: EngineState: Got OBD message
2015-06-09 19_15: EngineState: Got lookup request
2015-06-09 19_15: EngineState: waiting for CAN
2015-06-09 19_15: EngineState: SID 7DF/8 2 1 0 99 99 99 99 99
2015-06-09 19_15: EngineState: Got OBD message
2015-06-09 19_15: EngineState: Got lookup request
2015-06-09 19_15: EngineState: waiting for CAN
2015-06-09 19_15: EngineState: SID 7DF/8 2 1 1 99 99 99 99 99
2015-06-09 19_15: EngineState: Got OBD message
2015-06-09 19_15: EngineState: waiting for CAN
2015-06-09 19_15: EngineState: SID 7DF/8 2 1 1 99 99 99 99 99
2015-06-09 19_15: EngineState: Got OBD message
2015-06-09 19_15: EngineState: waiting for CAN
2015-06-09 19_15: EngineState: SID 7DF/8 2 1 1 99 99 99 99 99
2015-06-09 19_15: EngineState: Got OBD message
2015-06-09 19_15: EngineState: waiting for CAN
2015-06-09 19_15: EngineState: SID 7DF/8 1 3 99 99 99 99 99 99
2015-06-09 19_15: EngineState: Got OBD message
2015-06-09 19_15: EngineState: waiting for CAN
2015-06-09 19_15: EngineState: SID 7DF/8 1 3 99 99 99 99 99 99
2015-06-09 19_15: EngineState: Got OBD message
2015-06-09 19_15: EngineState: waiting for CAN
2015-06-09 19_15: EngineState: SID 7DF/8 1 3 99 99 99 99 99 99
2015-06-09 19_15: EngineState: Got OBD message
2015-06-09 19_15: EngineState: waiting for CAN
2015-06-09 19_15: EngineState: SID 7DF/8 1 3 99 99 99 99 99 99
2015-06-09 19_15: EngineState: Got OBD message
2015-06-09 19_15: EngineState: waiting for CAN
2015-06-09 19_15: EngineState: SID 7DF/8 1 3 99 99 99 99 99 99
2015-06-09 19_15: EngineState: Got OBD message
2015-06-09 19_15: EngineState: waiting for CAN
2015-06-09 19_15: EngineState: SID 7DF/8 1 3 99 99 99 99 99 99
2015-06-09 19_15: EngineState: Got OBD message
2015-06-09 19_15: EngineState: waiting for CAN
2015-06-09 19_15: EngineState: WARNING: MAF sensor needed for current fuel algorithm
2015-06-09 19_15: EngineState: SID 7DF/8 1 7 99 99 99 99 99 99
2015-06-09 19_15: EngineState: Got OBD message
2015-06-09 19_15: EngineState: waiting for CAN
2015-06-09 19_15: EngineState: SID 7DF/8 1 7 99 99 99 99 99 99
2015-06-09 19_15: EngineState: Got OBD message
2015-06-09 19_15: EngineState: waiting for CAN
2015-06-09 19_15: EngineState: SID 7DF/8 1 7 99 99 99 99 99 99

Original comment by: rusefi

@rusefi
Copy link
Collaborator Author

rusefi commented Jun 9, 2015

ISO attached

Original comment by: rusefi

@rusefi
Copy link
Collaborator Author

rusefi commented Oct 19, 2015

Rhinoman says:

"The specs that you can get on-line are the SAE specs, these are the specs that were originally called up by the OBD2 legislation, SAE specs generally are the US implementations of the International (ISO) standards. They are available from the internet archive and are usually easier to locate from Google.

i.e. SAE J1962 (connector).
https://archive.org/details/gov.law.sae.j1962.1995

i.e. SAE J1979 (test modes)
https://archive.org/details/gov.law.sae.j1979.2002

I have some ISO specs such as ISO11898 (CANbus)

The original CARB regulations are here:
http://www.anr.state.vt.us/air/docs/CalifCode/1968.1.pdf
You need to trawl through the EPA/CARB website because the regulations changed continuously. Mostly they just added stuff, foe example, KWP2000 and CANbus weren't allowed by the original regulations.

The main advantage of using ISO/SAE standards is that a cheap Bluetooth/ELM tool can be used, the main disadvantage is that, prior to CAN, its a very slow interface. Suzuki models use a combination of a proprietary implementation for live data and an OBD2 compliant implementation for fault codes, live data is also available via OBD2 for the proles."

See also
http://rusefi.com/forum/viewtopic.php?f=5&t=373&p=16744#p16736
http://rusefi.com/forum/viewtopic.php?f=5&t=373&p=16744#p16744

Original comment by: rusefi

@rusefi
Copy link
Collaborator Author

rusefi commented Nov 18, 2015

See also https://sourceforge.net/p/rusefi/tickets/30/

Original comment by: rusefi

@rusefi
Copy link
Collaborator Author

rusefi commented Dec 3, 2015

http://forscan.org/forum/viewtopic.php?f=4&t=867

Original comment by: rusefi

@rusefi
Copy link
Collaborator Author

rusefi commented Feb 16, 2017

See also fpoussin/MotoLink#1

Original comment by: rusefi

@rusefi rusefi self-assigned this Feb 21, 2017
@rusefi
Copy link
Collaborator Author

rusefi commented Apr 10, 2017

See https://github.com/fpoussin/MotoLink/blob/master/code/app/canbus.c#L32

@rusefi
Copy link
Collaborator Author

rusefi commented Nov 12, 2017

See also https://github.com/openxc/uds-c

@rusefi
Copy link
Collaborator Author

rusefi commented Jan 8, 2019

@fpoussin points to https://github.com/advancedtelematic/isotp-c

@rusefi
Copy link
Collaborator Author

rusefi commented Jan 11, 2019 •
edited
Loading

See also https://www.trionictuning.com/forum/viewtopic.php?f=58&p=90418

I wonder if between https://github.com/advancedtelematic/isotp-c for rusEfi firmware side and Saab https://txsuite.org/ for Windows side we can get fancy ISO-TP (ISO15765-2) support relatively easily? No idea what is the level of effort

@dron0gus @fpoussin

rusefi pushed a commit that referenced this issue May 12, 2019
@rusefillc
OBD-II at least something? #214
30019fb 
docs
@dron0gus
Copy link
Member

See also
https://github.com/UAVCAN/libuavcan_stm32
https://uavcan.org/Implementations/Libuavcan/

@rusefi rusefi mentioned this issue Jan 26, 2020
Closed
@rusefi rusefi changed the title OBD-II at least something? OBD-II at least something? actually ISO15765-2 Jan 26, 2020
@rusefi rusefi removed their assignment Jul 19, 2020
@rusefillc rusefillc changed the title OBD-II at least something? actually ISO15765-2 Unified Diagnostic Services (UDS) - actually ISO15765-2 Nov 27, 2021
@rusefillc rusefillc added the CAN label Nov 27, 2021
@rnd-ash
Copy link

rnd-ash commented Oct 12, 2022

A bit of an old issue to comment on, but I actually implemented the full KWP2000 layer (Similar to UDS) on my 722.6 TCU! (Supports over either USB or CAN with ISO-TP).

I should note this KWP2000 layer also emulates the OEM TCU one, so my custom TCU actually works fine in Mercedes' own diagnostic tool.

I am planning to eventually migrate to UDS (And keep KWP for just interfacing with Mercedes' tool sets)

You can check all that code here:
https://github.com/rnd-ash/ultimate-nag52-fw/tree/main/src/diag

@rusefillc
Copy link
Contributor

See also #4501

@rusefillc
Copy link
Contributor

https://github.com/bri3d/VW_Flash

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CAN enhancement help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rnd-ash @dron0gus @rusefillc