Use as a OPC server
The OPC interface allows FA-Server to become an OPC server and communicate with other SCADA and OPC client applications. The OPC specification complies with DA1.0/2.0.
The basic information required for connection is as follows (when migrating from an older version to a higher version, changes will be required for parts that differ from the older specifications. For details on the changes, see "Migrating from older versions" below).
OPC Specifications |
explanation |
Program ID (ProgID)
|
The program ID is the following fixed string, specified in uppercase half-width characters. 32bit version: "RW.SERVER32.6" 64bit version: "RW.SERVER64.6" |
Item ID (ItemID)
|
"Unit name.Folder name.Tag name" Example: "U01.F01.T01" However, the characters specified in "Access Path" below must be omitted. |
Access Pass (AccessPath)
|
You can freely set the access path. When you specify the access path, you can omit part of the first half of the item ID.
example) Access path: "U01.F01." Item ID "T01" |
The following is a configuration example when using an access path.
|
explanation |
Examples |
Example 1 |
If you want to handle item IDs as full paths |
Access pass: None Item ID 1: U01.F01.T01 Item ID 2: U01.F01.T02 |
Example 2 |
If you want to use the item ID as the tag name |
Access path: U01.FD01. Item ID 1: T01 Item ID 2: T02 |
Example 3 |
To directly specify the PLC address using the item ID |
Access Path: U01.F01.# Item ID 1: M0000 Item ID 2: D0000 |
Migrating from previous versions
When running as a OPC server, some specifications have changed from the previous version. Please check the following.
OPC Specifications |
Ver4 |
Ver5 |
Ver6 |
Program ID
|
RW.FASERVER.4 |
RW.FASERVER.5 |
32-bit version: RW.SERVER32.6 64-bit version: RW.SERVER64.6 |
Access Pass
|
Unit name.Folder name |
Unit name.Folder name. (※Add a period to the end) |
Equivalent to Ver5 |
Item ID
|
[Unit name.Folder name]Tag name |
Unit name.Folder name.Tag name |
Equivalent to Ver5 |
OPC Item Data Type
If the OPC client requests a data type (vtRequestedDataType) when adding items, the data will be converted to that data type and passed to the client.
OPCIf no data type is requested by the client, the native type for numeric tags is VT_R8, for bit tags is VT_BOOL, and for character tags is VT_BSTR. Also, if you check "Make array" below, it will be an array type.
(default data type)
Tag Type |
No sequence check |
With sequence check |
Bit Tag |
VT_BOOL |
VT_BOOL | VT_ARRAY |
Numeric Tags |
VT_R8 |
VT_R8 | VT_ARRAY |
String Tags |
VT_BSTR |
VT_BSTR | VT_ARRAY |
If you want to change the native type (default type), use the "OPC Native data type settings (for OPC server unit only)" filter. Set the filter in the "Filter tab" of the tag properties.
