7. Maintenance
373
limits, the CPU recognizes it and automatically is restarted with the user application. The diagnostic
will still be active to show to the user that the last initialization suffered a power supply failure.
2 – In case the NX8000 has a voltage drop to an inferior value than the minimum required limit and it
returns to a higher value within 10 ms, the power supply failure is not recognized by the CPU and the
diagnostic is not generated as the system remains intact during this time. But if the voltage drop takes
longer than 10 ms, the “POWER SUPPLY FAILURE” message is shown on the CPU screen and the
diagnostic is activated.
Figure 7-10. Power Supply Failure Message
The user can change the value of the variable attributed to the power supply failure to FALSE during
the applicative execution, facilitating the verification and treatment of this diagnostic.
The POWER SUPPLY FAILURE diagnostic is already mapped in a specific memory region, defined
as CPU Detailed Diagnostic. This way it is just to use it as global variable. The variable name is
described in the detailed diagnostic list in the Diagnostics via Variables chapter.
Common Problems
If, at power on the CPU, it does not work, the following items must be verified:
Is the room temperature within the device supported range?
Is the rack power supply being fed with correct the voltage?
Is the power supply the module inserted on the far left in the rack (observing the rack by the front
view) followed by the Nexto Series CPU?
Are there network devices, as hubs, switches or routers are powered, interconnected, configured
and working properly?
Is the Ethernet network cable properly connected to the Nexto CPU NET 1 or NET 2 port and to
the network device?
Is the Nexto Series CPU on, in execution mode (Run) and with no diagnostics related to
hardware?
If the Nexto CPU indicates the execution mode (Run) but it does not respond to the requested
communications, whether through MasterTool IEC XE or protocols, the following items must be
verified:
Is the CPU Ethernet parameters configuration correct?
Is the respective communication protocol correctly configured in the CPU?
Are the variables which enable the MODBUS relations properly enabled?
If no problem has been identified, consult the Altus Technical Support.
Troubleshooting
Table 7-32 shows the symptoms of some problems with their possible causes and solutions. If the
problem persists, consult the Altus Technical Support.
Lack of power supply or
incorrectly powered.
- Verify if the CPU is connected properly in the rack
- Power off and take off all modules from the bus,
but the power supply and the CPU
- Power on the bus and verify the power supply
functioning, the external and the one in the rack
- Verify if the supply voltage gets to the Nexto
power supply contacts and if is correctly polarized