RW 6.16 bug with IRB 7600-325/3.1 and Quad-Arm IRB 4600-60/2.05 Type C

Marty2906
Marty2906 ✭
edited March 29 in IRC5
Hello.

We upgraded our working system to RW 6.16. After that the Deadman releases by itselfe. While we were moving through the code Step by Step or with Play and even in Automatic, the Controllers Motors turned off by itselfe.

We downgraded to the original RW which was installed and then everything worked fine again. No Motors OFF or releasing Deadman while running through the Programm in any Mode.

That was not good at all...

Addon:
On our Quad-Arm (IRB 2600ID-15/1.85 Type A) or Dual-Arm (IRB 2600-20/1.65 Type B ) or Single Robot (IRB 4600-60/2.05 Type C) are no Problems with RW 6.16.

Addon 2:
Happened on our Quad-Arm IRB 4600-60/2.05 Type C too. Solved by downgrading RobotWare to it's delivered RW.

Regards
Marty

Post edited by Marty2906 on
Tagged:

Comments

  • Maxim Riabichev
    Maxim Riabichev admin
    Hi Marty,

    Please get in touch with your local ABB for assistance with this issue.

    https://new.abb.com/contact-centers

    —
    Maxim Riabichev
    PC Software Support Engineer
  • Marty2906
    Marty2906 ✭
    Hi Maxim.

    Downgrading helped but it's still a Problem with that RobotWare with with IRB 7600-325/3.1 and Quad-Arm IRB 4600-60/2.05 Type C, because when you have an issue with the SoftSuperior Stop (that's fixed with 6.16) you have now a new Problem with the Motors OFF when you install 6.16 on your system.

    Best regards
    Marty



  • AlwaysBeBootin
    AlwaysBeBootin ✭
    Hey Marty,

    We have an IRB 4600 robot with the exact same issue that you are describing after updating to 6.16.00. We were previously running 6.15.06, which had a whole different set of issues that would put the controller into system failure when simply loading programs. I am about to try loading 6.15.08 which includes some fixes that can cause those system failures.

    I know you've already downgraded, but what I found on 6.16.00 is that when the robot goes into guard stop / motors off, there are no active alarms, however on the internal errors screen there are these three following errors:

    -100000 internal error
    splin_ip.cpp 3991 error in spline_ip_work_area_and_wzone_test pose error
    -100000 internal error
    Dyn_spline.c 361 in dyn_spline_get_pos geo_pline_eval
    -100000 internal error
    Jspline.c 230 x=0.027198 is not in interval [0 0.024197]

    It's a bit disheartening to have to walk through a minefield of bugs when upgrading. This seems like a pretty major issue that got missed.

    Thanks,
    Jeff
  • Maxim Riabichev
    Maxim Riabichev admin
    Hey guys,

    I think it's important that you reach out to your local ABB and report this issue, if you haven't already done so.

    https://new.abb.com/contact-centers

    Thanks!

    —
    Maxim Riabichev
    PC Software Support Engineer
  • Marty2906
    Marty2906 ✭
    Hello togehter.

    On my Systems there was no visible Error. The controller only turns the motors off in every mode (step, 100% or auto).

    To downgrade the robots was my idea to solve the problem, but I wanted to update because of some very important corrections in the RW.

    So I contacted the local ABB technician and they told me, that we are not allowed to upgrade the RW. I was very disappointed about this answer because a newer RW are fixing issues that could occur in lower RW.

    That's the current state.

    Best regards
    Marty

Categories

In this Discussion