ADLINK MNET-J3/S23/MIA/DA2/SAN Single Axis Module Installation and Wiring Guide



ADLINK MNET-J3/S23/MIA Single Axis Motion Module Installation and Wiring Guide

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)

10 Mbps/5 Mbps/2.5 Mbps (selected for long-distance or high anti-interference requirements)

The speed of the master station and all slave stations must be consistent, otherwise they cannot connect.

3.3 Communication status indication

The red LED indicator on the module displays the 3.3V internal control power status:

Always on: Module power supply is normal (provided by+5V or+24V of servo driver CN1)

Off or flashing: abnormal power supply or module failure

Some modules also have communication status LEDs (such as green flashing indicating normal communication, and constant light indicating connection), please refer to the corresponding manual for details.

I/O interface and pin definitions (CN1/CN2/CN3)

Taking MNET-J3 as an example, the pin allocation is as follows:

4.1 CN1/CN2 (serial communication)

Pin Name Function Direction

1 RS485+serial communication data+I/O

2 RS485- Serial Communication Data - I/O

3 FG frame grounding (shielding)-

These two ports are used for bus cascading, with CN1 connected to the previous level and CN2 connected to the next level (or vice versa, depending on the module type).

Use standard RJ-45 connectors (8P8C), but only use 4/5 pins (DATA -/DATA+), leaving the other pins reserved.

4.2 CN3 (I/O signal)

Pin Name Function Direction

1 PEL forward limit input

2 MEL negative limit input

3 SD/CPP deceleration input/comparator output (+) I/O

4 ORG origin input input

5 EMGI emergency stop input

6 CPN comparator output (-) output

7 24V 24V power input (external I/O power supply) input

8 GND 24V power supply ground-

9 GND signal ground-

10 FG frame grounding-

Signal Explanation:

PEL/MEL: Positive/negative overtravel limit, usually using normally closed (B-type) contact switches, with a wiring capacity of 24V/6mA. Software can configure logical polarity.

ORG: Origin signal, used for zeroing mode. Supports normally open/normally closed configuration.

EMGI: Emergency stop input, external normally closed contact, triggering the module to immediately stop pulse output (emergency stop can be enabled/disabled by software).

SD/CPP: Dual function pin - can be used as a deceleration input (SD) to decelerate in advance when approaching the limit; It can also be used as the positive output (CPP) of a position comparator to trigger external devices.

CPN: The negative output of the comparator (differential pair CPP/CPN) needs to be used in conjunction with CPP.

Attention to I/O power supply:

The module is usually powered internally (5V/3.3V) by servo driver CN1, but external I/O (limit switches, origin, etc.) require an external 24V power supply, which is connected through CN3's 24V and GND. Make sure to confirm that the 24V power supply capacity meets the total current of all input circuits (usually 6-10mA per switch).

Motion control performance

This series of single axis modules supports the following motion characteristics (implemented by Motionnet main station and APS function library):

Pulse output frequency: No instruction frequency limit (actually limited by Motionnet communication rate and scanning period)

Scanning cycle: Approximately 0.97 ms (theoretical value) at full load of 64 axes at 20 Mbps, ensuring fast response

Acceleration and deceleration types: linear (T-curve) and S-curve (S-curve), with programmable parameters

Sports mode:

Single axis relative/absolute positioning

Single axis speed mode (Jog or continuous operation)

Return to zero (multiple modes, supporting limit+origin+encoder index combination)

Support position/speed coverage (on the fly change)

Feedback: Closed loop position monitoring is achieved through servo drive encoder signals (read by the module and transmitted back to the main station)

Since the module itself does not have an independent CPU, all interpolation operations and trajectory planning are completed by the main station, and the module only executes the received pulse instructions. Therefore, this series of modules does not support multi axis interpolation (line/arc interpolation) and is only suitable for point-to-point (PTP) independent axis motion. If interpolation function is required, the 4-axis module MNET-4XMO should be selected.

Debugging and Configuration (MotionCreatorPro 2)

Similar to MNET-4XMO, this series of modules is also configured and tested through MotionCreatorPro 2 software:

After installing the driver on the main station (such as PCI-7856), open MotionCreatorPro 2.

Click on Field Bus Connect, select Motionnet and baud rate.

The system automatically scans all slave IDs and displays a list of online modules.

For each module, the following can be done:

Axis parameter settings: acceleration and deceleration time, start stop speed, curve type, limit logic, electronic gear, etc.

Single axis motion test: relative/absolute positioning, Jog motion, zeroing.

I/O monitoring: Check the status of PEL/MEL/ORG/EMG and force output comparison signals.

Error code query: When the motion is abnormal, check the returned error code (refer to the APS function library manual).

Common troubleshooting and solutions

7.1 Module unable to connect or communication interrupted

Check power supply: Confirm that the servo drive is powered on and whether the CN1 interface has 5V/24V output. If the Power LED is not on, the module is not powered on.

Check for ID conflicts: Confirm that the station numbers of all modules are unique and there should be no duplicate IDs in the scanning list of the main station.

Check baud rate: The rate set by the master station and module is consistent.

Check the Ethernet cable: Use standard shielded Ethernet cable (CAT5e STP) and ensure that the terminal module has enabled terminal resistors. If the cable exceeds the specified length, try slowing down to 10 Mbps.

Check topology: Confirm it is a daisy chain with no branches or loops.

7.2 Motor not rotating or abnormal positioning

Check if the command has been issued: Execute a single axis motion in MotionCreatorPro 2 and observe the changes in the command counter. If there is no change, check the return value of the function call.

Check servo enable (SVON): Confirm that the servo drive is in the Servo On state (which can be controlled through the drive panel or external input).

Check the limit switch: If PEL or MEL is triggered (and the limit logic configuration is correct), the movement is prohibited. Limit testing can be forcibly ignored through software (only during debugging).

Check the electronic gear ratio: Confirm that the PRA-EGEAR parameter is set correctly to avoid too few pulses causing unclear movement.

Check wiring: Although the direct insertion module reduces external wiring, it is still necessary to confirm that the CN1 interface of the servo drive is not damaged (such as bent pins).

7.3 Inaccurate zeroing position

Check ORG signal logic: Confirm that the normally open/normally closed setting matches the actual switch type.

Check zeroing mode: Some modes require the combination of EZ (encoder index) signal to confirm whether the servo driver outputs EZ signal and is correctly connected to the module.

Reduce crawling speed (PRA_CRV_SPEED): Improve stopping position accuracy.

Check the mechanical coupling: if there is slippage, the repeatability of returning to zero is poor.

7.4 Trigger output invalid (using CPP/CPN)

Confirm that the module supports the comparison output function (both MNET-J3/S23/MIA support it).

Check if the comparator enables setting and comparing position values within the motion range.

Measure the differential voltage between CPP and CPN using an oscilloscope to confirm whether the pulse width and polarity meet the requirements.

Note that CPP/CPN is a differential signal (similar to RS-422), and the receiving end needs to support differential input.

7.5 Limit or origin signal no response

Check if the 24V and GND of CN3 are correctly connected to the external power supply.

Measure the voltage of PEL/MEL/ORG pins to GND with a multimeter, and a level change should occur when the switch is triggered (logic configured by software).

Confirm that the logic polarity (NH/NL) in MotionCreatorPro 2 is consistent with the actual switch.

Maintenance and spare parts recommendations

Regular inspection of network cable connectors: RJ-45 locks are prone to loosening in vibration environments, and it is recommended to use industrial grade network cables with locking screws.

Cleaning module gold fingers: If disassembly is required, wipe the CN1 interface gold fingers with alcohol to prevent oxidation and poor contact.

Backup module: For critical production lines, it is recommended to reserve 1-2 modules of the same model, which can be replaced within 5 minutes in case of failure (ID reset is required).

Configuration file backup: Backup the parameter files (. ini) for each axis in MotionCreatorPro 2 to the cloud, and quickly restore them after replacing the module.