Centroid Community CNC Support Forum

fyi.. CNC12 v5.24 RC45(RC = release candidate = no beta count down timer) is available for testing.

RC5 https://www.centroidcnc.com/centroid_di ... taller.zip

changes from RC4

- Fixed bug where the Scales menu would incorrectly throw a warning message that the feature is not unlocked, even when an Ultimate license was active on Acorn
- Removed Escape key from the rtg screen
- Removed excess space on the run time graphics screen to allow 5+ axes to fit better
- Fixed 'bug' where fkeys would disappear not showing anything when a keyboard modifier is pressed. This occured because CNC12 attempted to draw alternative keys but found none.




CNC12 v5.24 RC5 DRAFT release notes are here:
https://www.centroidcnc.com/centroid_di ... _notes.pdf

Thumbs up for you hard work done fast. That is a long list in the relase notes of improvements.

I will test it out on the WE after the scales are connected to the new control.

Uwe

suntravel wrote: ↑Thu Jan 16, 2025 4:13 pm Thumbs up for you hard work done fast. That is a long list in the relase notes of improvements.

I will test it out on the WE after the scales are connected to the new control.

Uwe

right on thanks for your testing efforts in advance. we tried to keep v5.24 as a bug fix only release as to not introduce new issues which would take longer to flush out but, we couldn't help ourselves from adding some OEM requested features that were "easy" to do, such as PWM delay and travel past a soft limit M297/8, scale max error for message, and M291 reset MPG offset.

Work on v5.30.0 has begun. it will be the first release with the new numbering scheme with a third decimal point so revisions like v5.30.1, v5.30.2,v5.30.3 etc are be possible.

found an issue with Mill and Router part zero F7 auto zero macro so, making a fix and will put up a rev6 on Monday.

cnckeith wrote: ↑Fri Jan 17, 2025 2:47 pm found an issue with Mill and Router part zero F7 auto zero macro so, making a fix and will put up a rev6 on Monday.

I have just installed 5.23 this new encoder max error feature is perfect.
I got 410 Error with encoder on rotary axis faster than f6000 in 5.22.
This is now ok in 5.23
But now there is a bug with M92/A L1, DRO is counting but the axis will not move.
But if I trip sensor input10 (ForthAxisHomeOk ) with a screwdriver it stops counting.
The axis is working ok otherwise.
Now I have a full closed loop 5 axis
I have had to set velocity to 0 on the rotary encoders to stop overshooting after fast moves.

Uwe

probably I got 410 error in 5.22 on rotary encoders because there I have had velocity set to 0.2 ?

suntravel wrote: ↑Mon Jan 20, 2025 11:47 am

cnckeith wrote: ↑Fri Jan 17, 2025 2:47 pm found an issue with Mill and Router part zero F7 auto zero macro so, making a fix and will put up a rev6 on Monday.

I have just installed 5.23 this new encoder max error feature is perfect.
I got 410 Error with encoder on rotary axis faster than f6000 in 5.22.
This is now ok in 5.23
But now there is a bug with M92/A L1, DRO is counting but the axis will not move.
But if I trip sensor input10 (ForthAxisHomeOk ) with a screwdriver it stops counting.
The axis is working ok otherwise.
Now I have a full closed loop 5 axis
I have had to set velocity to 0 on the rotary encoders to stop overshooting after fast moves.

Uwe

I'm still looking into this but your P423 value shouldn't exceed 255 or go below 0 realistically. I'm not sure how the value -2147483617 will affect your dro.

I have not changed this by hand...

Uwe

Sorry for the short answer. I was busy supporting a German user with TV.

The strange value in P423 was set by the wizard. I set it to 31 like in 5.22 but M92/A L1 will not put out pulse to the driver, only the DRO is counting.

Also after setting home without M92/A L1 in the cncm.hom same thing with M92/A L1 in MDI, DRO is counting but no move on the enabled servo.

Switched back to 5.22, set velocity to 0 for A and C and no 410 error moving the axes at full speed, M92/A L1 is doing what it is supposed to do.

Uwe

suntravel wrote: ↑Mon Jan 20, 2025 4:29 pm Sorry for the short answer. I was busy supporting a German user with TV.

The strange value in P423 was set by the wizard. I set it to 31 like in 5.22 but M92/A L1 will not put out pulse to the driver, only the DRO is counting.

Also after setting home without M92/A L1 in the cncm.hom same thing with M92/A L1 in MDI, DRO is counting but no move on the enabled servo.

Switched back to 5.22, set velocity to 0 for A and C and no 410 error moving the axes at full speed, M92/A L1 is doing what it is supposed to do.

Uwe

This is an odd one, can you try a few tests for us, we are having trouble replicating this behavior.

1. Does the A Axis rotate if M92 /A L1 is performed in MDI?

2. Try Performing M92 /A, without the L1, does A rotate?

3. Does disabling the scale for the A Axis then trying M92 /A L1 move the axis?

4. Just want to confirm that M92 is the only m-code that does not move the A-Axis? What about M91, or other M-Codes? I assume normal G0, G1 moves work and Jogging?