VT05s not returning any hex information.

I have a vt05s Chinese gps tracker don't have any proper documentation including protocol. I tried the way manual finding the port but it's not working. Does all gps trackers using sockets to transfer data to traccar platform?

Do you have HEX samples? What ports have you tried?

Actually I went through this link

https://www.traccar.org/identify-protocol/

No hex samples or success message in the log file. I tried port 5001.

Then you should probably start with troubleshooting.

I have downloaded traccar locally in my Ubuntu and using the public IP address to the device. Reason may be my country not allowing to use public IP. So trying demo.traccar.org provide me a solution to find me protocol? I mean can you check that?

I setup the device with demo.traccar.org as sever and I tried 5001 5008 as ports
My IMEI of the device : 355139089894379

Can you check for any logs there

Unfortunately we don't provide support for demo servers. If you need assistance, you can try one of our subscriptions.

[b2d53d64: oigo < 89.248.160.150] HEX: 474554202f20485454502f312e310d0a486f73743a207777770d0a0d0a

[f5b75b44: enfora < 122.228.19.79] HEX: 00405000000000855db491280000000000017c9140000000aa39da423765cf010000000000000000000000000000000000000000000000000000000000000000

[0d3d6632: enfora < 175.157.50.218] HEX: 78781101035513908989437900003202002c95cb0d0a

Thanks for your reply Anton. Exactly these are the returns from my VT05s. I don't receive these messages continuously as when I'm using mobile client(OSMAND). For VT05s I only received these three messages.

Enfora and Oigo are listed devices so I changed the port number exactly to 5008 and 5121. But nothing went good.

Any helps to me appreciated.

You have to read this:

https://www.traccar.org/clones/

Ok I will try the link and update here.

Your last sample is GT06 protocol, port 5023.

I tried all 7 ports one by one. I let some time to device to keep update the log files. No updates in my traccar log files.

You are correct login packets from device to server's start bits: 7878. I tried 5023 no changes in the log and I'm using my personal server on AWS Why the log shows "Oigo" too. It's confusing me more.

2020-05-04 02:44:02  INFO: [e595d47c: gl100 < 5.8.18.88] HEX: 0300002f2ae00000000000436f6f6b69653a206d737473686173683d41646d696e697374720d0a0100080003000000
2020-05-04 02:46:02  INFO: [e595d47c] timed out
2020-05-04 02:46:02  INFO: [e595d47c] disconnected
2020-05-04 03:01:16  INFO: [e5439ab0] connected
2020-05-04 03:01:16  INFO: [e5439ab0: flextrack < 5.8.18.88] HEX: 0300002f2ae00000000000436f6f6b69653a206d737473686173683d41646d696e697374720d0a0100080003000000
2020-05-04 03:03:16  INFO: [e5439ab0] timed out
2020-05-04 03:03:16  INFO: [e5439ab0] disconnected

I let the device for a whole day. I got some logs like the above. So far enfora, oigo, flextrack, gl100 are the names I found in the log and I setup the device for listed port number and check for device activation. Nothing happen favor to me.

For VT05s chinse tracker to integrate with traccar.

send server setting SMS as follow SERVER,0,<server name>,1# don't use the format in manual and use 5023 port.

Thank you Anton for the great platform and instance responses.