Skip to content
Version 2026.25

Finding devices ​

Find devices looks for PLCs and controllers on the networks Nexus is connected to and lists what answers. You pick the ones you want, and each one becomes an ordinary device connection, the same as one you typed in under Devices → Add. It applies straight away, with no restart.

Finding devices only adds device connections. It never creates tags or screens: bind tags to a device in Studio as usual.

What it can find ​

Kind of deviceHow Nexus asksWhat it learns
EtherNet/IP (Allen-Bradley and others)One List Identity broadcast, UDP port 44818Vendor, device type, product name, revision, serial number
BACnet/IPOne Who-Is broadcast, UDP port 47808Device instance and vendor number
Modbus TCPTries each address in a range you enter, TCP port 502Vendor, product code and revision when the device supports Read Device Identification; otherwise only that it answered

OPC UA servers are not searched for. Add them by endpoint under Devices → Add.

The EtherNet/IP and BACnet searches send one broadcast to each network Nexus is on and wait for answers. Nothing is scanned. Modbus has no broadcast, so a Modbus search connects to every address in the range you give it, one short connection each. It only runs when you enter a range and press Search, and the range can be no larger than a /24 (254 addresses).

Find devices ​

  1. Open Devices in the configuration interface and press Find devices. On a new gateway, a banner at the top of the page offers the same button until someone uses it or presses Dismiss.
  2. Tick what to look for. EtherNet/IP and BACnet/IP are ticked to start.
  3. For Modbus TCP, enter the address range, for example 192.168.1.0/24.
  4. To search a routed network as well as the ones Nexus is on, choose Search another network too and enter its broadcast address, for example 10.20.0.255. Routers often do not forward broadcasts, so this works only where yours does.
  5. Press Search. A broadcast search takes about two seconds; a full /24 Modbus range can take up to ten.

Each result shows its address, what it said about itself, and a name suggestion. A device that is already a device connection on this gateway is marked Already added and starts unticked.

Two kinds of result are listed but start unticked, because adding them is probably not what you want:

  • An EtherNet/IP device that is not a controller, such as a drive or an I/O adapter. The Allen-Bradley driver reads controller tags.
  • A Modbus address that accepted the connection but never answered Modbus ("Port open, no Modbus reply"). Something listens on port 502 there, but it may not be a Modbus device.

You can tick either kind if you know better.

Add what you found ​

There are two ways, and both end in the same device connection.

Add selected adds every ticked device in one go with the suggested settings. Edit a name in the list first if you like. Before anything is added, every ticked row is checked: if a name you typed is already in use, or a row's settings would be refused, that row is marked, nothing is added, and you can fix it or untick it and press Add selected again. A suggested name that is already taken is given a number instead (PLC-2).

Review… on one row closes the list and opens the normal Add form with that device filled in. Change anything you need, then press Add device. Use this when the defaults are not right, for example:

  • EtherNet/IP: devices are added as a ControlLogix on path 1,0, except a Micro800 found by the scan, which is added with no path (it takes none). For a MicroLogix, or a controller behind a different backplane slot, set the PLC type and path here. See Devices and drivers.
  • Modbus TCP: devices are added with unit ID 1. Set the real unit ID and the word order your device uses.

If the license's device limit is reached partway through Add selected, the devices before it are added and the rest are marked with the reason.

Who can use it ​

Finding devices needs the same permission as adding a device: an account that can change the gateway configuration (the Admin role, unless you have changed the roles). It works under every security profile, including Hardened: a search only happens when an administrator starts one.

Every search is written to the audit log as DEVICE_DISCOVERY, with who ran it, the kinds of device searched for, the Modbus range and extra broadcast address if any, and how many devices answered. At most two searches run on a gateway at once; a third is refused with "Two searches are already running".

When nothing is found ​

  • Check that the devices are powered on and on a network Nexus is connected to. The search starts from Nexus, not from your browser.
  • Broadcasts do not cross routers unless the router is set up to forward them. Use Search another network too, or add the device by address under Devices → Add.
  • Answers to a broadcast come back to Nexus on UDP. A firewall on the Nexus computer that drops incoming UDP can hide every EtherNet/IP and BACnet answer even though the devices replied. Modbus searches are not affected.
  • Some devices are set not to answer identity requests. Add those by address.

The banner is remembered by the gateway

Whether the Find devices on this network banner has been used or dismissed is stored in device_discovery_state.json in the data directory, so it stays gone for every administrator and every browser. Delete the file to bring the banner back.