Nissan Stagea Series 2 (260RS) Haltech uC-10 Dash Install Guide
This guide outlines the installation process for a Haltech uC-10 digital display into a Series 2 WC34 Nissan Stagea 260RS, replacing the factory gauge cluster. Due to connector and wiring differences, especially when compared to the Series 1 Stagea or R33 Skyline, this guide is specific to the Series 2 model and may not be compatible with other variants.
Note: The factory instrument cluster uses different connectors than what is shown in some R33 or early Stagea documentation. This guide has been verified using a Series 2 260RS, which appears to have updated cluster wiring and connector shapes.
🔌 Powering the uC-10 Display
This installation assumes the Haltech uC-10 receives power and ground via the CAN cable directly from a Haltech ECU (e.g. Elite or Nexus series). If using a different power source, ensure proper fusing and ignition-switched power are used.
You will be removing the OEM instrument cluster completely, and tapping into the factory cluster wiring loom for critical signal inputs such as indicators, high beam, fuel level, and so on.
📎 Connector Overview & Pin Identification
Below is a layout of the uC-10's 34-pin connector alongside the relevant OEM dash plug wiring from the WC34. The OEM cluster loom has three main plugs. Carefully identify them by shape and keying. The diagrams shown are from the rear of the plug, with wire side facing you.
To keep the install reversible, it's strongly recommended to splice or tee into the OEM wires rather than cutting them. This allows for reinstallation of the factory cluster in the future if desired.
Tip: There is ample space behind the dash surround to neatly tuck the uC-10 wiring and unused connectors. Zip-tie everything securely to avoid rattles or damage. We also recommend using electrical tape around the connectors to avoid electrical damage or interference.
Ground Loop Note: As the transmission speed sensor was supplied with a ground from the OEM dash which has now been removed, a ground loop wire needs to be installed between pin 7 and pin 26 on the OEM cluster wiring to supply ground to the sensor, without it the VR signal will be too erratic and not read properly. The sensor ground link is optional. It links the uC-10 sensor ground to the body ground which the Fuel Level, VSS, and other dash sensors are connected to. We found it to slightly increase sensor accuracy.
Alternator Excite (charging light) Note: The uC-10 features a dedicated alternator excite pin, which can be utilized when the uC-10 completely replaces the factory gauge cluster. The uC-10 can supply the same resistance that the warning lamp would have done from the factory cluster without the need to wire in an external resistor. However, it is best practice (or if you are using a iC-7) to wire in a 100ohm resistor to excite the alternator regulator to charge now that the OEM dash charge light has been removed. This is the same ohm resistor fitted to the OEM dash and it is used if the charge light fails. This will produce a reliable 14.0v charge (13.5v under load). The resistor can be a regular 100ohm 1w resistor.
🖥️ Haltech uC-10 Dash Calibration and CAN Setup Guide
When integrating a Haltech uC-10 dash with your ECU—in this case, the Haltech Nexus S3—it's critical to configure the CAN communication correctly in both devices using the NSP software. A common mistake (which I made myself) is attempting to set up sensors like vehicle speed and fuel level inside the dash and send their values to the ECU. This approach will not work properly.
Instead, Haltech expects the uC-10 to act as an I/O expander, where the ECU takes ownership of the configuration and control of these inputs and outputs. This has major benefits: any advanced logic or functions you want to program in the ECU can directly utilize these inputs without relying on a loosely synced CAN message from the dash.
When properly configured, the ECU will broadcast sensor channels via CAN, and the dash will simply display them—nothing more. Below is a step-by-step explanation of how to configure CAN communications properly, followed by setup and calibration of the speed and fuel level sensors.
🧠 Step 1: Configure CAN in the Nexus S3 ECU
Correctly configuring the ECU’s CAN system to treat the dash as an I/O expander:
In the S3's NSP software:
Navigate to Connections > CAN > Haltech CAN System
Enable the Dash checkbox
Set the Dash Type to uC-10
📟 Step 2: Confirm CAN Settings on the uC-10 Dash
The dash should be set to listen for the ECU's broadcasted CAN channels:
In the uC-10’s NSP project:
Navigate to Connections > CAN > Haltech CAN System
Ensure the same CAN settings are enabled
Dash should have External IO Control enabled only if the ECU is using those inputs directly
🏎️ Step 3: Vehicle Speed Sensor Setup
You’ll configure the speed input in the ECU, not the dash. Below are the relevant settings.
🛠️ Wiring and assignment:
Sensor Type: Reluctor
Edge Select: Falling
Input Pin: SPI2 on Dash (controlled by ECU over CAN)
Optional pulse arming thresholds
🧮 Calibration:
Main Source: Drive Train
Calibrate using known speed vs pulses (e.g., GPS or roller dyno)
In this example:
8636 pulses/mifor Drive Train sensor
Filter set to 100 ms to smooth noisy signal
⛽ Step 4: Fuel Level Sensor Setup
Just like with vehicle speed, the ECU owns this channel when configured correctly.
🧪 Wiring and assignment:
Input Type: Analog - Voltage
Sensor Type: Percentage
Pull-up Enabled: 240 ohm
Connected to: AVI1 on Dash, controlled via CAN by ECU
📐 Calibration:
0.09V = Full Tank (100%)
1.00V = Empty (0%)
Set the correct volume of the tank (e.g., 70L)
With this setup, your uC-10 dash behaves as a smart peripheral, letting your Nexus ECU make full use of the additional I/O channels while maintaining a clean and reliable CAN data stream for display. This enables future expansions like warning triggers, mapped functions, or advanced controls all handled through the ECU.