This release note describes enhancements and fixes for CoreHub firmware version 3.9.508.
Available for Rollout | Proposed Phase 1 start: October 23, 2025 |
CoreHub Improvements
The following enhancements and fixes were completed for this release.
Out-of-Order Motion and Ignition Events Sent to Drive (CR-2786)
We fixed a timing issue that occasionally caused out-of-order Motion and Ignition On events to the Drive tablet, resulting in invalid Unidentified Driving (UD) records.
Unreasonable Time Duration Values Sent to Driver Efficiency Report (CR-2828)
We improved the logic for calculating Over RPM seconds to prevent populating the Driver Efficiency report with unreasonable time duration values.
Backwards Odo Jump Due to Backup Logic Failures When Redis Unavailable (CR-2203)
Fixed an issue where the Canbus Manager’s GPS odometer backup logic was prone to failures during Redis recovery, potentially causing negative odometer jumps.
Update the Location Based on Movement Detection (CR-2349)
When GPS is poor, CoreHub uses the last known GPS position. We now use movement detection to update the latitude/longitude positioning based on distance traveled.
Prioritize ECM Source 17 for New Installs (CR-1992)
For more recent vehicle makes and models, we have observed that ECM Source 17 appears to be more reliable. Moving forward, for new installs, we will prioritize selecting ECM Source 17. If it is unavailable, we will select Source 00 or the next available and reliable source.
Improved ELD Compliance (CR-1889, CR-2163)
We improved the reliability of ELD ECM malfunction detection to ensure the vehicle maintains compliance.
Fixed Timestamp Out of Order (CR-2093)
A timestamp out-of-order event caused motionStop events to be ignored. We fixed this so that motion events trigger motion ignition on/off instead of GPS speed.
Motion Stop Timer Duplicated (CR-2229)
The hysteresis time for the motion stop was duplicated, causing the device to wait twice as long to trigger ignition off based on the motion stop event. This issue was fixed to remove the duplication.
Configurable Speed Threshold for Movement Detection (CR-1804)
We introduced configurable speed thresholds for movement detection, enabling more precise detection of motion start/stop events, and thereby providing more accurate tracking of driver break times.
Improved Backwards GPS Odometer Jumps (CR-2251)
Previously, when the battery was lower than 30%, the payload of the wakeup alarm atom was outdated, causing an odometer backwards jump. We fixed this issue so that WakeAlarm uses the correct value.
Improved GPS Location Updates (CR-2457, CR-2627, CR-1987)
We improved the performance of GPS location updates so that they have fewer processing delays, resulting in reduced position malfunction events.
Improved Accelerometer Sensor Processing (CR-2541)
We improved the accuracy of accelerometer sensor data and reduced noise.
Incorrect Timestamps and Duplicated Events (CR-2353)
We fixed a race condition that resulted in sending incorrect timestamps and duplicated events.
Device Health Monitoring Improvements
The following enhancements and fixes were completed for this release.
Clean Up EV-Specific Data (CR-1913)
Improved logging and truncated irrelevant data.
Low-Battery Spamming Alert (CR-2492)
We fixed an issue in which excessive events could be generated when external power was disconnected, internal battery drops below 30%, and Redis is unavailable.
We improved system stability during simultaneous power and storage service disruptions.
Internal Monitoring Improvements
VIN Detection and Changes (CR-1795, CR-1831): Reduced the excessive VIN change alerts we were sending.
ECM Config Metric (CR-1817): Corrected metric that was previously reporting incorrect ECM configs, enabling us to capture ECM config issues within the fleet.
GPS Performance (CR-2355, CR-1953): Added advanced internal monitoring metrics and matrices for GPS performance.
Engine Data (CR-2195): Added a guard to prevent outdated engine data and engine hours from being processed, resulting in false internal monitoring alerts.
CPU Temperature Greater Than 95 Degrees (CR-2625): CoreHub now sends an alert if the CPU temperature is greater than 95 degrees for more than five minutes. This enables us to intervene by rebooting the unit if it is on the verge of a shutdown due to high temperatures.
Odometer Jumps (CR-2756): Improved metrics for ECM data including odometer and engine hours to reduce false positives and improve accuracy of our fleet-wide representation.
Vehicle Moving With No Location Updates (CR-2575): Added a monitoring alert when a vehicle is in motion for more than 30 minutes without location updates. This can help to better detect poor GPS and potential odometer jumps.
New Device Health Metrics (CR-1993, CR-1943, CR-1769): To provide enhanced reporting on the quality and accuracy of device location, distance, ignition, and ECU data.