nisscan.com

It does look like something is pulling the timing. Quite possibly the detonation sensors.
Do you get any fault codes?

When the NDS II software connects to an ecu it checks which function the ecu supports. If the function is greyed out, it means it's not supported by the ecu. The ecu can disable a function due to some fault or the function is not supported by the ecu at all.

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