NexBot Robotics Support

NexBot Vision SD312-015 Force Sensor Unresponsive on R-50 Assembly Line

Industrial Robotics & Maintenance Parts case CASE-00412

StatusClosed
PriorityCritical
CategoryMalfunction
Product SKUNXB-SNS-SD312-015
Created2025-04-28
Resolved2025-05-06

Description

We have a critical production stoppage on our main assembly line. Our R-50 robot, which uses a NexBot Vision SD312-015 1500N Single-Axis Force Sensor for a press-fit application, has faulted. The robot controller is reporting a loss of communication with the sensor over the EtherCAT network. We have inspected the sensor, and none of its status LEDs are illuminated. We have confirmed the 24VDC power rail for our end-of-arm tooling is active and supplying the correct voltage. We also power-cycled the entire robotic cell, but the sensor remains completely unresponsive. All other devices on the EtherCAT bus are functioning normally. This sensor is less than six months old, and we need urgent assistance to diagnose whether this is a configuration issue or a hardware failure, as our line is down.

Symptoms

  • Sensor status LEDs are off
  • Robot controller reports EtherCAT communication loss
  • No force data being transmitted
  • Production line halted

Resolution

The issue was determined to be an internal hardware failure of the force sensor. After remote diagnostics confirmed the 24VDC power supply and EtherCAT cabling were providing correct voltage and continuity, the sensor remained unresponsive. The lack of status LEDs indicated a fault in the sensor's main power or logic board. The customer was advised to replace the faulty unit. A replacement NexBot Vision SD312-015 sensor was ordered and installed, which immediately restored communication and allowed the production line to resume normal operations. The faulty unit was returned for failure analysis under warranty.

Resolution Steps

  1. Verified with the customer that the 24VDC power supply was delivering a stable voltage between 23.5V and 24.5V directly at the sensor's connector pins.
  2. Instructed the customer to swap the EtherCAT cable with a known-good cable from an adjacent device to rule out a cable fault. The issue persisted.
  3. Confirmed that other devices on the same EtherCAT segment were communicating correctly, isolating the fault to the sensor itself.
  4. Based on the lack of any status LEDs and the results of the previous steps, diagnosed an internal hardware failure of the NXB-SNS-SD312-015 sensor.
  5. Authorized a warranty replacement for the sensor.
  6. Customer installed the new sensor, re-addressed it on the EtherCAT network, and confirmed successful communication and operation.
  7. Provided an RMA number for the return of the defective unit for failure analysis.