[ChrisMan]

Can you try to reproduce this issue with the latest version of RoboDK?
We improved the driver to stop when a warning is provided. If the robot stops again, can you check if you have any warning or error messages on the robot controller?

You can take the latest version here:
https://robodk.com/download

I downloaded the latest version (it says updated August 8th), and it seems to be working more consistently, but it still skips. Here are two logs, one when the robot did not skip during movement and one when the robot did skip. There are no errors on the controller or teach pendant.

[Albert]

We just updated RoboDK again to improve the stability of the driver with Mitsubishi. I recommend you to take the latest version again:
https://robodk.com/download

I also recommend you to take the modifications to your script in the attached file. The following is important:

1. The Driver setParam call does not have an effect unless you trigger the Connect command or setRunMode to run on the robot. Turning servos On should not be needed anyway with the Mitsubishi driver as this is done automatically when connecting.
   
2. setRounding should be called after Connect to have an effect on the robot.
   
3. setRunMode(RUNMODE_RUN_ROBOT) is done automatically with Connect and it not needed to call it. It does not do any harm though, it is redundant.
   

Let us know if you still have issues.

[ChrisMan]

Thank you for the help. It runs more consistently now. However, The error is still occurring at least once every 200 cycles. The arm and program just stop on error. We wanted to know why it is erroring and how to make the arm complete the step that errored?

[Albert]

Is this the exact same error as before? Are you sure the axis limits are properly updated in RoboDK?

It would help if you can provide the log if you see a different behavior.

[ChrisMan]

Is this the exact same error as before? Are you sure the axis limits are properly updated in RoboDK?

It would help if you can provide the log if you see a different behavior.

It is the same error in the log, I couldn't capture it the last time I saw it but I will try to when it happens again.

I think the behavior is different due to the changes you made because the arm stops on warning now it seems. From the previous replies it sounds like that was the intended functionality, but how can I prevent this warning from occurring? 

How do I check the axis limits in RoboDK? I am pretty sure they are fine because the robot can execute hundreds of times just fine now, and only errors out rarely. Is there a way I can get more detailed logs from either the controller or RoboDK to get more information on whats happening?

[Albert]

I blieve this issue happens because RoboDK assumes the movement is feasible, however, the robot is unable to make this movement.

What would be ideal is to pause the robot as soon as you see the warning message and give us more informatio about where the robot is located and where you are trying to move the robot to.

[ChrisMan]

I blieve this issue happens because RoboDK assumes the movement is feasible, however, the robot is unable to make this movement.

What would be ideal is to pause the robot as soon as you see the warning message and give us more informatio about where the robot is located and where you are trying to move the robot to.

The issue happens with the same script as earlier in the posts. I am trying to get the log but it happens quite rarely now, will post it when it happens. Also, it happens on different movements, there doesnt seem to be a pattern that I have seen, but it has only happened maybe three times since the blocking issue was fixed within thousands of movements to the same positions and same paths

[Albert]

OK thank you for your feedback. It is great to get this update and narrow down the issue. If you find a way to reproduce it may be also useful to setup a call with our technical team. In this case you can contact us by email better:
https://robodk.com/contact

[KaiTheEngineer]

Hi Albert,

ChrisM, and I are on the same team. We are still having issues with the bug. It happens once or twice within 6 hours of operations. Is there a way I can save the "Show Log" with the Python API?

[Albert]

It is currently not possible to save the log using Python but you should be able to save it manually. Could you share your RoboDK project file and the error log? We can better take a look.