When I hit the stop button in the controller it doesn’t stop the spindle. Are any of you experiencing this?
A little background:
I just upgraded to a spindle (80mm 220 from PwnCNC)
I just upgraded to 1.4 (from 1.09, yes I know…)
Since I now have control of the spindle I assumed stop would stop everything read in a post from last year (with no responses) that stop may only stop movement not spindle rotation. If this is the case, Estop (in the GUI, not the physical button) worked to stop the movement and the second press allowed to restart.
A little more context. I was running a spindle warm up program that I grabbed from PwnCNC and it has no movement of the OF only spindle rotation. So this may be the reason it feels like a bug. I’ll test it with other programs when I’m ready to start cutting.
where with G4 (Dwell), P is measured in seconds, not in milliseconds. That means your code lets the spindle pause for one and a half month.
Stop does not work during the execution of a command, so stop would work in one and a half month
Better try this one:
Buildbotics’ software-based estopped mode stops any stepper motors, pwm spindles and routers connected via a relay on pin 15 (‘tool-enable’), and spindles on VFDs attached to RS-485 serial communications Modbus interface on pins 13 and 14.
Software-based estopped mode is available either on the red/yellow icon on the top right corner of the User Interface Display, or by attaching a button to pin 23 on the 25-pin I/O port. It is NOT triggered with the mushroom-shaped button on top of the CNC controller case.
it is P[seconds] in the official NIST RS-274/NGC standard. The NIST EMC (Enhanced Machine Controller) later evolved to LinuxCNC, and the Buildbotics took their g-code dialect as model. But the…