%0 Conference Paper %1 vonArnim_2019_OpcUaAddressSpaceGeneration %A von Arnim, Christian %A Friedl, Sebastian %A Lechler, Armin %A Verl, Alexander %B 2019 IEEE 17th International Conference on Industrial Informatics (INDIN) %D 2019 %K OPCUA communication-systems information-modelling interoperability isw-2019 migration myown %P 959-964 %R 10.1109/INDIN41052.2019.8972189 %T Automated OPC UA address space generation from existing data structures %U https://ieeexplore.ieee.org/document/8972189/ %V 1 %X If existing communication systems are converted to OPC UA, an OPC UA information model is required for the existing data structures. In small systems, an information model can be created manually with reasonable effort. In systems with numerous data structures, however, the effort for manual creation is too demanding. In order to continue using the existing data structures in the code without having to handle OPC UA-specific data structures, a transformation between the existing data structures and the OPC UA information model is necessary. This article presents a possibility of generating an OPC UA information model by a description of the existing data structures, e.g. generated based on ROS messages. The description of data structures is evaluated at runtime and linked with the existing data structures. The different representations for the different access types (read, request/response) in the OPC UA information model are discussed. In addition, an OPC UA client can read the information model from the descriptions of the data structures and write the read data back to the original data structure. In this way, both the provision of the data via OPC UA and the reception are possible. The adaptation effort of the existing software is minimal, since the existing structures are automatically populated and can still be used as usual.

@inproceedings{vonArnim_2019_OpcUaAddressSpaceGeneration, abstract = {If existing communication systems are converted to OPC UA, an OPC UA information model is required for the existing data structures. In small systems, an information model can be created manually with reasonable effort. In systems with numerous data structures, however, the effort for manual creation is too demanding. In order to continue using the existing data structures in the code without having to handle OPC UA-specific data structures, a transformation between the existing data structures and the OPC UA information model is necessary. This article presents a possibility of generating an OPC UA information model by a description of the existing data structures, e.g. generated based on ROS messages. The description of data structures is evaluated at runtime and linked with the existing data structures. The different representations for the different access types (read, request/response) in the OPC UA information model are discussed. In addition, an OPC UA client can read the information model from the descriptions of the data structures and write the read data back to the original data structure. In this way, both the provision of the data via OPC UA and the reception are possible. The adaptation effort of the existing software is minimal, since the existing structures are automatically populated and can still be used as usual.}, added-at = {2020-02-03T07:33:28.000+0100}, author = {von Arnim, Christian and Friedl, Sebastian and Lechler, Armin and Verl, Alexander}, biburl = {https://puma.ub.uni-stuttgart.de/bibtex/237821900e8a52e8da97c1d8fd8d9fc85/isw-bibliothek}, booktitle = {2019 IEEE 17th International Conference on Industrial Informatics (INDIN)}, doi = {10.1109/INDIN41052.2019.8972189}, interhash = {cf375099f700a15e78d26be15596ceeb}, intrahash = {37821900e8a52e8da97c1d8fd8d9fc85}, issn = {1935-4576}, keywords = {OPCUA communication-systems information-modelling interoperability isw-2019 migration myown}, month = {07}, pages = {959-964}, timestamp = {2021-06-17T10:59:41.000+0200}, title = {Automated OPC UA address space generation from existing data structures}, url = {https://ieeexplore.ieee.org/document/8972189/}, volume = 1, year = 2019 }