Recent PlasmaC Update and No Motion

Should affect both

phillc54 wrote: Should affect both

So what was broke exactly? I had some weird issues that sounded similar at first but I attributed them to the hypersensing comp that Rod ended up updating. I guess I’m asking What recreated the issue?

snowgoer540 wrote:

phillc54 wrote: Should affect both

So what was broke exactly? I had some weird issues that sounded similar at first but I attributed them to the hypersensing comp that Rod ended up updating. I guess I’m asking What recreated the issue?

load say the imperial wrench, start a cut (leave the torch disabled) do a breakaway then resume the job. Motion doesn't resume after the probe.

will we see a v0.166 in the config tab once the update is successfully installed?

Yes. The Buidlbot hasn't yet started to build the packages so it may be a while.

phillc54 wrote:

snowgoer540 wrote:

phillc54 wrote: Should affect both

So what was broke exactly? I had some weird issues that sounded similar at first but I attributed them to the hypersensing comp that Rod ended up updating. I guess I’m asking What recreated the issue?

load say the imperial wrench, start a cut (leave the torch disabled) do a breakaway then resume the job. Motion doesn't resume after the probe.

You know, you’d think I would have experienced this when I was doing the thc tuning and I had my float switch clamped. Maybe I did and I chalked it up to other stuff, because I was fixated on tuning. I wasn’t running a program though just single cuts.

Guess I need to break my torch away more often haha.

After applying update via halcompile.

testing with imperial wrench, machine failed to probe (no ohmic connection) and hit the breakaway, retracted to full height, even with program stopped "no programming running" i have no jog, AXIS +/- does nothing, keyboard does nothing, pressing start moves to line 10 of the gcode, and stops.

snowgoer540 wrote: You know, you’d think I would have experienced this when I was doing the thc tuning and I had my float switch clamped. Maybe I did and I chalked it up to other stuff, because I was fixated on tuning. I wasn’t running a program though just single cuts.

Yes, I am surprised that it hasen't reared is ugly head before.
The main issue is that is wasn't waiting for the offset to complete when going to max height. I also reduced the max offset height to 5mm (0.197") below max limit so we stay well away from the issue with offsets and limits.

I have the same issues as Tesremos. I was able to dry run fine on the first program. But after that first dry run was complete and the program restarted, the second pierce caused the same issue and added a new one. I no longer have any job control after killing the cut program. Navigating to other screens is possible but nothing functions. Only fix is restarting LinuxCNC.

phillc54 wrote:

snowgoer540 wrote: You know, you’d think I would have experienced this when I was doing the thc tuning and I had my float switch clamped. Maybe I did and I chalked it up to other stuff, because I was fixated on tuning. I wasn’t running a program though just single cuts.

Yes, I am surprised that it hasen't reared is ugly head before.
The main issue is that is wasn't waiting for the offset to complete when going to max height. I also reduced the max offset height to 5mm (0.197") below max limit so we stay well away from the issue with offsets and limits.

So if I’m understanding correctly, how we have probe height offsets set could affect whether or not we saw an issue?