Unknown Port for VT06

CharlesEvo8 years ago

Hi All,

I tried several ports no. for VT06, but still unable to find matching one.

2017-02-15 10:35:18 DEBUG: [4CDE7AE0: 5026 < 183.171.82.180] HEX: 2929b100071780c6630c880d
2017-02-15 10:35:38 DEBUG: [4CDE7AE0: 5026 < 183.171.82.180] HEX: 2929b100071780c6630c880d

2017-02-15 10:40:26 DEBUG: [922CC64A: 5006 < 183.171.82.180] HEX: 2929b100071780c6630c880d
2017-02-15 10:40:46 DEBUG: [922CC64A: 5006 < 183.171.82.180] HEX: 2929b100071780c6630c880d

Any idea how to solve this issue? I have the docs but it is only provided in Chinese.

Charles.

Anton Tananaev8 years ago

It looks like KHD protocol. Correct port is 5058.

CharlesEvo8 years ago

Dear Anton,

Got it working now. Thanks alot.

Charles.

CharlesEvo8 years ago

Dear Anton,

For KHD, we are connection additional input for the fuel sensor. It the current protocol enable to transmit the data?

Here is the logs from the device:

  ["im"]=>
  string(9) "231287099"
  ["pro"]=>
  string(3) "khd"
  ["lat"]=>
  string(7) "3.10135"
  ["long"]=>
  string(18) "101.63991666666666"
  ["alt"]=>
  string(3) "0.0"
  ["sp"]=>
  string(3) "0.0"
  ["c"]=>
  string(5) "164.0"
  ["sc"]=>
  string(6) "0xF020"
  ["dt"]=>
  string(13) "1487251671000"
  ["gprmc"]=>
  string(68) "$GPRMC,132751.000,A,0306.0810,N,10138.3950,E,0.00,164.00,160217,,*08"
  ["attr"]=>
  string(71) "{"odometer":0,"ip":"183.171.87.100","distance":0.0,"totalDistance":0.0}"

HEX Data

2017-02-16 05:41:29 DEBUG: [62B2CD96: 5058 < 183.171.87.100] HEX: 2929b100071780c6630c880d
2017-02-16 05:41:29 DEBUG: [62B2CD96: 5058 > 183.171.87.100] HEX: 292921000588b1001d0d
2017-02-16 05:42:14 DEBUG: [62B2CD96: 5058 < 183.171.87.100] HEX: 2929b100071780c6630c880d
2017-02-16 05:42:14 DEBUG: [62B2CD96: 5058 > 183.171.87.100] HEX: 292921000588b1001d0d
2017-02-16 05:42:52 DEBUG: [62B2CD96: 5058 < 183.171.87.100] HEX: 2929a3002e1780c663170216134251003060811013839500000333f8000000ffff5200000a000000000000000601020000ed0d
2017-02-16 05:43:44 DEBUG: [62B2CD96: 5058 < 183.171.87.100] HEX: 2929b100071780c6630c880d
2017-02-16 05:43:44 DEBUG: [62B2CD96: 5058 > 183.171.87.100] HEX: 292921000588b1001d0d
2017-02-16 05:44:30 DEBUG: [62B2CD96: 5058 < 183.171.87.100] HEX: 2929b100071780c6630c880d
2017-02-16 05:44:30 DEBUG: [62B2CD96: 5058 > 183.171.87.100] HEX: 292921000588b1001d0d
2017-02-16 05:45:15 DEBUG: [62B2CD96: 5058 < 183.171.87.100] HEX: 2929b100071780c6630c880d
2017-02-16 05:45:15 DEBUG: [62B2CD96: 5058 > 183.171.87.100] HEX: 292921000588b1001d0d
2017-02-16 05:45:52 DEBUG: [62B2CD96: 5058 < 183.171.87.100] HEX: 2929a3002e1780c663170216134551003060811013839500000319f8000000ffff5200000a000000000000000601020054940d
2017-02-16 05:46:00 DEBUG: [62B2CD96: 5058 < 183.171.87.100] HEX: 2929b100071780c6630c880d
2017-02-16 05:46:00 DEBUG: [62B2CD96: 5058 > 183.171.87.100] HEX: 292921000588b1001d0d

Again, we can work out something by buying the support hours to get the fuel sensor data back to us.

Thank you.

Charles.

Anton Tananaev8 years ago

Traccar doesn't fuel sensor for this particular protocol. Do you have protocol documentation? We can definitely work on adding support for it.

CharlesEvo8 years ago

Yes. But it is in Chinese. You can use google Translate for the document.

http://52.77.39.80/staging/VT06.pdf

Anton Tananaev8 years ago

It will be harder to work with translated document. Send me an email if you want to discuss implementation.

CharlesEvo8 years ago

Noted. We did some trial and error on the last 8 chars of HEX and figure out that the device is actually submitting the fuel sensor data and it is very consistent. Will send you the email with our findings.