Frequently asked questions about the NCoder
This page contains answers to frequently asked questions about the NCoder device, including error messages specific to encoder operations. For general Space error messages, see the Error message FAQs.
How do I initialise an NCoder?
The NCoder must be initialised before you can use it with Space. The procedure differs depending on whether the NCoder is connected via Ethernet or USB.
Ethernet connection
- Add the NCoder in Space under System > Salto Network. See How to add an NCoder for more information.
- In Admin > Local settings, select the Online option for the NCoder.
- Hold the CLR button on the back of the NCoder for 5 seconds to enter addressing mode. The LED will turn solid yellow while the NCoder is in addressing mode.
- Using a web browser on the same network, go to
192.168.0.234. - Set the required network parameters (for example, static IP address if not using DHCP) and click Send. The NCoder will exit addressing mode automatically once the settings are saved. If no changes are needed, hold the CLR button for 5 seconds to exit addressing mode manually.
- In Space, go to System > Salto Network, select the NCoder, and click Initialize.
- The NCoder is now ready to use.
USB connection
- Connect the NCoder to the PC using the supplied USB cable.
- In Admin > Local settings, select the Local option for the NCoder.
- Attempt any operation on the NCoder, for example Read Key. Space will display a warning message prompting you to initialise the device.
- Press the CLR button on the back of the NCoder, then click Initialize in Space.
- The NCoder is now ready to use.
Understanding the NCoder LED
The LED on the NCoder indicates its current status. The following table describes the most common states:
| Status | LED | Buzzer |
|---|---|---|
| Waiting for a key to be presented | Blinking green (continuous) | Low-pitched beep (continuous) |
| Processing a key | Blinking yellow (continuous, 100 ms) | Low-pitched beep (100 ms) |
| Key successfully processed | Solid green (1 second) | Low-pitched beep (1 second) |
| Operation failed | Solid red (1 second) | High-pitched beep (1 second) |
| NCoder startup | Solid green (1 second) | None |
| Waiting for initialisation | Blinking red (continuous) | None |
| Addressing mode | Solid yellow (continuous) | None |
| Factory mode | Solid red (continuous) | None |
| Desktop Reader (DR) mode activation | Yellow (1 second) then green (0.5 seconds) | Silent (1 second) then high-pitched beep (0.5 seconds) |
If the NCoder still doesn't work after initialisation
If the NCoder is not responding correctly and reinitialising does not resolve the issue, you can perform a factory reset to return it to its original state.
A factory reset will erase all configuration on the NCoder. You will need to reinitialise it in Space after performing a reset.
To perform a factory reset, hold the CLR button while connecting the power supply, and continue holding it for 5 seconds. The NCoder will return to factory mode (indicated by a solid red LED).
After the reset, follow the initialisation procedure above.
Error messages related to initialisation
If the NCoder has not been initialised before use, Space will display a Peripheral not initialized message when you attempt to use it. If the initialisation process starts but does not complete within the expected time, Space will display an NCoder initialization timeout message. In both cases, follow the initialisation procedure above before trying again.
What should I do if I get a card security error?
A card security error means that Space was unable to verify the security credentials stored on the card when it was presented to the encoder.
This can happen in the following situations:
- The card was originally issued by a different system or a different Space installation using different security settings.
- The card has been reformatted or had its contents erased.
- The card type is not compatible with the security configuration of your Space installation.
What does the 'Key Overflow' error mean?
A key overflow error means that Space could not write the required data to the card because the card does not have enough available memory, or because an internal limit on the card has been reached.
This can occur when you try to write a large amount of data that exceeds the card's memory, for example if the user has access to multiple doors, zones, calendars, or other resources.
To solve this issue, you can try the following:
- Reduce the amount of data assigned to the user/card in Space, for example by removing some access rights or calendars.
- Re-issue the card.