Post
A very realistic SO-101 classroom problem appears when students select the wrong configuration, namespace, or robot profile. The arm may still connect, but one or more joints move in the wrong direction or respond in ways that do not match the lesson plan.
How are you diagnosing SO-101 motion problems caused by students loading the wrong config?
Please share how you detect config mismatch quickly, which signs indicate a profile or direction-map issue instead of hardware damage, and what classroom safeguards stop the same mistake from happening again.
If you reply, include one exact wrong-motion symptom and one exact startup or validation step that exposed the config problem.