help finding no-name/chinese OBD tracker port

RichardG6 years ago

Hi Support/Anton,

Could you please help me with this issue?

I've purchased a chinese tracker that plugs into the OBD port of the car. I've got this device working using the sellers tracking software, but I want to configure it to use traccar.

I've tried all the ports in your guide: https://www.traccar.org/ports-for-tk-gt-and-other-gps-devices/

This is what my logs show:

2016-06-19 22:35:51  INFO: [71D81AF6] connected
2016-06-19 22:35:52 DEBUG: [71D81AF6: 5093 < 49.181.203.198] HEX: *HIDDEN HEX*
2016-06-19 22:36:18 DEBUG: [71D81AF6: 5093 < 49.181.203.198] HEX: *HIDDEN HEX*
2016-06-19 22:36:43 DEBUG: [71D81AF6: 5093 < 49.181.203.198] HEX: *HIDDEN HEX*
2016-06-19 22:36:44  INFO: [71D81AF6] disconnected

When I convert the hex using your tool I get the below output:
À> OBD_3G1_V1.0.3 HIDDEN IMEI ‡ ¡¶À

Information from the chinese trackers user manual:
● OBDII and CANBUS protocol, DC 12V and 24V;
● Support wireless relay (cut off engine remotely);
● 2G GSM/GPRS 850/900/1800/1900MHz;
● 3G UMTS/HSPA 2100/1900/850/900MHz;
● Plug and play, small size, no installation cost;
● Collect fuel consumption, fuel level data;
● Very accurate mileage data (accuracy>99%);
● Collect DTC (Diagnostic Trouble Code) for remote diagnostic;
● Collect RPM, VIN, engine temperature data;
● Internal GSM and GPS antennas;
● TCP and UDP;
● Update firmware over the air;
● Illegal start-up, impact and rollover alarm;
● Detect harsh acceleration, braking, turn and high revolution;
● Driving behavior recording and analysis;
● Store break points data in non-volatile memory;
● Track on Google map and other maps;
● Auto sleep mode to save automotive power;
● Wide working temperature range: -30 to +80℃.

2.3 Technology Specifications
Appearance Features
16 Pin Connector Insert in OBDII port in vehicle
Three Indicators When device connects power at first time, three indicators will light and blink together then turn off. Yellow and red indicators will blink late. This mean device has been initialized.
Blue Indicator Quick blinking means offline, slow blinking means online.
Green Indicator Quick blinking means no GPS signal, slow blinking means GPS signal received.
Red Indicator Sleeping status: Indicator will blink but blue and green indicators will be off.
Working mode: Indicator will be off.
USB Port Locally update firmware and debug program
GPS Antenna Internal
Communication Antenna Internal
Technology Parameters
CPU NXP ARM7
GPS Module U-blox or JRC
Communication Module Telit 3G module UL865
2G: GSM/GPRS 850/900/1800/1900MHz
3G: UMTS/HSPA 2100/1900/850/900MHz
3D Accelerometer Range:±2g/±4g/±8g
Dynamic, Optional
Output data rate(ODR): 1.56-800Hz
Protocol ISO 15765-4 (CAN)
ISO 14230-4 (Keyword Protocol 2000)
ISO 9141-2 (Asian, European, Chrysler
vehicles)
SAE J1850 VPW (GM vehicles)
SAE J1850 PWM (Ford vehicles)

ISO 15765
ISO 11898 (raw CAN)

SAE J1939 protocol

Non-legislated OBD protocols (can be added, not standard function):
Single Wire CAN (SW-CAN) – GM proprietary network
Medium Speed CAN (MS-CAN) – Ford proprietary network
General Statement
Material ABS
Size 624820mm
Weight 70g
Battery 50mAh li-polymer
Battery DC 9 - 32V
Current 70mA (Working), 20mA(Sleeping)
Working Temperature -30℃-75℃
Working Humidity 95%(Non-condensed)

2.3 Interface

PIN Function PIN Function
1 NC 9 NC
2 SAEJ1850 bus + 10 SAEJ1850 BUS-
3 NC 11 NC
4 Vehicle body GND 12 NC
5 Signal GND 13 NC
6 CANBUS HIGH 14 CANBUS LOW
7 K line 15 L or K2 line
8 NC 16 Power +

Anton Tananaev6 years ago

Not sure how you want me to identify protocol if you are not showing the actual messages from the device. If you are concerned about privacy, you can send me sample by email (see support page for address).

RichardG6 years ago
2016-06-20 10:21:01  INFO: [BCC992CF] connected
2016-06-20 10:21:02 DEBUG: [BCC992CF: 5055 < 49.195.15.237] HEX: c0010c003e0002000000000024020012a0014f42445f3347315f56312e302e330013a0043335353835353035303434303635380006a08701000006a0a103bfc0
2016-06-20 10:21:27 DEBUG: [BCC992CF: 5055 < 49.195.15.237] HEX: c0010c003e0002000000000025020012a0014f42445f3347315f56312e302e330013a0043335353835353035303434303635380006a08701000006a0a103c4c0
2016-06-20 10:21:52 DEBUG: [BCC992CF: 5055 < 49.195.15.237] HEX: c0010c00120060000000000026000600010100c0
2016-06-20 10:21:54  INFO: [BCC992CF] disconnected
Anton Tananaev6 years ago

It doesn't match any existing protocol as far as I can tell. I need protocol documentation for your device.

RichardG6 years ago

I've emailed you a copy of the user manual