Abstract: Methods and systems are provided for driveline control and diagnostics. In one example, a vehicle system may include a controller with instructions stored in a first memory unit and when executed by a first processing unit cause the controller to write mechanical vehicle component operating data to a shared memory unit. The controller further includes instructions stored in a second memory unit that when executed by a second processing unit cause the controller to read the mechanical vehicle component operating data to determine data validity.

Abstract: Methods and systems are provided for controlling and diagnosing a mechanical vehicle component. In one example, a method may include determining a vehicle speed and a plurality of clutch position settings at a diagnostic controller, and identifying unauthorized conditions based on these determinations. Further, the diagnostic controller may trigger an active fault state of the mechanical vehicle component in order to avoid unauthorized conditions that may lead to unwanted or unanticipated changes in vehicle motion.

Abstract: Methods and systems are provided for controlling and diagnosing a mechanical vehicle component. In one example, a method may include determining an input device state and an electric machine torque at a diagnostic controller, and identifying a fault condition based on these determinations. Further, the diagnostic controller may trigger an active fault state of the mechanical vehicle component to avoid unintended vehicle acceleration, particularly at low speeds.

Abstract: Methods and systems are provided for controlling and diagnosing a mechanical vehicle component. In one example, a method may include determining an input device state and an electric machine torque at a diagnostic controller, and identifying a fault condition based on these determinations. Further, the diagnostic controller may trigger an active fault state of the mechanical vehicle component to avoid unintended vehicle acceleration, particularly at low speeds.

Abstract: Methods and systems are provided for controlling and diagnosing a mechanical vehicle component. In one example, a method may include determining a vehicle speed and a plurality of clutch position settings at a diagnostic controller, and identifying unauthorized conditions based on these determinations. Further, the diagnostic controller may trigger an active fault state of the mechanical vehicle component in order to avoid unauthorized conditions that may lead to unwanted or unanticipated changes in vehicle motion.

Abstract: Methods and systems are provided for controlling and diagnosing a mechanical vehicle component. In one example, a method may include determining a vehicle speed and a plurality of clutch position settings at a diagnostic controller, and identifying unauthorized conditions based on these determinations. Further, the diagnostic controller may trigger an active fault state of the mechanical vehicle component in order to avoid unauthorized conditions that may lead to unwanted or unanticipated changes in vehicle motion.

Abstract: Methods and systems are provided for controlling and diagnosing a mechanical vehicle component. In one example, a method may include determining an input device state and an electric machine torque at a diagnostic controller, and identifying a fault condition based on these determinations. Further, the diagnostic controller may trigger an active fault state of the mechanical vehicle component to avoid unintended vehicle acceleration, particularly at low speeds.

Abstract: Methods and systems are provided for controlling and diagnosing a mechanical vehicle component. In one example, a method may include determining a vehicle speed and a plurality of clutch position settings at a diagnostic controller, and identifying unauthorized conditions based on these determinations. Further, the diagnostic controller may trigger an active fault state of the mechanical vehicle component in order to avoid unauthorized conditions that may lead to unwanted or unanticipated changes in vehicle motion.

Abstract: Methods and systems are provided for driveline control and diagnostics. In one example, a vehicle system may include a controller with instructions stored in a first memory unit and when executed by a first processing unit cause the controller to write mechanical vehicle component operating data to a shared memory unit. The controller further includes instructions stored in a second memory unit that when executed by a second processing unit cause the controller to read the mechanical vehicle component operating data to determine data validity.

Abstract: A functional architecture pattern has a first software module, an operating system module, a first board support package, and a first microcomputer. The functional architecture pattern further has a second software module, a second board support package, and a second microcomputer that are logically separated from the first software module, the operating system module, the first board support package, and the first microcomputer. The first software module is developed according to quality management standards, while the operating system module, both first and second board support packages, and the third software module are developed according to safety integrity levels standards so as to make a logical split-off on three levels between the first software module software and the second software module.

Abstract: A functional architecture pattern has a first software module, an operating system module, a first board support package, and a first microcomputer. The functional architecture pattern further has a second software module, a second board support package, and a second microcomputer that are logically separated from the first software module, the operating system module, the first board support package, and the first microcomputer. The first software module is developed according to quality management standards, while the operating system module, both first and second board support packages, and the third software module are developed according to safety integrity levels standards so as to make a logical split-off on three levels between the first software module software and the second software module.

Abstract: A process for decomposing safety software involves the steps of providing a first software module associated with a first logical unit, providing a second software module associated with a second logical unit, instructing the first software module to implement a first safety goal based on a quality management level, and instructing the second software module to implement a second safety goal based on a safety integrity level, where the second software module uses at least one input and at least one output of the second logical unit to determine if the second safety goal is satisfied. Consequently, the second software module uses a result of the first software module to determine if the first safety goal has been completed, and the second software module uses at least one algorithm to verify an operational status of the first logical unit.

Abstract: A process for decomposing safety software involves the steps of providing a first software module associated with a first logical unit, providing a second software module associated with a second logical unit, instructing the first software module to implement a first safety goal based on a quality management level, and instructing the second software module to implement a second safety goal based on a safety integrity level, where the second software module uses at least one input and at least one output of the second logical unit to determine if the second safety goal is satisfied. Consequently, the second software module uses a result of the first software module to determine if the first safety goal has been completed, and the second software module uses at least one algorithm to verify an operational status of the first logical unit.