Skip to main content

Device Connection Errors

When trying to add a device (such as a robot) in Device Configuration, you may get a communication error. Sometimes this can be caused by devices being powered off or by cables being loose, but it can also be caused by incompatible IP addresses.


EXAMPLE 1 - Robot + Forge/Hub

Setup

Suppose you are using a Forge/Hub with the following setup:

  1. In Settings > Network, you see three configured Network Interfaces:
  • eno1

    • IP Address: 172.16.255.250
    • Pendant IP Address: 172.16.255.253
    • Subnet Mask: 255.255.255.0

  • enp3s0

    • IP Address: 192.168.0.10
    • Subnet Mask: 255.255.255.0

  • wlp2s0


  1. In the native robot software, you have these settings:
  • IP Address: 192.168.1.20
  • Subnet Mask: 255.255.255.0

  1. In Device Configuration, you’re trying to add a device with the IP Address set to 192.168.1.20.

Solution

In this case:

  • The “eno1” network interface dictates the pendant connection. Its settings cannot be changed.

  • The “enp3s0” network interface dictates device connections.

  • The “wlp2s0” network interface dictates wireless functionalities, such as online license activation and online updates.

There is a mismatch because the IPC's Ethernet port is on the 192.168.0.XXX network and the robot is on the 192.168.1.XXX network.

tip

To fix this, change the IP Address for “enp3s0” from 192.168.0.10 to 192.168.1.10.


EXAMPLE 2 - Robot + Forge/Ctrl

Setup

Suppose you are using a Forge/Ctrl with the following setup:

  1. In Settings > Network, you see one configured Network Interface:
  • enp1s0

    • IP Address: 172.16.255.250
    • Pendant IP Address: 172.16.255.253
    • Subnet Mask: 255.255.255.0
    • Gateway: 172.16.255.249
  1. In the native robot software, you have these settings:
  • IP Address: 192.168.1.20
  • Subnet Mask: 255.255.255.0

  1. In Device Configuration, you’re trying to add a device with the IP Address set to 192.168.1.20.

Solution

In this case, there is a mismatch because ForgeOS is running on the 172.16.255.XXX network and the robot is on the 192.168.1.XXX network.

tip

To fix this, change the robot's IP Address in the native robot software and in Device Configuration from 192.168.1.20 to 172.16.255.251 (assuming that this doesn't conflict with other devices).


EXAMPLE 3 - Conveyor + Forge/Ctrl

Setup

Suppose you are trying to connect a Modbus TCP device to ForgeOS. The device uses a fixed IP Address that's different than what ForgeOS runs on:

  1. In Settings > Network, you see one configured Network Interface:
  • enp1s0

    • IP Address: 172.16.255.250
    • Pendant IP Address: 172.16.255.253
    • Subnet Mask: 255.255.255.0
    • Gateway: 172.16.255.249
  1. The documentation for your device (e.g., an EMI conveyor with a fixed IP Address of 131.200.131.2 and subnet of 255.255.255.0) states an IP Address outside the 172.16.255.XXX network.

Solution

In this case:

  1. Plug an Ethernet cable from the conveyor to an unused port on the Forge/Ctrl (e.g., LAN2).

  2. In Settings > Network, wait for another Network Interface to appear (such as "enp2s0").

  3. Configure this new "enp2s0" interface to have an IP Address and subnet that allows ForgeOS to communicate with the conveyor.