Schneider Electric Exchange Community

Discuss and solve problems in energy management and automation. Join conversations and share insights on products and solutions. Co-innovate and collaborate with a global network of peers.

Register Now
Learn about the Community. Join our Core Community to Get Started
Knowledge Base
cancel
Showing results for 
Search instead for 
Did you mean: 

Xenta 527 Appears offline: Troubleshooting steps.

Issue

Xenta 527 Appears offline: Troubleshooting steps.

Environment

  • I/NET
  • Xenta 527
  • Xenta 527-NPR

Cause

Possible Causes:

  • Ethernet Communication is down
  • Ethernet Port is closed
  • Device is configured incorrectly
  • Device failure

Resolution

Ethernet Communication is down

  1. Using the command prompt ping the devices IP and trace its route. "ping xxx.xxx.xxx.xxx" and "tracert xxx.xxx.xxx.xxx" Watch to see if the Domain server prints out the correct Host name.  If the device is shows as offline there may be an error with Firewall settings or Ethernet communication at the Host Workstation
  2. Connect to the router via Internet Explorer
  3. If neither of these are possible Communication is definitely down on the Workstation side. Next check the Xenta Server side.
  4. Disconnect the Ethernet cable from the Device and plug it into a laptop. See if you are on the network. 

Ethernet Port Is closed

  1. If the above process shows that Ethernet communication between the Workstation and Router is valid, you may have port closed.
  2. Use a crossover cable to connect a laptop to the device and see if you can connect to a controller ON THAT LINK in I/NET. Look for live values in Controller Summary. 
  3. If you are able to do this, and you are able to show that Ethernet communication between the 2 devices is working then you most likely have a firewall on port 50069
  4. Contact the building IT department

Device is configured incorrectly

  1. If, in the above process, you were unable to connect to I/NET while direct connected to the Router via an Ethernet crossover cable, the device may be configured incorrectly
  2. Open the active I/NET configuration Profile
  3. Ensure that TCP/IP is enabled
  4. Add the Router’s IP address to the Reference Host Table
  5. Restart the I/O server
  6. Check communication
  7. Connect to the 527 via HyperTerminal
  8. type setip and verify you have been using the correct IP address and host name
  9. type inethost and add the Workstation’s IP address to Reference host table.
  10. restart the 527
  11. Communication should be restored.

Device failure

  1. Observe the "Run" light on the device.  It should be solid green.
  2. Observe the TCP/IP port LED. If you are actively communicating this should be blinking
  3. If you are unable to connect to the device via a HyperTerminal Direct Connection or Internet explorer while direct connected you may have a device failure
  4. Cycle Power on the device
  5. Connect via HyperTerminal (if you cannot do this, try using the failsafe mode. If that fails, replace device)
  6. Type the command “format” to format the device
  7. type “setip” and enter IP information
  8. Download and install the latest system file for the 527 you are using. Remember that the 527 and the 527-NPR use different install files.
  9. Configure the I/NET communication in HyperTerminal

Other Troubleshooting Steps

  1. See if the communication error shows up on multiple computers and if possible multiple locations. There may be an error with Firewall settings or Ethernet communication that only effects part of a large system Host Workstation
  2. Use a different Ethernet port to connect the 527 or workstation to
  3. Direct connect to a controller on the controller LAN via TAP and see if any stations are offline.  It is theoretically possible that some form of electrical failure on the controller LAN has cause the 527 to appear offline.  If you are unable to see the entire controller LAN from anyone one device, you should troubleshoot Controller LAN communication.

If this is a recurring issue for the site, please download and use this document for information gathering and troubleshooting.

Tags (3)
Labels (1)
No ratings