WP6-22: Difference between revisions
Jump to navigation
Jump to search
(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") |
|||
Line 11: | Line 11: | ||
| Provide || TODO | | Provide || TODO | ||
|- | |- | ||
| 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. | |||
==Contribution and Improvements== | ==Contribution and Improvements== |
Revision as of 08:28, 12 July 2022
SelfTestTool
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.
Contribution and Improvements
TODO
Interoperability with other C4D tools
TODO
Current Status
TODO
Design and Implementation
TODO