Haltech CAN System

Nexus Series Firmware Help › Connections › CANUpdated Sep 2026

Plugging a Haltech CAN device into the bus is only half the job. The Nexus ECU won't use it until you switch it on in the Haltech CAN System page in NSP. Here's what lives on that page, and how we set up each type of device.

What this page is for

The Haltech CAN System node in NSP is the ECU's list of Haltech-made CAN devices. Tick a device here and the ECU starts listening for it, adds its inputs and outputs to the lists you assign from, and lets you choose a DTC severity for it. That severity decides how seriously the ECU treats a device that drops off the bus, which matters more for a wideband feeding closed loop fuel than for a keypad.

The physical side is simple: every device connects to the ECU's CAN port directly or through a CAN hub. The general CAN settings, like which channel runs which protocol, live under CAN, and factory-car CAN is covered in vehicle CAN system.

Device by device

DeviceWhat to enableWhat you get
DashThe Haltech CAN supported dash tick boxThe ECU broadcasts data the dash can show
Wideband controllersThe WBC-1 and/or WBC-2 boxO2 sensor channels you can assign as inputs and use in O2 control
IO expandersBox A and/or Box BExtra inputs and outputs, labeled IOA or IOB
Thermocouple amplifiersThe TCA model and box letter you actually haveThermocouple channels you can assign to EGT and other temperature inputs
KeypadsThe correct keypad sizeButtons you can assign to functions
DynamometerMainline DynoCAN communication between ECU and dyno

Dashes

If you're running a Haltech CAN dash, tick the supported dash box. If the dash is connected and powered but every value reads zero, the dash firmware may need an update. Contact Haltech support or ask us and we'll help get it current. Our uC-10 guide covers dash wiring.

Wideband controllers

The single-channel WB1 brings one O2 sensor and the dual-channel WB2 brings two. Tick the WBC box for each controller you've connected, then assign each sensor where you need it, including O2 control for closed loop fueling. On a WB2, double-check which sensor is on which bank before you trust closed loop.

IO expanders

Tick Box A or Box B to match the expander you've connected. Its channels then show up as IOA or IOB in the input and output lists, and in the IO resource report on the functions page. If you're running two, make sure each box is set to its own letter.

Thermocouple amplifiers

Four variants can connect to a Nexus: two-channel TCA 2 as Box A or Box B, and four-channel TCA 4 as Box A or Box B. Check the label on yours before ticking anything, because picking the wrong one gives you missing or phantom channels. Once the probes are plugged in, assign each channel to its input in the navigation tree. We stock the TCA2 and TCA4.

Keypads

Pick the size that matches your hardware: 2 x 4 is two rows of four buttons (8 total) and 3 x 5 is three rows of five (15 total). Two brightness settings sit here too:

  • Backlight Brightness Level: the glow of the whole keypad.
  • LED Brightness Level: the indicator LEDs on each button.

If you share a keypad between the ECU and a dash, these brightness values are global. See multi-master CAN for how that works.

Dynamometer

On a Mainline chassis dyno, set this to Mainline Dyno so the ECU and dyno can talk over CAN. Leave it off otherwise.

Troubleshooting

SymptomUsually
Device's channels don't appear in the input listNot ticked on this page, or the wrong box letter chosen
Dash shows all zerosDash not enabled, wrong CAN protocol on that channel, or old dash firmware
CAN device DTCLoose DTM-4, missing termination, or the device isn't powered
Keypad buttons in the wrong placesWrong keypad size selected

FAQ

Do I need a CAN hub?

Only when you have more devices than free CAN connections. Plan the layout, including termination, before you buy.

Can I have two of the same device?

For IO expanders and thermocouple amps, yes, as long as one is Box A and the other is Box B.