Do you have protocol documentation or at least some message samples?
Looks like port 5010 is the correct one.
It goes online but does not connect the coordinates to the traccar. No 360gps app working normally. I tested it on the latest traccar version 4.11, 4.12, 4.14. All without GPS coordinates.
Have you checked logs to see if your device is sending any coordinates?
HEX: 5452565950313432313132323856313035312e323138335330333833322e33303332573030302e303134333532383138382e3933313030303039303131303030303130303031342c3732342c31312c3137352c363632322c41524147414f656c6f7c30302d31412d33462d37442d36332d45357c2d37332647616d61414f2e7c41432d38342d43362d31442d41382d33327c2d393123
HEX: 545256595031362c313030303039303131303030313030323030313032303430303030393939393223
You should probably provide some comment.
As I understand it in hexcode does not collect coordinates.
OK, so your device is not sending coordinates.
Yes. It is not sending coordinates on the traccar. On server 360gps app sends normally. Need some information to implement this protocol for future update?
I'm confused. Your device is not sending the data. How is this related to the protocol? What update are you talking about?
The tracker is working normally on the manufacturer's own server. However, when I use traccar on the port 5010 on the server, the device goes online but does not send the coordinates.
If you need to implement an update in traccar for this protocol, inform me an IP that I send the command so that you can check the problem in question.
I bought a GF-21 and it doesn't work on the Topin port... It uses the S1903 protocol on the board. It came online on port 5010. Will it be another port or do you need to update the traccar for a future update to this protocol? The official app is 360gps in command sms domain#47.75.221.215#6100#