Coban TK-103

eliphas,
please, send your device ID, we will check logs.

It's the only tracker on the account test12960758540, the imei is 353451040220624. It was pointed to wialon (TK103 port) in 17/01, from around 17:05GMT to 17:30GMT, then I changed to TK102 port and waited until around 17:50GMT.

The tracker is configured back to gpstrackerxy now, but I can change it back when it finishes the trip back here today.

I tried setting it as 102 too, changed the tracker type on the site and the port number on the tracker, tested about 15 minutes then changed it back. No messages received on the site...

Yes, I did change the adminip to 77.74.50.78 and port 20222 (tk-103) on the first try, on the second the port was 20157 (tk102).
I did the GPRS123456 and then check123456 to see if gprs status was on, it was.

The auto-track command would be t020s***n123456, but I didn't need to set it on the gpstrackerxy site. And I think this would only send SMS status messages, no? And even if the device is not sending status at a specified interval, it should "ping" the server, appearing as online in the map?

I thought that on GPRS mode the server itself would set the tracker interval - At least this is how it does on the gpstrackerxy site, I don't need to set auto-track by SMS, there is a "track" button there where I set the interval.

On another tought, looking back on the TK102 config page, it lists the auto-track command as required, and seems to need phone number both of the tracker (on the server) and the server (on the tracker, added by the adminsms command I think).

I have just ignored this config steps, as I really need to use GPRS-only tracking. SMS messages are really expensive here (about Us$0.2 each in a prepaid plan), whereas GPRS data (in the amounts needed to track the device) would be orders of magnitude cheaper (less than Us$10 for 50MB/month).

Edit: Looking at the sister gps-trace forum, another guy had problems on the same day, with a original TK-102. Maybe it was just a glitch on the matrix and today all is working fine? Don't know, will test it when the tracker gets back here.

eliphas, 9-18 GMT+02 (EET), support - 8-20.

But if you do not represent a company which is our customer, then, probably, your chances for support here are near zero, especially for this 100 types of firmware/protocol tracker (tk-103). Only GPS-Trace forum can help you.

But if you are our customer, then you may be 100% sure it will work with Wialon, after our engineer will look at it.

eliphas,
please, check private messages

I am facing the same problem with my Coban TK-103A device. How to resolve it?

crabi
maybe your tracker sends speed in knots. we register speed parameter as km/h by default. Check it by conversion speed value from monitornig site to km/h. 1 knot = 1,852 km/h

Hi,

I configured my device as Xexun TK-102, but its still not recieiving and data. The logs are empty. Can someone please check it, my id is test12972567450 and i have only one device.

Regards,
Mukesh

Dear,

I am very interested in your software, we have evaluated some time and it seems perfect, the only drawback is that we continue to have the problem of speed, actual speed is less than the speed recorded in the system, know any way to solve this problem ?, to obtain an affirmative answer could contract the service quickly.

Greetings and thanks

Hello again guys,
I had a busy week and didn't find time to share my findings.
Anyway, I waited without feedback much more than actually trying to do something

The solution for my problem was really just doing everything again and again, then one time it worked (the basic positioning, at least) as the TK-102. I didn't even made tests with the tracker on a vehicle after that.

I just stopped using the Coban and am now testing the original Xexun TK-103-2 (as TK-102 too).

Along these weeks, I received many responses from other people in other forums, and most of them did exactly this, stopped trying to get the Coban work and jumped to other test tracker. We are now testing the TK-103-2... at least it worked fine right on the second try, as a TK-102.

Anyway, I can bet that this Coban GPS-103A I have sends the speed in KNOTS, too. I sniffed some data using the windows server that comes with the tracker and wireshark, before trying Wialon, and the difference was clear in high speeds. The windows server reported the correct velocity in km/h.

There is no setup on the tracker to change this to km/h, at least not in the manual I have.

It looks like that when sending the info via GPRS it sends the raw data it gets from the chip -- the speed of the Coban on my bench was 0.00 only half the time, the other half it was 0.05, 0.11, 0.03, etc... When sending by SMS, it converted and rounds this down to 0.0 km/h, so it is pre-processed when sending by SMS.

The Xexun always gives me 0.0 km/h from both SMS and GPRS when stopped, making me think that it always preprocess the NMEA info that the GPS module spits out.

crabi, yes, please give your user name for trial version.

crabi, please put units online.