Profiles¶
A profile declares the command interface, limits, sequence policy, fault corpus, and applicable references for one evaluation. It is an evaluation input, not a system certification or a reusable production safety case.
Packaged reference profiles¶
| Profile | Interface model | Applicable references |
|---|---|---|
robot_diff_drive_ros2_v0 |
ROS 2 differential drive | ISO 3691-4:2023, IEC 61508:2010 |
automotive_ecu_can_v0 |
CAN torque command | ISO 26262:2018, IEC 61508:2010 |
industrial_cobot_joint_v0 |
SPI joint command | ISO 10218-1:2011, ISO/TS 15066:2016 |
The default sample command uses robot_diff_drive_ros2_v0. The other profiles
are packaged reference inputs that can be supplied through --profile.
Structure¶
{
"schema_version": "1.0",
"profile_id": "my_controller_v0",
"applicable_standards": ["ISO 3691-4:2023"],
"producer_config": {"name": "controller", "interface_type": "ros2_diff_drive"},
"receiver_config": {"name": "receiver", "controller_type": "motion_controller"},
"command_limits": {},
"fault_corpus": {"faults": []}
}
The fault corpus is evaluated only as described by the trace and profile. The presence of a standards reference does not establish compliance with that standard.
See Custom Profiles and Profile Schema.