SUPPORT & ROADMAP
What works today. What’s coming.
A straight answer, because ‘supports every ECU’ is a lie.
COMPATIBILITY MATRIX / SCROLL HORIZONTALLY ON SMALL SCREENS
CAPABILITY
STATUS
PLATFORM
NOTES
Haltech NSP CSV datalog import
DEMONSTRATED
Haltech NSP
Genuine exported logs processed
Haltech sensor characterisation
DEMONSTRATED
Haltech Nexus R3
Sensor-calibration workflow
Live ECU connection
IN DEVELOPMENT
—
Separate from file import
File-based calibration interpretation
IN DEVELOPMENT
—
Read-only
Calibration table editing
FUTURE DIRECTION
—
Fuel, ignition, boost, sensors
Direct ECU calibration read/write
FUTURE DIRECTION
—
Bench lock and readback verification intended
Additional standalone ecosystems
FUTURE DIRECTION
Link, Holley, others
Manufacturer-independent architecture
OEM tuning ecosystems
FUTURE DIRECTION
EcuTek, HP Tuners, others
Roadmap only; not validated support
DESIGNED FOR REAL PERFORMANCE HARDWARE
Built for serious engine management.
Initial product work is developing around genuine Haltech telemetry and sensor-calibration workflows, with a longer-term manufacturer-independent architecture intended to support additional standalone ECU ecosystems.
Manufacturer-aware engineering. Platform-independent ambition.
INITIAL DATA FORMAT FOCUS
HALTECH / NEXUS R3
An early data-format focus—not an endorsement, sponsorship, partnership, or claim of authorized integration.
DEMONSTRATED / HALTECH NSP FILE IMPORT + NEXUS R3 SENSOR CHARACTERISATION
Importing a datalog is not a live ECU connection.
Haltech is an early data-format focus — not an endorsement, sponsorship, partnership, or claim of authorised integration.
Calibration writes are intended to require explicit operator authorisation, compatibility checks, backups and readback verification.
NOW / DEMONSTRATED — Haltech NSP log import and Nexus R3 sensor characterisation.
NEXT / IN DEVELOPMENT — Live connection and read-only calibration interpretation.
LATER / FUTURE DIRECTION — Wider ecosystems, table editing and direct read/write.