Technical Bulletin: PROFINET and PROFIsafe Configuration for NXB-SRV-DC112-008 Servo Motor

Related Products

Tools Required

• Laptop with engineering software
• Industrial Ethernet cable (shielded, CAT5e or better)
• Torque wrench
• Standard electrician toolkit

Article

This document outlines the standard procedure for configuring the NexBot Safety DC112-008 Dc Servo Motor (SKU: NXB-SRV-DC112-008) on an industrial network. Proper configuration of its PROFINET communication and integrated PROFIsafe functions is critical for ensuring operational reliability and functional safety in robotic systems such as the NexBot R-20 and R-50 series, where this motor is commonly used for J1, J2, and J3 axes.

Incorrect setup can lead to communication faults, unexpected machine behavior, or failure of safety-critical functions. Following these steps ensures that the motor is correctly integrated into the machine control and safety system.

Overview of PROFINET and PROFIsafe

PROFINET is the open Industrial Ethernet standard used for data communication in automation technology. It facilitates high-speed, deterministic data exchange between controllers (PLCs) and distributed field devices like the NXB-SRV-DC112-008 servo motor.

PROFIsafe is a safety communication technology that operates over PROFINET. It allows for the transmission of safety-related signals (e.g., emergency stops, light curtain trips) over the same network cable used for standard control data, eliminating the need for separate hardwiring for safety circuits. This is achieved by adding a safety layer to the standard communication protocol.

Prerequisites

Before beginning the configuration, ensure you have the following:

• Software: An installed and licensed version of the engineering software used for your master PLC/robot controller (e.g., TIA Portal, NexBot Motion Studio, or equivalent).
• GSDML File: The correct Generic Station Description Markup Language (GSDML) file for the NXB-SRV-DC112-008 motor. This file describes the motor's properties to the engineering software.
• Network Access: Physical access to the robot controller cabinet and an available port on the PROFINET network switch.
• Documentation: The electrical schematics for the robot cell and the risk assessment documentation defining the required safety functions.
• Permissions: Administrative rights within the engineering software to modify hardware configurations and safety programs.

Step-by-Step Configuration Procedure

1. Hardware Installation and Connection

1. Mount Motor: Ensure the NXB-SRV-DC112-008 motor is securely mounted at its designated position (e.g., J1, J2, or J3 axis). Verify that all mounting bolts are torqued to the manufacturer's specification.
2. Connect Power: Connect the 24VDC power supply to the motor's power connector. Ensure correct polarity.
3. Connect Network: Using a shielded, industrial-grade Ethernet cable (CAT5e or higher), connect one of the motor's PROFINET ports to the controller's PROFINET network.

2. GSDML File Installation

1. Launch your engineering software.
2. Navigate to the hardware catalog manager or GSD file management tool.
3. Select the option to install a new GSD file.
4. Browse to and select the GSDML file for the NXB-SRV-DC112-008. The software will integrate the motor into its hardware catalog.

3. PROFINET Network Configuration

1. In your project's hardware configuration or network view, drag the NXB-SRV-DC112-008 motor from the hardware catalog onto the PROFINET network.
2. Assign a unique Device Name to the motor. This name must exactly match the name you will later assign to the physical device. Example: j1-axis-motor.
3. Assign a unique IP Address and Subnet Mask within the project's network range. Example: 192.168.1.12.
4. Download the hardware configuration to the PLC/controller.
5. Using the engineering tool's online functions, assign the configured Device Name and IP Address to the physical motor on the network.

4. PROFIsafe Parameterization

This step is critical for functional safety and must be performed with care.

1. In the motor's device properties within the hardware configuration, navigate to the safety parameters section.
2. Enable PROFIsafe communication for the device.
3. Assign a unique F-Destination Address (PROFIsafe address) to the motor. This address must be unique across all safety devices in the project. Consult your project's safety plan for the correct address to use.
4. Configure the required safety functions (e.g., Safe Torque Off - STO). The available functions are defined in the GSDML file.
5. Set the F_WD_Time (watchdog time) according to your risk assessment. This value determines how long the device will wait for a valid safety message before faulting.
6. After setting all parameters, the engineering tool will generate a parameter signature or checksum (F_iPar_CRC). This value must be confirmed and accepted.
7. Compile and download the safety program and hardware configuration to the controller.

Verification and Commissioning

1. Check LEDs: Observe the status LEDs on the motor. A solid green 'BF' (Bus Fault) and 'SF' (System Fault) LED indicates an error, while a lit 'LINK' LED and no fault lights indicates successful network connection.
2. Online Diagnostics: Go online with the controller and check the device diagnostics for the motor. Ensure it is shown as 'Reachable' and has no active faults.
3. Safety Function Test: With the machine in a safe state and all personnel clear, systematically test each configured safety function. For example, activate an E-Stop and verify that the motor's STO function is triggered and reported correctly in the safety program.
4. Axis Jogging: Perform slow-speed jogging of the axis controlled by the motor to confirm correct direction of motion and control response.

Common Issues and Troubleshooting

• Communication Fault (BF LED flashes): This typically indicates a network issue. Check that the Ethernet cable is securely connected, the Device Name in the project matches the name assigned to the physical motor, and there are no IP address conflicts.
• PROFIsafe Fault (SF LED lit, safety program fault): This often relates to a mismatched F-Destination Address or an incorrect parameter signature. Verify that the address assigned in the hardware configuration is correct and that the safety parameters have not been changed without recompiling and downloading the safety program.

Keywords