Supported device types and versions
Communication line configuration
Station configuration
I/O tag configuration
Literature
Changes and modifications
Document revisions
The FINS protocol (Factory Interface Network Service) implements client (master) communication with Omron PLCs. The FINS/UDP protocol variant based on the UDP protocol (on the TCP/IP-UDP line) as well as the FINS/TCP protocol variant using the TCP protocol (on the TCP/IP-TCP line) are implemented. Read (MEMORY AREA READ) and write (MEMORY AREA WRITE) commands are supported.
Note: it is recommended to use the FINS/UDP protocol variant; FINS/TCP protocol has a higher overhead (16 bytes for each request and response) and is suitable for demanding network environments (firewalls, the need for address translation - NAT, etc.). Not every Omron PLC supports the FINS/TCP protocol variant.
Communication was tested against a CJ-series CJ2M CPU (both FINS/UDP and FINS/TCP protocol variant).
Configuration dialog box - tab Parameter.
They influence some optional parameters of the protocol. The following station protocol parameters can be set:
Table 1
| Parameter | Meaning | Unit | Default value |
|---|---|---|---|
| Source Parameters | Section of parameters describing the source address (D2000 KOM process) | ||
| This parameter specifies the network address number of the source device (D2000 KOM process). The Source Network Address is sometimes referred to as SNA in Omron FINS documentation. The valid range is 0 to 127. Actual network numbers can range from 1 to 127. FINS interprets 0 as 'use the local network'; as such, 0 must not be used when data will be routed through gateway PLCs. The default value for network addresses is zero. This is interpreted by FINS as an instruction to use the local network. Actual network numbers can range from 1 to 127. Using zero is convenient if there is only one network level. When using gateway devices, however, specify the actual network number (1–127) to avoid routing ambiguities. | - | 0 |
| This parameter specifies the node number of the source device (D2000 KOM process). The Source Node is sometimes referred to as SA1 in Omron FINS documentation. The valid range is 0 to 254. If the destination PLC is configured to use automatic address generation, then this number must be the host number portion of the host computer's IP address. For example, if the host computer has an IP of 111.222.333.123 and the subnet mask is 255.255.255.000, the source node number should be 123. If the target PLC is configured to use an address table, then the table must have an entry for the host computer's IP. The node number in this table entry must agree with the source node number entered for the driver. Note: if the line is configured as TCP/IP-TCP (FINS/TCP protocol), it is recommended to use a value of 0, which means that the node number of the source device will be assigned by the PLC during connection establishment. | - | 254 |
| This parameter specifies the number of the Unit at the source device (D2000 KOM process). The Source Unit is sometimes referred to as SA2 in Omron FINS documentation. It is an arbitrary number in range 0-255. | - | 0 |
| Destination Parameters | Section of parameters describing the destination address (Omron PLC) | ||
| This parameter specifies the network address number of the destination device. The Destination Network Address is sometimes referred to as DNA in Omron FINS documentation. The valid range is 0 to 127. Actual network numbers can range from 1 to 127. FINS interprets 0 as use the local network; as such, 0 must not be used when data will be routed through gateway PLCs. | - | 0 |
| This parameter specifies the node number of the destination device. The Destination Node is sometimes referred to as DA1 in Omron FINS documentation. The valid range is 0 to 254. Note: if the line is configured as TCP/IP-TCP (FINS/TCP protocol), this parameter is not used, as the node number of the destination device will be announced by the PLC during the connection establishment. | - | 0 |
| This parameter specifies the destination device unit number, which is sometimes referred to as DA2. The valid range is 0 to 255. The default number for DA2 is 0. | - | 0 |
| Other Parameters | Other communication parameters | ||
| The parameter affects the work with 4-byte values (DWORD, LONG, FLOAT), which are read in two consecutive registers. E.g. I/O tag with address DM28,FLOAT will read registers 28 and 29 from DM memory and interpret them as a 4-byte real number. The "4-byte Endian Mode" parameter specifies the order of the registers and bytes in the resulting number.
The order of letters and numbers indicates the order of registers and bytes in the interpretation of the resulting 32-bit number, on the left is the most significant byte/register, on the right the least significant.
For example, if bytes <AA><BB><CC><DD> are received, the Bb (3412) order means that the hexadecimal value CCDDAABB will be interpreted, which in the case of DWORD type is a number 3 437 079 227. The IL (2143) order would mean interpretation as a hexadecimal value of BBAADDCC, which in the case of a DWORD type is a number 3 148 537 292. | - | Bb (3412) - big-endian, 2nd register significant |
| Maximum count of data bytes that are requested in one request. The total size of a response is 14 bytes + Data Size. | Byte | 512 |
| Maximum count of request retries. If no reply returns after a request had been sent, the station will be in the status of a communication error. | s | 2 |
| Timeout before resending a request if no reply had not received. | s | 0.1 | |
| Maximum wait time to receive a response. | s | 0.1 | |
| Logging of additional debug information about communication. | YES/NO | NO | |
Note: the configuration of the network parameters for directly connected PLCs was as follows:
Possible types of I/O tag values: Ai, Ao, Di, Do, Ci, Co.
In the Omron FINS protocol, the address space is divided into several areas. Work with the following areas is supported:
In each area, there is independent addressing with an address size of 2 bytes, i.e. addresses from 0 to 65535. The actual size of the address space depends on the particular PLC model.
The size of the register in the AR, DM, CIO, HR, WR areas is 2 bytes.
The address of the I/O tag format is <area><offset> [.<bit>] [,<type>] where:
<type> is an optional part of the address that specifies how the data is interpreted:
| Type | Description |
|---|---|
| BIT | Working with a single bit (default value if the address contains a bit specification, eg HR1.3) |
| BYTE_U | The higher (first) byte of the register |
| BYTE_L | The lower (second) byte of the register |
| WORD | Register interpreted as a 16-bit unsigned number (default value if the address does not contain a bit specification, e.g. HR1) |
| SHORT | Register interpreted as a 16-bit signed number |
| BCD | Register interpreted as an unsigned BCD number (0-9999). |
| SBCD | Register interpreted as a signed BCD number (+/-7999). The sign is defined by the highest bit. |
| LBCD | Two 16-bit registers interpreted a 4-byte unsigned BCD number (0-99999999). |
| SLBCD | Two 16-bit registers interpreted a 4-byte signed BCD number (+/-79999999). The sign is defined by the highest bit. |
| DWORD | Two 16-bit registers interpreted as a 32-bit unsigned number (byte order depends on the 4-byte Endian Mode parameter) |
| LONG | Two 16-bit registers interpreted as a 32-bit signed number (byte order depends on the 4-byte Endian Mode parameter) |
| FLOAT | Two 16-bit registers interpreted as a 32-bit float number (byte order depends on the 4-byte Endian Mode parameter) |
-