That could be the case.
I personally think it has something to do with the way I programmed the movement of the disc. The printer sends a busy response through the serial connection while executing a XYZ movement (G1). So normally the printer is running multiple processes at the same time. My code seems to prevent multiple processes. There is no response through the serial. I think the program is stuck in the waiting times that I used for manipulating the servo drive. Therefore the printer is no longer able to do anything else besides operating the servo which leads to some kind of internal error.
In other words, I should be programming the movement of the disc in such way that it doesn't use those waiting times. But again, I'm a absolute beginner in these kind of things.
I personally think it has something to do with the way I programmed the movement of the disc. The printer sends a busy response through the serial connection while executing a XYZ movement (G1). So normally the printer is running multiple processes at the same time. My code seems to prevent multiple processes. There is no response through the serial. I think the program is stuck in the waiting times that I used for manipulating the servo drive. Therefore the printer is no longer able to do anything else besides operating the servo which leads to some kind of internal error.
In other words, I should be programming the movement of the disc in such way that it doesn't use those waiting times. But again, I'm a absolute beginner in these kind of things.