ET 200SP AI 6ES7134-6HB00 Update Time: S7-1500 TIA Configuration

David Krause15 min read
I/O ModulesSiemensTechnical Reference
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

ET 200SP AI 6ES7134-6HB00 Update Time: S7-1500 TIA Configuration

Technical reference for the SIMATIC ET 200SP AI 2×U/I 2-/4-wire HS analog input module (order number 6ES7134-6HB00-0CA1). Covers default update time, sample/conversion timing, peripheral-access reads (IWn:P), FC / FB design patterns, integration-time trade-offs, isochronous PROFINET configuration, and TIA Portal commissioning checks for S7-1500 controllers.

Module Identification and Scope

The order number 6ES7134-6HB00-0CA1 identifies the SIMATIC ET 200SP AI 2×U/I 2-/4-wire HS (High Speed) analog input module. The HS suffix designates the high-speed variant of the ET 200SP AI family with isochronous-mode support, sub-millisecond update capability, and dedicated channel-diagnostic interrupts. The module provides two channels that can each be wired as voltage (U) or current (I), in 2-wire or 4-wire connection modes, with 16-bit resolution.

Decoding the MLFB (Machine-Readable Product Designation):

  • 6ES7 - SIMATIC product family identifier
  • 134 - Function class: analog input module
  • 6 - ET 200SP distributed I/O system
  • HB - AI 2×U/I 2-/4-wire, High Speed variant
  • 00 - Functional state index (firmware family)
  • 0CA1 - Hardware revision / firmware version suffix
Always match the exact firmware version printed on the physical module's label against the device version selected in the TIA Portal hardware catalog. A version mismatch typically yields the diagnostic-buffer entry "Incorrect module" or "Firmware version not supported", and the module will not enter cyclic data exchange.

Update-Time Fundamentals: Sample, Conversion, Cycle

Three timing values govern when a value visible to the user program reflects a real electrical change at the screw terminal:

  1. Sample time (t_S) - The interval at which the module's ADC samples the input signal. Shorter sample time yields wider bandwidth but increases noise pickup.
  2. Conversion time (t_C) - The interval the ADC requires to digitize the sampled value. For the 6ES7134-6HB00-0CA1 in default TIA configuration, this is 10 ms per channel as confirmed in the module discussion.
  3. Update time (t_U) - The interval at which the module transfers a freshly converted value to the backplane bus, refreshing the process image visible to the CPU.

The end-to-end latency seen by a function block = module update time + PROFINET update time + OB1 / OB1x cycle time. With 10 ms default and a 2 ms OB1 cycle, the program-visible latency is approximately 12 ms.

Reference: S7-1200 Signal-Board Update Times

For comparison, the S7-1200 analog signal board (SB) documentation publishes the following values, illustrating how integration frequency drives update rate:

Integration selection Sample time Update time
400 Hz (2.5 ms) 0.156 ms 0.156 ms
60 Hz (16.6 ms) 1.042 ms 1.042 ms
50 Hz (20 ms) (per manual) (per manual)

Source: Sample time and update times for the analog inputs - TIA Siemens Documentation

The ET 200SP AI HS module extends the range significantly on the high end, supporting integration times as short as 2.5 ms / 400 Hz in isochronous mode. The exact minimum update time for the 6ES7134-6HB00-0CA1 must be verified against the module's manual because the figure varies with firmware revision and PROFINET send-clock selection.

Default Configuration: 10 ms Update Time

Out of the box, with both channels enabled at the default integration setting, the 6ES7134-6HB00-0CA1 returns a refreshed value every 10 ms. The user program sees a new value at the IW input word at each OB1 cycle, with a maximum latency of one OB1 cycle plus one module update interval.

Default configuration produces these timing values:

  • Sample time per channel: approximately 5 ms
  • Conversion time per channel: 5 ms
  • Per-channel update time: 10 ms
  • Number of channels used: 2 (scanned sequentially in multiplexed architecture)
  • Effective refresh of channel 0: 10 ms
  • Effective refresh of channel 1: 20 ms (multiplexed scan: channel 0, then channel 1)
Even with a 10 ms module update, the visible-to-program latency is OB1 cycle time + 10 ms. If the OB1 cycle is 2 ms, total latency is approximately 12 ms. Reduce the OB1 cycle time, move reads into a fast OB (OB1x priority class 1 to 24), or enable isochronous mode if deterministic sub-millisecond latency is required.

Direct Value Read: IWn:P Syntax

The standard input word IWn is refreshed from the process image at the end of the OB1 cycle (or on each access for S7-1500 with automatic process-image update). To obtain the most recent hardware value immediately - bypassing the process image - Siemens provides the "P" qualifier:

IWn:P

Where:

  • n - input word address (for example, IW 0, IW 2, IW 4)
  • :P - "peripheral access" - direct read from the I/O module, bypassing the I/O process image

Behavior:

  1. The instruction reads the most recently converted value from the module's internal buffer immediately.
  2. It does not refresh the standard IWn in the process image. The peripheral read is a one-shot direct query.
  3. If the same value is required in multiple places, the read result must be stored in a static or temporary variable first - the value is not cached.

Worked example in Structured Text for a function block that needs an immediate sample:

// FB 1 - "FastAnalogRead"
VAR
  aiCurrentValue : INT;    // Static - holds most recent direct read
  aiFilteredValue : REAL;  // Smoothed value used downstream
END_VAR

BEGIN
  // Read the most recent hardware value NOW (bypass process image)
  aiCurrentValue := "DI_AI_HW".%IW0:P;
  // Scale INT 0..27648 to engineering units 0.0..100.0 %
  aiFilteredValue := INT_TO_REAL(aiCurrentValue) / 276.48;
END_FUNCTION_BLOCK

The peripheral read incurs the module's internal conversion cycle, not additional bus time. A peripheral read requested 1 µs after the module's update event returns the new value; a read requested 1 µs before the next update returns the previous one. The user code cannot tell which it received without a timestamp.

FC 2 and FB 1: Reading vs. Using the Value

The original question describes a design where FC 2 collects all current physical I/O states (100 digital inputs, 20 analog inputs) and FB 1 (or other downstream code) consumes those values. Two valid implementation strategies exist, with very different timing characteristics:

Strategy A: Centralized Snapshot in FC 2

FC 2 reads the inputs (optionally using :P peripheral access) and stores them in a global DB. FB 1 reads from the DB. This guarantees consistency - all 20 analog values come from the same instant in process time - but introduces the FC 2 cycle time as additional latency.

// FC 2 - "CollectIO"
VAR_TEMP
  tInfo : SYSTEM_INFO;
END_VAR

VAR_GLOBAL
  gAnalogSnapshot : ARRAY[0..19] OF INT;  // Populated by FC 2
END_VAR

BEGIN
  // Capture 20 analog values from ET 200SP head module 0
  gAnalogSnapshot[0]  := "ET200SP_Head".%IW0:P;
  gAnalogSnapshot[1]  := "ET200SP_Head".%IW2:P;
  gAnalogSnapshot[2]  := "ET200SP_Head".%IW4:P;
  // ... continue for all 20
END_FUNCTION

Strategy B: Direct Read in FB 1

FB 1 reads the analog inputs directly at the point of use with :P access. Values reflect the module's most recent conversion but are not guaranteed to be aligned in time across the 20 channels - each :P read can return a value from a different module scan.

Use Strategy A (centralized FC + global DB snapshot) for closed-loop control, totalizers, and any application where the 20 analog values must represent the same instant in process time. Use Strategy B for monitoring, alarms, and HMI display where occasional skew of one conversion interval is acceptable. For motion or high-speed control, enable isochronous mode and read from the time-stamped process image provided by the isochronous task.

Integration Time and Noise Rejection

The module supports configurable integration times that trade update rate against mains-frequency noise rejection. Typical selections available in TIA Portal under the channel diagnostics view:

Integration Approx. update / channel Rejection target Use case
2.5 ms (400 Hz) ~0.156 ms None / wide bandwidth Fast control loops, isochronous
16.6 ms (60 Hz) ~1.042 ms 60 Hz interference North American mains environments
20 ms (50 Hz) ~1.25 ms 50 Hz interference European / Asian mains environments
100 ms (10 Hz) ~6.25 ms Strong mains + harmonics Heavily disturbed industrial sites

Select the integration time closest to 1/f of the local mains frequency for typical process measurements. Select 2.5 ms only when the application explicitly requires the bandwidth, because noise rejection degrades significantly. For settling-time theory on related DAC architectures (8 µs at 8-bit LSB settling), see the TI precision-DAC reference: Settling time and update rate - TI video and DAC - Understanding Settling Time & Update Rate - TI E2E. The same settling-vs-bandwidth trade-off applies in the input direction: shorter integration lets signal edges through faster but also admits more noise.

Isochronous Mode for Deterministic Latency

The 6ES7134-6HB00-0CA1 supports isochronous (synchronous) mode via PROFINET IRT (Isochronous Real Time). In isochronous mode:

  1. The PROFINET controller sends a synchronization frame at a configured send clock - typically 250 µs to 4 ms.
  2. The ET 200SP interface module distributes the sync to all slots in the station.
  3. The AI module samples its inputs, converts them, and makes them available in a deterministic window - typically 1 to 2 send clocks after the sync edge.
  4. Values are guaranteed to be present in the process image at a precise phase offset from the sync frame, allowing jitter-free coupling to motion or high-speed control loops.

Configuration prerequisites for isochronous mode:

  • ET 200SP PROFINET interface module (IM 155-6 PN) with firmware version supporting IRT - confirm against the IM manual.
  • S7-1500 CPU with firmware that supports isochronous tasks (most current S7-1500 CPUs do, but verify the catalog note).
  • PROFINET topology configured in TIA Portal with a sync domain and a designated sync master.
  • Port assignment: controller and device must share the same sync role configuration (sync master / sync slave).

Within TIA Portal, the path is: Device configuration → ET 200SP station → AI module → Properties → "Isochronous mode" → enable → assign the slot to a PROFINET IO system with isochronous tasks enabled.

For motion applications, the typical isochronous task is set to the servo cycle (1 ms is common) and the AI values appear with a defined Ti (input time) and To (output time) per the PROFINET plan. Field-proven caveat: the bus cycle time in the PROFINET send-clock must be a divisor of the OB1x cycle time, or TIA Portal will issue a topology diagnostic during compile.

Hardware Limit: Multiplexed Architecture

Unlike a SAR ADC with simultaneous sample-and-hold on every channel, the ET 200SP AI module is multiplexed. The analog switch connects channel 0, samples and converts it, then switches to channel 1, samples and converts, then returns to channel 0. With two channels enabled at 10 ms conversion, channel 0 has a true 20 ms effective update rate (not 10 ms), and channel 1 the same. Setting one channel to "disabled" in TIA Portal reduces the per-active-channel update time by half.

For applications requiring simultaneous sampling of all channels, the ET 200SP family provides dedicated modules (such as AI Energy Meter or RTD/TC variants with per-channel track-and-hold). The 6ES7134-6HB00-0CA1 does not have a simultaneous-sample architecture; do not assume channel 0 and channel 1 are time-aligned within one module scan.

Peripheral-Access Code Patterns

The peripheral-access qualifier is universally available in SCL, STL, LAD, and FBD for S7-1500 and S7-1200. Avoid using :P in tight loops because each call initiates a new read on the backplane bus - the I/O module services one request per cycle. For multiple channel reads, prefer the I/O address-offset form:

// Sequential channel read using pointer arithmetic (SCL)
#iValueCh0 := "ET200SP".%IW0:P;
#iValueCh1 := "ET200SP".%IW2:P;
// Both reads complete within one module scan; subsequent reads in
// the same OB cycle return cached values from the bus interface.

For 20 analog channels spread across multiple AI modules, the worst-case latency from a field event to a program-visible value is the sum of:

  1. Module update interval per channel (10 ms default, ~0.156 ms isochronous at 400 Hz)
  2. Bus cycle (PROFINET update time, typically 1 ms)
  3. OB1 cycle or OB1x cycle time

For default 10 ms operation: 10 + 1 + OB1_typical (2 ms) = approximately 13 ms end-to-end latency. For isochronous 250 µs operation: 0.25 + 0.25 + OB1x (0.5 ms) = approximately 1 ms end-to-end latency.

Configuration in TIA Portal

Step-by-step procedure to set update time on the 6ES7134-6HB00-0CA1:

  1. Open the project in TIA Portal (V16 or later recommended for full module support).
  2. Expand the ET 200SP station in the project tree, right-click the AI module, choose "Properties".
  3. Navigate to the "Channel 0" and "Channel 1" tabs. For each, select:
    • Measurement type: Voltage (U) or Current (I)
    • Measuring range: 0..10 V, ±10 V, 0/4..20 mA, etc.
    • Integration time: 2.5 / 16.6 / 20 / 100 ms (per the rejection table above)
  4. Navigate to "Module parameters" and verify the "Diagnostics" settings for wire break and overflow.
  5. If isochronous mode is required: Properties → "Isochronous mode" → enable. Then assign to an isochronous PROFINET IO system.
  6. Compile the project and download hardware configuration to the CPU.
  7. Online → "Monitor all" to view the live IW values and the channel status.
A configuration change of the integration time requires a stop/start of the module (or a full station restart) to take effect. The OB1 cycle in between will continue to read the previous update time, so do not assume a parameter write is live.

Diagnostics and Verification

Verification checklist for the 6ES7134-6HB00-0CA1:

  1. Online diagnostics: TIA Portal → Online → Diagnostics → Module information. The "Module status" should read "OK" and "Channel status" should read "Valid value".
  2. Process image inspection: Add a watch table. Force a known voltage / current on the input terminal. Confirm the IW value updates within one integration interval plus one OB1 cycle.
  3. Quality code (S7-1500): Use "AI_Channel".%IW0 with quality information. The associated ST (S7-1500) or QUALITY tag indicates "Good (non-cascade)" when the value is valid; a value of 0x80 (bad) or 0x40 (uncertain) indicates a channel fault or re-initialization state.
  4. Isochronous diagnostics: If isochronous mode is active, TIA Portal → isochronous tasks panel → "Life sign" must remain at zero. A non-zero life sign indicates the synchronization was lost - the application is still running but values are no longer deterministic.
  5. Cycle time measurement: Insert a timer in OB1 reading the same IW. The minimum observed interval between value changes equals the integration time. If the observed interval exceeds the configured value, check the OB1 cycle time and any "process image update" settings.

Troubleshooting Matrix

Symptom Likely cause Remedy
IW value frozen at 0 or 32767 Channel disabled in HW config; wire break; sensor open Re-enable channel in TIA Portal; check wiring; verify sensor source
IW value changes slower than expected Long integration time selected (e.g. 100 ms); OB1 cycle > update time Reduce integration time; shorten OB1 cycle or move reads to OB1x
IW value noisy / unstable 2.5 ms integration used in 50/60 Hz environment Switch integration to 16.6 ms (60 Hz) or 20 ms (50 Hz)
Isochronous life sign incrementing Sync-master topology change; cable swap; port role mismatch Re-assign sync role in TIA Portal; verify port assignment matches topology editor
FC 2 sees different value than FB 1 reads direct FC 2 captured an older value due to :P behavior or stale data block Use Strategy A consistently; refresh global DB inside FC 2 every cycle
Module not entering data exchange Firmware mismatch between physical module and TIA device version Read module label; match firmware in TIA Portal hardware catalog

Field-Proven Caveats

  • The peripheral-access read IWn:P returns a value cached in the IM (interface module), not a freshly-triggered conversion. Forcing a fresh conversion requires an isochronous sync edge or a separate trigger mechanism.
  • Mixed-vintage ET 200SP stations (older IM, HS AI) limit the minimum send clock. If the IM does not support 250 µs, the AI cannot deliver its fastest update either - the bus, not the module, is the bottleneck.
  • For 100 digital inputs + 20 analog inputs scanned in one OB1 cycle with :P, the OB1 cycle time grows noticeably (the I/O bus serializes the reads). On a 1 ms nominal OB1, plan for 2-3 ms with the :P pattern and 1 ms with the standard process-image pattern.
  • For thermal-RTD or thermocouple measurement, the 6ES7134-6HB00-0CA1 is the wrong module - select the AI 4×RTD/TC or AI Energy Meter variant. The U/I module is specified for voltage and current only.

FAQ

What is the default update time of the 6ES7134-6HB00-0CA1?

10 ms per channel, as confirmed in the module's default TIA Portal configuration. End-to-end program-visible latency is approximately 12-13 ms including the OB1 cycle time. Adjust the integration time in the channel properties to trade update rate against 50/60 Hz noise rejection.

Does IWn:P update the standard IWn process image?

No. The :P qualifier performs a direct peripheral read from the module and returns the value to the calling instruction, but it does not refresh the standard process-image input IWn. Store the result in a static or temporary variable and use the stored value everywhere else in the program.

Can I read 20 analog inputs with a consistent timestamp?

Only if all 20 inputs are read in the same module scan. Use a centralized FC (e.g. FC 2) to read all inputs with :P access into a global DB within a single OB1 cycle, then consume the snapshot from FB 1. Reading the 20 inputs at the point of use in FB 1 does not guarantee a single-instant snapshot because each :P read can return a value from a different module scan.

What is the fastest update rate achievable on this module?

With isochronous mode enabled and the integration time set to 2.5 ms (400 Hz), the module produces new values at the S7-1200 SB reference rate of 0.156 ms per channel. PROFINET IRT and an S7-1500 isochronous task are required to exploit this rate deterministically. End-to-end latency including bus and OB1x cycle is approximately 1 ms. Verify the exact minimum against the module's manual because the figure varies with firmware revision and PROFINET send-clock selection.

How do I avoid the FC 2 collection cycle from masking rapid changes?

Either reduce the OB1 cycle time so FC 2 runs more frequently, move the reads into a fast OB (OB1x priority class 1 to 24) that runs at the desired rate, or enable isochronous mode and assign the AI module to an isochronous task. Avoid mixing 100 digital inputs and 20 analog reads with :P in one OB1 cycle, as the peripheral reads lengthen the cycle and erode the isochronous window.

Back to blog