Solutions · Trucks & LCV
Heavy-duty fleet stack — J1939, FMCSA ELD, and A/B OTA.
MOS4 ships J1939/HD-OBD/FMS via obdstacks-v2, FMCSA-certified ELD via the hours-of-service micro service, rear-face tachograph integration on C4Max EU, and A/B OTA with automatic rollback — so your team builds the fleet application, not the protocol or compliance infrastructure.
How MOS4 fits
Three capabilities for a heavy-duty fleet programme.
J1939, HD-OBD, FMS from one runtime
All heavy-duty protocols share one unified protocol API via obdstacks-v2. The multistacks pattern runs J1939 and HD-OBD concurrently. DTC acquisition is available for J1939 SPN faults and HD-OBD service 03. Stack definitions are JSON data files — PGN or SPN changes are data-file edits.
FMCSA-certified ELD via hours-of-service
FMCSA-certified ELD via the hours-of-service micro service. Code ported to gamma. Tracks all seven FMCSA HOS rule sets. HOS application available June 2026 — white-label via ekkofleet.com.
Rear tachograph integration on C4Max EU
C4Max EU stack ships with rear-face tachograph integration for EU regulatory heavy-duty fleets. C4Max is the primary EU/NA platform. Ekko Drive serves a complementary driver-cabin role.
FMCSA compliance
hours-of-service — all seven HOS rule sets.
The service hours-of-service micro service tracks all seven FMCSA
HOS rule sets, seven malfunction codes (P/E/T/L/R/S/O), and five diagnostic codes continuously.
Four FMCSA data-transfer channels: SOAP, email, USB, and Bluetooth. Certification test harness
ships in-repo.
| HOS rule | Limit | Reset |
|---|---|---|
| 11-hour driving | 11 hours driving after 10 consecutive off-duty hours | 10 consecutive off-duty hours |
| 14-hour window | 14-hour on-duty window after coming on-duty | 10 consecutive off-duty hours |
| 30-minute break | Break required after 8 cumulative driving hours | 30-minute off-duty or SB period |
| 60/70-hour limit | 60 hours / 7 days or 70 hours / 8 days on-duty | 34-hour restart |
| 34-hour restart | Restart 60/70-hour limit after 34 consecutive off-duty | 34 consecutive off-duty hours |
| Sleeper-berth split | SB split: 7+3 or 8+2 hours | Combined 10 hours off-duty |
FMCSA-certified ELD via the hours-of-service micro service. HOS
application available June 2026 — ekkofleet.com.
Platform metrics
Key numbers.
Reference architecture
A heavy-duty fleet programme on MOS4.
FAQ
Frequently asked questions
-
Which heavy-duty protocols does obdstacks-v2 cover?
J1939, HD-OBD, J1587/J1708, J1850, CAN-FD, and FMS — all share one unified protocol API. The multistacks pattern runs J1939 and HD-OBD concurrently without separate hardware.
-
Is the ELD FMCSA-certified?
Yes. FMCSA-certified ELD via the hours-of-service micro service. Code is ported to gamma. The HOS application is available June 2026 — white-label via ekkofleet.com.
-
Which platforms carry rear tachograph integration?
C4Max EU stack ships with rear-face tachograph integration. This is C4Max-specific.
-
What is the difference between C4Max and Ekko Drive?
C4Max is the primary EU/NA heavy-duty platform. Ekko Drive serves a complementary driver-cabin role. Both are available. C4Max scenario: 153 features confirmed. Ekko Drive: 151 features.
-
How does the HOS duty-status transition work?
MEP YAML policies trigger on DB key changes — engine power, speed, GNSS fix validity — and call HosService.SetDutyStatus. Carrier-specific HOS thresholds change via policy update, not a firmware release.
-
How does cellular connectivity work on sealed telematics units?
GSMA SGP.22 v2.2 LPA ships with the modem stack. Carrier switches operators by remote SIM profile swap — no physical access to the telematics unit required.
-
How does OTA rollback work in a truck fleet?
A/B rootfs with bootcount-based rollback. A failed OTA reverts without a workshop visit. Signed delta packages reduce over-air payload on cellular.
Bring your fleet programme.
Protocol mix, ELD requirements, EU tachograph scope, and OTA lifecycle constraints. We will sketch the MOS4 fit during the call.