Module Software Updater

Firmware Updater & Installer

Choose your project and install firmware directly via USB-C. All projects support version selection.

Important: Use Chrome or Edge on desktop — Safari and mobile browsers aren't supported. Use a USB data cable (USB-C at the controller end); power-only cables won't work.
No cable after this one: from SpeedPulser v4.02, SpeedPulser Pro v4.02, Can2Cluster v3.24, Can2RPM v1.07, Steering Wheel Controller v1.05, AirLift v2.12 and usb2ip v0.6 onwards (and every S3 / C3 board release), later updates can be installed from the controller's own OTA tab — either straight from GitHub (join the controller to your home Wi-Fi in the Home WiFi card first) or by uploading littlefs.bin and firmware.bin from the release folder (an S3 / C3 board uses the folder ending -S3 / -C3, e.g. V5.01-S3; the controller refuses firmware built for the other board). USB is only needed for this first install, or if the web interface is ever lost (the controller then shows a recovery page at 192.168.1.1 with the same two uploads).

OpenHaldex Installer

USB flashing via ESP Web Tools
DevKit or S3 / C3 board? SpeedPulser Pro, the Steering Wheel Controller and the AirLift Controller now also come on an ESP32-S3 board, and Can2RPM on an ESP32-C3 board. The two need different firmware, so each has its own box below. A DevKit board has a separate ESP32 development board plugged into headers on the main PCB; an S3 or C3 board has the chip soldered flat onto the main PCB, with its own USB-C socket and BOOT / RESET buttons. On recent firmware the controller's OTA tab shows which board it is under Hardware. Picking the wrong box can't harm the controller: the installer checks the chip when it connects and refuses firmware made for a different one.

SpeedPulser Pro — DevKit board

USB flashing via ESP Web Tools

SpeedPulser Pro — S3 board

ESP32-S3 · USB flashing via ESP Web Tools

Multi-Function Steering Wheel Controller — DevKit board

USB flashing via ESP Web Tools

Multi-Function Steering Wheel Controller — S3 board

ESP32-S3 · USB flashing via ESP Web Tools

AirLift Controller — DevKit board

USB flashing via ESP Web Tools

AirLift Controller — S3 board

ESP32-S3 · USB flashing via ESP Web Tools

Can2RPM — DevKit board

USB flashing via ESP Web Tools

Can2RPM — C3 board

ESP32-C3 · USB flashing via ESP Web Tools

SpeedPulser

USB flashing via ESP Web Tools

Can2Cluster

USB flashing via ESP Web Tools

usb2ip

USB flashing via ESP Web Tools

Browser & cable requirements

  • Browser: Chrome (or Chromium based) or Microsoft Edge
  • Cable: A USB data cable (USB-C at the controller end)
  • Ports: Try a different USB port if it won’t connect
  • Close other tools: Serial monitors / other flashing tools can block access
If the device doesn’t appear, unplug it, wait 2 seconds, plug it back in, and try again. The most common failures are due to unsupported browsers, power-only cables, or other apps blocking the serial port. Make sure that you know your cable supports data, and that you’re using a supported browser. If it still doesn’t work, try a different cable or USB port. Shorter cables tend to work better.

Post-update checklist

  • Power cycle: Turn the OpenHaldex Controller off then back on after flashing completes
  • Connect Wi-Fi: Join the controller’s Wi-Fi network
  • Open UI: Visit 192.168.1.1 or openhaldex.local
  • Confirm: Check the hardware version and that the UI loads normally
  • Check settings: Ensure all settings are correct in the UI - remember that this is a fresh install, so any previous settings are gone.
If openhaldex.local doesn’t resolve, use 192.168.1.1 directly.

Common issues & fixes for them

  • “No compatible devices found” / nothing appears: Use Chrome/Edge on desktop, try a different USB port, and use a known-good data cable.
  • Permission popup doesn’t show: Make sure no other tabs/apps are using the serial port (PlatformIO serial monitor, Arduino IDE, etc.).
  • Install starts then fails partway: Swap cable/port, avoid USB hubs, and retry with the device unplugged/replugged. Shorter cables work better.
  • UI doesn’t load after install: Power cycle the controller, then connect to its Wi-Fi and open 192.168.1.1.
  • Wi-Fi connects but no page loads: Ensure your phone/PC is actually on the controller Wi-Fi (some devices auto-switch back to other Wi-Fi networks).
  • Device not detected / flashing won't start: Some devices require the boot button to be held while plugging in (or while pressing reset). Hold BOOT, plug in the USB cable, then release — then try connecting again in the browser.
Still stuck? Try joining the Forbes Automotive community Discord and ask for assistance. Alternatively, send us an email at sales@forbes-automotive.com.