Intermittent PROFINET Communication Fault on R-20 Robot Axis 4 with new NexBot Servo Drive SD-48

Description

We recently replaced the servo drive on Axis 4 of our R-20 series robot with a new NXB-DRV-SD-048-A unit. Since the replacement, the axis has been experiencing intermittent but frequent faults. The robot will run for 10-15 minutes and then stop with a communication error. The HMI displays error E-4101, pointing to a PROFINET timeout for the Axis 4 drive. We have verified the 48VDC power supply is stable and within spec. We have also replaced the PROFINET cable between the controller and the drive with a known good one, but the issue persists. The status light on the drive itself flashes amber during the fault, but is solid green when it's operating correctly. We suspect a potential configuration mismatch or a faulty drive, as the previous unit did not have this issue. This is causing significant downtime on our assembly line.

Symptoms

• Intermittent axis fault alarm on HMI
• PROFINET communication timeout error
• Servo drive status LED flashes amber during fault
• Robot stops mid-cycle without warning

Resolution

The root cause was identified as an incorrect GSDML file being used in the master PLC's hardware configuration. The customer had replaced an older model drive but did not update the device profile in their engineering software. The new NXB-DRV-SD-048-A drive requires the latest GSDML file to establish stable PROFINET communication. We guided the technician to download the correct file from our support portal, update their project's hardware catalog, and recompile and download the configuration to the controller. This resolved the communication timeouts.

Resolution Steps

1. Confirmed the customer was using the correct component, SKU NXB-DRV-SD-048-A.
2. Instructed the customer to download the latest GSDML file for the SD-48 drive from the NexBot support portal.
3. Guided the technician on how to remove the old device profile from their PLC engineering software's hardware catalog.
4. Assisted with importing the new GSDML file and replacing the old drive with the correct NXB-DRV-SD-048-A profile in the project.
5. Verified that the PROFINET device name and IP address settings were correctly transferred to the new device configuration.
6. The customer downloaded the updated hardware configuration to the master controller.
7. After a power cycle of the robot and drive, the drive's status LED remained solid green and the E-4101 error was cleared.
8. The customer ran the robot in a production cycle for 2 hours and confirmed the issue was fully resolved.