We use cookies to personalize content, interact with our analytics companies, advertising networks and cooperatives, and demographic companies, provide social media features, and to analyze our traffic. Our social media, advertising and analytics partners may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services. Learn more.
I finally got around to actually using the new UGS for cutting instead of just loading and seeing features and my 3 axis probe script (from Charley) which has worked flawlessly has stopped working.
UGS senses the file is done (actually says -2 rows remaining) but it doesn’t trigger the usual prompt saying done or change the UI to be usable.
Happens on both Platform and Classic nightly builds.
There isn’t a M30 command at the end but it’s never posed a problem. Even the Easel generated Gcode I use doesn’t have a M30 or similar command. Is that maybe why?
In minnesota, we have tons of snow, tornadoes, linux, if you can figure it out, and unlimited updates to win-10. I guess we have it all! geez i love it here!
Hey Charley, those large files were definitely an issue with UGS 1.0.9. Thanks to many laser users who reported the issue and a lot of refactoring, it’s been solved in the nightly build since January last year. If you’re feeling adventurous one day I invite you to give UGS another go. I do my best to make UGS as easy as possible for novices to get into hobby CNC. With UGS platform I’m starting to build some of the more advanced features that a power user might want.
Hey that’s great news. I wasn’t aware that it had been resolved. I used UGS exclusively for a long time until I started doing lithophanes that had such large file sizes. My hat’s off to you guys for making it available to users. One thing that would make it much more user friendly would be the addition of a set of buttons that will send the machine to Work Position zero. Many users have such terrible problems with limit switches that they don’t bother with them any longer and don’t home their machines, (myself included). When they click the Return to Zero button it is sending the machine crashing in to rails, especially after zeroing with a three axis touch plate. The only way to get your bit to X Y Z zero after zeroing with a 3 axis touch plate like the Triquetra Touch Plate that I have sold a ton of, is to either manually jog to 0 0 0, type in the actual distance to travel and jog that direction one axis at a time, or enter g-code commands in the macro tabs to tell the machine to go to work zero for each axis.
I’m afraid of cold and snow… Brrrrr.