buildbotics / bbctrl-firmware

Buildbotics CNC Controller Firmware
https://buildbotics.com/
Other
67 stars 26 forks source link

Ability to move tool during pause #220

Open leadgtr7 opened 5 years ago

leadgtr7 commented 5 years ago

It would be great to have a command that would prompt user to continue but allow the machine to still move with the gamepad.

Use case would be to send a M6 tool change that woud execute a probe command and allow user to move tool head to anywhere to run the probe.

DougCoffland commented 4 years ago

A second customer has asked for the ability to take control of the machine during a pause. His use case was if a tool breaks or slips, he would like to be able to pause and change the tool, then resume operation.

I would add to that the ability to pause, select a gcode line and then resume executing from that line. LinuxCNC has this capability.

tmadrms commented 4 years ago

Since I’m just getting setup I’ve not run into this yet, but this will certainly be a welcomed addition.

tmadrms commented 4 years ago

This became even more desirable now that I've been doing longer cuts. In my case not only would be nice to be able to move the tool, but also stop the spindle for an overnight break and restart same place in the morning. I can achieve this by hacking up the g-code file, but it would be much nicer to just be able to pause and turn it off.

Aiph5u commented 2 years ago

Hey Doug @DougCoffland, hey all,

I'd like to let you know that this feature is requested by users of the Onefinity CNC Controller which uses a fork of Buildbotics Controller.

This issue, i.e.

No jogging in x, y, or z possible during tool change event (M6) or during pause

was discussed the other day when I was focusing on using a smart g-code insertion in the ‘tool-change’ field of the General Configuration Tab for allowing tool changes inside programs as Buildbotics suggested in Manual V1.1.

While inserting a more or less smart g-code into the 'tool-change' field allows at least certain tool changes (but only at a position that this g-code provides), more than one user say that with other CNC Controllers, they have the full freedom to jog around on all axes, or probe Z, and that they are really missing this feature on the Onefinity and the Buildbotics Controller:

Do you think it would be difficult to implement this feature?

TheColonel2688 commented 2 years ago

This became even more desirable now that I've been doing longer cuts. In my case not only would be nice to be able to move the tool, but also stop the spindle for an overnight break and restart same place in the morning. I can achieve this by hacking up the g-code file, but it would be much nicer to just be able to pause and turn it off.

Unless I am missing something

  1. You can already do this.
  2. That has nothing to do with this issue as stated.

Shrugges

TheColonel2688 commented 2 years ago

@Aiph5u

Hey Doug @DougCoffland, hey all,

I'd like to let you know that this feature is requested by users of the Onefinity CNC Controller which uses a fork of Buildbotics Controller.

This issue, i.e.

No jogging in x, y, or z possible during tool change event (M6) or during pause

was discussed the other day when I was focusing on using a smart g-code insertion in the ‘tool-change’ field of the General Configuration Tab for allowing tool changes inside programs as Buildbotics suggested in Manual V1.1.

While inserting a more or less smart g-code into the 'tool-change' field allows at least certain tool changes (but only at a position that this g-code provides), more than one user say that with other CNC Controllers, they have the full freedom to jog around on all axes, or probe Z, and that they are really missing this feature on the Onefinity and the Buildbotics Controller:

* [here](https://forum.onefinitycnc.com/t/like-many-new-forums-the-excitement-and/9209/21) and [here](https://forum.onefinitycnc.com/t/like-many-new-forums-the-excitement-and/9209/25)

* [Feature Requests: Tool change jogging plus notifcation/ETA of toolchange](https://forum.onefinitycnc.com/t/tool-change-jogging-plus-notifcation-eta-of-toolchange/6091)

* [Here’s a key element missing from the BB controller](https://forum.onefinitycnc.com/t/heres-a-key-element-missing-from-the-bb-controller/10405) (with video!)

Do you think it would be difficult to implement this feature?

Note: The 1F Firmware is forked from BB firmware and is maintained by different people. BB firmware is incompatible with the 1F controller hardware so unless you have a BB controller, asking for features in the BB Firmware won't help you.

Aiph5u commented 2 years ago

Hey TheColonel2688,

Note: The 1F Firmware is forked from BB firmware and is maintained by different people.

I had a look at both codebases. I believe that if it was implemented in the buildbotics code, it could easily be adapted downstream. Onefinity is not that responsive to this feature request.

Also at least one user (see link above) stated he would switch to Buildbotics Controller if this feature was implemented.

BB firmware is incompatible with the 1F controller hardware so unless you have a BB controller, asking for features in the BB Firmware won't help you.

By the way, the Buildbotics hardware was forked too (see here vs. here).

TheColonel2688 commented 2 years ago

I had a look at both codebases. I believe that if it was implemented in the buildbotics code, it could easily be adapted downstream. Onefinity is not that responsive to this feature request.

Well yeah but Onefinity would have the merge the changes unless you forked the 1F code and then merged the changes. 1F repo seems to be waaaaaaay behind BB. so merging in upstream features doesn't seems to be something they are interested in.

Also at least one user (see link above) stated he would switch to Buildbotics Controller if this feature was implemented.

I missed that part

By the way, the Buildbotics hardware was forked too (see here vs. here).

Yes, but they have Diverged.

My point is simply unless YOU are going to do the merging into the 1F codebase then asking for new features here is point less, as the 1F team seems to have no interest in it.