Showstopper Plasma Cutter retrofit

tommylight wrote:

Yes it is and that is unfortunate as the probing is done twice every time at very low speeds.
I am beating a dead horse, as i have insisted from the very start of PlasmaC that should not be implemented at all, only a single probe.
On a plate with over 200 pierces, probing time is in hours, no matter how fast the Z axis is.

I've seen you say this numerous times on the forum. This has to be a setting/config issue on your part. In an effort to hopefully put the "they didnt listen to me" part of this to bed, I made a video this evening while I was cleaning up the garage. It shows QtPlasmaC (using the PlasmaC component) doing 2,400 probes. Not a single one of them double probed, and it should be noted that all 2,400 probes were completed in ~1 hour.



It should also be noted that I made Cut Height and Pierce Height equal so it didn't look like there was an extra probing move.

I should also note that when the heights/settings are wrong, probing does take longer.

phillc54 wrote:

It is probably an incorrect setting, my table only probes once.

X2, I agree.

snowgoer540 wrote:

Deleting the var file was a placebo. When you receive that error, it's because the ohmic probe tripped prior to reaching probe height. 

This cannot happen. Ohmic sensing monitors motion.motion-type and can only activate when linuxcnc is actually probing, If its triggering, it has to be the breakaway or float switch.

rodw wrote:

snowgoer540 wrote:

Deleting the var file was a placebo. When you receive that error, it's because the ohmic probe tripped prior to reaching probe height. 

This cannot happen. Ohmic sensing monitors motion.motion-type and can only activate when linuxcnc is actually probing, If its triggering, it has to be the breakaway or float switch.

That seems a bit odd as default plasmac configs don't use the LinuxNC internal probing, they usually use external offsets.

phillc54 wrote:

That seems a bit odd as default plasmac configs don't use the LinuxNC internal probing, they usually use external offsets.

But isn't plasmac.ohmic-enable only enabled when ohmic probing? We monitor that too.

rodw wrote:

phillc54 wrote:

That seems a bit odd as default plasmac configs don't use the LinuxNC internal probing, they usually use external offsets.

But isn't plasmac.ohmic-enable only enabled when ohmic probing? We monitor that too.

Yes, but probing is enabled from the beginning of the down motion before probe height is reached because fast probing is valid.

rodw wrote:

snowgoer540 wrote:

Deleting the var file was a placebo. When you receive that error, it's because the ohmic probe tripped prior to reaching probe height. 

This cannot happen. Ohmic sensing monitors motion.motion-type and can only activate when linuxcnc is actually probing, If its triggering, it has to be the breakaway or float switch.

It's exactly how it works.

Videographic evidence: