Posts by PaulC_Eire

A member of my team came across this today (26/02/2020):

https://www.universal-robots.c…-cb3-generation-3-robots/

Basically update to 3.12 asap due to a controller fire risk in the event of a PSU over-voltage situation that is not detected.

2 issues with this:

1. Method of communication - none: It was found in release notes/faq when looking for an update (leading to point 2). It was originally "posted" on 07/02/2020 - almost 3 weeks ago.
2. Notification of update available: Previously we would receive an email notification when a new version of software became available. This has now stopped and we've missed quite a few revs. This means our updates now take longer as we have to update rev by rev without jumping to the latest.

Now my 2 questions:

1. Has anyone had controller overheating/fire issues? What was the damage/outcome? How was it detected/resolved?
2. Has anyone else stopped getting notifications of the software updates from UR?

We're quite taken aback that we are only finding out about this now and that it was accidentally found in release notes. Surely for something as serious customers and integrators should be notified immediately?

Hi Folks,

Has anyone created a script/function where it uses the controller's time/date to carry out a task?

For example check if the date = DD/MM/YYYY or time = HH:MM:SS and if so do whatever.

I haven't managed to find any such variables but I'm going to assume the values can be read from a register somewhere?

Any help or guidance much appreciated

Fault found!

"V right4" cable (White) to Axis 4 motor was broken inside the arm in the vicinity of axis 3. Also some damage to "W right 4" (Black) cable. Repaired and added extra protection/insulation to the cables.

See attached image.

Have highlighted the issue to ABB and awaiting a response.

Helpful document for debug: 3HAC050778-003 (Pages 32 & 42)

Matt,

If it was the drive would this mean that none of the other axis can be operated too? We have noticed that even if we now try to jog any other axis separately using the pendant joystick it throws up the same error.

Hi all,

Looking for some advice on an issue we're having with one of our ABB YuMi (IRB 14000) robots.

The events leading up to this issue are unknown unfortunately but the result is the following errors:

• Event Message 34316 - Motor Current Error
  • Joint rob_R_4

• Event Message 34318 - Driver Inverter Saturated Error
  • Joint rob_R_4

As a result the motors are stuck in the "Off" state. The right arm can be moved by pressing the release button on the under-body.

I have visually inspected the arm and removed covers around Joint 4 but nothing stands out to me.

Can anyone shed some light on:

1. Root cause - e.g. roughly man-handled by some idiot damaging the joint brakes/robot collisions
2. Fix/direction on next steps - we have contacted ABB but no response yet.

What was the outcome from this? We have a number of these that are giving the same error after unboxing. However some appear to have charged up the batteries once left powered on for upto 24 hours but others have not charged.

Potential battery issue?