The top of the line: three channels and a 1.0 TOPS NPU running Linux.
H.264 only: the clip weighs about twice an H.265 one, which matters on the SIM, not on the disk.
01 — Specification
Transcribed from the manufacturer's own product page. Certificates are issued per device, not per manufacturer — ask us for the certificate of this model before you commit to a market.
The factory datasheet for the DR03 (PDF) — the original, on the manufacturer's own server.
02 — What it is, physically
Everything here is transcribed from the manufacturer's dimension drawing and I/O table. It is the half of the specification an installer needs and the half nobody publishes.
The manufacturer's datasheet (PDF) — every figure in this section came out of it.
| Colour | Signal | What it does |
|---|---|---|
| Red | V+ | Permanent 9–36 V. Fuse it at the take-off, not at the device. |
| Orange | ACC | Ignition sense. This is the wire that decides when the camera sleeps, and the one most often taken off a fuse that is live with the key out. |
| Black | GND | Chassis earth. A painted bolt is the commonest reason a camera reboots on a cold start. |
| White | SOS | Panic input, pulled to ground by a button. The clip it saves is the one that goes to the insurer. |
| Grey | Left turn / DIN_H1 | Indicator sense, so a lane-departure warning knows the driver meant it. |
| Purple | Right turn / DIN_H2 | The other indicator. Same job, other side. |
| Yellow | Fuel− out | Low-side output for a fuel-cut relay. It switches the relay, never the pump. |
| Brown | ADC | Analogue input: a capacitive fuel sender, a temperature probe, a body switch. |
7 lines in, 1 line out. Colours are transcribed from the manufacturer's own drawing and are not a substitute for a multimeter on the first vehicle of a batch. The long, thin one: 140 mm across and 28 mm deep, which is what lets it sit along the top of the screen behind the mirror rather than below it.
03 — Through the OBD port
Not one device in this catalogue has an OBD-II connector or a CAN transceiver. That is worth knowing before a tender is answered, because “OBD” in a specification usually means two different jobs and only one of them is possible with this hardware.
Pin 16 of the SAE J1962 connector is battery positive (12 V on a Type A, 24 V on a Type B), pin 4 is chassis ground and pin 5 is signal ground. An OBD take-off lead gives V+ and GND with no splicing, which is why hire fleets and short-term fits use one. Two catches: on most vehicles that pin is live with the key out, so ACC still has to come from a switched fuse, and a lead hanging off the column gets kicked loose.
Road speed, engine RPM, odometer, engine hours, fuel level and fault codes live on CAN, on pins 6 and 14. There is no CAN on any of these devices, so none of it reaches the camera. Speed and position come from the GNSS receiver instead, and harsh-driving events from the on-board accelerometer.
Discrete inputs and the analogue line on every model: ignition, indicators, a panic button, a fuel sender on ADC. On the recorders and the EH15-V2 it goes further — brake and door inputs, 1-Wire for driver identification, and RS485 for the sensor bus. A CAN or FMS gateway on RS232 is the obvious next step, and we have not tested one: whether BSJ's firmware parses a third-party gateway is a question for them, and until somebody runs it on a bench this site is not going to claim it works.
If a customer's specification says OBD, ask which they mean. Powering off the port takes a €10 lead. Reading the bus needs a device that has CAN on it, and that is a different box beside this one, not this one.
Pinout from the SAE J1962 connector tables; I/O from each model's own datasheet, linked above.
04 — What it means in service
The platform speaks the camera protocol and is tested end to end against a device simulator. It has not yet run against this model on a bench — the first real camera is the milestone we are working to, and we will say so here when it passes.
Not in Wialon's device list yet — the vendor is adding the current models. It runs on FleetSight regardless.
flespi parses BSJ telemetry for one tracker only and no video; Navixy has no BSJ connector yet.
The full matrix →Camera-class devices run from €145 to €189 to the integrator, by annual volume. The exact figure for this model is on the current price list — it moves with the exchange rate and the batch.
The tiers and what is included →Nothing streams in the background. Over the SIM the camera sends telemetry, events and one frame per event — around 40 MB a month; a clip goes up only when someone asks for it, and only for the window they asked for. That is roughly €0.12–0.23 of cellular data a month per vehicle, against the €9 a month a stream-everything architecture spends before anybody has watched a thing.
Forty-five to ninety minutes in a van, at €90–170 of auto-electrical labour, and the last step is the one that gets skipped: a vehicle is not fitted until a frame from it has reached somebody's screen.
The seven steps, and what moves the price →The camera it is quoted against is usually a Streamax: €284–397 ex VAT at a European distributor, and their cloud is €4.49–11.21 a vehicle a month on top of that.
Against Streamax, priced out → All eight comparisons →Put the DR03 in a vehicle before you commit to a batch.
Two demo units, configured for the platform you run and the vehicle you fit, with the certificate position for your country in writing. Tell us the fleet and we quote the configuration rather than the catalogue.
05 — Others in this class
Specification read from the manufacturer's page on 20 September 2026: bsjiot.com/DR03 . Photo by the manufacturer. If a figure here disagrees with the datasheet you were sent, the datasheet wins and we want to hear about it.
Tell us the platform you run, the vehicles you fit and roughly how many cameras a year. You get the current price list, the certificate list for the models you care about, and two demo cameras configured for your platform before they ship — at your own trade price, credited against your first order.
Or write to [email protected]
