Troubleshooting E-8104: Noisy or Erratic Data from 311-005 Force/Torque Sensor

Related Products

Tools Required

• Torque wrench with appropriate socket
• Multimeter
• Set of hex keys
• Standard safety equipment (safety glasses, gloves)

Article

This article provides troubleshooting steps for resolving noisy, erratic, or drifting data from the NexBot Robotics 311-005 6-Axis Force/Torque Sensor (SKU: NXB-SNS-311-005). These symptoms are often associated with the controller error code E-8104 (Sensor Data Unstable) and can significantly impact the performance of precision applications such as assembly, polishing, and material handling.

Symptom

You may be experiencing one or more of the following issues:

• Unstable Readings: The force and/or torque values (Fx, Fy, Fz, Tx, Ty, Tz) fluctuate rapidly on the teach pendant or monitoring software, even when the robot is stationary and not in contact with any object.
• Data Drift: The sensor readings do not return to zero after a force or load is applied and then removed. This is also known as a non-zero bias.
• Controller Alarms: The robot controller logs error code E-8104 or similar warnings related to sensor data quality or communication timeouts.
• Inconsistent Performance: The robot exhibits jerky or unpredictable motion during operations that rely on force control feedback.

Cause

The root cause for unstable sensor data can be mechanical, electrical, or software-related. Common causes include:

1. Mechanical Issues: Loose mounting bolts connecting the sensor to the robot's J6 wrist flange or connecting the end-of-arm-tooling (EOAT) to the sensor.
2. Electrical Noise: Electromagnetic interference (EMI) from high-power cables (e.g., motor power, welder cables), an unstable 24VDC power supply, or improper grounding.
3. Communication Faults: A damaged or improperly seated EtherCAT cable, leading to intermittent data packet loss.
4. Incorrect Software Configuration: An incorrect sensor zeroing (tare) procedure was performed, or the payload data for the attached EOAT is not correctly configured in the robot controller.
5. Sensor Overload: The sensor has been subjected to a force or torque beyond its maximum rated limits due to a collision or improper handling, potentially causing permanent damage or calibration drift.

Resolution Steps

WARNING: Before beginning any inspection or repair, ensure the robot controller is powered off and all hazardous energy is controlled by following proper lockout/tagout (LOTO) procedures.

Step 1: Verify Mechanical Mounting

A secure mechanical connection is critical for accurate data. Loose hardware can introduce vibration and false readings.

1. Power off the robot system and apply LOTO.
2. Inspect the EOAT: Ensure the end-of-arm-tooling is securely fastened to the face of the NXB-SNS-311-005 sensor. Check all mounting bolts for tightness.
3. Inspect the Sensor Mounting: Check the bolts that secure the sensor to the robot's J6 flange. These are often hidden by the tooling adapter plate.
4. Torque Bolts to Specification: If any bolts are found to be loose, tighten them in a star or cross pattern to ensure even pressure. For standard M6 bolts, a typical torque value is 10 Nm. Always consult the robot's specific maintenance manual for exact torque specifications.

Step 2: Inspect Electrical and Communication Connections

Electrical noise and poor connections are a primary cause of data instability.

1. Inspect EtherCAT Cable: Carefully examine the EtherCAT cable connected to the sensor for any signs of physical damage, such as pinching, abrasions, or sharp bends. Ensure the connectors are fully seated and locked at both the sensor and the controller/junction box.
2. Verify Power Supply: Use a multimeter to measure the 24VDC supply voltage at the sensor's power connection. The voltage should be stable and within the specified tolerance (typically +/- 10%). Fluctuations or low voltage can cause erratic sensor behavior.
3. Check Cable Routing: Ensure the sensor's EtherCAT cable is routed separately from high-power cables, such as robot motor power or welder cables, to minimize EMI. Maintain the maximum possible distance between signal and power cables.
4. Confirm Grounding: Verify that the robot controller and the sensor's shielding are properly connected to earth ground.

Step 3: Review Software Configuration

Incorrect software settings can make a perfectly functional sensor appear faulty.

1. Perform a Sensor Tare (Zeroing): With the robot powered on and the EOAT attached, move the robot to a position where the tool is not touching anything and is oriented vertically downwards to minimize gravitational effects. Execute the sensor zeroing or taring function from the robot controller. This establishes a correct zero-point reference.
2. Verify Payload Settings: Navigate to the payload settings menu in the robot controller. Confirm that the mass, center of gravity, and inertia values for the currently attached EOAT are entered correctly. Incorrect payload data will cause the controller to misinterpret gravitational forces as external forces, leading to drift and errors, especially as the robot wrist changes orientation.

Step 4: Check for Overload History

If the steps above do not resolve the issue, the sensor may have been damaged.

1. Review Logs: Check the robot controller's alarm history for any collision detection alarms or other events that indicate a severe physical impact.
2. Contact Support: If a past overload event is suspected, the NXB-SNS-311-005 sensor may require recalibration or replacement. Contact NexBot Robotics support for further assistance.

Prevention

• Incorporate bolt torque checks for the sensor and EOAT into your robot's regular preventive maintenance schedule.
• Always use high-quality, shielded EtherCAT cables for sensor communication.
• Follow best practices for cable routing, keeping signal and power cables separated.
• Ensure payload data is updated in the controller every time the end-of-arm-tooling is changed.
• Properly configure and enable collision detection features in the robot program to protect the sensor from damaging impacts.

Keywords