Home Apps
Platform
Tracking panel Zones and alerts Reports Mobile app Compatible devices Device catalogue Connects to other systems Developer access Our own maps Every client, separate Backups Service status Where your data lives
Your brand
Your domain and logo Your app in the stores Your website Security padlock and email What you need to start How long it takes Brands already running Your reseller panel
What improvement you offer your client
Road safety Anti-theft and recovery Fuel control Regulatory compliance Preventive maintenance Delivery reliability Working-hours control Cold chain School routes Asset control Onboard video Guard patrols Field work Tracking with no device Satellite coverage Automatic alerts Silent devices Connect to their system
Who to sell it to
Freight transport Passenger transport School transport Delivery and last mile Construction and machinery Agriculture Field services Food and refrigerated Vehicle rental Security and guarding
Pricing
How billing works Volume plans What's included Your margin Payment methods Annual prepayment
Resources
Your first 30 days Technical support Training Sales material Frequently asked How to start a tracking business What it costs to start Which devices to buy How to bill your client Which protocol your GPS uses What the PESV is The GPS is not reporting Look up an IMEI Is my device supported? Your carrier's APN Look up a list of IMEIs Compare devices How much data the SIM uses When 2G shuts down When do I break even? Quote with your brand
Contact Request Demo

The JT1078 (cameras) protocol

The vehicle video protocol: it does not send position, it sends pictures. It is a Chinese standard used by fleet cameras, among them Jimi IoT's JC series — JC181, JC182, JC371, JC450, JC451 — and the DC600.

Video does not travel the same path as position: they are two separate connections, and it consumes orders of magnitude more data. That is why a camera needs its own mobile data plan, not the tracker's.

Which port it comes in onOur server listens for the JT1078 (cameras) protocol on port 6232. That is the port you set on the device, together with the server address. Point it somewhere else and the data still leaves, but the server cannot read it.
Careful with what other sites tell youTwo traps measured in practice. The device announces itself with a 12-digit key but its own record stores 15, so you must register the one the device actually sends. And confirm how many days footage is kept before promising a customer anything.

Build the configuration command

We do not have this protocol's commands yetWe would rather tell you than make them up. We only publish the ones we have checked against the manufacturer's manual or against a real device. If you have them confirmed, send them to us and we will add them.

Devices that use it

Receive this protocol on your own platform

No server to set up and nothing to program: the platform already reads this protocol. You add the brand and the domain.

See how becoming a distributor works

Back to the lookup

Frequently asked questions

What is the difference between JT1078 and JT808?

JT808 carries position and vehicle status; JT1078 carries the picture. Many camera devices speak both at once, which is why they need two separate connections.

How much mobile data does a camera use?

Orders of magnitude more than a tracker. It is the mistake that costs the most money: quoting video on a tracking data plan. The camera's plan is separate.

Why does the platform not recognise my camera if the IMEI is right?

Because many of these cameras announce a 12-digit key while their own record stores 15. You have to register the one the device actually sends, not the one printed on it.