MASTERDRIVE CUVC F008/F081 Fault: Profibus Watchdog Reset

1. Problem Overview

The Siemens MASTERDRIVE CUVC (Control Unit Voltage Converter) vector-control platform, used widely on DC and AC machines built between the late 1990s and mid-2000s, is a mature drive family. However, when installed in a system that sits idle for a long shutdown (weekends, holidays, plant stoppages), operators frequently report a cluster of communication faults on the first cold-start attempt. The three most common cold-start faults are:

• F008 – Serial interface / communication fault at the basic unit (USS channel or PROFIBUS telegram timeout).
• F081 – Communication fault to the CBP (Communication Board PROFIBUS) at startup or during operation.
• F082 – Process data monitoring (watchdog) timeout on the CBP/CBP2 communication channel.

These faults are especially disruptive in mixed fleets (a machine may contain 20+ MASTERDRIVE units) where only one specific drive – typically the auxiliary blower, exhaust, or low-power fan – trips and cannot be reset from the operator panel. The drive then requires a manual reset at the PMU (Parameterization Unit) using the P key. This is the exact symptom pattern reported on a 23-drive Italian-built machine using an S7-300 CPU317-2DP PROFIBUS DP master with the following hardware:

• CUVC control card: 6SE7090-0XX84-0AB0 (compact CUVC board, hardware version up to FW 3.xx)
• CBP2 PROFIBUS submodule: 6SE7090-0XX84-0FF5 (PROFIBUS-DP communication board, ~12 Mbaud)
• Master controller: SIMATIC S7-300 CPU 317-2DP, PROFIBUS DP interface

2. Fault Code Reference Table

The following table maps the three fault codes to their meaning, status bit, and default behavior. Always cross-check the live status using parameter r947 (fault number) and r949 (fault value) before changing any setting.

All three faults default to OFF2 (rapid stop, pulse inhibit via the IGBT gate drivers) and require a manual fault acknowledgement before the drive will re-enable. This is why a press of the operator-panel reset button – which typically issues an STW1 bit 7 = 0 → 1 edge to clear acknowledged faults – fails for these particular codes when the master has not yet polled a fresh telegram.

3. Root Cause: Process Data Watchdog (Parameter P722)

The primary root cause for the recurring F008 / F081 / F082 cluster on Monday-morning cold starts is the process data monitoring time, parameter P722. This parameter defines the maximum interval (in milliseconds) that the CUVC will wait for a valid PROFIBUS PZD (process data) telegram from the CBP2 submodule before tripping a fault.

Per the MASTERDRIVE Compendium (E20125-B-P35 series), section 8.2.7.4 – "Process data monitoring", the watchdog behaves as follows:

• P722 = 0 → Process data monitoring disabled. No F081/F082 trip is generated even if telegrams stop.
• P722 = 1…65000 → If no valid PZD is received within this window, the drive generates F081 or F082 (OFF2) and sets status bit "Communication fault" in ZSW1.
• P722 < PLC scan time at first cold start → Fault is guaranteed on the first PLC cycle because the DP master has not yet completed bus initialization, parameterization, and configuration telegrams for the CBP2.

On a cold start, the S7-300 powers up, runs OB100 (warm restart) or OB101/OB102, then begins DP user-data exchange. The CBP2 must complete its own DP slave initialization (baud-rate detection, parameterization, configuration telegrams) before it can deliver a PZD to the CUVC. If the CUVC watchdog window expires before the first valid PZD arrives, the drive trips F082 immediately. On the second start (when the master is already configured) the window is easily met and the drive runs cleanly – exactly the "Monday-only" symptom pattern.

4. Secondary Root Causes to Investigate

Before concluding that P722 is the only issue, rule out the following hardware and wiring factors. Each has caused identical symptoms in field installations and is documented in Siemens technical support notes.

4.1 DC Link Pre-Charge and Undervoltage

If r006 (actual DC link voltage) is below the undervoltage threshold when the CBP2 begins its initialization, the CUVC may flag F008 because the internal logic supply rails are unstable. On Monday-morning cold starts, mains can sag, or the pre-charge resistor may have degraded.

• Measure DC link voltage at the power section terminals with a true-RMS multimeter.
• Compare against r006 on the PMU – values must match within ±5%.
• Verify the pre-charge circuit: 24 V control supply, contactor sequence, and the line filter are healthy.

4.2 PROFIBUS Cable and Connector Integrity

The CBP2 9-pin D-sub connector uses pin 6 (VP) and pin 5 (DGND) for the bus terminator. A cold start can cause intermittent contact resistance changes in:

• PROFIBUS connector with switched terminator (verify terminator is ON at both ends only).
• Crimp or screw connections at the bus cable shield clamp (Drain wire must contact 360° around the connector housing).
• Oxidized pins in the Sub-D backshell – clean with isopropyl alcohol and DeoxIT.

4.3 CBP2 Module Seating and Firmware

The CBP2 plugs into a 96-pin DIN connector on the CUVC. Thermal cycling across weekends can cause intermittent contact lift. Reseat the CBP2 with the CUVC powered down for at least 60 seconds, then re-tighten the two retaining screws. Also confirm the CBP2 firmware version with parameter r060 (SLB/CB firmware version) – mismatched CBP2 and CUVC firmware can cause watchdog timing drift.

4.4 S7-300 Startup Sequence

The CPU 317-2DP must complete the following sequence before user data is exchanged:

1. Power-on self-test and OB100/OB102 execution.
2. PROFIBUS DP initialization at the configured baud rate (typical 1.5 Mbaud or 12 Mbaud).
3. CBP2 parameterization telegram (read GSD file identification, configure PZD slots).
4. CBP2 configuration telegram (check PZD length and consistency).
5. First user-data telegram – this is the moment the CUVC watchdog starts being serviced.

Steps 1–4 can take 1.5 to 4 seconds on a CPU 317-2DP with 20+ slaves. If P722 is below this total, F082 is guaranteed.

5. Diagnostic Procedure

Follow this procedure in order. Do not skip the r006 step; it is the single most important first check.

1. Read the active fault buffer on the PMU: r047 shows the current fault number, r947 shows the fault number, and r949 shows the fault value. Confirm F008 / F081 / F082.
2. Verify DC link voltage: Compare r006 (PMU display) with a DMM measurement at the DC+ and DC- terminals. Acceptable deviation: ±5%.
3. Check process data monitoring time: Read P722. Record the current value.
4. Check the PROFIBUS slave diagnostic buffer in the S7-300: STEP7 → Hardware → PROFIBUS DP → Diagnostic → Slave diagnostic. Look for "Diagnostic interrupt", "Identifier-related diagnostic", or "Module status" entries on the CBP2.
5. Check parameter r748.0 (control word 1 status) and r749.0 (status word 1) – bit 3 ("Fault present") and bit 10 ("Control request") will confirm the drive's state at the time of trip.
6. Capture a PROFIBUS trace with a BT200/BT300 or Amprolyzer / INspektor. Look for corrupted telegrams, retries, or short inter-frame gaps immediately before the trip.

6. Solution: Adjust Parameter P722

The primary and recommended fix is to set P722 to a value greater than the worst-case PLC cold-start time. Use the table below as a sizing guide.

For the affected 23-drive installation, P722 = 6000 (6 seconds – the factory default) is the starting recommendation. If the trip persists, increase to 8000, then 10000. The author's case shows that P722 = 0 (monitoring disabled) stopped the trip entirely, which is acceptable for non-safety drives but not for motion-control or hoist applications.

6.1 Step-by-Step P722 Edit at the PMU

1. Press P on the PMU – the display shows P000.
2. Use the ↑ / ↓ rocker to scroll to P722.
3. Press P to enter edit mode. The display shows the current value (e.g., 6000).
4. Use the rocker to set the new value. Acceptable values: 0 to 65000.
5. Press P to save. The PMU briefly shows the parameter number and returns to the parameter list.
6. Press and hold P for > 3 seconds, or cycle the drive's 24 V control supply, to commit the change to non-volatile memory.

6.2 Setting P722 from DriveMonitor or STARTER

For drives connected to a USS or PROFIBUS point-to-point link to a commissioning PC, the change can be made via the Siemens Industry Online Support tools:

1. Open DriveMonitor (legacy) or import the MASTERDRIVE DSF file into STARTER.
2. Go online with the affected drive.
3. Navigate to Parameters → Communication → Process data monitoring time.
4. Set P722 to the recommended value, write to the drive, and execute Copy RAM to ROM.
5. Verify by reading P722 back, then power-cycle the drive's 24 V control supply to confirm retention.

7. Verification Procedure

After applying the P722 change, perform the following verification steps to confirm the cold-start problem is resolved without introducing new risks.

1. Cold-start simulation: Power down the entire cabinet including 24 V control supply for at least 5 minutes. Power up, and time the interval from PLC "RUN" LED to drive "Ready" (no F008/F081/F082). Record the time on at least 3 separate cold starts.
2. Watchdog validation: With the drive running, stop the CPU (toggle PLC to STOP). The drive should trip F081/F082 after P722 milliseconds ±10%. If it trips earlier, P722 is not being honored – check firmware version and CBP2/CUVC seating.
3. Bus quality check: View parameter r748 bit 10 and the CBP2 diagnostic counters. On a clean bus, retry counters should remain 0 over an 8-hour shift.
4. Operator panel reset test: Trip the drive intentionally via DI (digital input) – confirm the operator-panel reset button clears it. Then trip via PROFIBUS stop – confirm reset also works. This proves the master→slave handshake is healthy.
5. Multi-cycle stress test: Run 5 cold starts across 5 days at different ambient temperatures (cooler cabinet at 5 °C and warmer at 35 °C). All must start cleanly.

8. When P722 Adjustment Alone Is Not Sufficient

If F081/F082 continues after raising P722 to 10000 ms, or if F008 appears independently of F081/F082, the drive is exhibiting a real hardware or wiring issue. Take the following steps in order.

9. Hardware Replacement Decision Matrix

The original case history notes "uncountable" power section replacements and 1–2 CUVC card replacements, plus 1 CBP2 replacement. This level of replacement is excessive if the root cause is P722. Use the matrix below to decide whether hardware replacement is justified.

10. Field-Proven Recommendations for This Installation

Based on the 23-drive Italian machine with S7-300 CPU317-2DP and the CUVC/CBP2 hardware, the following configuration is recommended.

1. Set P722 = 6000 (factory default) as the baseline. If F081/F082 still trips within the first week, raise to 8000, then 10000.
2. Save parameters to EEPROM via P971 = 1 on each drive after any change. A drive that reverts to a default P722 of 0 will silently disable the watchdog.
3. Verify DC link voltage on every drive at the next scheduled maintenance: measure r006 and compare to a DMM reading. Capacitors aged beyond ESR 200 mΩ at 1 kHz should be considered for rebuild.
4. Add a 30-second delayed enable in the PLC program: do not send the ON command (STW1 bit 0) to the blower drive for at least 5 seconds after the drive reports "Ready to switch on" (ZSW1 bit 2). This gives the DP master a clean handshake window and avoids the first-cycle race.
5. Replace the CBP2 connector if its age is > 5 years. The Siemens 6GK1500-0FC10 or equivalent 9-pin PROFIBUS connector with switchable terminator and diagnostic LED is recommended.
6. Log the fault buffer to the operator panel HMI on every cold start. If F081/F082 recurs after P722 adjustment, capture r947 and r949 for root-cause analysis.

11. Related Parameters to Audit

When you are already editing P722, audit the following parameters. They all interact with the cold-start behavior of the CUVC.

12. Quick-Reference Cold-Start Checklist

• ☐ Confirm fault code via r947 – must be F008, F081, or F082.
• ☐ Verify r006 matches DMM at DC+ / DC- (±5%).
• ☐ Read current P722 value.
• ☐ Set P722 = 6000 (baseline) or higher if DP cold start > 6 s.
• ☐ Execute P971 = 1 to save to EEPROM.
• ☐ Power-cycle 24 V control supply and verify P722 is retained.
• ☐ Run 3 cold starts; confirm zero F008/F081/F082.
• ☐ Trip test: stop PLC, confirm drive trips F081/F082 within P722 ±10%.
• ☐ Restore PLC and confirm operator-panel reset clears the fault.
• ☐ Update maintenance log with new P722 value and any hardware changes.

13. Frequently Asked Questions