Meitrack VT380 not recognize ?

binooetomo8 years ago

Dear All..

I have Meitrack VT380

  1. Part of my 

        <entry key='meitrack.enable'>true</entry>
 <entry key='meitrack.resetDelay'>120</entry>
 <entry key='meitrack.port'>5020</entry>

  2. Part of my tracker-server.log

    2016-03-29 06:20:20  INFO: [4E45B765] id: 4, time: 2016-03-29 06:20:18, lat: -7.73878, lon: 110.40925, speed: 0.0, course: 105.0
2016-03-29 06:20:29 DEBUG: [4E45B765: 5020 < 202.67.40.26] HEX: 2424413133382c3836313037343032373337323237382c4141412c33352c2d372e3733383738312c3131302e3430393235302c3136303332393130323032382c412c31312c31312c302c3130352c302e382c3231352c3239322c34323732312c3531307c38397c324237457c353746432c303030302c303030437c303030387c7c303244387c303130302c2a44380d0a
2016-03-29 06:20:29  INFO: [4E45B765] id: 4, time: 2016-03-29 06:20:28, lat: -7.73878, lon: 110.40925, speed: 0.0, course: 105.0
2016-03-29 06:20:40 DEBUG: [4E45B765: 5020 < 202.67.40.26] HEX: 2424423133382c3836313037343032373337323237382c4141412c33352c2d372e3733383738312c3131302e3430393235302c3136303332393130323033382c412c31312c31312c302c3130352c302e382c3231352c3239322c34323733312c3531307c38397c324237457c353746432c303030302c303030417c303030327c7c303244387c303046462c2a46450d0a
2016-03-29 06:20:40  INFO: [4E45B765] id: 4, time: 2016-03-29 06:20:38, lat: -7.73878, lon: 110.40925, speed: 0.0, course: 105.0
2016-03-29 06:20:50 DEBUG: [4E45B765: 5020 < 202.67.40.26] HEX: 2424433133382c3836313037343032373337323237382c4141412c33352c2d372e3733383738312c3131302e3430393235302c3136303332393130323034382c412c31312c31312c302c3130352c302e382c3231352c3239322c34323734312c3531307c38397c324237457c353746432c303030302c303030397c303030327c7c303244387c303046462c2a46390d0a
2016-03-29 06:20:50  INFO: [4E45B765] id: 4, time: 2016-03-29 06:20:48, lat: -7.73878, lon: 110.40925, speed: 0.0, course: 105.0
2016-03-29 06:21:00 DEBUG: [4E45B765: 5020 < 202.67.40.26] HEX: 2424443133382c3836313037343032373337323237382c4141412c33352c2d372e3733383738312c3131302e3430393235302c3136303332393130323035392c412c31312c31312c302c3130352c302e382c3231352c3239322c34323735312c3531307c38397c324237457c353746432c303030302c303030387c303030347c7c303244387c303046462c2a46450d0a
2016-03-29 06:21:00  INFO: [4E45B765] id: 4, time: 2016-03-29 06:20:59, lat: -7.73878, lon: 110.40925, speed: 0.0, course: 105.0
2016-03-29 06:21:10 DEBUG: [4E45B765: 5020 < 202.67.40.26] HEX: 2424453133382c3836313037343032373337323237382c4141412c33352c2d372e3733383738312c3131302e3430393235302c3136303332393130323130392c412c31322c31312c302c3130352c302e382c3231352c3239322c34323736312c3531307c38397c324237457c353746432c303030302c303030417c303030347c7c303244387c303130302c2a44420d0a
2016-03-29 06:21:10  INFO: [4E45B765] id: 4, time: 2016-03-29 06:21:09, lat: -7.73878, lon: 110.40925, speed: 0.0, course: 105.0
2016-03-29 06:21:20 DEBUG: [4E45B765: 5020 < 202.67.40.26] HEX: 2424463133382c3836313037343032373337323237382c4141412c33352c2d372e3733383738312c3131302e3430393235302c3136303332393130323131392c412c31312c31312c302c3130352c302e382c3231352c3239322c34323737312c3531307c38397c324237457c353746432c303030302c303030397c303030327c7c303244387c303130302c2a44330d0a
2016-03-29 06:21:20  INFO: [4E45B765] id: 4, time: 2016-03-29 06:21:19, lat: -7.73878, lon: 110.40925, speed: 0.0, course: 105.0
2016-03-29 06:21:30 DEBUG: [4E45B765: 5020 < 202.67.40.26] HEX: 2424473133382c3836313037343032373337323237382c4141412c33352c2d372e3733383738312c3131302e3430393235302c3136303332393130323132392c412c31302c31312c302c3130352c302e392c3231352c3239322c34323738312c3531307c38397c324237457c353746432c303030302c303030417c303030307c7c303244387c303130302c2a44430d0a
2016-03-29 06:21:30  INFO: [4E45B765] id: 4, time: 2016-03-29 06:21:29, lat: -7.73878, lon: 110.40925, speed: 0.0, course: 105.0
2016-03-29 06:21:40 DEBUG: [4E45B765: 5020 < 202.67.40.26] HEX: 2424483133382c3836313037343032373337323237382c4141412c33352c2d372e3733383738312c3131302e3430393235302c3136303332393130323133392c412c31302c31312c302c3130352c302e392c3231352c3239322c34323739312c3531307c38397c324237457c353746432c303030302c303030417c303030327c7c303244387c303046462c2a30430d0a

  3. Use the last data with hex-decoder, got :

    $$H138,861074027372278,AAA,35,-7.738781,110.409250,160329102139,A,10,11,0,105,0.9,215,292,42791,510|89|2B7E|57FC,0000,000A|0002||02D8|00FF,*0C

I think it's looks like a valid meitrack protocol.
Anyhow, when I check the webUI (the device is registered) ... there is no data from this device.

Kindly please tell me what to do.

Sincerely
-bino-

Anton Tananaev8 years ago

As far as I can see the data is decoded correctly (see INFO log records), so you should be able to see your device.

binooetomo8 years ago

Dear Sir.

It Works now.

I guess there is something with the webUI.
Right after I post previouse message, I retry to click device name ... and it showed.

Appreciate your response.

Sincerely
-bino-