Skip to content
Ralf Steinert edited this page Nov 15, 2026 · 3 revisions

enip-sim simulates EtherNet/IP (CIP) devices that behave: an AC drive whose motor ramps to its speed reference and trips when you tell it to, an I/O block that mirrors its channels, a bare adapter to build your own on. They speak explicit messaging (unconnected and connected) and, since 0.2.0, implicit (Class 1) I/O — the cyclic exchange over UDP 2222 that a scanner uses to run a device. So you can develop and test SCADA links, HMIs, gateways or your own scanner code without a PLC or a drive on the bench, also in CI.

What it is for

  • Scanner and gateway code before the hardware is there, or while the line runs and nobody lets you touch it.
  • Running EtherNet/IP code in CI. A device starts in milliseconds, in a pytest fixture or as a Docker service container.
  • Testing the unhappy paths. Rejected Forward_Opens with the real extended status, connection timeouts, lost I/O packets, a tripped drive, late or missing answers.

Where to start

If you want to … read
run a drive over Class 1 I/O in two minutes [[Implicit I/O
put it into automated tests Testing in CI
look something up the README (reference)

Cross-checks

Explicit messaging is cross-checked in the test suite against pycomm3. Implicit I/O was cross-checked by hand against EIPScanner 1.3.0 (C++): Forward_Open and Large_Forward_Open, io-block loopback, the drive ramping at a 20 ms RPI, Forward_Close and a size rejection. Not tested against a real PLC.

Clone this wiki locally