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. Fanuc 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

EE Connector Pinout Questions

  • StoopidEngineer
  • February 27, 2020 at 4:22 PM
  • Thread is Unresolved
  • StoopidEngineer
    Reactions Received
    6
    Trophies
    3
    Posts
    43
    • February 27, 2020 at 4:22 PM
    • #1

    Hey Gang - Looking at the pinout for the EE Connector on an old LR Mate, and was hoping someone could help clarify some things for me.

    Pinout given is:

    1 - RDI1

    2 - RDI2

    3 - RDI3

    4 - RDI4

    5 - RDI5

    6 - RDI6(*PPABN)

    7 - (*HBK)

    8 - +24V

    9 - +24V

    10 - +24V

    11 - 0V

    12 - RDICOM

    Pins 1 through 5 are obviously inputs. I'm guessing pin 6 is configurable from input 6 tom something else? What the heck is *PPABN?

    Pin 7 - What is *HBK?

    +24V is clear, but the 0V and RDICOM for pins 11 and 12 is confusing. I've run into trouble with different companies meaning different things by 'Common' before (You don't wire hand I/O to 0V or COM on Epson robots, you wire them to what they call 'Ground' but really isn't)

    Can I use the 0V and RDICOM interchangeably? Or do I need to use RDICOM for the common connection of all the inputs? Or do I use the 0V for the common connection of all the inputs?

    It's great they give me 3 pins of +24VDC for 6 inputs, because it works out perfectly if I want to use splitters, or at least only have to try to solder two conductors into a single pin, but why only have one (or maybe two?) commons? This type of stuff drives me nuts, because I hate putting giant j-boxes on the end of little robots.

    Appreciate the help with this - Thanks!

  • stare284
    Reactions Received
    25
    Trophies
    4
    Posts
    373
    • February 27, 2020 at 4:33 PM
    • #2

    HBK is hand broken

    PPABN Pneumatic Pressure Abnormal

  • StoopidEngineer
    Reactions Received
    6
    Trophies
    3
    Posts
    43
    • February 27, 2020 at 4:47 PM
    • #3

    Ah, acronyms. Thanks for breaking those out for me.

    Functionally, if I put 24VDC to pin 6, I'll get an air pressure alarm, and if I put 24 VDC to pin 7, I'll get the SRVO-006 alarm? i.e. I don't have to use them, but I don't have to jumper them?

  • stare284
    Reactions Received
    25
    Trophies
    4
    Posts
    373
    • February 27, 2020 at 4:53 PM
    • #4

    You can turn of the Hand Broken in the System Config so you don't have to supply power to it at all.

    I think you can do the same for the air but not 100% sure without looking at a pendant.

  • kluk-kluk
    Reactions Received
    53
    Trophies
    5
    Posts
    300
    • February 27, 2020 at 5:26 PM
    • #5

    You can disable PPABN with a variable, i think it is in $parameter-group

  • kwakisaki
    Reactions Received
    694
    Trophies
    12
    Posts
    4,770
    • February 27, 2020 at 10:15 PM
    • #6

    Each Arm input requires a min current per input to switch on/off.

    As IO can usually have NPN or PNP configurations, I am sure RDI Com is for this purpose accompanied with a 'moveable link' to switch between either a common rail 0v (PNP) or common rail 24v (NPN) configuration - ie sourcing current or sinking current to activate the input.

    Attached is a snippet (but not the same pinout) which highlights the RDICOM, link and circuit.

    Images

    • Capture.JPG
      • 49.5 kB
      • 319 × 361
      • 365

    View my channel at Industrial Robotics Consultancy Limited - YouTube

  • StoopidEngineer
    Reactions Received
    6
    Trophies
    3
    Posts
    43
    • February 28, 2020 at 3:06 PM
    • #7

    @kwakisaki - Ah, that makes absolutely perfect sense now that you say it. I'm in the US and rarely encounter NPN devices, so my mind doesn't usually jump to this - thanks for the input!

    It's going to be easy enough to test out and make sure, but it looks like (based on my amateur-ish reading of the schematic you posted) that the default is for PNP, and I don't need to put power to the RDICOM pin - that make sense to you?

    Thanks!

  • kwakisaki
    Reactions Received
    694
    Trophies
    12
    Posts
    4,770
    • February 28, 2020 at 8:52 PM
    • #8

    Exactly..………:top:

    I'm pretty sure (although I am new to Fanuc) that the later versions of Arm, do not have the RDICOM as a terminal, but still have the movable link.

    Here in the UK is usually PNP also, but care should be taken to check the configuration and manuals prior to wiring the peripherals as incorrect wiring could cause excess current being pulled.

    Most locations/countries have a default standard, but with cross ordering and 2nd user equipment being sourced from different locations, you should always verify which configuration it is set for before wiring up.

    We know when something is pulling too much current as fuses pop, wiring melts and then we have a look at the manual and say oops! my bad...….:away:

    Yes, PNP configuration is what is referred to as 'sourcing current'.

    So by supplying 24V as input, you will 'source' the current.

    Whereas NPN configuration is what is referred to as 'sinking current'.

    So by supplying 0v as the input, will 'sink' the current.

    If you look at proximity sensors and the like, you will find they are available in PNP and NPN flavours.

    So OEM's would have to manufacture/supply 2 different types of board to support which is costly in comparison to a 'universal board' that can be configured using links.

    View my channel at Industrial Robotics Consultancy Limited - YouTube

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
  • krc5
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • 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
  • krc5
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Similar Threads

  • KRC4 Compact X11 and X55 - once again

    • dgrzywnowicz
    • January 23, 2018 at 9:06 PM
    • KUKA Robot Forum
  • Control another Controller with an E71 controller

    • BCITokyo
    • June 9, 2016 at 8:59 PM
    • Kawasaki Robot Forum
  • Syncing two RS050N using Master/Slave Configurations or anything else

    • BCITokyo
    • May 26, 2016 at 1:04 PM
    • Kawasaki Robot Forum
  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