WP6-22: Difference between revisions
(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") |
|||
| (11 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
| Require || - | | Require || - | ||
|- | |- | ||
| Provide || | | Provide || Self tests to check hardware failures | ||
|- | |- | ||
| Input || | | Input || n.a. | ||
|- | |- | ||
| Output || | | Output || faults report | ||
|- | |- | ||
| C4D tooling || n.a. | | C4D tooling || n.a. | ||
|- | |- | ||
| TRL || - | | TRL || 5 | ||
|- | |||
| License || Proprietary | |||
|} | |} | ||
== Detailed Description == | == 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== | ==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 == | == Interoperability with other C4D tools == | ||
It has interoperability with other tools such as: AsyncCommsTool and Kibana, a data visualization dashboard software. | |||
==Current Status== | ==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== | ==Design and Implementation== | ||
The solution is developed in C language and has been implemented for UPBoard hardware platform. | |||
Latest revision as of 07:51, 23 September 2022
SelfTestTool
| 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.