UaGateway
1.5.10.468
|
When mapping the address space of an underlying COM DA server to the address space of UaGateway’s OPC UA server, COM Variant data types are converted to OPC UA data types. Currently, the following conversions are supported:
Variant Type | OPC UA Type |
---|---|
VT_EMPTY | NULL |
VT_BOOL | Boolean |
VT_I1 | SByte |
VT_I2 | Int16 |
VT_I4 | Int32 |
VT_I8 | Int64 |
VT_UI1 | Byte |
VT_UI2 | UInt16 |
VT_UI4 | UInt32 |
VT_UI8 | UInt64 |
VT_R4 | Float |
VT_R8 | Double |
VT_CY | Double (possible out of range conversion error) |
VT_BSTR | String |
VT_DATE | DateTime |
For underlying COM DA servers, only the standard properties (AttributeID 1-6, value, timestamp, quality) are mapped to OPC UA. All other COM DA properties are not mapped but ignored.
Note that OPC UA Properties of an underlying OPC UA Server can be mapped to vendor-specific attributes (see Property mapping from UA to COM DA).
Aggregates of underlying COM HDA Servers are not made available via UaGateway’s OPC UA Server, only raw historical data.
UaGateway runs as a Windows service and thus in a service context with dedicated user rights, which makes it hard to configure DCOM for remote connections.
Thus we strongly recommend to only run the UaGateway on the same machine as the COM DA Clients/Servers that should be connected.
It is only possible to install a single UaGateway on the same PC, multiple installations are not possible. This has to be especially kept in mind when installing an OEM Edition of UaGateway, which can’t be run side by side with a "regular" UaGateway.