4G CAT.1 GPS Tracker for Electric Motorcycles and Low-Speed EVs OEM / ODM — we carry the protocol, your controller keeps the controls

What we actually make

Three functions are ours. Everything else on the vehicle is somebody else's job, and the page says so.

What the gateway relays — and what it does not do

This is the part buyers ask about first, so it is written plainly: the gateway relays those commands between the vehicle's own controller or instrument cluster and the cloud. The aircon and seat functions are implemented by your controller — we only carry the protocol.

Function on the vehicle	Who implements it	What we supply
Aircon / heating, seat heating	Your controller or instrument cluster	protocol interface supported — command relay only
Windows, mirrors (fold / heat)	Your controller	protocol interface supported
Lighting, lock, P-gear, three-speed, EPS	Your controller	protocol interface supported
Fault codes, protection state, vehicle status	Your controller	uplink of the status bytes it sends us
Positioning, mobile uplink, tyre pressure	Us	the gateway and the TPMS sensors
Anti-theft	Our manufacturing partner	module available through our partner — details on request

Model range

Three model numbers cover this product line. The pairing matters: the cloud box is the master, the BLE controller answers it.

Model	What it is	Position in the pair
VTC-100	Combined unit — one 4G cloud box plus one BLE body controller, supplied and tested as a pair	Primary configuration
VTC-101	4G cloud box — positioning, cellular link, and the telematics side of the system	Master
VTC-102	BLE body controller — the local node that talks to the vehicle's own controller and instrument cluster	Slave (answers the master within 20 ms)

The full specification sheet for this line is being finalised; items still open are marked TBC rather than filled in with a number. Ask us for the current revision.

Interface and protocol

These are the numbers that decide whether the gateway can be integrated at all. They are the same for every OEM build; the harness and firmware variant are not.

Item	Specification
Serial link to the controller	115200 baud, 8 data bits, 1 stop bit, no parity (8N1)
Frame format	start byte 0xAA · command code · data length · data payload · sum check · end byte 0x0D
Checksum	sum check over the command code through the last data byte
Cloud transport	MQTT 3.0 or above over a persistent TCP connection; the platform is the server, the gateway is the client
Topics	uplink C/UP/#device_id · downlink S/DOWN/#device_id
Device identity	one key per device — username, password and deviceid are issued per unit
Encryption	TLS 1.3 optional; a client credential can be issued if your platform requires it
Standards referenced	JT/T 808-2013 · GB/T 32960

If your platform already speaks one of those standards, tell us which and we will confirm where the gateway's own message set has to be mapped.

Voltage range

Eight voltage classes are supported, selected per build — one vehicle family per variant rather than a universal unit that guesses.

Supported classes	36 V · 48 V · 60 V · 64 V · 72 V · 80 V · 84 V · 96 V
How it is set	a configuration bit per class, set in the factory profile
Battery reporting	lead-acid voltage or lithium SOC, reported on the same uplink

A mis-set voltage class is the most common commissioning error on this product family. It is worth putting the vehicle's nominal voltage in the order, not just in the email.

OEM / ODM options

• Brand and label — your marking on the housing and on the packaging.
• Harness and connector — matched to your controller's existing plug, so the vehicle build does not need a new branch.
• Firmware variant — the command map fixed to your controller model, so field configuration is smaller and support calls are shorter.
• Payload and topic naming — your platform's field names, not ours, where the platform team prefers it.
• TPMS pairing — with or without tyre-pressure sensors on the same unit.

Status: small-batch production. We would rather say that than announce a product that only exists on a slide. Volume, lead time and pricing are quoted per project.

CE for this line is in progress. We do not claim any certification, approval or registration until we actually hold it, and we will say so in writing when we do.

Common questions before an OEM enquiry

Can the gateway read our controller if we do not have a protocol document?

Usually. Most electric-vehicle controllers in this class use a documented serial frame with a start byte, a command code and a sum check. What we need from you is a frame capture — one request and one reply for the values you care about — and we will confirm whether it maps to our command set before anyone quotes anything.

Do we have to buy the TPMS part?

No. The gateway is useful on its own for positioning and uplink. If you do want tyre pressure, the BLE sensors report to the same gateway, so it is one record instead of two platforms.

Can the anti-theft function be included?

The anti-theft module comes through our manufacturing partner. We will confirm what is available for your build rather than promise a function we do not make.