<img alt="" src="https://secure.intelligent-consortium.com/820374.png" style="display:none;">
Skip to content
Customer portal
Open a support ticket
  • There are no suggestions because the search field is empty.

Why does TOP Server show Omron FINS Ethernet network relay error 0x9005?

This article explains the Omron FINS Ethernet network relay error 0x9005 in TOP Server, the FINS addressing settings that commonly cause it, and what to review if the error continues.

Why does TOP Server show Omron FINS Ethernet network relay error 0x9005?

The TOP Server event log may show a message similar to:

Device responded with network relay error. 

Net address = 005, Node address = 224, 

Main error = 0x10, Sub error = 0x05, End code = 0x9005.

Unlike a basic communication timeout, 0x9005 means an Omron device in the communication path responded to TOP Server but reported that the FINS request could not be relayed correctly.

This is commonly seen when TOP Server communicates through one Omron PLC or Ethernet module to reach another PLC on a routed FINS network, such as Controller Link.

 What TOP Server settings should I check?

  • On the affected Omron FINS Ethernet device, verify the following settings:

  • Device ID: The IP address of the Omron PLC or Ethernet module that TOP Server can reach directly.

  • Source Network Address: The FINS network number representing the Ethernet network TOP Server is communicating from.

  • Source Node: The FINS node assigned to the TOP Server computer.

  • Destination Network Address: The FINS network number of the target PLC or network.

  • Destination Node: The FINS node number of the target PLC.

  • Destination Unit: Commonly 0 when communicating with the PLC CPU.

When troubleshooting a routed FINS connection, make sure to verify both the source and destination addressing. Correct Destination Network Address and Destination Node settings alone do not guarantee that the FINS request can be routed successfully.

Source Network Address and Source Node

The Source Network Address and Source Node are especially important when communicating through one Omron PLC to another.

Consider the following example network:

TOP Server PC IP: 192.0.2.172
Gateway PLC IP: 192.0.2.224
Gateway Ethernet FINS Network/Node: Network 5, Node 224
Remote PLC FINS Network/Node: Network 1, Node 2

The TOP Server device configuration may require:

Device ID: 192.0.2.224
Source Network Address: 5
Source Node: 172
Destination Network Address: 1
Destination Node: 2
Destination Unit: 0

In this example, TOP Server communicates directly with the gateway PLC at 192.0.2.224, while the FINS destination settings identify the remote PLC at Network 1, Node 2.

The Source Network Address and Source Node identify the TOP Server computer on the FINS network. When automatic IP address conversion is being used, the Source Node commonly corresponds to the host portion of the TOP Server computer's IP address.

What if error 0x9005 continues?

If the source and destination addressing have been verified and the error continues:

  • If the TOP Server computer has multiple network adapters, bind the Omron FINS Ethernet channel to the specific network adapter used for the Omron network.

  • Verify the FINS routing tables and routed network configuration between the PLCs.

  • Verify the Ethernet module's address conversion method and confirm the TOP Server computer is represented correctly if an IP address table is used.

TOP Server builds the FINS request using the configured source and destination addressing, while the Omron PLCs and communication modules route the request through the configured network.