Troubleshooting the SIMOREG 6RA70 F038 Overspeed Fault

David Krause3 min read
SiemensTroubleshootingVFD / Drives
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

An F038 overspeed fault on a Siemens SIMOREG DC Master 6RA70 can be narrowed down by comparing the failing drive with an equal-rated spare. In the reported case, the same motor, encoder assembly, encoder cable, and downloaded program operated correctly on the spare drive. That result shifts the investigation toward the original drive, but it does not prove which internal component is defective.

Interpret the drive-swap result

Observation Engineering conclusion
Motor and encoder assembly run correctly with the spare drive The motor and encoder are less likely to be the primary cause.
Both drives have the same rating The spare provides a relevant comparison, subject to hardware-condition differences.
The same program was downloaded to the spare A program-level parameter error becomes less likely, but commissioning state or drive-specific data may still differ.
F038 remains associated with the original drive Prioritize the original drive's connections, control board, and commissioning state.

The supplied evidence identifies F038 as an overspeed fault but does not provide the official trip threshold, firmware scope, or diagnostic-word definition. Verify those details in the applicable 6RA70 documentation before changing protection settings.

Recheck the encoder interface under operating conditions

Inspect and retighten the encoder terminals on the original drive even if continuity checks have passed. A drive replacement can disturb or retighten a marginal termination, making the spare-drive test appear to clear an encoder problem. Confirm that the encoder cable is shielded, routed away from power cables, and grounded at the drive-side shield connection as described in the evidence.

Do not infer signal integrity from a stationary cable check alone. Observe whether F038 occurs only during rotation, acceleration, or another repeatable operating condition, then compare the original and spare drive behavior under the same command.

Isolate the CUD1 board

Use a controlled CUD1 board exchange to test whether the fault follows the board. Record each drive-and-board combination so the result distinguishes a CUD1 fault from a chassis, connector, or commissioning issue.

  1. Install the spare CUD1 board in the original drive and run the same controlled test.
  2. If the fault clears, install the suspected CUD1 board in the spare drive for confirmation.
  3. If F038 follows the suspected board, treat the CUD1 as the isolated fault location. If it stays with the original drive, investigate the remaining drive hardware and its encoder-interface connections.

Perform board exchanges only with the equipment safely isolated and according to the manufacturer's service procedure.

Separate commissioning data from feedback faults

If the board test is inconclusive, preserve the existing configuration, apply the factory setting, and commission from the beginning without downloading the original parameter set first. Perform optimization with P051, then run the motor alone using the resulting basic parameters. If the fault disappears, reintroduce the application configuration in controlled stages to identify the setting associated with the trip.

Commissioning isolation test:
1. Preserve the current configuration
2. Apply the factory setting
3. Commission without downloading the old parameters
4. Perform optimization using P051
5. Run the motor alone with the basic parameters

A further diagnostic proposed in the evidence is an open-loop test using P083=3. Use this only as a controlled troubleshooting step after confirming that open-loop operation is safe for the machine. If open-loop operation succeeds while encoder-controlled operation produces F038, focus on the feedback path, encoder interface, and related commissioning data; the result alone does not identify a failed component.

FAQ

What does F038 mean on a SIMOREG 6RA70?

The supplied case identifies F038 as an overspeed fault. Confirm the exact trip definition and threshold in the documentation applicable to the installed drive and firmware.

How do I determine whether the CUD1 board causes F038?

Run the original drive with the spare CUD1, then test the suspected CUD1 in the spare drive. A fault that follows the board isolates the problem to the CUD1; a fault that remains with the original drive points elsewhere in that drive or its connections.

Can I test a 6RA70 F038 fault without encoder feedback?

The evidence proposes an open-loop test with P083=3. If it runs open loop but trips under encoder control, investigate the feedback path and related commissioning data, while observing all machine-safety constraints.

Back to blog