Botopsy Lab

Learn Case Files Playgrounds Diagnose a robot

Learn Case Files Playgrounds Pricing Sign in Diagnose a robot

Loading system evidence

Botopsy Lab

Diagnostic training for engineers who need to restore real robot systems, not repeat expected outputs.

BUILD / BREAK / DIAGNOSE / FIX

Explore

Learn Case Files Playgrounds Projects Universities Pricing

Resources

Documentation Status Discord Support

First repair is public

Find the frame fault.

No account is required for the first diagnosis.

© 2026 Botopsy Lab. All rights reserved.

Privacy Policy Terms of Service Refund Policy

[email protected]

22 live cloud cases · full library free to explore

Case Files

Start with a symptom. Collect evidence, commit to a hypothesis, repair the system, and prove the fix.

Start free case 001

Public guided case

The obstacle appears on the wrong side

Align LiDAR evidence with the physical warehouse without reversing scan samples.

LiDAR measurementbase_link to laser transformcostmap

Inspect the evidence

Mobile robot reliabilitySYSTEM / FAULT / EVIDENCE

Incident library

Browse by system boundary.

Course disclosures keep the full library available without presenting 96 equal choices at once.

01Robotics Development Setup & Recovery16 cases

01Gazebo freezes inside the virtual machineResource selectionPreview 02The LiDAR is absent inside WSLHardware accessPreview 03The installer cannot see free spaceDisk preparationPro 04Windows asks for a recovery key after repartitioningDisk encryptionPro 05The installer boots in legacy modeFirmware modePro 06NVIDIA driver loads to a black screenSecure BootPro 07The root partition fills during a ROS buildPartition sizingPro 08The installer plans to format the EFI partitionPartition safetyPro 09Windows disappears from the boot menuBootloader discoveryPro 10WiFi is missing after installationKernel driverPro 11The serial port denies accessLinux permissionsPro 12The node works in a shell but fails as a serviceService environmentPro 13Packages cannot be resolvedDistribution compatibilityPro 14Conda shadows ROS Python packagesPython environmentPro 15The new package cannot be foundWorkspace overlayPro 16The old code still runsBuild statePro

02ROS 2 Systems Debugging16 cases

01The topic exists but publishes nothingPublisher control flowPro 02The heartbeat stalls while diagnostics runCallback groupsPro 03The topic exists but no messages arriveQoS reliabilityPro 04Late subscribers miss the mapQoS durabilityPro 05The late subscriber never learns its configQoS durabilityPro 06The transform is too oldTF bufferPro 07One node uses wall timeSimulation clockPro 08The prepare-pick trigger deadlocks the supervisorExecutor deadlockPro 09The robot stopped during a deliveryIncident reconstructionPro 10The node appears missingProcess lifecyclePreview 11The process runs but node creation failedCompositionPreview 12The action server cannot be foundNamespacePro 13The launch file places a node in the wrong namespaceLaunch scopePro 14The parameter loads under the wrong nodeParameter YAMLPro 15The safety subscriber reacts two seconds lateExecutor blockingPro 16The bag replay cannot reproduce the faultReplay timePro

03Mobile Robot Reliability16 cases

01The obstacle appears on the wrong sideSensor frameLive 02The scan is mirrored after filteringLaserScan indexingPro 03The robot drives straight but odometry curves leftEncoder signPro 04Simulation is accurate but hardware driftsOdometry calibrationPro 05The model explodes in GazeboInertial modelPreview 06The planner clips shelving cornersCollision geometryPreview 07Detections appear behind the robotOptical frame conventionPro 08Empty space fills with obstaclesInvalid sensor dataPro 09The robot climbs an impossible rampMotor limitsPro 10Perfect LiDAR hides localisation failureSensor realismPro 11The map draws the corridor twiceScan matchingPro 12A false loop closure folds the mapPose graphPro 13Localisation never convergesInitial posePro 14The robot cannot relocalise after a bumpMotion modelPro 15The test passes against a stale mapTest isolationPro 16One random seed hides wheel slipRobustness testingPro

04Nav2 Incident Response16 cases

01The goal is accepted but the robot never movesLifecycleLive 02The costmap ignores visible scansSensor sourcePro 03Protective stops trigger oscillation recoverySafety integrationPro 04One server never follows startupLifecycle orchestrationPreview 05A removed pallet remains blockedObstacle clearingPro 06A wide corridor is rejectedFootprint geometryPro 07Inflation closes the doorwayInflation policyPro 08The planner rejects a reachable dockGoal validityPro 09The path cuts through unmapped spaceUnknown-space policyPro 10The robot spins but cannot move forwardVelocity constraintsPro 11The controller refuses a safe bendTrajectory criticsPro 12Recovery loops foreverBehavior tree control flowPro 13Recovery resumes toward the old goalBehavior tree blackboardPro 14The robot reaches the goal but never succeedsGoal tolerancePro 15A restart repeats the deliveryMission idempotencyPro 16The robot docks but never chargesDocking statePro

05Hardware Integration & CANopen16 cases

01Every CAN frame is an errorCAN bitratePro 02The interface repeatedly enters bus-offCAN error recoveryPro 03The drive remains pre-operationalCANopen NMTPro 04The motor receives commands but stays disabledCiA 402 enable sequencePro 05The controller loads but cannot activateCommand interfacePro 06The drive moves to another device pathDevice identityPreview 07The controller disconnects under accelerationPower integrityPreview 08CAN fails only at full cable lengthCAN terminationPro 09The CAN device exists but sends nothingSocketCAN statePro 10Two drives answer as one nodeCANopen identityPro 11Velocity commands become enormousPDO encodingPro 12The control loop stalls on SDO trafficCANopen timingPro 13The drive faults immediately after resetCiA 402 fault recoveryPro 14A second controller cannot switch inResource claimsPro 15The robot keeps moving after software stopsCommand watchdogPro 16The drive re-enables after an emergency stopSafe recoveryPro

06Production ROS Operations16 cases

01The robot works on one laptop but not anotherDDS domainLive 02Discovery is asymmetric across middlewareDDS configurationPreview 03The graph disappears when the firewall startsFirewallPro 04WiFi roaming stalls control dataWireless reliabilityPro 05The container cannot open CANContainer capabilityPro 06The container loses project changesContainer storagePro 07The robot fails only at bootStartup readinessPro 08A restart loop erases the useful logService recoveryPro 09The service is green but uselessReadinessPro 10The workspace failure has no causal traceTrace propagationPro 11Two robots run different code under the same tagRelease identityPro 12The canary passes while missions failRollout gatePro 13Rollback starts but cannot load configurationRollback compatibilityPro 14The diagnostic bundle contains credentialsEvidence handlingPro 15Only one warehouse loses navigationFleet cohortPro 16Recovery causes a second outageIncident commandPro