3.2.3.3: Process Data for Vehicle Actuators
This process shall be responsible for providing the interface between other automatic vehicle control process and the actuators which actually change the vehicle's controls. The process shall both implement commands and monitor the operation of the actuators to check that they only move when requested. If they move for any other reason, e.g. the driver has touched the vehicle controls, the process shall disable automatic operation. When receiving vehicle action requests due to a collision or position warning from the Monitor Vehicle Status process, this process shall provide the steering and or braking commands to the Basic Vehicle's actuators. The process shall perform its own built-in self test (BIST) analysis. It shall report any errors that this shows to another process in the vehicle and shall cease to accept further requests to change the vehicle's actuators.
This process is associated with the Vehicle physical object.
This process is associated with the following functional objects:
- Vehicle Basic Safety Communication
- Vehicle Control Automation
- Vehicle Control Warning
- Vehicle Cooperative Cruise Control
- Vehicle Environmental Monitoring
- Vehicle Intersection Warning
- Vehicle Platoon Operations
- Vehicle Queue Warning
- Vehicle Traveler Information Reception
This process is associated with the following data flows:
- actuator_commands
- driver_manual_input
- fbv-brake_servo_response
- fbv-steering_servo_response
- fbv-throttle_servo_response
- feedback_actuator_response
- feedback_actuator_status
- fov-vehicle_profile_information
- manual_input_received
- platooning_selected
- tbv-change_brake_setting
- tbv-change_direction
- tbv-change_throttle_setting
- vehicle_action_requests
- vehicle_actuator_feedback_for_crash_avoidance
- vehicle_actuator_feedback_for_safety
- vehicle_safety_action_requests