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

New to Kawasaki. Really struggling with setting up an Ethernet IP scanner device

  • dohlfhauldhagen
  • March 25, 2024 at 7:45 PM
  • Thread is Unresolved
  • dohlfhauldhagen
    Reactions Received
    7
    Trophies
    3
    Posts
    59
    • March 25, 2024 at 7:45 PM
    • #1

    Hello all. I'm very new to Kawasaki after being used to ABB and Fanuc for most of my career. I have an MX350L robot on an E controller, and right now I'm just playing around trying to familiarize myself with the programming environment.

    Right now I have a small test network setup with an Allen Bradley PLC, a Balluff input block, and the robot. I have the robot connected to my switch via port 2, and everything is assigned a 192.168.11.xxx address. I was able to establish comms between the PLC and robot as an adapter, however I am really struggling getting the robot to communicate with the IO block as a scanner.

    Attached is a pic of my PLC config to talk to the robot, my network setup for the adapter, and my config settings for the scanner device. The pic also shows the assembly and input/output instance settings for the Balluff block from the manual. If I make the PLC the owner of the Balluff block with these settings, it works just fine. But I want the robot to have control over this device, not the PLC, and that's where I'm running into trouble. After I set this all up and run the TYPE EIPSTATUS(1) command in KRterm, I always get a 0 indicating that there are no communications between the robot and the Balluff block.

    I should mention that I am referencing the General Fieldbus I/O Usage Manual. And I should also say that it is somewhat confusing for me. I don't really understand what the manual means when it talks about allocating signals as master or slave. I'm not used to seeing this terminology anywhere except for when I've worked with Devicent in the past. I also cannot seem to get the ZSIGSPEC command to work, as KRterm says the operation is not allowed. On top of that, I don't really even understand what this command does, as the manual does not do the best job spelling it out in layman's terms.

    Any direction on this would be super appreciated, thank you.

    Images

    • kawasaki scanner help.png
      • 1.21 MB
      • 834 × 1,200
      • 54
  • kwakisaki
    Reactions Received
    694
    Trophies
    12
    Posts
    4,770
    • March 25, 2024 at 9:30 PM
    • #2

    Could be many things as ethernetip is very critical for correct values to be applied.

    Do you have error code displayed when you see monitor screen on teach pendant for ethernetip?

    I see you have 32 signals set for local use, are you using 1TW board or ArmID board for this?

    I have configured 3x Balluff IO blocks for direct control from robot successfully without PLC attached.

    (application did not have PLC installed).

    So I can confirm these following modules work correctly direct control from robot as scanner setup:

    - 3x Balluff BNIEIP 302-105-Z015 16in/16out.

    Where are you intending Balluff IO Block to be allocated:

    - What allocation range is set for PLC - Starting and Ending and number of bytes.

    - What allocation range is set for BALLUFF - Starting and Ending and number of bytes.

    Please check your producing and consuming values are not the wrong way round.

    (This can only be confirmed with your .eds for your Balluff IO Blocks).

    Please check 32 bytes shared memory offset........I question this value.

    - But this depends on where Balluff allocation sits - is it before PLC or after PLC signal allocation?

    View my channel at Industrial Robotics Consultancy Limited - YouTube

  • kacz0r
    Reactions Received
    12
    Trophies
    3
    Posts
    25
    • March 25, 2024 at 10:51 PM
    • #3

    If last window You have attatched is from Balluff software config You have IP adress misspeled and it is out of robot's subnet.

    Other tahna that ples provide eds. file or at lest Balluff IO module name os it is possible to check configuration manual for that product.

    In eds file check for connection type as setting it to multicast where point2point is expeced or vice versa leads to connection trubles.

    You can also checconnection ststus and error code via monitor menu -> Software EthernetIP status

    There You will have link status and error cod if devices can see each other but some settings are incorrect.

  • dohlfhauldhagen
    Reactions Received
    7
    Trophies
    3
    Posts
    59
    • March 26, 2024 at 4:25 PM
    • #4

    Thanks for the replies guys. That last picture of the Balluff config is just from the manual, so that IP address is not reflective of what I'm actually using. All are on the same subnet and I can ping all devices from my PC. I do have the EDS as well and did verify that producing and consuming values were correct. Like I said, I'm extremely new to the Kawasaki system and right now I'm just using equipment we have around the shop to teach myself.

    Unfortunately, I am on the road now for a different job and can't look into some of your suggestions right now. Hopefully I will be able to later this week and provide an update.

  • dohlfhauldhagen
    Reactions Received
    7
    Trophies
    3
    Posts
    59
    • March 28, 2024 at 2:16 PM
    • #5

    I got it. I double checked the produced and consumed tag values with the EDS again, and I guess I did have it backwards. I have communication now. Thank you again for the support!

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

Tags

  • kawasaki
  • Ethernet
  • scanner
  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