3D Printing Powerpac stops program for no apparent reason
in PowerPacs
Hi,
I will rewrite this post as I pressed enter by mistake.
We have started playing with the very neat 3DP powerpac and I have several questions:
1. Can you understand why the robot stops in my station just when its about to start welding? This seems to happen only when the process is "move". When I set the process to "Arc", it goes perfectly.
2. Previously, my controller setup was not correct (no 3DP option) so the Add In was generating files I could see, like one called Mod_3DP_1 containing a bunch of target in the form of cfidata variables. But now, it generates an encrypted file. So my question is: are we not supposed to see the type of program generated? How as a user am I supposed to check if the program does not contain weird stuff, like missing ArcL commands or what not.
3. I am wondering how the pipeline will look when we want to automate the whole process (no use of the add in, but use of direct RAPID commands to the 3DP module). Will we be able to load gcode then have the 3DP module convert and load the rapid code automatically, is it already possible and I missed some documentation, or...?
Thanks
I will rewrite this post as I pressed enter by mistake.
We have started playing with the very neat 3DP powerpac and I have several questions:
1. Can you understand why the robot stops in my station just when its about to start welding? This seems to happen only when the process is "move". When I set the process to "Arc", it goes perfectly.
2. Previously, my controller setup was not correct (no 3DP option) so the Add In was generating files I could see, like one called Mod_3DP_1 containing a bunch of target in the form of cfidata variables. But now, it generates an encrypted file. So my question is: are we not supposed to see the type of program generated? How as a user am I supposed to check if the program does not contain weird stuff, like missing ArcL commands or what not.
3. I am wondering how the pipeline will look when we want to automate the whole process (no use of the add in, but use of direct RAPID commands to the 3DP module). Will we be able to load gcode then have the 3DP module convert and load the rapid code automatically, is it already possible and I missed some documentation, or...?
Thanks
0
Comments
-
guillaumebatun said:This seems to happen only when the process is "move". When I set the process to "Arc", it goes perfectly.0
-
Well, I have no idea, since I can't see the generated program to see at what line its bugging...0
-
I have the same issue with the ArcL command. The welder stops just as the weld starts. It works okay with MoveL.0
-
If the robot stops when the Arc process is used, the problem is most likely that you use a 'welddata' with weldspeed set to 0.Best regards,
Anders Spaak
ABB Robotics1
Categories
- All Categories
- 5.5K RobotStudio
- 396 UpFeed
- 18 Tutorials
- 13 RobotApps
- 297 PowerPacs
- 405 RobotStudio S4
- 1.8K Developer Tools
- 250 ScreenMaker
- 2.8K Robot Controller
- 316 IRC5
- 61 OmniCore
- 7 RCS (Realistic Controller Simulation)
- 798 RAPID Programming
- AppStudio
- 3 RobotStudio AR Viewer
- 18 Wizard Easy Programming
- 105 Collaborative Robots
- 5 Job listings