| Versions |
  |
|
| Author |
 Topic  |
|
GPSman
76 Posts |
 Posted - 05 mai 2011 : 23:30:46
|
There are already some topics that deal with some problems of TK103 trackers, but this one is dedicated to Xexun TK103-2 trackers. I have recently bought a Xexun TK103-2 directly from Xexun and like to share my experiences with you.
After charging it for 10 hours I attached the GPS and GSM antenna and inserted a SIM card in the SIM tray and pushed it into the tracker. It instantly powered on and found GSM signal in about 10-15 seconds. For comparison I used to have a clone TK102, which unfortunately turned out to have SIM contact problems, and it took minutes to get signal, sometimes even more.
This unit feels much more reliable than what I experienced with a clone TK102. It had 6 GPS satellites fixed in less than half minute, although I tried it in my room, not under clear sky.
When the unit is switched on it always starts up in a so called deactive fortify mode. In this state the unit is flashing around once every second (when there's no GSM signal, it flashes around 2-3 times a second).
I sent begin123456 and it replied with begin ok. I added my phone number as admin number with admin123456 <my phone number> command then called it. It instantly hanged up and changed state to active fortify. In this state the car is protected and the red LED keeps flashing once every 4 seconds. It now detects when ACC is on (via purple wire), or detects when the car alarm sounds for more than 10 seconds (via white wire) or when the car moves more than 500m away from the place where the fortify was activated. When the tracker's red wire connecting it to +12V is cut it also alerts, however this latter happens not only in active fortify mode but in any other modes (tracking, monitoring, deactive fortify) as well.
For testing purposes I have not installed the tracker in a car, but I connected the red and black wires to my PC power supply's +12V and GND.
ACC detection:
In active fortify mode I attached the purple wire to +12V and the tracker instantly sent an SMS containing the coordinates and the word "fortify" after Signal:F.
The manual says that fortify can be activated only when ACC is not detected. Well, I tried that out, but there was no such limitation. In deactive fortify mode I attached the purple wire to +12V and then called the unit and it switched to active fortify mode (blinking once every 4 seconds) then instantly sent an alert SMS.
When I called the device again to deactivate protection, the tracker did not alert if I attached the purple wire to +12V just as I expected.
By the way, I think connecting to driver side's car door is a better idea than to ACC, because then you can receive an alert SMS right when someone opens up your car, not only when the thief manages to power it up :)
Power cutoff detection:
With the unit connected to +12V I switched off my PC (ie. disconnected from power source) and it instantly sent an SMS containing the word "battery" after Signal:F. This worked not only in active fortify mode, but in any modes (tracking/monitoring/deactive fortify).
Car alarm detection:
In active fortify mode I attached the white wire for some 5 seconds to +12V (normally this should be connected to car alarm's siren, so that it "hears" when it sounds) and nothing happened. So far so good.
I attached it then for about 10 seconds and instantly received an SMS containing the word "trigger" after Signal:F.
I have not tested it however if car alarm detection works even in deactive fortify/tracking/moniting mode as well, or only in active fortify mode.
Engine/gasoline cutoff feature:
Now, it needed two tests and a couple of e-mails with belinda at xexun dot com until it finally worked. At first I just connected the relay to the tracker (it has a nice little connector so you don't have to
know which is + and which is GND, but I figured it out the black wire from the relay is + and the white one is GND on the control circuit). I attached a 12V 5W light bulb to the load circuit and of course
powered it with +12V. It nicely lit up. However even if I sent powercar123456 00 or powercar123456 11 it kept glowing. I thought the relay or the tracker must have been wrong. The relay was just fine, because I tried it, so the tracker did not control the relay. I checked the datasheet on hke.cn website, and it turned out that it needs more than 8.4V to operate and since it is a normally closed relay it needs 8.4V to open the load circuit, thus switching off the light bulb. What? The tracker operates on a 3.7V battery, how would it control the relay with 8.4V?
"Let's connect the car battery's +12V to the tracker", I thought then. And yes, this was the solution. It is not mentioned in the manual but the tracker MUST be connected to the car battery in order to
be able to use powercar feature. To make things a little complicated powercar command works exactly the other way round than what is mentioned in the manual.
Actually powercar123456 11 shuts down the car and powercar123456 00 restores power, but this is not what is written in the manual, go check it. I have already told Xexun about this and also that maybe a separate shutdown123456 and powerup123456 command would have been much more straightforward than these commands. Maybe in the next firmware, who knows... :)
Monitor mode:
I activated it with monitor123456 then called the device. External microphone is not so sensitive so you can hardly hear what is said 1 meter away from it.
Tracking mode:
I had to switch to tracker mode with tracker123456 command, because the tracker was in fortify mode by default, so calling it right away would only activate/deactive fortify mode and one would not receive any coordinates.
I also changed the SMS format to maps.google.com link format because I have an internet enabled phone and it is much easier to see where am I that way. I sent smslink123456 for that. You can change it back with smstext123456. It is good to know that SMS format does not only apply to SMSs sent in tracking mode (when the device is called it returns coordinates in an SMS), but also when some event, eg. ACC on is detected and an alert SMS is sent.
SMS coordinates:
I went out for a little ride with the car and tested my TK103-2 and maps.google.com. It sent SMSs in less than 10 seconds after I called it and the coordinates were 5-10m accurate.
GPRS coordinates:
I set up my tracker to work with www.gps-trace.com's servers. I had to use the settings of a Xexun TK102. When I selected TK103 in gps-trace.com, it was unable to get any coordinates. I configured adminip and apn. Since my network operator does not need apn user/pass, I left those unchanged (empty by default). It remains a question however what happens when you set apn user name and password for an operator, but you change SIM card later and you no longer need to have apn user/pass, only apn. These fields cannot be cleared according to the manual, only overwritten, so how can you provide no user/pass? noadminip123456 clears adminip setting only, so GPRS mode is deactivated and coordinates are sent in SMS. But the next time you configure adminip and maybe a new APN, and you no longer want apn user/pass what can you do? Has anyone tried "apnuser123456 " or "apnpasswd123456 " yet?
I forgot to test it, but according to Xexun not only ip address, but a hostname (eg. yourname.dyndns.org) can be provided for adminip, so one no longer has to have static IP address in order to use own tracker server.
After I issued a t005s***n123456 command gps-tracker.com instantly started to show my car's coordinates.
I drove for about 20 minutes, then came home and listed the messages on gps-trace.com and added them to the map. The driving path was very-very accurate with 5 seconds interval. I could even see on the map when I drove on the left or right side of the road. Compared to what a pain in the *** it was to try to configure GPRS on a clone TK102, it just worked on TK103-2 flawlessly.
All in all I am very satisfied with this tracker and I am somewhat angry that I threw 60$ out of the window with a clone TK102 first. I had to pay only a little more for this TK103-2 and it is really worth the money. It not just works, but I think it feels better: this aluminium case painted in black feels much more sturdy. Also the external GPS antenna is really good: it helped to get 6 GPS fixed in about 20 seconds INSIDE my room, about 1,5 meters from the window. For a clone TK102 it sometimes took minutes (especially after first power up) and it was much less accurate.
I hope I helped some of you with my experiences. If you have any questions I am happy to help. What I still need to test is the firmware upgrade and configuring the tracker from PC instead of via SMS. But since my cable did not arrive I could not do it yet.
Does anyone know if I need only a simple USB-mini USB cable for TK103-2 or I need an Y-shaped USB data cable with an embedded USB to RS232 converter chip just like what is used for TK102? Given that I don't have a cable yet all the above testing was done via SMS which cost like 10 euro cent each. Let's just hope I won't have a huge bill :) |
Edited by - GPSman on 06 mai 2011 08:30:23
|
|
|
Ads
|
|
|
GPSman
76 Posts |
Posted - 07 mai 2011 : 22:26:44
|
I am planning to use an own wire harness for this tracker, because I need thinner and much longer wires. Does anyone happen to know what is the name/brand/type of the 2x5 pin connector used on the back of the tracker? It looks similar to a HRB 10-pin connector (http://www.alibaba.com/product-gs/401745629/HRB_3_00mm_0_118_pitch.html), but I am not sure. And half of those contacts are square shaped and half have chipped off corners on one edge. You can see this on page 3 of manual (http://www.xexun.com/Download/20101118162716859375.pdf).
1 2 3 4 5
6 7 8 9 10
On that figure 1, 2, 5, 8 and 9 pins have chipped corners, the others are squares. What connector is this? HRB looks a little different regarding these chipped corners.
UPDATE:
I got info from Belinda, it's a 5557-10AW connector. I think it must be a replica of Molex 5557 dual row 10-pin 4.20mm mini-fit, jr. receptacle. I found this datasheet: http://www.datasheetarchive.com/pdf-datasheets/Datasheets-12/DSA-229113.html
Looking around on molex.com, I found this kit: http://www.molexkits.com/76650-0078. It contains a male and a female connector and crimp type sockets + pins. Of course one might also need a crimp tool to make sure the wires are properly connected (http://www.molex.com/molex/products/datasheet.jsp?part=active/0638190900_APPLICATION_TOOLIN.xml&channel=Pro) and also a wire extraction tool, should one want to remove the wires already attached to a connector (http://www.molex.com/molex/products/datasheet.jsp?part=active/0011030044_APPLICATION_TOOLIN.xml&channel=Pro).
I hope this will be useful for someone later on. It took quite some time to figure it out. |
Edited by - GPSman on 11 mai 2011 21:44:21 |
 |
|
|
krister
Spain
151 Posts |
Posted - 18 juin 2011 : 10:53:59
|
| Very nice review! :) |
|
|
|
Grottenolm
Germany
206 Posts |
Posted - 19 juin 2011 : 13:53:54
|
Thumbs up, nice review ;-)
quote:
Does anyone know if I need only a simple USB-mini USB cable for TK103-2 or I need an Y-shaped USB data cable with an embedded USB to RS232 converter chip just like what is used for TK102?
You need a coverter cable like the cable for the TK102-2, usual USB cable doesnt work ;-) |
|
|
|
GPSman
76 Posts |
Posted - 05 juil. 2011 : 21:54:24
|
@Grottenolm: thanks! In the meanwhile my cable arrived. I tested it with your configuration tool, and it worked very nice. I no longer have to send SMS to configure, I can do it with my PC. Nice!
My latest experiences with TK103-2 is not so nice though, as I found a very annoying bug. To activate car protection, I call the tracker which automatically hangs up. This acknowledges that the tracker went into protection mode (+12V is detected on purple wire - eg. engine is started - it sends an alert SMS).
Then I leave the car for a couple of days. Before getting in the car, I call the tracker again to deactivate the protection. It hangs up as usual. But when I start the engine it sends an alert SMS, although I deactivated it!
When I don't wait a few days, only 1-2 hours before I use the car again, then it deactivates the protection normally.
At first I thought this is my mistake, because I thought after an alert SMS comes, it is enough to call the device to deactivate protection, and call it once again to activate it.
But actually, first a "fortify123456" needs to be sent to "acknowledge" the fact that it sent an alert, and only after that can I call the tracker to deactivate protection.
If after an alert I just call to deactivate, and later on call to activate again, it will not notify me about alerts, because I have not sent a fortify123456 SMS yet to acknowledge the previous alert. At least this is what I figured out, I still need to clear this up with Xexun.
Have anyone else come across this "false alert in deactivated mode" bug yet? I have already wrote an e-mail to Belinda, I hope she can help me with this. Actually this bug pretty frequently gives false alarms, that costs me money, and is also annoying when I start the car, and it alerts me while I am in a hurry. If I don't deactivate it (SMS + call), then it keeps alerting every 3 minutes or so. Which is OK, but only when the car is really stolen, not when I want to use it.
Also I feel it would be much better if the tracker could notify me when protection is activated and when it is deactivated. Of course there is this "fortified123456" SMS, but it is not convenient and costs 2 SMS (command+reply SMS). It would be much better if the tracker hanged up right away (just like it does now) when protection is deactivated, and hangs up after 4 calling tones when protection is activated. Maybe sometime, in a later firmware... If only I was able to write my own software for these units :)
UPDATE:
Belinda confirmed the tracker has a watchdog circuit that restarts the CPU when the software freezes. Once the tracker restarts it always enters fortify mode with deactivated protection.
I think this might be the case: although I activated protection, after a couple of hours/maybe days, it restarts because of some bug. The protection now gets deactivated. When I want to drive my car, I think it is still in active fortifying mode, but in fact the protection has already got deactivated. So when I call to deactivate it, it actually gets activated (just the opposite what the user would expect). Since there is no way to know if a call activates or deactivates protection, if I start the car it might happen that it sends alert SMS, because it has actually just entered active fortifying mode as commanded by my "deactivatation call".
I suggested Xexun to save the last used state in memory. So when the device gets reseted for any reason, it can return to the previously saved state. Let it be active fortifying mode, or even live GPRS tracking. After bootup it should continue sending coordinates or continue protecting the car.
Of course the best would be if the tracker did not restart at all. But its still better if it restarts, then at least it continues to work like before.
Let's see if they can fix this. I am waiting for an answer, and a new firmware... |
Edited by - GPSman on 06 juil. 2011 11:38:47 |
|
|
|
riosjosl
1 Posts |
Posted - 09 juil. 2011 : 18:14:13
|
Hi my friend, i buy this GPS traker, but i have problem. When i sent begin123456, this tracker dont respond me, but i call and this sent me the coordinates, i send the command t030s005n123456 and respond me, but then of 10 hours I call again and the tracker dont respond me, i sent the command t030s005n123456 and nothing. This is like off. I reset and out the chip and then insert the chip again, but i have the self problem. What can happen whit this tracker, is bad? or a I worked bad?
Please help me....thank soo much.... |
|
|
|
Grottenolm
Germany
206 Posts |
Posted - 10 juil. 2011 : 23:31:26
|
The easiest solution is to send a format command to the tracker.
If this command fails by sms try my tool by cable. |
|
|
|
GPSman
76 Posts |
Posted - 11 juil. 2011 : 16:44:04
|
@riosjosl: you may want to check if this is a Xexun original device. Check the IMEI number: imei123456. Of course you must have a unit first, that is responding to your SMSs. Try removing the battery and SIM card, then readd them. If you have a cloned device, it may happen that the SIM connector has contact problems. Try to push it a little bit.
If you have the IMEI number type it in on www.xexun.com's top left corner and you'll find out if it is a Xexun or a clone.
By the way I never experienced anyhing like this with my tracker, but I had the same experience with a cloned TK102. Where did you buy the tracker from? Can't you get a refund? |
Edited by - GPSman on 11 juil. 2011 16:51:20 |
|
|
|
RC200
70 Posts |
Posted - 09 août 2011 : 17:25:30
|
TK103-2 has nice features but misses some points ... it has no external inputs to enter/leave fortify mode (I would call it arm/disarm mode). This is just painful to send sms each time you park the car.
This is for me a major drawback.
It seems TK103-2 is ARM based and not STC based, more standby time .... bla bla bla ... read here:
We have two versions of our gps tracker TK103,the old STC solution and the new ARM7 solution. Now,we are main pushing our new version TK103-2 due to there are many cloned ones in the market,what’s more,instead of the old TK103,TK103-2 improves on the previous version in terms of stability,speed, software,etc.
TK103-2 with all the features which the old TK103 has, besides these, the following features are all available:
1. The minimum interval for data sending of TK103 is 30 seconds, for the new ARM7 solution, it can be 5 seconds.
http://ningmore.com/products/gps-tracker/2011_03_07_28.html
GPSman, could you confirm YOUR TK103-2 is not STC microcontroller based ?
Could you confirm the standby time ?
Personnally, I ordered the GPS103-B. Not sure if the manufacturer is Coban. There're so many similar part numbers ...
This unit has less features (or at least not so well thought compared to Xexun TK103-2) but it has external remote to enter arm/disarm state !
I started to dissect the product. Here are the results:
GPS103-B:
STC based (don't care)
Standby is announced for 48h, I cannot believe it (-)
I measured about 80-90mA drawn on 12V, GSM attched, GPS attached, doing nothing
Siren wire is output only, meaning it cannot detect your OEM alarm siren going off (but I plan to connect my OEM alarm siren output to ACC input wire)
External remote to enter ARM/DISARM state
==> the unit has additionnal remote controller chip on small extension board (part # is XXXX, tbc later)
Header pins are VT D3 D2 D1 D0 VCC GND
VCC is 5V
Press A (ARM) on remote shows 5V on D0 and VT (default is low level)
Press B (DISARM) on remote shows 5V on D1 and VT (default is low level)
I noticed something interesting, when pressing B in SOS mode, the unit stops sending you "help me!" (otherwise the unit keeps sending "help me!" every 3-5 mins, very ennoying at the end). This is particularly useful if you couple this to your OEM car alarm ... but if the siren was triggered just before pressing B, the siren will finish its 30s cycle (painful) (but will not start again in 3mins).
Only D0 and D1 are wired to STC through NPN transistors (pins X and Y on STC, tbc later). STC is triggered on falling edges/low level then.
It means you can couple your car alarm to the unit. Most aftermarket alarms have factory arm/disarm outputs with ground pulse when arming/disarming. This is my next step.
GPS module is unknown (I don't care)
GSM/GPRS module is SIMCOM 900B (as listed below)
Classical usb cable for TK102 family works but I don't manage to send AT commands yet (some help needed here)
I got this on short cable on boot @19200 bauds (it seems to be the default fixed baudrate then):
þþþþ (i.e. 0x49 0x49 0x49 0x49 0xFF 0xFF 0xFF 0xFF)
RDY
+CPIN: NOT INSERTED
+CFUN: 1
+CREG: 2
+CREG: 0
AT+GMM
SIMCOM_SIM900B
OK
AT+CGSN
35345xxxxxxxxx
OK
Strangely, IMEI doesn't start with 012... but it is SIMCOM 900B module though ...
When connected with long cable, I only see AT+GMM and AT+CPOWD commands being output continuously ...
SIMCOM 900B module is PNX4851 NXP baseband chipset based.
My assumptions is short cable corresponds to debug serial port of PNX and long cable to normal serial port. I got no answer neither on long cable when sending AT command.
Grottenolm, your config tool of course doesn't work, at least b/c of the uart speed (I read somewhere TKxxx uses 57600 by default, right ?).
I don't know how your config tool interacts with the tracker, do you use AT commands, which ones ? Is it documented somewhere ?
I will keep you informed of my progress with GPS103-2 b/c I found out there's not so much information on this tracker (some people thinking it's the same than TK103(-2) but it's not)
FYI, GPS103-2 doesn't support the following sms commands (non exhaustive):
format, apnuser, apnpassword, fortify
My application (that may give some ideas):
_Car
_Tracker must be wired to my OEM car alarm in some way (only one remote in my pocket, no additional SMS to send)
_ACC input (white) wired to OEM alarm siren output
_Sensor input wired to OEM alarm radar sensor
_Reset input (ground pulse) wired to nothing (or maybe to OEM alarm disarm pulse, to be sure to have a default state when opening the car, but reset microcontroller doesn't leave the ARM state, I tested it ... then not so useful)
_SOS input (ground 3s) wired to a hidden switch
_Door input (blue or green) wired to doors, trunk and hood with diodes
_Relay output (yellow) wired to fuel cut relay AND windows roll-up module input (double role in my case)
_Siren output (orange) wired to a siren inside the car only
Overall, the GPS103-B behaves as described, here is the list of bugs found, to be completed:
1) the manual describes:
6.7.4 If you want to track the target tracker device when it enters into another country, you must add the country code before the cell phone number, for example, send SMS” admin123456 008613322221111” to the device. Note: 13322221111 will be set up as the authorized number.
==> when sitting in my country, 0645XXXXXX works as an admin number but 0033645XXXXXX doesn't !! I pretty sure this is b/c the network presents the full number when calling the unit (i.e. 0645XXXXXX) and the traacker simply compares it to the number recorded .... 0645XXXXXX <> 0033645XXXXXX . That's a pitty, if confirmed, it means I have to change the admin number to 0033645XXXXXX each time I will be abroad !!
2) end of list
|
Edited by - RC200 on 09 août 2011 18:19:37 |
|
|
|
GPSman
76 Posts |
Posted - 12 août 2011 : 22:21:43
|
@RC200: Xexun TK103-2 does not have external arm/disarm function indeed. But you can call the device in armed (fortyifying) mode, and it will instantly disconnect and go to disarmed (no fortify) mode. This does not cost any money.
It is ARM7 based, actually it has an LPC2134 microcontroller. I usually have it attached to my car battery, but I think the battery lasts maybe 30-35 hours. At least I received a low battery SMS after just 12 hours, and it reported battery is below 3,7V. When attached to car battery and fully charged it used to report 4,28V. I think it has a 3,7V, 1100mAh battery.
Anyways my problem is still that the tracker does not always leave armed mode when calling. Actually calling it changes mode to and from armed and disarmed mode. When the tracker is hidden and you can't see the LED flashing you have no way to know whether it is in armed or disarmed mode.
Normally of course it should be in disarmed state, and when you call it, it goes to armed state, so the next time you want to use the car you just call it so you will know it is disarmed. However, sometimes it is not. So when I start the car, I soon get an SMS. When this happens, I have to send "fortify<password>" in SMS, then call the tracker to leave fortifying mode (disarm it). This is very annoying, as this takes another minute before I can start, and I still have to send a "fortified<password>" to learn the current arm/disarm status just to make sure it is really disarmed. So it costs 4 SMS (2 sent, 2 received) to actually disarm the car properly. Normally it should not cost anything, because calling and hanging it up instantly is free of charge.
Unfortunately Xexun did not admit having this bug, actually they told me they never received a problem report of this kind, although they said they had a lot of customers. Well, it may be only me using it for protecting my car. The GPRS tracking mode works OK by the way, and I think most customers use it for tracking only.
It would be pretty good to have the Xexun firmware source code, or a third party open source code, so that I could finally fix this annoying problem, if Xexun is not willing to... |
Edited by - GPSman on 12 août 2011 22:34:07 |
|
|
|
RC200
70 Posts |
|
|
GPSman
76 Posts |
Posted - 24 août 2011 : 14:59:26
|
It looks very similar to a Xexun TK103-2, but it has a couple of extra features as well. Eg. status LED is not built in, but connected via a wire. Mine has a built-in LED which is useless, when it is well hidden in the car.
It also has external shake sensor, while TK103-2 has only built-in one(?) I could not make it work yet, probably it is just supported by the firmware, but not by the hardware.
Also yours have two, a (+) and a (-) door trigger, mine has only (+) trigger for ACC detection. So I had to build a small (+)->(-) converter (basically a reed relay + some diodes) so now I can have (+) and (-) triggers as well, and both are connected to my tracker's (+) trigger. So whenever a door is opened, it will alert, just like when ACC is detected.
Battery switch is also a neat idea. When I want to disable protection for a while (eg. it is in a car service and battery will be disconnected), I have to remove the battery completely to prevent discharging completely. Otherwise I would get a lot of SMSs whenever the car battery is disconnected. Okay, I can live with this. |
|
|
|
GPSman
76 Posts |
Posted - 25 sept. 2011 : 22:15:49
|
Meanwhile I have received a new firmware from Xexun for the TK103-2 tracker. I uploaded it, but it won't fix the problem I have: after a few hours, maybe a few days the tracker resets itself and forgets that it was in armed state.
Since I am not even notified about this, not only can anyone steal the car without me noticing it, but the next time I want to use my car and I call the tracker, it activates protection instead of deactivating it, so it will send an alarm SMS when I start the car. I have to spend a few minutes sending a deactivation SMS, then calling the tracker to actually really deactivate protection, then I still need to make sure it is really deactivated (sometimes it happened that it was not), so I send a query SMS to get the status of the tracker whethet it is in armed or disarmed state.
Since it looks like Xexun does not even want to admit that they have this software bug (they told me they have never received any reports about it, although they have quite a few customers), I will have to look for a more reliable tracker.
GPS103-B looks better, at least it has a remote controller to arm/disarm, and as you said even if the microcontroller resets it returns to the previous state. So it wouldn't forget to protect the car, which is a major problem with TK103-2.
However disarming it with a phone call would be even better for me, because I cannot attach it to my car's alarm, so I would have to carry 2 remote controllers. |
|
|
|
Cid
Brazil
1 Posts |
Posted - 30 sept. 2011 : 23:48:36
|
| I had some little problems with the TK103 and decided to use the command RESET123456. Bad idea. I thought it would return the unit to default settings. But I think that I format it, because now it does not return to any SMS command. How can I reinstall the firmware? I see that there are USB cables to connect the computer to the TK103, however my TK has no USB output. Please help me. |
|
|
|
tiru
4 Posts |
Posted - 01 nov. 2011 : 12:13:18
|
HELLO GPSMan,
I saw your email online and thought you could help me with this question. I have TK102 and TK103 devices and used them well. They work great however if I lose battery power, the devices are loosing the configuration data especially update interval tn command.
For example:
1) Power on the device
2) Configure GPRS settings
3) send gps location update command t060s***n
4) works great and sends gps locations every 60 secs
5) Power down the device
6) wait for 1 hr or 2 hrs
7) Power up
8) Expectation is that device will connect to the server and sends GPS coordinates every 60 secs. The noticed behavior was that, it connects to the server and the keep alive command ( remembers gprs configuration) and server configuration details but never sends GPS details. To fix it, I had to resend the t060s***n command again.
The question is, is this expected behavior or am I missing something. Without this fix, device is pretty much useless. We can NOT deploy in commercial space.
Please let me know, if you have tested the above scenario.
We are in tracking business and looking for good trackers.
|
|
|
|
GPSman
76 Posts |
Posted - 02 nov. 2011 : 17:02:44
|
@tiru: I believe you are right. I could not test this scenario as I usually use it for SMS tracking (as a car antitheft) device, and since it is well hidden in the car I can only remove and reinsert the battery if I disassemble some parts of the car. However based on my experience with the arm/disarm states (or so called fortify and no fortifying modes) if the tracker gets reseted for any reason, and this includes battery outage, the tracker enters default mode, which is no fortifying, so when the internal battery is depleted (eg. disconnected from the car's battery for more than 24 hours) it forgets to protect the car after starting up.
In a similar way I can imagine it also forgets the last received SMS command, so it won't start sending coordinates after startup.
However I think there is a workaround: when your server detects that coordinates are not sent, it may start requesting coordinates on its own. Alternatively you should not even use the tn command, but the server should request one coordinate at a time (tn030s001n123456) every 30 seconds or at any interval you need.
As an other option if you order a lot of tracker from Xexun, you can even ask for a custom firmware that enables your trackers to start sending coordinates right after startup. The server side solution seems to be better though, and I prefer sending a tn030s***n123456 packet whenever the server detects a tracker is not sending anything. |
|
|
|
Topic |
|
|
|
| This page was generated in 1,11 seconds. |
 |
|
- 
- 
Xexun TK103-2 experiences
