Skip to main content
Jump to: navigation, search

Difference between revisions of "BaSyx / Documentation"

m (Updates links)
 
(33 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== The Eclipse BaSyx middleware ==
+
== The Eclipse BaSyx Middleware ==
  
The BaSyx middleware groups Industrie 4.0 components around an end-to-end communication medium, the virtual automation bus (VAB). The VAB implements an object oriented communication approach that exports all information and services as objects with a unique identifier that are connected to one virtual and homogeneous communication network, even if it is realized by multiple physical networks. The VAB therefore defines five virtual communication primitives that are mapped to concrete physical networks. VAB primitives provide a unified way to access properties and operations of VAB objects in a network and machine independent manner. VAB gateways realize inter-network communication by mapping the comminication primitives to network specific telegrams, and this way enable end-to-end communication. Gateways furthermore may be used to integrate legacy devices by implementing a VAB interface for them.  
+
The BaSyx middleware groups Industrie 4.0 components around an end-to-end communication medium, the virtual automation bus (VAB). The VAB implements an object oriented communication approach that exports all information and services as objects with a unique identifier that are connected to one virtual and homogeneous communication network, even if it is realized by multiple physical networks. The VAB therefore defines five virtual communication primitives that are mapped to concrete physical networks. VAB primitives provide a unified way to access properties and operations of VAB objects in a network and machine independent manner. VAB gateways realize inter-network communication by mapping the communication primitives to network specific telegrams, and this way enable end-to-end communication. Gateways furthermore may be used to integrate legacy devices by implementing a VAB interface for them.  
 
+
The graphic below illustrates an architecture overview on the BaSyx middleware, its component types, and predefined component interfaces:
+
  
 +
The graphic below illustrates an architecture overview of the BaSyx middleware and its various components:
  
 
[[file:BaSyx.Architecture_Overview.png|center|1024px]]
 
[[file:BaSyx.Architecture_Overview.png|center|1024px]]
  
  
 
+
BaSys 4.0 compliant systems consist of the following core and optionally extended components:
BaSys 4.0 conforming production systems consist of the following types of communicating Industrie 4.0 components:
+
  
 
{| class="wikitable"
 
{| class="wikitable"
 +
|-
 +
! colspan="3" | Plattform Industrie 4.0 compliant components
 
|-
 
|-
 
! Component type
 
! Component type
 
! Description
 
! Description
 +
! Type
 +
|-
 +
| [[BaSyx_/_Documentation_/_AssetAdministrationShell|Asset Administration Shell]]
 +
| An Asset Administration Shell is a "standardized digital representation of the asset, corner stone of the interoperability between the applications managing the manufacturing systems. It identifies the Administration Shell and the assets represented by it, holds digital models of various aspects (submodels) and describes technical functionality exposed by the Administration Shell or respective
 +
assets." (Details of the Asset Administration Shell, 2018, p. 13, [https://www.plattform-i40.de/PI40/Redaktion/DE/Downloads/Publikation/2018-verwaltungsschale-im-detail.pdf])
 +
!style="background-color:green;color:white" | Core
 
|-
 
|-
| [[BaSyx Control Components|Control component]]
+
| [[BaSyx_/_Documentation_/_API_/_Submodel|Asset Administration Shell Submodels]]
|Control components realize BaSys 4.0 conforming service based Industrie 4.0 interfaces to assets. Assets may be devices, e.g. PLC controllers, sensors, actuators, but can represent any asset that realizes services or provide information, which also includes for example human workers. Control components provide a service based interface with callable services that e.g. drill a hole into a work piece. They define how a specific service is implemented, but do not decide about the orchestration of services, i.e. a control component does not decide when and of a particular service is called.
+
| "A Submodel defines a specific aspect of the asset represented by the Asset Administration Shell. A Submodel is used to structure the virtual representation and technical functionality of an Administration Shell into distinguishable parts. Each Submodel refers to a well-defined domain or subject matter. Submodels can become standardized and thus become submodels types. Submodels can have different life-cycles." (Details of the Asset Administration Shell, 2018, p. 46, [https://www.plattform-i40.de/PI40/Redaktion/DE/Downloads/Publikation/2018-verwaltungsschale-im-detail.pdf])
 +
!style="background-color:green;color:white" | Core
 
|-
 
|-
| [[BaSyx Control Components|Group component]]
+
| [[BaSyx_/_Documentation_/_API_/_Registry|Registry]]
 +
| The BaSys 4.0 Registry enables registration and lookup of Asset Administration Shells within defined system boundaries. Entities that provide Asset Administration Shells including their submodels may register and hence enable other participants to find them. The necessary information required for registration amongst others are unique identifiers for the Administration Shell and her respective Asset, endpoint information regarding the Asset Administration Shell's API and their submodel service provider.
 +
!style="background-color:green;color:white" | Core
 +
|-
 +
| Discovery
 +
| The BaSys 4.0 Discovery is a service that uses the registry to find Asset Administration Shells and Submodels. It provides additional functionalities to discover Asset Administration Shells and their Submodels based on filter criteria. These criteria are more advanced than a regular query parameter. The discovery service may provide indexing and/or crawling mechanisms to cache results from queried elements resp. find deeper information when searching.
 +
!style="background-color:green;color:white" | Core
 +
|-
 +
! colspan="3" | BaSys components
 +
|-
 +
! Component type
 +
! Description
 +
! Type
 +
|-
 +
| [[BaSyx_/_Documentation_/_ControlComponent|Control component]]
 +
|Control components realize BaSys 4.0 conforming service based Industrie 4.0 interfaces to assets. Assets may be devices, e.g. PLC controllers, sensors, actuators, but can represent any asset that realizes services or provide information, which also includes for example human workers. Control components provide a service based interface with callable services that e.g. drill a hole into a work piece. They define how a specific service is implemented, but do not decide about the orchestration of services, i.e. a control component does not decide when and if a particular service is called.
 +
!style="background-color:green;color:white" | Core
 +
|-
 +
| [[BaSyx_/_Documentation_/_ControlComponent|Group component]]
 
| Group components implement higher-level services that use services of other control and group components. Similar to control components, group component services provide the implementation of services but do not decide about when and why a provided service is invoked. Service callers are other components that orchestrate services.  
 
| Group components implement higher-level services that use services of other control and group components. Similar to control components, group component services provide the implementation of services but do not decide about when and why a provided service is invoked. Service callers are other components that orchestrate services.  
 +
!style="background-color:green;color:white" | Core
 
|-
 
|-
| [[BaSyx.VAB|Virtual Automation Bus]]
+
| [[BaSyx_/_Documentation_/_VAB|Virtual Automation Bus]]
| The virtual automation bus (VAB) is our implementation of an end-to-end communication for Industrie 4.0. It maps one communication semantic with five primitives (create/update/read/delete/invoke) to different networks and protocols. This way, the VAB can bridge networks via gateways, and can also integrate legacy devices into the virtual end-to-end communication network.
+
| The virtual automation bus (VAB) is our implementation of an end-to-end communication for Industrie 4.0. It maps one communication semantic with five primitives (create/retrieve/update/delete/invoke) to different networks and protocols. This way, the VAB can bridge networks via gateways, and can also integrate legacy devices into the virtual end-to-end communication network.
 +
!style="background-color:green;color:white" | Core
 
|-
 
|-
 
| [[BaSyx Device integration|Device integration]]
 
| [[BaSyx Device integration|Device integration]]
 
| Device integration components are VAB components that are part of devices and communicate with the VAB. Device manager components for example connect native status data to VAB objects and upload Asset Administration Shells (AAS) and Sub Models of their device to AAS servers.
 
| Device integration components are VAB components that are part of devices and communicate with the VAB. Device manager components for example connect native status data to VAB objects and upload Asset Administration Shells (AAS) and Sub Models of their device to AAS servers.
 +
!style="background-color:orange;color:white" | Extended
 
|-
 
|-
| Gateway
+
| [[BaSyx_/_Documentation_/_Gateway |Gateway]]
 
| Virtual Automation Bus protocol gateways bridges communication networks to enable inter-network communication. Every gateway needs to provide a mapping of all of the five BaSys communication primitives to its supported protocols to enable end-to-end communication. Gateways can be cascaded to bridge multiple networks.  
 
| Virtual Automation Bus protocol gateways bridges communication networks to enable inter-network communication. Every gateway needs to provide a mapping of all of the five BaSys communication primitives to its supported protocols to enable end-to-end communication. Gateways can be cascaded to bridge multiple networks.  
|-
+
!style="background-color:orange;color:white" | Extended
| Asset Administration Shell
+
| An Asset Administration Shell (AAS) is a digital object that represents a physical or non-physical entity. It provides common meta data about its entity and enables access to Asset Administration Shell sub models. Asset Administration Shells are provided by Asset Administration Shell providers to the Virtual Automation Bus.
+
|-
+
| [[BaSys 4.0 Sub Models|Asset Administration Shell sub models]]
+
| Asset Administration Shell sub models are part of Asset Administration Shells. They consist of (optionally nested) properties and operations with a defined meta model. AAS sub model providers provide different kinds of data as AAS sub models and hide the technology that is necessary to access native data sources. Asset Administration Shell sub model providers are implemented for example for configuration property files, SWL data bases, file systems, XML files, and numerous other sources of information. The BaSyx SDK provides a template implementation of an AAS sub model provider that may be used as foundation of tailored provider implementations.
+
|-
+
| Registry / Discovery
+
| The registry/discovery component enables registration and lookup of Asset Administration Shells. Entities that provide Asset Administration Shells and/or sub models may register them with the Registry and enable other components to access them.
+
 
|-
 
|-
 
| Strategy / Optimization  
 
| Strategy / Optimization  
| The Strategy/Optimization component calculates production plans and production schedules that define when, and on which machine a production step for a specific product will be executed. This component is usually a domain or plant specific application component.  
+
| The Strategy/Optimization component calculates production plans and production schedules that define when, and on which machine a production step for a specific product will be executed. This component is usually a domain or plant specific application component. Strategy, optimization and monitoring components are highly plant specific. These components use provided interfaces of other BaSys 4.0 components, but are not required to provide defined BaSys 4.0 interfaces.
 +
!style="background-color:orange;color:white" | Extended
 
|-
 
|-
 
| Process control
 
| Process control
 
| The process control component executes the production plans that the Strategy/Optimization component did create. Eclipse BaSyx will integrate for example the open source Activiti BPMN engine as process control engine.  
 
| The process control component executes the production plans that the Strategy/Optimization component did create. Eclipse BaSyx will integrate for example the open source Activiti BPMN engine as process control engine.  
 +
!style="background-color:orange;color:white" | Extended
 
|-
 
|-
 
| Monitoring
 
| Monitoring
 
| The monitoring component enables the monitoring of the production process. It for example collects and aggregates data for analysis or pushes selected and aggregated data to a dashboard.
 
| The monitoring component enables the monitoring of the production process. It for example collects and aggregates data for analysis or pushes selected and aggregated data to a dashboard.
 +
!style="background-color:orange;color:white" | Extended
 
|}
 
|}
  
 +
In addition to these components, BaSyx users may add other application specific components that connect to the network via an exposed endpoint depending on the communication technology (HTTP, OPC UA, BaSyx native) used.
  
In addition to these predefined component types, BaSyx users may add other application components that connect to the VAB and interact with other components and their exported VAB objects. Every VAB object has a defined and unique ID:
+
== BaSyx Identification Naming Convention ==
 +
BaSys provides a unified way to identify types and instances regardless whether it is an information model (Submodel, Concept Description, Data Element, etc.) or an asset type resp. asset instance. These identifiers can be used as unique identifier for Asset Administation Shells and Assets as well as for semantic references within the meta-model elements of the Asset Administration Shell:
  
* [[BaSyx.ID|BaSyx URI ID schema]]
+
* [[BaSyx_/_Documentation_/_Identification|BaSyx URI ID schema]]
  
 +
== BaSyx Components ==
  
BaSyx defines interfaces for predefined component types. Interfaces are well-defined interaction points in the BaSys 4.0 architecture. They enable the substitution of component implementations and the development of conforming implementations by 3rd parties. BaSys 4.0 components and BaSyx components define HTTP-REST interfaces on middleware and plant levels, as well as OPC-UA and native TCP BaSyx interfaces on device level. Conforming implementations of BaSys 4.0 components need to implement at least the interfaces shown in the above figure and the following table. The BaSyx platform provides a reference implementation for core components that are necessary to create and deploy an Industrie 4.0 solution.
+
BaSyx defines interfaces for all components contained in the architecture overview above. Interfaces are well-defined descriptions of the interaction pattern (contract) and the necessary information models (payload) for the interaction between communication participants. All BaSyx components define at least an HTTP/REST interface on middle-ware and application level. On field device level, OPC UA as well as native BaSyx/TCP are applicable for component interfaces.  
 +
 
 +
Compliant implementations of BaSyx components need to implement at least the interfaces depicted in the following table. BaSyx provides reference implementations for core components that are necessary to create and deploy an Industrie 4.0 solution.
  
  
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
! Component type
+
! Component
! Necessary provided interfaces
+
! Provided Interfaces
! Interface type
+
! Available Technologies
 
|-
 
|-
 
| Control component
 
| Control component
| [[BaSyx.ControlComponent|BaSyx control component API]]
+
| [[BaSyx_/_Documentation_/_ControlComponent|BaSyx control component API]]
 
| OPC-UA, BaSyx native
 
| OPC-UA, BaSyx native
 
|-
 
|-
 
| Group component
 
| Group component
| [[BaSyx.ControlComponent|BaSyx control component API]]
+
| [[BaSyx_/_Documentation_/_ControlComponent|BaSyx control component API]]
 
| OPC-UA, BaSyx native
 
| OPC-UA, BaSyx native
 
|-
 
|-
Line 79: Line 107:
 
|-
 
|-
 
| Asset Administration Shell
 
| Asset Administration Shell
| AAS
+
| [[BaSyx_/_Documentation_/_AssetAdministrationShell|BaSyx Asset Administration Shell Service Provider API]]
 
| HTTP-REST
 
| HTTP-REST
 
|-
 
|-
| Asset Administration Shell sub models
+
| Asset Administration Shell Submodels
| [[BaSyx.Submodel|BaSyx submodel provider API]]
+
| [[BaSyx_/_Documentation_/_API_/_Submodel|BaSyx Submodel Service Provider API]]
 
| HTTP-REST
 
| HTTP-REST
 
|-
 
|-
| Registry / Discovery
+
| Registry
| [[Basyx.Discovery|BaSyx discovery API]]
+
| [[BaSyx_/_Documentation_/_API_/_Registry|BaSyx Registry API]]
 
| HTTP-REST
 
| HTTP-REST
 
|-
 
|-
Line 104: Line 132:
  
  
Strategy / optimization and Monitoring components are highly plant specific. These components use provided interfaces of other BaSys 4.0 components, but are not required to provide defined BaSys 4.0 interfaces.
+
Eclipse BaSyx implements the following ready-to-use components:
  
 +
'''Asset Administration Shell & Submodel Providers'''
  
== BaSyx component types ==
+
Asset Administration Shell and Submodel providers provide generic Virtual Automation Bus objects, Asset Administration Shells, and/or Submodels with a defined ID on the network.  
 
+
Eclipse BaSyx implements the following ready-to-use components and component templates as Java Servlets in the package basys.components:
+
 
+
 
+
'''AAS/Sub model providers'''
+
 
+
AAS/Sub model providers provide generic Virtual Automation Bus objects, Asset Administration Shells, and/or sub models with a defined ID on the virtual automation bus.  
+
 
* [[BaSyx CFG sub model provider|CFG Submodel provider]]
 
* [[BaSyx CFG sub model provider|CFG Submodel provider]]
 
* [[BaSyx RAW AAS/Submodel provider|RAW AAS/Submodel provider]]
 
* [[BaSyx RAW AAS/Submodel provider|RAW AAS/Submodel provider]]
Line 122: Line 144:
  
  
'''Registry providers'''
+
'''Registry Providers'''
  
Registry providers enable Industrie 4.0 devices to register asset administration shells (AAS), and AAS users to lookup a specific asset administration shell.
+
Ready-to-use reference implementations of the [[BaSyx.Registry|BaSyx Registry API]] enable Industrie 4.0 components to register their Asset Administration Shells resp. users/applications to find those in a BaSyx compliant manner.
* Precompiled registry
+
* Pre-compiled Registry (Local, Cloud & On-Premises via Docker)
* File based registry
+
* Simple File-based Registry (Local & Docker)
* SQL based dynamic registry
+
* SQL-based Dynamic Registry
  
  
'''Control component templates (Java/C++)'''
+
'''Virtual Automation Bus Providers'''
  
Control components implement and connect production services to the Industrie 4.0 infrastructure. Device control components usually integrate production devices into the Industrie 4.0 infrastructure, but may also connect to worker guidance systems and therefore integrate services provided by human workers. Group control components use other control components to provide higher-level services.  
+
Low-level providers provide generic Virtual Automation Bus objects and do not make an assumption on the structure. Thus, all types of objects can be offered by such a provider.
* ''under construction: control component template (Java/C++)''
+
* [[BaSyx_/_Documentation_/_HashMap_Provider_|HashMap provider]]
 +
* [[BaSyx_/_Documentation_/_FileSystem_Provider_|FileSystem provider]]
 +
* [[BaSyx_/_Documentation_/_Lambda_Provider_|Lambda provider]]
  
  
{| class="wikitable"
+
'''Control Component Templates'''
| BaSyx project links:  [[BaSyx | Project BaSyx main wiki page]]  <nowiki>|</nowiki> [[BaSyx.WhatIsBasyx | What is BaSyx?]]  <nowiki>|</nowiki>  [[BaSyx.Documentation | BaSyx Developer Documentation]]
+
 
|}
+
<<under construction>>
 +
 
 +
== BaSyx SDK Architecture ==
 +
The documentation of the BaSyx SDK architecture is provided on its own [[BaSyx:BaSyx.Documentation.SDK|documentation page]].

Latest revision as of 10:03, 12 March 2020

The Eclipse BaSyx Middleware

The BaSyx middleware groups Industrie 4.0 components around an end-to-end communication medium, the virtual automation bus (VAB). The VAB implements an object oriented communication approach that exports all information and services as objects with a unique identifier that are connected to one virtual and homogeneous communication network, even if it is realized by multiple physical networks. The VAB therefore defines five virtual communication primitives that are mapped to concrete physical networks. VAB primitives provide a unified way to access properties and operations of VAB objects in a network and machine independent manner. VAB gateways realize inter-network communication by mapping the communication primitives to network specific telegrams, and this way enable end-to-end communication. Gateways furthermore may be used to integrate legacy devices by implementing a VAB interface for them.

The graphic below illustrates an architecture overview of the BaSyx middleware and its various components:

BaSyx.Architecture Overview.png


BaSys 4.0 compliant systems consist of the following core and optionally extended components:

Plattform Industrie 4.0 compliant components
Component type Description Type
Asset Administration Shell An Asset Administration Shell is a "standardized digital representation of the asset, corner stone of the interoperability between the applications managing the manufacturing systems. It identifies the Administration Shell and the assets represented by it, holds digital models of various aspects (submodels) and describes technical functionality exposed by the Administration Shell or respective

assets." (Details of the Asset Administration Shell, 2018, p. 13, [1])

Core
Asset Administration Shell Submodels "A Submodel defines a specific aspect of the asset represented by the Asset Administration Shell. A Submodel is used to structure the virtual representation and technical functionality of an Administration Shell into distinguishable parts. Each Submodel refers to a well-defined domain or subject matter. Submodels can become standardized and thus become submodels types. Submodels can have different life-cycles." (Details of the Asset Administration Shell, 2018, p. 46, [2]) Core
Registry The BaSys 4.0 Registry enables registration and lookup of Asset Administration Shells within defined system boundaries. Entities that provide Asset Administration Shells including their submodels may register and hence enable other participants to find them. The necessary information required for registration amongst others are unique identifiers for the Administration Shell and her respective Asset, endpoint information regarding the Asset Administration Shell's API and their submodel service provider. Core
Discovery The BaSys 4.0 Discovery is a service that uses the registry to find Asset Administration Shells and Submodels. It provides additional functionalities to discover Asset Administration Shells and their Submodels based on filter criteria. These criteria are more advanced than a regular query parameter. The discovery service may provide indexing and/or crawling mechanisms to cache results from queried elements resp. find deeper information when searching. Core
BaSys components
Component type Description Type
Control component Control components realize BaSys 4.0 conforming service based Industrie 4.0 interfaces to assets. Assets may be devices, e.g. PLC controllers, sensors, actuators, but can represent any asset that realizes services or provide information, which also includes for example human workers. Control components provide a service based interface with callable services that e.g. drill a hole into a work piece. They define how a specific service is implemented, but do not decide about the orchestration of services, i.e. a control component does not decide when and if a particular service is called. Core
Group component Group components implement higher-level services that use services of other control and group components. Similar to control components, group component services provide the implementation of services but do not decide about when and why a provided service is invoked. Service callers are other components that orchestrate services. Core
Virtual Automation Bus The virtual automation bus (VAB) is our implementation of an end-to-end communication for Industrie 4.0. It maps one communication semantic with five primitives (create/retrieve/update/delete/invoke) to different networks and protocols. This way, the VAB can bridge networks via gateways, and can also integrate legacy devices into the virtual end-to-end communication network. Core
Device integration Device integration components are VAB components that are part of devices and communicate with the VAB. Device manager components for example connect native status data to VAB objects and upload Asset Administration Shells (AAS) and Sub Models of their device to AAS servers. Extended
Gateway Virtual Automation Bus protocol gateways bridges communication networks to enable inter-network communication. Every gateway needs to provide a mapping of all of the five BaSys communication primitives to its supported protocols to enable end-to-end communication. Gateways can be cascaded to bridge multiple networks. Extended
Strategy / Optimization The Strategy/Optimization component calculates production plans and production schedules that define when, and on which machine a production step for a specific product will be executed. This component is usually a domain or plant specific application component. Strategy, optimization and monitoring components are highly plant specific. These components use provided interfaces of other BaSys 4.0 components, but are not required to provide defined BaSys 4.0 interfaces. Extended
Process control The process control component executes the production plans that the Strategy/Optimization component did create. Eclipse BaSyx will integrate for example the open source Activiti BPMN engine as process control engine. Extended
Monitoring The monitoring component enables the monitoring of the production process. It for example collects and aggregates data for analysis or pushes selected and aggregated data to a dashboard. Extended

In addition to these components, BaSyx users may add other application specific components that connect to the network via an exposed endpoint depending on the communication technology (HTTP, OPC UA, BaSyx native) used.

BaSyx Identification Naming Convention

BaSys provides a unified way to identify types and instances regardless whether it is an information model (Submodel, Concept Description, Data Element, etc.) or an asset type resp. asset instance. These identifiers can be used as unique identifier for Asset Administation Shells and Assets as well as for semantic references within the meta-model elements of the Asset Administration Shell:

BaSyx Components

BaSyx defines interfaces for all components contained in the architecture overview above. Interfaces are well-defined descriptions of the interaction pattern (contract) and the necessary information models (payload) for the interaction between communication participants. All BaSyx components define at least an HTTP/REST interface on middle-ware and application level. On field device level, OPC UA as well as native BaSyx/TCP are applicable for component interfaces.

Compliant implementations of BaSyx components need to implement at least the interfaces depicted in the following table. BaSyx provides reference implementations for core components that are necessary to create and deploy an Industrie 4.0 solution.


Component Provided Interfaces Available Technologies
Control component BaSyx control component API OPC-UA, BaSyx native
Group component BaSyx control component API OPC-UA, BaSyx native
Gateway Gateway Any to any
Asset Administration Shell BaSyx Asset Administration Shell Service Provider API HTTP-REST
Asset Administration Shell Submodels BaSyx Submodel Service Provider API HTTP-REST
Registry BaSyx Registry API HTTP-REST
Strategy / Optimization --- HTTP-REST
Process Control Process management, Process execution HTTP-REST
Monitoring --- HTTP-REST


Eclipse BaSyx implements the following ready-to-use components:

Asset Administration Shell & Submodel Providers

Asset Administration Shell and Submodel providers provide generic Virtual Automation Bus objects, Asset Administration Shells, and/or Submodels with a defined ID on the network.


Registry Providers

Ready-to-use reference implementations of the BaSyx Registry API enable Industrie 4.0 components to register their Asset Administration Shells resp. users/applications to find those in a BaSyx compliant manner.

  • Pre-compiled Registry (Local, Cloud & On-Premises via Docker)
  • Simple File-based Registry (Local & Docker)
  • SQL-based Dynamic Registry


Virtual Automation Bus Providers

Low-level providers provide generic Virtual Automation Bus objects and do not make an assumption on the structure. Thus, all types of objects can be offered by such a provider.


Control Component Templates

<<under construction>>

BaSyx SDK Architecture

The documentation of the BaSyx SDK architecture is provided on its own documentation page.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.