Dash Cam with Sony STARVIS 2 Sensor: Technical Specifications for a Night-Capable Build
Pull the footage after an incident, and you find out what your dash cam is really worth. The daylight clips look fine. The one you actually need was shot at half past eight on a wet evening, and the plate is a white smear under a streetlight.
That failure is almost always the dash cam sensor, not the lens and not the encoder. A dash cam with sony starvis 2 sensor inside it starts from the part Sony built for those exact conditions, which is why so many OEM builds land there.
This post covers the dash cam technical specifications that decide the outcome: what the IMX662 and IMX678 actually give you, which dash cam sensor to specify for your scene, and the five things you still have to engineer yourself when you build a dash cam on an embedded module.
What You Get from a Module, and What You Do Not
A dash camera module is the imaging front end and nothing else. Image sensor, lens mount, ISP, and a standard interface over USB, MIPI CSI-2, or GigE. No card slot. No car power input. No housing.
An embedded dash cam is what you get when you take that module and design the rest around it. You control the sensor, the field of view, the recording policy, and the shape of the product. You also inherit the work the consumer unit hid from you.
That trade is worth making for a fleet system, for an OEM camera that has to fit a specific vehicle, or for a product the retail unit simply cannot do. It is not worth making to save money on one camera.
Why Every Dash Cam with Sony STARVIS 2 Sensor Stands Out in Low Light
Sony STARVIS 2 is a back-illuminated CMOS family designed for low-light video, and four of its properties map onto what a vehicle camera actually faces.
Sensitivity comes first. Back-illumination puts the wiring behind the photodiode rather than in front of it, so more of the light that arrives lands on silicon. In a low-light dash cam, that margin is the difference between a legible plate at dusk and a grey rectangle.
Then nir sensitivity. STARVIS 2 parts respond well into the near infrared, so a night vision dash cam can work from IR illumination in a cabin, or from street lighting alone on the road.
Dynamic range is third. Oncoming headlights against unlit tarmac, a tunnel exit at noon, low winter sun straight down the lane. Clear HDR and D-Log HDR hold detail at both ends of that range instead of surrendering one of them, and without that an HDR dash cam is just a camera that blows out every tunnel mouth.
So what sensor is best for dash cam work is a family question before it is a part number question. Pick STARVIS 2, then pick the resolution your storage can carry.
IMX662 Technical Specifications: The 1080p Option
The IMX662 is the 1080p dash cam option in the family, and most builds land on it for an unglamorous reason. A long recording loop has to fit on a card.
It is a 2MP sensor at 1920 × 1080 on a 1/2.8-inch optical format with 2.9 µm pixels. For a 1080p part, that pixel is large, and pixel area is where the low-light behaviour comes from.
A Starvis 2 IMX662 camera gives you 1080p HDR with Clear HDR and DOL HDR modes. Vadzo’s modules stream H.264, H.265, or MJPEG depending on the interface, and the strong NIR response means the same Starvis 2 IMX662 camera doubles as a cabin-facing night camera under IR light.
Optics are M12 S-mount, which matters more here than it does on a bench camera. An M12 lens dash cam can be specified around 105 degrees diagonal for a forward view, or taken out to a 200-degree FOV camera when a full cabin or a wide rear approach has to be in frame.
For a 1080p dash cam, the IMX662 is the sensible default. The storage arithmetic works, the night performance is the whole point of the part, and the lens range covers both channels you are likely to want.
IMX678 Technical Specifications: The 4K Option
The IMX678 is the step up, and you take it for reach rather than for light.
It is an 8.4MP sensor at 3856 × 2180 on a 1/1.8-inch format. That larger format is what lets it hold STARVIS 2 low-light behaviour while carrying four times the pixel count.
A STARVIS 2 IMX678 camera runs 4K at 30 fps with up to 110 dB of HDR, and it carries the same LED flicker mitigation and NIR response as its smaller sibling. A Starvis 2 IMX678 camera also supports PTP synchronisation across channels, which you need if a surround view has to line up frame to frame.
The case for a 4K dash cam is plate reading. At 1080p, a plate two lanes over and thirty metres back is a handful of pixels. At 4K it is often readable, and if your footage has to survive an insurance dispute, that difference is the whole point.
The case against it is storage and encoding load. Run the retention arithmetic before you put 4K on every channel.
The Four Vadzo STARVIS 2 Modules
The USB parts suit a self-contained unit with its own board; the GigE parts suit a vehicle with several cameras and one recorder.
USB modules for a self-contained dash cam
Both are UVC devices, so Windows, Linux, and Android hosts see them without a custom driver. On a Jetson or a Raspberry Pi, that saves real schedule time.
The MerlinPlus is the closer match to a dash cam because it is a dash cam with onboard storage in its own right. The microSD keeps writing even when the USB link drops, and dual-endpoint streaming lets the same connection carry a second stream for preview or on-device AI while the first one records.
Both take M12 lenses at roughly 105 or 200 degrees diagonal, with onboard dewarping on the MerlinPlus for the ultra-wide option. A USB dash cam module at 200 degrees is what you want for a cabin channel where the whole interior has to be in shot.
GigE and PoE modules for a multi-camera vehicle
Module | Sensor | Resolution | Interface | Notable | Buy Now |
Innova-662CRE | Sony IMX662 STARVIS 2 | 2MP, 1920 × 1080 | GigE with PoE 802.3af | 1080p HDR, ONVIF, H.264 / H.265 / MJPEG | |
Innova-678CRS | Sony IMX678 STARVIS 2 | 8.4MP, 3856 × 2180 | GigE with PoE 802.3af | 4K at 30 fps, up to 110 dB HDR, auto IR-cut, PTP sync |
A GigE dash cam channel is one Ethernet cable from camera to recorder, and because it is a PoE dash cam on 802.3af, that cable carries the power as well. In a bus or a truck, where every extra run has to be clipped along a headliner by someone standing on a seat, that halves the install.
A fleet dash cam build usually puts an Innova-678CRS forward for plate detail, Innova-662CRE units on the rear and sides where 1080p and a wide angle are enough, and one in-vehicle recorder pulling every stream over RTSP and ONVIF.
The Five Things You Still Have to Engineer
The datasheet stops at the interface.
Recording comes first. You need loop recording with sensible file segmentation, usually one to three minutes per clip, plus a lock mechanism that protects a clip when something happens, plus wear and capacity management on the card. Getting loop recording wrong is how a card dies at eight months, and nobody notices until they need the footage.
Power is second, and a vehicle electrical system is a hostile place to take power from. You are converting 12 V or 24 V down to 5 V for a USB module, or feeding a PoE supply for a GigE one, with a safe shutdown when the ignition goes off and transient protection that assumes the worst.
Third is telemetry. GPS gives you speed and location. A g-sensor or IMU gives you impact and harsh-driving detection, and since the g-sensor is what triggers the clip lock, it is not really optional. CAN bus is there if you want braking and indicator state alongside it.
Fourth is the enclosure: automotive-grade housing that holds the M12 lens and the board stack, mounts to the windscreen or dash, and survives heat and vibration without shifting focus.
Fifth is software. On USB, that means a host application that grabs the UVC stream, encodes it if needed, and writes it with loop and event handling. On GigE it means a recorder that consumes the RTSP and ONVIF streams, tags events, and offers playback to whoever asks for the footage.
None of this is exotic work. All of it is work, and it is why an OEM dash cam programme runs in months rather than weeks.
Which Module for Which Build
For a compact self-contained unit, take the Merlin-662CRS or the MerlinPlus-662CRS. USB 2.0 UVC connects to common SoCs without driver work, and the MerlinPlus handles continuous recording on its own microSD while the USB stream feeds preview or AI.
For a multi-camera fleet vehicle, take the Innova-662CRE and Innova-678CRS as PoE IP cameras, with the 678CRS forward and one central recorder handling storage, GPS, and telematics.
For an OEM-style hidden module, the Merlin-662CRS becomes the camera head inside your own housing, with a small, embedded board or telematics box in the dash taking the video and integrating CAN, GPS, and LTE.
The sensor question is already settled either way. STARVIS 2 for the light, then IMX662 or IMX678 depending on whether you need reach or storage headroom. Request an evaluation unit and record a night drive on your own route before you commit. Our engineering team can shortlist against your channel count, retention target, and mounting.
Frequently Asked Questions
What sensor is best for a dash cam?
For vehicle capture, the answer to what sensor is best for dash cam work is the Sony STARVIS 2 family, because a dash cam sensor has to survive the conditions dash cams actually meet. Back-illumination raises sensitivity for a night-vision dash cam; strong nir sensitivity helps in cabin and low-light scenes; and Clear HDR and DOL HDR make it a real HDR dash cam across headlights and tunnel mouths rather than one that clips. LED flicker mitigation matters just as much, since pulsed traffic signals and brake lights can otherwise disappear between frames. After that, it becomes a resolution question. Vadzo builds a dash cam with Sony Starvis 2 sensors at both tiers, the IMX662 at 1080p and the IMX678 at 4K, so you pick resolution without changing sensor family.
Do I need 4K or is 1080p enough?
It depends on what has to be legible. The dash cam technical specifications decide it: a 4k dash cam on a Starvis 2 IMX678 camera gives 3856 × 2180, usually the difference between a readable plate two lanes over and a smear, so it is the right call when footage has to stand up as evidence. A 1080p dash cam on the IMX662 covers the scene and the vehicle ahead at a quarter of the data rate, which is what makes long retention affordable. The Starvis 2 IMX662 camera’s 2.9 µm pixels on a 1/2.8-inch format also make it a strong low-light dash cam in its own right. Most fleet builds run 4K forward and 1080p everywhere else. Vadzo’s Innova-678CRS and Innova-662CRE are built for that split.
Can a camera module record on its own, or do I need a host?
Most modules need a host, but not all of them. A dash cam with onboard storage such as the MerlinPlus-662CRS writes to its own microSD, so recording continues even when the USB link drops, and dual-endpoint streaming lets the same connection carry a second stream for preview or on-device AI. Every other module streams to a host that does the writing, which means you supply loop recording, segmentation, and event locking yourself. A Gige dash cam channel always records centrally, since the stream goes over the network to a recorder. Across the Vadzo range, the MerlinPlus is the one that behaves most like a finished embedded dash cam out of the box.
What do I still have to build around the module?
Five things, and none of them ship on the camera: recording logic with loop, segmentation, and event lock; vehicle power conversion with safe shutdown and transient protection; telemetry including GPS and a g-sensor for impact detection, with CAN if you want vehicle state; an automotive-grade enclosure and mount that handles heat and vibration; and the host or recorder software that ties it together. That is what how to build a dash cam means in practice, and a dash camera module removes the imaging risk from that list, which is the part hardest to recover from if you get it wrong. Vadzo supplies the module and the SDK, so your effort goes into the system rather than the image.
USB or GigE for a dash cam build?
Choose USB when the processor sits beside the camera in one unit, which is the classic dash cam shape. A USB dash cam module such as the Merlin-662CRS is UVC, so Windows, Linux, and Android hosts see it with no custom driver. Choose GigE when several cameras feed one recorder across a large vehicle, because a PoE dash cam channel carries power and data on a single cable and runs to a hundred metres. For a fleet dash cam in a bus or a truck, that single-cable property usually decides it. An M12 lens dash cam is available either way, around 105 degrees for a forward view or as a 200-degree FOV camera for cabin coverage, so the optics choice stays independent of the interface.
