With which programming languages can development be done for Ethernet/IP?

Start with the communication task
EtherNet/IP development can use C, C++, Python, Java, C# and JavaScript. On PLC platforms, LD, ST and FBD are relevant; for testing and modeling, LabVIEW and MATLAB/Simulink can also be options with suitable components. Language familiarity is one consideration. The device's access method, the application's network role and its timing requirements determine what the solution must support.
Editor's note: Reading PLC tags, managing cyclic I/O connections and developing EtherNet/IP device firmware are three different tasks. A library that reads tags does not necessarily provide scanner or adapter functions. EtherNet/IP devices also do not all expose data through symbolic tags in the same way as Logix controllers.
Establish the protocol role and data model first
Explicit messaging can access parameters, diagnostics or tags through supported services. Implicit I/O exchanges cyclic data through configured connections. Scanner and adapter roles must match the functions supported by the target device. Opening a TCP socket alone does not implement EtherNet/IP sessions and CIP services. The distinction between network layers and the application protocol matters here.
C and C++: embedded devices and protocol stacks
C and C++ can be used for device firmware, communication components and control applications on appropriate platforms. A protocol stack or SDK handles sessions, connections and CIP objects. For example, the C-based OpENer stack targets I/O adapter devices and supports explicit and I/O connections. That scope does not automatically make it a scanner solution.
Embedded projects require assessment of memory, processor resources, operating system interfaces, timing and license terms. Developers must also map application I/O data to CIP objects. Compiling a stack does not establish that the product has passed conformance testing. Assess the relevant standards and conformance requirements separately when developing a device for sale.
PLC languages: LD, ST and FBD
On suitable PLC platforms, Ladder Diagram (LD), Structured Text (ST) and Function Block Diagram (FBD) can implement machine logic and communication-related functions. The controller's communication infrastructure generally handles cyclic I/O connections, while the application uses mapped data. Supported explicit messages can be invoked through vendor-specific instructions or function blocks.
For example, CODESYS EtherNet/IP Scanner is an additional option for compatible controllers and is configured in the development environment. Verify the controller model, runtime components and license. Configuration involves the EDS, connection points, I/O sizes and data mapping. A PLC's ability to execute ST does not establish that it supports an EtherNet/IP scanner.
C# and Java: PC applications and data integration
C# can be suitable for data collection services, user interfaces and SCADA integration. .NET is a development platform; .NET Framework is a separate, Windows-focused product family. Modern .NET can target multiple operating systems, provided the selected EtherNet/IP SDK and native dependencies support them. The libplctag project offers C#/.NET wrappers alongside its C core.
Java can support data services and enterprise integration applications running on industrial computers. For example, libplctag4j is an actual Java wrapper around the underlying C library and uses JNA components. Check the operating system, processor architecture and native library version alongside the Java version. Writing the application in Java does not guarantee that its SDK works on every platform.
Python: testing, logging and supported tag access
Python can be used for logging, test automation and prototypes. pycomm3's LogixDriver provides tag access on supported Logix controllers. It should not be treated as a universal I/O scanner for all EtherNet/IP products. Assess driver support for the controller family, firmware, data types and required operations.
The following example reads one tag from a suitable ControlLogix or CompactLogix system. Install the package in a compatible Python environment with python -m pip install pycomm3, then replace the IP address, CIP route and tag name with values from the actual project. Here, backplane/0 identifies backplane slot 0; controller routes are not all identical.
from pycomm3 import LogixDriver
plc_path = "192.168.1.10/backplane/0"
tag_name = "TemperatureSensor"
with LogixDriver(plc_path) as plc:
result = plc.read(tag_name)
if not result:
raise RuntimeError(str(result.error))
print(f"{result.tag}: {result.value} ({result.type})")
TemperatureSensor must already exist in the PLC and permit external reading. The library does not create the tag or the physical sensor. The code checks the result's error status, and the with block closes the connection on exit. The example does not write application data and has not been run against a physical PLC. A continuously running service also needs reconnection, logging and error handling.
JavaScript and Node.js: the service behind a web interface
Node.js can implement a data collection service using a suitable EtherNet/IP library. Its TCP API provides transport functionality; CIP operations still require protocol support. Assess port and traffic requirements for the functions used. Ordinary browser JavaScript cannot open arbitrary TCP/UDP sockets directly to a PLC. A web interface can instead communicate with a backend service over HTTP or WebSocket, with that service handling PLC communication.
LabVIEW: connecting a test system to a PLC
LabVIEW uses graphical programming to build test and measurement applications. NI-Industrial Communications for Ethernet/IP provides a Class 1 adapter role, explicit messaging and I/O data communication on compatible systems. A cyclic connection requires a suitable scanner at the other end. The NI driver's adapter function should not be interpreted as general implicit I/O scanner support. Check hardware, LabVIEW version and operating system compatibility together.
MATLAB and Simulink: identify the actual interface
MATLAB and Simulink can support analysis, modeling and testing; EtherNet/IP connectivity depends on the selected integration. The OPC UA, OPC Classic HDA, Modbus, MQTT and PI support listed for Industrial Communication Toolbox does not establish direct EtherNet/IP scanner support. Modbus TCP and EtherNet/IP are also different application protocols.
One concrete example of direct connectivity is Simulink Real-Time with suitable Speedgoat hardware. Speedgoat offers scanner or adapter solutions through the relevant I/O modules and Simulink blocks. Alternatively, data can be obtained through a supported OPC server or middleware. With that approach, the MATLAB-facing protocol can differ from the PLC-facing protocol.
Timing and data quality matter as much as the language
A fast polling loop alone does not provide guaranteed real-time control. Operating system scheduling, runtime behavior, network load and device capacity affect latency and update intervals. Choosing C/C++ alone does not guarantee timing either. Tasks with strict cycle requirements need suitable controllers, real-time infrastructure and validated communication components.
Map data types, scaling, array lengths and byte order correctly. Distinguish the last successful value from a new reading, and avoid presenting stale data as valid after a timeout. Diagnostics and error logs help separate connection problems from data mapping errors. For write operations, assess supported security capabilities alongside access controls and network segmentation.
Which option should you start with?
Collecting production data from a PLC may call for a suitable Python, C#, Java or Node.js driver. Managing cyclic field I/O requires a scanner-capable controller or SDK. Developing a new field device brings an adapter stack and product testing into focus. In industrial applications, this task distinction should guide the initial choice.
For example, on a packaging line, a service recording production counts in a database performs a different job from the controller managing cyclic remote I/O. Validate supported services, reconnection behavior, version compatibility, maintenance and licensing in a small trial project to turn the language choice into a concrete engineering decision.
Sources
OpENer: C-based I/O adapter stack
ODVA: product conformance testing
CODESYS: scanner functions and controller requirements
Microsoft: the .NET platform and runtime
libplctag: C library and language wrappers
libplctag4j: Java, JNA and native libraries
pycomm3: connection paths, sessions and error status
pycomm3: LogixDriver tag reading API
Node.js: TCP client and server API
NI: Class 1 adapter and messaging support for LabVIEW