The ADLINK Motionnet series of direct insertion single axis motion control modules (MNET-J3, MNET-S23, MNET-MIA, etc.) are designed for multi axis point-to-point motion applications. Through an innovative direct insertion structure, they are directly installed on the CN1 communication port of the corresponding brand servo drive, without the need for traditional terminal boards, greatly saving control cabinet space and reducing wiring workload. Each module is compatible separately Mitsubishi J3A/J4A(MNET-J3)、Yaskawa Sigma V(MNET-S23)、Panasonic MINAS A4/A5(MNET-MIA)、Delta A2(MNET-DA2) And Sanyo R series (MNET-SAN). The modules are connected in series through standard LAN cables (CAT5/CAT5e STP) to form the Motionnet bus. A single master station can support up to 64 modules (64 axes) with a scanning cycle of only 0.97 ms (20 Mbps full load 64 axes). This article is based on the product data manual, systematically sorting out the correspondence between various models, hardware installation and ID settings, communication connections, I/O wiring, motion performance, and common troubleshooting, providing a quick deployment guide for automation engineers.
Corresponding relationship between product family and servo drive
Motionnet single axis module adopts the design concept of "one module, one axis". Each module is directly inserted into the CN1 port (command input interface) of a servo driver, receives motion commands from the master station (such as PCI-7856) through the serial bus, and returns encoder feedback and I/O status. The CN1 pin definition and communication protocol of different brands of servo drives vary, so modules are differentiated by driver brand and model:
Model compatible servo drive series description
MNET-J3 Mitsubishi MR-J3A/MR-J4A Mitsubishi J3/J4 series universal
MNET-S23 Yaskawa Sigma V (SGDV series) Yaskawa Sigma V series
MNET-MIA Panasonic MINAS A4/A5 Panasonic A4/A5 series
MNET-DA2 Delta ASD-A2 Series Delta A2 Series
MNET-SAN Sanyo R Series Sanyo R Series
Selection key: It is necessary to select the corresponding Motionnet module based on the brand and model of the servo drive used on site. Mixing will result in communication failure or hardware damage. The module size is only 52.4 × 16.3 × 69.5 mm, weighing about 50g, and can be directly embedded in the front end of the driver without occupying additional DIN rail space.
Hardware installation and physical connection
2.1 Module installation steps
Power off operation: Before installation, be sure to cut off the power supply to the servo drive and main station.
Align the CN1 interface: Align the 50 pin (or corresponding) connector of the module with the CN1 command input port of the servo drive, ensuring the correct direction (there is a foolproof design on the module).
Locking fixing screws: Use matching screws to secure the module to the driver, ensuring reliable electrical contact and preventing vibration loosening.
Connect Motionnet bus:
Use CAT5e or CAT6 STP shielded Ethernet cables to connect the module's CN2 (or HS1) to the previous module or main station, and CN1 (or HS2) to the next module (or end).
The RS-485+and RS-485- pins of the module are used for serial data communication (see pin allocation table for details).
2.2 Communication Connection Topology
Motionnet adopts a multi station serial daisy chain topology, where the MNET port of the main station (such as PCI-7856) is connected to the first module and sequentially connected to the last module. The terminal module needs to enable terminal resistors on the hardware (some modules can be set through dialing or jumper, please refer to the manuals of each module for details).
Key constraints:
Maximum number of modules: 64 (corresponding to 64 axes)
Bus length: 32 modules up to 100m at 20 Mbps, 64 modules up to 50m (64 modules can reach 100m at 10 Mbps)
Minimum cable length: 0.6m (to avoid signal reflection)
Shielded Ethernet cables must be used, and the shielding layer must be grounded at one end (usually on the main station side)
Communication and ID settings
3.1 Slave Station ID (Station Number)
Each Motionnet slave module must have a unique station number (ID 0~63) on the bus. The ID is usually set through the rotary dip switch or DIP switch on the module. For example, some modules use a combination of two BCD dip codes (ten digit and one digit), or binary dip codes (S1). Please refer to the quick guide attached to the module for specific setting methods, but the principles are as follows:
IDs on the same bus cannot be duplicated, otherwise there will be communication conflicts.
The main station identifies each module through an ID, so it needs to be consistent with the actual dialing value in the program configuration.
Suggest assigning IDs in physical order (such as 0, 1, 2...) for easier management and debugging.
3.2 Communication speed
The communication rate is uniformly set by the main station, and the module adapts through S2 dialing or automatic adaptation. Common speed:
20 Mbps (default, high speed, suitable for fewer axles and shorter cables)