This release note describes enhancements and fixes for CoreHub APK Version 3.8.503.
What's New in This Release?
What's New in This Release?
Enhancements:
Improved vehicle calibration and driver behavior configurations
Wired ignition for Engine Hours calculation when ECU data not available
Driver login events
Improved ECM malfunction detection on ELD
Enhanced Engine Hours and distance data validation logic
CoreHub reset logic improved
Fixed Issues:
Configurable speed threshold for movement detection
Improved Odometer source logic
Improved backwards GPS Odometer jumps
Engine Data internal monitoring
Available for Rollout | To come |
Enhancements
The following enhancements were completed for this release.
Improved Vehicle Calibration and Driver Behavior Configurations (CR-1906)
To reduce false driver behavior events, we improved the CoreHub calibration logic and application of driver behavior configurations. This applies to harsh cornering, harsh braking, and so on.
Wired Ignition for Engine Hours Calculation When ECU Data Not Available (CR-2087)
Added support for configuring Odometer and Engine Hours sources independently, allowing more flexibility in collecting these values from the ECU, GPS, or wired ignition. This ensures accurate Odometer and Engine Hours reporting even when the ECU provides only Odometer or only Engine Hours.
Driver Login Events (CR-2159, CR-2158)
Improved the CoreHub driver login feature so that driver login failure events are sent to 360 and the Drive application. Specifically, failure to login after 60 seconds from ignition.
Improved ECM Malfunction Detection on ELD (CR-2163, CR-1889)
We improved the reliability of ECM malfunction detection to ensure vehicles maintain compliance. Previously, when autodetection failed in certain scenarios, the ELD’s compliance malfunction monitoring logic didn't always raise a report. Now, auto-detection failures result in an ECM Malfunction event.
Enhanced Engine Hours and Distance Data Validation Logic (CR-1779, CR-2164)
Enhanced our ECU data validation logic to better handle anomaly Engine Hours and Odometer data received from the ECU. We added ECM data filtering logic for Total Engine Hours and Odometer to filter out sudden spikes and other abnormal readings provided by ECUs.
CoreHub Reset Logic Improved (CR-2281)
Sometimes resetting CoreHub when moving a unit to a different vehicle would not delete all the app data, as expected for a reset. We enhanced the logic for resetting and clearing all data when switching a CoreHub to a different vehicle.
Fixed Issues
The following issues were fixed for this release.
Configurable Speed Threshold for Movement Detection (CR-2017, CR-1804)
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 Odometer Source Logic (CR-1992)
In some J1939 installs, CoreHub would report 0 odometer from source 0. To fix this, we changed the J1939 odometer source address priority order for new installs from 00 to 17 (infotainment and dashboard odometer ECU).
Improved Backwards GPS Odometer Jumps (CR-2251)
When the battery power was less than 30%, the GPS odometer would use an outdated value when the wakeup alarm was initiated. This caused an odometer backwards jump. This issue was fixed.
Engine Data Internal Monitoring (CR-2195)
Added a guard to prevent outdated engine data and Engine Hours from processing and sending false internal monitoring alerts. This fixes units that showed high, abrupt changes to engine hours.