1. Home
    1. Dashboard
    2. Search
  2. Forum
    1. Unresolved Threads
    2. Members
      1. Recent Activities
      2. Users Online
      3. Team Members
      4. Search Members
      5. Trophys
  3. Articles
  4. Blog
  5. Videos
  6. Jobs
  7. Shop
    1. Orders
  • Login or register
  • Search
This Thread
  • Everywhere
  • This Thread
  • This Forum
  • Articles
  • Pages
  • Forum
  • Blog Articles
  • Products
  • More Options
  1. Robotforum - Support and discussion community for industrial robots and cobots
  2. Forum
  3. Industrial Robot Support and Discussion Center
  4. ABB Robot Forum
Your browser does not support videos RoboDK Software for simulation and programming
Visit our Mainsponsor
IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Sponsored Ads

ABB S4C+ Controller || Error 50056

  • robomaniac
  • August 13, 2018 at 9:53 PM
  • Thread is Resolved
  • robomaniac
    Trophies
    3
    Posts
    25
    • August 13, 2018 at 9:53 PM
    • #1

    Hello Everyone,
    I have ABB IRB2400 and IRB1400 robots with S4C+ Controller.When I try to jog the manipulator arm it doesn't allow me to jog the robot and immediately drops the error 50056 Error: Joint collision. I Checked all the axis but its not hitting anywhere when I try to jog.The actual error description is as follows:

    50056 Error: Joint collision Actual torque on joint irb_3 ishigher than ordered while at low or zero speed. Might be caused by jam error (the arm has got stuck) or hardware error.

    Initially i was able to jog axis no. 1,2 & 3 and had problem on axis 4,5 & 6.But,Now it gives me the same error on all the axis.

    I am new with these S4C+ Controllers.can someone please give me some reason for this thing.Any comments would be really appreciated.
    Thank you

  • SAABoholic
    Reactions Received
    21
    Trophies
    5
    Posts
    550
    • August 14, 2018 at 5:09 PM
    • #2

    Could be a lot of things, but first you could/should verify that the brake for the axis actually releases (be careful with ax 2/3 and don't release more than one at a time).
    You'd want someone supporting the arm while you test it, the 2400 have individual buttons for each axis, tap/blip the button real quick and listen for a "clonk" and arm will move.
    On the 1400 there's just one for all of them so be careful.

    If the brake releases I'd verify that you have the correct robot type booted (save system parameters and look in the moc.cfg file), it should match what's printed on the back of the robot.
    Over the years they've changed motors and gearboxes which is designated by a Type A(or nothing) Type B, C etc...

  • Skooter
    Reactions Received
    167
    Trophies
    6
    Posts
    2,005
    • August 16, 2018 at 3:37 AM
    • #3

    To expand on SAABoholic's brake check:
    After verifing the manual brake release using the buttons as described, verify the brakes release automatically. Do this by pulling in the deadman, then slightly move the joystick to release the brakes but not move the robot. Make sure you get the "clonk" sound on all six motors as their brakes release. The brakes are located internally near the back in each motor. Try using a mechanics stethoscope (or screwdriver to the ear) if you have problems hearing it. If you do not get the "clonk" when first moving the joystick after pulling in the deadman, then verify that contactor KM3 is pulling all the way down when you first move the joystick and that you have 24VDC at KM3-14 (wires 364 & 365).

Advertising from our partners

IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Advertise in Robotics
Advertise in Robotics

Job Postings

  • Anyware Robotics is hiring!

    yzhou377 February 23, 2025 at 4:54 AM
  • How to see your Job Posting (search or recruit) here in Robot-Forum.com

    Werner Hampel November 18, 2021 at 3:44 PM
Your browser does not support videos RoboDK Software for simulation and programming

Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Thread Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Users Viewing This Thread

  • 1 Guest
  1. Privacy Policy
  2. Legal Notice
Powered by WoltLab Suite™
As a registered Member:
* You will see no Google advertising
* You can translate posts into your local language
* You can ask questions or help the community with your knowledge
* You can thank the authors for their help
* You can receive notifications of replies or new topics on request
* We do not sell your data - we promise

JOIN OUR GREAT ROBOTICS COMMUNITY.
Don’t have an account yet? Register yourself now and be a part of our community!
Register Yourself Lost Password
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on Google Play
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on the App Store
Download