Replies: 2 comments 1 reply
-
Sorry for the late reply and thanks for the feedback!
Yeah it requires a bit more space, I'll see if I can shrink it down a bit. Do you mind sharing a screen shot so that I can see the layout you are using?
I am not able to reproduce this problem, they consistently change state in the same way as before. I'll see if I can add another color to better signal if the feature is active.
The old features were practically hard coded for how GRBL deals with overrides. With the latest work I was trying to make an abstraction layer that could work for other controllers such as g2Core. Unfortunately the rapid rate overrides worked completely different than the feed/spindle overrides and was more difficult to implement. When looking at a couple of other senders I decided that the rapid rates overrides could wait. Have you ever used the rapid overrides? |
Beta Was this translation helpful? Give feedback.
-
re. use of Rapid Override - yes, I use it on occasion, usual use case is diagnosing or testing a setup condition. My CNC serves 3 cutting processes (tri-CAM); milling, plasma, and laser. The max XY speeds for the machine electronics vs. mechanical load is 16,000mm/m, however this is only useful when raster scanning during low load cutting with laser and 3D carving of shallow passes due to mechanical resonance in my beefy machine. Most all other cutting processes are either higher load (milling) or are very sensitive to mechanical resonance (laser non-raster and plasma) so I have to dial down the max XY speed to 8,000mm/m, as well as change acceleration; btw-, UGS makes it easy for me to do this via Machine->Firmware Settings->Import menu, I only import the $nn settings that I need to change, so a I keep 2 .settings files readily available for this purpose, one is Fast Max Spd+Accel, the other is Slow.... Sometimes a Rapid Override can help me fine tune a specific table fixture setup or situation in addition to these adjustments. re. Spindle, Mist, and Flood buttons in 2.1.5- Since the override commands don't post to the console log anymore (sorry, another undesired changed IMHO) and the button shades of color don't always change, I don't know the override state at times unless I take other measures like checking the DRO or #G. They may always toggle state, but I'm not getting that visual feedback and often times I'm testing or "dry running" a gcode job in my office on a grbl board with no physical machine attached. There are many use cases for UGS, and perhaps I'm an outlier :( But I love it more than the competition. btw- Run From... feature is awesome, I use it often in plasma cutting where the probability of a torch collision with tipped up metal cutout parts is fairly high, there is never enough physical Z retract clearance height that I can program it seems (not a UGS issue). UGS does an excellent job of back-scanning the gcode to get the modal conditions in the correct state depending on the starting point in the file. Also, I run in G90 absolute mode when plasma cutting, and that gives me confidence that the coordinates are going to be correct. |
Beta Was this translation helpful? Give feedback.
-
constructive feedback...
Beta Was this translation helpful? Give feedback.
All reactions