Recent Posts

Pages: [1] 2 3 ... 10
General Discussion / Re: Planning for Kuka purchase
« Last post by Johannes @ Robots in Architecture on March 28, 2017, 09:26:58 AM »

Well, a KR150 - which is probably one of the most common models - has got 2.7m reach fully stretched, so 5.5m are plenty and 4.7 still enough, considering that you generally don't use the robot fully stretched. The height is not much, but should be sufficient, considering these robots are slightly over 2m in their base position. It can stretch to 3.1m, though - so you will either have to be careful, or reduce the workspace of the machine.

An issue to consider is safety: It's convenient to be in the same room as the robot, but outside its reach. So having slightly more room wouldn't be bad, though you can still limit the robot's axis range to get a bit more "save" space.
If you don't need to work all around the robot (note that its base can rotate +/-180, not the full 360) then it probably makes sense to place it 1.5m or so away from the back wall. With the 2.7m of the robot, it would take up 4.2m, so that 1.3m are still left to install a fence, or at least mark the space where the machine cannot reach. Or consider adding a window into the wall, so that you can observe the machine safely. Of course all of that is not official safety advice ;)

KUKA provides convenient 2D drawings of robots in their download section (look into the Archive for older machines) that you can place in your plan, and you can of course also use the downloadable version of KUKA|prc to check reachability.


General Discussion / Re: Planning for Kuka purchase
« Last post by atk on March 27, 2017, 10:15:32 PM »
Hi Johannes,

We are now looking at some used robots.  We found some local resellers and are waiting on quotes.  Most of the used machines are quite a bit bigger and so now my concern is space.  The room we have set aside for the robot arm is 5.5 m x 4.7 m and 2.5 m in height.  How much space do you usually give a robot arm?  I know that's vague, but is there a standard area they recommend based on the size of the robot?



Here's your file back - the Reduce Filesize option was enabled, now I've turned it off. Also, the Safe Plane component needs a plane as the input, not a surface (though it might still work due to GH's creative casting).
Note that your referenced Rhino geometry was missing, so I filled in some placeholders.

Support / Re: Compilation error, - "Component not of this type"
« Last post by hyun.parke on March 27, 2017, 04:19:03 PM »
Okay here's the definition I'm having trouble with.

I kept getting the same error message so I simplified it down, but still getting the same compilation errors.

General Discussion / Re: Possible purchase of a used kuka robot
« Last post by androidrobo on March 27, 2017, 11:51:22 AM »
KUKA Robots Controller KR C2(available here)
Axes: 6
Max. Reach: 2700/2900/2100mm
Max. Load: 150/130/110kg
I know, I unlocked you yesterday!
But you need to download it from the member section if you haven't done so already!

Best, Johannes
Support / Re: Compilation error, - "Component not of this type"
« Last post by hyun.parke on March 27, 2017, 07:55:22 AM »
Thanks Johannes, will try with the reduce filesize unchecked.

By they way I already have a member license from this year!  :D
Sorry, the exact name would be "Reduce Filesize - Skip Redundant Positions" in the settings via Advanced/Code. Without it, there shouldn't be a problem. Or upgrade to the member version, which is at least one year ahead of the trial version.
Support / Re: Compilation error, - "Component not of this type"
« Last post by hyun.parke on March 27, 2017, 06:37:18 AM »
Thanks Johannes for quick reply,

Safe space option? I assume it is related to code generation so I looked up  KUKA PRC settings, but can't find it.

Where should I look for? Or do you mean by safe plane?

It seems that you have used the "Safe Space" option - it seems that it is causing problems (there are blocks with "AX" for some reason), so please deactivate it and it should work just fine. It would be great if you could send me the GH file, then I can try to find the problem. It might also be that this has already been fixed for the member version.

Pages: [1] 2 3 ... 10