Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Johannes @ Robots in Architecture

Pages: [1] 2 3 ... 43
1
Support / Re: Robot origin and BASE coordinate system
« on: October 10, 2018, 06:50:28 PM »
Hello,

Changing the base is currently not supported as we never saw it as a high priority. But I've now also come across a few projects that would have benefited from it.
I'll put it to my todo list!

Best,
Johannes

2
Support / Re: axis limits and galapogus
« on: October 05, 2018, 10:55:36 AM »
Hello Pete,

Nice project!
What I did to make it work was the following: You work in the "back" of the robot, so there really isn't a way to avoid A1 problems. So what I did is set the posture of the robot to "101", which has the robot "flipping over".
However, then the height is more limited due to the limits of A2, so I had to lift up the position of the wooden elements.
Also, when flipped over the reach is less, so I had to adjust the maximum distance of the rail in the settings.

So now the main thing to optimize via Galapagos could be the position of the rods. If you cannot adjust their position "physically" as freely as I did in the digital simulation you could put in constraints, so that e.g. Galapagos moves it only within the range that is possible.
That being said, you're probably quicker doing that by hand.

Best,
Johannes

3
Support / Re: Restrict A1 movement
« on: October 03, 2018, 11:17:48 AM »
Not with a six-axis robot as you do not have the required redundancy.

If you put the robot onto a rail (= 7 axis system), you could e.g. move the rail in a way that there is minimal A1 movement.
With a 6 axis robot you can just lay out the frames in an efficient way that improves reachability and reduces A1 movement. But there is no standard strategy or pattern you could use - that very much depends on what you are using the robot for.

Best,
Johannes

4
Tutorials / Re: Surface Milling Tutorials
« on: October 01, 2018, 11:59:42 AM »
Hello,

I haven't come across any GH plugin that would do that for you in a reliable way, as those strategies are quite complicated and also do not fit that well into the GH way of programming.
Don't get me wrong, it's definitely possible to create milling strategy for individual use cases in GH and you can save great amounts of time through mass customization opposed to CAM software. But there isn't a script that will work well for "all" geometries, like in CAM software where you define the stock, the geometry, set a few parameters and get a working solution.

For "generic" CAM work we usually use Fusion 360, as it has got a nice interface and doesn't cost much (free for EDU). There is a Fusion 360 component in KUKA|prc, you can right-click it to export a postprocessor. Code generated through this PP can then be imported into GH and e.g. combined with your parametric geometry. Note that you need an additional "orientation" point as you get 5-axis G-code out of Fusion, that does not define the rotation around the tool axis!

Best,
Johannes

5
Support / Re: Sanding elipses using a fixed tool
« on: September 28, 2018, 05:12:54 PM »
Hello,

Here's the file in Rhino 5 format. The GH file will complain about a version mismatch but should work as intended!
I actually didn't make it to China, here's a video what the colleagues from IP did: https://vimeo.com/287454509

Best,
Johannes

6
Support / Re: Sanding elipses using a fixed tool
« on: September 24, 2018, 06:40:25 PM »
Hello,

Here's a quick example that should help you get started polishing the wood ellipses.
You see that A6 is running into its limitation, so you may need to set A6 on your robot to infinite rotation, which of course complicated the air supply for the gripper.
Maybe make sure that the robot starts close to the negative limit and then only turns in the positive direction.

Best,
Johannes

7
All the best for the future, Akanksha!

8
General Discussion / Re: WISH : Analysis - Null Axis values if out of range
« on: September 20, 2018, 10:51:19 PM »
Here's an example to illustrate it.
The first PTP and LIN positions are outside of the A5 reach, so that A5 is 1. The next position cannot be reached at all, which is why all axes are at 1. The axis value that you are getting is only the (more or less) maximum extension so that you can see where the unreachable position is located at. I believe that's better than just having the robot disappear when there is no mathematical solution.

Best,
Johannes

9
General Discussion / Re: WISH : Analysis - Null Axis values if out of range
« on: September 20, 2018, 10:02:00 PM »
Hmmm... I wasn't able to replicate that, see the attached screenshot.
It may be that your position is completely out of range, i.e. unreachable, no matter the axis limit? Like e.g. when you put a position 10.000mm away from the robot's center.

Best,
Johannes

10
General Discussion / Re: Virtual Robot for KR150 2000 Series (or Similar)
« on: September 20, 2018, 09:56:01 PM »
Hello,

The "KUKA KR150-240 -2" should be the right one. But there are also additional versions like e.g. KR150L130 that are longer and therefore support less weight.
To be on the safe side, move your robot into its standard home position with A2 at -90 and A3 at 90 and then get its Cartesian position with both tool and base set to 0.
Make a point with those coordinates in Rhino/GH and check if it corresponds to the digital robot.

Best,
Johannes

11
General Discussion / Re: WISH : Analysis - Null Axis values if out of range
« on: September 19, 2018, 07:50:03 PM »
I'll look into the all 0/1, but the ten values refer to a maximum of 10 axes, 6 + 4 external ones.

Best,
Johannes

12
General Discussion / Re: WISH : Analysis - Null Axis values if out of range
« on: September 19, 2018, 06:59:56 PM »
Hello,

For me the problem with NaN or null is that it doesn't tell you if it's exceeding the range in positive or negative direction.
We already provide the Reachability output in the Analysis component - doesn't that do the job?
You could just replace the axis values with NaN based on that output, if you want to.

Best,
Johannes

13
Hello,

Well, I'd say it depends on which direction you want to take, if you want to work at a company, found a startup or do academic research.
I'm guessing that you are outside the EU and US, so it may make sense to enroll for a relevant Master or PhD program, also to acquire skills with robots. There are several countries in Europe with good academic programs and very low or free tuition. Note that there are usually restrictions on how much you are allowed to earn with a student visa.
I don't think your nationality is a problem - you just need to be allowed to work in the EU or UK, you don't need to be from there. I would assume that if you finish an academic program it would be easier to get a work permit in that country, but I'm really not an expert.

Hope that helps a bit!
Best,
Johannes

14
Sounds good, will look into that. I'll need to look into the most understandable CNC terms for it. Probably Rapid for Flyover, Approach and Retract?
Best,
Johannes

15
Support / Re: Collision and Unreachable Position Detection
« on: September 13, 2018, 12:00:55 PM »
Hello,

Can you maybe internalize the plane input? That way it's static geometry and we don't need the custom DLLs.

Best,
Johannes

Pages: [1] 2 3 ... 43