Technical Bulletin: PROFINET Integration for NexBot Safety MA012-008 Robot Arm
This technical bulletin provides best practices for integrating and configuring the NexBot Safety MA012-008 robot arm with a PROFINET network for optimal performance and reliability.
Related Products
Tools Required
- Laptop with PLC engineering software
- PROFINET-rated Ethernet cable
- Managed industrial Ethernet switch (recommended)
- Torque driver for network connectors
Article
This document outlines the recommended procedures and best practices for the successful network integration of the NexBot Safety MA012-008 6-Axis Robot Arm (SKU: NXB-ROB-MA012-008) into a PROFINET industrial network. Proper configuration is critical to leverage the robot's full capabilities, including its ±0.04 mm repeatability and high-speed operation, and to ensure stable communication with the master PLC controller.
Prerequisites
Before beginning the integration process, ensure you have the following:
- Robot System: A fully commissioned NexBot Safety MA012-008 robot arm and controller, powered by 480VAC.
- PROFINET Controller: A PLC or other master device capable of functioning as a PROFINET IO Controller.
- Engineering Software: The appropriate software for configuring your PROFINET IO Controller (e.g., TIA Portal, Step 7, etc.).
- GSDML File: The correct General Station Description Markup Language (GSDML) file for the MA012-008. This file can be downloaded from the NexBot Robotics support portal.
- Cabling: High-quality, shielded, 4-wire or 8-wire PROFINET-rated Ethernet cabling, such as NXB-CBL-NET533-005.
Network Topology Recommendations
The MA012-008 controller base features integrated switch ports, allowing for flexibility in network design. The chosen topology can impact performance and fault tolerance.
- Line Topology: Devices are daisy-chained. This is simple and cost-effective but creates a single point of failure; a break in the chain can disconnect all downstream devices.
- Star Topology: Each device connects directly to a central switch. This is the most common and robust topology for industrial applications, as the failure of one cable or device does not affect others. We strongly recommend using managed industrial Ethernet switches for diagnostics and traffic management.
- Ring Topology (MRP): Requires managed switches that support Media Redundancy Protocol (MRP). This topology provides network redundancy, automatically redirecting traffic if a single connection is lost. It is recommended for applications requiring maximum uptime.
Configuration Procedure
Step 1: GSDML File Installation
The GSDML file contains all the necessary information for the IO Controller to recognize and communicate with the MA012-008 robot.
- Open your PLC engineering software.
- Navigate to the hardware catalog or device management section.
- Use the 'Install GSD' or equivalent function to import the
GSDML-Vxx-NexBot-MA012-008-YYYYMMDD.xmlfile. - After successful installation, the NexBot Safety MA012-008 will appear in your hardware catalog, ready to be added to your project.
Step 2: Hardware Configuration
- In your project's hardware configuration view, add the MA012-008 robot from the catalog to your PROFINET network.
- Assign a unique Device Name to the robot. This name must exactly match the name you will set on the robot controller itself. Device names are case-sensitive.
- Assign a unique IP Address, subnet mask, and gateway appropriate for your network.
- Connect the robot to the IO Controller in the network view.
Step 3: I/O Module Configuration
The MA012-008 exposes data through configurable modules in the GSDML file. You will need to add modules for process data (e.g., target positions, status words, command words) and safety signals (if using PROFIsafe).
- Select the configured robot in the device view.
- Drag and drop the required I/O modules into the device's configuration slots.
- Map the I/O addresses to your PLC's memory space (e.g., %I, %Q). Refer to the MA012-008 integration manual for a detailed description of each available data module.
Step 4: Setting the Device Name on the Robot
The robot controller must be assigned the same Device Name configured in the PLC project.
- Connect to the robot controller using the NexBot maintenance software.
- Navigate to the 'Network Configuration' section.
- Enter the exact Device Name you assigned in Step 2.
- Apply the settings and cycle power on the robot controller.
Physical Layer Best Practices
To ensure reliable communication and maintain the robot's IP67 rating, adhere to the following physical installation guidelines:
- Cabling: Use only shielded, industrial-grade PROFINET cables. Ensure the cable bend radius is respected to avoid signal degradation.
- Connectors: Use IP67-rated M12 D-coded or RJ45 connectors as appropriate for the controller ports. Ensure connectors are properly torqued and sealed to prevent moisture and dust ingress.
- Grounding: The robot arm and controller must be properly bonded to the facility's earth ground. Ensure the shields of the PROFINET cables are properly terminated at both ends to provide a low-impedance path for electrical noise.
Verification and Diagnostics
- After downloading the hardware configuration to your PLC, check the diagnostic LEDs on both the PLC and the robot's network interface.
A solid green 'BF' (Bus Fault) LED and 'SF' (System Fault) LED being off typically indicates a healthy connection.
- Use the PLC's online diagnostic tools to verify that the robot is reachable and that I/O data is being exchanged correctly. The diagnostics buffer will provide detailed error codes if a communication fault occurs.