Speed Limiter Firmware Updates and Software Management

Modern speed limiters are not simple electromechanical devices that cut a cable at a fixed speed. They are sophisticated embedded computing systems — microcontroller-based platforms running firmware that manages CAN bus communication, speed signal processing, calibration algorithms, fault detection, and tamper resistance. Like all embedded software systems, speed limiter firmware evolves over time: new vehicle variants require support, bugs are identified and resolved, regulatory requirements change, and new features are developed.

Managing firmware across a fleet of speed limiters is an operational responsibility that many fleet managers have not historically given significant attention. As speed limiters become more capable — and as vehicles become more electronically complex — firmware management is becoming an important part of fleet compliance strategy.

What Is Speed Limiter Firmware?

Firmware is the software embedded in the hardware of a device — stored in non-volatile memory and executed directly by the device’s microcontroller. Unlike application software running on a general-purpose computer, firmware is closely tied to the specific hardware it runs on and to the real-time requirements of the device’s function.

For the AutoKontrol System 80, firmware performs the following core functions:

• Reading vehicle speed from CAN bus, wheel speed sensor, and/or GPS inputs
• Applying the calibration algorithm to convert raw speed data into an accurate vehicle speed value
• Comparing current speed against the programmed limit
• Generating the throttle intervention signal (CAN bus TSC1 command or pedal signal modification) when the limit is reached
• Monitoring power supply voltage, CAN bus integrity, and tamper indicators
• Logging fault events with timestamps and odometer readings
• Communicating with the diagnostic interface and, in TrackSpeed installations, with the ScorpionTrack Fleet telematics unit

Each of these functions is defined by the firmware. The configuration parameters (speed limit setting, calibration values, vehicle type) are data stored separately from the firmware itself, but the algorithms that use that data are entirely defined by the firmware version.

Why Firmware Updates Matter

New Vehicle Support

The commercial vehicle market introduces new models, new engine variants, and new CAN bus implementations continuously. A speed limiter firmware version released in 2020 may not correctly interpret the CAN bus messages of a 2025 truck model. Firmware updates extend System 80 compatibility to new vehicles, ensuring that operators who refresh their fleet are not faced with compatibility gaps that require hardware replacement.

Vehicle manufacturer software updates also occasionally change CAN bus message formats or introduce new ECU source addresses. AutoKontrol monitors these changes — through its manufacturer relationships and through diagnostic data from the SGH Connect installer network — and issues firmware updates to maintain compatibility.

Bug Fixes

All complex software contains bugs. In safety-critical embedded systems, the discovery of a bug — even one that manifests only in a very specific combination of circumstances — requires a prioritised response. AutoKontrol maintains a structured software development lifecycle that includes formal regression testing for all firmware releases. When a bug is identified in the field, a corrective firmware update is developed, tested, and released, and the affected vehicles are identified and updated.

Regulatory Updates

Speed limiter regulations evolve. Changes to type approval requirements, DVSA inspection procedures, or EU/UK regulations may require changes to System 80 firmware to maintain compliance. Firmware updates can implement regulatory changes without requiring hardware replacement, protecting the operator’s investment.

Feature Enhancements

As AutoKontrol develops new capabilities — improved GPS cross-reference algorithms, enhanced tamper detection, better integration with new telematics platforms — these are delivered through firmware updates to existing System 80 units. Operators who keep their devices current benefit from capability improvements over the life of the installation.

Update Methods

Wired Update via Diagnostic Port

The primary update method for System 80 units is via a wired connection to the vehicle diagnostic port (or directly to the System 80’s own diagnostic connector). AutoKontrol’s proprietary diagnostic tool presents available firmware updates, performs pre-update checks (battery voltage, current firmware version, vehicle variant), executes the update, and verifies integrity post-update.

This method requires the vehicle to be at a workshop or visited by a mobile SGH Connect engineer. The update process typically takes 10–20 minutes, including pre and post-update verification. During the update, the vehicle must not be driven — most systems implement an interlock that prevents the update if the vehicle is moving.

For small fleets, wired updates via SGH Connect service visits are straightforward to manage. For large fleets, the logistics of visiting each vehicle individually makes wired updates operationally significant.

OTA (Over-the-Air) Updates via TrackSpeed

For vehicles equipped with the TrackSpeed combined speed limiter and GPS tracking solution, firmware updates can be delivered over the air via the ScorpionTrack Fleet telematics unit’s cellular data connection.

OTA firmware updates work as follows:

1. AutoKontrol releases a new firmware version and makes it available on the TrackSpeed management platform
2. The fleet manager or AutoKontrol operations team schedules the update for target vehicles — typically to occur when the vehicle is stationary and the ignition is off, to avoid disrupting operations
3. The ScorpionTrack Fleet unit downloads the firmware package via its cellular connection
4. At the scheduled time, the telematics unit transfers the firmware to the System 80 via the internal CAN bus connection
5. The System 80 validates the package’s cryptographic signature before writing it to firmware memory
6. Post-update, the System 80 performs an integrity check and reports success or failure back through the telematics unit to the fleet management portal

OTA updates eliminate the need for workshop visits for routine firmware maintenance and enable consistent firmware versions to be maintained across a large, geographically dispersed fleet.

Fleet Version Management

For fleet operators managing many vehicles, maintaining a consistent, known firmware version across all speed limiters is important for both compliance and operational consistency. An inconsistent firmware landscape — where different vehicles run different firmware versions with different capabilities or bug fixes — makes diagnostics harder and compliance verification less confident.

The ScorpionTrack Fleet portal presents the current firmware version of each TrackSpeed unit, allowing fleet managers to:

• Identify vehicles running outdated firmware
• Schedule updates for specific vehicles or vehicle groups
• Verify update completion and flag any failures for follow-up
• Maintain a firmware update log for each vehicle as part of its compliance record

For non-TrackSpeed fleets, firmware version management is coordinated through SGH Connect service records, with AutoKontrol recommending update schedules aligned with annual inspection visits.

Version Control and Rollback

Firmware development follows a formal version control process. Each release is assigned a version number and associated with release notes documenting changes, bug fixes, and new vehicle support. Prior to general release, firmware is tested against AutoKontrol’s vehicle compatibility test suite — a programme of test vehicles covering the most common commercial vehicle platforms.

In the rare event that a firmware release introduces an unexpected issue, the previous verified version is available for rollback. For OTA-enabled devices, rollback can be executed remotely. For wired-update devices, a service visit is required. The ability to roll back rapidly is a critical feature of responsible embedded software management.

Cybersecurity Considerations

As speed limiters have become networked devices — connected via CAN bus to vehicle ECUs and, in TrackSpeed installations, via cellular networks to cloud platforms — cybersecurity has become a relevant design consideration.

Key cybersecurity measures in the System 80 firmware architecture include:

Cryptographic signature verification — every firmware package is signed with AutoKontrol’s private key. The System 80 will only accept and install firmware packages that carry a valid signature. This prevents an attacker from flashing unauthorised firmware onto the device.

Secure boot — at power-on, the bootloader verifies the integrity of the application firmware before executing it. A corrupted or modified firmware image is detected and the device enters a safe fault state rather than executing potentially malicious code.

Encrypted communication — communication between the System 80 and the ScorpionTrack Fleet telematics unit uses encrypted protocols. Data transmitted over the cellular network is encrypted in transit.

Authentication for configuration changes — any change to speed limit settings or calibration parameters requires authenticated access. Remote configuration changes require authentication at both the telematics portal and the System 80 level.

These measures ensure that the System 80 cannot be weaponised against the operator’s or driver’s interests through software, and that the tamper detection described in our guide to tamper detection and tamper-proof speed limiter design extends fully into the software domain.

For detail on how the CAN bus integration that firmware manages is structured, see our guide to CAN bus speed limiter interface.

To discuss firmware update services or upgrade your fleet to TrackSpeed with OTA capability, get a quote from the AutoKontrol team.