abb_libegm: RobotWare 6.13 EGM UdpUc error

Hello,

I work with the Yumi and EGM. I upgraded the RobotWare version from 6.12 to 6.13. My Rapid code worked when I was using version 6.12 but with version 6.13, when I run the Rapid code I get the following two errors:

  • 41830, Error sending EGM UdpUc message.
  • 41822, No data from the UdpUc device.

I also updated the RobotWare to version 6.13 of the ABB1200 in our lab and tried to run the same Rapid EGM code. This works on the ABB1200 with RobotWare version 6.13.

I tried with the Yumi by simulating RobotWare versions 6.11 and 6.12 and it works.

Do you know why I get these errors with RobotWare 6.13 on the Yumi ?

My Rapid code is

`MODULE TRob1Main

!***********************************************************
! Program data
!***********************************************************
! Home position.
 LOCAL CONST jointtarget home:=[[0,-130,30,0,40,0],[135,9E+09,9E+09,9E+09,9E+09,9E+09]];

! Identifier for the EGM correction.
LOCAL VAR egmident egm_id;

! Limits for convergance.
LOCAL VAR egm_minmax egm_condition := [-0.1, 0.1];
        
!***********************************************************
!
! Procedure main
!
!   This RAPID code exemplify how to run EGM joint position
!   motions.
!
!   Note: Update the UCDevice "ROB_1" with correct
!         values for the remote address and port
!         (i.e. to the EGM server).
!
!         Update via RobotStudio:
!         Controller tab -> Configuration ->
!         Communication -> Transmission Protocol
!
!***********************************************************
PROC main()
    
    MoveAbsJ home, v100, fine, tool0;
    
    WHILE TRUE DO
                                
        ! Register an EGM id.
        EGMGetId egm_id;
        
        ! Setup the EGM communication.
        EGMSetupUC rob_L, egm_id, "default", "ROB_1", \Joint;
        
        ! Prepare for an EGM communication session.
        EGMActJoint egm_id
                    \J1:=egm_condition
                    \J2:=egm_condition
                    \J3:=egm_condition
                    \J4:=egm_condition
                    \J5:=egm_condition
                    \J6:=egm_condition
                    \J7:=egm_condition
                    \MaxSpeedDeviation:=180.0;
                    
        ! Start the EGM communication session.
        EGMRunJoint egm_id, EGM_STOP_HOLD\J1\J2\J3\J4\J5\J6\J7\CondTime:=5\RampOutTime:=1;
        
        ! Release the EGM id.
        EGMReset egm_id;
        
        WaitTime 5;
    ENDWHILE
    
ERROR
    IF ERRNO = ERR_UDPUC_COMM THEN
        TPWrite "Communication timedout";
        TRYNEXT;
    ENDIF
ENDPROC

ENDMODULE`

About this issue

  • Original URL
  • State: open
  • Created 5 years ago
  • Comments: 18 (7 by maintainers)

Most upvoted comments

Hi, I’m also working with YuMi using EGM with RobotWare version 6.13.00.00, utilizing the ABB robot driver repository (https://github.com/ros-industrial/abb_robot_driver) and the State Machine 1.1 as RAPID code. I set the UDP connection by assigning the UcDevice ip and the ip of the two mechanical units as that of my pc, which is the EGM server. I can launch EGM through EGMRunJoint in the state machine, but the communication times out, giving me the following errors:

  • 41830: Error sending EGM UdpUc message.
  • 41822: No data from the UdpUc device.

These are the same errors reported by @Luc90 , who opened this issue. Has anyone managed to confirm over the years if the RobotWare 6.13 version is indeed the root cause of this problem?

I’m posting here because this issue seems identical to Luca’s EGM problem and unrelated to the other repositories I’ve mentioned.

Thank you!

The version of abb IRB2600’s robotware is 6.06,Can i update the robotware version to 6.07.01 to use this library?

I’ll try to keep the abb_robot_driver under a separete PC.

It could be abb_robot_driver’s threads are starved, leading to the timeout.

For abb_robot_driver specifically, you could perhaps see whether installing an PREEMPT_RT kernel and then using chrt (with suitable parameters (something like --fifo -p 99 as a first test) and run by a user with the required permissions) helps mitigate this.

If your ros_control controller is taking too long, changing priorities like this likely won’t help, but for other ‘random’ scheduling events or other thread-starvation out of the sphere of influence of abb_robot_driver, it could help.


Edit: you should be able to use chrt as a launch-prefix command, if using ROS 1 .launch files.

I’m somewhat confused.

You mention RW6, but the application manual you link is for RW7.