S7-300F SM 336F: Deactivate Spare Channels to Suppress Wire Break

David Krause14 min read
S7-300SiemensTroubleshooting
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

Problem Overview and Affected Hardware

The Siemens SM 336F failsafe analog input module (order number 6ES7 336-4GE00-0AB0) reports wire break diagnostics on channels that have no sensor wired. The diagnostic event appears in the F-CPU diagnostic buffer, lights the SF (group fault) LED on the module, and - if not handled correctly - can trip the F-CPU into a safe state or force the safety program into a passivated state for the affected channels. This is the expected behavior of a failsafe module, not a hardware defect: the F-module monitors every activated channel continuously and treats an open input as a fault because it cannot verify the safety function on that channel.

The fix is to mark unused channels as deactivated in the failsafe parameter assignment, which removes them from safety monitoring and from the diagnostic event generator. No dummy loads, jumper wires, or termination resistors are required, and - in fact - adding such loads is rejected as a non-compliant workaround for SIL 2 / SIL 3 systems.

Item Value
Module SIMATIC SM 336F (F-AI)
Order number (MLFB) 6ES7 336-4GE00-0AB0
Function Failsafe analog input (F-AI)
Number of channels 6 inputs in 3 paired groups
Channel groups Pair 0 (CH0/CH1), Pair 1 (CH2/CH3), Pair 2 (CH4/CH5)
Range - Pair 0 / Pair 1 Current 4-20 mA or 0-20 mA
Range - Pair 2 Voltage 0-10 V or RTD / resistance
Resolution 15 bits + sign
Update time Per-channel group, configurable
Safety integrity SIL 2 (1oo1) / SIL 3 (1oo2); Cat 3 / PL d, Cat 4 / PL e (ISO 13849-1)
Protocol PROFIsafe over S7-300 backplane or PROFINET (via ET 200M + IM 153-4 PN)
Configuration tool STEP 7 V5.x or TIA Portal with S7 F-ConfigurationPack
Compatible F-CPUs CPU 315F-2 DP/PN, CPU 317F-2 DP/PN, CPU 319F-3 PN/DP, and equivalent

The module occupies one slot in the S7-300 / ET 200M rack. It is documented in the SIMATIC S7-300 Module Data manual and the SIMATIC S7 F/FH Systems - Configuring and Programming manual.

Root Cause Analysis

Failsafe analog input modules implement permanent cross-check diagnostics on each activated channel. For a 4-20 mA loop the module sources a small test current and measures the resulting loop voltage. If the measured current falls below approximately 3.6 mA the module asserts a wire-break diagnostic. For 0-10 V inputs a similar test verifies that the input voltage sits inside the configured range; an open input sits at an undefined potential and is also flagged.

When a new project is created, every channel of the SM 336F defaults to activated with a default measurement type (typically 4-20 mA on current pairs). Spare channels have no sensor, so they immediately trigger the wire-break diagnostic on the first I/O update after startup.

Engineering note: Wire-break diagnostics on a failsafe module are not nuisance alarms - they are the evidence that the module can actually detect a broken cable or failed sensor, which is mandatory for SIL 2/3. The problem is purely that channels intentionally left unwired must be removed from safety monitoring by parameter.

Three failure patterns typically appear at first commissioning:

  1. Wire break on every unused current channel (most common) - default 4-20 mA range and no field wiring.
  2. Wire break on the voltage/RTD pair - default 0-10 V range on CH4/CH5 with no sensor.
  3. Wire break on the partner of a single wired channel - sensor wired to CH0 only, CH1 left open, partner not deactivated.

All three patterns resolve with the same fix: set Evaluation of the sensor (or Sensor evaluation) to deactivated for the unwired channel.

Preconditions

  1. STEP 7 V5.5 SPx or TIA Portal V13 SP1 / V15.1 / V16 / V17 / V18 with the matching S7 F-ConfigurationPack installed on the engineering station.
  2. Access to the offline S7-300 / ET 200M station configuration that matches the running CPU.
  3. The F-CPU's safety password (F-password) if the F-CPU is password-protected.
  4. An empty / writable path to download the modified HW Config into the target CPU.
  5. A current backup of the safety program (F-block container) before any parameter change.
  6. An updated I/O list that explicitly identifies which channels are spare and which are active.

Solution: STEP 7 V5.x (HW Config)

  1. Open SIMATIC Manager and load the offline S7-300 project.
  2. Open HW Config for the S7-300 station (or ET 200M station for distributed I/O).
  3. Select the SM 336F (order number 6ES7 336-4GE00-0AB0) in the rack view.
  4. Double-click the module (or right-click → Object Properties).
  5. Switch to the Parameters tab. Three channel pairs are visible: Pair 0 (CH0/CH1), Pair 1 (CH2/CH3), Pair 2 (CH4/CH5). Each pair has two drop-downs - lower channel and upper channel.
  6. For every unused channel, change Sensor evaluation (or Evaluation of the sensor) from activated to deactivated.
  7. If both channels of a pair are spare, deactivate both. The pair remains in the project but is excluded from safety diagnostics.
  8. Confirm OK to close the Properties dialog.
  9. From the menu: Station → Save and Compile.
  10. Download to the target CPU: PLC → Download to Target System. Confirm the F-password prompt when it appears.
  11. Confirm any safety-mode prompts. The CPU does not STOP for a pure parameter modification, but the safety signature changes.

What NOT to do on spare channels

  • Do not install 250 Ω termination resistors across unused 4-20 mA inputs to "trick" the module. The channel is still activated and any drift or noise will eventually cross the wire-break threshold.
  • Do not leave the channel at its default settings and ignore the diagnostic. F-modules must be intentionally configured for every channel, including unused ones.
  • Do not edit the F-parameters without recording the new safety signature in the project's safety log.

Solution: TIA Portal

  1. Open the project in TIA Portal (V15.1 or later recommended for current F-ConfigurationPack support).
  2. Open Devices & Networks and switch to Device View.
  3. Click the SM 336F module in the rack of the S7-300 / ET 200M station.
  4. In the Inspector window, navigate to Properties → Module parameters.
  5. Expand the channel groups (Pair 0, Pair 1, Pair 2). Each pair exposes parameters for the lower and upper channel.
  6. For every unused channel, set Sensor evaluation to deactivated.
  7. Save the project, then Compile → Hardware (rebuild all).
  8. Establish an online connection to the F-CPU and download. Authenticate with the F-password when prompted.
  9. Confirm the safety signature prompt and the automatic safety program recompile.
Tip: In TIA Portal, deactivated channels still appear in the F-I/O DB but return the substitute value (typically 0) and the quality code substitute / deactivated. No diagnostic interrupt is raised for these channels.

Verification and Diagnostic Clearing

After the parameter change has been downloaded to the F-CPU, verify the fix in four steps.

  1. Diagnostic buffer: Open Online & Diagnostics → Diagnostic buffer (TIA) or PLC → Module Information → Diagnostic Buffer (STEP 7). Confirm no further wire-break entries for the previously reported channel numbers.
  2. Module LEDs: The SF (group fault) LED on the SM 336F extinguishes. The green active / ready LED remains on. If the module is on an ET 200M station, also confirm the IM 153-4 SF LED is off.
  3. CPU mode: The F-CPU remains in RUN. The safety program (F-runtime group) continues to execute normally.
  4. Live channel readout: In the F-I/O DB (F-channel-driver DB) or via the F-shared DB, the deactivated channel returns a substitute value (typically 0) and the quality code indicates substitute / deactivated.
Tip: If the wire-break entry persists in the diagnostic buffer after the download, it is the historical event from before the fix. Clear the diagnostic buffer (PLC → Clear/Reset Diagnostic Buffer) and monitor for new entries. Only new entries indicate an unresolved fault.

Channel Pairing (1oo1 / 1oo2) and SIL Modes

The SM 336F always evaluates channels in pairs to deliver failsafe integrity. There is no true single-channel safety mode; the closest equivalent is a 1oo1 evaluation with the partner channel deactivated. Supported modes:

Mode Description Achievable SIL Use case
1oo1 (single channel) One sensor wired to one channel; partner deactivated SIL 2 / Cat 3 / PL d Lower-demand safety functions
1oo2 single-sided One sensor wired to two channels; one output voting SIL 3 / Cat 4 / PL e Single sensor, redundant wiring
1oo2 double-sided Two independent sensors on two channels SIL 3 / Cat 4 / PL e High-integrity process shutdown

When wiring only one sensor per pair (the most common configuration), the partner channel must be deactivated - exactly the procedure in this article.

SM 336F Channel Pair Configuration Pair 0 (CH0/CH1) CH0: Activated (sensor wired) CH1: Deactivated (spare) Mode: 1oo1 single-channel SIL 2 / Cat 3 / PL d Pair 1 (CH2/CH3) CH2: Activated CH3: Activated Mode: 1oo2 dual-channel SIL 3 / Cat 4 / PL e Pair 2 (CH4/CH5) CH4: Deactivated CH5: Deactivated Mode: spare pair No safety function

Wire-Break Detection Parameters and Diagnostic Events

The wire-break check is enabled by default for every activated channel and is tied to the configured measurement type:

Range Wire-break trip condition
4-20 mA I < approximately 3.6 mA
0-20 mA Trip typically suppressed (no valid lower limit)
0-10 V U < approximately 0.5 V or open line detected
RTD / Resistance R > configured upper limit

If wire-break detection must be disabled on an active channel for technical reasons (e.g., a sensor cannot source 4 mA minimum), the parameter Wire break / Short circuit can be cleared individually. This is a deliberate safety-engineering decision and must be documented in the safety validation report, because removing the wire-break check on an active channel reduces the diagnostic coverage.

Diagnostic Buffer Event Reference

The SM 336F writes standardized diagnostic events readable in the F-CPU diagnostic buffer. Typical entries:

Event text (English) Event text (German) Meaning
Channel x: Wire break Kanal x: Drahtbruch Input current / voltage below detection threshold
Channel x: Short circuit Kanal x: Kurzschluss Sensor supply or input shorted to ground / 24 V
Module OK Baugruppe OK Module-side diagnostic cleared
Parameter assignment error Parametrierfehler Configuration inconsistent (e.g., mixed ranges in one pair)
Channel information present Kanalspezifische Diagnose At least one channel is in fault state
External fault Externer Fehler Fault external to module (e.g., sensor)
Internal fault Interner Fehler Module-internal fault; replace module

The exact event IDs and language are visible in the F-CPU's diagnostic buffer regardless of the HMI language setting.

S7 F-ConfigurationPack and Engineering Tool Versions

The S7 F-ConfigurationPack is the software extension that exposes the safety parameters (sensor evaluation, channel pairing, discrepancy time, etc.) inside HW Config / TIA Portal. Without it, the Parameters tab for the SM 336F either does not appear or is greyed out. Versions must match the base STEP 7 / TIA Portal version:

Engineering tool Matching F-ConfigurationPack
STEP 7 V5.5 SPx S7 F-ConfigurationPack V5.5 SPx
TIA Portal V15.1 S7 F-ConfigurationPack V15.1
TIA Portal V16 S7 F-ConfigurationPack V16
TIA Portal V17 S7 F-ConfigurationPack V17
TIA Portal V18 S7 F-ConfigurationPack V18

If the F-ConfigurationPack is missing, install it from the Siemens Industry Online Support entry for the F-ConfigurationPack, restart the engineering software, and re-open HW Config. Mismatched versions between the F-ConfigurationPack and the base TIA Portal are the most common reason for the safety Parameters tab not being visible.

Troubleshooting Matrix

Symptom Probable cause Action
Wire break on unused channel immediately after first commissioning Channel not deactivated in F-parameter assignment Deactivate per Step-by-Step Procedure above
Wire break on wired channel Open cable, failed sensor, sensor < 3.6 mA minimum Check wiring loop continuity and sensor output
Wire break persists after deactivation Old diagnostic buffer entry not cleared Clear diagnostic buffer or warm-restart the F-CPU
F-CPU goes to STOP after parameter download Safety signature mismatch / safety program not recompiled Recompile F-program with new signature; re-authenticate with F-password
Parameters tab is greyed out S7 F-ConfigurationPack missing or version mismatch Install matching F-ConfigurationPack; re-open HW Config
"Evaluation of the sensor" field not present Older GSD file or wrong module variant in rack Confirm MLFB is exactly 6ES7 336-4GE00-0AB0; update HW catalog
Channel pair cannot be configured independently SM 336F evaluates pairs only Move single-channel sensor to a pair and deactivate the partner
Wire break on spare ET 200M F-channel Same root cause as central rack Deactivate in ET 200M station configuration, not in F-CPU HW Config
Parameter download rejected with "F-password required" F-CPU is password-protected Enter the F-password in the online download dialog
Channel reads 0x7FFF in F-I/O DB Deactivated channel returns substitute value, not a fault Verify the quality code in the F-I/O DB; no action required
Wire break only on RTD pair (CH4/CH5) Default 0-10 V range with no sensor Deactivate CH4 and CH5; or configure RTD range with correct wiring

Safety Program Re-Validation and Migration to S7-1500F

Any change to an F-module's parameters counts as a modification to the safety-related system per IEC 61511 / IEC 61508 / IEC 62061. After the parameter change:

  1. Document the new safety signature and parameter set in the project's safety validation report.
  2. Perform a proof test of every safety function that uses the SM 336F, including a deliberate wire-break test on each activated channel to verify that the diagnostic still trips the safety shutdown.
  3. Update the as-built documentation and re-issue the safety manual to the operations team.
  4. If the installation is regulated (e.g., functional safety per Machinery Directive 2006/42/EC), notify the notified body as required.
  5. Re-issue the PFD / PFH calculation for the safety function with the new activated channel count.
Warning: Deactivating a channel removes it from safety monitoring. Only deactivate channels that are physically not wired and are documented as spare in the I/O list. Never deactivate a channel that carries a safety sensor.

Migration path to S7-1500F

For new installations on S7-1500F or ET 200SP, the equivalent F-AI module is the 6ES7 536-1MF00-0AB0 (F-AI 4xI) in ET 200SP. Parameter assignment is entirely inside TIA Portal; no separate F-ConfigurationPack is needed for safety parameter visibility. The same deactivation workflow applies: mark unused channels as deactivated in the channel properties.

Related F-modules

Module Function Use when
SM 326F (6ES7 326-1RF00-0AB0) F-DI 24 V, 8-channel Failsafe digital inputs (e.g., E-stops, guards)
SM 326F (6ES7 326-2BF01-0AB0) F-DI 24 V, 24-channel Higher-density F-DI on F-CPU
SM 336F (6ES7 336-4GE00-0AB0) F-AI 6-channel This article
SM 336F (6ES7 336-1HE00-0AB0) F-AI 8-channel Higher-density F-AI on F-CPU
ET 200M + IM 153-4 PN Distributed F-I/O PROFIsafe over PROFINET
ET 200SP F-AI 4xI (6ES7 536-1MF00-0AB0) F-AI in ET 200SP Newer installations on S7-1500F

FAQ

Why does my brand-new SM 336F report wire break on every channel at first startup?

Every channel of the SM 336F defaults to activated with the 4-20 mA measurement type. With no sensor wired, the input current sits below the 3.6 mA wire-break threshold and the module generates a wire-break diagnostic per channel. Deactivate each unused channel in HW Config → Parameters → Sensor evaluation = deactivated, then re-download the HW Config to the F-CPU.

Do I need to install a resistor or loop simulator on every spare SM 336F channel?

No. Deactivating the channel in the F-parameter assignment is the correct SIL-compliant method. Adding a 250 Ω resistor across a 4-20 mA spare channel produces ~12 mA, which suppresses the wire-break alarm, but the channel still consumes a safety slot and any subsequent sensor failure will not be detected because the module has been bypassed rather than configured. The official Siemens method is parameter-level deactivation.

What happens if I change F-parameters without entering the safety password?

The download is rejected by the F-CPU. The CPU stays in RUN with the old parameters and the modified HW Config is reported as inconsistent with the running safety signature. Re-attempt the download with the correct F-password; the safety program signature will be updated and recorded in the safety log.

Does deactivating a channel affect the safety integrity level of the remaining channels?

No. Deactivating a channel only removes that channel from safety monitoring. The remaining activated channels retain their configured SIL / Cat / PL rating (e.g., SIL 3 in 1oo2 mode). However, the overall PFD / PFH calculation of the safety function must be re-issued to reflect the new activated channel count.

My spare channels are on an ET 200M station, not the central rack. Where do I deactivate them?

In HW Config / TIA Portal device view, open the ET 200M station, select the SM 336F inside the distributed station, and apply the same Parameters tab → Sensor evaluation = deactivated procedure. The configuration is stored in the ET 200M station configuration, which is downloaded via PROFINET / PROFIBUS to the IM 153 interface module.

Can I suppress wire-break diagnostics without deactivating the channel?

Yes - the parameters Wire break and Short circuit can be cleared independently of Sensor evaluation. However, this is a deliberate safety-engineering decision that reduces diagnostic coverage on an active channel. It must be justified in the safety validation report and approved by the safety engineer. Never use this as a substitute for deactivating truly spare channels.

Back to blog