Recent posts
#91
General Discussion / Re: EOAT KITS FOR 3D PRINTING?
Last post by happytriger2000 - January 18, 2024, 02:31:27 PM@MarK,
I'm also planning on doing 3d printing with robots, may be these links might help:
* https://massivedimension.com/products/mdpe10-massive-dimension-direct-print-particle-extruder
* https://dyzedesign.com/pulsar-pellet-extruder/
* https://ceadgroup.com/wp-content/uploads/2019/09/FOLDER-RE.pdf
* https://www.cosineadditive.com/en/extruders
* https://rev3rd.com/pellet-extruders/
cheerio!
I'm also planning on doing 3d printing with robots, may be these links might help:
* https://massivedimension.com/products/mdpe10-massive-dimension-direct-print-particle-extruder
* https://dyzedesign.com/pulsar-pellet-extruder/
* https://ceadgroup.com/wp-content/uploads/2019/09/FOLDER-RE.pdf
* https://www.cosineadditive.com/en/extruders
* https://rev3rd.com/pellet-extruders/
cheerio!
#92
General Discussion / Re: rotational_axis
Last post by Johannes @ Robots in Architecture - January 17, 2024, 03:51:33 PMHello,
The first step is to get the root point of your turntable. Currently, it is set to 1500,0,0 (via right-clicking the turntable component). I guess that is not right.
Then when you calibrate the Offset Base, you will get values that are in relation to your positioner. So if the base origin is 10cm above the positioner, you will get something like 0,0,100 for XYZ.
Your current values seem a bit strange, because they have got a 2m offset in X and the other values quite low. Are the robot and the positioner more or less on a shared plane in Z?
In any case, unless you are working with a HUGE positioner, a base with 2000mm distance from the root point of the positioner is not really feasible, the values will be much lower.
Hope that helps with troubleshooting!
Best,
Johannes
The first step is to get the root point of your turntable. Currently, it is set to 1500,0,0 (via right-clicking the turntable component). I guess that is not right.
Then when you calibrate the Offset Base, you will get values that are in relation to your positioner. So if the base origin is 10cm above the positioner, you will get something like 0,0,100 for XYZ.
Your current values seem a bit strange, because they have got a 2m offset in X and the other values quite low. Are the robot and the positioner more or less on a shared plane in Z?
In any case, unless you are working with a HUGE positioner, a base with 2000mm distance from the root point of the positioner is not really feasible, the values will be much lower.
Hope that helps with troubleshooting!
Best,
Johannes
#93
General Discussion / Re: rotational_axis
Last post by Moh.Yazdan - January 17, 2024, 03:37:09 PMHello Johannes,
Thank you very much for your response, and I'm sorry for replying late. I was waiting for the new robot to be installed to measure the XYZABC.
I measured XYZABC from the base and entered the resulting values with the same base number in KUKA|prc. The values are as follows:
X= 2011.78, Y= 221.90, Z= -34.91, A= -0.08, B= -0.03, C= 179.99.
However, in the .src file, X has negative values (X= -1940), and when I try to run the simulation, I get the following error: "Unreachable point Software end switch-A5." Attached, you will find my simulation in Grasshopper and photos of the TCP/Base coordinates, as well as the mentioned error.
Could you please check the simulation file to see where I went wrong?
It would be very kind of you to assist.
Thank you,
Mohammad
Thank you very much for your response, and I'm sorry for replying late. I was waiting for the new robot to be installed to measure the XYZABC.
I measured XYZABC from the base and entered the resulting values with the same base number in KUKA|prc. The values are as follows:
X= 2011.78, Y= 221.90, Z= -34.91, A= -0.08, B= -0.03, C= 179.99.
However, in the .src file, X has negative values (X= -1940), and when I try to run the simulation, I get the following error: "Unreachable point Software end switch-A5." Attached, you will find my simulation in Grasshopper and photos of the TCP/Base coordinates, as well as the mentioned error.
Could you please check the simulation file to see where I went wrong?
It would be very kind of you to assist.
Thank you,
Mohammad
#94
General Discussion / Re: robot milling
Last post by mortezasarv - January 17, 2024, 11:50:37 AMThank you very much
#95
Support / Re: Method for sending digital...
Last post by Studio3P - January 16, 2024, 09:57:29 PMThank you! I just took a look under the hood of the script and this seems to point in right the direction. Many Thanks!
#96
General Discussion / Re: robot milling
Last post by Johannes @ Robots in Architecture - January 16, 2024, 05:36:27 PMBy default, KUKA|prc generates a new file when the input changes. You can right-click the KUKA|prc Core component and enable the option to expose the file name. You now get an extra input for the file name. This could now include the current date or for example an incrementing number.
Just be aware that the file name is also used for the internal project name, so don't use any empty space, special characters or a number at the start.
So now you change the start position in Grasshopper and get a new file to run on the robot.
Is that what you are looking for?
Best,
Johannes
Just be aware that the file name is also used for the internal project name, so don't use any empty space, special characters or a number at the start.
So now you change the start position in Grasshopper and get a new file to run on the robot.
Is that what you are looking for?
Best,
Johannes
#97
General Discussion / Re: robot milling
Last post by mortezasarv - January 16, 2024, 04:44:04 PMI want to change the starting position of the toolpath. it is OK for me to manually copy a file to the robot
#98
General Discussion / Re: robot milling
Last post by Johannes @ Robots in Architecture - January 16, 2024, 02:04:47 PMSorry, it's still not clear to me what you want. Do you only want to change the starting position of the toolpath or the entire toolpath?
Either is easy to do in Grasshopper/KUKA|prc, the question is how to get it to the robot. Are you using mxAutomation? Or is it OK for you to manually copy a file to the robot?
Best,
Johannes
Either is easy to do in Grasshopper/KUKA|prc, the question is how to get it to the robot. Are you using mxAutomation? Or is it OK for you to manually copy a file to the robot?
Best,
Johannes
#99
Support / Re: Roboteam example
Last post by Johannes @ Robots in Architecture - January 16, 2024, 02:02:01 PMHello,
Sometimes it needs a re-compute in Grasshopper, do that and then move the slider.
You can change the root point of the robot via the Custom Robot component. Plug it in as a reference and change the root point.
What is not supported is that when one robot moves, the second robot is constrained to it, i.e. it follows its movement.
Best,
Johannes
Sometimes it needs a re-compute in Grasshopper, do that and then move the slider.
You can change the root point of the robot via the Custom Robot component. Plug it in as a reference and change the root point.
What is not supported is that when one robot moves, the second robot is constrained to it, i.e. it follows its movement.
Best,
Johannes
#100
General Discussion / Re: Boolean output for robot m...
Last post by Johannes @ Robots in Architecture - January 16, 2024, 01:59:25 PMHello,
That's not a problem, should be done in just a few lines of code in the sps.sub - the program that runs cyclically in the background. Something like:
Of course I haven't tested it. Consider making a backup before changing important files like the sps.sub. Or run an additional SUB program if your robot supports it!
Best,
Johannes
That's not a problem, should be done in just a few lines of code in the sps.sub - the program that runs cyclically in the background. Something like:
Code Select
IF $VEL_ACT > 0.0 THEN
$OUT[1] = TRUE
ELSE
$OUT[1] = FALSE
ENDIF
Of course I haven't tested it. Consider making a backup before changing important files like the sps.sub. Or run an additional SUB program if your robot supports it!
Best,
Johannes