01-20-2025, 06:42 AM (This post was last modified: 01-20-2025, 06:43 AM by farhan.)
i generated the code with motoman_cartesian for cube, here's the code attached below with pulse/degree ratio. actually, I don't understand how to read code with post processor motoman_cartesian. so, I do mastering the robot with move all joint to zero pulse and then moved each joint for certain degree and checked it again. all joint move as desired with no offset.
Are you sure you selected the correct robot in RoboDK? Did you use the ALL.PRM file to upload the pulses/degree ratio? If you can send us the file we can double check.
Also, you can simply choose to use the Motoman Cartesian post processor by right clicking on your program and select Motoman Cartesian. Then you can generate the program again.
for file ALL.PRM, here i attached.
and for generated code with motoman_cartesian. i did generate it and attached it in the previous reply as like u said. because i dont fully understand the generated code with post processor motoman_cartesian and the code cannot import to the pendant, so i just generated it and sent it in the previous replay in file name KTKC.jbi and do the next step, mastering the robot and move each joint to desired angle (as i said in previous reply)
This issue is very strange. I verified your ALL.PRM file from your robot controller and it looks correct, matching your Yaskawa Motoman MH80 robot.
Did you buy the robot controller separately from the robot arm?
Is it possible that the robot controller is configured to work with the Motoman MH80 but the robot arm is a different model?
based on information i got from my supervisor, the robot was bought in a bundle, the robot motoman mh80 include the controller dx100 and not separately.
and question about dx100 configuration, after I search, Yes, it is possible to do that, but such a configuration would cause significant issues in robot operation.
for my dx100, this controller is configured for robot mh80, not another robot. this robot have been used for a couple years in my lab and there is no problem with it.
From my point of view, there is something wrong with the configuration of the controller itself with the robot arm.
I would try just programming a long straight line using Cartesian targets (only with the teach pendant or maybe with the help of RoboDK), and see if/how the robot deviates from the line.