Meiligao Protocol · MVT340 / MVT380 / VT310 / VT600 reference
59 devices 3 brands Port 5009 (Traccar reference) · 20332 (legacy Wialon) TCP

Meiligao Protocol (MVT family · VT310 / VT600 / VT900 / MVT340 / MVT380)

Binary TCP protocol designed by Shenzhen Meiligao Electronics · the third pillar of Chinese OEM GPS protocols alongside GT06 and TK103. Often called "MVT" after the MVT-series fleet trackers that made it widespread.

Talk to integration team Browse 59 supported devices

3 min read · ~478 words

Quick answers

Is Meiligao the same as Meitrack?

Not exactly. Meiligao was the original Shenzhen OEM (VT and MVT series). Meitrack spun out as a separate brand and developed its own modernized protocol (CCE / MT-protocol). They share lineage but the wire formats differ · a Meitrack T1 or P99G does NOT speak Meiligao MVT protocol.

What's the Meiligao packet header?

$$ (two ASCII dollar signs, bytes 0x24 0x24). Followed by a 2-byte length, a 7-byte BCD device ID, a 2-byte command code, the body, a 2-byte CRC-CCITT, and \r\n. The BCD device ID is the giveaway · if you see $$ headers without BCD IDs, it's a different protocol that just happens to use $$ (uncommon but exists).

What port does Meiligao use?

Configurable. The Traccar reference is 5009. Many integrators run it on other ports for legacy reasons (Wialon historically used 20332). The device's adminip SMS command sets whichever port the server expects.

Does Meiligao support photo upload?

Some MVT-series firmware does · the MVT800 in particular accepts a camera module and uploads JPEG snapshots over the same TCP channel using extended command codes. The base MVT340 / MVT380 do not have camera support · they're position-and-IO devices.

Can I run Meiligao + GT06 on the same server?

Yes, on different ports. Meiligao on 5009 (TCP), GT06 on 5023 (TCP) · the listener binds each port to its respective decoder. Traxelio and Traccar both follow this pattern · one server, many protocol ports.

The Meiligao protocol (sometimes called the MVT protocol after the MVT-series devices it shipped with) is the binary TCP wire format used by Shenzhen Meiligao Electronics across their VT and MVT tracker lines · VT310, VT600, VT900, MVT100, MVT340, MVT380, and dozens of OEM rebrands. Meiligao is one of the three pillars of cheap Chinese GPS tracker OEMs (alongside Concox/GT06 and Coban/TK103), and the MVT-series fleet hardware introduced a generation of Eastern European and African operators to GPS-tracker integration.

Protocol-at-a-glance

  • Transport · TCP
  • Default port · 5009 (Traccar reference)
  • Encoding · binary, big-endian, packet header $$ (two dollar signs), terminator
  • Auth · embedded · the device ID is in every packet's identification field (no separate login)
  • Heartbeat · device sends a heartbeat (0x0A command code) on a configurable interval; server echoes
  • Spec · Meiligao publishes a PDF for integrators · the most-cited reference is the VT310 / VT600 protocol document v3.4

Packet structure (essentials)

Every packet has the same envelope:

$$ [LEN_HIGH] [LEN_LOW] [ID_BYTES x 7] [CMD_HIGH] [CMD_LOW] [BODY...] [CHK_HIGH] [CHK_LOW]
  • LEN = total packet length (2 bytes)
  • ID_BYTES = 7-byte device ID (BCD-encoded; the device's printed ID padded with leading zeros)
  • CMD = 2-byte command code (0x9955 = position, 0x0A = heartbeat, 0x4101 = login response, etc.)
  • BODY = command-specific payload
  • CHK = CRC-CCITT over the packet (excluding $$ and )

The 7-byte BCD device ID is what makes Meiligao distinctive · if you see $$ headers but the ID field is BCD instead of ASCII, you're looking at MVT-family traffic.

Why Meiligao matters

  • Fleet-OEM bridge · The MVT-series (MVT340, MVT380) was one of the first sub-$50 trackers with proper relay outputs, RS-232 fuel-sensor input, and configurable I/O · before that, those features were $200-plus Teltonika territory
  • Long-lived hardware · MVT380 units sold in 2014 are still running on 2G networks in markets where 2G sunset hasn't happened
  • Eastern-European adoption · widely deployed by Russian, Ukrainian, and Romanian integrators (Wialon-compatible decoder shipped early)
  • Meitrack lineage · Meitrack (the more visible brand today) spun out of the same team · the MT-series uses a different, modernized protocol but the lineage explains some shared design choices

Configuring a Meiligao device for any server

Two paths · SMS commands or the Meiligao Manager Windows configurator:

Manager path (preferred · most devices ship with USB-to-serial):

  1. Open Meiligao Manager
  2. Connect device via USB-to-serial cable
  3. Set IP/port to your server (your-server.com:5009)
  4. Set APN to your carrier's value
  5. Apply, power-cycle

SMS path (works on most MVT-series with a SIM):

adminip,000000,your-server.com,5009#
apn,000000,internet#
gprs,000000#

(000000 is the default password · change it if you've set one. Replace your-server.com:5009.)

After GPS lock and GPRS attach, confirm the first decoded position in Traxelio.

Supported devices in our catalog

Meiligao VT310, VT600, VT900, MVT340, and MVT380 are catalogued under protocol: "meiligao". The MVT380 is the headline model · 4-input / 4-output, RS-232 fuel sensor, relay, internal backup battery, broadly available second-hand at very low cost.

Setup walkthrough

  1. 1

    Insert SIM with data plan + airtime

    Confirm the SIM works for data in a phone first. MVT-series devices have a single multi-purpose LED · a dead SIM and a config issue look identical from the LED alone.

  2. 2

    Connect over USB-to-serial (recommended)

    Open Meiligao Manager on Windows, plug in the USB-to-serial cable, click Read Parameters. This is faster and more reliable than SMS for the first config · you see the full parameter table at once.

  3. 3

    Point the device at your server

    In Manager, set Main Server IP/host to your-server.com and port to 5009. Or via SMS: adminip,000000,your-server.com,5009#. The default admin password is 000000 · change it after first config.

    adminip,000000,your-server.com,5009#
apn,000000,internet#
gprs,000000#
  4. 4

    Change the admin password

    password,000000,<new_password># · default 000000 is a security liability on a SIM that could receive any SMS. Pick a 6-digit value and store it with the device record.

  5. 5

    Confirm first position arrives

    Send status,<password># and watch your server log for the heartbeat (command 0x0A) followed by the first position (command 0x9955) after a clean boot with GPS lock. No traffic after the reboot · re-check APN (silent failure mode #1).

  6. 6

    Don't have a Meiligao-compatible server yet?

    Traxelio decodes Meiligao MVT-family natively on port 5009. Send adminip,<password>,traxelio.com,5009# and the first decoded position can be verified in Traxelio · including relay-output and fuel-sensor channels on the MVT340 / MVT380. Or self-host Traccar · same decoder, same port.

Reference

Configuration reference

Parameter Value
Transport TCP
Default port 5009 (Traccar reference) · 20332 (legacy Wialon)
Encoding Binary · big-endian
Packet header `$$` (0x24 0x24)
Packet footer `\r\n` (0x0D 0x0A)
Authentication Embedded · 7-byte BCD device ID in every packet
Heartbeat Command `0x0A`, server echoes
Checksum CRC-CCITT over packet excluding header + footer
Message types 0x9955 (position) · 0x0A (heartbeat) · 0x4101 (login response) · 0x4001 (config request) · 0x4137 (server-to-device command)
IMEI format 7-byte BCD (device-printed ID padded with leading zeros, packed two digits per byte)
SMS password Six-digit numeric · default `000000` · changed via `password` SMS command
Configurator Meiligao Manager (Windows)
Spec name Meiligao VT310/VT600 Protocol Specification
Spec versions v3.4 (most cited)
Open-source decoder Traccar `MeiligaoProtocolDecoder` is the most authoritative open reference
Vendor Shenzhen Meiligao Electronics

SMS commands

adminip,000000,your-server.com,5009#

Point the device at a server (default password `000000` · replace if changed).

apn,000000,internet#

Set the SIM's APN.

gprs,000000#

Enable GPRS data session (some firmware needs this explicitly after APN change).

t030s***n,000000#

Report every 30 s when ignition is on, indefinitely (`***n` = no end condition).

password,000000,newpass#

Change the admin password from default · do this before deploying to a customer SIM that might receive arbitrary SMS.

status,000000#

Query GSM signal, GPS lock, battery, ignition state · returns an SMS reply.

output,000000,1#

Engage the first relay output (`0` releases). MVT340/MVT380 only · base VT310 has no relay.

Or skip the integration

Traxelio decodes Meiligao natively

Point your device at our endpoint, then verify the first decoded position in Traxelio. We handle the protocol, ack the packets, and serve the dashboards.

Plan a protocol cutover Talk to integrators

Protocol Capabilities

Data Points from Meiligao Devices

Traxelio processes all telemetry data sent by Meiligao trackers for comprehensive fleet insights.

Core Tracking

  • GPS Location
  • Speed
  • Altitude
  • Heading / Direction
  • Street Address
  • GPS Accuracy

Engine & Driving

  • Ignition Status
  • Odometer / Mileage

Sensors

  • Battery Level

Event Coverage

Alerts you'll get from devices on this protocol

Device online

The device is back online and transmitting data.

Device offline

The device has stopped reporting. It may have lost connection or power.

Device Moving

The vehicle is currently in motion.

Device Stopped

The vehicle is stationary.

Device overspeed

The vehicle is exceeding the set speed limit.

Geofence enter

The vehicle has entered a defined zone.

Geofence exit

The vehicle has exited a defined zone.

Alarm

Tow

Possible towing activity detected, check vehicle status.

Ignition On

The ignition is ON. The engine has started.

Ignition Off

The ignition is OFF. The engine has been stopped.

Long Idle

The vehicle has been idling for a long period.

All Models

Representative Meiligao Devices (59)

Start with the strongest matches, then use pagination or brand pages for the full compatibility list.

AVL-011

Meiligao

CT01

Meiligao

CT03

Meiligao

CT04

Meiligao

CT04-R

Meiligao

CT04-X

Meiligao

GSY007

Meiligao

GT 30

Meiligao

GT-110ES

Meiligao

GT-110K

Meiligao

GT-110M

Meiligao

GT-110P

Meiligao

Compatible Brands

Brands Using Meiligao Protocol

Meiligao

39 devices

Topten

16 devices

PT

4 devices

Common troubleshooting

Device sends one packet, server decodes garbage, then nothing

Almost always a header confusion · $$ is not unique to Meiligao (a few other protocols use the same bytes). Check the BCD device-ID field at offset 4 · if it's not 7 BCD bytes matching the printed device ID, the listener is auto-routing to the wrong decoder. Bind Meiligao to its own dedicated port instead of multiplexing.

MVT380 relay output engages but doesn't release after `output,<pw>,0#`

Relay-release is a separate command code and some firmware revisions reject the output,...,0# shorthand. Use the long form: output,<pw>,01000000# for release-output-1. Confirm with status,<pw># which echoes the I/O state.

Fuel-sensor readings arrive but values look like noise (jumping by 20% per second)

The MVT380's RS-232 input is sensitive to ground loops · if the fuel sensor and the tracker draw power from different points on the chassis, you'll see noise. Bond both grounds to the same point near the tracker. The sensor's manufacturer manual usually has the recommended wiring.

Explore More

Other Protocols

GT06

99 devices

H02

96 devices

Teltonika

84 devices

GL200

36 devices

Huabao

32 devices

GPS103

31 devices
View All Trackers

FAQ

Frequently Asked Questions

Is the Meiligao protocol open / publicly documented?

Meiligao distributes the protocol PDF to integrators on request (the VT310/VT600 spec v3.4 is the most cited). The open-source Traccar project ships a complete MeiligaoProtocolDecoder that handles all known message types · the most accessible reference for a working implementation.

Is Meiligao still being manufactured?

Yes · Meiligao continues to ship VT and MVT firmware revisions, though the brand's market share has shrunk as Meitrack (the spin-off) and Concox/Jimi (GT06) have grown. New device sales lean toward LTE-enabled MVT successors; the installed base of 2G / 3G MVT340 / MVT380 remains massive in second-hand and legacy fleet deployments.

What's the difference between MVT340 and MVT380?

MVT340 is the smaller, lower-cost fleet tracker · 2 digital inputs, 1 digital output, no analog input. MVT380 adds 4 inputs / 4 outputs, an analog input (for fuel sensor), RS-232 (for fuel sensor or driver-ID reader), and an SOS button. Same protocol, very different installation profile.

Does Meiligao work over 4G LTE?

Newer Meiligao MVT-LTE revisions ship with LTE Cat-1 modems and speak the same MVT protocol over the IP layer · transport-agnostic at the application layer. The bulk of the installed base is still 2G / 3G; replace fleet by fleet as carriers sunset older RATs.

Why is the device ID 7 BCD bytes instead of an IMEI?

Meiligao pre-dates the IMEI-as-device-ID convention. The 7-byte BCD field carries a 14-digit decimal ID printed on the device label · originally chosen for cheap firmware (BCD decode is one instruction on the 8051-class MCU the early MVTs used). You can resolve the BCD ID to the IMEI via the device's status SMS reply, which prints both.

Talk to integration team
T
Trax
Online
Say hello to Trax!