The PnTelegramType represents a Telegram. The PnTelegramType can at least have one Input Telegram, one Output Telegram or both.
Table 56 – PnTelegramType Definition
|
Attribute |
Value |
||||
|
BrowseName |
PnTelegramType |
||||
|
IsAbstract |
False |
||||
|
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
|
Subtype of the BaseObjectType defined in OPC 10000-5. |
|||||
|
0:HasComponent |
Object |
Input |
|
PnIoTelegramType |
O |
|
0:HasComponent |
Object |
Output |
|
PnIoTelegramType |
O |
|
Conformance Units |
|||||
|
PNRIO Cyclic Telegrams |
|||||
.
The Input Object shall contain the Input component of the Telegram.
The Output Object shall contain the Output component of the Telegram.
The PnIoTelegramType represents an Input Telegram as well as an Output Telegram and associated status information.
Table 57 – PnIoTelegramType Definition
|
Attribute |
Value |
||||
|
BrowseName |
PnIoTelegramType |
||||
|
IsAbstract |
False |
||||
|
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
|
Subtype of the BaseObjectType defined in OPC 10000-5. |
|||||
|
0:HasComponent |
Object |
<Nr_SignalName> |
|
PnIoSignalType |
MP |
|
0:HasProperty |
Variable |
IoTelegramImage |
0:ByteString |
0:PropertyType |
O, RO |
|
0:HasProperty |
Variable |
Length |
0:UInt16 |
0:PropertyType |
M, RO |
|
0:HasProperty |
Variable |
ProviderStatus |
PnIoTelegramStatusEnumeration |
0:PropertyType |
M, RO |
|
0:HasProperty |
Variable |
ConsumerStatus |
PnIoTelegramStatusEnumeration |
0:PropertyType |
O, RO |
|
Conformance Units |
|||||
|
PNRIO Cyclic Telegrams |
|||||
The <Nr_SignalName > Object references one Signal associated with an Input- or an Output Telegram (IO Telegram). <Nr> shall reflect the order of the Signal in the IO Telegram, consistent with the Offset property of the PnIoSignalType Object.
There shall exist as many References to as many Signal Objects as are needed to map the content of the IO Telegram.
The IoTelegramImage Property shall contain an octet string representation of the IO Telegram. If consistency of the content cannot be guaranteed, the IoTelegramImage Property shall not be provided.
The Length Variable contains the length (the number of bytes) of the IO Telegram.
The ProviderStatus Variable contains the data provider’s Qualifier for the IO Telegram (IOPS according to [PN Service]) encoded as PnIoTelegramStatusEnumeration.
The ConsumerStatus Variable contains the data consumer’s Qualifier for the IO Telegram (IOCS according to [PN Service] is not relevant for RIOforFA, therefore ConsumerStatus is optional) encoded as PnIoTelegramStatusEnumeration.
The PnIoSignalType gives access to the Variables containing the data of one Signal.
Table 58 – PnIoSignalType Definition
|
Attribute |
Value |
||||
|
BrowseName |
PnIoSignalType |
||||
|
IsAbstract |
False |
||||
|
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
|
Subtype of the 0:BaseObjectType defined in OPC 10000-5. |
|||||
|
0:HasProperty |
Variable |
SignalId |
0:UInt16 |
0:PropertyType |
O, RO |
|
0:HasProperty |
Variable |
Offset |
0:UInt16 |
0:PropertyType |
M, RO |
|
Conformance Units |
|||||
|
PNRIO Cyclic Telegrams |
|||||
The SignalId Variable contains an optional unique identifier for the IO signal.
The Offset Variable contains the number of the first byte of the IO data in the IO Telegram. The numbering shall start with 0.
A Signal Object shall only be provided if it relates to the functional aspect using a 0:RepresentsSameEntityAs Reference.