Feature Request

Penguin Phill (the lady says hi :lol:)

Hi Lady

Does CR have to be a button in the Extras panel, or can it be a custom button on the main page as well?

Only the extras at this stage, I would need to duplicate the code into two other scripts to make it available on any user button. I was kinda thinking that it wouldn't be used a lot so could hide away until needed.

Is the X at the top left? I thought it was at the top right (so I changed it)

Oops, yes that depends on the windows manager settings. I always put the controls on the left so it is the same as my Macs.

Is the GUI's Resume button the Play symbol or the Pause symbol.

Pause symbol.

Also, editing this got me thinking... do we really need to move the torch along the cut path during a CR event? I get that sometimes you want to move forward or backward depending on where you are at in the cut. Say it flamed out at the end of the cut and you just want to move to the beginning of the next cut, for example.

I have never used it but it has been a part of PlasmaC since the beginning and it doesn't cost anything...

At any rate, see attached for my edits.

I'll check it out later, off to do grocery shopping with the chief. :S

phillc54 wrote:

Penguin Phill (the lady says hi :lol:)

Hi Lady

Does CR have to be a button in the Extras panel, or can it be a custom button on the main page as well?

Only the extras at this stage, I would need to duplicate the code into two other scripts to make it available on any user button. I was kinda thinking that it wouldn't be used a lot so could hide away until needed.

Is the X at the top left? I thought it was at the top right (so I changed it)

Oops, yes that depends on the windows manager settings. I always put the controls on the left so it is the same as my Macs.

Is the GUI's Resume button the Play symbol or the Pause symbol.

Pause symbol.

Also, editing this got me thinking... do we really need to move the torch along the cut path during a CR event? I get that sometimes you want to move forward or backward depending on where you are at in the cut. Say it flamed out at the end of the cut and you just want to move to the beginning of the next cut, for example.

I have never used it but it has been a part of PlasmaC since the beginning and it doesn't cost anything...

At any rate, see attached for my edits.

I'll check it out later, off to do grocery shopping with the chief. :S

Grocery shopping sounds... fun? My experience is always that like 4 things cost at least $50. Never seems to be an inexpensive experience. Luckily the lady went on Friday while I worked from home

Ok, I updated the document again to make the changes to the questions I wasn't sure of. Removed from the previous post and attached here.

As for the motion sliders in the CR dialog box, I guess I am wondering how it would behave then. Call the point at which it caused point A, and the point someone moves it to along the cut path point B. If during a CR event, you move from point A to point B, then use the direction buttons (call it point C), and then press Resume Cut, does the torch go from point C to point B, or point C to point A?

I would expect point C to point B. Just checking.

I guess the only other thought to ponder would be: Does it make sense to leave paused motion Fwd and Rev off of the CR dialog box? I only ask because it would seem that moving the torch along the cut path before using the direction arrows sort of defeats the point of using the direction arrows in the first place. If that makes sense?

Looks good, a couple of changes:

Leave this bit out as I "may" do that in master (and the next 2.8 version) if there is enough interest. I don't think there is not enough time to get it into 2.8 before release.
"Note: this function cannot be moved to any of the user-programmable buttons on the main screen."

Change:
"(or the X at the top right)"
to:
"(or the X in the title bar)"

As for the motion sliders in the CR dialog box, I guess I am wondering how it would behave then. Call the point at which it caused point A, and the point someone moves it to along the cut path point B. If during a CR event, you move from point A to point B, then use the direction buttons (call it point C), and then press Resume Cut, does the torch go from point C to point B, or point C to point A?

I would expect point C to point B. Just checking.

Correct, the first move is from current position to where it was prior to the direction buttons being used.

I guess the only other thought to ponder would be: Does it make sense to leave paused motion Fwd and Rev off of the CR dialog box? I only ask because it would seem that moving the torch along the cut path before using the direction arrows sort of defeats the point of using the direction arrows in the first place. If that makes sense?

I think it should, it is and always was a part of the cut recovery process. I would guess that on most cut errors the torch would move on a small distance until the error paused the machine. Then you would just reverse along the path then offset into the scrap side with the direction buttons.


P.S. I liked your Eagle Rare video, if I were you, I would go click Machine then uncheck Show Offsets to give a cleaner look in the Preview tab. If you want to see the offsets you can check with the DRO tab.

phillc54 wrote: Looks good, a couple of changes:

Leave this bit out as I "may" do that in master (and the next 2.8 version) if there is enough interest. I don't think there is not enough time to get it into 2.8 before release.
"Note: this function cannot be moved to any of the user-programmable buttons on the main screen."

Change:
"(or the X at the top right)"
to:
"(or the X in the title bar)"

As for the motion sliders in the CR dialog box, I guess I am wondering how it would behave then. Call the point at which it caused point A, and the point someone moves it to along the cut path point B. If during a CR event, you move from point A to point B, then use the direction buttons (call it point C), and then press Resume Cut, does the torch go from point C to point B, or point C to point A?

I would expect point C to point B. Just checking.

Correct, the first move is from current position to where it was prior to the direction buttons being used.

I guess the only other thought to ponder would be: Does it make sense to leave paused motion Fwd and Rev off of the CR dialog box? I only ask because it would seem that moving the torch along the cut path before using the direction arrows sort of defeats the point of using the direction arrows in the first place. If that makes sense?

I think it should, it is and always was a part of the cut recovery process. I would guess that on most cut errors the torch would move on a small distance until the error paused the machine. Then you would just reverse along the path then offset into the scrap side with the direction buttons.


P.S. I liked your Eagle Rare video, if I were you, I would go click Machine then uncheck Show Offsets to give a cleaner look in the Preview tab. If you want to see the offsets you can check with the DRO tab.

Ok I can make those changes in the morning if you’d like and I’ll attach them here.

New release? I don’t follow along at that level so I’m not sure what’s going on with LinuxCNC itself.

Truthfully, I moved “load sheet” off of my main screen and swapped in Cut Recovery at the end of the night, I didn’t think to test it quick lol. I just figured I’d use it more often than load sheet. I’ll move her back for now no biggie.

Like you said it doesn’t hurt anything having it there. All of the cuts I made when I induced failures were made from the point of failure, I didn’t jog along the cut path at all, just for the record.

Oh, I didn’t know that was an option, or if I did I forgot. I’ll definitely do that. It’ll be nice to have it be cleaner.

Ok I can make those changes in the morning if you’d like and I’ll attach them here.

All good, I can do it here. I just copied and pasted yours into the docs and made those two changes. Thanks again.

New release? I don’t follow along at that level so I’m not sure what’s going on with LinuxCNC itself.

2.8 is in final testing and about to be released. Once it is released then new features won't appear in the distribution ISO until the next point release (2.8.1) I want to get CR in 2.8 before release and there will not be enough time to add the code so it can be on the main GUI screen and test it out thoroughly.
Having said that if you use Buildbot builds then any additions will be available immediately. Not half confusing is it?

User Guide extract


Part of the message is hidden for the guests. Please log in or register to see it.