Maybe it expects some message acknowledgement from the server? Do you have protocol documentation?
I found a protocol description here:
https://drive.google.com/file/d/0Bw13bQgIGLTaSkEzTFJlZjNaWVk/view?pref=2&pli=1
What protocol are you using for those devices?
I use port 5013 if you mean that.
it is h02 in device list.
I don't see anything about confirmation in the document. It's either not required (then the problem is on the device side), or the document is not complete.
The problem was on device side. After many restarts and sending commend nosleep123456 the trackers now work permanently.
Hello,
has anyone experience with the trackers LK 106 and 109 from TK Star?
I have these and technically they work well with the platform. But both trackers turn off after a short time by themselves. I already tried to change the working mode with
Command: sleep123456off Response: sleep ok
and also with
Command: nosleep123456 Response: no sleep ok
But none of these commands changed the behaviour. Maybe one of you know this problem and hopefully the solution.