STOBER adds EtherNet/IP support for the SB6, SC6, and SI6 drive controllers

They combine standardised communication with Drive Based Motion functions: The higher-level controller communicates via EtherNet/IP, while the drive controller performs the actual motion function. This lets mechanical engineers offload motion control tasks from the controller.

"We are consistently expanding the integration of our system solution with control systems worldwide, thereby tapping into new markets," says Daniel Lohse, Director of Business Development for EMEA at STOBER. "EtherNet/IP is more than just another interface: It combines open machine communication with decentralised motion intelligence."

The open standard expands the range of applications: Drive controllers can now also be integrated into control environments that communicate via EtherNet/IP. Among other applications, the protocol is widely used in controllers from Rockwell Automation (Allen-Bradley brand) and Schneider Electric. The EtherNet/IP interface of the drive controllers is ODVA-certified.

According to HMS Networks' 2026 Market Analysis, EtherNet/IP, PROFINET, and EtherCAT together account for about three-quarters of the market for wired protocols. "EtherNet/IP is the dominant protocol in North America and the second-largest in factory automation worldwide, and its market share is growing," Lohse notes. "This makes our drive controllers attractive to European companies that export to that region, as well as for local mechanical engineering applications - for example, in the food, packaging, material handling, logistics, and medical technology sectors."

The controller says what to do - the drive controller says how

The machine and process logic remain in the controller. It transmits set values and motion commands to the drive controller via EtherNet/IP in accordance with PLCopen Motion Control. Its Drive Based Motion application controls position, velocity, torque, and force.

"The controller specifies what the axis should do. The drive controller determines how the motion is executed," says Matthias Meyering, Technical Product Manager at STOBER. "Drive Based Motion is therefore particularly worthwhile for machines whose controllers are not intended or required to perform extensive motion control tasks. This is an attractive architecture for single axes and decentralised axes." In this way, the drive controller itself becomes a motion controller.

Drive Based Motion is particularly well-suited for modular machines consisting of independent functional units. In a single module, the drive controller can handle more of the motion function. Essentially, the controller exchanges commands and process data with the drive controller. The module's axis functions remain clearly separated. Furthermore, because the motion function is not programmed into the controller, it depends less on how the specific controller implements motion control. This makes it easier to reuse drive solutions and integrate axes into different machine designs.

A separate path for safety

The division of responsibilities remains transparent for functional safety as well. As a safety function, the drive controllers offer Safe Torque Off (STO), which safely interrupts the energy supply to the motor that generates torque. They implement STO via digital inputs, independently of EtherNet/IP. To this end, the SB6, SC6, and SI6 can be equipped with the optional STOBER SR6 safety module.