234
3 TROUBLESHOOTING
3.3 Troubleshooting by Symptom
3.3 Troubleshooting by Symptom
Troubleshooting related to network and connection
Symptom Check point Corrective action
Login screen does not appear. Is there any disconnection in the connection route? • Connect the cables properly.
• Replace the cables to new ones.
Is the CPU module right after powering ON or
resetting?
• The screen appears after 30 seconds after starting the
CPU module.
Is an IP address set to the personal computer? • Set the IP address of the personal computer and the
BACnet module to be on the same network. (Page 197
Network information)
Is the IP address duplicated? • Review the setting of the IP address.
Can the module communicate using Ping
command?
• Check if the IP address and the host name are correct.
• Check if the cable is disconnected.
Is there a firewall on the communication route? • Contact the network administrator to check the setting of
the firewall.
Is restoration performed? • Check if the IP address is changed by restoration.
Unable to log in. Are the user name and password correct? • Check if the case (upper or lower) is correct.
• When the user name or password is changed, log in with
the new user name or new password.
• Check if the login information is changed by restoration.
• If the login information has been forgotten, initialize the
BACnet module.
Unable to communicate with another
BACnet device.
Is the IP address duplicated? • Review the setting of the IP address.
Is the instance number of devices duplicated? • Review the instance number of the device.
Is the communication to the target BACnet device
established?
• Check the BACnet device of the communication target.
Is the BACnet module in stop state (the
background of the screen is yellow)?
• Restart the operation of the BACnet module. (Page
225 Restart)
Is the destination to send packet correct? • Check the destination in the communication log. (Page
196 Displaying communication logs of BACnet)
To Next Page
Loading...
