[jheimann]

I have a uFactory 850 robot arm and downloaded the uFactory 850 robot from the RoboDK library.  I added the robot to my station and tried to connect to my robot, but it failed with an error 'Cannot start c:/RoboDK/api/robot/uFactoryDriver.exe"  A picture of the error is attached.  It would seem that the robot in your library is missing a key file.  Can this be fixed in the library so that I can connect to my robot?

Thanks!

[Albert]

Is this uFactory robot part of the xArm series?

Have you tried using the xArmDriver?

What issues do you see?

[jheimann]

I switched to the XarmDriver.py and that seems to work for the robot, but sometimes it hangs up when running on the robot.  The connection status is yellow and says "working" but nothing is moving and RoboDK becomes unresponsive.  The only way out of this is to kill the process (close RoboDK) and start over.  Not sure if this is driver related or not, but it happens sporadically, but often enough to be a real bother.

[Albert]

Thank you for letting us know. Can you share the Connection log after the driver remains stuck?

For your information, you can double click on disconnect and it should kill the driver process only. So you don't need to restart RoboDK.

[jheimann]

Where do I find the connection log?  When RoboDK hangs up, I can't click on anything.  The screen whitens up and I get program is not responding, do I want to wait for it or close it.  Attached is a screen shot of it being hung.  You can see the instruction it is hung at.  I will say that the move that was being executed, did execute on the robot, but the software does not reflect the move yet.  Also attached is the RDK file. 

This happens every time I try and run the program.  Not sure what to do here... any help would be appreciated.

[Albert]

I understand this is not only an issue with the driver but also RoboDK hangs up. A quick way to make sure you recover your session in RoboDK is to kill the subprocess driver started by RoboDK (Ctrl+Alt+Delete and kill the driver such as xArmDriver in your case or Python instances).

To debug the driver, we'll need the connection log you shared in your first post in this thread.

If you are unable to recover control of RoboDK, to debug this issue better it would help if you can follow these steps:

1. Close RoboDK
   
2. Start RoboDK by double clicking the file: C:/RoboDK/RoboDK-Debug.bat
   
3. Try to reproduce the problem in RoboDK until it crashes.
   
4. Right after the crash, send us this file: C:/RoboDK/bin/RoboDK.debug.txt
   

Also, can you provide information about the version of RoboDK and the computer you are using?