-
Hello, I'm new to UGS Platform and CNC in general so this may be obvious to some but I'm having difficulty getting design elements to run/execute in the order I would like them to. I have a project which has many (31) design elements. All of the design elements are ordered with the expectation that cutting/milling will take place in the order the design elements are listed. I've re-created many of these elements in a separate files and tested on a scrap piece of wood and they behave as expected but these are essentially 2 or 3 element tests. The problem is when I run the full project the elements get run almost completely out of order. Down to the point where I cut two pockets - one is 2.4mm deep and 36mm square and the second one is inset 2.5mm from two edges of the first and is 27.7mm by 23.9mm and is 5mm deep. When I send this to my 3040 prover CNC the first run had an element order of execution of 3, 4, 1, 2, 29, 30, 27, 28, 15, 16, 14, 13, 18, 17, 31 at which point I aborted because 31 is the last step and cuts the finished part out from the main piece of wood. In a couple of the above instances it cuts air because the the pocket is defined as two parts, a shallower one and a deeper smaller one inside. Unfortunately, the deeper part of the pocket is cut first, then the shallower part is cut afterwards. About 80% of the second shallower pocket cutting is just cutting air and the first pocket makes the CNC rather angry, causing skipping or in one instance cutting so deep it just burns a path. I've tried exporting the full project to gcode and it seems the same silliness regarding order is being carried on in the exported gcode as well. What I find odd is that looking at the ugsd file all of the design elements are listed in exactly the order I would like them to execute in. Why is it re-ordered on export and for run/execution??? Is this a bug in UGS Platform? Is this a setting I'm missing? Is there something else going on? How do I FORCE an order of execution? I'm currently looking at exporting to gcode and manually re-ordering the elements but I can't help but think this is the kind of thing the UGS was designed to do. Am I missing something really fundamental? Thanks in advance for you help and suggestions. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Hi David, When I first built the design feature there was so much travel time between different objects so I thought that it would be a good idea to optimise it with some ordering so that it works on the closest objects first. This turned out to be a bad idea for just the reason you have described. Therefore I changed behaviour in the latest release where it will process the objects in the order defined by the list. Please try the latest version from here: Thanks for the feedback by the way, the designer tool is quite new so if there is something else that grinds your gears please let me know. |
Beta Was this translation helpful? Give feedback.
Hi David,
When I first built the design feature there was so much travel time between different objects so I thought that it would be a good idea to optimise it with some ordering so that it works on the closest objects first. This turned out to be a bad idea for just the reason you have described.
Therefore I changed behaviour in the latest release where it will process the objects in the order defined by the list.
Please try the latest version from here:
https://github.com/winder/Universal-G-Code-Sender/releases/tag/v2.0.15
Thanks for the feedback by the way, the designer tool is quite new so if there is something else that grinds your gears please let me know.