Finished a project. Replaced the stock. Reset XYZ with Autoplate. Reviewed with outline then I hit run.
Spindle goes to XY, waits it’s wind up time then lowers to the project and starts to ramp in without the spindle turning. No G code was changed.
I haverun through the troubleshooting. The console shows nothing. I reset to the original specs. Unplugged everything to remove all static memory, rebooting cold. Nothing worked. I am hesitant to start doing the wire checks and changes Scieni says as everything worked fine 5 minutes earlier.
You got up out of bed …
On a possibly bit more helpful note, what does the display on the VFD say? Does it still appear to be alive? Did you check the connector at the top of the spindle to see if it is seated properly? I believe that there is a way to manually control the spindle from the VFD but I do not know the steps you need to take to accomplish that (sorry). I would also verify the Altmill configuration to verify that it is set up to run a spindle rather than a router that is turned on manually. Nothing should have changed in the configuration but shit happens.
From what you report, there is nothing you did that caused this. I would have expected gSender or the controller to have caught the fact that the spindle was not up to speed but it would appear that there is a condition where the feedback from the spindle just doesn’t work.
I would wait a day to see if anybody comes up with an idea but after that I would raise a ticket with Sienci.
@Groucho194 I’d follow Sienci’s advice and check the cable from the VFD to the spindle. There have been reports of a wire breaking off at one of the connectors.
If you want to see if the VFD and spindle (and cable) are fine, put the VFD in manual mode. The instructions are somewhere in here : Spindle and VFD – Sienci Labs. There are other troubleshooting steps you might want to follow before going to manual mode.
But before all that, can you control the spindle from gSender? At the bottom right, there’s a spindle tab. You can start, stop, change speed from here without using any gcode.
Just yesterday mine did the same thing. I mistakenly set Z depth incorrectly, as soon as the program started I saw the error and hit stop on Gsender the gantry stopped but spindle did not. The Estop failed to stop the spindle and I had to unscrew the connector on top of the spindle to stop it. On subsequent attempts to restart the program the spindle didn’t start. After cold resets, etc. I noticed the the spindle controller panel had strange numbers on it. Following much fiddling around with controller I was able to get it to read F 125 again. The spindle restarted correctly on the next program run attempt. It wasn’t apparent to me exactly what I did to restore the typical display of F 125.