How to configure a Motec ECU to work with a Haltech display dash

Nexus Software Programmer › Dash functions › Configuring for third-party ECUsUpdated Sep 2026

A Haltech display dash will happily show data from a MoTeC ECU, as long as both ends agree on which CAN bus they're on and how fast it runs. Here's how we set up MoTeC M1 and Hundred Series ECUs to feed a Haltech dash.

What you're setting up

A dash like the Haltech iC-7 (or the iC-7 OBD-II version) reads engine data over CAN. With a MoTeC ECU, three things have to line up:

  1. Wiring: power, ground and a CAN connection between the dash and the ECU.
  2. The dash: told, in NSP, that its data comes from a third-party ECU.
  3. The MoTeC ECU: transmitting on the bus the dash is connected to, at the right speed.

Step 1: wiring

Give the dash a good switched 12V feed and a solid ground, then connect its CAN High and CAN Low to the MoTeC ECU's CAN High and CAN Low pins on the ECU connector. High goes to high and low to low. Swapping them is one of the most common reasons a dash shows nothing.

If you'd like to avoid splicing into the ECU loom, the HT-130046 CAN adaptor loom is made for this. It terminates the Haltech CAN High (white) and CAN Low (blue) in a Superseal plug to suit the ECU side, and a DTM-4 socket that takes the CAN cable supplied with the dash. It also has red and black flying leads for switched 12V and ground. For a dash going into a car without other Haltech gear, the semi-terminated standalone iC-7 harness is another tidy option.

M1 owners: check the bus number

MoTeC M1 ECUs have more than one CAN bus. Wire the dash to the same bus you select for transmission in the M1 steps below, or the dash will be listening on a bus that isn't carrying the data.

Step 2: set up the dash in NSP

If your dash runs NSP, or has been updated to it, set its data source to a third-party ECU and choose MoTeC. The "third-party ECU CAN" part of sourcing data for dashes in NSP walks through the screen. If you're new to the dash side of NSP, navigating dashes in NSP is a good primer.

Step 3a: MoTeC M1 series

  1. Connect to the ECU online in M1 Tune.
  2. Open the All Calibrate worksheet.
  3. In the Calibrate pane, tick the Setup type so the setup parameters are visible.
  4. Go to ECU > Transmit > CAN Bus. Note which bus is selected, or if none is, pick a free one.
  5. Go to CAN > Bus X, where X is that bus number, and set Mode to 1 Mbps.

Step 3b: MoTeC Hundred Series (M400, M600, M800 and similar)

  1. Connect online using MoTeC ECU Manager.
  2. Open Adjust > General Setup > Communications > CAN Setup.
  3. Configure the CAN transmit settings so the ECU broadcasts the data set the Haltech dash expects. If you're not sure of the exact values for your firmware, ask us and we'll send the screen we work from.
  4. Save the map and restart the ECU so the new settings take effect.

Checking it works

Turn the ignition on and look for live values that change: engine speed at crank, coolant temperature climbing as it warms, throttle moving with the pedal. If some channels work and others don't, the link is fine and the question is which channels the MoTeC stream includes.

Troubleshooting

SymptomUsually
Dash powers up but shows no engine dataCAN High and Low swapped, wrong M1 bus, or dash not set to a third-party ECU
Data drops in and outBit rate mismatch, poor ground, or a missing CAN termination
Changes on a Hundred Series ECU didn't stickMap not saved, or the ECU not restarted afterward
Only some channels showThe channel isn't part of what the ECU transmits

FAQ

Can a Haltech dash work with other brands of ECU?

Yes. We have similar guides for Link, Syvecs and other ECUs.

Do I need the adaptor loom?

No, it just saves splicing. Any clean CAN High and CAN Low connection with good power and ground will do the job.