Listed in this Annex are the requirements for the compliance statement from the supplier of the PLCopen OPC UA Client for IEC 61131-3. The compliance statement consists of two main groups: supported data types and supported Function Blocks, in combination with the applicable inputs and outputs. The supplier is required to fill out the tables for the used data types and Function Blocks, according to their product, committing their support to the specification.

By submitting these tables to PLCopen, and after approval by PLCopen, the list will be published on the PLCopen website, www.PLCopen.org, as well as a shortform overview, as specified in ‎Appendix A.2 Overview of the Functionblocks and A.2 Overview of the Functionblocks as below.

In addition to this approval, the supplier is granted access and usage rights of the PLCopen OPC UA Client logo, as described in Annex B:

Function Blocks and Inputs and Outputs

An implementation which claims compliance with this PLCopen OPC UA specification shall offer a set of Function Blocks for communication, meaning one or more Function Blocks, with at least the basic input and output variables, marked as “B” in the tables. These inputs and outputs have to be supported to be compliant.

For higher-level systems and future extensions any subset of the extended input and output variables, marked as “E” in the tables can be implemented.

Vendor specific additions are marked with “V”, and can be listed as such in the supplier documentation.

• Basic input/output variables are mandatoryMarked in the tables with the letter “B”
• Extended input /output variables are optional Marked in the tables with the letter “E”
• Vendor Specific additionsMarked in the vendor’s compliance documentation with “V”

All the vendor specific items will not be listed in the comparison table on the PLCopen website, but in the detailed vendor specific list, which also is published.

All vendor specific in- and outputs of all FBs must be listed in the certification list of the supplier. With this, the certification listing from a supplier describes all the I/Os of the relevant FBs, including vendor-specific extensions, and thus showing the complete FBs as used by the supplier.

For compliance reason we identify in A.2 the difference of “V1.0” or “V1.1” or “No” (empty field) support.

Supplier name
Supplier address
City
Country
Telephone
Fax
Email address
Product Name
Product version
Release date

I hereby state that the following tables as filled out and submitted do match our product as well as the accompanying user manual, as stated above.

Name of representation (person):

Date of signature (dd/mm/yyyy):

Signature:

Chapter	Function Block	Supported V1.0 / V1.1 / V1.2 / No	Comments
7.1	UA_Connect
0	UA_Disconnect
7.3	UA_NamespaceGetIndexList
7.4	UA_ServerGetUriByIndex
7.5	UA_ServerGetIndexByUriList
7.6	UA_TranslatePathList
7.7	UA_NodeGetHandleList
7.8	UA_NodeReleaseHandleList
7.9	UA_NodeGetInformation
7.10	UA_SubscriptionCreate
7.11	UA_SubscriptionDelete
7.12	UA_SubscriptionModify
0	UA_SubscriptionProcessed
7.14	UA_MonitoredItemAddList
7.15	UA_MonitoredItemRemoveList
7.16	UA_MonitoredItemModifyList
7.17	UA_MonitoredItemOperateList
7.18	UA_ReadList
7.19	UA_WriteList
7.20	UA_MethodGetHandleList
7.21	UA_MethodReleaseHandleList
7.22	UA_MethodCall
7.23	UA_Browse
7.24	UA_EventItemAdd
7.25	UA_EventItemOperateList
7.26	UA_EventItemRemoveList
7.27	UA_HistoryUpdate
8.1	UA_ConnectionGetStatus
10	Phased out Functionsblocks
10.1	UA_NamespaceGetIndex
10.2	UA_TranslatePath
10.3	UA_NodeGetHandle
10.4	UA_NodeReleaseHandle
10.5	UA_NodeGetInfo
10.6	UA_SubscriptionOperate
10.7	UA_MonitoredItemAdd
10.8	UA_MonitoredItemRemove
10.9	UA_MonitoredItemOperate
10.10	UA_Read
10.11	UA_Write
10.12	UA_MethodGetHandle
10.13	UA_MethodReleaseHandle