nisscan.com

It depends which parameters your ecu supports. Most probably:

- NB Sensor 1 bank 1
- NB Sensor 1 bank 2
- NB Sensor 2 bank 1
- NB Sensor 2 bank 2
- A/F Alpha b1
- A/F Alpha b2
- A/F Alpha b1 stored
- A/F Alpha b2 stored

Have a look at this video.
https://youtu.be/UkPSA0NuPZo?si=kFbYhskBMbz_l0sz

Under Settings->Communication disable the Auto option next to the COM Port setting. This way the software will not try any other Com Ports and fail immediately if there are any issues.

In your Windows Device Manager, what is the Device Status for your adaptor's Com Port?

1. Connect to the ecu you want to monitor. ECM for example.
2. Select ECM from the top menu then Data Display Settings.
3. Select the parameter you want to monitor for each gauge.

Was the log generated with NDS II Windows Pc software or the Android app?

Can you attach the log file?

They need to be done but they are done automatically by the ECM.

The OBDLink SX adaptor is compatible with the NDS II Android app. In the app, you need to change the adaptor type to USB FTDI and USB Adaptor Speed to 115200.

This adaptor is not compatible with the Windows software.

I think the issue is that you have RPM assigned to every gauge. Try other parameters as well and don't repeat them

Are you trying to verify if the radiator logic hardcoded in the ecu is correct? Or if your radiator fans are working?

BTW. The NDSI ver 1.54 Android app and Windows PC version 2.56 software have a register called Radiator Fan Hi.

Really? Why?