Kits and cameras

What is a kit

Everything Roudiy knows about a truck comes from its kit. Device Hub describes it in one line: JC371 dashcams + KD032 gateways in your fleet.

JC371 AI dashcam. It has 4G and GPS, runs AI on the camera image and talks to the driver with voice prompts; it has no screen. It records video to its SD card.
KD032 gateway. Plugs into the truck’s engine (ECM) port and reads engine data: odometer, RPM, fuel level, coolant, battery and fault codes.

A truck can run with the dashcam alone. The vehicle’s Live tab then shows Data source JC371 instead of JC371 + KD032, and engine values show No ECM data yet or Not available. Location, events and video still work.

Cameras and channels

The JC371 records up to three video channels. You pick a channel whenever you ask for video.

Channel	Camera	What it sees
CH1	Road	The road ahead. Used for ADAS events such as forward collision warning and lane departure.
CH2	Driver	The driver’s seat. Used for fatigue, phone and distraction events. Seen only by roles you allow.
CH3	Aux	An optional extra camera.

In Device Hub, each camera has a coloured chip:

Green: the camera works.
Red: the last snapshot failed.
Gray: not installed, or no snapshot yet.
Dashed: unknown, Unknown — kit has not connected yet.

Installation and the install check

You do not install kits yourself. If Device Hub is empty you see No kits yet — Kits are installed by Support. A Roudiy technician fits the JC371 and the KD032 in the truck and pairs the kit with the vehicle. An automatic install check then runs for up to 10 minutes and confirms:

Device online
GPS fix
CH1–CH3 snapshots
ECM data (odometer, RPM)

When the check passes, the kit becomes Active.

Kit status: where the kit is in its life

The kit status says where a kit stands, from the warehouse to retirement.

In stock

Allocated
Allocation failed

ActiveInstall check passed
OfflineNot reporting

FaultyMarked by Support

Retired

A kit moves between Active and Offline many times; Faulty is set by Roudiy Support.

Device Hub has a tab for the common views: All, Active, Offline, Allocated, Faulty and Retired.

Connection: is it reporting right now

Connection is separate from status and answers “can the kit talk to Roudiy right now?”

Online: the kit is connected and sending data.
Offline: the kit has stopped reporting. Last seen tells you when it last did.
Sleeping: offline because the ignition is off. This is normal: the dashcam sleeps when the truck is parked with the engine off.
Unknown: the kit has not connected yet.

Device Hub Refreshes every 30 s. A truck that is Offline in Fleet View shows its last known location. If a kit stays offline for 24 hours, the default alert rule Kit offline for 24 hours notifies your company admin.

Pairing and unpairing

Pairing links a kit to a vehicle, so its GPS, events and video belong to that truck. One vehicle has one kit. When you pair, only vehicles without a kit are listed. If you try anyway, you see This vehicle already has a kit. Unpair it first or pick another vehicle.

Unpairing breaks the link: New GPS data will not be recorded for this vehicle. History already recorded stays. You must unpair a kit before you can deactivate its vehicle.

Licences

Each kit has licences: Video, ADAS, DMS and FaceID. A licence that is not active is shown struck through with (not licensed) in the kit’s details.

Reboot

If a kit misbehaves, a user with the right permission can restart it: The JC371 will restart and go offline for a short time. If the kit is offline, the command waits: Device is offline — the command will be delivered when it reconnects (expires in 1 h). A command moves through Queued, Sent and Executed, or ends as Failed, Expired or Cancelled. Only a Queued reboot can be cancelled, and after a reboot there is a short wait before the next one.