| 1. |
- Aidemark, Joakim, 1965, et al.
(författare)
-
Experimental evaluation of time-redundant execution for a brake-by-wire application
- 2002
-
Ingår i: International Conference on Dependable Systems and Networks, 2002. DSN 2002. Proceedings. - 0769511015 ; , s. 210-215
-
Konferensbidrag (refereegranskat)abstract
- This paper presents an experimental evaluation of a brake-by-wire application that tolerates transient faults by temporal error masking. A specially designed real-time kernel that masks errors by triple time-redundant execution and voting executes the application on a fail-stop computer node. The objective is to reduce the number of node failures by masking errors at the computer node level. The real-time kernel always executes the application twice to detect errors, and ensures that a fail-stop failure occurs if there is not enough CPU-time available for a third execution and voting. Fault injection experiments show that temporal error masking reduced the number of fail-stop failures by 42% compared to executing the brake-by-wire task without time redundancy.
|
|
| 2. |
|
|
| 3. |
|
|
| 4. |
|
|
| 5. |
|
|
| 6. |
- Damschen, Marvin, et al.
(författare)
-
Business Model
- 2021
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- The objective of X2Rail-3 (Grant Agreement No. 826141) Task 7.5 is an analysis of the businessmodel for the Virtually Coupled Train Sets (VCTS) concept. The VCTS concept was developed inX2Rail-3 Work Packages 6 and 7. The MOVINGRAIL project, which was the only project fundedunder the IP2 open call S2R-OC-IP2-01-2018, provided inputs concerning the cost effectiveness,application roadmap as well as business risks and overall market potential of VCTS. Thisdeliverable (D7.5) is the outcome of Task 7.5. First, it provides an analysis of the inputs providedby MOVINGRAIL, putting them in context with previous X2Rail-3 work. Then, taking theconclusions of the analysis into account, two different application cases for VCTS are presented.Strategies to implement the application cases are detailed, including a vision for implementingVCTS within the RCA and OCORA reference architectures. Finally, the business case of VCTS iscompared against business objectives identified within the LinX4Rail project.The application cases for VCTS presented in this deliverable are standalone VCTS and ETCS-based VCTS. Standalone VCTS is an application of VCTS that focuses on low-traffic lines thatare today using Class B signalling systems that cannot be upgraded to ETCS in a cost-effectiveway. In summary, it is a low-cost onboard train protection system which has the objectives ofproviding an economically interesting upgrade path for Class B systems and raising the maturityof the underlying technology required for VCTS, thus, fostering the wide-scale introduction. ETCS-based VCTS is an application of VCTS that focuses on high-traffic lines and bases on ETCS Level2 or Level 3. ETCS-based VCTS is the actual goal of the VCTS concept and has the mainobjectives of reducing headway and improving flexibility of operation in order to increase linecapacity and provide the technical basis for innovative business models.For each application case, a migration strategy is presented, detailing the non-technical andtechnical steps required for implementing and on-site testing a first complete demonstrator withina period of three to five years. The migration strategies provide details for train protection, trafficmanagement, automatic train operation, on-board train integrity, communication and VCTS (on-board and trackside, if applicable) sub-systems. As detailed in Deliverable 7.4 “Impact Analysis”which was prepared in parallel to this deliverable, the introduction of VCTS does not change thefundamental principles of any of the existing sub-systems, i.e., a full rework is not required.Beyond the migration strategies, the vision of implementing ETCS-based VCTS within the RCAand OCORA reference architectures is presented, which would imply software changes only and,thus, simplify the migration considerably. Finally, the impact of VCTS is compared against thebusiness objectives identified in the LinX4Rail project. Taking the presented migration strategiesand MOVINGRAIL input into account, it is shown that VCTS is in line with the RUs’, IMs’ andsuppliers’ business objectives.Ultimately, VCTS is an innovative concept that can raise scepticism by operators and the generalpublic. Its safety can be achieved within the near future, but this needs to be communicated clearlyto foster the acceptance of VCTS. Only then, VCTS cannot only improve current railway operationwith increased capacity, reliability and lower operational costs, but even provide the basis for novelbusiness models that benefit from the increased flexibility.
|
|
| 7. |
|
|
| 8. |
|
|
| 9. |
|
|
| 10. |
- Folkesson, Peter, 1968, et al.
(författare)
-
Back-to-Back Fault Injection Testing in Model-Based Development
- 2015
-
Ingår i: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics). - Cham : Springer International Publishing. - 1611-3349 .- 0302-9743. - 9783319242545 - 9783319242552 ; 9337, s. 135-148
-
Konferensbidrag (refereegranskat)abstract
- Today, embedded systems across industrial domains (e.g., avionics, automotive) are representatives of software-intensive systems with increasing reliance on software and growing complexity. It has become critically important to verify software in a time, resource and cost effective manner. Furthermore, industrial domains are striving to comply with the requirements of relevant safety standards. This paper proposes a novel workflow along with tool support to evaluate robustness of software in model-based development environment, assuming different abstraction levels of representing software. We then show the effectiveness of our technique, on a brake-by-wire application, by performing back-to-back fault injection testing between two different abstraction levels using MODIFI for the Simulink model and GOOFI-2 for the generated code running on the target microcontroller. Our proposed method and tool support facilitates not only verifying software during early phases of the development lifecycle but also fulfilling back-to-back testing requirements of ISO 26262 when using model-based development.
|
|
