For the exit slits (SL1K2 target), we had a case where the arbiter wasn't sending us any data, but this was causing motion to fail entirely, instead of just timing out the arbiter request and doing the motion with a fast fault as is intended.
The motor is absolutely encoded, is configured for enable during motion, and works great other than the case where the arbiter isn't working, in which case it works... sometimes (???)
For the exit slits (SL1K2 target), we had a case where the arbiter wasn't sending us any data, but this was causing motion to fail entirely, instead of just timing out the arbiter request and doing the motion with a fast fault as is intended.
The motor is absolutely encoded, is configured for enable during motion, and works great other than the case where the arbiter isn't working, in which case it works... sometimes (???)