Markon GPS – Troubleshooting Guide

First send command PARAM# to make sure SMS command is working or not.
If not getting the reply of SMS command then need to check SIM card or installation to make sure device is connected to power.

If getting SMS reply but device is not coming online on server then follow below steps:
status# and check# and APN# – make sure APN is correct

Example: APN,airteliot.com#

In status# reply:
GPRS:link UP means device is connected to server.
GPRS:link DOWN means device is not connected to server.
Possible reasons: wrong APN, wrong server command, network issue, server response issue, or server port issue.
In check# reply:
- If GPRS status is showing 0 means internet is not working
- If showing 1 means working
- If using URL/Domain in server configuration then check GET IP – if show 0.0.0.0 means internet is not working
If showing "searching satellite" then check where# first. In where reply you can check last fixed GPS date.

In status# reply if satellite status is like 0(24) or 0(4) means location issue or installation place (mounting) issue. To cross check this issue please move the vehicle and in moving condition check status#. If in moving also showing searching satellite like 0(24) then need to check installation place.

Second case "UART NO DATA".
If showing "UART NO DATA" in moving condition also then hardware issue – need to send back the device.

Application to check Satellite signal status: GPS Test on Play Store
Recently, we have found an issue with a few vehicles. After connecting the device to the vehicle battery or turning the ignition on, the GPS is not able to get a fix. This is due to electromagnetic interference.

We suspect that this is caused by an interference source. Since this problem has emerged recently, please first check if any new devices have been installed in the vehicle, such as Bluetooth speakers, etc., which might cause electromagnetic interference to the tracker.

If you can obtain the tracker, you can take it outside for testing to see if the positioning works well when the ACC is turned ON.

If in status# reply showing "GPS:ON, Uart no data;" in moving showing the same – that means hardware issue & need to send back the device to Markon office.

Address:
Markon Electronics Corporation Private Limited
U-1 Central Ground Floor
Green Park Extension, New Delhi – 110016
Contact person: Sanjay Mishra
Contact number: +91 8178772372

If still facing issue:

Shift the non-AIS device to this server: server,1,gps.markongps.com,21100,0#
Wait for 2 minutes then check status# again & cross check GPRS status
If showing GPRS link up that means device is working fine & maybe your server port issue/Wrong response/Protocol integration issue etc.. & need to check with your software provider

If showing GPRS link:up but still device is not coming online then send following commands & then check the data:

. gpsdup,on#

. fdrift,off#

. timer,10,10#

. acc,on,0#

. reset,1#

After above commands: If still device is offline and showing GPRS link down then please share the only raw data with device IMEI, raw data sample (decoded data not required, required only Hex logs).

78 78 05 15 00 49 F1 64 0D 0A

78 78 0A 13 46 06 04 00 02 00 4A 76 B8 0D 0A

78 78 05 13 00 4A 15 26 0D 0A

78 78 0A 13 46 06 04 00 02 00 4B 67 31 0D 0A

If Showing wrong location on server: please check use following command to check GPS status

1. status# (make sure GPS is fixed and GPRS link is UP)

2. URL# (using this command you will get the current location and then you can match the location with server location)

3. where# (using this command you will get current lat, lng with speed value)

Sleep Mode

What is Sleep mode?

Answer: Once ignition is off, device will go in sleep mode after 5 minutes. In sleep mode device will send heartbeat packet as per configured interval & information packet.

In sleep mode only GPS module will be off to save the vehicle battery and data.

Enable Sleep Mode

SENDS,5# – What does "SENDS" command do?
sends command controls the GPS module. If sends is 5 that means once ignition is off then in next 5 minutes GPS module will enter sleep mode (GSM module will keep working) and device will send only HBT packet to server. Once ignition is on, device will exit the sleep mode and keep sending location data normally.

Recommended commands for sleep mode:

1. gpsdup,off# (For data when ignition is off or GPS is not fixed)

2. sends,5#

3. hbt,1,1#

4. timer,10,3600# (timer is for location packet interval)

5. sf,on# (sf static filter for static drift)

6. fdrift,on# (fdrift is filter for speed drift)

Disable Sleep Mode

After these commands no matter ignition is on or off, device will always send the data (maybe in static you can face static drift issue).

1. sends,0# (GPS module will be always on)

2. gpsdup,on#

3. sf,off#

4. hbt,1,1#

5. timer,10,10#

6. sf,on#

7. fdrift,off#

These servers should be whitelisted:

fota.markongps.in and 43.205.18.220 – OTA server, need to whitelist both URL and IP (reason: sometime Operator is not able to resolve the DNS address, due to this issue need to whitelist both address IP and URL)
gpsdev.markongps.in & 94.136.186.76 – testing server1 for troubleshooting (mandatory only for testing purpose else ignore this one)
test.markongps.in & 217.216.78.62 – testing server2 for troubleshooting (mandatory only for testing purpose else ignore this one)
Communication Protocols: TCP, HTTP, FTP, UDP, SSL, PAYLOAD, EXISTING, SIP, SMTP, RTMP, SSH, HTTPPROXY
Application Protocols: Google Maps, Google APIs, AMAZONAWS, AMAZON, Others, Bittorrent, Google Cloud Messaging, Encrypted Client, Microsoft, Google, DTLS
Where to find Application & Communication Protocols (example: with Airtel M2M Portal): in side menu find → Rule center → Data whitelisting → Edit APN configuration → then under the action table title, click on pencil edit button

Recently, we have observed some issues with Airtel M2M SIM cards.

If the data flow shows Login → HBT packet → connection disconnects, and then again Login → HBT packet, this indicates a whitelisting issue. Because the data connection drops within milliseconds, the device is unable to upload the location packet. Due to this, the latest location will not be updated on the server.

You can check the current location using the URL# or WHERE# SMS command. (For more details, please contact: support@markongps.com)

Note: We have observed that this issue may affect approximately 30%–40% of devices.

We have conducted multiple meetings with the Airtel team, and after applying the recommended configuration, the issue is getting resolved.

If you are still facing the same issue, please raise a complaint with Airtel stating: "Facing data disconnection issue within milliseconds." Once you receive the meeting link from Airtel, please include our support team (support@markongps.com). Our team will assist in explaining the issue to Airtel.

Important: Before raising the issue, please ensure that the testing URL is whitelisted.

In Wetrack140 do not configure APN or GMT, APN and GMT will be configured automatically. To reset the APN configuration use: ASETAPN,ON#
Default APN is TAISYSNET for Taisys & SENSEM2M2 for Sensorise.

Important Note: After reactivation of eSIM need to send clear# and reset,1# command to clear older data.
Planumber (vehicle number) should be correct otherwise it will create issue in govt. backend portal.

Default planumber is: planumber,000000000#
Query current parameter: planumber#
In NIC backend portal please configure vehicle number example: planumber,AB12C1516#

GPRS Command Headers

$Header,MARK,PARAM# – BSNL/APSAC/MH mining etc.
$Header,CMD,PARAM# – NIC
$CMD,PARAM# – CDAC

Manual Network Switching (Wetrack140 – Taisys Esim)

1. Airtel → esim,airtel#
2. Vodafone → esim,Vodafone#
3. BSNL → esim,bsnl#
4. esimauto,on# (once you switch the network then please send esimauto,on#)

Manual Network Switching (Wetrack140 – Sensorise Esim)

1. Primary Profile → esim,1#
2. Secondary Profile → esim,2#
4. esimauto,on# (once you switch the network then please send esimauto,on#)

Latest Wetrack140 Firmware for Taisys/Sensorise ESIM

1. BSNL (Standard): NT06I_AIS140_WCAI_4IN1TS_V1.2_250618.1847
2. NIC: NT06I_AIS140_WCAI_4IN1TS_V1.2_250618.1847
3. CDAC: NT06I_AIS140_WCAI_4IN1TS_V1.2_250618.1847

Disable LED sleep (use case: after this command device LED will always on)

LEDSLEEP,A#
A = On / Off
Default: on
Query current parameter: LEDSLEEP#
Command example: LEDSLEEP,off#

In Wetrack140 if green LED (GSM) is not blinking after manual reboot also – that means eSIM profile is crashed or eSIM issue & if in moving condition also showing UART NO DATA in status reply then need to send back the device to:

Markon Electronics Corporation Pvt. Ltd.
U 1 Central Ground Floor
Green Park Extension, New Delhi – 110016
Contact person: Sanjay Mishra
Contact number: +91 8178772372

MAHAKHANIZ Ports for Markon

Command Example: backupserver,1,mh.markongps.in,18009,0#

If device is not updating on MH mining portal then:

Required configuration:
1. sends,0#
2. sf,off#
3. gpsdup,on#
4. timer,10,10#

Check backupserver# and status#
In status# reply GPS should be fixed; if GPS not fixed then mining server will reject the data.
If showing "searching satellite" then move the vehicle and check status#

Example of GPS not fixed: Battery:4.03V,NORMAL; GPRS:Link Up; Signal Level:Strong; GPS:Successful positioning; SVS Used in fix:0(36); (OR 0(0))

Example of FIXED GPS: Battery:4.03V,NORMAL; GPRS:Link Up; Signal Level:Strong; GPS:Successful positioning; SVS Used in fix:24(36);
If still showing "searching satellite" then need to check installation place of device
In backupserver# reply cross check the mining URL and port
Last command reset,1#; after command wait for 10 minutes and then check the data on MH mining portal

Note: After all above troubleshooting if still device is not updating then share (support team refer point no.18) the device IMEI and MH mining portal snapshot where last update is visible with date and time.

Available Ports (MAHAKHANIZ)

#	Port	Current Status
1	17003	NOT IN USE (please do not use this port)
2	18004	USED
3	17012	USED
4	18002	USED
5	18003	USED
6	19004	Available for Use (Max 1400 device)
7	17010	Available for Use (Max 1400 device)
8	17011	Available for Use (Max 1300 device)
9	19001	USED (please do not use this port)
10	17005	Available for Use (Max 1300 device)
11	17001	Available for Use (Max 1300 device)
12	20011	Available for Use (Max 1200 device)
13	17004	Available for Use (Max 1000 device)
14	20012	Available for Use (Max 700 device)
15	20001	Available for Use (Max 1200 device)
16	19008	USED (please do not use this port)
17	19006	Available for Use (Max 1000 device)
18	19009	USED
19	20004	Available for Use (Max 500 device)
20	20002	Available for Use (Max 1000 device)
21	18010	USED
22	18011	USED
23	20006	USED
24	19005	Available for Use (Max 500 device)
25	20013	USED
26	18001	USED
27	18009	USED
28	17006	USED

Chandigarh NIC

sf,on#

gpsdup,on#

timer,10,10#

soetime,1#

sosalm,on#

backupserver,1,vltspvt.chd.gov.in,9031,0#

soeserver,1,vltsemg.markongps.in,5012,0#

SOESERVER,1,vltsemg.chd.gov.in,9032,0#

relaysos,on#

If panic alert is not getting cleared then check:

sosalm# (sosalarm should be on - sosalm,on,0#)
soetime,1# (SOETIME close the emergency automatic - soetime,1# means device will close the emergency in 1 minute; max interval 24 hrs, value will be in minute)
relaysos,on# (this is for LED blink function)
exitsoe# (this command close the emergency immediately)

Wait for 2 minutes then press panic button again and check the data. If still data is not coming then need to check panic connection (contact Rahul: +91 98996 28620).

Bihar Mining and NIC Configuration

soetime,1#

gpsdup,on#

timer,10,10#

sosalm,on,0#

backupserver,1,vlts.bihar.gov.in,9999,0#

backupserver2,0,0.0.0.0,0000,0#

soeserver,1,vltsemg.markongps.in,9032,0#

Bihar Mining and NIC Configuration (Second)

soetime,1#

gpsdup,on#

timer,10,10#

sosalm,on,0#

backupserver,1,brvlts.markongps.in,9031,0#

backupserver2,0,0.0.0.0,0000,0#

soeserver,1,vltsemg.markongps.in,9032,0#

Vahan-Common-layer

Backupserver,1,commonlayer.parivahan.gov.in,9031,0#

soeserver,1,vltsemg.markongps.in,5018,0#

gpsdup,on#

Timer,30,30#

Soetime,1#

hbt,1#

Sosalm,on,0#

SOESERVER,1,commonlayer.parivahan.gov.in,9032,0#

Dehi NIC

backupserver,1,vltspvt.delhi.gov.in,9031,0#

soeserver,1,vltsemg.markongps.in,5013,0#

sosalm,on,0#

relaysos,off#

timer,10,10#

soetime,1#

ledsleep,off#

Rajasthan NIC

backupserver,1,vltspvt.rajasthan.gov.in,9031,0#

soeserver,1,vltsemg.markongps.in,5015,0#

Timer,20,120#

hbt,1#

gpsdup,on#

APSAC Mining Configuration{Protocol TYpe BSNL}

backupserver,1,device.apsac.ap.gov.in,5008,0#

gpsdup,on#

sf,off#

timer,10,10#

Himachal Configuration{Protocol TYpe BSNL}

backupserver,1,hp.markongps.in,443,0#

gpsdup,on#

timer,10,10#

sf,off#

soetime,1#

Note: Make sure GPS is fixed. If GPS is not fixed then CDAC server will reject the request. GPS status can be checked using Status# command.

Odisha Configuration{Protocol TYpe NIC}

backupserver,1,pvtdevices.odishatransport.gov.in,8212,0#

soeserver,1,emrdevices.odishatransport.gov.in,9202,0#

gpsdup,on#

relaysos,on#

soetime,30#

GPCB Command

backupserver,1,gpcb.markongps.in,9999,0#

gpsdup,on#

sf,off#

timer,10,10#

planumber,vehiclenumber#

West Bengal CDAC Configuration

server,1,vltsgw.wb.gov.in,80,0#

sends,0#

sf,off#

gpsdup,on#

http_mode,0#

http_recv,0#

Pondicherry

soeserver,1,pondicherry.markongps.in,9201,0#

backupserver,1,pondicherry.markongps.in,9201,0#

BSNL Backend Command

backupserver,1,bsnl.markongps.in,5678,0#

Soeserver,1,Emergency.vltsecurity.com,1090,0#

gpsdup,on#

Sf,on#

timer,10,10#

Standard FCI "FCIVLTS"

BACKUPSERVER,1,fcivlts.in,9999,0#

gpsdup,on#

timer,10,10#

server,1,ais.markongpas.in,5179,0#

Haryana FCI "Map My India"

backupserver,1,pujabfci.markongps.in,4030,0#

gpsdup,on#

timer,10,10#

server,1,ais.markongpas.in,5335,0#

Haryana FCI FleetRobo

backupserver,1,fci.new.markongps.in,7884,0#

timer,20,60#

gpsdup,on#

sf,off#

hbt,1#

West Bengal FCI

server,1,vltsfs.wb.markongps.in,4443,0#

sends,0#

sf,off#

gpsdup,on#

backupserver,1,ais.markongps.in,8090,0#

NHAI

backupserver,nhai.markongps.in,3002,0#

soeserver,1,nhai.markongps.in,4446,0#

planumber,vehiclenumber# | example: planumber,DL13CU5959#

gpsdup,on#

timer,10,10#

accalm,on,0#

poweralm,on,0#

sosalm,on,0#

Wetrack 4-in-1 Firmware Configuration

latest version - NT06I_AIS140_WCAI_4IN1TS_V1.2_250618.1847

esimtype,1# - For sensorise Esim

esimtype,2# - For Taisys OLD esim {before june 2025}

esimtype,3# - For Taisys new ESIM {after july 2025}

{Note: after esim provider selection wait for 20 second, device will reboot, after reboot only setup other commands like server, backupserver etc..}

Protocol selection {only for "NT06I_AIS140_WCAI_4IN1TS_V1.2_250618.1847" or above 4IN1TS_1.2}:

1. sys_protocol,0# {means Bsnl/apsac/mh mining version etc.. string type NRM}

2. sys_protocol,1# {means NIC/Vahan-commonlayer/Uttarakhand/Chandigarh/Delhi/GPCB/Pondicherry/Bihar mining/Odisha/etc.. String Type PVT}

3. sys_protocol,2# {CDAC}

Note: After the sys_protocol command, the device will revert to its default configuration. You will need to reconfigure the server, backup server, SOE server, etc., again.

Harsh Acceleration/Brake

SPEEDCHECK,A,M,T,ΔV1,ΔV2#

A=ON/OFF; speed change detection switch, default: OFF;

M=0-1 alarm type, default: 0;

T=1-30 seconds, detection time, default: 4 seconds;

ΔV1=10-300km/h, acceleration threshold (speed change), default: 30km/h;

ΔV2=10-300km/h, deceleration threshold (speed change), default: 50km/h;

Example: SPEEDCHECK,on,0,4,15,15#

Query current parameter: SPEEDCHECK#

Sharp Turn Alarm

SWERVE,A,M,ΔC,V,T#

A=ON/OFF, sharp turn alarm switch, default off;

M=0-1, alarm type, default M=0;

C=10-180 degrees, course angle variation threshold, default 30 degrees;

V=10-200KM/H, speed threshold, default 60km/h;

T=1-30 seconds, sharp turn detection time, default 3 seconds

Example: SWERVE,on,0,15,15,3#

Query current parameter: swerve#

OverSpeed Alarm

SPEED,A,B,C,M#

A=ON/OFF, open or close over speed alarm, default: OFF

B=5–600 (second), time interval, default 20 (second)

C=1~255(km/h), speed limit, default 100(km/h);

M=0/1, way of alarm, 0: GPRS only, 1: SMS+GPRS, default 1.

SPEED,ON,10,60,0#

Query current parameter: speed#

Displacement Alarm / Moving Alarm in Ignition Off Condition

MOVING,A,R,M#

A=ON/OFF, default OFF;

R=100~1000, moving radius, unit: meter, default: 300

M=0~2, way of alarm. 0: GPRS only, 1: SMS+GPRS, 2:

MOVING,ON,100,2#

Query current parameter: moving#

Power Cut Alarm

POWERALM,A,M,T1,T2#

A=ON/OFF, default ON;

M=0/1/2, way of alarming,

0: GPRS only, 1: SMS+GPRS,

2: GPRS+SMS+phone call, M=3 GPRS+CALL, default 2

T1=2–60 (second), default 5

T2=1–3600 (second), default 300

Query current parameter: POWERALM#

Example: POWERALM,ON,0,10,60#

Query current parameter: poweralm#

Device (Internal) Low Battery Alarm

BATALM,A,M#

A=ON/OFF; Default: Off

M= alarm way, range 0~1; default M=1

Query current parameter: BATALM#

Example: BATALM,ON,0#

Query current parameter: batalm#

Ignition On/Off Alarm

ACCALM,A,M,T,N#

A=ON/OFF; default:OFF

M=0/1, alarm way; 0 only GPRS; 1 SMS+GPRS

T= 5~60 seconds; detect time

N=0~2; 0:ACC state change alarm; 1:ACC change off alarm; 2: ACC change on alarm

Query current parameter: ACCALM#

Example: ACCALM,ON,0#

Mileage

MILEAGE,A,L#

A=ON/OFF; Default OFF

L = mileage initial value, mileage value, unit: km, range 0-999999km; when L is 0, it means that the mileage is cleared. The default is 0;

Query current parameter: MILEAGE#

Example: mileage,on#

HeartBeat Packet Interval

HBT,T1,T2#

T1 = 1 to 300 minutes, heartbeat packet upload interval when ACC ON

default value: 3 minutes;

T2 = 1~300 minutes, heartbeat packet upload interval when ACC OFF

default: 5 minutes

Query current parameter: HBT#

Example: HBT,1,1#

Angle Upload

ANGLEREP,X,A,B#

X=ON/OFF, default ON

A=5–180 degrees, diversion angle degree, default 30 degrees

B=2–5 seconds, detecting time, default: 3 seconds

Query current parameter: ANGLEREP#

Example: ANGLEREP,ON,30,3#

Device LED Sleep Enable / Disable

LED sleep disable:

LEDSW,A#

A = ON/OFF

Query current parameter: LEDSW#

Command example: LEDSW,off#

V5 / VL149 / GT800 / Wetrack2 / Wetrack-lite

Vehicle Battery data {external voltage packet 0x94} (on server value will be in Voltage)

{External power detection}

ADT,SW,T

SW = On/off

T = Interval - 5~3600 in seconds

Example: ADT,ON,30#

Query current parameter: ADT#

Sample Raw data: 79 79 00 08 94 00 05 49 01 A3 70 57 0D 0A

start bit: 79 79

Package Type: Data transmission general package (94)

Packet length: 8(0008)

Information Type: External voltage (00), Transfer file information: 0549(0549)

External voltage = 13.53(0549)

Message serial number: 01A3(01A3)

Verification information: 7057(7057)

stop bit: 0D 0A

V5/VL149 Soft ACC Command:

acc,on,0# (detect ignition using wire)

acc,on,3# (detect ignition using motion)

Query current parameter: ACC#

Timer Command {location packet interval}:

TIMER,T1,T2#

T1 : ranges 0/5~18000 seconds, upload interval when ACC ON, default is 10;

T2 : ranges 0/5~18000seconds, upload interval when ACC OFF, default is 10;

Query current parameter : TIMER#

Example- Timer,10,10#

Power Saving Command (Vehicle Battery Protection)

External low battery protection:

EXBATCUT,A,M,N1,N2,T#

A=ON/OFF

M=alarm way, range 0|1; 0 GPRS; 1 SMS+GPRS

N1=external voltage is lower than the low voltage protection threshold, range 10-360; unit:0.1V, (360=36V)

N2=recover the external power supply voltage range 10-360; unit:0.1V

T=detection time, range 1-300, unit: second, default 10 seconds

Query current parameter: EXBATCUT#

Example: EXBATCUT,ON,1,120,135,10# (120 means 12 volt)

Low external battery alarm:

EXBATALM,A,M,N1,N2,T#

A=ON/OFF; Default: OFF

M = alarm way, range 0~1; 0 only GPRS, 1 SMS+GPRS; default: M=1;

N1=10-360; low voltage alarm threshold, unit: V

N2=10-360; contact alarm threshold, unit: V

T=1-300; detection time, unit: second, default value: 10 seconds;

Query current parameter: EXBATALM#

Example: EXBATALM,ON,0,100,130,10# (100 means 10 volt)

Final command to execute the function (without this command function will not work):

FLYCUT,ON#

V5 RELAY Command (When showing searching satellite or GPS is not fixed – no speed limit in this command)

1. Prelay,1#

2. Prelay,0#

Vibration Alert Setup

SENSORSET,10,1,1,1#

SENALM,ON,0,1,10,1,1#

LEVEL,1#

SENDS,1,10,1#

Collision Alarm Commands: COLLIDE

COLLIDE,A,M,N,T1,T2,V#

A = ON/OFF, collision switch, default off;

M = Alarm reporting method: M=0: GPRS only; M=1: SMS+GPRS, default 0;

N = 10-1024, Collision Level Default: 480

T1 = 3-20, Delay in starting detection after receiving a collision interrupt, 10 seconds by default

T2 = 10-90, Third-stage detection time, 90 seconds by default

V = 5-30, Determine vehicle speed, 5 km/h by default

V5 Dual IP or URL Server Command

For IP:

server,0,ip,port,0# (Example: server,0,127.0.0.1,5172,0#)

server3,0,ip,port,0# (Example: server3,0,127.0.0.1,5172,0#)

To cancel dual IP function: SERVER3,NULL#

For Domain/URL:

server,1,url,port,0# (Example: server,1,markongps.com,21100,0#)

server3,1,url,port,0# (Example: server3,1,markongps.in,5023,0#)

To cancel dual URL: SERVER3,NULL#

V5/GT800/Wetrack2/GT06N/Wetrack-lite LockIP Command: LOCKIP#

First cross check the current server before sending lockip command (use server#). If server command is correct then only send LOCKIP# command.
Unlock command is not available. For unlock device please send email to support@markongps.com

HBT "HeartBeat" Data Packet Interval

HBT,A,B#
A = Ignition on interval, Default:3, Max 1~300 Minute
B = Ignition off interval, Default:5, Max 1~300 Minute GET current value : HBT# Example Set - HBT,1,1#

VL149 Specific Commands

VL149 Dual IP or URL Server Command

For IP:

server,0,ip,port,0# (Example: server,0,127.0.0.1,5172,0#)

protocol,2,on,0#

second_server,on,0,yourserverip,serverport,0# (Example: second_server,on,0,127.0.0.1,5172,0#)

To cancel dual IP function:

protocol,2,off#

second_server,off#

For Domain/URL:

server,1,URL,port,0# (Example: server,1,xyz.com,5172,0#)

protocol,2,on,0#

second_server,on,1,yourserverURL,serverPort,0# (Example: second_server,on,1,xyz.com,5072,0#)

To cancel dual URL:

protocol,2,off#

second_server,off#

VL149 LockIP Command: LOCKIP,ON#

First cross check the current server before sending lockip command (use server# or QLOCKIP). If server command is correct then only send LOCKIP,on# command.
Unlock command is not available. For unlock device please send email to support@markongps.com

V5/VL149/Wetrack2/GT800/GT06N: History Log store capacity is 1000 location packets.

GT800 Dual IP or URL Server Command

For IP configuration:

Enable/Disable the second server: SECOND_SERVER_SW,1# | 0 means disable | 1 means enable

server1: server,0,ip,port,0# (Example: server,0,127.0.0.1,5172,0#)

server2: second_server,0,ip,port,0# (Example: second_server,0,127.0.0.1,5172,0#)

To cancel dual IP function: second_server,NULL#

For Domain/URL:

SECOND_SERVER_SW,1#

server1: server,1,url,port,0# (Example: server,1,markongps.com,21100,0#)

server2: second_server,1,url,port,0# (Example: SECOND_SERVER,1,gps.markongps.com,21100,0#)

To cancel dual URL: second_server,NULL#

Wetrack2 Soft ACC Command

vacc,off# (detect ignition using wire)

vacc,on# (detect ignition using motion)

GPRS Command Example (Command from Server)

Hex GPRS command Example "Relay#": 78 78 10 80 0A 00 00 00 00 72 65 6C 61 79 23 00 01 AB F7 0D 0A

Decoded Hex Command(Relay#): 78 78 10 80 0A 00 00 00 00 72 65 6C 61 79 23 00 01 AB F7 0D 0A

Package Type: Send packet under online instructions (80)
Packet length: 16(10)
Instruction length: 10(0A) Server flag: 00000000(00000000)
Instruction content: relay#(72656C617923) Language: (0001)
Message serial number: 0001(0001)
Verification information: ABF7(ABF7)

Hex Response Example of Relay#: 79 79 00 11 21 00 00 00 00 01 52 45 4C 41 59 3A 30 02 B3 48 FF 0D 0A

Decoded hex Response Example: raw data: 79 79 00 11 21 00 00 00 00 01 52 45 4C 41 59 3A 30 02 B3 48 FF 0D 0A
Package Type: Online instruction response package (21)
Packet length: 17(0011)
Server flag: 00000000(00000000) Encoding type: ASCII code (01)
content: RELAY:0(52454C41593A30)
Message serial number: 02B3(02B3)
Verification information: 48FF(48FF)

Relay,1#: 78 78 12 80 0C 00 00 00 00 72 65 6C 61 79 2C 31 23 00 01 20 D2 0D 0A
relay,0#: 78 78 12 80 0C 00 00 00 00 72 65 6C 61 79 2C 30 23 00 01 3C 69 0D 0A

Pbsw Command

(After enabling "PBSW" History location data comes with heartbeat packet – only for NON AIS V5/VL149 devices)

pbsw,on# (after this command history data will contain one heartbeat packet in the end of packet – in this case need to read complete buffer, data and once hbt packet found send hbt response)
To disable: pbsw,off#
Query current parameter: PBSW#

Example:
Location history packet example when PBSW is ON:
78 26 22 19 07 13 16 35 06 C6 03 0C 94 1D 08 43 E5 04 00 04 93 01 94 0A 00 A3 00 2E DE 00 0E 01 00 00 02 D3 04 22 51 3D 0D 0A 78 78 26 22 19 07 13 16 35 10 C6 03 0C 94 1D 08 43 E5 04 00 04 93 01 94 0A 00 A3 00 2E DE 00 0E 01 00 00 02 D3 04 23 9D 8C 0D 0A 78 78 26 22 19 07 13 16 35 1A C6 03 0C 94 1D 08 43 E5 04 00 04 93 01 94 0A 00 A3 00 2E DE 00 0E 01 00 00 02 D3 04 24 A7 5C 0D 0A 78 78 26 22 19 07 13 16 35 24 C6 03 0C 94 1D 08 43 E5 04 00 04 93 01 94 0A 00 A3 00 2E DE 00 0E 01 00 00 02 D3 04 25 5A 40 0D 0A 78 78 26 22 19 07 13 16 35 2E C6 03 0C 94 1D 08 43 E5 04 00 04 93 01 94 0A 00 A3 00 2E DE 00 0E 01 00 00 02 D3 04 26 26 B4 0D 0A 78 78 0A 13 06 06 04 00 02 00 05 0B 4D 0D 0A

After enabling the pbsw command this is the Response example for history location packet: 78 78 05 13 00 34 8F DF 0D 0A

GPSDUP Command

(basically gpsdup command copies last fixed location & keeps sending with updated date and time when ignition is off or when GPS is not fixed – once ignition on and GPS is fixed then command has no impact)

GPSDUP,A#
A=ON: Regularly upload data when tracker's ignition is OFF or vehicle static
A=OFF: No location data is uploaded when ignition off, sleeps or static. Default: OFF
Query current parameter: GPSDUP#
Example: GPSDUP,ON#
Reply: OK!

SF "Static Data Filtering"

Use case: SF command helps to avoid static jumps when vehicle is in parking. Example if value is SF,on,100# then in this case if ignition off and any static jump found within 100 meter then device will not upload that false data to server.

SF,[A][,B]#
A=ON/OFF; static drift filtering switch; default: ON
B=10-1000(m); maximal filtering distance; default: 100(m);
Query current parameter: SF#
Example: SF,ON,100#
Reply: OK!

VL149 & V5(4G) SF "Static Data Filtering"

Use case: SF command helps to avoid static jumps when vehicle is in parking. Example if value is SF,on,100# then in this case if ignition off and any static jump found within 100 meter then device will not upload that false data to server.

SF<,A> <,B> <,C>#
A=ON/OFF; static drift filtering switch; default value: ON
B=10-1000m; maximum filtering distance; default value: 100m;
C=0-2000KM/H; any value exceeding this threshold will be fully filtered; a value of 0 means no filtering is applied;

GET Query the currently set parameters: SF#
SET - SF,ON,100,180#

FDRIFT "Speed Data Filtering"

Use case: if vehicle is moving with slow speed in narrow streets and not getting the data on server as per configured timer interval or moving is not clear then use "FDRIFT,off#" command and test one more time.

FDRIFT,[A][,B]#
A=ON/OFF; speed drift filtering switch; default: ON
B=10-1000(m); maximal filtering distance; default: 100(m);
Query current parameter: Fdrift#
Example: Fdrift,ON,1000#
Reply: OK!

Note: If vehicle is moving with slow speed (5 or 10 Km/h) & device is not uploading location data like E-riksaw then use fdrift,off#.

Please use following configuration and monitor the data for 1 or 2 days:

1. sf,off#
2. fdrift,off#
3. anglerep,on,5,2#
4. acc,on,0#
5. gpsdup,off#
6. HBT,1,1
7. timer,5,10#
8. speed,on,5,15,0#
9. sends,5#
10. pbsw,off#
11. level,5#
12. accalm,on,0#
Use case: if vehicle is moving with slow speed (2 or 5 Km/h) & device is not uploading location data, then use fdrift,off#.

Second approach:

1. sf,off#

2. fdrift,off#

3. anglerep,on,30,3#

4. acc,on,0#

5. gpsdup,on#

6. HBT,1,1

7. timer,5,10#

8. speed,on,5,15,0#

9. sends,5#

10. pbsw,off#

11. level,5#

12. accalm,on,0#

Third approach:

1. sf,on#

2. fdrift,off#

3. anglerep,on,10,2#

4. acc,on,0#

5. gpsdup,on#

6. HBT,1,1

7. timer,5,10#

8. speed,off#

9. sends,5#

10. pbsw,off#

11. level,5#

12. accalm,on,0#

Note: After both configurations if still facing the issue please share the Raw data (Hex logs) with device IMEI to this email: support@markongps.com

For Non-AIS Device, V5/VL149/Wetrack2/Wetrack-lite/GT800/EV02/ET300/Alite/PT06/GT06N/GT06F/G17/SK05

server,1,gps.markongps.com,5023,0#

LG300

server,1,gps.markongps.com,24102,0#

Wetrack140 – Standard, BSNL/APSAC/MH mining

server,1,gps.markongps.com,21104,0#

Wetrack140 – NIC

server,1,gps.markongps.com,21105,0#

Wetrack140 – CDAC

backupserver,1,gps.markongps.com,21106,0#

Teltonika

url - gps.markongps.com, port-8003

ITRIANGLE AIS140

url - gps.markongps.com, port-8002

Atlanta AIS140 {BSNL/ MH mining / APSAC etc..} | protocol version: AIS140_GPS_PROTO_V.1.4

url:gps.markongps.com, port:24107

Timezone

For Non AIS/NON AIS140 device: GMT,E,0,0#

For personal tracker (PG201 or GK309):
GMT,E,8,0#
server,1,gps.markongps.com,21100,0#

Dashcam JC261 Configuration Details

corekitsw,0

RSERVICE,rtmp://172.105.59.200:1936/live

UPLOAD,http://172.105.59.200:23010/upload

server,1,gps.markongps.com,21100

Dashcam JC371 Configuration Details

1. URLTYPE,2# (2 is for IOTHUB, 1 is for tracksolidPro)

2. SERVER,gps.markongps.com,21122,NA,NA,NA,DL12CU4979# { in last replace with orignal vehicle number}

3. RATATION,1,0,0,1080# (for Screen Mirroring)

4. UPLOAD,http://172.105.59.200:23010/upload {make sure using updated version V1.7.1.4, build date: 251204}

5. RATATION,2,0,0,720# {when facing issue with CH2}

In live streaming if facing date/time issue (like 2023):

Make sure firmware is latest {to check latest version details please visit: https://iconcox.in/fota-version/fota.html}

And use following commands:

TIMESYNC,AUTO#

VIDEOTIMEZONE,E,5,30#

Other useful URLs:

1. http://IP:8881/live/1/device_imei.flv (live streaming url using IOTHUB)

2. http://IP:8881/1/device_IMEI.history.flv (History streaming url using IOTHUB)

Wetrack140 BSNL/MH mining/GPCB/Himachal/Chandigarh/FCI/Vahan/etc & eSIM related query, eSIM top-up related query please contact:

1. Rahul Pathak (AIS/NON AIS devices support)
Phone: +91 9899628620
Email: rahul@markongps.com

(including Tracksolid and Tracksolidpro platform support & GPS device installation Guide, relay installation or issue, dashcam installation etc.)

2. Karishma Mehra (Wetrack140 Support)
Phone: +91 7428497890
Email: karishma@markongps.com

3. Ritu (Wetrack140 eSIM related support – activation / data & sms whitelisting / renewal etc.)
Phone: +91 7428497891

4. Abhishek Tripathi (Wetrack140 Support)
Phone: +91 9910012230
Email: abhishek@markongps.com

5. Mayank Srivastava (Tech Support AIS140 / Non AIS / OTA etc.)
Phone: +91 73035 20013
Email: mayank@markongps.com

Billing Related Query

1. Chander Negi
Phone: +91 9910447572
Email: accounts@markongps.com

For Dispatch Details (docket etc.)

1. Aman Sharma
Phone: +91 9650987438

2. Rishu Gaur
Phone: +91 8882777885

For Repairing Status or Details

1. Sanjay Mishra
Phone: +91 8178772372
Email: repair@markongps.com

Troubleshooting guide

If showing "searching satellite" then check where# first. In where reply you can check last fixed GPS date.

Second case "UART NO DATA".

Recently, we have found an issue with a few vehicles. After connecting the device to the vehicle battery or turning the ignition on, the GPS is not able to get a fix. This is due to electromagnetic interference.

Sleep Mode

Enable Sleep Mode

Disable Sleep Mode

GPRS Command Headers

Manual Network Switching (Wetrack140 – Taisys Esim)

Manual Network Switching (Wetrack140 – Sensorise Esim)

Latest Wetrack140 Firmware for Taisys/Sensorise ESIM

MAHAKHANIZ Ports for Markon

If device is not updating on MH mining portal then:

Available Ports (MAHAKHANIZ)

Chandigarh NIC

Bihar Mining and NIC Configuration

Bihar Mining and NIC Configuration (Second)

Vahan-Common-layer

Dehi NIC

Rajasthan NIC

APSAC Mining Configuration{Protocol TYpe BSNL}

Himachal Configuration{Protocol TYpe BSNL}

Odisha Configuration{Protocol TYpe NIC}

GPCB Command

West Bengal CDAC Configuration

Pondicherry

BSNL Backend Command

Standard FCI "FCIVLTS"

Haryana FCI "Map My India"

Haryana FCI FleetRobo

West Bengal FCI

NHAI

Wetrack 4-in-1 Firmware Configuration

Harsh Acceleration/Brake

Sharp Turn Alarm

OverSpeed Alarm

Displacement Alarm / Moving Alarm in Ignition Off Condition

Power Cut Alarm

Device (Internal) Low Battery Alarm

Ignition On/Off Alarm

Mileage

HeartBeat Packet Interval

Angle Upload

Device LED Sleep Enable / Disable

V5 / VL149 / GT800 / Wetrack2 / Wetrack-lite

Vehicle Battery data {external voltage packet 0x94} (on server value will be in Voltage)

Power Saving Command (Vehicle Battery Protection)

V5 RELAY Command (When showing searching satellite or GPS is not fixed – no speed limit in this command)

Vibration Alert Setup

Collision Alarm Commands: COLLIDE

V5 Dual IP or URL Server Command

V5/GT800/Wetrack2/GT06N/Wetrack-lite LockIP Command: LOCKIP#

HBT "HeartBeat" Data Packet Interval

VL149 Specific Commands

VL149 Dual IP or URL Server Command

VL149 LockIP Command: LOCKIP,ON#

GT800 Dual IP or URL Server Command

Wetrack2 Soft ACC Command

GPRS Command Example (Command from Server)

Decoded Hex Command(Relay#): 78 78 10 80 0A 00 00 00 00 72 65 6C 61 79 23 00 01 AB F7 0D 0A

Hex Response Example of Relay#: 79 79 00 11 21 00 00 00 00 01 52 45 4C 41 59 3A 30 02 B3 48 FF 0D 0A

V5/VL149 Current Consumption

Monthly Approx Data Consumption

SOS Number Configuration

Center Number Configuration

Server Configuration with IP/URL

APN Configuration

password,oldpassword,newpassword#

SENSORSET Command

Pbsw Command

(After enabling "PBSW" History location data comes with heartbeat packet – only for NON AIS V5/VL149 devices)

GPSDUP Command

(basically gpsdup command copies last fixed location & keeps sending with updated date and time when ignition is off or when GPS is not fixed – once ignition on and GPS is fixed then command has no impact)

SF "Static Data Filtering"

VL149 & V5(4G) SF "Static Data Filtering"

FDRIFT "Speed Data Filtering"

Clear History Data

Check Stored History Data in Memory

If facing Static drift/Jump issue in ignition off condition or in parking, please use following configuration and monitor the data for 1 or 2 days:

Please use following configuration and monitor the data for 1 or 2 days: