Menu

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.

Show posts Menu

Messages - GOBLIN

#1
General Discussion / Re: Path planning
December 23, 2025, 07:05:06 PM
You know, you're right. The whole problem with open-source stuff generally is that it's someone's massive brainchild that speaks Chinese and I have to teach it how to build a car in one month haha.

Yes we are printing large objects - so actually just having the points loaded sucks up a lot of processing power.
Thank you for the advice!

Also - I've seen there is a grasshopper 2, ever played around with it? Seems to handle text panels horribly!!!
#2
General Discussion / Re: Path planning
December 22, 2025, 07:34:45 PM
Johannes,

It's not so much that I want or need Gcode - I mean the actual toolpath. Making our own custom Gcode flavors over here. Flavortown - Guy fieri style!

Just looking for like a python library with could do things like take a "slice" and do polygonal decomposition, or geodesic slicing, or something along those lines...

Anything to make life more easier. But not excessively easier. Hate that.
#3
General Discussion / Re: Path planning
December 19, 2025, 08:51:16 PM
True. There are definitely some clever ways to approach this... For now, just adjusting position and frame A rotation of the move planes.
I feel so silly for waiting so long to try Galapagos. It is so easy to use!!!

We are in touch. I think we will be wiring payment soon. We've been going back and forth for like 2.5 weeks......

We've been looking for some open-source slicer software - preferably something we can integrate into grasshopper. Python libraries ideally. COMPAS-dev caught our attention. Is there anything you'd recommend checking out?
#4
General Discussion / Re: Path planning
December 18, 2025, 11:28:57 PM
Johannes,

That is not our case - we work in the 3d printing industry.
Maximizing the size of a part put's the workspace through the entire reach bubble.
This generally encourages singularities. There are workarounds, usually sacrificing build volume....

Would there be a way to optimize a print job position/orientation based on the analysis output for singularity risk...?

We are working on getting a license now to have access to the analysis values.
#5
General Discussion / Re: Tool definition inputs
December 18, 2025, 11:21:50 PM
I love you, man. Thank you!
#6
General Discussion / Re: Path planning
December 18, 2025, 07:24:54 PM
I wish KUKA had better performance around singularity regions... Really an issue with the KRC4's on KSS 8.x.x
Ever had any luck navigating around them? Maybe we could switch to joint commands... But that is not ideal in the slightest.

Have you ever used Galapagos or similar to optimize a job location based on singularity outputs...?
#7
General Discussion / Tool definition inputs
December 18, 2025, 07:20:21 PM
Hello KUKA|PRC reps,

Any way the tool definition block can have the location/rotation of the TCP set by sliders?
Would help in some optimizing work I am doing, where a tool is being designed!

- GOBLIN MANS
#8
General Discussion / Path planning
December 10, 2025, 01:28:11 AM
Does KUKA|PRC use ROS?
How the heck does it do path planning to show users what the robot will do?