Line 1: |
Line 1: |
− | ===To check or OBD data is available from OBD device, please follow this description=== | + | ===To check if the OBD data is available from the device, please follow this tutorial=== |
| | | |
| Send ''[[FMB obdinfo|obdinfo]]'' SMS/GPRS command to device. | | Send ''[[FMB obdinfo|obdinfo]]'' SMS/GPRS command to device. |
− | <br/>
| |
| | | |
− | The device responds with:<br/> Protocol, VIN, AdaptiveTiming value, requested PID counter, OBD application state, available vehicle PIDs, mil status, number of DTCs.<br/><br/> | + | |
− | For example: Protocol:6,VIN:WVWZZZAUZFW125650,TM:0,CNT:11,ST:PROTOCOL DETECTION,P1:0x98180001,P2:0x1,P3:0xE0800020,P4:0x0,Fuel:OFF,MIL:0,DTC:0,ID0 | + | The device responds with: Protocol, VIN, Adaptive Timing value, requested PID counter, OBD application state, available vehicle PIDs, mil status, number of DTCs. |
− | <br/><br/>
| + | |
− | According to obdinfo response you can check available OBD parameters via OBD Pid Reader. OBD reader can be found [https://www.glmsoftware.com/Downloads1.aspx '''here'''] | + | For example: Protocol:6 VIN: WVWZZZAUZFW125650,TM:0,CNT:11,ST:PROTOCOL DETECTION,P1:0x98180001,P2:0x1,P3:0xE0800020,P4:0x0,Fuel:OFF,MIL:0,DTC:0,ID0 |
− | <br/><br/>
| + | |
| + | According to the obdinfo response you can check available OBD parameters via OBD PID Reader. OBD reader can be found [https://www.glmsoftware.com/Downloads1.aspx '''here'''] |
| + | |
| [[Image:OBDII_SCAN.png|center]] | | [[Image:OBDII_SCAN.png|center]] |
− | Protocol:6 – specifies car supported protocol.<br/> | + | |
− | VIN:WVWZZZAUZFW125650 -specifies car vin number.<br/> | + | Protocol:6 – specifies car supported protocol. |
− | ST:PROTOCOLDETECTION- specifies OBD application state<br/> | + | |
− | P1:0x98180001,P2:0x1,P3:0xE0800020,P4:0x0 - specifies available vehicle PIDs. These values specifies available parameters in car. If all pids values 0 (P1:0x0,P2:0x0,P3:0x0,P4:0x0), it means that OBD parameters is not readable.<br/> | + | VIN: WVWZZZAUZFW125650 -specifies car VIN number. |
− | MIL:0 - mil status, indicates state of the led(0- OFF, 1-ON).<br/> | + | |
− | DTC:0 - number of errors.<br/><br/> | + | ST: PROTOCOLDETECTION- specifies OBD application state. |
− | Please find additional information here:<br/> | + | |
| + | P1:0x98180001,P2:0x1,P3:0xE0800020,P4:0x0 - specifies available vehicle PIDs. These values specify the available parameters in a given car. If all PID values are 0 (P1:0x0,P2:0x0,P3:0x0,P4:0x0), it means that OBD parameters are not readable. |
| + | |
| + | MIL:0 - mil status, indicates the state of the LED (0- OFF, 1-ON). |
| + | |
| + | DTC:0 – the number of errors. |
| + | |
| + | Please find additional information here: |
| + | |
| #[https://wiki.teltonika-gps.com/view/FMB001_Supported_OBD_protocols '''OBDII protocols supported by the FMB001 and FM3001'''] | | #[https://wiki.teltonika-gps.com/view/FMB001_Supported_OBD_protocols '''OBDII protocols supported by the FMB001 and FM3001'''] |
| + | |
| #[https://wiki.teltonika-gps.com/view/Template:FMB_Device_Family_Parameter_list#OBD_II_.28Blue-tooth.29 '''OBDII parameter list'''] | | #[https://wiki.teltonika-gps.com/view/Template:FMB_Device_Family_Parameter_list#OBD_II_.28Blue-tooth.29 '''OBDII parameter list'''] |