Murphys Law Commands

[Inspirol]

Anything that could go wrong will go wrong. With that said, think about any failure points in your subsystem, and any workarounds we can produce for that.

For example, if the wrist absolute encoder is messed up (meaning the wrist motor doesn't know where it is) some possible solutions could be:

1. running the wrist down until the current spikes due to the stopper. That way, we would know where are.

2. run the wrist down and only shoot up close

you get the idea

[mbardoe]

Super Idea... Let's make sure to put as many ideas here as we can.

[gap-06]

Wrist potential issues: (will reply with potential solutions)

1. Absolute encoder messed up (What Sebastian said)
2. Issue setting correct target velocity
3. The wrist/pivoting motor doesn't work

[gap-06]

2. Issue setting correct target velocity

Allow for overriding so that if it's going at a velocity much higher/lower than intended, the target vel can be multiplied by a constant to match intended amount