Configure the Omron FINS Connector
Discover and connect Omron FINS PLCs, configure memory items and data types, read and write values, and troubleshoot communication errors.
The Omron FINS Connector connects SIA Connect to Omron PLCs and other controllers that support FINS communication over Ethernet. It supports FINS/TCP and FINS/UDP, instance discovery, memory-area reads and writes, scalar values, arrays, and strings.
This guide explains how to discover or create an Omron FINS instance, configure its network parameters, create items manually, select data types, verify communication, and resolve common errors.
Writing to PLC memory can change machine behavior. Confirm the target address and data type, and perform test writes only when the connected process is in a safe state.
Before you begin
Prepare the following information:
- The PLC hostname or IPv4 address.
- Whether the PLC uses FINS/TCP or FINS/UDP.
- The FINS port. The default is
9600. - The source and destination network, node, and unit addresses required by the PLC configuration.
- The PLC memory areas, addresses, and data types you need to access.
- Whether strings require byte swapping.
Make sure that FINS communication is enabled on the correct PLC Ethernet interface and that SIA Connect can reach it through the network.
Discover Omron FINS instances
The Connector can discover FINS devices using UDP broadcast and a FINS/TCP node-address handshake. It can also probe IPv4 hosts on the selected interface for FINS/TCP.
- In the Edge Portal, go to Configuration > Connectors.
- Find the installed Omron FINS Connector.
- Start instance discovery.
- Configure the discovery parameters.
- Start the scan.
- Select the supported FINS devices you want to import.
- Import the selected instances.
Discovery parameters
| Parameter | Default | Accepted values | Description |
|---|---|---|---|
| Scan duration (ms) | 60000 |
1000 to 300000
|
The complete discovery window in milliseconds. |
| Network interface | eth0 |
An available interface or All IPv4 interfaces | The interface used for FINS/UDP broadcasts and the TCP subnet scan. |
| UDP ports | 9600 |
Valid UDP port numbers | The ports used for FINS CPU Unit Data Read broadcasts. |
| TCP ports | 9600 |
Comma-separated ports and ranges | The ports used for the FINS/TCP handshake. For example, 9600,9601 or 9600-9610. |
The TCP scan is limited to 256 hosts and 64 configured TCP ports. Use a specific network interface and narrow port range to reduce scan time.
A discovered instance is preconfigured with the detected address, protocol, port, and FINS node information. Review these values against the PLC configuration before using the instance.
Discovery can list an Omron device that responds on the network but does not provide FINS CPU or data services on that interface. Such a candidate is marked as unsupported and cannot be imported as a FINS instance. This can occur when the device only responds through EtherNet/IP or exposes FINS on another Ethernet port.
Create an instance manually
- In the Edge Portal, go to Instances.
- Select Add instance.
- Select the Omron FINS Connector.
- Enter a descriptive instance name.
- Enter the PLC hostname or IPv4 address in Address.
- Configure the instance parameters.
- Select Create.
Instance parameters
| Parameter | Default | Description |
|---|---|---|
| Protocol | TCP | Select TCP or UDP to match the PLC. |
| Port | 9600 |
The FINS TCP or UDP port configured on the PLC. |
| Timeout | 2000 |
The communication timeout in milliseconds. |
| Source network address | 0 |
The FINS network address used by SIA Connect. |
| Source node | 0 |
The FINS node used by SIA Connect. FINS/TCP can negotiate the node automatically when this is 0. |
| Source unit | 0 |
The source unit address. |
| Destination network address | 0 |
The FINS network containing the destination PLC. |
| Destination node | 0 |
The FINS node assigned to the destination PLC. |
| Destination unit | 0 |
The destination unit address. CPU Unit is normally 0. |
| String byteswap | No swap | Select Swap if the two characters stored in each 16-bit word appear in the wrong order. |
Values below 20 in the Timeout field are interpreted as seconds for compatibility with older Connector configurations. Enter a timeout in milliseconds when creating a new instance.
Create items
The Connector does not support item discovery because FINS does not provide tag browsing. Create each item from the PLC memory map.
- Open the Omron FINS instance.
- Open the Items tab.
- Select Add item.
- Enter a name and UID.
- Enter the PLC memory location in Address.
- Select the matching Data type.
- Configure whether the item can be read, written, or both.
- Configure the required read interval or event behavior.
- Select Create.
Address syntax
Combine the Omron memory-area prefix with the memory location. Address ranges are inclusive.
| Purpose | Example | Description |
|---|---|---|
| Single word |
D100 or DM100
|
Reads or writes one Data Memory word. The Connector treats D as DM. |
| Single bit | CIO100.0 |
Addresses a bit within a word. |
| Word range | D200-209 |
Addresses ten consecutive words, including both endpoints. |
| Work area | W24 |
Addresses a word in the Work area. |
| Holding area | H20 |
Addresses a word in the Holding area. |
| Auxiliary area | A100 |
Addresses a word in the Auxiliary area. |
The available memory areas and valid ranges depend on the PLC model and operating mode. Confirm every address in the Omron documentation for the connected controller.
Use a range for strings because each PLC word stores up to two characters. For example, D200-209 provides ten words, or up to 20 characters. Reading stops at the first null character.
A bit range is calculated from complete words. Test bit-array addressing carefully because a range such as W10-11 represents 32 bits.
Select a data type
| Data type | Size | Description |
|---|---|---|
| Bool | 1 bit | Returns or writes 0 and 1. |
| Int | 1 word | Signed 16-bit integer. |
| Unsigned int or Word | 1 word | Unsigned 16-bit integer. |
| Double int | 2 words | Signed 32-bit integer. |
| Unsigned double int or Double word | 2 words | Unsigned 32-bit integer. |
| Real | 2 words | 32-bit IEEE 754 floating-point value. |
| Double | 4 words | 64-bit IEEE 754 floating-point value. |
| String | Selected address range | Two characters per word. String byte order is controlled by the instance setting. |
| Unsigned BCD16 | 1 word | Unsigned 16-bit binary-coded decimal from 0 to 9999. |
| Unsigned BCD32 | 2 words | Unsigned 32-bit binary-coded decimal from 0 to 99999999. |
| BCD16 type 0-3 | 1 word | Omron signed 16-bit BCD formats. Select the type used by the PLC application. |
| BCD32 type 0-3 | 2 words | Omron signed 32-bit BCD formats. Select the type used by the PLC application. |
Read arrays and strings
A range address returns multiple numeric values as a compact JSON array. For example, reading three Int values could return:
["10","20","30"]Multiword data types use the required number of PLC words. For example, a range covering four words returns two 32-bit values or one 64-bit value.
A String item returns text instead of a JSON array. Change String byteswap on the instance if adjacent characters are reversed.
Write scalar values, arrays, and strings
For a single address, map one value to the item. For a range address, map a valid JSON array containing the values to write.
For example:
[10,20,30]The Connector does not write more values than fit in the configured address range. A non-array value sent to a numeric range is rejected as an invalid array format.
For a String item, send the text value directly. If the string is longer than the selected address range, only the characters that fit are written.
When several writes to the same item are queued, the Connector uses the newest queued value.
Automatic identity items
After a successful connection, the Connector creates read-only identity items when the information is available:
- Vendor
- Model
- Firmware
Some PLCs do not support the CPU information command used for Model and Firmware. Communication can still continue, but only Vendor may be available.
Verify the configuration
- Confirm that the instance and required items are enabled.
- Check that the instance has no active connection error.
- Confirm that the Vendor item reports Omron.
- Open a known read item and compare its value with the PLC programming software.
- Test a write only after confirming that the target is safe and writable.
- Confirm the written value in the PLC and then read it back through SIA Connect.
Troubleshoot the Omron FINS Connector
The instance reports Timeout to PLC
- Confirm that the PLC is powered and reachable.
- Check the Address, Protocol, Port, and Timeout fields.
- Confirm that FINS is enabled on the selected PLC Ethernet interface.
- Check routing, subnet settings, and firewall rules.
- Confirm that the source and destination FINS addresses match the network configuration.
The instance reports Failed to connect to PLC
Confirm that the selected protocol is correct and that the PLC listens on the configured port. A TCP connection cannot be established against a UDP-only FINS configuration.
The client and server use the same FINS node
Assign different source and destination node values. For FINS/UDP, the source node normally corresponds to the final octet of the SIA Connect IPv4 address when the FINS network uses IP address conversion.
The item reports an invalid read or write address
Confirm the memory-area prefix, word number, bit offset, and range. Check that the area is available on the PLC model and that the selected Data type fits within the configured range.
The item reports Could not determine start address of byte
The range syntax could not be parsed. Use an inclusive range such as D200-209 and make sure the starting address includes a supported memory-area prefix.
The item reports Unknown type
Select a supported value in Data type. If the item was imported from an older configuration, edit and save it using one of the current data types.
An array write is rejected
Send a valid JSON array to numeric range items. Check the brackets, commas, quotation marks, and value types. The number of values must not exceed the capacity of the address range.
A string is truncated or has reversed characters
Increase the number of words in the address range if more characters are required. Change String byteswap between No swap and Swap when characters appear in pairs in the wrong order.
Real or Double values are incorrect
Confirm that the PLC stores the value as a 32-bit Real or 64-bit Double and that the start address and range cover two or four consecutive words respectively.
A discovered Omron device cannot be imported
The device answered the network scan but did not provide usable FINS CPU or data services on that interface. Check whether the device uses EtherNet/IP, whether FINS is enabled, or whether another Ethernet port provides FINS communication.
Discovery does not find the PLC
- Select the network interface connected to the PLC network.
- Confirm that the interface has a valid IPv4 address.
- Check the configured UDP and TCP ports.
- Increase the scan duration when the network is slow.
- Use a narrower subnet or port range where possible.
- Create the instance manually if broadcasts are blocked by routing or firewall rules.