New account creation is currently unavailable. Existing members can continue reading and joining discussions.
Pages 1
I too was looking for the tracker/camera combo and looks like the MVT600 is gold. The possibility of using the LCD screen to send messages to the driver is a good bonus.
Anyone has experience with this tracker on wialon? Looks like there is only 10 in the database.
Hello all,
I am testing Meitrack's VT310 digital I/O pins, it has 5 inputs and 5 outputs.
I already have made the inputs read and configured them right, and can see the changes in the report (added in1...in5).
Wialon does not like the info when the alarm is activated, I followed up in another post that I think is the same problem here:
VT310 Veer Report Problem
Anyway, here is the question for this own post:
The device sends info about the outputs too, but I can't understand how to "get" that info on Wialon. I would like to know the state of the 5 outputs, like I know of the 5 inputs. I tried adding
The info is sent in the same parameter from the tracker, as the protocol documentation says:
XXXX in HEX, representing eight inputs and eight outputs:
0001 - first output is on
0102 - first input is on, second output is on
I activated OUT2 on wialon (I can see the 0002 being sent from the COM console), but don't know how to get this info on the message report.
Tried:
out1-out8 (all of them displays as "---" in the messages input report)
IN1-IN10 (maybe after IN1-IN8, the IN9 and IN10 would be the first two "outs".
On the raw messages report, I get "I/O=0/0" when input1 is off, "I/O=1/0" when input1 is on, but no mention of the output.
+1 for having the input sensors on VT310 supported.
Maybe the outputs and GPRS commands too? 
The protocol is very well documented, PDF at:
http://www.meitrack.net/support/protocols
The good thing is if you implement the support for one model, you support all of meitrack's models.
(we are thinking of using other models, very satisfied with VT310)
Edit:
My bad, I just was not using the thing right. Looks like the IN1 and IN2 work, at least. will test the others 
Edit2:
Now I can read inputs 1 to 5, happy!
But like anibalfv reported for the heading change "alert", wialon does not accept the packet when the inputs are activated, only when they are reported by the timed interval. This is what I see in MyCOM:
Interval, with INPUT1 activated:
$$ }5 1 I U195006.000,V,2231.4673,S,04406.9321,W,0.00,0,070711,,*1F|0.0|357|0100|000E,000B|02D40002007C8E8B|07|000002FC
Alarm, *when* INPUT1 is activated:
$$ ~5 1 I 195201.000,V,2231.4673,S,04406.9321,W,0.00,0,070711,,*1A|0.0|357|0100|000E,000B|02D40002007C8E8B|07|000002FCA
anibalfv, did you solded your problem with the manufacturer? Any good news? I think this is the same problem, but I am not as good in "decrypting" this protocol as you guys
If any other copy/paste or testing needed just ask!
Superb, thank you very much shal!
My regards
--
Eliphas
Hello shal!
You mean you want to have only points visible, without track?
Yes, just the points. When there are many points in a tiny location the track lines do not help much, only add to the clutter. And when the interval between two points are far apart (like when the GPS signal is lost for some minutes), the straight lines from a point to another gives the impression that the tracker just headed straight to that other location, which does not make sense.
To implement this we need some more people asking for the same feature. They can post in this thread.
/me wishes that more people need this
(Igor from Help System told me to make this request here)
Sometimes when the GPS/GSM signal is lost for some minutes, the track lines cause more problems than it helps in visualizing the current locations (like, signal is lost before going from one side of a river to the other, then a straight line to the new location a couple of minutes later, very far from the bridge heh)
Likewise, when the vehicle goes around circling a small place/area various times, the image gets overloaded with a lot of lines.
I would like to request the inclusion of an option to make the line thinner (1px) and hide (0px?) the track between the points on the "Tracks" menu, where you can select an interval and color and pixel size, making the map show only the dots with the coordinates received.
I changed the pixel size to 1px (with firebug help), it worked -- and the thinner line is much more pleasing on the "small area circling" episodes -- why we have only 3px minimum? Sadly, changing that to zero did not work, so it seems that you will need to make a little change in the backend too.
Could you forward to the devs this request and tell if it can be done?
Here is a mashup I made to illustrate what an "invisible" line looks like
http://dl.dropbox.com/u/552/WialonHiddenTrack.png
Cheers,
--
Eliphas
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.
Thanks bako, message replied.
Will update this thread with our results
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.
Thanks for the fast and really-to-the-point reply, shal.
Well, technically I am not a customer. My employer now have the task to find, configure, and support a cost-effective GPS tracking device and nice website tracker for a customer. I am in the process of finding, evaluating, and selecting the best trackers and systems for that (was made aware that cost is very important, so any "pro" trackers are automatically out of the table). By the availability, import taxes, freight, the GPS103 from Coban or the "real" TK-103 from Xexun are the most likely candidates so far -- and I am still waiting for the Xexun to come.
I browsed your website, used the demo account, liked the system, requested a quote for 50 units (Anton Hamalinski - Gurtam Sales, was very fast on the subject!).
My company liked the pricing range and sent me on to verify real compatibility issues with the trackers we have in mind.
So, I got to the site and created the fully functional 30-day trial account, like Mr. Anton kindly pointed me to do, and here I am, trying to see if this tracker will work with the system, like I was commanded to.
Would this at least make me a "pre-customer", with maybe 50% sure chances of tracker working? At least trying? I need to get a leap of faith from support
Anyway, now is 16:20 localtime (20:20 GMT+2), so... I will wait.
will test it when the tracker gets back here.
I now have the tracker in the bench, GPRS connected, gpstrackerxy.com still fine. Still no luck seeing it online in the wialon map, or even a status on the log report. Tried with the 20222 tk-103 port and 20157 tk-102 port numbers.
I think the protocols are not really the same; on gpstrackerxy.com it blinks the LED at regular 2 seconds (meaning all right) all the time. Check command will result on GPRS:ON.
On wialon, it regularly (about a minute or so) switchs between the 2 secs and the 1 sec blink (meaning some problem), then again and again. If I "check" when the tracker is on the 1 sec blink, it responds with GPRS:OFF, otherwise, GPRS:ON.
At which time (please include GMT time zone) I am more likely to get a more real time chat with gurtam members, so we can see what could be the problem? I could wake up earlier or get to sleep later
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,
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 think that the problem is the coban T103 have un imei of 15 digits and the xexun t103 permit an imei of 12 digit
I resolve the problem, settings me device like xexun t102 ( you must use the server for t102 device) and work fine,but can´t stop the car.
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...
Hello there,
I have a Coban TK-103 on field test right now, and it is working very well for my needs. The plan is getting about 50 of these set up for a customer.
Was trying to setup tracking on the free trial, but my device unfortunately is not listed. I was hoping that it would work as the other "compatible" (clone/original) tracker, Xexun TK-103, but I couldn't make the server receive any info about the tracker.
Configured it as TK-103 and even TK-102 on the unit's properties to no avail. No tracking info was received on the site, from what I can see. (Testing account is test12960758540 , if you guys can see some debug info from there)
Will I have to stay with the basic ugly gpstrackerxy.com site or can I still count on Wialon? REALLY like the features here
Pages 1
