Feature Request

snowgoer540 wrote: 2. I met Rod's Kangaroo. Circumstances: I forgot to enable the torch. Pressed F9, it ohmic sensed until infinity. Video Evidence . My stupidity, but maybe the software should let us know when we're trying to do something stupid?

Watching your video makes me wonder if this is not caused by the material bouncing on impact the way your material is overhanging the slat like that. I've had similar issues with high warpage. Are you still using hypersensing with ohmic2.comp?

I have to get some parts cut over the weekend, and I think my machine is back together, so I may get a chance to review this. I want to have a think about how to account for this...

I just pushed some fixes which hopefully will sort issues these out.

@Greg, I updated the cut-recovery branch as well.

@Clive, can you recall how it happened as it "should" only affect the manual/single cut feature.

phillc54 wrote: I just pushed some fixes which hopefully will sort issues these out.

@Greg, I updated the cut-recovery branch as well.

@Clive, can you recall how it happened as it "should" only affect the manual/single cut feature.

Sorry Phill at the time I thought it was my incompetence some time ago now but I am fairly sure it was with the single line cuts but probably messing around ie jumping back and forwards with run panel and config as well. So not helpful.

phillc54 wrote: OK, so it seems all machines are different...

Maybe, but what I think is going on is that everyone's Hypertherm is currently the same (WRT CPA), but we are trying to use them in different applications but considering it the same because the uses all require CPA. For example, Stefan uses CPA with an F9 and manual jogging which doesn't require the Arc-ok signal at all to work. I want to use CPA with a program to cut a specific shape out of expanded metal, which will require the Arc-ok signal to continue motion. Still out on the testing, but I'm 98% sure hypertherm doesnt provide Arc-ok with the torch on even though it's in CPA.

I can emulate that in a sim so it should be fixable.

Perfect, I like when issues are reproducible easily!

When you say straight cut was it Single Cut from the run panel or a "manual" cut.?

Sorry, yes Single Cut from the run panel.

So the system errored then paused and you couldn't jog?

Correct. And also after I pressed stop, it sometimes wouldn't let me jog for a few seconds.

That was a freeby, didn't you want it?

Well, admittedly it was entertaining and made me chuckle, so I'll take that! :lol:

Me either

Luckily misery loves company.

I know you are just doing your job but I thought I told you that I wasn't bored.

Well, when I said double down, I meant it :laugh::silly: At least you know I'm true to my word!


I see that you've pushed a fix for these things, but I didn't want to not answer your questions in case there was something hanging out there you were waiting on an answer from me for. I will update, and get back to doing what I do best! Thanks for taking the time to fix these things! Much appreciated.

rodw wrote: Watching your video makes me wonder if this is not caused by the material bouncing on impact the way your material is overhanging the slat like that. I've had similar issues with high warpage. Are you still using hypersensing with ohmic2.comp?

I have to get some parts cut over the weekend, and I think my machine is back together, so I may get a chance to review this. I want to have a think about how to account for this...

I remembered that you'd had a similar looking error, but this one was caused because I didnt have the torch on in the GUI. So it would come down, find the surface, and try to fire the torch, since it was off, it counted it as a failed attempt, and then would try again. The only problems I think are present in this particular scenario are that 1. It allowed me to manually fire the torch without having the torch enabled. 2. It didn't count the failed attempts as failed attempts.

Yes, I am using Ohmic2.comp still. I should also point out that after I clicked to turn the torch on, the ohmic stuff worked as intended. I've not had any issues with ohmic, save for rusty material not making a good connection.

snowgoer540 wrote: I didn't want to not answer your questions in case there was something hanging out there you were waiting on an answer from me for. I will update, and get back to doing what I do best! Thanks for taking the time to fix these things! Much appreciated.

Hopefully I got it sorted but if not I am confident you will be able to find out.

BTW I like the colour (color) of the water in you tray, it reminded me of the Little Colorado River.