Neoway protocol
Neoway OBD and telematics dongles using JT/T 808-style binary framing on TCP — distinct from GT06 SMS clones.
On Traxelio
What Neoway trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Neoway
Point this protocol at Traxelio
Point Neoway at Traxelio
-
1
Install SIM and seat OBD dongle
Use a LTE data plan. Insert the N2610, start the engine, idle 3–5 minutes until GNSS/modem indicators stabilize.
-
2
Apply Neoway server parameters
Use the manufacturer integration workflow (SMS or configurator) to set APN, server IP/domain, and TCP port — do not paste GT06 templates.
-
3
Aim at Traxelio TCP port
Configure the server host from BYOD and catalogue port 5269 once SMS templates are authored.
-
4
Confirm JT808-style registration
First packets should include
0x0100register /0x0200location IDs. If you see GT06 signatures, the wrong protocol was selected. -
5
Verify decode on neoway listener
Ensure positions arrive on the Go neoway handler (shadow 6269 during validation) before promising fleet activation.
Still offline after GPS lock
Neoway still not landing
- Device connects but payloads do not decode
Almost always wrong decoder class — Neoway JT808-style frames routed through GT06 parsers never parse. Map the listener to
neowayand inspect message IDs.- BYOD shows host/port but no SMS steps
Expected until Neoway SMS dialect is cited. Use the manufacturer integration guide for server programming; do not invent GT06 SERVER templates.