🧩 How to Send TurboLamik Transmission Data into Haltech via CAN (I/O Box Emulation)

Integrating a TurboLamik TCU with a Haltech ECU gives you the ability to monitor transmission data such as gear position, slip, trans temp and more — directly inside the Haltech software.

Rather than using custom CAN streams, TurboLamik uses a different approach: it emulates a Haltech I/O Expander, a method that requires no special CAN decoding or user-defined templates inside Haltech NSP.

This guide walks you through setting up that integration step-by-step.

---

🔌 Step 1: Connect TurboLamik to Haltech CANbus

• Wiring: Connect TurboLamik to Haltech’s CANbus (CAN 1 or CAN 2) using standard CAN H and CAN L wiring.

• Set CAN Profile in TurboLamik:

  • Set CANbus Profile to 8 (Haltech)

  • Set CAN Speed to 1 Mbps (Option 4) — this is the only CAN speed Haltech supports

• Enable CANbus in Haltech:

  • In NSP, go to Main Setup → Devices → CAN Bus

  • Ensure the CAN bus you're using is enabled

🧠 No external CAN termination resistors are needed — both TurboLamik and Haltech include internal termination.

---

⚙️ Step 2: Configure TurboLamik CAN TX to Emulate a Haltech I/O Expander

In the Custom CAN TX section of TurboLamik, apply the following settings:

1. Send ID = 704

   • This emulates Haltech I/O Box A

   • Use 705 for I/O Box B (if needed)

2. Analog CAN Out Maximum Value = 4095

   • Haltech expects a 0–5V signal to be scaled from 0–4095

   • ⚠️ Using 5000 (common for other ECUs) may cause errors

3. Enable "Send ID+0" Flag

   • This enables CAN transmission of the four analog values using Haltech’s CAN Switch Board (CSB) format

---

🧩 Step 2.5: Assign Parameters to the Four Analog Outputs

TurboLamik allows you to assign a wide range of internal parameters to the analog outputs that will be sent to Haltech. However, Haltech only accepts 4 channels via the I/O Expander interface — choose what’s most important for your build.

✅ Best practice: Choose values like Gear Target, Slip, or Program Selector to start.

 

 

---

🖥️ Step 3: Set Up Haltech NSP to Receive I/O Expander Data

✅ 3.1: Add the I/O Expander Device

1. Open Haltech NSP

2. Go to Main Setup → Devices

3. Click Add Device

4. Select I/O Expander 12 (CAN)

   • Assign it to the correct CAN bus (used in Step 1)

If you used Send ID 704 in TurboLamik, it will appear as I/O Box A

---

✅ 3.2: Assign Analog Inputs

1. Navigate to Inputs → I/O Expander 12

2. You’ll see Analog 1–4 listed

3. Click each input and:

   • Assign a label (e.g. “Gear Position” or “Slip %”)

   • Adjust scaling or filtering as needed to match what TurboLamik is sending

---

✅ 3.3: Use the Data in Logging or Strategies

Once configured, these inputs can be:

• Logged inside NSP

• Displayed on an iC-7 dash

• Used in tables, axis conditions, or safety strategies

Example uses:

• Boost limits by gear

• Engine limp mode if clutch slip exceeds safe limits

• Visual indicators for shift mode or converter lockup

---

🧠 Summary & Limitations

While the I/O Expander emulation is a clever and effective way to send data from TurboLamik to Haltech, there are known limitations — especially on Haltech’s side.

Haltech’s I/O Boxes were never intended for fast, time-critical control. They refresh data at 10 Hz (10x per second), which is too slow for:

• Real-time shift cuts

• Precise throttle blip control

• High-resolution torque modulation

🚫 Avoid using I/O Box data for real-time functions like blip or torque cut.

✅ What it’s good for:

• Logging

• Dash display

• Engine-side transmission safeties

For example:
You could set a limp mode if TPS > 30% and clutch slip > 10% for more than 5 seconds — a smart way to catch misconfiguration or failure before it damages the transmission.