HELP! how do I connect my GPS Tracker TK-102b

BetoBauducco

Hello! I have a GPS of Chinese origin that I could previously configure on the web, but now I can’t. Tried the guides provided on the page but failed to do so.

The gps is the GPS Tracker TK-102b, could someone help me? It does not appear in the configuration models. GPS works correctly with commands. Previously with the Orange server it used to work very well

Just in case I leave a photograph with the model. !

rost

Hello, BetoBauducco ,

Let’s get it in order.

Model 102-b is not directly integrated into the application, however, most likely, it can be used under a different type of device in the application, since there are a lot of copies of such a tracker.

To find out which type to use, use the guide below:
Since trackers of different manufacturers and models work according to different protocols, it is difficult to say for sure whether your tracker corresponds to one of the protocols we support.
Please try to identify your tracker on id.wialon.net as one of the Concox, Coban or Xexun devices.
If your tracker is determined, take a screenshot, write down the name of the model of the tracker and the identified ID (may coincide with the IMEI, may be part of it with zero or without).
After that, return to the application.

Then, knowing your device type and exact ID, create a unit on the system. – https://help.gurtam.space/en/article/configuring-and-deleting-a-unit
After creation, you will get a IP and a port to which you want to direct the device.
Also, these IP and port can be found in the Сommon settings of the created unit. – https://help.gurtam.space/en/article/configuring-and-deleting-a-unit
Configure your device to this IP and port.

This way, when your device starts sending data to the system, you will see your tracker on the map.

If you have any problems or questions during the setup process, write to us at support@gps-trace.com, indicating the login, unit ID and device type with a link to this forum topic, we will try to help.

rost

BetoBauducco,
You can start identifying your device from the Xexun tk 102-2 device, most likely this is the correct model.

papo

rost identify your tracker on id.wialon.net

please revise this advice. I saw it multiple times on your forum.
It is a service for finding tracker’s IMEI/ID.
You need to setup your device with different port for different tracker model.
How would this help?

It can not be used to identify the protocol. You would need to keep trying changing port until you’ll see your device in the list. I find it even more difficult and uncertain than to keep trying different models/types directly in gps-trace interface.
Specially when someone is paying two SMS costs to change a server and get an SMS reply.

e.g. In this case, you might suspect it’s a clone of Xexun, you would need to keep changing tracker configuration using SMS, trying these ports:

device          port
Xexun TK-102	20157
Xexun TK102-2	20668
Xexun TK-103	20222
Xexun TK103-2	20462

But if you don’t know at all what it is, look at the port assignation page how many ports you’ll need to try. scroll down it keeps expanding: https://gurtam.com/en/all-hw

Why don’t you create a id-protocol site for this?
To ID my protocol, I used regex on the sourcecode at https://github.com/traccar/traccar/blob/master/src/test/java/org/traccar/protocol

Also on your page, the link: “(see devices/ports list)” points to http://gurtam.com/en/gps-hardware
but it should point to: https://gurtam.com/en/all-hw

BetoBauducco

Thanks for your quick response. I added the tracker under the Xexun tk 102-2 settings. As I used the Xexux protocol I added 2 units, one with the full ID according to the IMEI and another with 0 + the last 11 digits.

So far I can’t get it to work.

Next I leave the specifications uncertain in my device:
1) HOST: 12741.flespi.gw
2) IP PORT: 26731
3) TIME ZONE: UTC 0
4) ID: IMEI: 355488020121590 or 0 + 11 for Xexun protocols: 088020121590
5) IP TRACKER: 193.193.165.37

I still have the doubt whether the IP of the device should I modify it and in that case what it should be or leave it as is.

I would appreciate if you can help me. Thanks

rost

Hello, BetoBauducco ,

First of all try to use IP instead of DNS.
You can find IP to direct your device in unit’s Common settings.
More info here. – https://help.gurtam.space/en/article/configuring-and-deleting-a-unit

By the way, its better to identify your device on id.wialon.net firstly and then use ID and device type identified there. Also try to do this, guide is in my first reply.

Then please write us about the results!

ashe

BetoBauducco Hello!
Were you able to connect the device?
If not, please check additionally the APN settings of the tracker and that there is enough money on the SIM card that you use with the tracker.
You can configure the tracker for debugging on server 193.193.165.37 and port 29355. We will see what data the tracker sends.
You can also write in more detail about the problem at suppot@gps-trace.com.

papo

Actually, your TK-102B, as showed in the picture in original post, a Chinese clone of another Chinese tracker,
uses based on my experience TK-103 protocol. I have two of them bought 2 years apart, SMS commands and replies differ, but both use TK-103.
This clone usually does not have the bump on the bottom and it does have SD card slot instead of a flash chip.

With wrong protocol, you’ll see in gps-trace.com > Toolbox a log: disconnected with error
Then when you’ll go to traffic in the Toolbox, you’ll see received data from tracker.
If the tracker uses TK-103 protocol, data starts with: (0 and ends either in ,00000000L00000000) for position message, or with text HSO near the end for a heartbeat message.
e.g. (01234567891BR00123456A1234.6419N01234.0342E000.0143053000.00,00000000L00000000)
e.g. (012345678914BP00HSO)
e.g. (012345678913BP00123456789123456HSOP5A)
such is definitely TK-103 protocol
More examples of valid TK-103: https://github.com/traccar/traccar/blob/master/src/test/java/org/traccar/protocol/Tk103ProtocolDecoderTest.java

and if it’s too different and you are familiar with regex, search parent dir of above link for correct protocol

rost

Hello, papo .

Yes, you understood everything correctly, we advise you to sort through the devices until the device appears in the list. At the moment, this is the only possible option.

As for the resource that could recognize the protocol that needs to be used, we have developments on this issue and such a resource was almost ready, but we refused to release it for a while. We will soon return to the implementation and soon such a tool will appear.

Thank you for noticing!