Messages

Hello,

I'm sorry for the confusion, I will word that differently in the next release.
The KUKA|prc message refers to the toolpath reduction inputs, where you can additionally reduce the complexity of a toolpath, which in my experience doesn't work so great in Fusion.
So you can leave the Fusion settings at the default!

Tolerances of 0.1mm and less will also lead to HUGE files. Always consider that your robot is probably less accurate than 0.1mm, at least when you calibrate the tool manually it's VERY hard to get better accuracy than 0.15mm. The same applies to the mechanics of the robot.

Best,
Johannes

Hello,

Are you sure that you installed the software?
You should have a KUKA|prc V2 tab in the upper row of the GH window.
Is it there?

The screenshot was tiny, so I couldn't see much.

Best,
Johannes

Hello,

What would be your questions?

Best,
Johannes

I have got a few more basic tutorials, send me an eMail and I can forward them!
Best,
Johannes

We're very much looking forward to the document!
Hopefully we can make it in some way worth your while!

All the best,
Johannes

Hello,

You basically just need to do two transformations.
Attached to my post is an example!

Best,
Johannes

Hello,

I'll see if I can make a transformation component for all KUKA|prc movements, but it will take a while!

Best,
Johannes

Hello Jason,

I actually recently integrated CIR and SPL movements into Sunrise, the "problem" is that it only works with the next release of KUKA|prc.
If the CIR movements are a priority for you, please send me an eMail and I'll send you a link to the new release.

Best,
Johannes

Hello,

I see what you mean, maybe I can make it optional! Will look into it!

Best,
Johannes

P.S.: Relative axis values are already working, that was a great suggestion!

Hello,

Here is an example how to use it. The Toolaxis Offset component is really one is use like every day, so if something is making issues, it must be a very exotic coincidence. As with all things involving computers, it's not impossible, so I'm not doubting you, I'm just saying that I haven't come across that problem before.

Please send me an example if you run into disappearing offsets!

Best,
Johannes

Not currently, but in the next version it might be an option for the Analysis output. It's already working, but not exposed in the UI.

Best,
Johannes

Yes, I just added the line that generates the text for the end movement, I must have overlooked it before.
But it's just a cosmetic change, all the data was of course there.

Best,
Johannes

Hello,

If you are constantly getting problems with singularities, it might be worth it to slightly change your setup, i.e. adjust the tool angle, and often simply lowering or lifting your table by 10cm makes a big difference.
I'll look into the file you sent me before, haven't had the time yet.

Best,
Johannes

Might be, but not sure if on the GH or PRC side.
Please send me the file (gladly just the parts relevant to the problem) so I can take a look!

Thanks,
Johannes

Hello,

That was developed under the assumption that if you do a retract movement, you want to move in an accurate way.
Also, if you have a PTP movement you need to define a status value, and if you are unlucky the status works for one command, but not for the offset one. Then you would need to include an extra status input and at some point you have 20 inputs that nobody understands.
However it's easy to implement by yourself - that's the nice thing about Grasshopper!

I've attached a cluster that more or less duplicates what the toolaxis offset component is doing. Hope that helps!

Best,
Johannes