BMW CF80 — Signal from engine management: setpoint-torque request

CF80 means Signal from engine management: setpoint-torque request. The receiving control unit stores it when the engine-management torque target does not arrive in a credible form for coordinated drivetrain operation. The code identifies a signal-path problem; it does not by itself prove an internal engine or transmission failure. What Does CF80 Mean? CF80 is Signal from engine management: setpoint-torque request. During coordinated drivetrain operation, controllers exchange torque targets so a shift, traction intervention, or load transition can occur smoothly. The receiver expects the request, its validity state, and the surrounding operating data to agree at the same moment. In practice, CF80 can be secondary to another engine-management fault that blocks a trustworthy torque value. It can also follow an interrupted network message, unstable controller supply, incompatible software, or a receiver that misjudges otherwise valid data. Vehicle order, module variant, and companion faults determine which branch applies. Code: CF80 Definition: Signal from engine management: setpoint-torque request Module: receiving drivetrain controller; verify by VIN Key data: requested torque, actual torque, engine speed, selected gear, message validity Typical cause: upstream engine fault or interrupted data path Severity: moderate; higher with harsh shifts or limp mode Note: diagnose companion faults before replacing modules Preserve the complete scan before clearing CF80. An engine-management fault recorded at the same mileage often explains why the torque request became unavailable. What Symptoms Does CF80 Cause? CF80 may produce no driver-visible symptom when it is a stored communication event. If the signal loss is current, watch for a harsh load change, delayed torque transfer, a drivetrain warning, or limp mode exactly when requested torque and actual response separate. A stable engine with an isolated historical code points away from mechanical transmission damage. • Requested engine torque freezes while actual torque continues changing during the captured load transition. • A drivetrain warning appears at the same mileage as an engine-management or network communication fault. • Shift quality becomes abrupt only when the torque-request validity state changes from valid to invalid. • Engine speed flares or drops unexpectedly while selected gear remains stable in the stored event. • The code returns immediately after clearing when the affected controller wakes and exchanges drivetrain data. • CF80 remains historical after several clean drive cycles when the original supply interruption has disappeared. Why Does CF80 Occur? CF80 usually starts upstream: engine management cannot publish a credible setpoint, or the receiver cannot obtain it intact. Begin with engine faults and shared supply history, then inspect network behavior and software compatibility. Internal controller failure is possible, but it belongs last because a substituted module will inherit the same missing or invalid input. • A stored DME or DDE fault prevents calculation of a dependable engine torque target. • Low system voltage during starting interrupts one controller while the other continues recording messages. • Connector fretting or moisture intermittently distorts the relevant powertrain-network data at the receiver. • Network wiring damage creates repeated message errors when vibration or drivetrain movement loads the harness. • Mismatched coding or software integration levels make two controllers interpret the torque message differently. • An internal transmitter or receiver fault corrupts the signal after external paths test correctly. How Is CF80 Diagnosed with OBDThink? Read every control unit and preserve mileage, voltage, engine speed, gear state, and the stored freeze frame data before clearing anything. OBDThink is an independent BMW coding and diagnostics app and is not affiliated with BMW AG. Compare CF80 with engine-management and network faults from the same event rather than treating one code in isolation. • 1. Save the complete vehicle scan and group faults by mileage, voltage, and occurrence time. • 2. Check DME or DDE first for faults that inhibit calculated or delivered engine torque. • 3. Compare requested torque, actual torque, engine speed, and selected gear during a repeatable load change. • 4. Observe whether torque-request validity fails before the drivability symptom or only after it. • 5. Inspect controller supplies and grounds under load if several modules reset in one event. • 6. Examine powertrain-network connectors and harness sections that react to heat, vibration, or movement. • 7. Verify VIN-specific coding and software integration when CF80 began after programming or module replacement. • 8. Follow the BMW test plan for the identified receiver only after upstream evidence is clean. IF an engine-management fault occurs before CF80 AND requested torque becomes invalid, THEN repair the upstream engine fault first. ELSE IF several controllers lose messages at the same low-voltage event, THEN test shared supply and network wake-up. ELSE IF requested torque remains valid but the receiver alone rejects it, THEN verify receiver coding, software, connector, and internal operation. The fastest separation is temporal: identify which fault occurred first and whether the requested-torque validity changed before the receiver stored CF80. How Is CF80 Repaired? Repair follows the evidence chain, not the most expensive component. Correct the upstream engine fault or supply interruption first, repair damaged network connections next, and then confirm coding compatibility. Replace or program a controller only when its inputs, wiring, power, grounds, and integration state have been verified under the same conditions that reproduce CF80. • Low cost: clean and secure the affected controller connector after documenting any moisture or fretting. • Low cost: repair a confirmed supply or ground voltage drop that resets the signal source. • Medium cost: restore damaged powertrain-network wiring where movement reproduces message-validity loss. • Medium cost: resolve the verified DME or DDE fault that suppresses credible torque calculation. • Medium cost: align VIN-specific coding and approved software when integration mismatch is documented. • High cost: replace the proven faulty controller only after communication and supply tests pass. After repair, CF80 no longer occurs, torque-request validity stays stable, and requested versus actual torque follows the same load transition without new companion faults. Can You Drive with CF80? You may drive briefly with historical CF80 when there is no warning, limp mode, harsh shift, or unexpected engine response. Current CF80 means drivetrain torque coordination may be unreliable, so avoid hard acceleration, towing, and situations requiring predictable power delivery until the event data has been checked. Stop driving if engine speed rises without matching acceleration, the gearbox strikes into gear, power falls suddenly, or a red drivetrain warning appears. Continuing under those conditions can add clutch heat or create unsafe hesitation. A normal drive cycle is appropriate only for controlled verification after the underlying fault is repaired. Stop if severe shift shock, uncontrolled engine-speed change, or sudden loss of propulsion accompanies CF80. Which Questions Are Asked Frequently? These answers distinguish the stored signal fault from mechanical damage and explain what evidence should control the next step. CF80 is most useful when read beside the complete fault memory, not when translated as an automatic instruction to replace an engine or gearbox controller. • Does CF80 mean the transmission is defective? No. CF80 identifies an engine-management setpoint-torque request signal problem; companion faults and synchronized live data must establish whether any hardware is faulty. • Can low battery voltage store CF80? Yes. If one controller resets while another remains awake, the torque message can vanish; matching undervoltage timestamps support that branch. • Should CF80 simply be cleared? Preserve the scan first. Clearing without recording mileage, voltage, and companion faults removes the evidence needed to find the originating controller. • Can programming cause CF80? It can when coding or integration levels are incompatible. Confirm that timing against repair history before considering software correction. Start with the earliest fault in the event, prove whether engine management produced a credible torque target, and follow the data path toward the receiver. That order turns CF80 from a vague drivetrain message into a testable diagnosis.