Custom
Electronics for the Fleets, Networks, and Vehicles That Keep the World
Moving
From J1939-integrated commercial vehicle telematics gateways to FMCSA ELD-compliant electronics to transit automatic passenger counting hardware — Ankh builds transportation hardware around the fleet constraint set: ISO 16750 vehicle environmental qualification, MIL-STD-810 vibration, J1939 CAN Bus integration at the PGN level, and the real-time data demands of large-scale fleet operations.
The Challenge
Commercial Fleets Need Hardware Built for the Vehicle Environment — Not Consumer IoT Bolted to a CAN Bus
Commercial vehicle fleets operate at the intersection of three converging pressures simultaneously. Regulatory compliance requirements — ELD mandates, driver hours enforcement, emissions reporting — demand continuous, reliable data from every vehicle in the fleet, and an ELD that fails a roadside inspection means a driver out-of-service violation, a carrier compliance record entry, and a FMCSA safety rating impact. Safety mandates — ADAS adoption, driver monitoring requirements, speed limiter regulations — require real-time, sub-100ms processing in vehicle safety electronics. And operational efficiency pressure — fuel cost, driver productivity, asset utilization — makes fleet telematics data a commercial imperative, not just a compliance exercise.
Off-the-shelf telematics hardware was designed for the average fleet, the average vehicle type, and the average regulatory environment. Not for a mixed fleet of 47 different vehicle types from 12 OEMs, each with its own J1939 implementation and proprietary CAN Bus parameters. Not for a specialized cargo monitoring requirement that no standard trailer tracker addresses. Not for a transit authority with specific APC counting accuracy and GTFS-Realtime location update rate requirements that commercial fleet hardware cannot meet. And not for the ISO 16750 and SAE J1455 vehicle environmental qualification that separates hardware that survives in a commercial vehicle over a 10-year service life from hardware that fails within months of a maintenance bay high-pressure wash.
Ankh builds transportation hardware around the specific fleet constraint — vehicle type mix, regulatory jurisdiction, CAN Bus protocol complexity, and fleet management platform integration — rather than forcing fleet operations to adapt to generic hardware limitations. We understand the difference between a J1939 PGN and a proprietary OEM parameter, between an ELD and a GPS tracker, and between a dashcam and a compliant driver monitoring system with sub-100ms drowsiness detection latency.
Transportation Hardware We Engineer
From J1939-integrated telematics gateways to FMCSA ELD electronics to transit APC hardware — purpose-built for the vehicle environment and compliant with the regulatory frameworks governing commercial fleet operations.
ISO 16750 and SAE J1455 thermal range (-40°C to 85°C), vibration, and EMC design for the commercial vehicle electrical environment. IP54 enclosures for cab-mounted hardware subject to high-pressure washdown. MIL-STD-810 vibration qualification for frame-mounted hardware transmitting continuous road shock and engine vibration. Connector selection for thousands of mating cycles by drivers and maintenance crews across the vehicle service life.
J1939 PGN decoding across 47+ vehicle types from 12+ OEMs — standard J1939 messages and proprietary OEM parameter groups decoded from reverse-engineered vehicle CAN Bus captures. DM1 active fault code monitoring with manufacturer-specific fault code libraries. Multi-network CAN Bus architectures on modern trucks and buses. OBD-II mode 01-09 data access with protocol auto-selection for mixed light commercial fleets.
Edge AI firmware for real-time driver monitoring — drowsiness classification at greater than 95% sensitivity with less than 5% false positive rate, sub-100ms end-to-end camera-to-alert latency. Forward collision risk assessment, lane departure warning, and automatic emergency braking interface firmware running on ARM Cortex-A with dedicated NPU. FreeRTOS real-time kernel for deterministic sub-100ms vehicle safety system response.
Automatic passenger counting hardware with greater than 95% NTD counting accuracy, validated against manual counts per transit authority procurement specifications. GTFS-Realtime location transponder firmware with sub-30-second update intervals. NTCIP-compliant transit signal priority electronics. Contactless fare collection reader hardware with sub-300ms transaction time at peak crowding conditions.
Battery state of health monitoring firmware for EV commercial fleet conversion programs — cell voltage balancing, state of charge estimation, degradation trend analysis. Charging infrastructure management hardware for depot and en-route charging. SAE J2735 V2X communication firmware for DSRC and C-V2X SPaT and MAP message processing. AV sensor interface electronics for LiDAR, radar, camera, and ultrasonic fusion platforms.
TMS middleware connecting custom hardware to McLeod, TMW, Oracle Transportation Management, and SAP TM. Real-time fleet tracking, trip history, driver behavior scoring, IFTA fuel tax mileage calculation, and regulatory compliance reporting. OTA firmware update systems for overnight fleet-wide rollouts across thousands of vehicles via LTE push with rollback capability for safety-critical vehicle electronics.
Platforms & Protocols
The Technology Stack Behind Commercial Vehicle Electronics
Why Engineering Teams Choose Ankh
J1939 Fluent at the Firmware Level
PGN decoding across 47 vehicle types, proprietary OEM parameter mapping alongside standard J1939 messages, multi-network CAN Bus architectures on modern trucks and buses, DM1 active fault code monitoring with manufacturer-specific fault code libraries. Not a CAN shield and a library — a firmware team that has reverse-engineered proprietary OEM CAN Bus messages and built telematics hardware that extracts real fleet intelligence from vehicles the OEM never intended to share data from.
FMCSA ELD Compliant by Design
Hours of Service electronic logging firmware built to the FMCSA technical specification from the first line of code: CMV engine synchronization, driver authentication, RODS generation, roadside inspection Bluetooth and web services transfer protocol, and the specific timing and data accuracy requirements that determine whether an ELD passes FMCSA certification testing. ELD compliance is not a software feature — it is a firmware architecture discipline, and an ELD that fails a roadside inspection generates consequences that cost more than the entire telematics hardware program.
Vehicle Environmental from the First Schematic
ISO 16750 and SAE J1455 environmental design: -40°C to 85°C operating range, IP54 for cab-mounted hardware subject to high-pressure washer exposure in vehicle maintenance facilities, MIL-STD-810 vibration qualification for hardware mounted on frames that transmit road shock and engine vibration continuously for the vehicle's operating life, and EMI design for the high-transient electrical environment of commercial vehicle charging systems and high-power inverters. Hardware designed to survive what a commercial vehicle actually does to electronics.
Fleet Scale from 50 to 50,000 Vehicles
OTA firmware updates across the entire fleet overnight via LTE push, remote diagnostics and health monitoring from the fleet management platform, hardware architecture that does not require re-engineering when a 50-vehicle pilot becomes a 5,000-vehicle national deployment, and TMS integration middleware that connects to McLeod, TMW, Oracle, and SAP without rewriting the hardware firmware for each platform.
FMCSA ELD and J1939 Telematics Gateway for a National Carrier
Custom FMCSA-certified ELD and fleet telematics gateway deployed across a 3,400-vehicle mixed fleet — supporting 23 distinct vehicle types from 8 OEMs with vehicle-specific J1939 and proprietary CAN Bus parameter libraries, FMCSA ELD technical specification compliant HOS recording, real-time GPS and sensor data streaming at 1Hz to the carrier's McLeod TMS platform, and OTA firmware update via LTE for overnight fleet-wide updates.
Start a Similar ProjectBuilding electronics for transportation fleets? Let's move.
J1939 firmware at the PGN level and FMCSA ELD compliance from the first architecture review. Vehicle environmental design to ISO 16750 and MIL-STD-810. Full-stack delivery from the telematics gateway on a truck cab to the TMS platform in the carrier operations center.
Quote your project