The difference is it uses cutting paths generated in Mastercam. and THAT does have an effect on the speed. Then I have control over the space between points, the tolerance to the shape, the zone/approximation settings etc. I used the surface generated to create a cutting path. I guess where robotmaster comes in is I wouldn't just use the point cloud as my program points. The speed of the robot, then depends on how you make the program. Going straight from a point cloud to code might work if you keep the robot posture the same (3-axis router style) and stay in the middle of the work envelope. it does this while correctly maintaining configurations (wrist/elbow/base).
Robotmaster doesn't optimize the running speed - but what it does do is optimizes the robot orientation, changes in orientation - and changes the robot posture/orientation to avoid collisions, joint limits, etc. It was originally a point cloud with a surface wrapped on it - not sure which scanning software did it, most likely polyworks or geomagic, I just got the file as an IGES with mesh surface. Just seeing this now - I work as an AE for Robotmaster, and the original skull file came from me.
0 kommentar(er)
