You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Standard OBD-2 protocol is not supported in electric vehicles. Other diagnostic protocols over OBD-socket are used instead, applying longer parameter IDs. Is there a plan to support these protocols in further Freematic software versions?
The text was updated successfully, but these errors were encountered:
I doubt it's even specific to EV's. It might simply be recent cars in general: they don't support the standard OBD-II PID's, but work using Unified Diagnostic Services instead.
Based on the information in this issue I've been trying some things and these are some of the problems in need of solving in order to support UDS.
Using other services than 01.
Currently the service / mode used is hardcoded.
Better response parsing
I believe that at this time, only the first line returned by the co-processor (acting as an ELM327) is parsed, while there may be several, as UDS uses ISO-TP in order to handle messages that are larger than the space available in a CAN frame.
Support getting multiple data points from one PID
In UDS, it seems common to have one PID with many data fields within it. For example 220101 in Hyundai/KIA vehicles: source
I do think the lack of UDS support will increasingly be a deal breaker for Freematics products.
Standard OBD-2 protocol is not supported in electric vehicles. Other diagnostic protocols over OBD-socket are used instead, applying longer parameter IDs. Is there a plan to support these protocols in further Freematic software versions?
The text was updated successfully, but these errors were encountered: