Postby sebste » Wed Mar 06, 2019 10:34 pm
Okay - With a little massaging of the GRBL postprocessor I finally got a version that works for me, which I have attached.
* I added a --spindle-wait option to give the spindle some time to get up to / change speed.
* I also added a --stop-on-zero-rpm option to replace spindle start with 0 rpm by spindle stop command (M3 S0.0 -> M5) if desired
* It also addresses the following problem (I think it really could be seen as a bug, but this sort of a hack at least band-aids it, even if in the wrong place):
If different tool controllers are used for the same tool number, the changes in spindle speed for the subsequent operations are ignored if there is no change to a different tool number in between.
Say we create a tool controller with aggressive feeds and speeds for a roughing operation for tool #1 and another tool controller with more moderate feeds and speeds i.e. for a spring pass operation directely afterwards, then Path does realize that the tool# has not changed between operations and therefore does not issue a toolchange. Since the spindle commands are tied to tool changes, Path does not apply the changes in SpindleSpeed to the spring pass operation.
This modified postprocessor fixes this problem by removing all spindle start commands issued by the tool change and puts them right at the beginning of the operation. So every operation has its own spindle start command which reflects the changes in spindle rpm between different tool controllers for the same tool#
Let me know what you think.
-
Attachments
-
spindle_mod_grbl_post.py
- (13.8 KiB) Downloaded 18 times