Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Fusion 360 and RoboDK Issues

#1
Hi All,

I have created working tool paths in Fusion 360 , and am having a lot of trouble getting them to work properly in RoboDK.  I'm actually not even sure how to ask questions at this point because it seems so complicated.  Are there any videos on the net that go through, in detail, the process of taking a milling program from Fusion and correctly importing it into RoboDK ... and actually having it work?  

I have created a program for a wood part I need to mill on my Kuka KR210.  It consists of a roughing phase and a finishing phase.  There is a tool change in the middle.  When I import the program into RoboDK, it only imports the roughing pass.  I don't know if it is going to pick up the correct tool at the beginning.  I don't know if it will change tools in the middle.  I don't know how to get it to load the finishing pass.  When I try to "Generate Robot Program" it tells me that Python is not configured properly ... and then it says to "Set the path to the Python interpreter in Tools-Options-Python".  There is no "Options" option in the "Tools" pulldown ... so how is this even set?  And what is Python anyway?  

Sorry to drop a lot on here.  I've got the robot up and running, and have been milling parts for a while, but I've been farming out the program creation.  I have all the software to create the programs myself at this point, but the educational resources at RoboDK are non existent, so I'm not sure where to start.  

Thanks for your time and consideration.

Scott Baker
#2
I just have to ask since you ask about tools from Fusion360.
Do you have a automatic tool changer on your robot?

I do not have one and is looking into setting up one.
I use the correct tool(size) withinin fusion but I set actual tool number inside Robodk with the correct tcp and corresponding tool number from the robot. What you import from F360 is mostly points in space and not a model and/or size of tool. But you can get a tool number, but I consider that only useful if you have a automatic tool changer. Hence the question and I want to know about your setup if you have one...

Shift + O to get to option.
#3
(11-03-2024, 08:00 PM)Borgis1 Wrote: I just have to ask since you ask about tools from Fusion360.
Do you have a automatic tool changer on your robot?

I do not have one and is looking into setting up one.
I use the correct tool(size) withinin fusion but I set actual tool number inside Robodk with the correct tcp and corresponding tool number from the robot. What you import from F360 is mostly points in space and not a model and/or size of tool. But you can get a tool number, but I consider that only useful if you have a automatic tool changer. Hence the question and I want to know about your setup if you have one...

Shift + O to get to option.

Hi,

Yes I do have an automatic tool changer.  The robot and software was all set up by an integrator friend of mine, so all the tools have been entered into Fusion 360, RoboDK and the robot itself.  Everything is calibrated ... I just need to figure out how to use the software.  Fusion 360 has very good support ... I can send them a question and they send me back a video that explains exactly how to do whatever I was having trouble with.  RoboDK does not seem to have such a thing ... at least not what I can find ... I just get sent to the forum.  
#4
I watched a lot of videos by Jeremy. Helped me to get a grasp on the logic. I also had a lot of help from the F360 forum when they were up an coming. Now a days, they seem not so hungry anymore, as they have stopped responding on user wishes on the forums and rather concentrate on adding weight to the Fusion family by having it include everything they can buy off the shelf instead of taking care of the existing userbase, If autodesk could buy excel and a rocket launcher to include, they would. What they do not want to do is fixing their own PP for cutting machines. enough rant.
Back to topic (ish). I suggest the tutorials from Jeremy on youtube. Started me at least. He had a video about the "Program events" within the import gcode settings where you would find and implement how to make a program react to tool changes.
#5
Quote:When I try to "Generate Robot Program" it tells me that Python is not configured properly ... and then it says to "Set the path to the Python interpreter in Tools-Options-Python".  There is no "Options" option in the "Tools" pulldown ... so how is this even set?  And what is Python anyway?  

Please make sure that you are using the latest version of RoboDK.
The embedded Python interpreter is used to create programs.
The interpreter selection is available on the Python tab (Tools - Options - Python).

ptn.png   

Tool change operations are recognized when importing NC code.
As Borgis mentioned, you can use the ‘Program Events’ of the Machining project:

png.png   

The corresponding program calls will be created with the instrument number as an argument.

Next, you have several options:

- link these program calls to the tool change programs that exist on the robot controller
- link these program calls to tool change programs created with RoboDK
- Modify the postprocessor code to add a specific tool change procedure

You can find the Machining project description at the following link:
https://robodk.com/doc/en/Robot-Machinin...ingProject
#6
(11-04-2024, 09:43 AM)Sergei Wrote:
Quote:When I try to "Generate Robot Program" it tells me that Python is not configured properly ... and then it says to "Set the path to the Python interpreter in Tools-Options-Python".  There is no "Options" option in the "Tools" pulldown ... so how is this even set?  And what is Python anyway?  

Please make sure that you are using the latest version of RoboDK.  I am yes.  It is a brand new license. 
The embedded Python interpreter is used to create programs.
The interpreter selection is available on the Python tab (Tools - Options - Python).
I know where the Python thing is, but I have no idea what it is, what it does, and what to change.  Pressing buttons and picking different things within that menu does nothing ... nothing changes. 
Tool change operations are recognized when importing NC code.
As Borgis mentioned, you can use the ‘Program Events’ of the Machining project:
I looked at that too, but it makes no sense.  I'm not sure what I'm looking at.  
The corresponding program calls will be created with the instrument number as an argument.
Next, you have several options:
- link these program calls to the tool change programs that exist on the robot controller.
Sorry I have no idea what this means.

- link these program calls to tool change programs created with RoboDK.
Ha Ha, nope have no idea what this is.  
- Modify the postprocessor code to add a specific tool change procedure
Ugh, I definitely have no idea how to do this. :-(
You can find the Machining project description at the following link:
This is, unfortunately too basic.  It explains everything I already know how to do but none of the detailed things. 
https://robodk.com/doc/en/Robot-Machining.html#MachiningProject
  




Users browsing this thread:
3 Guest(s)