In the Windows Simulation Die Accelerators would sometimes have dips in command voltage or report Drive Not Responding errors. This was tracked down to a simulation only issue.

In the windows simulation the press operations were being logged to the console window to make watching the simulation easier. These debug prints were sometimes causing the press task not to run and generate new Set-points but the timer interrupts, encoder simulation and Loop still did run. This caused a dip in the command signal as the Loop tried to follow the instantaneous stop in the Set-points and then a Drive Not Responding when the Set-points instantly started again.