Event message 50204
We use IRB 1600 IRC5 as a welding robot. From time to time ( but sometimes even several times during one shift) we have message 50204 (motor supervision) and robot stopage without collision and any visible reason, it concerns sometimes axis 1, sometimes axis 3 - no logical repeatability. Breakdowns starts when some strange noise (only when arc is on) begins to hear - when the loudness increase stopages are more frequently, after also without any our activity noise disappear and the message doesn't appear. We can't find the noise source.
We already tested quick movement of the axes but without any disturbing noises, also the brakes works properly, engines aren't overheated.
We're hopeles but what worse service also.
Has anyone similar problem? Will be grateful for any suggestion.
0
Comments
-
I have seen a similar problem
The wire get stuck on the welding part.Robot make a movement to exit. In this movement the wire get broken from the part, but also, you have a motion supervision error.When you enter in the cell you don`t see any problem.In other cases customer forgot to configure the wirefeeder load in to the system.0 -
Thx for suggestion. OK I check again standing in the cell during the welding process. I wrote "again" because I already was there and didn't observe the moment that wire get stuck but it costs nothing to check again. Have you any idea what can cause that strange noise and structure trembling ( easy to feel putting palms on the house).Looking for noise source we checked wire path from wire drum up to nozzle finding nothing.0
-
hi,I had similar problem IRB 1600 with RW 5.07.I upgraded Robotware version from 5.07 to 5.08 , the problem was solved.0
-
Hi guys,the noise happens here too when my axis 2 and 3 are extended close to the maximum.Like if the robot was "forcing" a little bit more than he's use to.My 2 robots 2400-16 do the same so I suspect it's not something very rare.JetJet,
Janin Delorme, Ing. (P.Eng)0 -
Maybe you have some sort of mechanical problem with your robot arm. If it is making noise and vibrating and the MS error happens while the noise is occuring, then probably you have either misconfigured the tool/payload etc., or there is something physically wrong that is causing the required torque to exceed the expected torque. Another possiblity may be that you have the motion supervision values turned down?Russell Drown0
-
Hi Lucky Man,IA'm having more or less the same problem "message 50204 (motor supervision)" and in some positions the robot starts like trembling.How did you solve this error ?Many thanks and regards,
peiopirata2012-11-23 11:22:560 -
Hello Peiopirata,We too have the message "50204 (motor supervision)" with the robot trembling.Did you solve this problem?Any help would be much apprciated.Thanks0 -
Hi guys,Motion supervision errors can be caused by many different things.Wrong PayLoad;Wrong Tool mass;Motion Supervision setting too low (default is 100) but it can be adjusted;Cables of paint gun/Plasma torch, welding gun exercing a pull on the robot when extended (happens more on small payload robot);Excessive wear of robot (harder to move);Wall mounted or celing mounted robot with Alpha/Beta gravity variables not set properly.Mechanical problem with the robot but it's unlikely.The problem can probably be solved by increasing Motion Supervision but it would be best to identify the cause first.JetJet,
Janin Delorme, Ing. (P.Eng)0
Categories
- All Categories
- 5.5K RobotStudio
- 394 UpFeed
- 18 Tutorials
- 13 RobotApps
- 297 PowerPacs
- 405 RobotStudio S4
- 1.8K Developer Tools
- 249 ScreenMaker
- 2.7K Robot Controller
- 309 IRC5
- 59 OmniCore
- 7 RCS (Realistic Controller Simulation)
- 783 RAPID Programming
- AppStudio
- 3 RobotStudio AR Viewer
- 18 Wizard Easy Programming
- 105 Collaborative Robots
- 4 Job listings