If for some reason the Nox T3 and the Nonin 3150 Oximeter fail to pair, the following troubleshooting tips might help.
1. Try resetting the device following the How To reset the Device troubleshooting guide.
2. If an X-mark appears on the Nox T3 display instead of a checkmark:
This means that the pairing of the Nox T3 recorder and the oximeter has not been achieved and the programming of the oximeter failed. It is necessary to start the pairing process again. Before that can be done the oximeter needs to be restarted. That is done by removing the batteries and inserting batteries again to the oximeter. Then hold the grey activation button on the oximeter for at least three seconds. Resume the pairing process from Step 3.
Note: If this happens repeatedly, it might be necessary to send the oximeter in for service.
3. If the Nox T3 recorder seems to be stuck in the "connecting to" display screen:
Verify that the PIN number of the oximeter used matches the number displayed on the Nox T3. Etched onto the oximeter is the word “PIN” followed by a 6-digit number. This number can be found on the back of the oximeter device.
3.1 Incorrect PIN number
If the numbers do not match as is shown in the figure below the Nox T3 is unable to connect to the oximeter and is stuck in the "connecting to" display screen.
 |
 |
In the case of an incorrect PIN number it is necessary to re-configure the Nox T3 in Noxturnal and insert there the correct PIN number:
When you have completed the configuration with the correct PIN number in Noxturnal, resume the pairing process from step 1.
3.2 Correct PIN number but still stuck in the "connecting to" display screen
If you have verified that the PIN number is correct but the Nox T3 recorder is still stuck in the “connecting to” display screen, try to reboot the Nox T3 recorder. This is done by simply waiting for the Nox T3 to turn off (it turns off automatically in 2 minutes after it has been turned on) and then turn on the Nox T3 again by pushing the middle button. Then resume the pairing process from step 2.
For more troubleshooting tips, refer to the troubleshooting guide.
Rev.002
Comments