Today, at the start of our team meeting, the port 18 on our HS team robot died - it stopped being able to move the motor. The motor does short blink with about 1s period, the brain sees the motor in the device view, but ignores the up/down arrows. The motor is OK, so is the cable:
*) we have tried another motor and observed the same behavior.
*) we have moved the cable to the port 17 and the original motor, with the original cable worked flawlessly.
*) After switching back to port 18, we have reproduced the same problem - brain seeing the motor, but ignoring the command arrows.
We tried various things including power cycling the brain, but our port 18 is gone.
What is super intriguing is that before the end of the meeting, our MS team robot developed the same issue (similar robot design, the same port 18 used for the same purpose - intake roller motor).
Now, both of those robots were heavily battle tested before, worked well for more than a month being used almost daily by the drive team and the team programmers.
So we now have two brains with port 18 unusable, even though the port still apparently communicates. I haven’t tried any advanced troubleshooting so far, I might try observing the power delivery to the motor and checking if the brain sees motor movements next, but for the time being, we’ve swapped to port 17 and went on with the meeting…