+- RoboDK Forum (//www.sinclairbody.com/forum)
+-- Forum: RoboDK (EN) (//www.sinclairbody.com/forum/Forum-RoboDK-EN)
+ - - -论坛:通用RoboDK问题(//www.sinclairbody.com/forum/Forum-General-questions-about-RoboDK)
+--- Thread: Fusion360 Drill Path Heights Change in RoboDK (/Thread-Fusion360-Drill-Path-Heights-Change-in-RoboDK)
Fusion360 Drill Path Heights Change in RoboDK-Koen-01-07-2021
Hello,
Could you help me with a question regarding the Load CAM Project in RoboDK from Fusion360 feature?
I'm trying to load a CAM toolpath from Fusion360 into RoboDK. It drills 12 holes at two differents heights. However when I load the CAM path into RoboDK using the Fusion360 Plugin the Z heights in the RoboDK path differ from those in the Fusion360 path.
The path in fusion360 is shown in the first image attached. Here it can be seen that all movement actions happen at the same heights and the drilling depths differ for a few different holes.
The RoboDK path is shown in the second image, here it can be seen that for the deeper holes both the movement height and the hole height are positioned lower then they should be. To move to the undeep holes the robot moves diagonally upwards. I've tried using a smalle offset correction to move the entire path upwards but then the undeep holes are not drilled anymore.
Is there a way to fix these paths so they stay level?
In addition to the two images I've also attached the RoboDK workstation, and a snapshot of the version and license info to this post.
To export the path I've used the method described in:
https://www.youtube.com/watch?v=HaMICaEjaAk&feature=emb_logo
(So by using the Load CAM Project button)
I've already checked that the origin used in fusion360 manufacturing and the reference frame for the part match.
Thanks in advance for your help!
RE: Fusion360 Drill Path Heights Change in RoboDK-Jeremy-01-07-2021
Hi Koen,
Do you have the Fusion file?
It's indeed strange and I would like to investigate further.
Jeremy
RE: Fusion360 Drill Path Heights Change in RoboDK-Koen-01-12-2021
Hi Jeremy,
Thanks for the response, you'll find the fusion360 attached to this post. It has a dependency on another part and I'm not sure how well fusion360 exports handle dependencies so I've attached that as well.
Btw I also tested with fanuc G-Code export and it showed similar issues, maybe at has something to do with the way G81 'Drilling Cycle' is handled?