[samktki]

Thank you for your feedback. We just updated RoboDK to account for proper units when using the Automata EVA post processor.
You can take the latest version here (Windows only for now):
https://robodk.com/download

Thank you. 

Send Program to Robot: The joint boundary limit error is no longer occurring. However, I am now encountering an HTTPConnectionPool read timed out error with a read timeout of 5 seconds. This issue might also be related to my system; I will test further next week. The generated program still works if degrees are manually converted to radians, so it's unclear why the timeout happens.
Generate Robot Program as: Still outputs in degrees.
Generate Robot Program: Still outputs in degrees.

The EVA model posted by Olivier on 07-05-2025 is still behaving strangely when teaching targets and movements. While the axis values are correct during jogging, the robot's position becomes inaccurate when teaching targets and movements (it flips Axis 3, causing all axes to go non-optimal).
The attached pictures illustrate the issue:

• When homing the robot and teaching Target 1, everything appears to be fine.
  
• However, when adding a MoveJ command to Target 1, the robot's position becomes incorrect.
  

[Albert]

Are you available for a call in the next few days? We can better fix these issues over a call with someone in our technical team. You can contact us by email and mention this thread:
https://robodk.com/contact

[samktki]

I contacted by email and got response 15.5. that my request is forwarded to Support Team. I haven't heard anything after that. I know this is not maybe priority number one on your list, but I think we are really close to get EVA working. Just (minimum) Axis 3 flip correction and could use EVA + RoboDK in our lab exercixes. Axis 3 degree range is now right in RoboDK, but path planning is broken and robot pose is wrong after moveJ command in RoboDK (previous post images).