Wi-Fi communication is another method for connecting the Nexus Plug-in ECU to your laptop, serving as an alternative to a USB connection once the Wi-Fi module is enabled.
To set up your Wi-Fi connection follow these steps:
1. Open NSP and connect your Nexus Plug-in ECU using the provided USB-C cable.
2. Click on ‘Connections’ in the navigation tree and enable the Wi-Fi module.
3. Under ‘Connections’, select ‘Wi-Fi’ to set up your SSID and password. Note that your SSID must be at least 1 character long, and your password at least 8 characters.
4. Click ‘Apply’.
5. Power up the ECU using main power (ignition switch on), then go to your computer’s Network settings. Connect to your Nexus Plug-in ECU by selecting your chosen SSID and entering your password.
NOTE: The Wi-Fi antenna is internal on the Nexus Plug-in ECU. The unit must be powered by the main power source for Wi-Fi communication. Up to two computers can connect to the ECU via Wi-Fi, and one via USB-C, at any given time. When the Wi-Fi module is disabled, it is completely inactive and held in an OFF state.
Haltech Connect App
The Haltech Connect App enables you to connect wirelessly to and interact with your Haltech Nexus Plug-in ECU via your smartphone or tablet. View real-time data from the ECU, set up basic gauges, clear DTCs, assign wiring, and adjust select parameters. Available for free on Google Play (Android) and the Apple App Store (iOS).
Nexus Plug-in ECU Setup Wizard
The NSP software, when used with a Nexus Plug-in ECU, features a comprehensive setup wizard designed to create a basemap tailored for your specific application.
The process begins with naming your vehicle, which creates a dedicated folder on your laptop for saving maps and datalog files. You also have the option to add a vehicle description—a useful feature for quickly identifying different map versions.
Next, you select your vehicle and engine type from a list of Nissan Skylines (1989–2002), followed by selecting the auxiliary harness you’re using. This allows the ECU to assign I/Os to specific sensors such as a wideband O2 sensor, pressure sensors, and more.
The next few steps involve setting up application-specific options, such as selecting between cable or electronic throttle control, defining camshaft profiles, and configuring injectors and ignition systems.
After completing these steps, NSP presents a summary of your selections for confirmation, allowing any necessary adjustments before finalizing the setup. This thorough process ensures that the Nexus Plug-in ECU is optimally configured to start and run the engine with your own base tune.
Application Specific Notes
This Nexus Plug-in ECU is compatible with the following vehicles:
• Nissan Skyline R32 GTS-T RB20DET
• Nissan Skyline R32 GT-R RB26DETT
• Nissan Skyline R33 GTS-T RB25DET
• Nissan Skyline R33 GT-R RB26DETT
• Nissan Skyline R34 GT-R RB26DETT
• Manual transmissions only
1. Basemaps - Ensure that the ECU is correctly set up using the NSP software wizard, or that a correct map is uploaded to the ECU, before powering the unit through the vehicle. Please note that the wizard setup or base map serves only as a starting point, and the ECU will require appropriate tuning. Haltech is not responsible for any engine damage resulting from the improper use of base maps.
2. MAP Sensor - Air Flow Meters or MAF sensors, are not used, and a MAP sensor must be used instead. A vacuum hose and T-piece are included and can be installed between the fuel pressure regulator vacuum hose and the ECU’s onboard 4 bar MAP sensor.
3. Air Temperature Sensor - GT-Rs can use either the factory air temperature sensor or the one included in the kit. GTS-Ts must use the provided air temperature sensor.
4. Throttle Position Sensor - The Throttle Position Sensor (TPS) must be calibrated through the NSP software prior to starting the engine.
5. Base Timing - The base ignition timing must be checked and synchronized using a timing light once the engine has started and is idling.
6. Immobilizer - The factory immobilizer on the R34 GT-R is not supported.
ECU Pinout
Notes:
• Connector image shows the pin side of the ECU.
• Some pin connections are swapped internally depending on how the NSP wizard is set up (e.g., Injectors 4 and 6 on an RB20), so a physical wire swap is not required to suit the chosen application.
• Pin functions are set automatically by the NSP Wizard and may differ from those shown in this table. Specific functions can be viewed in NSP’s I/O Report.
• DPO 9–21 functions are fixed and cannot be reassigned in NSP.
Auxiliary Connector
Nexus Plug-in ECUs are fitted with a 26-pin auxiliary connector that can be used to wire in sensors or devices not available in the vehicle from the factory.
The ECU also includes an expansion harness that plugs into the auxiliary connector and can be conveniently routed through the vehicle’s firewall into the engine bay. The included expansion harness (HT-189000) provides a connector for a Haltech air temperature sensor, which can be used in place of the factory sensor—for example, when the original air temperature sensor is integrated into an air flow meter. A wideband O2 sensor plug is also available and is controlled directly by the ECU’s onboard wideband O2 sensor controller, allowing direct connection to a wideband hardware pack. A set of spare pins is also provided for the 26-pin connector, enabling the addition of sensors such as fuel and oil pressure sensors, flex fuel sensors, or DBW throttle and pedal upgrades.
IO and DBW Expansion Harnesses
In addition to the basic expansion harness included, Haltech offers optional expansion harnesses (sold separately) to conveniently support common sensor upgrades for your Nexus Plug-in ECU:
HT-189002 - IO Expansion Harness 2.5m (8’)
This expansion harness adds connections for sensors such as a wideband O2 sensor, flex fuel composition sensor, oil pressure sensor, fuel pressure sensor, and air temperature sensor. It also includes spare pins for connecting to additional outputs available on the 26-pin connector.
HT-189003 - DBW Expansion Harness 2.5m (8’)
This expansion harness adds connections for sensors such as a wideband O2 sensor, flex fuel composition sensor, oil pressure sensor, fuel pressure sensor, air temperature sensor, a Bosch DBW throttle plug, and a universal plug for an Accelerator Pedal Position (APP) sensor. This connector can be used to wire an APP sensor of your choice, and the pinout information for the opposing connector is shown on the right. Similar to the IO Expansion Harness, it also includes spare pins for connecting to additional outputs available on the 26-pin connector.
Nexus Plug-in ECU Brackets
The Nexus Plug-in ECU replaces the factory ECU, which is located behind the passenger-side kick panel. To access this location, the kick panel cover must be removed. The dimensions of the Nexus Plug-in ECU allow the cover to be reinstalled afterward.
The Nexus Plug-in ECU is also supplied with mounting brackets and screws to facilitate installation in this location. Each vehicle application (e.g., R32, R33, and R34) requires two brackets. The correct bracket combinations are shown below and on the following pages to ensure proper installation.
Note: A 10mm wrench or socket is required to unlock the factory ECU connector and to secure it back in place.
R32 Bracket Combination
R33 Bracket Combination
R34 Bracket Combination
Haltech CAN System
The Nexus Plug-in ECU is equipped with an onboard CAN connector for direct connection to a wide range of Haltech CAN expansion products.
Multiple CAN devices can be used simultaneously by linking them together using Haltech CAN cables and a Haltech CAN hub. Examples of Haltech CAN devices include the Haltech uC-10 display dash and the Haltech CAN keypad. The dash allows user-selected ECU or engine parameters to be displayed on a customizable screen, while the keypad enables you to scroll through multiple screens or control other functions managed by the ECU. Additionally, a Nexus IO16 can be added to expand input and output functionality via the Haltech CAN system, supplementing the onboard capabilities of the ECU.
The diagram below illustrates an example of how to connect these Haltech CAN devices (sold separately).