Omron FINS
The Omron FINS Device Driver allows Iotellect Server to communicate with devices supporting Omron FINS Protocol. These devices may be connected to the system and, like with all other types of devices, their data is converted into a unified form, so they can be accessed from different Iotellect facilities. See Devices article for more information about the "normalized" representation of devices in Iotellect.
Driver Information
Driver Plugin ID: | com.tibbo.linkserver.plugin.device.omronfins |
Global Settings
None defined.
User Level Settings
None defined.
Device Account Properties
Connection Properties
Connection settings define how Iotellect Server communicates with a certain Omron device. These settings may be accessed using the Edit Device Properties action of Device Context. The following connection properties are available:
Property | Description |
IP Address or Host Name | Address of Omron FINS device. |
Port | Device port (default is 9600). |
Source FINS Network Address | This parameter specifies address number of the Iotellect server inside source network (default is 1). |
Source FINS Node Address | This parameter specifies number of the source node (default is 127). |
Source FINS Unit Address | This parameter specifies number of the source unit (default is 127). |
Destination FINS Network Address | This parameter specifies address number of the destination address (default is 1). |
Destination FINS Node Address | This parameter specifies number of the destination node (default is 0). |
Timeout | Timeout (in ms) of replies that should be received back from remote nodes (default is 1 second). |
Retries | Number of times a packet will be sent before it consider it as not deliverable (default is 2). |
Device Registers
This property contains a list of Omron device registers that are accessed and managed by Iotellect. Once a new Omron device is added, one or more registers have to be configured to make device data available for the system. Each register is represented by a single variable of Device Context.
 | Omron devices do not provide metadata, so Iotellect Server cannot learn about available Omron registers of a particular device. That is why it's necessary to configure Device Registers manually. |
Here is a list of properties of each Omron register:
Property | Description | |
Name | Register name. A Device Context variable that will be used to access the register, so it may contain only letters, digits and underscore. | |
Description | Register textual description. Will be used as the description of the Device Context variable. | |
FINS Unit Address | This parameter specifies the number of the destination unit (default is 0). | |
Data Type | Defines how to interpret a value of one or more adjacent Registers. See type conversion section for details. Data Types: Boolean, Short, Word, Long, DWord, Float, Unsigned BCD, Unsigned Long BCD, Signed BCD, Signed Long BCD, String | |
Byte Order | Byte Orders: Hi-Lo, Lo-Hi, Hi Only, Lo Only. | |
Memory Type | Memory Type number of the Omron device register in decimal form. | |
Writable | Defines whether the register is modifiable. | |
Register Address (Offset) | Address (offset) of the Omron device register is entered in decimal or float form. The float form is used for Boolean registers only. The value after the comma refers to a specific register bit. For example: 100.0, meaning the register is 100 and the bit is 0. | |
Size | Number of registers to read by a single Omron FINS I/O operation and store in one Iotellect Server context variable. It may be useful to read registers at once in the following cases:
This setting default value is 1. It should not be changed in most cases. | |
| The actual number of registers read in a single I/O operation will be N * M, where
| |
Word Order | Word Orders: Hi-Lo, Lo-Hi. | |
 | You can import the list of registers from a file (e.g. CSV file) by using Import function of Data Table Editor component. |
| If you wish to connect several similar Omron devices to Iotellect, you can fill in the Device Registers table only once and then copy it to other devices using the Replicate action. |
Device Assets
Assets are not supported by the driver.
Device Settings
Omron device driver creates one Device settings variable per device register.
Type Conversion
The following table shows how Omron Registers are converted to Device context variables. Note that number of rows in each variable depends on the value of Size parameter. By default, all variables are single-row, i.e. scalar.
Data Type | Description | Iotellect Server Variable Format |
Boolean | 2-Byte Int Unsigned | Readable/Writable, 1 Column of type Boolean |
Short | 2-Byte Int Signed | Readable/Writable, 1 Column of type Integer |
Word | 2-Byte Int Unsigned | Readable/Writable, 1 Column of type Integer |
Long | 4-Byte Int Signed | Readable/Writable, 1 Column of type Integer |
DWord | 4-Byte Int Unsigned | Readable/Writable, 1 Column of type Integer |
Float | 4-Byte Float | Readable/Writable, 1 Column of type Double |
Unsigned BCD | 2-byte BCD Unsigned (0 - 9999) | Readable/Writable, 1 Column of type Integer |
Unsigned Long BCD | 4-byte BCD Unsigned (0 - 99999999) | Readable/Writable, 1 Column of type Integer |
Signed BCD | 2-byte BCD Signed (-7999 - 7999) | Readable/Writable, 1 Column of type Integer |
Signed Long BCD | 4-byte BCD Signed (-79999999 - 79999999) | Readable/Writable, 1 Column of type Integer |
String | Char | Readable/Writable, 1 Column of type String. Server reads number of registers specified by Size parameter and represents them as a string. |
Device Operations
No operations provided by the driver.
Device Events
No events provided by the driver.
Connection Handling
This driver makes the device Online if:
TCP connection with the Device was successfully established
Synchronization Details
Synchronization between Iotellect Server and Omron device includes the following steps:
Creating a Settings Cache according to the Device Registers list. Each variable is used to access a single Omron device register.
Reading Omron register values and storing these values in settings cache.
Was this page helpful?