After testing RoboDK with the Niryo I now got a Mitsubishi SCARA 4 axis robot. I was able to connect to the robot and also to read out the joint positions of the robot. Also it is possible to do exact 1 joint movement. Then the system runs into some connection problems. See attached protocol log. I also try to uncompile the driver /v37/apimitsubishi.pyc. Unfortunately the uncompiled version did not work. robot_msg is not initialised and after init robot_msg i get a robot movement error. Could you help me to get the driver work for 4 axis SCARA or to send me the source code of this driver?
BTW, Maybe you have the right robot as model for RoboDK?
it seems that the Problem occurs by the answer of the Robot Controller. The response of JPOSF is for example QoKJ1;-34.740;J2;4.390;J3;379.340;J4;62.250;;****,****;5;0.00;00000000. The problem seems to be "****,****"
For joint moving i have a quick and dirty solution, but now i faced with the problem of linear movements. Doing a linear movement results only in "Sending command..." in protocol window.
(see attached log line 106-108)
BTW, is there a more detailed debug output of roboDK possible by a parameter or somthing else?
Thank you for your tip to activate he developer mode. With the driver and the custom curve follow skript I noticed that the robot does not move continuously as in the simulation, but stops at every point. How do I get the robot to move continuously and evenly with the help of the RoboDK driver?
If you are using the driver, you can't avoid the stops at every point. This is because RoboDK and the controller communicate on a "per command" basis. In other words, RoboDK stream the motion commands one at a time, waiting for the confirmation of the robot before sending another one.
If you want continuous motion, you need to use the post-processor and generate the robot program.
This way the robot will have access to the complete program and can execute fluid motions.
Hello, I verified using the mitsubishi simulator that you can still retrieve the position of the robot via the driver, you should be able to use our api to retrieve the robot position in real time after the driver is connected even while the robot is running.
MonitorJointsReal.py Located inside "C:\RoboDK\Library\Macros" by default is an example of using the driver to update the position of the robot in the simulation real time.
It worked on the simulation, it would be nice if you could confirm it also works on real robots.
I will test it and give feedback. However, I have 2 weeks vacation and won't be back in the office until the end of the month. I hope that the dongle has been ordered by our company by then, so that I no longer have to use the extended test version.