OmronFins implements communication with CS/CJ/CP-series CPU Unit or NSJ devices that are compatibles with FINS. It operates as a Master on UDP or serial networks. The communications blocks are dynamically created according to the pooling cycle defined on the AccessType for each Device Point.

Summary Information

Communication Driver Name: OmronFins

Implementation DLL: T.ProtocolDriver.OmronFINS.dll

Protocol: FINS protocol

Interface: UDP and Serial

Equipments supported: CS/CJ/CP-series CPU Unit or NSJ Controller

Tested Equipment: SYSMAC CJ2M CPU34 and CPU35 using UDP/FINS


Supported Operands

OperandRead WriteData TypeAddress size
CIO – CIOYesYesWord2 bytes
WR – Work AreaYesYesWord1 bit
HR – Holding BitYesYesWord2 bytes
AR - Auxiliary BitYesYesWord2 bytes
DM – Data MemoryYesYesWord2 bytes
TA – TimersYesYesBCD2 bytes
CA – CountersYesYesBCD2 bytes
EM# – Extended MemoryYesYesWord2 bytes



Channel Configuration

Protocol Options

Mode: Determines the compatible equipment:

Network: Represents the FINS network. This information is related to the Master

Node: Represents the computer Node in the FINS network. If the number 0 is specified, the driver assumes the last octet of the IP Address as the Node number (for UDP Interface)

Ignore Non Fatal Error: Indicates the driver's behavior when the PLC returns a non fatal error status of 64:



Node Configuration

PrimaryStation Configuration

Serial channels:

Station syntax: <Network>;<Node>;<Unit Id>

Where:

E.g.: 0;1;0


UDP channels:

Station syntax:<IP address>;<Port>;<Network>;<Node>

Where :

E.g.: 192.168.1.101;9600;1;0


When using multiple nodes, the UDP port must be different for each Node.



Point Configuration

The syntax for the OmronFins communication points is: <Memory Area>:<Address>

For more information about the valid operands, see Supported Operands.

E.g.:



Troubleshoot

The status of the driver's execution can be observed through the diagnostic tools, which are:

• Trace window
• Property Watch
• Module Information

The above tools indicate if the operations have succeeded or have failed. A status of 0 (zero) means communication is successful. Negative values indicate internal driver errors, and positive values indicate protocol error codes.