Recent Posts

Pages: 1 [2] 3 4 ... 10
General Discussion / Re: Programming Issue: Kuka Robot difers form Controller
« Last post by donjorges on July 09, 2018, 11:49:11 AM »
Thanks Johannes, you´ve been amazing...

I contacted Kuka (luckily I was around a Kuka Headquater) and they were able to send me an installation cd for the roboter, and now I´m asking them for a lot of things, and they are very collaborative.
So I hope next questions from me will be about the PRC, instead of the roboter...jejejeje

Thanks a million, bro!..
Then it's probably best to reinstall the KUKA software, and then to restore to the last running WorkVisual project.
If you don't have a backup, try to connect to the robot from WorkVisual and download the projects you need.

Support / Re: No memory available > Robot is not working
« Last post by hadi on July 06, 2018, 11:23:34 PM »
Hello Johannes,

Thank you for your prompt reply! When I tried to activate the base project it showed me this error "an error occurred during activation. Unkown error on controller <WINODWS-P1VLBNC (localhost)>: Cross3ADS#2:Abort"

Please see screenshot attached.



My recommendation would be to try to load a previous project. Either activate the current one if you have it saved on your PC via WorkVisual, or alternatively go into the Expert user group and click the button with the cogwheel, somewhere on the left border, towards the middle. Activate a previous project from there.

Ideally everything will work again, but you may lose some changes, e.g. if you configured an additional Beckhoff IO module. This might also prevent the robot from moving, if it is looking for an IO module but cannot find it.

I once accidentally tried to copy a 40MB file and also got the error message - no further problems, though.


Support / No memory available > Robot is not working
« Last post by hadi on July 06, 2018, 09:07:24 PM »
Hello all,

I have a KR10 R1100 with a compact KRC 4 controller. Yesterday we sent a script that was 1.1 mg in size and the teach pendant showed an error saying that there's no available memory. So we deleted few src files to clean up some space.

After deleting few scripts we weren't able to delete any more. So we did a cold reboot. The src files after that started showing up with TXT icons but with an src extension.

The robot at the moment is not moving, and I can't even jog it on any mode. Even if we switch it to T2 mode it still shows up as if it is on T1.

Any help is much appreciated!
Hello Nick,

The postprocessors for SprutCAM and Fusion can be generated by right-clicking the GH components in the member version of PRC; it's not included with SprutCAM by default!

General Discussion / Re: Importing G-code from MasterCam and coverting it to PRC
« Last post by fr1670 on July 06, 2018, 04:45:28 PM »

Thank you for the response. In spurt cam what post processors setting do you have to use for KUKA PRC?

Support / Re: Horizontal turn table
« Last post by pak on July 06, 2018, 11:24:33 AM »
Hello Johannes,

Thank you for the custom file, it does work great !


We worked a lot with SprutCAM before, more recently for teaching and milling projects that are not too complicated we rely increasingly on Autodesk Fusion 360, as our students use it quite often for modelling.
So for both of these programs there are ways to import G-code into KUKA|prc.
However they work with custom postprocessors, so it's probably not that easy to take G-code from another software like MasterCAM.

I do not have access to MasterCAM at the moment, so I cannot really develop a workflow for it. I believe the default robot solution for MasterCAM would be RobotMaster, but of course it does not have all the capabilities of Grasshopper environment.

If you know how to write MasterCAM postprocessors yourself, you may be able to write G-code that looks similar to the code coming out of SprutCAM, though. So you would be able to use that component to get toolpaths from MasterCAM.

Support / Re: Horizontal turn table
« Last post by Johannes @ Robots in Architecture on July 05, 2018, 11:03:33 PM »

I just realized that you are referring to the automatic solver. It seems to be causing issues in that case, the rotation is going in the wrong direction.
I've replicated what the solver does in the attached, modified file, which now works fine in the simulation!

Pages: 1 [2] 3 4 ... 10