v5.22 is now available for testing. this is a bug fix only release 12-4-24

[suntravel]

Did some more testing, If I disable the scale, save and enable again it will be ok without 410 Error and without power cycle Acorn 6.

For me this looks like some kind of cache is not cleared after restarting to software...

Uwe

[Allin1Chris]

Utility will be fixed for next revision, and we are currently investigating the scale issue.

Appreciate you bringing these issues to light as always.

[Sword]

I've been having a closer look at the new graphing screen, and I like how it has been evolving. This should be the new RTG screen as well. Just make a cone for representing the tool as it follows the path instead of the sphere (instead of being tied to tool diameter).

A couple of things I've noticed, in the Dimension Menu, the previous and next line buttons don't go to the previous or next line. If you set a line by double clicking or with the Goto Line button, the previous/next buttons seem to just cancel the operation.

If it's possible, the measure/F4 menu option would be much more intuitive and useful if you could click on the first point to set the anchor, and then click for the second point to lock it in, or drag around as it is now for a dynamic measurement. As it is, if you happen to click on Measure, the first point is under where you clicked on the button. Yes, I know that the manual states to place the mouse/cursor at the first point and then hit F4, but that is not very intuitive and most users will likely just click the button instead.

[cnckeith]

I've been having a closer look at the new graphing screen, and I like how it has been evolving. This should be the new RTG screen as well. Just make a cone for representing the tool as it follows the path instead of the sphere (instead of being tied to tool diameter).

A couple of things I've noticed, in the Dimension Menu, the previous and next line buttons don't go to the previous or next line. If you set a line by double clicking or with the Goto Line button, the previous/next buttons seem to just cancel the operation.

If it's possible, the measure/F4 menu option would be much more intuitive and useful if you could click on the first point to set the anchor, and then click for the second point to lock it in, or drag around as it is now for a dynamic measurement. As it is, if you happen to click on Measure, the first point is under where you clicked on the button. Yes, I know that the manual states to place the mouse/cursor at the first point and then hit F4, but that is not very intuitive and most users will likely just click the button instead.

thanks! its and old section of the g code graph menu that has been neglected for sure... i'll write up the improvements.

- i can confirm this one. "A couple of things I've noticed, in the Dimension Menu, the previous and next line buttons don't go to the previous or next line. If you set a line by double clicking or with the Goto Line button, the previous/next buttons seem to just cancel the operation."

- and i totally agree on the F4 measure, not user friendly at all.
this is the way it should work. Press F4 Measure, user clicks on graph location data of that point appears, and then mouse around and see the live position and length data...then if users clicks on second point on the graph it takes a snap shot of both points and the length data.

- and ultimately RTG and G code graph should be the same screen.

[avp]

Hi Keith,
Not sure if you saw this post of mine in the other 5.2 available topic. Anyway here is what I was curious of.

I know at one time there was an interest in doing a little work to the back plot graphics, in order to make the toolpath trail more smooth on slower graphics processors. So you don't get the dots at high feed rates. It that something that will be worked on in the future? I notice mine doesn't follow the toolpath line in circles as well in some situations. The idea mentioned of not tying the tool diameter to the graph is good i think as well.
Bill

[cncsnw]

I have not had time to test this myself.

Does anyone know whether the animated probe status graphic, shown on the various probing cycle screens, has been fixed yet so that it correctly shows the state of a normally-closed probe?

Customer reports that, at least with Oak Mill v5.20, it is still backwards.

[RogDC]

On Acorn I can confirm that probe tip is green until the input closes and probe tip is red in 5.21 probing a bore.

[Allin1Chris]

I have not had time to test this myself.

Does anyone know whether the animated probe status graphic, shown on the various probing cycle screens, has been fixed yet so that it correctly shows the state of a normally-closed probe?

Customer reports that, at least with Oak Mill v5.20, it is still backwards.

I assume this is with P11 set as a Negative ?

The Probe Indicator looks at the input and if it is Red (Open) it is considered un-tripped and when Green (Closed) Tripped. Inverting the input will correct the state of the image.

[cncsnw]

Yes, this is with a negative value in Parameter 11.

Inverting INP769 is possible, but inconvenient

Since using a negative value for Parameter 11 has been documented as a feature for some years now, why not make it work that way?

[cnckeith]

11-19-24

v5.21 rev2 beta is now available for testing.

download here.
www.centroidcnc.com/centroid_diy/downlo ... 11-x64.zip


rev 2 Build notes.

- Added classes VB_[class] to the CentroidAPI to resolve ambiguity between the class and class instance that Visual Basic can't overcome.
- Added bit 4 (add 16) to parameter 113 to hide the Wizard button from the Utility menu (and all other buttons that may launch the wizard)
- Fixed bug where Z Clearance Height in Router Touch Plate menu would not convert between imperial and metric when changing units
- Updated Keyboard Jog Panel legend for Lathe
- Fixed bug where keyboard jogging is enabled, a command is entered and run in MDI, MDI is exited, and the keyboard jog panel is moved resulting in keyboard jogging no longer functioning
- Fixed bug where 410 Scale error would appear upon restart of software
- Lathe G99 moves without an encoder setup will issue a warning message
- Lathe parameter 48 is defaulted to 1 to make G98 the default mode
- Fixed some interactions between Keyboard Jogging and the MDI menu
- Fixed omission of the Scribe menu in the wizard