08-13-2021, 02:32 PM
Hi,
In this case, Run on Robot isn't really an option as you would lose any "fluid motion" capabilities. There's a required handshake between the robot and RoboDK after each move with live connection, the robot needs to stop at each point, which is not suitable for milling applications. So no need to waste time debugging that now.
We need to use the post-processor.
I see that your program is about 40K+ lines, which is too much for the robot memory.
I never encountered that issue on a Mitsubishi, but I did often for other brands, mainly Fanuc.
As a first quickly achievable step, I could find a quick way to split the program every 5000 lines so you could load them on the controller one by one.
Would that work for now?
Jeremy
In this case, Run on Robot isn't really an option as you would lose any "fluid motion" capabilities. There's a required handshake between the robot and RoboDK after each move with live connection, the robot needs to stop at each point, which is not suitable for milling applications. So no need to waste time debugging that now.
We need to use the post-processor.
I see that your program is about 40K+ lines, which is too much for the robot memory.
I never encountered that issue on a Mitsubishi, but I did often for other brands, mainly Fanuc.
As a first quickly achievable step, I could find a quick way to split the program every 5000 lines so you could load them on the controller one by one.
Would that work for now?
Jeremy
Find useful information about RoboDK and its features by visiting ourOnline Documentationand by watching tutorials on ourYoutube Channel.