bmellink
Not recognized=##
Hi, thanks for your work on this. I have a rebranded TK102. Upon setting everything up, I get
17:55:59 (#15) New connection from xx.xx.xx.xx:52331
17:55:59 (#15) Not recognized=##,imei:864894030xxxxxx,A;
17:56:29 (#15) Remote closed connection
Does this mean that my TK102 is sending the data in a different format? How can I echo out what the server sees?
So I've figured out that this code isn't compatible with TK102 (at least the version I have). I pieced together some info from other gits and with some editing, I think I can get it working.
Btw if anyone searches for the same problem: ## is the initial message that requires a LOAD and ON answer from the server. Then **,imei:864894030xxxxxx,B, which is followed by the tracker sending periodic GPS data.
My guess is that this is how the paid servers distinguish whether you've paid for the service and wither allow communication or block the tracker.
hi. can you share what worked for you please
So I've figured out that this code isn't compatible with TK102 (at least the version I have).
I pieced together some info from other gits and with some editing, I think I can get it working.
Btw if anyone searches for the same problem: ## is the initial message that requires a
LOADandONanswer from the server. Then**,imei:864894030xxxxxx,B, which is followed by the tracker sending periodic GPS data.My guess is that this is how the paid servers distinguish whether you've paid for the service and wither allow communication or block the tracker.
