KUKA|prc - parametric robot control for Grasshopper > Support

kuka.cnc code generation

(1/3) > >>

gergole:
Hello. I'm Gergő from the Kyoto Institute of Technology.

I'm using KUKA|prc 2022-01-21 and would like to generate a KUKA.cnc code for my KR22-R1610 robotic arm with a KR-C4 controller on KSS8.3.36.

I need to mill a complex geometry, so I have generated a toolpath in Fusion360.
Since the KRL code for even the first roughing was around 20 MB, I met the limits of the physical memory of the controller, so I would like to use the KUKA.cnc already integrated into our system.

However, when choosing the KUKA.cnc (beta)code option, no file is generated, even though the computer's processor has a high load for several seconds.

I left the settings at default, as you can see in the screen capture.

Am I missing something?

Johannes @ Robots in Architecture:
Hello Gergo,

Please note that KUKA.CNC creates a file that ends with *.nc and not *.src
So I would first check if you get an SRC file written, and if that is the case, change the code generation to KUKA.CNC and see if a NC file is written.

That being said, KUKA.CNC is complicated to integrate and leaves a lot of options to the integrator - so test it carefully and slowly.

Best,
Johannes

gergole:
Dear Johannes,

Thank you for your prompt reply.
I checked all kinds of options about the file generation (KRL/SUNRISE/CAMrob), which all generate files,
but KUKA.cnc option results in no file in the designated folder. I also checked the default location (desktop),
but there was neither any code generated there.

Could it be, that a certain component or setting is blocking the generation?

Gergő

Johannes @ Robots in Architecture:
Dear Gergo,

I'll send you an updated version via eMail to try out, just to see if it's your version of KUKA|prc or something else!

Best,
Johannes

gergole:
Dear Johannes,

Thank you for your mail.
I updated KUKA|prc, but it didn't solve the problem.

I tried to play around with the toolpath by splitting it up, and it turned out, that the NC code can be generated up until line 1799, after which it stops operating. Up until line 1799, there are only LIN movements,  but Line 1800 would be a CIR command: could this be a cause?

Bests,

Gergő

Navigation

[0] Message Index

[#] Next page

Go to full version