Access Official Technical PDF

Share Summary:LinkedInEmail

Integrated motion control brings servo drives, field devices and automation controllers into a coordinated machine architecture. When those components share an open, high-speed network, engineers can reduce separate communication paths and connect motion activity with wider production data. CC-Link IE Field Network is presented as one approach, combining distributed control, synchronized motion and safety communications on a single Ethernet-based network.

For machine builders and plant teams, the practical question is not simply network speed. It is how to select the right control mode, topology and engineering approach for each axis while keeping commissioning, diagnostics and maintenance manageable.

How integrated motion control supports connected machines

A machine commonly combines servo amplifiers, motors, I/O, HMIs, inverters, temperature controllers and other devices. Integrating these components on one network can reduce the need for separate communication systems and make it easier to connect standalone machines to plant-level control.

CC-Link IE Field Network uses Ethernet technology and supports communication at 1 Gbps. The network is designed to connect field devices with controllers and support information exchange beyond the shop floor. SLMP, or Seamless Message Protocol, enables connectivity between devices at the IT level and equipment on the production floor. This can support the collection of production, quality and control data across processes, provided the application is designed to collect and use that information appropriately.

The network also supports distributed control, synchronized motion and safety communications. Combining these functions can help reduce wiring between devices and provide a common communications structure. Safety functions still depend on the appropriate supported modules and system configuration; they are not achieved simply by connecting devices to a network.

Selecting a motion control mode

The servo system can be configured for different control requirements. The distinction between motion mode and I/O mode helps match control capability to the role of each axis.

Motion mode for coordinated axes

When used with a Simple Motion module or board, motion mode supports advanced functions such as multi-axis interpolation, synchronous control, and speed-torque control. It can suit equipment that requires coordinated trajectories or synchronization, including packaging, converting, dispensing and X-Y table applications. Other functions described for the system include gantry tandem control, cam control, cam auto-generation and mark detection.

Using function blocks and positioning data can make motion commands easier to organize within the sequence program. Standardized PLCopen Motion Control function blocks are intended to make programs more consistent and easier for other engineers to understand and maintain.

I/O mode for individual positioning axes

I/O mode uses the servo amplifier’s built-in positioning function. It can be used for a single positioning axis connected through a compatible controller or master/local module, without requiring the Simple Motion module for that axis. Typical examples include a belt conveyor, rotary table or ball-screw mechanism. Position, speed and related values can be set in a point table and selected by the sequence program.

A machine may combine the modes: motion mode can coordinate its primary axes, while I/O mode handles feeding or conveying axes. That arrangement allows the control architecture to reflect the actual machine task rather than treating every axis identically.

Topology and synchronized operation

Network topology affects how equipment is connected and how a machine can be expanded. The system supports star and line configurations, as well as combinations of the two. In a star arrangement, devices connect through a switching hub; in a line arrangement, modules connect along the network path. The appropriate choice depends on the equipment layout and connection requirements.

Synchronized communication can coordinate servo commands with input and output data. For example, encoder values, sheet-tension measurements or text data can be exchanged in line with the servo amplifier’s command communication cycle. This makes synchronized handling of machine signals available for applications that need motion and process data to remain coordinated.

Engineering and diagnostics across the network

An integrated engineering environment can bring together sequence-program development, motion parameter settings, servo adjustment, debugging and network configuration. A shared workflow can reduce the need to move between separate tools for routine setup tasks. Network diagnostics can help identify communication issues, while event histories and visual displays provide information for troubleshooting.

Diagnostic and maintenance functions described for the servo system include:

  • Reading servo amplifier information through the controller network for machine diagnosis.
  • Recording servo data, such as motor current and position command, around an alarm event for later analysis.
  • Monitoring estimated friction and vibration, and tracking total motor travel distance to support maintenance planning.
  • Backing up and restoring parameters for servo amplifiers and connected I/O modules through a compatible HMI.
  • Monitoring calculated driving and regenerative power data through the engineering software.

These tools provide information for engineers to investigate machine condition and alarms; they do not replace application-specific maintenance limits, safety validation or inspection procedures.

Practical considerations for system design

Before selecting a configuration, define which axes require coordinated motion and which need only straightforward positioning. Then verify controller and module compatibility, the required number of axes and stations, and the safety components needed for the application. Motor selection also matters: the product range described includes rotary, linear and direct-drive motors, each suited to different mechanical arrangements and motion requirements.

Finally, consider how network data will be used. Connecting servo and field-device information to a host system can improve visibility, but useful monitoring depends on selecting relevant data and establishing an appropriate engineering and maintenance process.

Conclusion

Integrated motion control on an open gigabit network can bring motion, I/O and wider automation communications into a more unified machine architecture. The practical benefits depend on choosing appropriate motion and I/O modes, planning the network topology, and using engineering and diagnostic tools effectively. For system integrators and plant teams, these decisions can support simpler connectivity, clearer troubleshooting and better access to machine data across the automation system.

Access Official Technical PDF

About The Author