Error Possible error causes and remedies
No active DHCP server is found in the system network.
Possible error causes include:
● Only a single computer has been configured in the system network with active DHCP server
- and this computer is not available. The system network is not operated with synchronizing
DHCP servers.
● No computer has been configured in the system network with active DHCP server. DHCP
operation is disabled on all potential computers (NCU, PCU). This is a configuration error.
● In the system network, there is no NCU or PCU computer available that has DHCP operation
activated on it and could be a server.
Remedy
In the system network, configure a computer that is available as DHCP server.
After it has booted, the TCU displays 'Waiting for HMI'. (The TCU cannot establish its connection to the HMI.)
Error cause 1
The connection to the HMI has not been established - neither the connection configured in
config.ini nor the default connection. An incorrect address for the HMI connection after booting
has been set in the config.ini file.
Remedy
Correct the configuration using the "System Network Center" program. The TCU automatically
reboots.
Error cause 2
The connection to the HMI has not been established - neither the connection configured in
config.ini nor the default connection. The computer, to which the TCU should connect after
booting according to the configuration in config.ini, cannot be reached because the computer
is not switched on/is not available.
Remedy
Switch off the computer (NCU or PCU) and switch on again.
Error cause 3
The connection to the HMI has not been established - neither the connection configured in
config.ini nor the default connection. The HMI on the computer, to which the TCU should connect
after booting according to the configuration in config.ini, cannot be reached because the HMI is
deactivated.
Remedy
Activate the HMI on the NCU using the service command sc enable HMI.
Error cause 4
The connection to the HMI has not been established - neither the connection configured in
config.ini nor the default connection. The HMI on the computer, to which the TCU should connect
after booting according to the configuration in config.ini, cannot be reached because the HMI
has either not start or has crashed due to a software error.
Remedy
Switch off the computer (NCU or PCU) and switch on again.
Configuring the network
17.6 Station-related network diagnostics
SINUMERIK Operate (IM9)
390 Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1
To Next Page
Loading...
Need help?
General
