Lantrix 1700

chuflo326 4 years ago

Hello, I have a Lantrix 1700, it appears offline, I looked at the log and this appears:

HEX: 3e5254543038303232323030303234302d333037363132332d3035383031303539303030313833333030394632313031203034313031303130203031302030303030303030303139303031363331303430313b49443d303030353b23323533303b2a32333c0d0a

Decoder:

>RTT080222000240-3076123-058010590001833009F2101 04101010 010 00000000190016310401;ID=0005;#2530;*23<

From what I read, the protocol is already developed, has anyone experienced something similar?

Anton Tananaev 4 years ago

What port are you using?

chuflo326 4 years ago

I tried with port 5031 and 5001 udp and also tcp

Anton Tananaev 4 years ago

If it doesn't work on the taip port, then it's probably not supported. Probably some changes in the format.

chuflo326 4 years ago

The strange thing is that a while ago I used it with traccar and it worked well for me, but it was some previous versions, I don't remember which one, could something change in the traccar protocols?

Anton Tananaev 4 years ago

We haven't changed this protocol in a long time, so I don't think so.

chuflo326 4 years ago

Hello, here I found a log of a previous server that had:

2017-07-05 10:57:29 DEBUG: [89567A67: 5031 < 181.116.209.44] HEX: 3e5247503034303731373134343932302d333037353239312d30353739383130393030303231303330304446313030323b49443d303030323b23303036413b2a32383c0d0a
2017-07-05 10:57:29 DEBUG: [89567A67: 5031 > 181.116.209.44] HEX: 3e41434b3b23303036413b49443d303030323b2a30303c
2017-07-05 10:57:30 DEBUG: [89567A67: 5031 < 181.116.209.44] HEX: 3e4552524f522044452049442f434845434b53554d3b49443d303030323b23303030323b2a36303c0d0a
2017-07-05 10:57:30  INFO: [89567A67] id: 0002, time: 2017-07-04 11:49:20, lat: -30.75291, lon: -57.98109, speed: 0.0, course: 210.0
chuflo326 4 years ago

there it is working on the UDP 5031 port, I keep you updated to see what happens
Thanks,.