DTC
As of 2019-03, no Teltonika OBD-II device is able to read out DTC's (diagnostic trouble codes).FMB001 and FM3001 can read out DTC's (diagnostic trouble codes).
There is also a "Fault Codes" AVL ID in newer firmware versions. If
- the elment is enabled and
- DTC's are available on the vehicle,
then DTC's will be sent to the server under the AVL I/O ID - 281 encoded with Codec 8 Extended.
There is also an SMS command:
- faultcodes = displays all visible fault codes.
There is no command that will list all DTC's supported by a vehicle. Only current (occurring at reading time) DTC's can be read out.
The DTC's that can be read by an FM OBD-II device depend on the vehicle make/model/year. Teltonika however does not have a Supported Vehicle List. Customers will have to
- plug in the FM OBD-II device and
- test the command to see
- if and
- possibly which
- DTC's are returned and read.
Supported OBD-II protocols:
- FMB001 Supported OBD protocols
FMB001 does not support SAE J1939 CAN (29 bit ID, 250 kbaud). - FM3001 Supported OBD protocols
SAE J1939 CAN (29 bit ID, 250 kbaud) is used only with FM3001 and ELD (electronic logging device) functionality.
How to read ELD data with FM3001?
Tesla Motors
Teltonika FMB OBD-II devices can be connected to Tesla cars featuring an OBD-II socket.
However, Tesla cars do not support the OBD-II protocol, so you might not receive data through this socket even if a Teltonika FMB OBD-II is connected.
If any probem occurs due to this connection, please send the following SMS command:
" setparam 40000:0" (disables OBD-II feature on the Teltonika device).
VIN
OBD-II VIN (vehicle identification number) has a length of 17 bytes and does not fit into Codec 8 protocol.
To get VIN:
- configure device to use Codec 8 Extended protocol
device Configurator > System > data protocol > codec 8 extended - configure server to use Codec 8 Extended protocol
- get AVL parameter ID: 256