FleetTech Pro — MNVR & Camera Master Reference

Platforms that send SMS / email from MNVR events

Key concept first: a traditional MNVR/MDVR rarely sends the notification itself. It reports alarm + GPS events (G-sensor, I/O input, SOS/panic, geofence, video loss, ADAS/DMS, low voltage) over its private protocol or JT808 to a platform — and that platform's notification engine sends the email or SMS. Most MDVRs can report to up to 8 platforms simultaneously, so the device can feed CMSV6 and a third-party engine at the same time.

The rule of thumb

Email is almost always native to the platform. SMS usually requires an SMS gateway (e.g. Twilio/an SMPP provider) or per-message credits configured inside the platform. A few all-in-one fleet platforms include SMS in plan.

Notification-capable platforms

Platform	Email	SMS	How it triggers
CMSV6 / CMSV7 (native MDVR platform)	Yes	Gateway	Alarm linkage rules on the platform fire email; SMS via configured gateway. Same family you provision directly.
Wialon (Gurtam)	Yes	Yes*	Notification engine on geofence, sensor, speed, alarm; SMS via account SMS or gateway. 1,380+ device types.
Navixy	Yes	Yes*	Instant alerts on MDVR events — accident, SOS, geofence exit; push/email/SMS.
flespi	Yes	Webhook	Ingests MDVR telemetry and runs notification/webhook logic; can forward to other engines or a custom SMS API.
GpsGate	Yes	Yes*	Rule-based event alerts; on-prem or cloud; SMS via plugin/gateway.
Traccar (open source)	Yes	Gateway	Notificators fire on alarm/geofence/device-status; email native, SMS via SMPP/gateway.
Mapon / GPSWOX / Key Telematics / Ruhavik / GPS-Trace	Yes	Varies	flespi-downstream and standalone engines; event-based email, SMS by integration.
Samsara / Geotab / Teletrac Navman (enterprise)	Yes	Yes	Turnkey safety alerts (often in-plan); proprietary hardware-friendly but relevant for clients comparing.

*SMS availability depends on the client's plan/region and whether an SMS gateway is connected. Always confirm before quoting SMS as included.

What you actually configure

On the device: which alarm types report and upload. On the platform: the rule (event → condition → recipients) and the channel (email/SMS). The handoff between them is where most "alerts not arriving" tickets live — verify the alarm is enabled on the device and the rule is linked to that vehicle.

Power & electrical

Three wires define every install. Get these right and 80% of "random reboot / won't power / battery drain / corrupt files" tickets never happen.

Constant +12/24V (B+, usually yellow): permanent battery feed, fused at the source (typically 2–5A). Keeps the real-time clock and any parking/buffer functions alive.
Ground (black): clean chassis ground or direct battery negative. A poor ground is the hidden cause of flickering video, noise lines, and brownout reboots.
ACC / ignition (usually red): the switched wire that tells the unit to boot/shut down with the key. This is the single most important wire to get right.

The ACC rule — prevention, not repair

Always tie ACC to a truly switched ignition source, never to constant power. Wired to constant 12V, the unit never shuts down → it drains the battery and skips its clean-shutdown routine, which corrupts the SD/HDD and causes the classic "files won't play / disk error." Tie ACC to switched ignition and the unit powers down gracefully every time.

Also verify

Voltage range: most MDVRs accept ~8–36V (covers 12V cars and 24V trucks). Confirm the unit's range before a 24V install.
Low-voltage protection: set the cutoff (e.g. 11.5V/23V) so the recorder stops before it kills the starting battery during parking mode.
Delay/shutdown timer: how long the unit keeps recording after ACC drops (0–min/hours) — set per the client's parking-surveillance need vs. battery budget.
Inrush/fuse sizing & fuse-tap quality: undersized taps and corroded crimps cause intermittent drops that look like firmware faults.

GPS / BeiDou antenna

Connector: typically SMA (check male/female; right-angle vs straight). Finger-tight only — over-torque cracks the center pin.
Placement: clear sky view — top of dash, parcel shelf, or roof (magnetic mount). Avoid burying it under metal, and beware metallic/ceramic windshield tint, which blocks the signal.
Ground plane: puck antennas want a metal surface beneath them; on all-plastic dashes, a small metal plate improves lock.
Verify lock: in the device's Net State / GPS status, locked = good. "Antenna unplugged / not connected" means a loose SMA or dead antenna. No fix → no positions → no geofence alerts downstream.

Diagnostic shortcut

If the platform shows the device online but with no movement/position, it's almost always GPS (antenna seating, sky view, or tint) — not the server link. The cellular and GPS paths are independent.

Cellular 4G — SIM, APN, antennas, server

SIM & data

Insert SIM with unit powered off; confirm form factor (often Micro/Nano on a carrier on a data/IoT plan). Disable PIN lock.
APN is carrier-specific and must be set exactly (name, and username/password if required). Wrong APN = "SIM present, no data, device offline."

Antennas

Main cellular antenna (and aux/MIMO on dual-antenna units) seated and routed away from the GPS antenna and noisy power runs.

Server / platform connection

Set Server IP or domain + port. For CMSV6, the device registration (gateway) port defaults to 6608.
Protocol: CMSV6 private protocol, or JT808 for third-party platforms. The device can hold up to 8 platform connections at once.
Confirm in Net State: cellular registered, server status connected/online, GPS locked.

CMSV6 server port map (open these on the firewall)

Login Server 6605/6606 · Gateway (device) 6607/6608 · Media 6602/6604 · User Mgmt 6603 · WiFi Download 6609/6610 · Storage 6611/6612 · Web 80/88/8080/8088 · FTP 2121, 2122–2124

WiFi — two completely different jobs

WiFi on an MDVR means one of two modes. Don't confuse them on a ticket.

AP / hotspot mode (config): the device broadcasts its own SSID; a phone/laptop connects to it to set up or live-view locally. Used at install time.
Client / STA mode (auto-download offload): the device joins a depot/garage WiFi when the vehicle returns, then bulk-uploads recorded files to the WiFi Download Server over LAN — no cellular data cost.

Auto-download setup

Device SSID/password must exactly match the depot access point.
WiFi Download Server configured (ports 6609/6610); a download rule links time range + alarm type to the device.
Best practice: upload alarm files only (not all footage) — full uploads saturate the link. Realistic LAN throughput ~3–6 MB/s.

Cameras, channels & video

Connection types you'll meet

Wired analog/AHD (most fleet MDVRs): 4-pin aviation connectors, power+video over one cable. Channels 1–4 (or 8). Most reliable.
IP cameras (higher-end MNVR): PoE/Ethernet, higher resolution, longer runs.
Wireless (2.4/5GHz paired) backup cams: transmitter on the camera, receiver at the monitor — convenient on trailers, more latency/interference risk.
WiFi cameras: join the recorder's or a local network; good for add-on angles.
4G standalone cams/dashcams: their own SIM + cloud, no separate recorder — effectively a 1-channel MNVR.

Stream & image settings

Main stream = high-res recording/local view (e.g. 1080P). Sub stream = low-res for remote live view over 4G (CIF/D1/720P) to save data.
Resolution / frame rate / bitrate per channel — the three dials that trade clarity against storage and data. Lower the sub-stream first to fix laggy remote view.
Audio format (G711A/G711U/G726) must match the platform or two-way audio/intercom fails.
OSD overlay: channel name, time, plate, GPS/speed stamped on footage for evidentiary value.

Triggers, I/O & backup-camera switching

Trigger wires turn raw cameras into a smart system — auto-switching views and firing the alarms that become SMS/email upstream.

Trigger	Wire to	Result
Reverse	Reverse-light +12V	Auto-switch to rear camera + on-screen parking lines while in reverse.
Left / Right turn	Turn-signal feeds	Pop the corresponding side camera; log lane changes.
Brake	Brake-light feed	Event marker / harsh-brake correlation.
SOS / Panic	Driver button (I/O in)	Flags an alarm event → platform notification (email/SMS).
G-sensor	Internal	Collision/harsh-event detection; sets pre/post-alarm clip + alert.
Speed	GPS (or pulse)	Overspeed alarm threshold; OSD speed stamp.

Backup camera specifics

Trigger wire taps the reverse-light positive so the view switches only in reverse (or set "always on" for a dedicated rear monitor).
Mirror / flip: rear cameras almost always need horizontal mirror so left/right read correctly to the driver; flip (vertical) compensates for upside-down mounting. These live in the camera/image menu.
Parking guidelines: enable/calibrate if the head unit supports overlay.
Wireless backup cams: pair transmitter↔receiver on the same channel; mount the transmitter clear of metal to reduce dropout.

Storage & recording modes

Media: SD card (smaller MDVRs), 2.5" HDD or SSD (MNVR). SSD survives vibration far better — recommend it for rough-duty fleets.
Initialize/format in-device before first use; a card formatted on a PC often won't index correctly.
Loop/overwrite: oldest footage overwrites when full — confirm it's on, or recording silently stops.
File segment length (e.g. 5–30 min) sets clip granularity for retrieval.
Recording modes: continuous, alarm-only, scheduled, or hybrid. Pre/post-alarm buffer captures seconds before and after an event.
Dual storage / mirroring on capable units writes alarm clips to a second card for tamper resilience.

Top corruption cause

Re-read Part 02: nearly every "disk error / unplayable file" traces back to ACC on constant power (no clean shutdown). Fix the wire, then reformat.

Universal menu map

Brands rename and reorder, but essentially every MDVR/MNVR/dashcam menu is this skeleton. Learn the map and you can navigate a model you've never seen.

System

Time / time zone / DST, time-sync source (GPS vs server), language, date format, device ID/plate, password & users.

Network

Server (IP/domain + port, protocol, up to 8 platforms) · 3G/4G (APN, dial) · WiFi (AP/client, SSID) · Net State (cellular/GPS/server status).

Record

Per-channel resolution, main/sub stream, frame rate, bitrate, audio format, schedule, mode (continuous/alarm/scheduled), pre/post-alarm.

Camera / Display

Channel names, OSD content, mirror/flip, brightness/contrast/saturation, preview layout, output mode.

Alarm / I/O

Input triggers (reverse, turns, brake, SOS), G-sensor sensitivity, speed/overspeed, geofence, video-loss, and the linkage (record/snapshot/upload/notify) each fires.

Storage

Format/initialize, overwrite, segment length, mirror/dual-write, disk health.

Maintenance

Firmware upgrade, reboot/auto-reboot, log export, import/export config (clone settings across a batch), factory reset.

Fleet efficiency move

Configure one unit fully, export the config, then import to the rest of the batch — only the device ID/plate and SIM differ. This is the backbone of profitable pre-provisioning.

Commissioning any unknown device + troubleshooting

The model-agnostic commissioning sequence

Power & ground (Part 02) — B+, ground, ACC to switched ignition; confirm clean boot.
Storage — insert, initialize in-device, set overwrite.
Cameras — connect channels; set mirror/flip and OSD; verify each feed.
GPS — seat antenna, confirm locked in Net State.
Cellular — SIM, APN, antennas; confirm registered.
Server — IP/domain + port (CMSV6 6608) or JT808; confirm online.
Triggers/alarms — wire reverse/SOS/etc.; enable alarm types + upload.
Platform rule — link the vehicle to a notification rule (email/SMS).
Export config for the rest of the batch.

Fast triage matrix

Symptom	First suspect
Device offline on platform	APN wrong, SIM data inactive, server IP/port typo, or cellular antenna.
Online but no location / no movement	GPS antenna (seating, sky view, tinted glass) — not the server.
"No signal" on a channel	Camera aviation connector, cable run, or channel disabled in Record menu.
"No sync" / files won't play	ACC on constant power → no clean shutdown → disk corruption. Fix wire, reformat.
Laggy/failed remote live view	Sub-stream too high for the 4G link — lower sub-stream resolution/bitrate.
Alerts not arriving	Alarm disabled on device, or platform rule not linked to that vehicle, or SMS gateway/credits.
Random reboots	Bad ground, undersized fuse tap, or low-voltage cutoff set too high.
Two-way audio fails	Audio format mismatch (G711A/U/G726) device vs platform.

Reseller / rebrand note

The vast majority of fleet-camera units sold through online marketplaces and third-party resellers are rebranded reference-design MDVR/dashcam platforms — they follow this exact skeleton with relabeled menus. Drilling into any specific model is mostly a matter of mapping its labels onto Part 09.

Field & Configuration Master Reference

Contents