Designing a servo platform for a machine involves more than selecting a motor and amplifier. Motion requirements, network architecture, controller capacity and commissioning tools all influence the final system. The MELSERVO-JET servo system brings these elements together, with options for rotary and linear motors, motion modules and industrial PC-based control. Understanding how the components fit together helps engineers and integrators assess the platform against their machine requirements.
MELSERVO-JET servo system architecture
The system is built around servo amplifiers, servo motors and a controller, supported by engineering software and related factory automation devices. The MR-JET-G amplifier connects through CC-Link IE TSN, while the MR-JET-G-N1 model supports EtherCAT. For EtherCAT configurations, an EtherCAT-compatible master module is required.
For CC-Link IE TSN systems, Mitsubishi Electric lists MELSEC iQ-R motion modules RD78G and RD78GH, as well as SWM78 Motion Control Software for an industrial personal computer (IPC) with a real-time operating system. The controller choice affects the supported axis count, operation cycle and programming environment, so it should be made in light of the application’s motion demands and system architecture.
Motion control and controller options
The motion controllers support positioning, synchronous, cam, speed and torque control. The RD78G family covers configurations from four to 64 axes per module, while RD78GH variants are specified for up to 128 or 256 axes per module. When MR-JET-G amplifiers are used for all axes, the maximum number of control axes is limited to 120. The listed minimum operation cycles are 62.5 microseconds for RD78G and 31.25 microseconds for RD78GH; connecting an MR-JET-G changes the minimum cycle to 125 microseconds.
Controllers can also distribute work between the PLC CPU and motion module. A PLC-only program can be suitable for users who want to manage motion through the CPU. For applications requiring more demanding or complex motion processing, programs can run on both the PLC CPU and motion module. This arrangement lets the motion module handle calculations and control tasks, reducing the processing burden on the CPU.
SWM78 offers a different approach: motion and network control are performed by software installed on an IPC running the INtime real-time operating system. Programming uses Visual C++, and its API library follows the interface of PLCopen Motion Control Function Blocks. The source describes SWM78 as “Available soon,” so project teams should confirm current availability and requirements before planning around it.
Network design with CC-Link IE TSN
CC-Link IE TSN uses Time Sensitive Networking to support deterministic industrial communication alongside TCP/IP information traffic on the same network. The source specifies a communication speed of 1 Gbps. In the described architecture, control communications receive priority, allowing compatible TCP/IP devices to share the network without interrupting cyclic control communication.
This can support an integrated shop-floor network for motion control, I/O and information exchange, rather than relying on separate networks for every communication need. The system can also carry production, quality and control data, including large recipe or traceability files. However, network layout details matter: the source specifies that TCP/IP devices must be connected after servo amplifiers and I/O modules. It also identifies some functions and device connections as planned for future support, so those items should not be treated as currently available without verification.
Servo motors, performance and machine fit
The listed rotary motor families are HG-KNS and HG-SNS. HG-KNS motors are small-capacity, low-inertia models rated from 0.1 to 0.75 kW; HG-SNS models are medium-capacity, medium-inertia units rated from 0.5 to 3.0 kW. Both families use a 22-bit absolute-position encoder. A battery is required when configuring an absolute-position detection system. The source also notes that the motors use the same dimensions and power and encoder cables as the prior HG series.
For the servo system, the published headline specifications include a 2.5 kHz speed frequency response, 22-bit encoder resolution and maximum torque of 300%. Actual motor speed varies by model. Linear motor options include LM-H3 and LM-AJ series, with the source identifying applications such as mounters, wafer cleaning systems, semiconductor manufacturing equipment and compact X-Y tables. Selection should account for the axis mechanics, required thrust, travel profile and machine layout rather than relying on a headline figure alone.
Engineering tools for setup and troubleshooting
MELSOFT GX Works3 provides an environment for system configuration, programming, debugging and maintenance. It supports structured text and other PLC programming methods, along with PLCopen motion function blocks. Shared labels can make axis and I/O information easier to reference between motion modules and PLC CPUs.
For system planning, Motorizer supports motor sizing, including multi-axis sizing and a range of load mechanisms. Model selection software helps identify amplifiers, motors and options such as encoder cables. During commissioning and maintenance, monitoring functions, event history and data logging can help teams examine system behavior. The Motion module’s servo system recorder automatically collects command and feedback data from drive axes when an error occurs, supporting investigation of faults across the axes.
Practical considerations for project teams
Before specifying the system, engineers should align the controller and network choice with axis count, required cycle time and programming approach. They should also validate motor and amplifier combinations, the need for absolute-position batteries, and the application’s mechanical requirements. Where planned features are relevant, confirm their release status and compatibility as part of the design process.
The practical value of the MELSERVO-JET platform lies in treating drives, motion control, networking and engineering as connected design decisions. A clear understanding of each component’s limits and role can help teams build a system suited to the machine, commission it efficiently and troubleshoot motion issues with better access to relevant data.