Rtde safety setup

Technical Questions Robot Communication
1

I’m retrieving robot position via rtde which was working fine before I updated to URSim 5.13.
After updating to URSim 5.13, an out of bounds error occurs when I receive data.
If I print out the data key types retrieved from rtde, I get the message below:
SafetySetup has not been confirmed yet therefore no data will be send yet URControl

I just checked and it also occurs in the physical robot.

Anyone know how to confirm safety setup?

2

Is anyone else’s RTDE functioning properly after updating to 5.13?
Maybe it’s just my safety setup that has been wiped after upgrading.
If anyone knows which safety setup to configure, I would appreciate your help.

3

Can anybody help here?
RTDE just doesn’t start and it’s occuring in more than one of our robots.
How is your RTDE working after updating to 5.13?

I’m trying to retrieve the following:
actual_TCP_pose
actual_q
actual_TCP_speed
input_bit_registers0_to_31
input_int_register_5
input_int_register_6
input_int_register_7
robot_mode

In the RTDEClient class, the read from my input stream is
types[0] = SafetySetup has not been confirmed yet
types[1] = therefore no data will be send yet URControl

Thanks for your help.

4

alrighty, then. thanks

5

it seems the safety setting was not being read correctly from the installation file during bootup.
a quick fix i found is to manually open the default installation file again.
hope it helps.

6

if anyone with the same problem stumbles on this thread,

assumed cause: the RTDE client is started in the constructor of the installation contribution, which occurs before the safety settings are properly loaded
quick fix: load the installation file again to properly load the safety settings
better fix: move the starting of the RTDE client to a different timing, preferably after all other settings are loaded. in my case, in the constructor of every program contribution.