1

Meitrack VT310

Topic: Meitrack VT310

Wow! My vehicle 'flied' 16420km in 1 hour & jumped from Bangladesh to Colombia!! My bad luck… I was in the vehicle  sad .

Let’s go seriously now…

See data below. Up to 20:01 today, it was at Dhaka, BD; but at 21:02, I discovered it at some place in Columbia. And till now (23:30) it’s there.

How it is happening? Am I getting data of another vehicle there in Columbia?

Note that I am testing Wialon through ‘Free trial’ with VT310. The device has been configured to send data every 10 seconds & goes ‘sleep’ when stationary for 1 hour. Device ‘Unique ID’ is 000001 & ‘Phone number’ is +8801746567154.

3957    20:00:21    0    23.739343, 90.379585    Road 2, Dhaka, BD    hdop=1, adc1=4, adc2=2, I/O=4/0
3958    20:00:31    0    23.739343, 90.379585    Road 2, Dhaka, BD    hdop=1, adc1=4, adc2=2, I/O=4/0
3959    20:00:42    0    23.739343, 90.379585    Road 2, Dhaka, BD    hdop=1, adc1=4, adc2=2, I/O=4/0
3960    20:00:52    0    23.739343, 90.379585    Road 2, Dhaka, BD    hdop=1, adc1=4, adc2=2, I/O=4/0
3961    20:01:02    0    23.739343, 90.379585    Road 2, Dhaka, BD    hdop=1, adc1=4, adc2=2, I/O=4/0
3962    20:01:12    0    23.739343, 90.379585    Road 2, Dhaka, BD    hdop=1, adc1=3, adc2=2, I/O=4/0
3963    21:02:14    ---    ---    ---    adc1=4
3964    21:02:45    0    4.88157, -74.030695        hdop=1.1, adc1=2, adc2=2, I/O=2/0
3965    21:03:15    0    4.88157, -74.030695        hdop=1.1, adc1=3, adc2=2, I/O=2/0
3966    21:03:46    0    4.88157, -74.030695        hdop=0.9, adc1=2, adc2=2, I/O=2/0
3967    21:04:16    0    4.88157, -74.030695        hdop=0.9, adc1=2, adc2=2, I/O=2/0
3968    21:04:46    0    4.88157, -74.030695        hdop=0.9, adc1=1, adc2=2, I/O=2/0
3969    21:05:58    0    4.88157, -74.030695        hdop=0.8, adc1=2, adc2=2
3970    21:06:02    0    4.88157, -74.030695        hdop=0.8, adc1=2, adc2=2

We are already in process of getting ‘Wialon Hosting’ & ordered for more tracking devices. In this stage I am simply worried with this experience.

Please help!!

2

Meitrack VT310

Re: Meitrack VT310

Maruf, currently 273 units are equipped with this device. This amount is usually rather low for such a cheap device, but still not very low to catch some stats.

First thing to do is to ensure that device itself works fine, by requesting its state through SMS.
If coordinates are wrong, just reboot it and/or ask your supplier to check the device.

If they are OK it may be so that firmware of your device sending data in unusual format, then our support team can check the problem in more details.

At the dark side of telematics...
3

Meitrack VT310

Re: Meitrack VT310

shal,

I’ve investigated the issue & want to share some facts in hope it will assist you to find out the root of the problem.

The vehicle ignition has been turned OFF at 23/08/2010 19:01. (see below)

REG    1282568458    23/08/2010 19:00:58    90.3795700073    23.7391466777    0    0    ALT:0.0,hdop:1.1,adc1:2.0,adc2:2.0    in2:1,in3:1,in4:1,,SATS:255
REG    1282568468    23/08/2010 19:01:08    90.3795700073    23.7391466777    0    0    ALT:0.0,hdop:1.0,adc1:2.0,adc2:2.0    in3:1,in4:1,,SATS:255
REG    1282568478    23/08/2010 19:01:18    90.3795283318    23.7392883301    0    0    ALT:0.0,hdop:1.0,adc1:2.0,adc2:2.0    in3:1,in4:1,,SATS:255
REG    1282568488    23/08/2010 19:01:28    90.3795283318    23.7392883301    0    0    ALT:0.0,hdop:1.0,adc1:2.0,adc2:2.0    in3:1,,SATS:255
REG    1282568498    23/08/2010 19:01:38    90.3795283318    23.7392883301    0    0    ALT:0.0,hdop:1.2,adc1:2.0,adc2:2.0    in3:1,,SATS:255
REG    1282568508    23/08/2010 19:01:48    90.3795283318    23.7392883301    0    0    ALT:0.0,hdop:1.2,adc1:2.0,adc2:2.0    in3:1,,SATS:255

Note that,
‘in1’ connected to ‘SOS switch’
‘in2’ connected to ‘door sensor’
‘in4’ connected to ‘ignition’
‘in3’ is used for special purpose & generally always ON.

Accordingly the device went to sleep mode after 1 hour at 23/08/2010 20:01, & stopped sending data. The locations before going to ‘sleep’ are okay. (see below)

REG    1282572052    23/08/2010 20:00:52    90.3795850118    23.7393433253    0    0    ALT:0.0,hdop:1.0,adc1:4.0,adc2:2.0    in3:1,,SATS:255
REG    1282572062    23/08/2010 20:01:02    90.3795850118    23.7393433253    0    0    ALT:0.0,hdop:1.0,adc1:4.0,adc2:2.0    in3:1,,SATS:255
REG    1282572072    23/08/2010 20:01:12    90.3795850118    23.7393433253    0    0    ALT:0.0,hdop:1.0,adc1:3.0,adc2:2.0    in3:1,,SATS:255
REG    1282572079    23/08/2010 20:01:19    90.3795850118    23.7393433253    0    0    ALT:0.0,hdop:1.0,adc1:3.0,adc2:2.0    in3:1,,SATS:255


But from 21:02, getting following strange location data (-74.0306949993    4.8815699895) against the vehicle. (see below)
Also inputs are unusual: for ours ‘in3:1’ should be there (see above). But here ‘in3:1’ is absent, instead ‘in1:0’ appears (see below). 'in1:0’ should not appear for our device; it is always 0.
Another point… data sending interval is around 37 seconds (see below). But our setting is to send every 10 seconds (see above).
Moreover, note that the device was in sleep mode & should not send data.
Thus, I’m confused if the below data is from our VT310.

REG    1282575734    23/08/2010 21:02:14    0.0000000000    0.0000000000    0    0    adc1:4.0    in1:0,
REG    1282575765    23/08/2010 21:02:45    -74.0306949993    4.8815699895    0    0    ALT:0.0,hdop:1.1,adc1:2.0,adc2:2.0    in2:1,,SATS:255
REG    1282575795    23/08/2010 21:03:15    -74.0306949993    4.8815699895    0    0    ALT:0.0,hdop:1.1,adc1:3.0,adc2:2.0    in2:1,,SATS:255
REG    1282575826    23/08/2010 21:03:46    -74.0306949993    4.8815699895    0    0    ALT:0.0,hdop:0.9,adc1:2.0,adc2:2.0    in2:1,,SATS:255
REG    1282575856    23/08/2010 21:04:16    -74.0306949993    4.8815699895    0    0    ALT:0.0,hdop:0.9,adc1:2.0,adc2:2.0    in2:1,,SATS:255
REG    1282575886    23/08/2010 21:04:46    -74.0306949993    4.8815699895    0    0    ALT:0.0,hdop:0.9,adc1:1.0,adc2:2.0    in2:1,,SATS:255
REG    1282575958    23/08/2010 21:05:58    -74.0306949993    4.8815699895    0    0    ALT:0.0,hdop:0.8,adc1:2.0,adc2:2.0    in1:0,,SATS:255
REG    1282575962    23/08/2010 21:06:02    -74.0306949993    4.8815699895    0    0    ALT:0.0,hdop:0.8,adc1:2.0,adc2:2.0    in1:0,,SATS:255
REG    1282575998    23/08/2010 21:06:38    -74.0306949993    4.8815699895    0    0    ALT:0.0,hdop:0.8,adc1:2.0,adc2:2.0    in1:0,,SATS:255


Then, from 22:38 to 22:47, the vehicle was moving in Columbia! (see below)
Also note, data sending interval is now around 30 seconds.

REG    1282581463    23/08/2010 22:37:43    -74.0307016671    4.8815333049    0    0    ALT:0.0,hdop:0.8,adc1:2.0,adc2:2.0    in1:0,,SATS:255
REG    1282581493    23/08/2010 22:38:13    -74.0305666665    4.8816016515    0    0    ALT:0.0,hdop:0.8,adc1:2.0,adc2:2.0    in1:0,,SATS:255
REG    1282581523    23/08/2010 22:38:43    -74.0299283326    4.8812483470    11    204    ALT:0.0,hdop:0.8,adc1:2.0,adc2:2.0    in1:0,,SATS:255
REG    1282581554    23/08/2010 22:39:14    -74.0304766675    4.8811950048    27    294    ALT:0.0,hdop:0.9,adc1:2.0,adc2:2.0    in1:0,,SATS:255
REG    1282581584    23/08/2010 22:39:44    -74.0327483336    4.8822249730    39    294    ALT:0.0,hdop:0.8,adc1:2.0,adc2:2.0    in1:0,,SATS:255
REG    1282581614    23/08/2010 22:40:14    -74.0349200010    4.8831750234    0    311    ALT:0.0,hdop:0.9,adc1:3.0,adc2:2.0    in1:0,,SATS:255
REG    1282581644    23/08/2010 22:40:44    -74.0360750000    4.8836800257    25    299    ALT:0.0,hdop:0.9,adc1:2.0,adc2:2.0    in1:0,,SATS:255
REG    1282581675    23/08/2010 22:41:15    -74.0356366674    4.8875133514    72    6    ALT:0.0,hdop:0.9,adc1:2.0,adc2:2.0    in1:0,,SATS:255
REG    1282581705    23/08/2010 22:41:45    -74.0338416656    4.8928866704    52    28    ALT:0.0,hdop:0.9,adc1:2.0,adc2:2.0    in1:0,,SATS:255
REG    1282581735    23/08/2010 22:42:15    -74.0348200003    4.8910016378    68    203    ALT:0.0,hdop:0.9,adc1:1.0,adc2:2.0    in1:0,,SATS:255
REG    1282581766    23/08/2010 22:42:46    -74.0361983339    4.8848283132    86    201    ALT:0.0,hdop:0.9,adc1:3.0,adc2:2.0    in1:0,,SATS:255
REG    1282581796    23/08/2010 22:43:16    -74.0380033334    4.8784883499    88    183    ALT:0.0,hdop:0.9,adc1:3.0,adc2:2.0    in1:0,,SATS:255
REG    1282581826    23/08/2010 22:43:46    -74.0378883322    4.8752049764    8    179    ALT:0.0,hdop:0.9,adc1:3.0,adc2:1.0    in1:0,,SATS:255
REG    1282581857    23/08/2010 22:44:17    -74.0375366648    4.8730450312    58    169    ALT:0.0,hdop:0.9,adc1:3.0,adc2:1.0    in1:0,,SATS:255
REG    1282581887    23/08/2010 22:44:47    -74.0378316681    4.8680916468    65    188    ALT:0.0,hdop:0.9,adc1:3.0,adc2:1.0    in1:0,,SATS:255
REG    1282581917    23/08/2010 22:45:17    -74.0378383319    4.8651533127    29    64    ALT:0.0,hdop:0.9,adc1:1.0,adc2:1.0    in1:0,,SATS:255
REG    1282581947    23/08/2010 22:45:47    -74.0376000007    4.8673350016    0    0    ALT:0.0,hdop:0.9,adc1:1.0,adc2:1.0    in1:0,,SATS:255
REG    1282581978    23/08/2010 22:46:18    -74.0376000007    4.8673350016    0    0    ALT:0.0,hdop:0.9,adc1:1.0,adc2:1.0    in1:0,,SATS:255
REG    1282582008    23/08/2010 22:46:48    -74.0376000007    4.8673350016    0    0    ALT:0.0,hdop:0.9,adc1:2.0,adc2:1.0    in1:0,,SATS:255
REG    1282582038    23/08/2010 22:47:18    -74.0374133348    4.8665183385    13    12    ALT:0.0,hdop:0.9,adc1:3.0,adc2:1.0    in1:0,,SATS:255
REG    1282582068    23/08/2010 22:47:48    -74.0373716672    4.8665783564    0    0    ALT:0.0,hdop:0.9,adc1:2.0,adc2:1.0    in1:0,,SATS:255
REG    1282582099    23/08/2010 22:48:19    -74.0373716672    4.8665783564    0    0    ALT:0.0,hdop:0.9,adc1:2.0,adc2:1.0    in1:0,,SATS:255


Later on it again make some moves from 23:27 to 23:32. (data not pasted here)


Then at 23:45, I sent an SMS to get its location. It returned the correct location & immediately after sending the SMS, it jumped to actual location (90.3794416746, 23.7392783483). From that time it starts jumping between Bangladesh & Columbia, which continues for 1 hour.

REG    1282585504    23/08/2010 23:45:04    -74.0306349993    4.8815583547    0    0    ALT:0.0,hdop:1.0,adc1:2.0,adc2:2.0    in1:0,,SATS:255
REG    1282585540    23/08/2010 23:45:40    -74.0306349993    4.8815583547    0    0    ALT:0.0,hdop:1.0,adc1:2.0,adc2:2.0    in1:0,,SATS:255
REG    1282585571    23/08/2010 23:46:11    -74.0306349993    4.8815583547    0    0    ALT:0.0,hdop:1.0,adc1:4.0,adc2:2.0    in1:0,,SATS:255
REG    1282585591    23/08/2010 23:46:31    90.3794416746    23.7392783483    0    0    ALT:0.0,hdop:2.1,adc1:3.0,adc2:2.0    in3:1,,SATS:255
REG    1282585592    23/08/2010 23:46:32    -74.0306349993    4.8815583547    0    0    ALT:0.0,hdop:1.0,adc1:4.0,adc2:2.0    in1:0,,SATS:255
REG    1282585626    23/08/2010 23:47:06    90.3794416746    23.7392783483    0    0    ALT:0.0,hdop:3.0,adc1:1.0,adc2:2.0    in3:1,,SATS:255
REG    1282585627    23/08/2010 23:47:07    90.3794416746    23.7392783483    0    0    ALT:0.0,hdop:3.0,adc1:1.0,adc2:2.0    in3:1,,SATS:255
REG    1282585649    23/08/2010 23:47:29    -74.0306349993    4.8815583547    0    0    ALT:0.0,hdop:1.1,adc1:4.0,adc2:2.0    in1:0,,SATS:255
REG    1282585663    23/08/2010 23:47:43    90.3794416746    23.7392783483    0    0    ALT:0.0,hdop:1.5,adc1:1.0,adc2:2.0    in3:1,,SATS:255
REG    1282585664    23/08/2010 23:47:44    90.3794416746    23.7392783483    0    0    ALT:0.0,hdop:1.5,adc1:1.0,adc2:2.0    in3:1,,SATS:255
REG    1282585679    23/08/2010 23:47:59    -74.0306349993    4.8815583547    0    0    ALT:0.0,hdop:1.1,adc1:4.0,adc2:2.0    in1:0,,SATS:255
REG    1282585700    23/08/2010 23:48:20    90.3794416746    23.7392783483    0    0    ALT:0.0,hdop:1.5,adc1:1.0,adc2:2.0    in3:1,,SATS:255


After 1 hour (at 00:45), the device again goes to sleep, & again it is permanently at -74.0306349993,4.8815583547.

REG    1282589136    24/08/2010 00:45:36    90.3795683225    23.7391733170    0    0    ALT:0.0,hdop:1.1,adc1:2.0,adc2:1.0    in3:1,,SATS:255
REG    1282589146    24/08/2010 00:45:46    90.3795683225    23.7391733170    0    0    ALT:0.0,hdop:1.1,adc1:2.0,adc2:1.0    in3:1,,SATS:255
REG    1282589156    24/08/2010 00:45:56    -74.0306349993    4.8815583547    0    0    ALT:0.0,hdop:0.8,adc1:3.0,adc2:2.0    in1:0,,SATS:255
REG    1282589156    24/08/2010 00:45:56    90.3795683225    23.7391733170    0    0    ALT:0.0,hdop:1.1,adc1:2.0,adc2:2.0    in3:1,,SATS:255
REG    1282589158    24/08/2010 00:45:58    90.3795683225    23.7391733170    0    0    ALT:0.0,hdop:1.1,adc1:2.0,adc2:2.0    in3:1,in4:1,,SATS:255
REG    1282589301    24/08/2010 00:48:21    -74.0306349993    4.8815583547    0    0    ALT:0.0,hdop:0.8,adc1:3.0,adc2:2.0    in1:0,,SATS:255
REG    1282589478    24/08/2010 00:51:18    -74.0306349993    4.8815583547    0    0    ALT:0.0,hdop:0.7,adc1:3.0,adc2:1.0    in1:0,,SATS:255
REG    1282589629    24/08/2010 00:53:49    -74.0306349993    4.8815583547    0    0    ALT:0.0,hdop:0.8,adc1:3.0,adc2:1.0    in1:0,,SATS:255
REG    1282589779    24/08/2010 00:56:19    -74.0306349993    4.8815583547    0    0    ALT:0.0,hdop:0.8,adc1:3.0,adc2:2.0    in1:0,,SATS:255
REG    1282589955    24/08/2010 00:59:15    -74.0306349993    4.8815583547    0    0    ALT:0.0,hdop:0.8,adc1:3.0,adc2:1.0    in1:0,,SATS:255


At 07:41, vehicle ignition ON & then it goes to actual location at 07:48. (see below)

REG    1282599598    24/08/2010 03:39:58    -74.0306699991    4.8816133499    0    0    ALT:0.0,hdop:0.8,adc1:2.0,adc2:1.0    in1:0,,SATS:255
REG    1282599943    24/08/2010 03:45:43    -74.0307250003    4.8815733592    0    0    ALT:0.0,hdop:0.8,adc1:2.0,adc2:1.0    in1:0,,SATS:255
REG    1282600119    24/08/2010 03:48:39    -74.0307250003    4.8815733592    0    0    ALT:0.0,hdop:0.8,adc1:2.0,adc2:1.0    in1:0,,SATS:255
REG    1282614087    24/08/2010 07:41:27    0.0000000000    0.0000000000    0    0    adc1:1.0,adc2:2.0    in3:1,in4:1,
REG    1282614097    24/08/2010 07:41:37    0.0000000000    0.0000000000    0    0    adc1:1.0,adc2:2.0    in3:1,in4:1,
REG    1282614108    24/08/2010 07:41:48    0.0000000000    0.0000000000    0    0    adc1:1.0,adc2:1.0    in3:1,in4:1,
.
.
.
REG    1282614461    24/08/2010 07:47:41    0.0000000000    0.0000000000    0    0    adc1:1.0,adc2:1.0    in3:1,in4:1,
REG    1282614471    24/08/2010 07:47:51    0.0000000000    0.0000000000    0    0    adc1:1.0,adc2:1.0    in3:1,in4:1,
REG    1282614481    24/08/2010 07:48:01    90.3716499964    23.7437383016    6    258    ALT:0.0,hdop:2.6,adc1:1.0,adc2:1.0    in3:1,in4:1,,SATS:255
REG    1282614491    24/08/2010 07:48:11    90.3714333216    23.7436749776    10    240    ALT:0.0,hdop:2.6,adc1:1.0,adc2:1.0    in3:1,in4:1,,SATS:255
REG    1282614501    24/08/2010 07:48:21    90.3713049889    23.7435766856    4    192    ALT:0.0,hdop:3.8,adc1:1.0,adc2:1.0    in3:1,in4:1,,SATS:255

I believe the messages with wrong location is not from our VT310; rather these are from vehicle in Columbia equipped with a non-VT310 device.

4

Meitrack VT310

Re: Meitrack VT310

Maruf, you are absolutely right, this is the problem. Unique ID of your device is 000001 - that is default ID for this device. Looks like somebody just using it also. Please select some unique value, update device and unit properties and all should be ok.

At the dark side of telematics...
5

Meitrack VT310

Re: Meitrack VT310

shal,

Fine, I’ll change Unique ID of my VT310.

But it is very peculiar how Wialon accepted one ID more than once. If the system cannot prevent accepting duplicate IDs, then it might collapse.

Wialon is not like that I think. Previously I tried to add existing Unique ID & existing Phone Number, but it didn’t allow me. That’s how it should be. That’s how it MUST be.

You should check how this case happened. There might exists some bug.

6

Meitrack VT310

Re: Meitrack VT310

Maruf, you can not add more then one unit os the same type and unique id or phone. This is the rule and system do not allow this.

At the dark side of telematics...
7

Meitrack VT310

Re: Meitrack VT310

Hi Guys !

I have a VT310 configured and working almost perfectly. This device has a very nice capability called Veer Report. This feature sends data to the server when the heading of the vehicle change beyond a preseted value. This helps to have a very accuracy tracking, because you will have , for example , one valid location data in every corner you turn...

I configured this option ( to 20 degree ) but I dont get any information on server when I turn. I would like to know whether is  a problem with the server software ( not able to recognize this kind of message  ) or my GPS is not sending anything to the server.

Thanks !

Anibal Vickacka
Punta Arenas
Chile

8

Meitrack VT310

Re: Meitrack VT310

anibalfv, looks like it is just dynamic send interval, so probably it is problem with hardware. Set angle to 5 degree to check the difference.

At the dark side of telematics...
9

Meitrack VT310

(edited by anibalfv 17/05/2011 17:15:54)

Re: Meitrack VT310

shal wrote:

anibalfv, looks like it is just dynamic send interval, so probably it is problem with hardware. Set angle to 5 degree to check the difference.

I have tryed everything and still is not working. Also I have noticed lost of data. For example, some times I am 1, 2 ,4 or even 10 minutes without receiving data from unit, even when I set it up to send data every 20 seconds. Sometimes I have 3 or 4 data every 20 seconds, and then one missing and then data again. ( so, I have a 40 seconds interval between data )

I'm sure I have GPRS signal, and even if there is no signal , it should save the data on the memory and send it later, wich happen when I take off the GPRS chip. But the points just dissapeared. It is possible the data are lost after being sent to the server ?

I need very good accuracy and I decided to buy this unit because the Veer Report option and the internal memory , but I'm having very bad results..

My account is anibalfvv and the pass is 4321 and on the 16th ( yesterday ) I had this missing data.

Please give me some advice !!

Thanks,

Anibal

10

Meitrack VT310

Re: Meitrack VT310

anibalfv,
all data packets which come from your device are stored in Wialon's database.
In your case, there might be a problem with GPS but not GPRS. If device is in the area where satellites are hardly available, it may not generate data packets for some time.
Also it's worth to mention that rare messages without coordinates won't affect creating of correct reports in Wialon.

Developer
Gurtam
11

Meitrack VT310

(edited by anibalfv 22/05/2011 06:22:45)

Re: Meitrack VT310

I think I have found the problem. Something is wrong when the GPS sends VEER REPORT data. I was able to see the data on MYCOM software ,  and this is what I found : ( my device id is 4925 )

This is the normal data , wich I'm receiving OK on the server :

$$ ~I%      U183420.000,A,5309.4611,S,07054.9487,W,0.00,297,210511,,*07|1.1|58|2000|0007,0005|02DA000304B09CD1|17|00006111 

24:24:20:7e:49:25:20:20:20:20:20:20:55    ( this is the hex code just before data , 13 bytes long the 4th byte OK )

This is the VEER REPORT data , that I'm NOT receiving on server :

$$  I%       R183354.000,A,5309.4614,S,07054.9477,W,0.13,337,210511,,*00|0.0|58|2000|0008,0004|02DA000304B09CCF|17|00006111 

24:24:20:20:49:25:20:20:20:20:20:20:20:52 (  this is the hex code before data , 14 bytes long and the 4th byte wrong )
 
And sometimes VEER REPORT sends this : ( 14 bytes long also, but the 4th byte is similar to the one with good data )

$$ ~I%       R183237.000,A,5309.6786,S,07055.3884,W,9.88,18,210511,,*32|0.0|52|2000|0007,0005|02DA000304B09D33|14|00005DE6'i

24:24:20:7e:49:25:20:20:20:20:20:20:20:52

So, the data is sent, but it has one extra byte and data packet length wrong , and the server doesn't validate the data.

I corrected  and added these data manually to Wialon, and the track is INCREDIBLE smooth now, with every corner and every turn marked.  I'm trying to get this fixed by the manufacturer....

The only problem is when the car is not moving , because the heading value from GPS goes crazy, so I have data sent every 3 seconds !!

Thanks !

Anibal

12

Meitrack VT310

Re: Meitrack VT310

Sorry my friend,

I had the same issue with wialon. Unfortunately wialon not recognize some reports of vt310/300, another case is the panic button.

Please test with the meitrack software, you´ll see your tracker working properly.

13

Meitrack VT310

Re: Meitrack VT310

globallbs
Just give us reports that are not recognized, we will add them.

WDC Administrator
Gurtam
14

Meitrack VT310

Re: Meitrack VT310

I am interested in the following reports:

- Headind o veer report.
- Panic button.
- Ignition on / off

Can you add events such as GPS antenna disconnect and battery?

15

Meitrack VT310

(edited by eliphas 07/07/2011 22:57:48)

Re: Meitrack VT310

+1 for having the input sensors on VT310 supported.
Maybe the outputs and GPRS commands too? smile
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 wink

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 smile

If any other copy/paste or testing needed just ask!

16

Meitrack VT310

Re: Meitrack VT310

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.

17

Meitrack VT310

Re: Meitrack VT310

For now Wialon don't parse and don't register outputs values.
We will check with the documentation and if information about outputs will be confirmed we will modify script to register this data.

Developer
flespi team
18

Meitrack VT310

Re: Meitrack VT310

Hi everybody,

i have some general questions for my understanding.
We want to move from our existing and own developed platform to wialon. Everything looks great, but i am a little bit helpless with reports:
i want to generate a easy tripreport, for example start time, end time, with adress, distance, etc.

we use VT310 Devices. I have journey which is the total! distance in Meter (Odometervalue), but if i try to set milagecounter it shows me value in KM (so its 1000x too much).

So basicaly i dont realy understand, how sensors are configured and implemented into individual reports...

i tried to understand documentation but still helpless...

Mabye someone has a hint :-)

Thanks
Wolf.

Politeness dictates it to write his name on a post
19

Meitrack VT310

(edited by GoGPS 19/11/2011 09:07:56)

Re: Meitrack VT310

wwbusch
1. You need add odometer like sensor
2. After this you need use formula. In sensor window choose tab calculation table
3. X = 1, a = 0.001, press ADD and OK
4. Thats all

Eduard Vald / GoGPS Service
www.gogps.eu
Skype: tivald.ee
20

Meitrack VT310

Re: Meitrack VT310

hi
can you advice or send me the parameter for MVT380
I need the full list for all the parameter that can be open under wialon
thank Isaac

21

Meitrack VT310

Re: Meitrack VT310

isaac wrote:

hi
can you advice or send me the parameter for MVT380
I need the full list for all the parameter that can be open under wialon
thank Isaac

22

Meitrack VT310

Re: Meitrack VT310

isaac wrote:
isaac wrote:

hi
can you advice or send me the parameter for MVT380
I need the full list for all the parameter that can be open under wialon
thank Isaac

Hi Isaac,

Just connect a MVT380 to Wialon and let it send some messages.
Than you can see in "Messages" the Raw-Data and check the params you need.
Thats the most easyest way :-)

Wolf.

Politeness dictates it to write his name on a post
23

Meitrack VT310

Re: Meitrack VT310

I'm working on Meitrack's VT 310 with resistance fuel type sensor. Can anyone guide me how to configure the fuel sensor to add the fuel percentage level to the report ?

Thanks.

24

Meitrack VT310

Re: Meitrack VT310

Did not use that type of trackers, but I can say how it should look. Tracker reads the resistance of the sensor and converts it into units that come to the server. On the server, you create a table "units => fuel (L)".

Евгений
Technoton Sensors Pvt. Ltd., India
http://technoton.in
25

Meitrack VT310

Re: Meitrack VT310

take a meter and read the voltage that the sensor is returning to make sure that it is in the range of the Tracker. You may need to turn on the ignition as most sensors are powerd down when the ignition is off so no readings will be sent. Then connect the sensor to an analogue port of the unit and see if you are seeing anything in Wialon for the corresponding parameter eg adc1 may show 6.567. Make sure that the port is enabled in the tracker.

You then need to calibrate the sensor by draining the tank and filling it in 5 or 10 lt increments and looking at the reading you are getting against the sensor in Wialon. Do this untill you have a full tank.

Go to the unit configuration in Wialon and create a fuel sensor and use the values you have captured as the inputs for the calibration table. Generat the table and you should be OK.

Phoenix Solusi
Mobile Visible Secure
Specialists in data acquisition and analysis for mobile and fixed assets. Integration in to content management systems is a specialty we have.