Yaskawa Sigma II Series NS300 DeviceNet Application Module Deep Technical Guide



Yaskawa Sigma II Series NS300 DeviceNet Application Module Deep Technical Guide

Introduction: Communication Hub in Industrial Automation

In modern industrial automation control systems, fieldbus technology is the core for achieving efficient and real-time data exchange between devices. As a leader in the field of motion control, Yaskawa Electric's Sigma II series servo drives are widely used in various precision machinery due to their excellent performance. In order to seamlessly integrate Sigma II series servo drives into the open DeviceNet industrial network, Yaskawa has launched a dedicated application module - NS300 (JUSP-NS300/JUSP-NS300-E).

This article is based on the official operating manual of Yaskawa (TOB-C718-6C), providing a comprehensive and in-depth analysis of the technical details of the NS300 module. From unboxing inspection, hardware installation, electrical wiring specifications to network topology design, we will provide you with a detailed professional guide aimed at helping engineers build a stable, efficient, and internationally compliant DeviceNet motion control system.

The cornerstone of safety regulations and operating environment

Establishing safety awareness is the first criterion for engineering implementation before starting any hardware operations. As an extension component of servo drives, the NS300 module's operating specifications directly affect personal safety and equipment lifespan.

1.1 Warning of danger level

The manual defines clear hazard level markings, and engineers must strictly identify:

Warning: Refers to a danger that may result in death or serious injury. For example, opening the terminal cover while powered on may result in electric shock; Failure to cut off the power and wait for 5 minutes (capacitor discharge) before maintenance may result in residual charges causing electric shock.

CAUTION: Involving minor injury or equipment damage. For example, incorrectly connecting a three-phase power supply to the output terminals (U, V, W) can result in fire or equipment damage; Touching the heat sink during operation may cause burns.

1.2 Special considerations for transportation and storage

The manual specifically mentions the precautions for insect and anti-corrosion treatment. If insect proof treatment is required for packaging wood, fumigation methods must be avoided, especially disinfectants containing halogens (chlorine, fluorine, bromine, iodine). These gases may corrode capacitors in electronic components, leading to product failure. Recommend using heat treatment (core temperature of 56 ° C for at least 30 minutes). In addition, the storage environment should be maintained between -20 ° C and+85 ° C to avoid physical damage to electronic components from extreme environments.

Hardware composition and interface analysis

The NS300 module, as a communication interface expansion unit for SGDH SERVOPACK, has a compact and functional interface design. A thorough understanding of the functions of each component is a prerequisite for proper wiring.

2.1 Key component description

Ground terminal: Connect to the terminal labeled "G" on the SGDH driver to ensure the equipotential connection between the module and the ground, which is the basis for anti-interference.

Rotary Switches:

× 1, × 10: Used to set the physical address of the DeviceNet node. This mechanical setting method ensures that even in the event of a power outage, the node address will not be lost.

DR: Used to set the baud rate for DeviceNet communication.

RS-232C communication interface (CN11): used to connect NSxxx setting tools for local parameter configuration and debugging.

LED indicator light (MS/NS):

MS (Module Status): Module status indicator, used to determine whether the module itself is powered on and running normally.

NS (Network Status): Network status indicator used to determine whether the module has successfully connected to the DeviceNet network and communication quality.

DeviceNet Communication Interface (CN6): The core interface used to connect to the main or branch lines of the DeviceNet network.

External communication interface (CN4): used to connect external I/O signals and fully closed-loop encoder signals.

2.2 Model Naming Rules

The suffix "E" in model JUSP-NS300-E represents compliance with the RoHS directive (restricting the use of certain hazardous substances in electronic and electrical equipment), reflecting Yaskawa's emphasis on environmental compliance.

Installation process and thermal management design

The NS300 module needs to be directly installed on SGDH SERVOPACK. Proper installation not only affects mechanical stability, but also directly affects heat dissipation efficiency.

3.1 Detailed explanation of installation steps

Remove the protective cover: Remove the connector cover on the SGDH drive CN10 interface.

Module docking: Insert the NS300 module vertically into the CN10 interface to ensure that the connector is fully compatible.

Grounding connection: This is the most crucial step. The ground wire of the NS300 module must be connected to the terminal labeled "G" on the SGDH driver.

Screw fastening: Depending on the driver model, use the accompanying M3 or M4 screws to secure it. The manual emphasizes that for rack mounted drives, spring washers and flat washers must be used, otherwise the grounding screw may protrude from the back of the flange, hindering the smooth installation of the drive.

3.2 Environmental thermal management and spacing control

Servo drives are high-power power electronic devices, and thermal management is crucial. After installing the NS300 module, the overall thermal design of the drive should follow the following principles:

Vertical installation: The driver must be installed perpendicular to the wall to ensure natural air convection.

Installation spacing:

Up and down space: Reserve at least 50mm of space to facilitate air circulation.

Left and right spacing: When installed side by side, modules should have a spacing of at least 10mm between them.

Cabinet environment: Cooling fans need to be installed inside the control cabinet to ensure that the ambient temperature does not exceed 55 ° C. It is recommended to maintain long-term reliability below 45 ° C.

DeviceNet Network Topology and Cabling Specification

This is the core part of this technical guide. DeviceNet, as a fieldbus based on CAN bus, has extremely high requirements for signal integrity in its physical layer design. Incorrect wiring is the main cause of communication interruption, packet loss, or device failure.

4.1 Network Topology Structure

The DeviceNet network consists of trunk and branch lines, supporting T-shaped branch and multi branch hybrid topologies.

Node: As a node on the network, the NS300 module can be either a master station or a slave station. The network supports a maximum of 64 nodes (addresses 0-63).

Terminal resistors: In order to eliminate signal reflection, terminal resistors must be installed at both ends of the main line. This is the most easily overlooked but crucial rule. Lack of terminal resistance can cause waveform distortion in communication, especially in high-speed communication (500kbps).

4.2 Connector Interface Definition (CN6)

NS300 adopts a 5-pin open connector, and the pin definition strictly follows the ODVA standard:

Pin 1 (V -, Black): 0V communication power supply

Pin 2 (CAN L, Blue): CAN low-level signal line

Pin 3 (SHIELD, Drain): Shielding layer connection

Pin 4 (CAN H, White): CAN high-level signal line

Pin 5 (V+, Red): 24V communication power supply

Attention: The communication power supply must be independently provided by an external source, and the control power supply of the servo drive cannot be borrowed to avoid power noise interference with the communication bus.

4.3 Cable selection and length limitations

DeviceNet cables are divided into thick and thin cables, and the selection directly determines the maximum coverage range of the network.

Baud rate, maximum length of coarse cable, maximum length of fine cable, total branch length limit

500 Kbps 100 m 100 m 39 m

250 Kbps 250 m 100 m 78 m

125 Kbps 500 m 100 m 156 m

Coarse cable: With low signal attenuation, it is suitable for long-distance backbone transmission, but it has high hardness and is not easily bent.

Thin cable: Good flexibility, suitable for short distance branch connections, but with significant signal attenuation.

Hybrid cabling calculation formula: When there are both thick and thin cables in the network, their lengths must satisfy specific linear constraint relationships. For example, at a baud rate of 125 Kbps: L_thick cable+5.0 × L_thin cable ≤ 500 meters. This formula reveals the "weighted" negative impact of thin cables on network length, which engineers must perform precise calculations when planning cabling.

4.4 Branch Line Length Rules

Single branch line restriction: The maximum length from the branch point of the main line to the node cannot exceed 6 meters.

Cumulative branch line limit: The total length of all branch lines on the network must be within the specified range (such as a total length of no more than 39 meters at 500 Kbps). Excessive accumulation of branch lines can lead to signal reflection and impedance mismatch.

4.5 Grounding strategy and anti-interference

Single point grounding: The shielding layer of the communication cable should be connected to the FG terminal of the communication power supply and finally grounded (with a grounding resistance of less than 100 Ω).

Prohibition of multiple grounding points: Multiple grounding points can form a ground loop and introduce significant noise interference.

Independent grounding: The grounding point of the DeviceNet network should not be shared with the grounding point of the servo drive or frequency converter to avoid interference from the ground current of strong electrical equipment on weak electrical communication signals.

Software configuration and EDS files

To make the NS300 module work properly on the network, in addition to physical wiring, software level configuration is also required.

5.1 Parameter Settings

When NS300 is installed on SGDH and powered on for the first time, the driver parameters will be automatically set to adapt to the application module. But before formal operation, users need to set the node address and baud rate by rotating the switch, and ensure that these settings are consistent with the configuration of the upper computer master station.

5.2 EDS file

The EDS file is the "electronic ID card" of the DeviceNet device. When using configuration tools such as DeviceNet Manager to scan the network, the corresponding EDS file must be imported.

File name: NS300.Eds (Standard Edition) or NS300E.eds (RoHS Edition).

Access: You can download it from the official website of ODVA or Yaskawa Electric. The EDS file contains information such as the parameter list and I/O data format of the device, which is crucial for the upper computer to recognize and control the NS300 module.

Trial operation and maintenance

6.1 Precautions for Trial Operation

Before connecting the load for trial operation, a no-load test must be conducted.

Inertia matching: The parameter Pn103 (load inertia ratio) is crucial. When conducting no-load testing, it must be set to 0 (factory default value). If this parameter is set incorrectly, the motor may experience oscillation or overshoot.

Emergency stop circuit: Before running with load, it is necessary to confirm the effectiveness of the emergency stop button to prevent equipment damage or personnel injury caused by sudden failures.

6.2 Maintenance Inspection

Servo drives are static sensitive equipment and require extra care during maintenance:

Discharge waiting: After power failure, it is necessary to wait for at least 5 minutes until the internal capacitor is discharged before touching the internal circuit.

Environmental inspection: Regularly check the temperature, humidity, dust accumulation, and operation of the cooling fan inside the control cabinet.

EMC Directive Compliance Measures

Equipment sold or used in the European market must comply with the EMC Directive (Electromagnetic Compatibility). The NS300 module has taken into account EMC requirements in its design, but the final compliance of the system depends on installation quality.

7.1 Cable shielding treatment

DeviceNet cable: A dedicated DeviceNet cable must be used.

Full loop encoder cable (CN4): A twisted pair shielded cable must be used and connected to a designated type of connector (such as Molex 54306-2011).

7.2 Application of magnetic rings and wire clamps

Ferrite magnetic ring: Magnetic rings (such as ESD-SR-25) must be installed near the main station and servo driver end of the DeviceNet communication cable, as well as near the servo end of the fully closed-loop encoder cable. Magnetic rings can effectively suppress high-frequency common mode noise.

Cable clamps: The shielding layer must be fixed and grounded through conductive metal clamps. The installation surface of the fixture needs to remove the paint to ensure good electrical connection.

7.3 Wiring Examples

In a typical compliant wiring scheme, the incoming power supply needs to pass through a noise filter, the power line between the servo driver and the motor needs to use shielded wire and be grounded at both ends, and the communication line needs to pass through a magnetic ring on the driver side and be grounded using a dedicated wire clamp. This three-dimensional shielding measure creates an electromagnetic safe operating environment.