New Traccar Protocol/TopFlyTech

Carlos Acosta3 years ago

Hi! I'm working with the TopFlytech brand, specifically with the TLW1-10 and TLW-8 models, I have configured port 5094, I see the gps online but with coordinates 0.000,0.000, the log file shows this when the gps.

2021-09-23 23:11:53  INFO: [a0d3063e: t800x < 200.68.186.54] HEX: 252501001700010867730050944713010805010a110720
2021-09-23 23:11:53  INFO: [a0d3063e: t800x > 200.68.186.54] HEX: 252501000f00010867730050944713
2021-09-23 23:11:58  INFO: [cff6b64e] connected
2021-09-23 23:11:58  INFO: [a0d3063e: t800x < 200.68.186.54] HEX: 2525110055000108677300509447132109232311530c540045004c00430045004c0004454447450847534d20313930300f333334303230323137373632363634143839353230323030323133393336303338363146
2021-09-23 23:11:58  INFO: [a0d3063e: t800x > 200.68.186.54] HEX: 252511000f00010867730050944713

These models are not compatible yet or does it have a different port configuration?

Thank you so much

Anton Tananaev3 years ago

What makes you think that device is sending valid GPS data?

It also looks like you cut out important parts from the log.

Carlos Acosta3 years ago

hi Anton!

that same record is always repeated, the first time the device was seen online in the log the following was recorded

2021-09-23 20:06:31  INFO: [a49ecacb: t800x < 200.68.159.112] HEX: 252501001700040867730050944713010805010a110720
2021-09-23 20:06:31  INFO: [a49ecacb: t800x > 200.68.159.112] HEX: 252501000f00040867730050944713
2021-09-23 20:06:32  INFO: [a49ecacb: t800x < 200.68.159.112] HEX: 2525110059000108677300509447132109232006310c540045004c00430045004c00064341542d4d310a4c54452042414e4420340f333334303230323137373632363634143839353230323030323133393336303338363146
2021-09-23 20:06:32  INFO: [a49ecacb: t800x > 200.68.159.112] HEX: 252511000f00010867730050944713
2021-09-23 20:06:32  INFO: [a49ecacb: t800x < 200.68.159.112] HEX: 252581008c000108677300509447130149004d00450049003a003800360037003700330030003000350030003900340034003700310033002c0055005000470052004100440045005f004d004300550020005300550043004300450053005300210020006600610069006c00650064002000540069006d006500730020003000200030002000300020003000
2021-09-23 20:06:32  INFO: [a49ecacb: t800x > 200.68.159.112] HEX: 252581000f00010867730050944713
2021-09-23 20:06:32  INFO: [a49ecacb] id: 867730050944713, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0, result: IMEI:867730050944713,UPGRADE_MCU SUCCESS! failed Times 0 0 0 0

from that moment I only get the following result (always the same)

2021-09-23 20:08:44  INFO: [3d42da16] connected
2021-09-23 20:08:44  INFO: [3d42da16: t800x < 200.68.159.112] HEX: 252501001700050867730050944713010805010a110720
2021-09-23 20:08:44  INFO: [3d42da16: t800x > 200.68.159.112] HEX: 252501000f00050867730050944713

and on the web therefore it only appears online but with coordinates 0 and that date

What parts are expected or missing?

thanks for your answer!

Anton Tananaev3 years ago

Have you checked it against protocol documentation?

URLEY REY3 years ago

Hello dear. The same thing happens to me you have found the fault because in the decoder used by the same manufacturer it shows the exact coordinates but traccar maps the information and places it as 0, if you have the solution I am willing to pay to give it a solution.

sebacipo3 years ago

Hello David, could you solve it??? I´m having the same problem.

URLEY REY3 years ago

Hello, if anton has solved me, I have made the contribution to the development and it is working well.