Troubleshooting Siemens ET 200M DI/AI 500ms Flicker to 7FFF

Problem Statement and System Context

The reported field symptom is a transient, simultaneous, ~500 ms dropout of every digital input (DI) and every analog input (AI) channel on a Siemens ET 200M remote I/O station that is connected to a host PLC over PROFIBUS-DP through an Optical Bus Terminal (OBT) fiber optic converter. The dropout is intermittent and apparently stochastic: it may occur once per shift or several times per hour. The AI raw values jump to 16#7FFF (decimal +32767) for the duration of the disturbance, then recover to normal process values without operator intervention. All hardware substitutions already attempted (PS 307 power supply, IM 153 interface module, suspect DI cards, and the OBT) have failed to eliminate the event. The pattern - all I/O affected simultaneously, no diagnostic LED extinction reported, no process-side common cause obvious - is the signature of a station-level fault, not a per-channel failure.

This article systematically walks through:

1. Decoding the 16#7FFF AI value in the STEP 7 VAT context.
2. Identifying which physical layers can produce a synchronous, sub-second loss of every input on a single ET 200M station.
3. Verifying the 24 V DC rail, the M/PE bonding, and the PROFIBUS shield termination.
4. Inspecting the OBT fiber optic link budget and connector cleanliness.
5. Capturing and interpreting the PROFIBUS diagnostic frames, the S7 diagnostic buffer, and the IM 153 status bytes.
6. A commissioning-grade verification procedure that confirms the fix.

Reference documentation throughout this article is drawn from the Siemens Industry Online Support portal at support.industry.siemens.com, the ET 200M Distributed I/O System Operating Instructions (covering IM 153-1/-2/-4 PN variants), and the S7-300 Module Data Reference for the SM 321 / SM 331 signal modules and PS 305 / PS 307 power supplies.

Decoding the 0x7FFF AI Reading

For SM 331 analog input modules configured in STEP 7, the raw integer returned to the CPU's process input image is a 16-bit signed value. 16#7FFF is decimal +32767 - the maximum positive value of a 16-bit signed integer. Siemens analog value overflow and wire-break handling follows this convention:

The fact that the AI reads 16#7FFF (overflow) - rather than 16#0000 (which would imply power loss) - during the flicker is informative. It means that during the disturbance the SM 331 module is still energized and still functional; it is reporting that the analog signal it sees is at or above the configured range maximum. This is the classic signature of a process-side common-mode transient: the analog input common pin sees a voltage excursion that pushes every channel into overrange at once. It is also consistent with the field cable shields and signal commons picking up an induced voltage that the analog front-end cannot reject because the M-to-PE bond has been disturbed.

Symptom Taxonomy: Why All Channels Simultaneously?

When every channel on a single ET 200M station misbehaves together, the cause must lie on a layer that is shared by every channel. In order of likelihood for the reported symptom set:

The reported symptom - all DIs drop and all AIs saturate to 0x7FFF, simultaneously, for ~500 ms - is the unique intersection of two events: (1) the DIs dropping implies the binary input voltage threshold is being missed or the DI module is briefly unpowered, and (2) the AIs saturating to 0x7FFF implies the analog common is being pulled up or the SM 331 module is briefly misreading every channel as overflow. The 500 ms duration is the giveaway: it is too long for a single power-supply hold-up event (typical hold-up is 20-50 ms), and too short for a manual intervention. It is the timescale of a PROFIBUS DP retry sequence combined with a brief process-image freeze.

PROFIBUS DP timing math for the symptom duration:

T_bit @ 1.5 Mbps   = 1 / 1.5e6     = 667 ns
T_slot (default)   = 1000 * T_bit  = 667 us per slot
Single retry       = ~3 * T_slot   = ~2 ms
DP slave re-sync   = token rotation + 3-5 retries + parameterization
                    = 100-500 ms typical at 1.5 Mbps with <= 32 slaves

The observed ~500 ms window fits this re-sync envelope exactly. The investigation must therefore concentrate on the layers that can produce a sub-second PROFIBUS re-sync event with a coincident analog overrange.

Root Cause Hypotheses, Ranked

For the symptom described, with the field-substitution history described, the highest-probability root causes are:

1. Impaired or intermittent OBT fiber link. The OBT is the most failure-prone item in the path: connector contamination, fiber bending below the specified minimum bend radius, aging splices, or a marginal optical power budget can produce sub-second link dropouts that the IM 153 sees as a PROFIBUS segment loss. Each dropout costs a re-sync of the DP slave (typically 100-500 ms at 1.5 Mbps depending on T_slot and retries).
2. Marginal 24 V DC rail - either the PS 307 output or the field-side 24 V that powers the DI inputs. Sags to 17-18 V will let the PS 307 still hold its DC OK contact but drop the IM 153 and SM 331 into undervoltage behavior, recovering when the rail rises. Sag events are typically caused by large inrush loads on the same AC feed (VFD DC-bus charging, contactor coils, lighting, heaters).
3. Broken or high-impedance M-to-PE bond. A broken M-to-PE bond allows the 24 V common to float relative to earth. Any induced voltage on the field cables then appears as a common-mode signal on every analog channel simultaneously and as a reference shift on the DI inputs, simultaneously producing both halves of the observed symptom.
4. PROFIBUS cable or connector defect at the IM 153 or the OBT. A marginal 9-pin D-sub connector (especially the +5 V on pin 6 for bus termination) or a corroded shield bond can produce intermittent dropouts without a hard BF.
5. EMC event from a newly installed or changed load. A VFD, soft-starter, or welder newly added to the plant AC distribution can radiate or conduct disturbances that the existing shield termination cannot reject.

Diagnostic Methodology

Resolve the issue by gathering hard evidence before swapping any more hardware. The following sequence is ordered by cost-of-attempt and by the diagnostic value of the artifact produced.

Capture the S7 diagnostic buffer at the moment of the event

On the host S7 CPU, open STEP 7 and connect online. In the CPU's Diagnostic Buffer (PLC → Module Information → Diagnostic Buffer), look for entries with the time stamp matching the field report of a flicker. Filter for OB 70 (I/O redundancy error), OB 82 (diagnostic interrupt), OB 86 (rack/station failure), OB 100 (warm restart), and OB 122 (I/O access error). Each entry records the logical address of the affected slot/module, the time stamp to the CPU's millisecond clock, and the event code. A burst of OB 86 entries with the ET 200M's diagnostic address is direct evidence of a PROFIBUS segment dropout of that station.

Sample diagnostic buffer entry for a station failure:

Event 1 of 20:  Station failure
  Event ID          : 0x39E0
  OB                : OB 86 (Rack/station failure)
  Time stamp        : 14:32:07.412
  Diagnostic address: 1023 (logical address of the IM 153)
  Event appears     : Rack 0, Slot 0, Station failure
  Event disappeared : Rack 0, Slot 0, Station return

Use a VAT table or watch table on the affected AI channels

Open STEP 7 and create a VAT table containing the input words (IW) of the AI module's channels. Enable Monitor (glasses icon) and watch the values during a flicker event. Confirm whether the value is precisely 16#7FFF or some other sentinel, and whether the DI inputs (I) in the same VAT show a coincident 1→0 transition. The transient's exact value narrows the cause: 16#7FFF with stable DIs implies analog common / cable routing; 16#7FFF with dropping DIs implies 24 V rail; 0x0000 with dropping DIs implies full station power-down.

Log the IM 153 status LEDs

Place a continuous-record camera (a phone in video mode is acceptable for a one-shift capture) on the ET 200M station's interface module so the SF, BF, and ACT LEDs are in frame. Review the footage in 4× playback aligned with the diagnostic buffer entries. Specifically watch for:

• ACT LED extinguishing - the IM 153 is off-bus; the cause is upstream (PROFIBUS or fiber).
• BF LED flashing or steady - bus fault; the DP slave is not receiving valid frames.
• SF LED illuminating - station fault, typically group error on a backplane module.
• DC OK LED on PS 307 dimming or flickering - direct evidence of 24 V rail brownout.

Capture PROFIBUS traffic on the segment

Connect a PROFIBUS protocol analyzer at the OBT's electrical side or at the host PLC's PROFIBUS port. Trigger on Slave Not Found, Diagnostic Request by the master, or on a gap in the token-passing sequence. Confirm that during the event the master reports "slave lost" and on recovery re-enters the DP slave into the poll cycle.

Measure the fiber optic receive level

Most OBTs and Siemens OLMs (Optical Link Modules) include either an LED-bar receive-level indicator or a diagnostic parameter that reports the optical receive power in dBm. Capture this value continuously or review its minimum during the event. A nominal plastic-fiber (POF) link at 660 nm should show ≥ -20 dBm; a nominal HCS (200/230 µm) link at 650 nm should show ≥ -24 dBm; a nominal glass (9/125 µm) single-mode link at 1300 nm should show ≥ -30 dBm. A drop of more than 3 dB during the event is the smoking gun for fiber impairment.

Measure the 24 V DC rail with a recording voltmeter

Place a true-RMS recording digital multimeter (Fluke 289, Hioki PW3198, or similar with a 1 ms sample rate and Min/Max logging) across the 24 V output of the PS 307 and at the SM 331 module's power terminals. Run it for at least 24 hours. The Min reading during a flicker event is the diagnostic. If the Min is above 22.0 V, the rail is healthy; if it drops below 18.5 V transiently, the rail is the cause.

Measure the M-to-PE bond impedance

With the station powered down and locked out, measure the resistance between the 24 V common terminal (M) on the PS 307 and the panel's PE bar using a four-wire milliohmmeter or a standard DMM in low-ohms mode. The reading should be below 1 Ω; many Siemens installation guides recommend ≤ 0.5 Ω. A reading above 5 Ω indicates a degraded bond that can allow the 24 V common to float during high-noise events.

Power Supply and 24 V DC Rail Verification

The PS 305 / PS 307 power supplies used in S7-300 / ET 200M stations are specified for an output of 24 V DC ± 3% (typ. 24.0-24.8 V under load), with a 5 A or 10 A rating depending on variant. The SM 331 analog modules are specified to operate down to 20.4 V (lower limit of 24 V DC "B" range per EN 61131-2) but below ~18.5 V the on-board DC/DC converter enters dropout and the module's output data freezes or reads invalid. The DI modules (SM 321 with 24 V DC inputs) accept a binary "1" between +13 V and +30 V referenced to M. If the 24 V rail sags to 13-15 V, every DI input reads "0" simultaneously.

The field engineer's report that the entire panel's 24 V supply has been replaced rules out a hard failure of the PS module but does not rule out a transient brownout caused by another load on the same AC feed. Investigate:

• Other loads on the same 230 V AC branch circuit feeding the PS 307 (VFDs, soft-starters, contactor coils, lighting).
• Loads on the same 415 V AC distribution upstream (large motor starts).
• DC-side inrush: large solenoid valves, 24 V DC motors, or capacitor banks on the same 24 V rail.

Grounding, Equipotential Bonding, and Shield Termination

Siemens PROFIBUS and ET 200M installations follow a documented grounding topology that, when violated, produces precisely the simultaneous, station-wide symptom described in the field report. The key principles (from the Siemens ET 200M manual and the S7-300 Installation Guide):

1. Single-point star ground. The panel's PE bar is bonded to the 24 V DC common (M) at one point only, typically at the PS 307's M terminal or at a dedicated ground bar near the PS.
2. Shield terminated at PE only. PROFIBUS cable shield and analog cable shields are bonded to the PE bar at the panel entry using shield clamps that provide 360° contact. They are not bonded at the field-device end; doing so creates a ground loop.
3. Equipotential bonding between cabinets. If the ET 200M and the host PLC are in different cabinets, a separate equipotential bonding conductor (typically 16 mm² Cu) is run between the two PE bars in addition to the PE/ground conductor in the supply cable.

The field report explicitly notes that the panel has been given a "separate electronic earthing" and that the PROFIBUS cable shield has been "directly connected to electronic earthing via cable." This is consistent with correct practice, but the diagnostic must verify that:

• The M-to-PE bond is intact and below 1 Ω.
• The shield termination is via a 360° clamp, not a "pigtail" wire.
• The PROFIBUS cable's drain wire (if present) is bonded to PE at the same point as the shield.

A common field defect is a piggy-back or daisy-chained M-to-PE bond: the M terminal is bonded to PE via a short wire to a din-rail-mounted ground bar that is itself bonded to PE via a longer run. If any of those intermediate bonds is loose or corroded, the bond is high-impedance at high frequency, allowing the 24 V common to float during fast transients while still passing a continuity check with a DMM at DC.

OBT Fiber Optic Link and PROFIBUS Physical Layer

The OBT converts electrical PROFIBUS-DP to fiber optic and back. Common Siemens part numbers for this function include the OLM (Optical Link Module) family - 6GK1 502-1CB00, 6GK1 502-3CB00, 6GK1 503-2CC00, and similar - which provide electrical PROFIBUS on one side and one or two optical ports on the other. Generic third-party PROFIBUS fiber converters that present the same PROFIBUS DP slave/master-facing electrical interface may also be in use.

PROFIBUS over fiber at 1.5 Mbps has the following operational considerations:

Failure modes specific to the OBT path:

1. Dirty or loose optical connector. A single speck of contamination on a POF connector face can introduce 5-10 dB of loss, which at the typical link budget of 10-15 dB can drop the link to the noise floor. Vibration or thermal cycling can modulate the loss and produce intermittent outages.
2. Bend radius violation. Plastic optical fiber has a minimum bend radius of 25-30 mm; below that, macrobending losses increase dramatically. A cable tie pulled too tight or a fiber routed around a sharp edge can produce intermittent loss.
3. OBT power supply instability. The OBT typically takes its 24 V DC from the same panel supply as the ET 200M. A brownout on the OBT (which is more sensitive to undervoltage than the IM 153) will cause the optical transmitter to drop output briefly while the IM 153 itself stays on-bus.
4. PROFIBUS connector at the OBT. The 9-pin D-sub at the OBT's electrical port, and the matching connector at the IM 153's port, must have pin 6 (+5 V bus termination power) connected if termination is active, and pin 2/7 (data A/B) must have the 220 Ω termination network enabled if the OBT is the segment end.

Interface Module (IM 153) Diagnostics and Bus Timing

The IM 153-1 and IM 153-2 maintain internal status that is exposed via PROFIBUS diagnostic frames. When the IM 153 detects a bus fault, it transmits a diagnostic message with the following relevant bits in the first two diagnostic bytes (per IEC 61158-6 / PROFIBUS DP-V0):

During a transient PROFIBUS dropout, the master will issue a Global Control freeze or clear command as part of its recovery; the IM 153 will report Diag.NotReady while it re-syncs to the master's parameterization. The process image held in the S7 CPU's input peripheral area is not updated during this window; by default, an S7-300 CPU leaves the last value in place (no substitute value), so the field sees every DI frozen at 0 and every AI frozen at its last value (or at 0x7FFF if the SM 331 had already written overflow prior to the dropout).

The IM 153's SF (red) LED will be lit solid if the IM 153 itself has a fault (e.g., no PROFIBUS address set, or backplane error); it will be lit flashing if there is a group fault. The BF (red) LED will be lit solid if no PROFIBUS communication is occurring, and flashing if communication is intermittent. The ACT (green) LED indicates active data exchange with the master and is the most informative indicator for the field engineer.

Step-by-Step Resolution Procedure

Execute the following in order. Stop as soon as the diagnostic evidence points unambiguously at a cause; do not perform later steps unless the evidence warrants them.

Step 1 - Confirm with the S7 diagnostic buffer

1. Connect STEP 7 online to the host CPU.
2. Open the CPU's diagnostic buffer (PLC → Module Information → Diagnostic Buffer).
3. Filter for OB 86 (rack failure) and OB 82 (diagnostic interrupt).
4. Note the time stamp and the logical address of every entry.
5. If OB 86 fires against the ET 200M's diagnostic address, the cause is at the PROFIBUS layer (segment, OBT, or fiber). Proceed to Step 4.
6. If OB 86 does not fire, but OB 82 fires against the SM 331's logical address with channel diagnostics reporting overflow, the cause is at the analog signal layer. Proceed to Step 3.
7. If neither fires, the cause is downstream of the I/O bus (e.g., field-side 24 V sag) - proceed to Step 2.

Step 2 - Verify the 24 V DC rail with a recording voltmeter

1. Place a recording DMM on the PS 307 24 V output terminals, configured for Min/Max capture at the highest available sample rate (≥ 100 ms).
2. Place a second recording DMM on the field-side 24 V supply that powers the DI inputs.
3. Run for at least one shift covering several flicker events.
4. If the 24 V rail sags below 20.4 V during a flicker, identify and remediate the source of the sag (inrush load, undersized supply, AC feed disturbance).
5. If the rail stays within 22-26 V across all events, the 24 V rail is exonerated; proceed to Step 3.

Step 3 - Verify M-to-PE bond and shield termination

1. De-energize and lock out the station.
2. Measure resistance from the PS 307 M terminal to the panel's PE bar with a four-wire milliohmmeter. Reading must be ≤ 1 Ω.
3. Inspect the PROFIBUS cable shield termination - the shield must be clamped to the PE bar with a 360° clamp (e.g., Weidmüller KLBÜ or Phoenix Contact SH-PCB), not a pigtail.
4. Inspect every analog cable shield at the panel entry - same requirement.
5. If the M-to-PE bond is > 1 Ω, re-make the bond with a dedicated 6 mm² Cu conductor and a ring terminal torqued to the manufacturer's spec.

Step 4 - Verify the OBT fiber optic link

1. With the station powered, measure the optical receive level at both ends of the fiber using a calibrated optical power meter appropriate to the fiber type (660 nm for POF, 850/1300 nm for glass).
2. Compare the measured level to the OBT's specified receiver sensitivity with margin. A typical Siemens OLM requires > -20 dBm at 660 nm on POF and > -24 dBm at 1300 nm on glass; the operating margin should be ≥ 6 dB.
3. Clean every optical connector per the connector manufacturer's procedure (typically isopropyl alcohol + lint-free wipe + dry).
4. Inspect the fiber routing for bend radius violations. Plastic optical fiber has a minimum static bend radius of 25 mm; dynamic (moving) applications require 50 mm.
5. If the OBT has an LED-bar receive-level indicator, photograph it at one-minute intervals over one shift and look for excursions.

Step 5 - Verify the PROFIBUS electrical segment

1. Confirm the segment topology: the OBT should be at one end, the IM 153 at the other, with no other devices. If both ends have PROFIBUS connectors, only one should have termination enabled.
2. Measure the segment resistance between pin 3 (data B) and pin 8 (data A) at the IM 153's PROFIBUS connector with the segment powered down. With termination active at the far end, the reading should be ≈ 220 Ω; with no termination active, the reading should be high (≥ 1 kΩ).
3. Check the +5 V on pin 6 of the IM 153's connector (bus terminator power) - should be 4.75-5.25 V DC.
4. Inspect the 9-pin D-sub connector for bent pins, broken solder joints on the data lines, or loose strain relief.

Step 6 - Capture and analyze PROFIBUS traffic during an event

1. Connect a PROFIBUS analyzer at the host PLC's PROFIBUS port.
2. Trigger on "Slave Lost" or "Diagnostic Request" events.
3. Capture the trace including the gap, the master's response, and the slave's recovery.
4. If the trace shows the IM 153 dropping off-bus for exactly the duration of the field-reported flicker (≤ 1 s) and then re-entering, the cause is upstream of the IM 153 (PROFIBUS or fiber).

Step 7 - Replace the OBT with a known-good spare

Only after Steps 1-6 have exonerated the power, grounding, and fiber as the diagnostic evidence indicates - or if a marginal receive level was observed in Step 4 - replace the OBT with a Siemens OLM (e.g., 6GK1 502-1CB00 for POF) or the original-equivalent third-party converter. After replacement, run a 24-hour soak test with continuous recording of the AI Min/Max and the 24 V rail Min/Max.

Verification, Acceptance Test, and Field-Proven Patterns

Once the corrective action is in place, perform the following acceptance test before declaring the issue closed:

1. 24-hour continuous monitoring. Install a recording DMM on the 24 V rail and a recording voltmeter on the optical receive level (or use the OBT's own diagnostics). Both must show zero excursions outside their respective tolerances.
2. Diagnostic buffer review. After 24 hours, the S7 CPU's diagnostic buffer must contain no OB 86 entries against the ET 200M's diagnostic address and no OB 82 entries against the SM 331 with channel-overflow flags.
3. AI histogram. Using the VAT table or a script in the S7 CPU, log every AI raw value over 24 hours and produce a histogram. Every channel's distribution must be normal (no spikes at 0x7FFF, no spikes at 0x0000, no gaps).
4. DI event log. Log every DI 1→0 transition over 24 hours; every transition must correspond to a known field event. Spurious transitions not corresponding to a field event indicate a remaining disturbance.
5. PROFIBUS error counters. Many PROFIBUS diagnostic tools expose slave-side error counters (CRC errors, frame errors, retry counts). These counters must not increment over 24 hours.

The following patterns recur in field reports of ET 200M station-wide flickering and should be on every engineer's mental checklist:

• "It's always the power supply" reflex. Most field engineers' first instinct is to replace the PS 307. In the case described, the PS has already been replaced and the symptom persists. This is a strong signal that the cause is downstream of the PS (load, wiring) or upstream (PROFIBUS, fiber).
• "It's the field device" assumption. When all channels flicker simultaneously, no single field device is to blame. The simultaneous coincidence across all channels is the diagnostic.
• "The shield is grounded" is not the same as "the shield is terminated correctly." A pigtail ground wire from a PROFIBUS cable shield to the PE bar can pass a continuity check with a DMM but present an impedance of tens of ohms at the frequencies of fast transients (10-100 MHz), which is exactly the band where PROFIBUS and analog signals are vulnerable. Always use a 360° shield clamp.
• "The fiber was tested when installed" ages. Optical connectors accumulate contamination over years of service, especially in industrial environments with oil mist, dust, or condensation. A 6 dB link margin at commissioning can become a 1 dB margin five years later. Re-verify every 12-24 months.
• 0x7FFF can also be a "stuck" reading on a true overflow. If a 4-20 mA field transmitter fails in a way that pushes its loop current above 20 mA (e.g., a short across the loop shunt), the SM 331 reads 0x7FFF. The diagnostic to distinguish a channel fault from a station-wide event is the coincidence: a single channel at 0x7FFF is a field fault; every channel at 0x7FFF simultaneously is a station event.
• Re-check after every plant change. The field engineer reports no changes prior to the symptom's appearance. This is the standard report from operators who are unaware that an electrical or HVAC change was made upstream. Walk the plant and the AC distribution one-line for any new VFD, soft-starter, welder, UPS, or large inductive load installed in the prior 60 days.

For the symptom set described - simultaneous DI drop and AI saturation to 0x7FFF for ~500 ms, with the field engineer's prior substitution history and the dedicated electronic earthing already added - the highest-probability single root cause is a marginal OBT fiber optic link, with a secondary candidate of a marginal M-to-PE bond that passes DC continuity but fails at transient frequencies. The corrective action is to clean, inspect, and power-meter the OBT fiber link; replace the OBT with a known-good unit if the link budget is marginal; and re-confirm the M-to-PE bond with a four-wire milliohmmeter (not a DMM in continuity mode). Verify with a 24-hour soak test recording the 24 V rail Min/Max and the AI histogram.

Primary references for the underlying specifications are the Siemens Industry Online Support portal at support.industry.siemens.com (search for ET 200M Distributed I/O System, IM 153, S7-300 Module Data, PROFIBUS Network Manual), the PROFIBUS standard IEC 61158-6, the PLC equipment standard IEC 61131-2:2013, and the panel grounding standard IEC 62103.

Frequently Asked Questions