Pratt GAUD Robotics Spring 2015

Welcome to the show.

Replies to This Discussion

Permalink Reply by Milad Showkatbakhsh on February 9, 2015 at 12:08pm

Hello Brian

So When I installed HAL , This error pops up every time that I open Grasshopper

Permalink Reply by Thibault Schwartz on February 9, 2015 at 12:16pm

Hi Milad,

HAL 5.3 will be released in the next few days (probably tomorrow night, we had to report it due to minor bugs to be fixed). It is compiled against GH0.9.0076 so you won't have this error anymore. This message is due to a SDK breakage that has not been fixed by a new GH release in the meantime.

Best,

Thibault

Permalink Reply by Milad Showkatbakhsh on February 9, 2015 at 12:22pm

Thank you for your quick respond . So I'll wait until the new one is coming out

Permalink Reply by Milad Showkatbakhsh on February 10, 2015 at 5:51pm

Hello

I have problem with Human plugin in grasshopper, What should I put in the " name " input of the " Hatch component " ? Rhino hatch names ? like Plus ? it seems it doesnt work with them . I really appreciate it in advance

Permalink Reply by Milad Showkatbakhsh on February 10, 2015 at 5:57pm

Hello

Attachments:

Capture.PNG, 241 KB

Permalink Reply by Andrew Heumann on February 10, 2015 at 5:59pm

This is due to a recent change in RhinoCommon - you will have to add a hatch to the document once before you can call it in the hatch component. So just fill a rectangle in your Rhino document with the desired hatch once then delete it - now the Human CreateHatch component will let you create that hatch.

Permalink Reply by Milad Showkatbakhsh on February 10, 2015 at 6:05pm

thank you it works

Permalink Reply by Milad Showkatbakhsh on February 24, 2015 at 2:33pm

So I just installed the new HAL , but when I open my file it says the following node is old . When I try to replace it with the new node , the new node does not have the coordinate input

Attachments:

lll.PNG, 177 KB

Permalink Reply by Thibault Schwartz on February 24, 2015 at 2:39pm

That's because you can now set reference axis systems in the toolpath ;)

Permalink Reply by Brian Ringley on February 25, 2015 at 11:49am

Thanks Thibault. Milad/all - we're going to stick with our current version through the robotic drawing project and then upgrade to the new version when we start the shell panel manufacturing process. This way we can avoid any confusion in the midst of production.

Permalink Reply by Denise Tang on February 25, 2015 at 12:49pm

Hi Brian,

I am having some trouble with the previewing robot movement preview for my drawing.

While it seems like all the appropriate information is going though, I keep getting an error when I try to preview the robot movement simulation. Can I still run the robot even with this particular error?

And a screen shot is attached.

Please let me know what you think!

Attachments:

Permalink Reply by Brian Ringley on February 25, 2015 at 1:27pm

Yes you can still run the robot.

The issue here is that the Expression component doesn't like empty character spaces in its input variable names - by changing the variable names to a simple x and y and re-connecting the input wires the error will be resolved.

The point of this expression component is to supply a target index to the HAL Mode Switch component from a 0 to 1 slider. This way a single slider can be used to control both HAL Preview Modes (0 to 1 normalized toolpath vs target indices).

By using the Stream Filter component the Mode Value List will simultaneously change the Mode and tSelect inputs, hopefully making your life a little easier.

Of course, the point of the target index preview mode is to supply specific indices (not necessarily having anything to do with slider control), and there is an index output on the Mode Switch component that displays the target index that corresponds with the normalized range, so, as a bit of a disclaimer, this might not be as useful as I'd like it to be!