Baum ü llerb b maXX 5000 Safety Configuration and Troubleshooting Guide

2.3 Common Installation Errors and Prevention

Error 1: After inserting the SAF module, the driver reported 'security module model mismatch'.

Reason: The firmware of different module types (SAF-001/002/003) is different and hot plugging is not allowed.

Solution: After power failure, reconfirm that the module model matches the order number and perform "safety module identification" in ProDrive.

Error 2: The STO light keeps flashing, unable to enable the drive.

Reason: The dual channel STO signals are not simultaneously at high levels (with a difference of more than 200ms).

Solution: Check if the external safety relay contacts are synchronized, or add a signal delay time parameter (parameter P-0-4030).

Detailed Explanation of Safety Parameter Configuration (ProSafePara Operation Guide)

3.1 Security Engineering Workflow in ProMaster

Create Project: Open ProMaster, create a new project, and add the b maXX 5000 device.

Switch to Safety View: Click on the "Safety" tab in the device editor, and upon first entry, you will be prompted to install the ProSafePara plugin.

Select security function: Check the required security function (such as STO, SS1, SLS, etc.). Each function has a unique ID and checksum.

Set limit value:

SLS: Set speed threshold (e.g. 500 rpm) and monitoring delay (e.g. 50ms).

SLP: Set the position window (e.g. ± 10 mm) and approach direction.

SS1: Set the deceleration ramp time (e.g. 500ms from rated speed to 0).

Security CRC calculation: After each modification of security parameters, the system automatically calculates the CRC, which needs to be confirmed by the user and written into the module.

Download and Verification: Download the security configuration to the SAF module via Ethernet or USB. Afterwards, a 'security test signature' must be performed - manually triggering each security function and confirming that the drive responds correctly.

3.2 Typical Configuration Case: Vertical Shaft to Prevent Falling

Equipment: b maXX 5325 axis unit+SAF-002+DSD servo motor with brake.

Requirement: When pressing the emergency stop button, the motor must stop at controlled deceleration (SS1), then the brake must be closed (SBC), and finally STO activated. If the speed exceeds 200 rpm, immediately trigger SLS and report an error.

Parameter settings:

SS1 deceleration time: P-0-4090=300ms

SBC output allocation: Digital output DO1, action logic "brake closed when speed<10rpm"

SLS speed threshold: P-0-4110=200 rpm, monitoring window: P-0-4111=100ms

Test steps:

Run the motor at 500rpm.

Press the emergency stop button.

Observe the status of the driver: the speed drops to 0 within 300ms, DO1 outputs a high level to close the brake, and finally the STO LED lights up.

If there are no abnormalities, generate a security test report and archive it.

Common safety function troubleshooting

The safety related failures encountered by on-site engineers are often not caused by hardware damage, but by parameter configuration, wiring, or logical conflicts. The following are the five most common types of safety faults and their systematic solutions for b maXX 5000.

4.1 Fault phenomenon: STO cannot be released (the driver always displays "Safe Torque Off Active")

Possible reasons:

The safety input terminals X5/1 and X5/2 did not receive 24V simultaneously.

The internal self-test of the security module failed.

The FSoE master station has not sent a 'Safe Operational' status.

Diagnostic steps:

Use a multimeter to measure the voltage between X5/1 and X5/3 (GND), and the voltage between X5/2 and X5/3 should both be 24V ± 10%.

If the voltage is normal, enter the ProDrive monitoring interface to check the "Safety Status" parameter (P-1-4100). If the value is' Waiting for start ', a safety reset (via I/O or FSoE) is required.

If it still doesn't work, power off and reinsert the SAF module, and check if there are any bent pins at the bottom of the module.

solve:

For hardware signal issues, check if the output contacts of the safety relay are stuck or delayed.

For FSoE, reconfigure the host connection relationship and confirm that the communication cycle is stable without frame loss.

4.2 Fault phenomenon: When SS1 is triggered, the motor stops freely instead of decelerating on a slope

Reason: The deceleration time set in the SS1 parameter is too large, or the internal current limit of the driver is too low, resulting in the inability to follow the deceleration slope.

terms of settlement:

Check if the deceleration time of SS1 (P-0-4090) is less than the inertia time constant of the actual load. For high inertia loads, 400~600ms can be set.

At the same time, check if the peak current limit of the driver (P-2-1015) is sufficient. For example, when the inertia ratio is greater than 10 times, it is recommended to set the peak current to 200% of the rated current.

Use the oscilloscope function of ProDrive to simultaneously record the speed command and actual speed, and observe the deviation between the two. If the deviation continues to exceed 50rpm for more than 200ms, the system will automatically switch to STO. At this time, the SS1 time should be increased or the current capacity should be improved.