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

Can't connect from my laptop to robot controller

  • tomexx
  • October 23, 2019 at 9:45 PM
  • Thread is Unresolved
  • tomexx
    Trophies
    4
    Posts
    66
    • October 23, 2019 at 9:45 PM
    • #1

    Hi,

    We've run an Ethernet line to the controller (R30-iB MATE) and setup Host Communication as follow:

    Port#1 IP addr: (Static ip given by IT)

    Subnet Mask: 255.255.255.0 (again from the IT)

    There's no router used. The line goes from the Ethernet switch to the robot controller.

    However I can not ping the robot. IT are asking me to put the gateway address but I don't see a space for it.

    Ethernet Port Status for Port #1 shows:

    Link State: 100/Full

    TX count: 3

    RX count: 1243

    Collisions: 0

    Storm count: 0

    What am I missing?

    Thanks,

    Tom

  • retobor
    Reactions Received
    17
    Trophies
    4
    Posts
    202
    • October 23, 2019 at 9:57 PM
    • #2

    Are you sure your laptop is on the same network as port 1 and not port 2? Your laptop is using the same 3 nodes as the robot and the last node is not used by any other device (ex. 192.168.1.xxx)?

    I believe 'router IP' is used for gateway, but I never set this.

  • HawkME
    Reactions Received
    568
    Trophies
    10
    Posts
    3,268
    • October 23, 2019 at 10:20 PM
    • #3

    Also, make sure the ethernet cable is plugged into port 1. Most controllers have 3 ports. Port 1, port 2, and vision port.

  • I3ooI3oo
    Reactions Received
    5
    Trophies
    3
    Posts
    77
    • October 24, 2019 at 2:47 PM
    • #4

    The router IP is the gateway. A gateway is only ever needed to send data from one network to a different network outside the subnet mask.

  • tomexx
    Trophies
    4
    Posts
    66
    • October 24, 2019 at 8:28 PM
    • #5

    Thanks for replay guys, Here's more info:

    My laptop's I/P is 10.7.71.**

    Robot's I/P is 10.7.114.**

    Is this an issue?


    I also put the gateway address into Router I/P spot on the controller.

    Still can't connect.

    Thanks,
    Tom

  • I3ooI3oo
    Reactions Received
    5
    Trophies
    3
    Posts
    77
    • October 24, 2019 at 8:39 PM
    • #6
    Quote from tomexx

    Thanks for replay guys, Here's more info:

    My laptop's I/P is 10.7.71.**

    Robot's I/P is 10.7.114.**

    Is this an issue?


    I also put the gateway address into Router I/P spot on the controller.

    Still can't connect.

    Thanks,
    Tom

    Display More

    Yes. You would need to change the subnet mask on both to 255.255.0.0

    If your mask is 255.255.255.0 on the last octect is allowed to change without going through the gateway/router.

  • tomexx
    Trophies
    4
    Posts
    66
    • October 24, 2019 at 8:56 PM
    • #7

    Tried changing subnet mask on the robot to 255.255.0.0. This didn't make a difference.

    However, I noticed that with my original settings I CAN access a different device on the network the robot is in so it's not the mask.

    My laptop's I/P is 10.7.71.**

    Temperature probe I/P is 10.7.114.74

    ...and I can access the temperature probe not problem even with both masks at 255.255.255.0

  • tomexx
    Trophies
    4
    Posts
    66
    • October 24, 2019 at 8:58 PM
    • #8

    ...The difference is the temperature probe has DHCP disabled and gateway entered - two items I don't know where to set on the robot.

  • Sergei Troizky
    Reactions Received
    67
    Trophies
    6
    Posts
    650
    • October 24, 2019 at 10:34 PM
    • #9

    - The Router IP is the Gateway. As I3ooI3oo already said, a gateway is only needed to send data to a network outside the subnet mask.

    - The robot does not use DHCP.

    - If there are two Ethernet ports on the robot, they cannot be configured both on the same subnet.

    - After the Host Comm setting changes, they must be initialized by the NEXT>>[F3]INIT or by the robot reboot.

    - Straight cable to be used with the switch and cross-link cable for direct PC-to-robot connection (the latter unless the PC automatically detects the cable type, typical for modern PC).

    - The subnet mask must be matching on the robot and the PC.

    - And finally, when you succeed pinging the robot, what do you expect to see further on the PC?

    I doubt the web-interface will be accessible unless there is the Internet Connectivity option installed.

    Do it well right away. It will become bad by itself.

  • tomexx
    Trophies
    4
    Posts
    66
    • October 25, 2019 at 3:31 PM
    • #10

    Thanks Sergei for clearing up few things.

    I'm hoping to connect to the web interface to look at error logs as well as backup files from my desk.

    I'm going to check if I have Internet Connectivity installed.

    Thanks,

    Tom

  • HawkME
    Reactions Received
    568
    Trophies
    10
    Posts
    3,268
    • October 25, 2019 at 6:53 PM
    • #11

    I would still make sure you have the Ethernet cable plugged into the correct port. On the mate controllers the ports are not labeled in a way that is very easy to read. I have seen this be the cause of the issue many times, and it only takes about 1 minute to try the other port and verify.

    The R-30ib Mate controller should not require any special software options to have access to the web server.

  • I3ooI3oo
    Reactions Received
    5
    Trophies
    3
    Posts
    77
    • October 25, 2019 at 8:00 PM
    • #12

    Look at the gateway on the temp probe, take that and put it as the gateway on the robot that should solve your issue.

    As a network engineer I can tell you that there are thousands of ways to setup a network. Your network could be using vlans. It could be segmented. The switches could be managed and only allowing traffic to specific ports.

  • I3ooI3oo
    Reactions Received
    5
    Trophies
    3
    Posts
    77
    • October 25, 2019 at 8:01 PM
    • #13

    Allow I would ping the temp probe with robot. If you can at least the robot is on the network.

  • YURIVIN
    Trophies
    2
    Posts
    2
    • October 22, 2020 at 6:34 PM
    • #14

    Tom - do you solve your problems?

  • hermann
    Reactions Received
    405
    Trophies
    9
    Posts
    2,597
    • October 23, 2020 at 8:15 AM
    • #15

    This thread is a year old, what do you think? What's the goal for this question?

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