FoundryNet / Error codes / EtherNet/IP 0x16
EtherNet/IP error code

0x16 (0x16) — Object does not exist

The specified object class is not implemented on this device at all.

Start free EtherNet/IP → canonical

Diagnosis

When you hit this


Resolution

How to fix it

  1. Read the Identity object first
    Class 0x01 is mandatory on every CIP device and tells you vendor, product code, and revision — enough to look up what else exists.
  2. Consult the EDS file
    The device's EDS enumerates supported classes. It is the authoritative answer to whether an object exists.

Normalization

What Forge does about it

This is a configuration or addressing mistake on the wire, upstream of anything Forge sees. Where Forge helps is the step after you fix it: once the point returns data, its vendor tag name maps to a canonical field automatically, so you do not also have to hand-maintain a name table for every point you just re-addressed.


Connect

Normalize EtherNet/IP telemetry

One MCP endpoint serves every protocol adapter. 16,908 curated mappings, 366 canonical fields.

# normalize telemetry from EtherNet/IP — and 13 other protocols
claude mcp add --transport http forge https://mcp.foundrynet.io/mcp \
  --header 'Authorization: Bearer YOUR_FORGE_KEY'
✓ forge connected — 32 tools available

Related

Keep reading

Other EtherNet/IP codes: 0x01 0x04 0x05 0x08

Equipment that speaks EtherNet/IP: ABB Robotics KUKA Fanuc Robotics Yaskawa Motoman Doosan Robotics Epson Robots Kawasaki Robotics Mitsubishi Omron Robotics Techman Robot

EtherNet/IP protocol hub

Other protocols: Modbus OPC UA MQTT / Sparkplug B FANUC FOCAS PROFINET / S7 BACnet/IP J1939 (CAN) MTConnect ROS 2 (DDS) SNMP MAVLink HTTP / REST CSV ingest

All error codes · All OEMs · All protocols

Industrial AI fails at the data layer. The Machine Agent explains why, weekly. Read it →
Get the thesis behind this infrastructure — The Machine Agent, weekly.