10-22-24 UPDATE! CNC12 v5.20 has been released Mill, Lathe, Router, Plasma is now available for public testing.

[djbeede]

we should have a v5.2 release candidate very soon, tomorrow most likely.

Any new guesstimate for when v5.2 will be available?
Thanks!

[cnckeith]

we should have a v5.2 release candidate very soon, tomorrow most likely.

Any new guesstimate for when v5.2 will be available?
Thanks!

i'm about to post a CNC12 v5.20 RC4 (release candidate #4 ) publicly, working on it now. Lots and Lots of stuff in this one!!!

[cncsnw]

Probably a little late to be asking this, but will the v5.20 release include a router-specific version of CNC12 for Oak/Allin1DC/MPU11?

[cnckeith]

Probably a little late to be asking this, but will the v5.20 release include a router-specific version of CNC12 for Oak/Allin1DC/MPU11?

Nope, Acorn, AcornSix and Hickory only for the new CNC12 Router version. (i'll see about that for oak/ain1/mpu11 in v5.3)

if you are a Centroid Alpha or Beta tester you got an email just now with a download link, please give it a go, if i don't hear any show stopper reports then i'll post here publicly.

[Sword]

I think there's an issue with Set Part Zeros and Manual positioning. For example, I want to probe the inside of an octagon frame for center. I start on the right side, and probe that edge and set the DRO to zero when finished. Then I jog over to the other edge and probe that edge to find the distance. When that edge is finished probing, the DRO changes from WCS to Machine Coordinates.

[cnckeith]

I think there's an issue with Set Part Zeros and Manual positioning. For example, I want to probe the inside of an octagon frame for center. I start on the right side, and probe that edge and set the DRO to zero when finished. Then I jog over to the other edge and probe that edge to find the distance. When that edge is finished probing, the DRO changes from WCS to Machine Coordinates.

thanks for reporting, looking into it now
are you using the probing cycles in the probing menu or the F7 Auto Zero (one axis at a time ones) in the part setup menu?

or

[cnckeith]

working on RC5 at the moment. today we fixed a rare annoying windows wxwidgets error message on start up bug and made some other minor wording changes for clarity.

[Sword]

thanks for reporting, looking into it now
are you using the probing cycles in the probing menu or the F7 Auto Zero (one axis at a time ones) in the part setup menu?

I was using the Auto Zero (Set part zeros/manual). Wanted to use the bore probe routine, but needed to change the max probe distance to allow it to travel all the way across a 22"+ span. The manual allowed for jogging to the other side instead of waiting for it to slowly make it's way over.
I didn't try it before shutting down for the day, but could probably have hit escape and came back in to try the other side. It works for the first attempt on one edge, but not a second attempt for the other edge. This was for X, didn't try Y.

[Sword]

thanks for reporting, looking into it now
are you using the probing cycles in the probing menu or the F7 Auto Zero (one axis at a time ones) in the part setup menu?

After revisiting this the next morning, it's setting the WCS DRO to the Machine coordinate value when finished probing (no F10/Set was issued afterwards). What I would have expected, would be that once one side is probed the DRO value would still read the active WCS location, and you could set that axis to 0.0, and then probe the other side to see the distance traveled. You could then do a SET for half that value in the case of probing for the center of a large ring/part.

[ASPeters]

thanks for reporting, looking into it now
are you using the probing cycles in the probing menu or the F7 Auto Zero (one axis at a time ones) in the part setup menu?

After revisiting this the next morning, it's setting the WCS DRO to the Machine coordinate value when finished probing (no F10/Set was issued afterwards). What I would have expected, would be that once one side is probed, you could set that axis to 0.0 and then probe the other side to see the distance traveled, and then do a SET for half that value.

This is what we managed to replicate this morning and it will be fixed for the next build. The Auto Zero button will automatically set the current axis to the value in the Part Position textbox at the end of the probing cycle.

To accomplish what you are describing, I would recommend doing the auto zero for your first side with 0 for your part position, and then doing a single axis probe for the other side, and then manually setting the axis to the half value as you describe. (In the next build of course)