10-04-2023, 05:11 PM
Right I understand that I can discover the failure at some point later on, but the question I'm asking is *why is roboDK failing to filter each time?* Is there a readout of which of these reasons (close to axis 5 at 0 deg, or arm fully extended, etc) is causing each failure?
In a single program I might have 40 lines that fail, spread out along the program
e.g.
Line 25, Line 456, and Line 3770 failed to filter.
What was the reason for each of those lines failing?
At the moment I'm forced to guess at a solution by adjusting the approach angle, the retract height, the cutting depth, or the transition or any of 100 possible things. Then I have to regenerate, export, and drop it into robodk to find out if it will filter or not.
In a single program I might have 40 lines that fail, spread out along the program
e.g.
Line 25, Line 456, and Line 3770 failed to filter.
What was the reason for each of those lines failing?
At the moment I'm forced to guess at a solution by adjusting the approach angle, the retract height, the cutting depth, or the transition or any of 100 possible things. Then I have to regenerate, export, and drop it into robodk to find out if it will filter or not.
