TK909 version 2.0
Same as me.
Recently, our development group brought some gps TKSTAR TK909 model because last year we integrated it to our kafka consumer project. We have a server that catches the trackings of those devices (Previously configured with the specified ip and port) and then parse the results to a real time system using the WatchProtocolDecoder protocol from traccar.
But then it happened. New GPS stopped working on our server. It seems that GPS updated the software Version, here I share images of the responses of previous and actual TK909:
This one is the old version that works perfectly reporting right trackings:
https://drive.google.com/file/d/1lQXaOxkbGzog9DCvhchtvrI5iWJZaBZ9/view
This is the answer of new version and as we can see it changed the version from 1.5 to 2.0.
https://drive.google.com/file/d/1SUbDFZyiTpYi5-6zBjeR1k__F2ZYl7-R/view
SMS works perfect in both versions, but version 2 only sends valid trackings to the www.mytkstar.net domain but when we set the ip and port of our server (even when the devices responds ok to configuration) the gps stop sending right data and only recive LK type, that doesn’t work for tracking because don’t contains the lat, long, alt, and another data.
In section 4 of FAQ from the official site (https://www.tk-star.com/TKSTAR-FAQ.html)
they says as next:
“Normally, we have preset the IP and Port on our tracking platform as default .
if you want to track it on others tracking platform, please provide us with your IP and port, then we could help you set IP and port before shipping.”
So, this makes me suspect that new devices version has some kind of validation or secure to restrict data to invalid servers.
I was searching for similar cases and replies on how to make it work. But I didn’t found anything.
Hope someone replies to this.
But you wrote you still receive LK message on your server for v2 tracker when you change the ip through sms ? So it actually sends LK to your server after that but not location data?
This is a Gps Pet tracker?
Since you write that that;
TK909 #2 Sends no valid trackings
Jan 19 13:38:17 p[911]: ID:90986-----*0007*LK,0,38
Jan 19 13:38:17 p[911]: ID:90986-----*0007*LK,0,38
Jan 19 13:38:19 P[911]: ID:90986-----*0007*LK,0,38
Jan 19 13:38:19 p[911]: ID:90986-----*0007*LK,0,38
Jan 19 13:38:20 p[911]: ID:90986-----*0007*LK,0,36
Jan 19 13:38:20 p[911]: ID:90986-----*0007*LK,0,36Is the device online in traccar server because of this link keep data?
If so, what happend when you sent the custom command to the device: CR
Check the log after that. It should send location data for three minutes every 20 seconds. Does it do that?
@Track-trace
Yes. I still receive LK message, but only of that type and it only contains the id(imei) of device, a number, the type LK, 0, and the battery percentage.
I.e. 909-------0007*LK,0,50
What is illogical because on response of sending a Check+pass command we receive the sms with the real position, but in our server just LK type data. Again, if we set the www.mytkstar.net domain and using the TKSTAR GPS app (android/iOS), we manage to see the real time tracking of those gps. Using the same route, same sim card, ensuring devices have gps signal, and so on.
So how about this ?
"If so, what happend when you sent the custom command to the device (through the server console): CR
Check the log after that. It should send location data for three minutes every 20 seconds. Does it do that?"
This is a Gps Pet tracker?
- Yes, is a GPS pet tracker.
Is the device online in traccar server because of this link keep data?
- Yes, i save latitude, longitude, altitude, battery, speed and course.
If so, what happend when you sent the custom command to the device: CR
- Whats the meaning of CR? Is a command?
Check the log after that. It should send location data for three minutes every 20 seconds. Does it do that?
- Yes, the device sends data every 20 seconds, just LK data.
@Track-trace
No, it doesn't.
Of course we turned on the GPRS mode and changed the apn as usually with the other gps TKSTAR TK909. We set configurations as always but new devices only gives us LK data, everyone of them (yes, every 20 seconds)
Do you know if exist some kind of validation to restrict data to invalid servers and only allow right data to the mytkstar server or another valid tracker plataform? ( Gurtam,gpswox,gpsgate,traccar .....)
Is there a way to integrate our ip to the list?
Or, if there is a command to downgrade the software version of the new devices?
Same problem here.
I tested with both TK909 and TK911Pro and immediately after changing IP server and port GPRS light switches from flashing to always on.
If I restore IP server to default mytkstar.net:7700, the GPRS led starts flashing after a few seconds.
APN configuration and GPRS commands return OK everytime.
I've emailed the supplier asking for a solution.
@Scotty07 in the FAQ section 4 it also states that you can use the command "adminip" to change the server...
These devices are now using watch protocol.
The solution is to configure them to use port 5093.
Thats Great, still it sounds strange to me that you would not have received the same position data on another port.
Same problem here. I have TK905 and a smarthome. I would like the tcp packets would be processed by my smarthome.
After changing IP server and port to my public IP address (port is open), the GPRS light switches from flashing to always on. If I restore IP server to default mytkstar.net:7700, the GPRS led starts flashing after a few seconds.
I tried use port 5093 and 5039, but neither helped.
Thanks for your help.
So what do you see exactly in your traccar server log (HEX data) when you point your device to traccar server?
I would like to use own (smarthome) server. I didn't try point my device to traccar server. When I change the ip of device settings, the GPRS light switches from flashing to always on. So I think it is a TK905 issue.
There is no log in your Smarthome?
Hi, I bought two TKSTAR909. Both works right at application, and led blinks on green indicating a right connection. But when I change the devices adminip configuration I got next results on server.
TK909 #1 Works right, sending valid trackings
TK909 #2 Sends no valid trackings
SMS works right, and devices matches to the configurations sended by SMS.
format --> response ok
admin + my phone number --> admin ok
apn + the apn --> apn ok
adminip + ip my server + port -->adminip ok
gprs --> gprs ok
apnuser123456 user —-> apnuser ok
apnpasswd123456 password —-> apnpass ok
check --> It responses and match on body to the APN configurations, IP and port. But on header it responses as next:
TK909 #1
Response: XM_TK909_SM_1.5_2019/09/09
TK909 #2
Response: TK909.MC25_V_2_0_20220617
When I change the TK909 #2 adminip, no matter the device location, led keeps turning on green (with no GPRS signal).
How can I fix this problem, with TK909 device #2, for sending valid tracks as #1? I realize you have different system versions:
#1 1.5 version
#2 2.0 version
How can I turn back 2.0 version to 1.5?
I'm using WatchProtocolDecote. Help!