iStartek vt202

Hi,

Not getting the new vt202 working on Traccar. The vt206 is working fine. Both on TRV.

This is the debug info:

2017-08-31 12:32:14 DEBUG: [2CE47473: 5010 < 185.68.55.253] HEX: 5452564150303033353231323130383830313535343823
2017-08-31 12:32:14 DEBUG: [2CE47473: 5010 > 185.68.55.253] HEX: 5452564250303023
2017-08-31 12:32:14 DEBUG: [2CE47473: 5010 < 185.68.55.253] HEX: 545256415031342c3230342c382c333233302c313330303723
2017-08-31 12:32:14 DEBUG: [2CE47473: 5010 > 185.68.55.253] HEX: 5452564250313423

Anyone have an idea?

Your device just doesn't report any GPS location data.

But in their own platform it does give location information. I have a manual for the tracker. Is it possible to have a quick look what goes wrong and might be different to the vt206?

Maybe their platform actively requests data from device? Traccar doesn't do that and your device doesn't send it. I would recommend contacting device vendor for more info.

Thanks! Asked them

Can Traccar send a request or is that impossible? No answer yet. They are off to bed.

Everything is possible, but I don't think that's how it should work.

If I email you the protocol document. Can you check it against the current trv protocol?
Maybe there is just a little mistake/difference in it. I'm trying to see the differences, but can't get the puzzle done.

It doesn't look like it needs anything 'special'.

Sure.

Is there a way to see the data before it is processed?

You can see HEX data in the logs. That's raw messages from devices.

Found out the current TRV protocol decoder on github doesn't completely match the spec's i've got.
Will try to update and see if I can make a working one.

I have implemented correct AP14 response. It always returns zeroes as coordinates for now, but the response format is correct.

Thanks! How do I implement it on my server? Wait for the update?

Build it from source or wait for update.