id stringlengths 9 9 | instruction stringclasses 35 values | context stringclasses 1 value | expected_output stringclasses 1 value | robot_domain stringclasses 7 values | scenario stringclasses 5 values | difficulty stringclasses 3 values | safety_notes stringclasses 4 values |
|---|---|---|---|---|---|---|---|
rs_000662 | Write a safety checklist for a lab robot during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | lab_robot | operating near humans in a shared workspace | hard | Keep clear of pinch points; verify E-stop is functional. |
rs_000565 | Write a safety checklist for a humanoid during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | humanoid | night shift operation with limited supervision | easy | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000753 | Write a safety checklist for a lab robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | lab_robot | night shift operation with limited supervision | easy | Keep clear of pinch points; verify E-stop is functional. |
rs_000498 | Write a safety checklist for a drone during: testing new PID gains on real hardware. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | testing new PID gains on real hardware | easy | Keep clear of pinch points; verify E-stop is functional. |
rs_000082 | Write a safety checklist for a mobile robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | mobile_robot | night shift operation with limited supervision | medium | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000689 | Write a safety checklist for a drone during: testing new PID gains on real hardware. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | testing new PID gains on real hardware | easy | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000182 | Write a safety checklist for a warehouse robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | night shift operation with limited supervision | easy | Test in simulation first; use low speed limits on real hardware. |
rs_000592 | Write a safety checklist for a drone during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | operating near humans in a shared workspace | easy | Keep clear of pinch points; verify E-stop is functional. |
rs_000525 | Write a safety checklist for a lab robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | lab_robot | night shift operation with limited supervision | medium | Do not bypass safety interlocks; confirm payload limits. |
rs_000337 | Write a safety checklist for a mobile robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | mobile_robot | night shift operation with limited supervision | easy | Test in simulation first; use low speed limits on real hardware. |
rs_000532 | Write a safety checklist for a drone during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | first autonomous run after firmware update | easy | Do not bypass safety interlocks; confirm payload limits. |
rs_000784 | Write a safety checklist for a industrial arm during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | industrial_arm | lifting a near-max payload | hard | Keep clear of pinch points; verify E-stop is functional. |
rs_000203 | Write a safety checklist for a humanoid during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | humanoid | night shift operation with limited supervision | easy | Keep clear of pinch points; verify E-stop is functional. |
rs_000499 | Write a safety checklist for a industrial arm during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | industrial_arm | operating near humans in a shared workspace | easy | Keep clear of pinch points; verify E-stop is functional. |
rs_000488 | Write a safety checklist for a service robot during: testing new PID gains on real hardware. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | service_robot | testing new PID gains on real hardware | medium | Do not bypass safety interlocks; confirm payload limits. |
rs_000288 | Write a safety checklist for a humanoid during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | humanoid | operating near humans in a shared workspace | easy | Do not bypass safety interlocks; confirm payload limits. |
rs_000041 | Write a safety checklist for a service robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | service_robot | night shift operation with limited supervision | medium | Keep clear of pinch points; verify E-stop is functional. |
rs_000786 | Write a safety checklist for a warehouse robot during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | lifting a near-max payload | easy | Keep clear of pinch points; verify E-stop is functional. |
rs_000442 | Write a safety checklist for a drone during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | lifting a near-max payload | medium | Test in simulation first; use low speed limits on real hardware. |
rs_000702 | Write a safety checklist for a warehouse robot during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | operating near humans in a shared workspace | medium | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000697 | Write a safety checklist for a drone during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | night shift operation with limited supervision | medium | Do not bypass safety interlocks; confirm payload limits. |
rs_000449 | Write a safety checklist for a lab robot during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | lab_robot | operating near humans in a shared workspace | medium | Do not bypass safety interlocks; confirm payload limits. |
rs_000329 | Write a safety checklist for a mobile robot during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | mobile_robot | operating near humans in a shared workspace | medium | Test in simulation first; use low speed limits on real hardware. |
rs_000482 | Write a safety checklist for a mobile robot during: testing new PID gains on real hardware. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | mobile_robot | testing new PID gains on real hardware | easy | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000622 | Write a safety checklist for a service robot during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | service_robot | first autonomous run after firmware update | easy | Do not bypass safety interlocks; confirm payload limits. |
rs_000749 | Write a safety checklist for a warehouse robot during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | lifting a near-max payload | medium | Test in simulation first; use low speed limits on real hardware. |
rs_000755 | Write a safety checklist for a lab robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | lab_robot | night shift operation with limited supervision | easy | Do not bypass safety interlocks; confirm payload limits. |
rs_000703 | Write a safety checklist for a mobile robot during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | mobile_robot | first autonomous run after firmware update | easy | Keep clear of pinch points; verify E-stop is functional. |
rs_000306 | Write a safety checklist for a warehouse robot during: testing new PID gains on real hardware. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | testing new PID gains on real hardware | medium | Keep clear of pinch points; verify E-stop is functional. |
rs_000700 | Write a safety checklist for a industrial arm during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | industrial_arm | operating near humans in a shared workspace | easy | Do not bypass safety interlocks; confirm payload limits. |
rs_000218 | Write a safety checklist for a humanoid during: testing new PID gains on real hardware. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | humanoid | testing new PID gains on real hardware | medium | Test in simulation first; use low speed limits on real hardware. |
rs_000281 | Write a safety checklist for a mobile robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | mobile_robot | night shift operation with limited supervision | easy | Test in simulation first; use low speed limits on real hardware. |
rs_000279 | Write a safety checklist for a drone during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | night shift operation with limited supervision | easy | Keep clear of pinch points; verify E-stop is functional. |
rs_000599 | Write a safety checklist for a warehouse robot during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | first autonomous run after firmware update | medium | Test in simulation first; use low speed limits on real hardware. |
rs_000156 | Write a safety checklist for a warehouse robot during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | first autonomous run after firmware update | easy | Keep clear of pinch points; verify E-stop is functional. |
rs_000074 | Write a safety checklist for a industrial arm during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | industrial_arm | first autonomous run after firmware update | hard | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000150 | Write a safety checklist for a warehouse robot during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | operating near humans in a shared workspace | hard | Keep clear of pinch points; verify E-stop is functional. |
rs_000169 | Write a safety checklist for a warehouse robot during: testing new PID gains on real hardware. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | testing new PID gains on real hardware | easy | Do not bypass safety interlocks; confirm payload limits. |
rs_000451 | Write a safety checklist for a lab robot during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | lab_robot | first autonomous run after firmware update | medium | Do not bypass safety interlocks; confirm payload limits. |
rs_000178 | Write a safety checklist for a warehouse robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | night shift operation with limited supervision | hard | Keep clear of pinch points; verify E-stop is functional. |
rs_000097 | Write a safety checklist for a service robot during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | service_robot | lifting a near-max payload | hard | Do not bypass safety interlocks; confirm payload limits. |
rs_000750 | Write a safety checklist for a drone during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | lifting a near-max payload | hard | Keep clear of pinch points; verify E-stop is functional. |
rs_000540 | Write a safety checklist for a industrial arm during: testing new PID gains on real hardware. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | industrial_arm | testing new PID gains on real hardware | hard | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000491 | Write a safety checklist for a warehouse robot during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | operating near humans in a shared workspace | easy | Do not bypass safety interlocks; confirm payload limits. |
rs_000157 | Write a safety checklist for a drone during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | night shift operation with limited supervision | hard | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000123 | Write a safety checklist for a warehouse robot during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | operating near humans in a shared workspace | easy | Test in simulation first; use low speed limits on real hardware. |
rs_000729 | Write a safety checklist for a warehouse robot during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | lifting a near-max payload | easy | Do not bypass safety interlocks; confirm payload limits. |
rs_000090 | Write a safety checklist for a lab robot during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | lab_robot | first autonomous run after firmware update | easy | Test in simulation first; use low speed limits on real hardware. |
rs_000537 | Write a safety checklist for a mobile robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | mobile_robot | night shift operation with limited supervision | hard | Do not bypass safety interlocks; confirm payload limits. |
rs_000798 | Write a safety checklist for a humanoid during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | humanoid | operating near humans in a shared workspace | medium | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000664 | Write a safety checklist for a service robot during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | service_robot | lifting a near-max payload | medium | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000643 | Write a safety checklist for a service robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | service_robot | night shift operation with limited supervision | medium | Do not bypass safety interlocks; confirm payload limits. |
rs_000388 | Write a safety checklist for a industrial arm during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | industrial_arm | operating near humans in a shared workspace | medium | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000322 | Write a safety checklist for a drone during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | first autonomous run after firmware update | medium | Test in simulation first; use low speed limits on real hardware. |
rs_000495 | Write a safety checklist for a warehouse robot during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | lifting a near-max payload | easy | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000501 | Write a safety checklist for a mobile robot during: testing new PID gains on real hardware. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | mobile_robot | testing new PID gains on real hardware | easy | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000315 | Write a safety checklist for a industrial arm during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | industrial_arm | operating near humans in a shared workspace | hard | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000366 | Write a safety checklist for a mobile robot during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | mobile_robot | operating near humans in a shared workspace | easy | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000241 | Write a safety checklist for a industrial arm during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | industrial_arm | night shift operation with limited supervision | easy | Test in simulation first; use low speed limits on real hardware. |
rs_000591 | Write a safety checklist for a service robot during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | service_robot | first autonomous run after firmware update | easy | Test in simulation first; use low speed limits on real hardware. |
rs_000094 | Write a safety checklist for a humanoid during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | humanoid | first autonomous run after firmware update | hard | Keep clear of pinch points; verify E-stop is functional. |
rs_000059 | Write a safety checklist for a lab robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | lab_robot | night shift operation with limited supervision | medium | Keep clear of pinch points; verify E-stop is functional. |
rs_000587 | Write a safety checklist for a drone during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | lifting a near-max payload | medium | Test in simulation first; use low speed limits on real hardware. |
rs_000273 | Write a safety checklist for a humanoid during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | humanoid | night shift operation with limited supervision | easy | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000186 | Write a safety checklist for a lab robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | lab_robot | night shift operation with limited supervision | easy | Keep clear of pinch points; verify E-stop is functional. |
rs_000078 | Write a safety checklist for a industrial arm during: testing new PID gains on real hardware. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | industrial_arm | testing new PID gains on real hardware | easy | Keep clear of pinch points; verify E-stop is functional. |
rs_000099 | Write a safety checklist for a humanoid during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | humanoid | first autonomous run after firmware update | medium | Do not bypass safety interlocks; confirm payload limits. |
rs_000386 | Write a safety checklist for a service robot during: testing new PID gains on real hardware. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | service_robot | testing new PID gains on real hardware | easy | Do not bypass safety interlocks; confirm payload limits. |
rs_000255 | Write a safety checklist for a lab robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | lab_robot | night shift operation with limited supervision | easy | Do not bypass safety interlocks; confirm payload limits. |
rs_000252 | Write a safety checklist for a drone during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | night shift operation with limited supervision | medium | Keep clear of pinch points; verify E-stop is functional. |
rs_000463 | Write a safety checklist for a lab robot during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | lab_robot | first autonomous run after firmware update | easy | Do not bypass safety interlocks; confirm payload limits. |
rs_000642 | Write a safety checklist for a humanoid during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | humanoid | lifting a near-max payload | easy | Do not bypass safety interlocks; confirm payload limits. |
rs_000394 | Write a safety checklist for a service robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | service_robot | night shift operation with limited supervision | easy | Keep clear of pinch points; verify E-stop is functional. |
rs_000370 | Write a safety checklist for a warehouse robot during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | first autonomous run after firmware update | hard | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000511 | Write a safety checklist for a industrial arm during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | industrial_arm | operating near humans in a shared workspace | medium | Test in simulation first; use low speed limits on real hardware. |
rs_000050 | Write a safety checklist for a mobile robot during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | mobile_robot | lifting a near-max payload | medium | Test in simulation first; use low speed limits on real hardware. |
rs_000443 | Write a safety checklist for a humanoid during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | humanoid | operating near humans in a shared workspace | easy | Test in simulation first; use low speed limits on real hardware. |
rs_000205 | Write a safety checklist for a warehouse robot during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | warehouse_robot | lifting a near-max payload | medium | Keep clear of pinch points; verify E-stop is functional. |
rs_000551 | Write a safety checklist for a mobile robot during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | mobile_robot | operating near humans in a shared workspace | medium | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000631 | Write a safety checklist for a drone during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | lifting a near-max payload | medium | Do not bypass safety interlocks; confirm payload limits. |
rs_000656 | Write a safety checklist for a humanoid during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | humanoid | night shift operation with limited supervision | easy | Test in simulation first; use low speed limits on real hardware. |
rs_000298 | Write a safety checklist for a service robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | service_robot | night shift operation with limited supervision | medium | Do not bypass safety interlocks; confirm payload limits. |
rs_000204 | Write a safety checklist for a humanoid during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | humanoid | lifting a near-max payload | easy | Keep clear of pinch points; verify E-stop is functional. |
rs_000243 | Write a safety checklist for a mobile robot during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | mobile_robot | operating near humans in a shared workspace | hard | Keep clear of pinch points; verify E-stop is functional. |
rs_000627 | Write a safety checklist for a humanoid during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | humanoid | night shift operation with limited supervision | easy | Test in simulation first; use low speed limits on real hardware. |
rs_000586 | Write a safety checklist for a service robot during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | service_robot | operating near humans in a shared workspace | medium | Keep clear of pinch points; verify E-stop is functional. |
rs_000353 | Write a safety checklist for a humanoid during: testing new PID gains on real hardware. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | humanoid | testing new PID gains on real hardware | easy | Test in simulation first; use low speed limits on real hardware. |
rs_000761 | Write a safety checklist for a mobile robot during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | mobile_robot | operating near humans in a shared workspace | medium | Keep clear of pinch points; verify E-stop is functional. |
rs_000395 | Write a safety checklist for a service robot during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | service_robot | first autonomous run after firmware update | easy | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000547 | Write a safety checklist for a industrial arm during: operating near humans in a shared workspace. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | industrial_arm | operating near humans in a shared workspace | easy | Ensure area is clear; follow lockout/tagout where applicable. |
rs_000319 | Write a safety checklist for a industrial arm during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | industrial_arm | first autonomous run after firmware update | easy | Do not bypass safety interlocks; confirm payload limits. |
rs_000731 | Write a safety checklist for a service robot during: first autonomous run after firmware update. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | service_robot | first autonomous run after firmware update | easy | Do not bypass safety interlocks; confirm payload limits. |
rs_000019 | Write a safety checklist for a drone during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | night shift operation with limited supervision | medium | Keep clear of pinch points; verify E-stop is functional. |
rs_000151 | Write a safety checklist for a drone during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | night shift operation with limited supervision | medium | Do not bypass safety interlocks; confirm payload limits. |
rs_000121 | Write a safety checklist for a drone during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | night shift operation with limited supervision | easy | Keep clear of pinch points; verify E-stop is functional. |
rs_000509 | Write a safety checklist for a industrial arm during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | industrial_arm | night shift operation with limited supervision | medium | Do not bypass safety interlocks; confirm payload limits. |
rs_000579 | Write a safety checklist for a lab robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | lab_robot | night shift operation with limited supervision | easy | Do not bypass safety interlocks; confirm payload limits. |
rs_000381 | Write a safety checklist for a industrial arm during: testing new PID gains on real hardware. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | industrial_arm | testing new PID gains on real hardware | easy | Test in simulation first; use low speed limits on real hardware. |
rs_000533 | Write a safety checklist for a service robot during: night shift operation with limited supervision. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | service_robot | night shift operation with limited supervision | easy | Keep clear of pinch points; verify E-stop is functional. |
rs_000124 | Write a safety checklist for a drone during: lifting a near-max payload. Keep it actionable. | Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.
Do not include anything that bypasses safety interlocks. | Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.
Hardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.
Software: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.
Operator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.
Test protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.
Abort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.
Post-run: power down safely, save logs, document anomalies and corrective actions. | drone | lifting a near-max payload | easy | Keep clear of pinch points; verify E-stop is functional. |
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 9