0. AAS 작성 시 참고사항

OPCUA 태그 정보를 이용하여 AAS 작성 시, 데이터 타입은 아래와 같이 변환되니 참고하여 작성바랍니다.
[AAS Datatype -> OPCUA Datatype]
nonNegativeInteger -> UInt32
unsignedLong -> UInt64
unsignedShort -> UInt16
Byte/unsignedByte -> Byte
Integer/Int -> Int32
Short -> Int16

1. Introduction

This program is used to convert the AAS files into a suitable format for AAS-based cloud data acquisition & storage system and MOS(Manufacturing Operation System), and was developed to be used in Windows 10 (and 11) environment to provide the user convenience.

2. Installation

Step 0

• Put the downloaded files in C drive.
  

Step 1

• Run the 00.PackageChecker.exe. In this progress, This executable checks the installed Python version and packages.
• If the Python is not installed, Opens the Python download window. Available Python versions are 3.8.2~3.11.xx.

Step 2

• After downloading all the packages through the Package Checker program, run the 01.Start_AAS_Parser_WS.exe executable file.
• The result is as follow:

[Note] Create nodeset.xml

Value tags may not be created if you are using the latest module version. Check the module version to create the nodeset.xml file.

• $ pip3 list

If you don't have the modules below, Install them.

modul_name	version	Uninstall commands	Install commands
asyncua	0.9.14	$pip3 uninstall asyncua	$pip3 install asyncua==0.9.14
xmlschema	1.1.1	$pip3 uninstall xmlschema	$pip3 install xmlschema==1.1.1
xmltodict	0.12.0	$pip3 uninstall xmltodict	$pip3 install xmltodict==0.12.0
asyncio	3.4.3	$pip3 uninstall asyncio	$pip3 install asyncio==3.4.3

Check the installed versions again with the command below.

• $ pip3 list

3. Running on Windows

Step 0

• Click '01.Start_AAS_Parser_WS.exe' to run the server.
• [Note] To use this program, an XML file created by AASX Package Explorer is required.

Step 1

• You have to put the extension(.xml) into the AAS directory(C:\AAS_Parser_V20230105\aas).
• Upload the XML file using the two buttons below.

Step 2

• After uploading the XML file, click the button 'Converting your AAS model' on the left table
• Wait for a while until the 3 files(nodeset.xml, engineering.csv, syscfg.json) are created.

Step 3

• In the progress, you can see the creation process of the 3 converted files through your command prompt screen.
• You can also check it through the output log button on the left table.

Step 4

• Now you can download the 3 files created. Click the Download button on the left table.

Step 5

• Edit the downloaded files(e.g. engineering.csv) and upload them to the AAS server and Edge Gateway server.

4. How to edit an AAS Model for utilizing this program.

Step 0

• Using the AASX Package Explorer provided by IDTA(Industrial Digital Twine Association), you can easily create AAS models on Windows operating systems.
• Create your own AAS model like below or Download the already created AAS template model.

Step 1

• Create CloudDataSolution AAS in the AASX Package Explorer.
• Then create CloudSolution Submodel and EdgeSolution Submodel. The submodels are composed of the following submodel elements.
• [Note 1] Value and valueType of all submodel elements (especially properties) must be filled in.
• [Note 2] If you have multiple field devices to communicate with the edge gateway, model it as follows.

Step 2

• Now you can convert your AAS model using the AAS Parser Web Server.
• Follow the 3. Running on Windows guide to convert your AAS model.
• Example of template conversion result:

5. How to edit configuration files

Step 1 : syscfg.json

• This file is for applying basic communication information.
• If you create CloudDataSolution AAS and fill contents successfully, Basic Configuration will be created as below :
  
• But if you get empty syscfg.json file, you just can fill contents manually.
• (Recommendation : editing AAS file and try again.)

Step 2 : engineering.csv

• This file is for mapping field data tags with AAS tags.
  
• A, E, F Columns are created automatically and B, C, D Columns are needed to be filled manually.
• Details are as follows :
  A : AAS Tag name from AAS file. This doesn't need to be modified.
  B : Gateway name. This column should be filled with the gateway name (defined in AAS) from which the data will be collected.
  C : Device name. This column should be filled with the field device name (defined in AAS) from which the data will be collected.
  D : Field Tag name. This column should be filled with the field data tag name(OPCUA). It contains namespace and tag identifier.
  E : Sampling rate. Basic value is 50 and engineer can change this column with appropriate value.
  F : Array index. If field data tag is an array, engineer should fill this column with array index. But field data tag is not an array, it should be filled with the value : -1(default value).

Step 3 : nodeset.xml

• This file is the OPCUA information model.
• It is recommended not to modify it arbitrarily.