COMP4DRONES - User contributions [en]

WP5-02

2022-10-10T13:09:15Z

Ikerlan:

=Security Management Toolchain=
{|class="wikitable"
| ID|| WP5-02
|-
| Contributor || IK
|-
| Levels || Functional
|-
| Require || Communication service to obtain security data from
|-
| Provide || Intrusion detection, attack prevention and security automatic updates.
|-
| Input || Drone communication and process information.
|-
| Output || Alerts to detect anomalous behaviour and act if it has been required.
|-
| C4D building block || Security, Communications.
|-
| TRL || 4
|}

==Detailed Description==

The component developed by IKERLAN is a Security Management Toolchain which is aimed towards the monitoring and control of the drone’s security. The main objective of this component is to increase the security level of drone-to-drone and drone-to-infrastructure communication through the identification and correction of issues that may suppose a threat. Several attacks that may potentially compromise the security of the communication links have been considered, such as eavesdropping or spoofing.. Considering the above, the Security Management Toolchain provides different monitoring, update, and visualization features in order to detect anomalous behavior and vulnerabilities within the drone.

The drone may present potential vulnerabilities due to multiple factors (e.g., outdated software versions, abnormal execution patterns, abnormal communications patterns, etc.) that may result in different cyber-attacks. This component addresses such vulnerabilities by the continuous monitoring of key security parameters. This allows to have an overall picture of the system, to detect faulty configuration that may suppose a risk and be able to change system configuration with the objective of addressing such issues. In case a software component version (applications, libraries, or certificates) is not correctly updated, it would be easier to attack and therefore it would become a potential target for any kind of cyber-attacks. The main security aspects addressed by this component are cyberthreat identification and cyberattack detection, such as identity spoofing, brute force, elevation of privilege, eavesdropping, hacking, among others.

===Design and Implementation===

The core of this component is built around a software solution that combines a Security Information Management (SIM) and Security Event Management (SEM) system, a Security Information and Event Management (SIEM). A framework based on a SIEM solution, collects and aggregates security data from network devices, servers, domain controllers, etc., bringing it together into a single centralized platform. It provides security data analysis from the data generated by applications and network hardware. In essence, a SIEM is a data aggregator, search, and reporting system, which stores, correlates, and applies analytics to security data to discover trends, detect threats and enable alerts. Thus, the Security Management Tool enables to carry out log data analysis, intrusions and malware detection, file integrity monitoring, configuration assessment or vulnerability detection.

Detection methodologies has been integrated to obtain the required security information and be able to send logs to the SIEM. To this end, this component includes both Host-based Intrusion Detection System (HIDS) and Network Intrusion Detection System (NIDS), which monitor network traffic for suspicious activities and possible threats, and issues alerts when such activities are discovered, generating system logs and identifying the design of usual attacks. In our use-case, the HIDS will monitor and analyze the internal aspects of the on-board device located in the drone, while the NIDS will examine the network traffic between the drone platform and the SIEM.

The detail for these modules and the whole component is divided between D5.5 and the D5.6 documents. To obtain a deeper insight of overall work, it is suggested to read both documents.

==Contribution and Improvements==
The contribution of this component focuses on the security of the drone. The inclusion of an IDS into the world of IoT devices is something that is going to be needed in the near future. With this component we have prooved that drones and IDS can coexist and work together without problems.

This component has been tuned and improved along the project, adpating to the needs of the devices is has to work with. Along the process, while some functionalities were added and configured, continous tests wer done to check the correct implementation. Not only that, the idea to add new functionalities, such as the automatic update of vulnerable components, came from a research to identify the best way to help on security on the drone area of knowledge. This implementation, even it may see complex at first wil help detecting attacks and preventing them, making the drones more secure, and in consecuence more efficient.

Component repository

2022-09-26T11:56:48Z

Ikerlan: /* Components list */

This repository aims at providing common components usable in different application domains, in particular those covered by project use-cases.

The requirements for using a components will be listed, as well as a documentation on how to use it. The component itself will be hosted by the partner who provides it.

==Components list==

{| class="wikitable"
|ID
|Contributor
|Title
|-
|[[WP3-01]]
|IKERLAN
|Safety function - Pre-Certified SOM
|-
|[[WP3-02]]
|EDI
|Modular SoC-based embedded reference architecture
|-
|[[WP3-03]]
|BUT
|Sensor information algorithms
|-
|[[WP3-04]]
|HIB
|Computer Vision Components for drones
|-
|[[WP3-10]]
|IFAT
|Component for trusted communication
|-
|[[WP3-13]]
|ENAC
|Paparazzi UAV
|-
|[[WP3-14_1]]
|ENSMA
|Collision avoidance and geo-fencing
|-
|[[WP3-14_2]]
|ENSMA
|Distributed control of multi-drone system
|-
|[[WP3-15_1]]
|ACORDE
|UWB based indoor positioning
|-
|[[WP3-15_2]]
|ACORDE
|Multi-antenna GNSS/INS based navigation
|-
|[[WP3-16]]
|SCALIAN
|EZ_Chains Fleet Architecture
|-
|[[WP3-19_1]]
|IMEC
|Hyperspectral payload
|-
|[[WP3-19_2]]
|IMEC
|Hyperspectral image processing
|-
|[[WP3-20]]
|MODIS
|Multi-sensor positioning
|-
|[[WP3-22]]
|UNIMORE
|Onboard Compute Platform Desing Methodology
|-
|[[WP3-24]]
|UNIVAQ
|Efficient digital implementation of controllers
|-
|[[WP3-26]]
|UWB
|Droneport: an autonomous drone battery management system
|-
|[[WP3-28]]
|UNISS
|Accelerator Design Methodology for OOCP
|-
|[[WP3-36_1]]
|UDANET
|Smart and predictive energy management system
|-
|[[WP3-36_2]]
|UDANET
|AI drone system modules
|-
|[[WP3-37]]
|Aitek
|Video and data analytics
|-
|[[WP4-2]]
|SCALIAN
|EZ_Land Precision landing
|-
|[[WP4-5]]
|SCALIAN
|AI detection for clearance
|-
|[[WP4-10]]
|ALM
|Cooperative Planner
|-
|[[WP4-14]]
|ALM
|Map Enhancement Service
|-
|[[WP4-15]]
|ALM
|Visual Analytics
|-
|[[WP4-16]]
|ACORDE
|Enhanced Navigation Software
|-
|[[WP4-17]]
|ACORDE
|Anchor&Tag firmware of the Indoor Positioning System
|-
|[[WP4-18_A]]
|TEKNE
|Drone-Rover Transponder
|-
|[[WP4-20]]
|ALM
|Attractor-based Navigation
|-
|[[WP4-22]]
|ALM
|Shared Reference Frame
|-
|[[WP4-32]]
|SHERPA
|Dynamic control development for navigation and precision landing
|-
|[[WP4-33]]
|UNIVAQ
|Autonomy, cooperation, and awareness
|-
|[[WP4-36]]
|IMCS
|Autonomous Decision Making in Critical Situations
|-
|[[WP4-37]]
|IMCS
|Algorithms for Runtime Safety Monitoring
|-
|[[WP4-39]]
|HIB
|Simulated data aggregator supporting intelligent decision in computer vision components
|-
|[[WP4-42]]
|SCALIAN
|AI Stabilization
|-
|[[WP5-02]]
|IKERLAN
|Security Management Toolchain
|-
|[[WP5-03]]
|SCALIAN
|EZ_Com Safe fleet communication
|-
|[[WP5-09]]
|ABI
|Communication scheme for unified system management
|-
|[[WP5-05_A]]
|TEKNE
|LP-WAN for UAV identification and monitoring
|-
|[[WP5-11_ACO]]
|ACORDE
|Navigation system with anti-jamming and anti-spoofing features
|-
|[[WP5-16-AIT]]
|AIT
|Cryptographic algorithms adapted for drones
|-
|[[WP5-19_ACO]]
|ACORDE
|Robust communication for an improved Indoor Positioning System
|-
|[[WP6-P4R]]
|CEA
|Model driven engineering
|-
|[[WP6-ESDE]]
|ACORDE
|ESL embedded SW Design Environment (ESDE)
|-
|[[WP6-IPS-MAF]]
|ACORDE
|Indoor Positioning System Modelling&Analysis Framework (IPS-MAF)
|-
|[[WP6-17]]
|UNIVAQ
|HW/SW CO-DEsign of HEterogeneous Parallel dedicated Systems (HEPSYCODE)
|-
|[[WP6-34]]
|UNIVAQ
|HEPSYCODE SystemC SIMulator Version 2.0 (HEPSIM2)
|}

WP5-02

2022-09-26T10:42:32Z

Ikerlan: Created page with "=Securityt Management Toolchain= {|class="wikitable" | ID|| WP5-02 |- | Contributor || IK |- | Levels || Functional |- | Require || Communication service to obtain security data from |- | Provide || Intrusion detection, attack prevention and security automatic updates. |- | Input || Drone communication and process information. |- | Output || Alerts to detect anomalous behaviour and act if it has been required. |- | C4D building block || Security, Commu..."

=Securityt Management Toolchain=
{|class="wikitable"
| ID|| WP5-02
|-
| Contributor || IK
|-
| Levels || Functional
|-
| Require || Communication service to obtain security data from
|-
| Provide || Intrusion detection, attack prevention and security automatic updates.
|-
| Input || Drone communication and process information.
|-
| Output || Alerts to detect anomalous behaviour and act if it has been required.
|-
| C4D building block || Security, Communications.
|-
| TRL || 4
|}

==Detailed Description==

The component developed by IKERLAN is a Security Management Toolchain which is aimed towards the monitoring and control of the drone’s security. The main objective of this component is to increase the security level of drone-to-drone and drone-to-infrastructure communication through the identification and correction of issues that may suppose a threat. Several attacks that may potentially compromise the security of the communication links have been considered, such as eavesdropping or spoofing.. Considering the above, the Security Management Toolchain provides different monitoring, update, and visualization features in order to detect anomalous behavior and vulnerabilities within the drone.

The drone may present potential vulnerabilities due to multiple factors (e.g., outdated software versions, abnormal execution patterns, abnormal communications patterns, etc.) that may result in different cyber-attacks. This component addresses such vulnerabilities by the continuous monitoring of key security parameters. This allows to have an overall picture of the system, to detect faulty configuration that may suppose a risk and be able to change system configuration with the objective of addressing such issues. In case a software component version (applications, libraries, or certificates) is not correctly updated, it would be easier to attack and therefore it would become a potential target for any kind of cyber-attacks. The main security aspects addressed by this component are cyberthreat identification and cyberattack detection, such as identity spoofing, brute force, elevation of privilege, eavesdropping, hacking, among others.

===Design and Implementation===

The core of this component is built around a software solution that combines a Security Information Management (SIM) and Security Event Management (SEM) system, a Security Information and Event Management (SIEM). A framework based on a SIEM solution, collects and aggregates security data from network devices, servers, domain controllers, etc., bringing it together into a single centralized platform. It provides security data analysis from the data generated by applications and network hardware. In essence, a SIEM is a data aggregator, search, and reporting system, which stores, correlates, and applies analytics to security data to discover trends, detect threats and enable alerts. Thus, the Security Management Tool enables to carry out log data analysis, intrusions and malware detection, file integrity monitoring, configuration assessment or vulnerability detection.

Detection methodologies has been integrated to obtain the required security information and be able to send logs to the SIEM. To this end, this component includes both Host-based Intrusion Detection System (HIDS) and Network Intrusion Detection System (NIDS), which monitor network traffic for suspicious activities and possible threats, and issues alerts when such activities are discovered, generating system logs and identifying the design of usual attacks. In our use-case, the HIDS will monitor and analyze the internal aspects of the on-board device located in the drone, while the NIDS will examine the network traffic between the drone platform and the SIEM.

The detail for these modules and the whole component is divided between D5.5 and the D5.6 documents. To obtain a deeper insight of overall work, it is suggested to read both documents.

==Contribution and Improvements==
The contribution of this component focuses on the security of the drone. The inclusion of an IDS into the world of IoT devices is something that is going to be needed in the near future. With this component we have prooved that drones and IDS can coexist and work together without problems.

This component has been tuned and improved along the project, adpating to the needs of the devices is has to work with. Along the process, while some functionalities were added and configured, continous tests wer done to check the correct implementation. Not only that, the idea to add new functionalities, such as the automatic update of vulnerable components, came from a research to identify the best way to help on security on the drone area of knowledge. This implementation, even it may see complex at first wil help detecting attacks and preventing them, making the drones more secure, and in consecuence more efficient.

Component repository

2022-09-26T10:39:54Z

Ikerlan: /* Components list */

This repository aims at providing common components usable in different application domains, in particular those covered by project use-cases.

The requirements for using a components will be listed, as well as a documentation on how to use it. The component itself will be hosted by the partner who provides it.

==Components list==

{| class="wikitable"
|ID
|Contributor
|Title
|-
|[[WP3-01]]
|IKERLAN
|Safety function - Pre-Certified SOM
|-
|[[WP3-02]]
|EDI
|Modular SoC-based embedded reference architecture
|-
|[[WP3-03]]
|BUT
|Sensor information algorithms
|-
|[[WP3-04]]
|HIB
|Computer Vision Components for drones
|-
|[[WP3-10]]
|IFAT
|Component for trusted communication
|-
|[[WP3-13]]
|ENAC
|Paparazzi UAV
|-
|[[WP3-14_1]]
|ENSMA
|Collision avoidance and geo-fencing
|-
|[[WP3-14_2]]
|ENSMA
|Distributed control of multi-drone system
|-
|[[WP3-15_1]]
|ACORDE
|UWB based indoor positioning
|-
|[[WP3-15_2]]
|ACORDE
|Multi-antenna GNSS/INS based navigation
|-
|[[WP3-16]]
|SCALIAN
|EZ_Chains Fleet Architecture
|-
|[[WP3-19_1]]
|IMEC
|Hyperspectral payload
|-
|[[WP3-19_2]]
|IMEC
|Hyperspectral image processing
|-
|[[WP3-20]]
|MODIS
|Multi-sensor positioning
|-
|[[WP3-22]]
|UNIMORE
|Onboard Compute Platform Desing Methodology
|-
|[[WP3-24]]
|UNIVAQ
|Efficient digital implementation of controllers
|-
|[[WP3-26]]
|UWB
|Droneport: an autonomous drone battery management system
|-
|[[WP3-28]]
|UNISS
|Accelerator Design Methodology for OOCP
|-
|[[WP3-36_1]]
|UDANET
|Smart and predictive energy management system
|-
|[[WP3-36_2]]
|UDANET
|AI drone system modules
|-
|[[WP3-37]]
|Aitek
|Video and data analytics
|-
|[[WP4-2]]
|SCALIAN
|EZ_Land Precision landing
|-
|[[WP4-5]]
|SCALIAN
|AI detection for clearance
|-
|[[WP4-10]]
|ALM
|Cooperative Planner
|-
|[[WP4-14]]
|ALM
|Map Enhancement Service
|-
|[[WP4-15]]
|ALM
|Visual Analytics
|-
|[[WP4-16]]
|ACORDE
|Enhanced Navigation Software
|-
|[[WP4-17]]
|ACORDE
|Anchor&Tag firmware of the Indoor Positioning System
|-
|[[WP4-18_A]]
|TEKNE
|Drone-Rover Transponder
|-
|[[WP4-20]]
|ALM
|Attractor-based Navigation
|-
|[[WP4-22]]
|ALM
|Shared Reference Frame
|-
|[[WP4-32]]
|SHERPA
|Dynamic control development for navigation and precision landing
|-
|[[WP4-33]]
|UNIVAQ
|Autonomy, cooperation, and awareness
|-
|[[WP4-36]]
|IMCS
|Autonomous Decision Making in Critical Situations
|-
|[[WP4-37]]
|IMCS
|Algorithms for Runtime Safety Monitoring
|-
|[[WP4-39]]
|HIB
|Simulated data aggregator supporting intelligent decision in computer vision components
|-
|[[WP4-42]]
|SCALIAN
|AI Stabilization
|-
|[[WP5-03]]
|SCALIAN
|EZ_Com Safe fleet communication
|-
|[[WP5-09]]
|ABI
|Communication scheme for unified system management
|-
|[[WP5-05_A]]
|TEKNE
|LP-WAN for UAV identification and monitoring
|-
|[[WP5-11_ACO]]
|ACORDE
|Navigation system with anti-jamming and anti-spoofing features
|-
|[[WP5-16-AIT]]
|AIT
|Cryptographic algorithms adapted for drones
|-
|[[WP5-19_ACO]]
|ACORDE
|Robust communication for an improved Indoor Positioning System
|-
|[[WP5-02]]
|IKERLAN
|Security Management Toolchain
|-
|[[WP6-P4R]]
|CEA
|Model driven engineering
|-
|[[WP6-ESDE]]
|ACORDE
|ESL embedded SW Design Environment (ESDE)
|-
|[[WP6-IPS-MAF]]
|ACORDE
|Indoor Positioning System Modelling&Analysis Framework (IPS-MAF)
|-
|[[WP6-17]]
|UNIVAQ
|HW/SW CO-DEsign of HEterogeneous Parallel dedicated Systems (HEPSYCODE)
|-
|[[WP6-34]]
|UNIVAQ
|HEPSYCODE SystemC SIMulator Version 2.0 (HEPSIM2)
|}

WP5-XX

2022-09-26T10:38:37Z

Component repository

2022-09-26T09:26:05Z

Ikerlan:

This repository aims at providing common components usable in different application domains, in particular those covered by project use-cases.

The requirements for using a components will be listed, as well as a documentation on how to use it. The component itself will be hosted by the partner who provides it.

==Components list==

{| class="wikitable"
|ID
|Contributor
|Title
|-
|[[WP3-01]]
|IKERLAN
|Safety function - Pre-Certified SOM
|-
|[[WP3-02]]
|EDI
|Modular SoC-based embedded reference architecture
|-
|[[WP3-03]]
|BUT
|Sensor information algorithms
|-
|[[WP3-04]]
|HIB
|Computer Vision Components for drones
|-
|[[WP3-10]]
|IFAT
|Component for trusted communication
|-
|[[WP3-13]]
|ENAC
|Paparazzi UAV
|-
|[[WP3-14_1]]
|ENSMA
|Collision avoidance and geo-fencing
|-
|[[WP3-14_2]]
|ENSMA
|Distributed control of multi-drone system
|-
|[[WP3-15_1]]
|ACORDE
|UWB based indoor positioning
|-
|[[WP3-15_2]]
|ACORDE
|Multi-antenna GNSS/INS based navigation
|-
|[[WP3-16]]
|SCALIAN
|EZ_Chains Fleet Architecture
|-
|[[WP3-19_1]]
|IMEC
|Hyperspectral payload
|-
|[[WP3-19_2]]
|IMEC
|Hyperspectral image processing
|-
|[[WP3-20]]
|MODIS
|Multi-sensor positioning
|-
|[[WP3-22]]
|UNIMORE
|Onboard Compute Platform Desing Methodology
|-
|[[WP3-24]]
|UNIVAQ
|Efficient digital implementation of controllers
|-
|[[WP3-26]]
|UWB
|Droneport: an autonomous drone battery management system
|-
|[[WP3-28]]
|UNISS
|Accelerator Design Methodology for OOCP
|-
|[[WP3-36_1]]
|UDANET
|Smart and predictive energy management system
|-
|[[WP3-36_2]]
|UDANET
|AI drone system modules
|-
|[[WP3-37]]
|Aitek
|Video and data analytics
|-
|[[WP4-2]]
|SCALIAN
|EZ_Land Precision landing
|-
|[[WP4-5]]
|SCALIAN
|AI detection for clearance
|-
|[[WP4-10]]
|ALM
|Cooperative Planner
|-
|[[WP4-14]]
|ALM
|Map Enhancement Service
|-
|[[WP4-15]]
|ALM
|Visual Analytics
|-
|[[WP4-16]]
|ACORDE
|Enhanced Navigation Software
|-
|[[WP4-17]]
|ACORDE
|Anchor&Tag firmware of the Indoor Positioning System
|-
|[[WP4-18_A]]
|TEKNE
|Drone-Rover Transponder
|-
|[[WP4-20]]
|ALM
|Attractor-based Navigation
|-
|[[WP4-22]]
|ALM
|Shared Reference Frame
|-
|[[WP4-32]]
|SHERPA
|Dynamic control development for navigation and precision landing
|-
|[[WP4-33]]
|UNIVAQ
|Autonomy, cooperation, and awareness
|-
|[[WP4-36]]
|IMCS
|Autonomous Decision Making in Critical Situations
|-
|[[WP4-37]]
|IMCS
|Algorithms for Runtime Safety Monitoring
|-
|[[WP4-39]]
|HIB
|Simulated data aggregator supporting intelligent decision in computer vision components
|-
|[[WP4-42]]
|SCALIAN
|AI Stabilization
|-
|[[WP5-03]]
|SCALIAN
|EZ_Com Safe fleet communication
|-
|[[WP5-09]]
|ABI
|Communication scheme for unified system management
|-
|[[WP5-05_A]]
|TEKNE
|LP-WAN for UAV identification and monitoring
|-
|[[WP5-11_ACO]]
|ACORDE
|Navigation system with anti-jamming and anti-spoofing features
|-
|[[WP5-16-AIT]]
|AIT
|Cryptographic algorithms adapted for drones
|-
|[[WP5-19_ACO]]
|ACORDE
|Robust communication for an improved Indoor Positioning System
|-
|[[WP5-XX]]
|IKERLAN
|Title
|-
|[[WP6-P4R]]
|CEA
|Model driven engineering
|-
|[[WP6-ESDE]]
|ACORDE
|ESL embedded SW Design Environment (ESDE)
|-
|[[WP6-IPS-MAF]]
|ACORDE
|Indoor Positioning System Modelling&Analysis Framework (IPS-MAF)
|-
|[[WP6-17]]
|UNIVAQ
|HW/SW CO-DEsign of HEterogeneous Parallel dedicated Systems (HEPSYCODE)
|-
|[[WP6-34]]
|UNIVAQ
|HEPSYCODE SystemC SIMulator Version 2.0 (HEPSIM2)
|}

WP6-22

2022-09-23T07:51:01Z

Ikerlan: /* SelfTestTool */

= SelfTestTool =
{|class="wikitable"
| ID|| WP6-SelfTestTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || Self tests to check hardware failures
|-
| Input || n.a.
|-
| Output || faults report
|-
| C4D tooling || n.a.
|-
| TRL || 5
|-
| License || Proprietary
|}

== Detailed Description ==

SelfTestTool is a system start-up and runtime test tool compatible with an external monitoring tool. Looking from a Safety operation perspective, the onboard test system performs different start-up analyses and runtime tests of the correct operation, checking for the presence of random hardware failures and reporting them to the external monitorization tool. Because of the nature of the tool itself, it is strongly related to the hardware where it is executed. Anyway, the tool is implemented for performing tests on different hardware platforms.

The system is composed of two main elements. The first one consists of a self-test checking tool, boarded on the drone device. That tool performs different system checks when the main application starts and also performs runtime diagnostics during normal operation. The second element is a system monitorization element developed in WP5 and used in conjunction with the self-test checking tool. This part of the system is the responsible of reporting the faults as soon as they are detected to the final user.

==Contribution and Improvements==

SelfTestTool provides some mechanisms to detect different types of random hardware failures. The tool executes some tests at the start-up of the system, generating a .json file in order to notify and monitor externally the results.

Self-test requirements for safety systems are required by IEC 61508-7 A.3.1, A.3.2 and A.3.3), ISO 26262 (ISO 26262-5 D.2.3.1), and other regulations.
This tools helps on the compliance of those safety standards reducing the effort to certified the system.

== Interoperability with other C4D tools ==

It has interoperability with other tools such as: AsyncCommsTool and Kibana, a data visualization dashboard software.

==Current Status==

The developed solution is implemented for a specific hardware platform. In case other platforms are required, modifications should be applied.

==Design and Implementation==

The solution is developed in C language and has been implemented for UPBoard hardware platform.

WP6-23

2022-09-23T07:26:24Z

Ikerlan: /* AsyncCommsTool */

= AsyncCommsTool =
{|class="wikitable"
| ID|| WP6-AsyncCommsTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || Fault injection tests for communication validation
|-
| Input || AsyncAPI model
|-
| Output || -
|-
| C4D tooling || n.a.
|-
| TRL || 5
|-
| License || Proprietary
|}

== Detailed Description ==

AsyncCommsTool is a model-based plugin to design, develop and validate message-driven IIoT architectures efficiently. The solution is based on AsyncAPI Toolbox, which helps in designing and implementing message-driven communication APIs using a model-based approach. AsyncCommsTool plugin is implemented to include the validation phase in the AsyncAPI Toolbox. This plugin helps in the automation of the design, implementation and verification of asynchronous architectures for IoT system communication using model-based techniques.

The purpose of the AsyncCommsTool is to incorporate utilities for assisting drone systems developers in the IoT communication verification tasks. The generation of tests (fault injections) that will help in the detection of inconsistencies in the communication protocol is automated.

==Contribution and Improvements==
With the AsyncCommsTool plugin, the AsyncAPI Toolbox is extended with the capability for automatically generating the test cases that enable to verify the correctness of the generated communication API.

== Interoperability with other C4D tools ==

It has interoperability with other tools such as: SelfTestTool and Kibana, a data visualization dashboard software.

==Current Status==

The toolchain provides automatic documentation and code generation. AsyncCommsTool provides a plugin that generates automatically test cases to detect communication inconsistencies and may help in the certification of the system. But currently, some bugs need to be solved in order to be a useful plugin.

==Design and Implementation==

The solution is developed in Java language.

WP6-23

2022-09-23T07:11:00Z

Ikerlan: /* AsyncCommsTool */

= AsyncCommsTool =
{|class="wikitable"
| ID|| WP6-AsyncCommsTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || Fault injection tests for communication
|-
| Input || AsyncAPI model
|-
| Output || -
|-
| C4D tooling || n.a.
|-
| TRL || 5
|-
| License || Proprietary
|}

== Detailed Description ==

AsyncCommsTool is a model-based plugin to design, develop and validate message-driven IIoT architectures efficiently. The solution is based on AsyncAPI Toolbox, which helps in designing and implementing message-driven communication APIs using a model-based approach. AsyncCommsTool plugin is implemented to include the validation phase in the AsyncAPI Toolbox. This plugin helps in the automation of the design, implementation and verification of asynchronous architectures for IoT system communication using model-based techniques.

The purpose of the AsyncCommsTool is to incorporate utilities for assisting drone systems developers in the IoT communication verification tasks. The generation of tests (fault injections) that will help in the detection of inconsistencies in the communication protocol is automated.

==Contribution and Improvements==
With the AsyncCommsTool plugin, the AsyncAPI Toolbox is extended with the capability for automatically generating the test cases that enable to verify the correctness of the generated communication API.

== Interoperability with other C4D tools ==

It has interoperability with other tools such as: SelfTestTool and Kibana, a data visualization dashboard software.

==Current Status==

The toolchain provides automatic documentation and code generation. AsyncCommsTool provides a plugin that generates automatically test cases to detect communication inconsistencies and may help in the certification of the system. But currently, some bugs need to be solved in order to be a useful plugin.

==Design and Implementation==

The solution is developed in Java language.

WP6-22

2022-09-23T07:10:28Z

Ikerlan: /* SelfTestTool */

= SelfTestTool =
{|class="wikitable"
| ID|| WP6-SelfTestTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || Self tests
|-
| Input || n.a.
|-
| Output || faults report
|-
| C4D tooling || n.a.
|-
| TRL || 5
|-
| License || Proprietary
|}

== Detailed Description ==

SelfTestTool is a system start-up and runtime test tool compatible with an external monitoring tool. Looking from a Safety operation perspective, the onboard test system performs different start-up analyses and runtime tests of the correct operation, checking for the presence of random hardware failures and reporting them to the external monitorization tool. Because of the nature of the tool itself, it is strongly related to the hardware where it is executed. Anyway, the tool is implemented for performing tests on different hardware platforms.

The system is composed of two main elements. The first one consists of a self-test checking tool, boarded on the drone device. That tool performs different system checks when the main application starts and also performs runtime diagnostics during normal operation. The second element is a system monitorization element developed in WP5 and used in conjunction with the self-test checking tool. This part of the system is the responsible of reporting the faults as soon as they are detected to the final user.

==Contribution and Improvements==

SelfTestTool provides some mechanisms to detect different types of random hardware failures. The tool executes some tests at the start-up of the system, generating a .json file in order to notify and monitor externally the results.

Self-test requirements for safety systems are required by IEC 61508-7 A.3.1, A.3.2 and A.3.3), ISO 26262 (ISO 26262-5 D.2.3.1), and other regulations.
This tools helps on the compliance of those safety standards reducing the effort to certified the system.

== Interoperability with other C4D tools ==

It has interoperability with other tools such as: AsyncCommsTool and Kibana, a data visualization dashboard software.

==Current Status==

The developed solution is implemented for a specific hardware platform. In case other platforms are required, modifications should be applied.

==Design and Implementation==

The solution is developed in C language and has been implemented for UPBoard hardware platform.

WP6-23

2022-09-23T07:09:08Z

Ikerlan: /* AsyncCommsTool */

= AsyncCommsTool =
{|class="wikitable"
| ID|| WP6-AsyncCommsTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || -
|-
| Input || AsyncAPI model
|-
| Output || -
|-
| C4D tooling || n.a.
|-
| TRL || 5
|-
| License || Proprietary
|}

== Detailed Description ==

AsyncCommsTool is a model-based plugin to design, develop and validate message-driven IIoT architectures efficiently. The solution is based on AsyncAPI Toolbox, which helps in designing and implementing message-driven communication APIs using a model-based approach. AsyncCommsTool plugin is implemented to include the validation phase in the AsyncAPI Toolbox. This plugin helps in the automation of the design, implementation and verification of asynchronous architectures for IoT system communication using model-based techniques.

The purpose of the AsyncCommsTool is to incorporate utilities for assisting drone systems developers in the IoT communication verification tasks. The generation of tests (fault injections) that will help in the detection of inconsistencies in the communication protocol is automated.

==Contribution and Improvements==
With the AsyncCommsTool plugin, the AsyncAPI Toolbox is extended with the capability for automatically generating the test cases that enable to verify the correctness of the generated communication API.

== Interoperability with other C4D tools ==

It has interoperability with other tools such as: SelfTestTool and Kibana, a data visualization dashboard software.

==Current Status==

The toolchain provides automatic documentation and code generation. AsyncCommsTool provides a plugin that generates automatically test cases to detect communication inconsistencies and may help in the certification of the system. But currently, some bugs need to be solved in order to be a useful plugin.

==Design and Implementation==

The solution is developed in Java language.

WP6-22

2022-09-23T07:08:14Z

Ikerlan: /* SelfTestTool */

= SelfTestTool =
{|class="wikitable"
| ID|| WP6-SelfTestTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || -
|-
| Input || n.a.
|-
| Output || faults report
|-
| C4D tooling || n.a.
|-
| TRL || 5
|-
| License || Proprietary
|}

== Detailed Description ==

SelfTestTool is a system start-up and runtime test tool compatible with an external monitoring tool. Looking from a Safety operation perspective, the onboard test system performs different start-up analyses and runtime tests of the correct operation, checking for the presence of random hardware failures and reporting them to the external monitorization tool. Because of the nature of the tool itself, it is strongly related to the hardware where it is executed. Anyway, the tool is implemented for performing tests on different hardware platforms.

The system is composed of two main elements. The first one consists of a self-test checking tool, boarded on the drone device. That tool performs different system checks when the main application starts and also performs runtime diagnostics during normal operation. The second element is a system monitorization element developed in WP5 and used in conjunction with the self-test checking tool. This part of the system is the responsible of reporting the faults as soon as they are detected to the final user.

==Contribution and Improvements==

SelfTestTool provides some mechanisms to detect different types of random hardware failures. The tool executes some tests at the start-up of the system, generating a .json file in order to notify and monitor externally the results.

Self-test requirements for safety systems are required by IEC 61508-7 A.3.1, A.3.2 and A.3.3), ISO 26262 (ISO 26262-5 D.2.3.1), and other regulations.
This tools helps on the compliance of those safety standards reducing the effort to certified the system.

== Interoperability with other C4D tools ==

It has interoperability with other tools such as: AsyncCommsTool and Kibana, a data visualization dashboard software.

==Current Status==

The developed solution is implemented for a specific hardware platform. In case other platforms are required, modifications should be applied.

==Design and Implementation==

The solution is developed in C language and has been implemented for UPBoard hardware platform.

WP6-23

2022-07-12T12:02:50Z

Ikerlan: /* Design and Implementation */

= AsyncCommsTool =
{|class="wikitable"
| ID|| WP6-AsyncCommsTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || TODO
|-
| Input || TODO
|-
| Output || TODO.
|-
| C4D tooling || n.a.
|-
| TRL || 5
|-
| License || Proprietary
|}

== Detailed Description ==

AsyncCommsTool is a model-based plugin to design, develop and validate message-driven IIoT architectures efficiently. The solution is based on AsyncAPI Toolbox, which helps in designing and implementing message-driven communication APIs using a model-based approach. AsyncCommsTool plugin is implemented to include the validation phase in the AsyncAPI Toolbox. This plugin helps in the automation of the design, implementation and verification of asynchronous architectures for IoT system communication using model-based techniques.

The purpose of the AsyncCommsTool is to incorporate utilities for assisting drone systems developers in the IoT communication verification tasks. The generation of tests (fault injections) that will help in the detection of inconsistencies in the communication protocol is automated.

==Contribution and Improvements==
With the AsyncCommsTool plugin, the AsyncAPI Toolbox is extended with the capability for automatically generating the test cases that enable to verify the correctness of the generated communication API.

== Interoperability with other C4D tools ==

It has interoperability with other tools such as: SelfTestTool and Kibana, a data visualization dashboard software.

==Current Status==

The toolchain provides automatic documentation and code generation. AsyncCommsTool provides a plugin that generates automatically test cases to detect communication inconsistencies and may help in the certification of the system. But currently, some bugs need to be solved in order to be a useful plugin.

==Design and Implementation==

The solution is developed in Java language.

WP6-23

2022-07-12T12:01:09Z

Ikerlan: /* Current Status */

WP6-23

2022-07-12T11:55:01Z

Ikerlan: /* Interoperability with other C4D tools */

WP6-23

2022-07-12T11:54:02Z

Ikerlan: /* Contribution and Improvements */

= AsyncCommsTool =
{|class="wikitable"
| ID|| WP6-AsyncCommsTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || TODO
|-
| Input || TODO
|-
| Output || TODO.
|-
| C4D tooling || n.a.
|-
| TRL || 5
|-
| License || Proprietary
|}

== Detailed Description ==

AsyncCommsTool is a model-based plugin to design, develop and validate message-driven IIoT architectures efficiently. The solution is based on AsyncAPI Toolbox, which helps in designing and implementing message-driven communication APIs using a model-based approach. AsyncCommsTool plugin is implemented to include the validation phase in the AsyncAPI Toolbox. This plugin helps in the automation of the design, implementation and verification of asynchronous architectures for IoT system communication using model-based techniques.

The purpose of the AsyncCommsTool is to incorporate utilities for assisting drone systems developers in the IoT communication verification tasks. The generation of tests (fault injections) that will help in the detection of inconsistencies in the communication protocol is automated.

==Contribution and Improvements==
With the AsyncCommsTool plugin, the AsyncAPI Toolbox is extended with the capability for automatically generating the test cases that enable to verify the correctness of the generated communication API.

== Interoperability with other C4D tools ==

TODO

==Current Status==

TODO

==Design and Implementation==

TODO

WP6-23

2022-07-12T10:40:20Z

Ikerlan: /* Detailed Description */

WP6-23

2022-07-12T10:20:05Z

Ikerlan: /* AsyncCommsTool */

WP6-22

2022-07-12T10:06:44Z

Ikerlan: /* Contribution and Improvements */

= SelfTestTool =
{|class="wikitable"
| ID|| WP6-SelfTestTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || TODO
|-
| Input || n.a.
|-
| Output || faults report
|-
| C4D tooling || n.a.
|-
| TRL || 5
|-
| License || Proprietary
|}

== Detailed Description ==

SelfTestTool is a system start-up and runtime test tool compatible with an external monitoring tool. Looking from a Safety operation perspective, the onboard test system performs different start-up analyses and runtime tests of the correct operation, checking for the presence of random hardware failures and reporting them to the external monitorization tool. Because of the nature of the tool itself, it is strongly related to the hardware where it is executed. Anyway, the tool is implemented for performing tests on different hardware platforms.

The system is composed of two main elements. The first one consists of a self-test checking tool, boarded on the drone device. That tool performs different system checks when the main application starts and also performs runtime diagnostics during normal operation. The second element is a system monitorization element developed in WP5 and used in conjunction with the self-test checking tool. This part of the system is the responsible of reporting the faults as soon as they are detected to the final user.

==Contribution and Improvements==

SelfTestTool provides some mechanisms to detect different types of random hardware failures. The tool executes some tests at the start-up of the system, generating a .json file in order to notify and monitor externally the results.

Self-test requirements for safety systems are required by IEC 61508-7 A.3.1, A.3.2 and A.3.3), ISO 26262 (ISO 26262-5 D.2.3.1), and other regulations.
This tools helps on the compliance of those safety standards reducing the effort to certified the system.

== Interoperability with other C4D tools ==

It has interoperability with other tools such as: AsyncCommsTool and Kibana, a data visualization dashboard software.

==Current Status==

The developed solution is implemented for a specific hardware platform. In case other platforms are required, modifications should be applied.

==Design and Implementation==

The solution is developed in C language and has been implemented for UPBoard hardware platform.

WP6-22

2022-07-12T10:05:50Z

Ikerlan: /* Detailed Description */

= SelfTestTool =
{|class="wikitable"
| ID|| WP6-SelfTestTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || TODO
|-
| Input || n.a.
|-
| Output || faults report
|-
| C4D tooling || n.a.
|-
| TRL || 5
|-
| License || Proprietary
|}

== Detailed Description ==

SelfTestTool is a system start-up and runtime test tool compatible with an external monitoring tool. Looking from a Safety operation perspective, the onboard test system performs different start-up analyses and runtime tests of the correct operation, checking for the presence of random hardware failures and reporting them to the external monitorization tool. Because of the nature of the tool itself, it is strongly related to the hardware where it is executed. Anyway, the tool is implemented for performing tests on different hardware platforms.

The system is composed of two main elements. The first one consists of a self-test checking tool, boarded on the drone device. That tool performs different system checks when the main application starts and also performs runtime diagnostics during normal operation. The second element is a system monitorization element developed in WP5 and used in conjunction with the self-test checking tool. This part of the system is the responsible of reporting the faults as soon as they are detected to the final user.

==Contribution and Improvements==

SelfTestTool provides some mechanisms to detect different types of random hardware failures. The tool executes some tests at the start-up of the system, generating a .json file in order to notify and monitor externally the results.

Self-test requirements for safety systems are required by IEC 61508-7 A.3.1, A.3.2 and A.3.3), ISO 26262 (ISO 26262-5 D.2.3.1), and other regulations.
This tools helps on the compliance of those safety standards. It is considered that an effort reduction for the certification has been done.

== Interoperability with other C4D tools ==

It has interoperability with other tools such as: AsyncCommsTool and Kibana, a data visualization dashboard software.

==Current Status==

The developed solution is implemented for a specific hardware platform. In case other platforms are required, modifications should be applied.

==Design and Implementation==

The solution is developed in C language and has been implemented for UPBoard hardware platform.

WP6-23

2022-07-12T09:23:05Z

Ikerlan: /* AsyncCommsTool */

WP6-22

2022-07-12T09:04:17Z

Ikerlan: /* Design and Implementation */

= SelfTestTool =
{|class="wikitable"
| ID|| WP6-SelfTestTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || TODO
|-
| Input || n.a.
|-
| Output || faults report
|-
| C4D tooling || n.a.
|-
| TRL || 5
|-
| License || Proprietary
|}

== Detailed Description ==

SelfTestTool is a system start-up and runtime test tool compatible with an external monitoring tool. Looking from a Safety operation perspective, the onboard test system performs different start-up analyses and runtime tests of the correct operation, checking for the presence of random hardware failures and reporting them to the external monitorization tool. Because of the nature of the tool itself, it is strongly related to the hardware where it is executed. Anyway, the tool is implemented for performing tests on different hardware platforms.

The system will be composed of two main elements. The first one will consist of a self-test checking tool, boarded on the drone device. That tool will perform different system checks when the main application starts and will also perform runtime diagnostics during normal operation. The second element will be a system monitorization element developed in WP and used in conjunction with the self-test checking tool. This part of the system will be the responsible of reporting the faults as soon as they are detected to the final user.

==Contribution and Improvements==

SelfTestTool provides some mechanisms to detect different types of random hardware failures. The tool executes some tests at the start-up of the system, generating a .json file in order to notify and monitor externally the results.

Self-test requirements for safety systems are required by IEC 61508-7 A.3.1, A.3.2 and A.3.3), ISO 26262 (ISO 26262-5 D.2.3.1), and other regulations.
This tools helps on the compliance of those safety standards. It is considered that an effort reduction for the certification has been done.

== Interoperability with other C4D tools ==

It has interoperability with other tools such as: AsyncCommsTool and Kibana, a data visualization dashboard software.

==Current Status==

The developed solution is implemented for a specific hardware platform. In case other platforms are required, modifications should be applied.

==Design and Implementation==

The solution is developed in C language and has been implemented for UPBoard hardware platform.

WP6-22

2022-07-12T09:03:29Z

Ikerlan: /* Current Status */

= SelfTestTool =
{|class="wikitable"
| ID|| WP6-SelfTestTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || TODO
|-
| Input || n.a.
|-
| Output || faults report
|-
| C4D tooling || n.a.
|-
| TRL || 5
|-
| License || Proprietary
|}

== Detailed Description ==

SelfTestTool is a system start-up and runtime test tool compatible with an external monitoring tool. Looking from a Safety operation perspective, the onboard test system performs different start-up analyses and runtime tests of the correct operation, checking for the presence of random hardware failures and reporting them to the external monitorization tool. Because of the nature of the tool itself, it is strongly related to the hardware where it is executed. Anyway, the tool is implemented for performing tests on different hardware platforms.

The system will be composed of two main elements. The first one will consist of a self-test checking tool, boarded on the drone device. That tool will perform different system checks when the main application starts and will also perform runtime diagnostics during normal operation. The second element will be a system monitorization element developed in WP and used in conjunction with the self-test checking tool. This part of the system will be the responsible of reporting the faults as soon as they are detected to the final user.

==Contribution and Improvements==

SelfTestTool provides some mechanisms to detect different types of random hardware failures. The tool executes some tests at the start-up of the system, generating a .json file in order to notify and monitor externally the results.

Self-test requirements for safety systems are required by IEC 61508-7 A.3.1, A.3.2 and A.3.3), ISO 26262 (ISO 26262-5 D.2.3.1), and other regulations.
This tools helps on the compliance of those safety standards. It is considered that an effort reduction for the certification has been done.

== Interoperability with other C4D tools ==

It has interoperability with other tools such as: AsyncCommsTool and Kibana, a data visualization dashboard software.

==Current Status==

The developed solution is implemented for a specific hardware platform. In case other platforms are required, modifications should be applied.

==Design and Implementation==

TODO

WP6-22

2022-07-12T09:02:18Z

Ikerlan: /* Contribution and Improvements */

= SelfTestTool =
{|class="wikitable"
| ID|| WP6-SelfTestTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || TODO
|-
| Input || n.a.
|-
| Output || faults report
|-
| C4D tooling || n.a.
|-
| TRL || 5
|-
| License || Proprietary
|}

== Detailed Description ==

SelfTestTool is a system start-up and runtime test tool compatible with an external monitoring tool. Looking from a Safety operation perspective, the onboard test system performs different start-up analyses and runtime tests of the correct operation, checking for the presence of random hardware failures and reporting them to the external monitorization tool. Because of the nature of the tool itself, it is strongly related to the hardware where it is executed. Anyway, the tool is implemented for performing tests on different hardware platforms.

The system will be composed of two main elements. The first one will consist of a self-test checking tool, boarded on the drone device. That tool will perform different system checks when the main application starts and will also perform runtime diagnostics during normal operation. The second element will be a system monitorization element developed in WP and used in conjunction with the self-test checking tool. This part of the system will be the responsible of reporting the faults as soon as they are detected to the final user.

==Contribution and Improvements==

SelfTestTool provides some mechanisms to detect different types of random hardware failures. The tool executes some tests at the start-up of the system, generating a .json file in order to notify and monitor externally the results.

Self-test requirements for safety systems are required by IEC 61508-7 A.3.1, A.3.2 and A.3.3), ISO 26262 (ISO 26262-5 D.2.3.1), and other regulations.
This tools helps on the compliance of those safety standards. It is considered that an effort reduction for the certification has been done.

== Interoperability with other C4D tools ==

It has interoperability with other tools such as: AsyncCommsTool and Kibana, a data visualization dashboard software.

==Current Status==

TODO

==Design and Implementation==

TODO

WP6-22

2022-07-12T09:00:51Z

Ikerlan: /* Contribution and Improvements */

= SelfTestTool =
{|class="wikitable"
| ID|| WP6-SelfTestTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || TODO
|-
| Input || n.a.
|-
| Output || faults report
|-
| C4D tooling || n.a.
|-
| TRL || 5
|-
| License || Proprietary
|}

== Detailed Description ==

SelfTestTool is a system start-up and runtime test tool compatible with an external monitoring tool. Looking from a Safety operation perspective, the onboard test system performs different start-up analyses and runtime tests of the correct operation, checking for the presence of random hardware failures and reporting them to the external monitorization tool. Because of the nature of the tool itself, it is strongly related to the hardware where it is executed. Anyway, the tool is implemented for performing tests on different hardware platforms.

The system will be composed of two main elements. The first one will consist of a self-test checking tool, boarded on the drone device. That tool will perform different system checks when the main application starts and will also perform runtime diagnostics during normal operation. The second element will be a system monitorization element developed in WP and used in conjunction with the self-test checking tool. This part of the system will be the responsible of reporting the faults as soon as they are detected to the final user.

==Contribution and Improvements==

SelfTestTool provides some mechanisms to detect different types of random hardware failures. The tool executes some tests at the start-up of the system, generating a .json file in order to notify and monitor externally the results.

Self-test requirements for safety systems are required by IEC 61508-7 A.3.1, A.3.2 and A.3.3), ISO 26262 (ISO 26262-5 D.2.3.1), and other regulations.
This tools helps on the compliance of those safety standards.

== Interoperability with other C4D tools ==

It has interoperability with other tools such as: AsyncCommsTool and Kibana, a data visualization dashboard software.

==Current Status==

TODO

==Design and Implementation==

TODO

WP6-22

2022-07-12T08:55:42Z

Ikerlan: /* Interoperability with other C4D tools */

WP6-22

2022-07-12T08:32:16Z

Ikerlan: /* SelfTestTool */

WP6-22

2022-07-12T08:28:27Z

Ikerlan: /* SelfTestTool */

WP6-22

2022-07-06T14:50:03Z

Ikerlan: Created page with "= SelfTestTool = {|class="wikitable" | ID|| WP6-SelfTestTool |- | Contributor || IKERLAN |- | Levels || Tool |- | Require || - |- | Provide || TODO |- | Input || TODO |- | Output || TODO. |- | C4D tooling || n.a. |- | TRL || - |} == Detailed Description == TODO ==Contribution and Improvements== TODO == Interoperability with other C4D tools == TODO ==Current Status== TODO ==Design and Implementation== TODO"

= SelfTestTool =
{|class="wikitable"
| ID|| WP6-SelfTestTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || TODO
|-
| Input || TODO
|-
| Output || TODO.
|-
| C4D tooling || n.a.
|-
| TRL || -
|}

== Detailed Description ==

TODO

==Contribution and Improvements==

TODO

== Interoperability with other C4D tools ==

TODO

==Current Status==

TODO

==Design and Implementation==

TODO

WP6-23

2022-07-06T14:48:46Z

Ikerlan: Created page with "= AsyncCommsTool = {|class="wikitable" | ID|| WP6-AsyncCommsTool |- | Contributor || IKERLAN |- | Levels || Tool |- | Require || - |- | Provide || TODO |- | Input || TODO |- | Output || TODO. |- | C4D tooling || n.a. |- | TRL || - |} == Detailed Description == TODO ==Contribution and Improvements== TODO == Interoperability with other C4D tools == TODO ==Current Status== TODO ==Design and Implementation== TODO"

= AsyncCommsTool =
{|class="wikitable"
| ID|| WP6-AsyncCommsTool
|-
| Contributor || IKERLAN
|-
| Levels || Tool
|-
| Require || -
|-
| Provide || TODO
|-
| Input || TODO
|-
| Output || TODO.
|-
| C4D tooling || n.a.
|-
| TRL || -
|}

== Detailed Description ==

TODO

==Contribution and Improvements==

TODO

== Interoperability with other C4D tools ==

TODO

==Current Status==

TODO

==Design and Implementation==

TODO