Configuring PROFINET I/O Data Limits on CPU 1513-1 PN

Overview

The question of "resolution" in a PROFINET context is frequently conflated with the protocol's data transport capacity. PROFINET itself is a deterministic, real-time Ethernet protocol that moves binary process data in defined I/O telegrams; it carries no inherent decimal point and no native engineering unit. The "resolution" of a measured value—the number of significant digits or smallest detectable change—is a property of the field device's transducer, its analog front end, and the data type declared in the device's GSDML. The controller (a Siemens SIMATIC S7-1500 CPU 1513-1 PN in this case) only consumes, scales, and stores the bits the device publishes.

This reference consolidates the limits that govern how much raw data a CPU 1513-1 PN can move on PROFINET, the maximum number of IO Devices and IO Modules it can address, and the engineering path required to bring a high-resolution field instrument—such as a weighing cell transmitter—into a STEP 7 / TIA Portal project without bottlenecking the bus.

The two commonly deployed hardware variants are 6ES7513-1AL02-0AB0 and 6ES7513-1AM03-0AB0, listed in the PROFIBUS & PROFINET Product Finder and the TIA Portal SIMATIC S7-1500 / ET 200MP manual collection respectively. The AM03 revision is the current production variant and the one documented in the Siemens cloud documentation for the ET 200MP / S7-1500 family.

PROFINET Architecture: Telegrams and Data Containers

PROFINET IO follows a producer/consumer model in which the IO Controller (the CPU) cyclically exchanges input and output data with IO Devices. Each IO Device exposes one or more slots, and each slot contains a subslot/module. The aggregated payload of all modules of one IO Device is the device's process data image—the value the controller reads or writes per cycle.

Three real-time classes matter for sizing:

• RT (Real-Time, Class 1)—cyclic data with priorities 0 (high) and 1 (low). Send clocks from 250 µs upward in practice; 1 ms is the practical minimum for most non-motion applications.
• IRT (Isochronous Real-Time)—scheduled with bandwidth reservation, used for motion and isochronous mode where jitter must be below 1 µs.
• NRT (Non-Real-Time)—standard TCP/IP/UDP/IP traffic for acyclic parameterisation, diagnostics, web server, and PROFIenergy.

The PROFINET IO telegram (V2.3+) carries an IO Data Container whose length is signalled in the first two octets. The controller reads this length to decode the slot structure. There is no implicit "resolution" parameter—every bit the device publishes is significant because PROFINET does not perform unit conversion in transit.

CPU 1513-1 PN Hardware Specifications

The CPU 1513-1 PN is part of the SIMATIC S7-1500 standard controller family with a single integrated PROFINET interface (X1 with an internal 2-port switch). Two order numbers are in active deployment:

Both variants ship with the X1 PROFINET interface supporting 100 Mbps full-duplex, MRP (Media Redundancy Protocol) client, and the PROFIenergy profile. Port 1 and Port 2 of the integrated switch are exposed on the front 35 mm shroud with pin assignments per IEC 61918. The newer 6ES7513-1AM03-0AB0 additionally supports the SYNC function for IRT and the S2 redundancy role. The S7-1500 / ET 200MP manual collection specifically documents the AM03 behaviour for "Failure of both redundancy connections and the PROFINET cable in the PROFINET ring" and "Failure of the two PROFINET cables in the PROFINET ring on the backup CPU," confirming the controller's PROFINET ring behaviour.

When used as MRP Manager, the CPU 1513-1 PN closes a ring of up to 50 PROFINET devices. In S2 mode (AM03) the controller and a backup CPU can each observe both ports; under a single-port failure the system continues to deliver process data without reconfiguration, satisfying the PROFINET conformance class CC-B (MRP) and CC-D (S2).

PROFINET Data Limits: Segment, Device, and Slot

The PROFINET IO specification (IEC 61784-2 / IEC 61158) caps the user data per IO Device and per controller. The numbers below are the contractual limits and the working envelope a TIA Portal engineer can rely on when planning a topology:

The 1 440-byte per-device figure is the same in both directions. A typical weighing cell with 2-byte status + 4-byte gross weight + 4-byte tare + 4-byte net weight consumes 14 bytes—less than 1 % of a single device's budget. The CPU 1513-1 PN can therefore host hundreds of high-resolution weighing instruments on one PROFINET line without exhausting the device budget; the wire-level bandwidth and the send-clock setting become the real limiters, not the protocol's count of devices.

PROFINET Topology Reference

Signal Resolution: Where the Limit Lives

PROFINET is bit-exact. The smallest delta a CPU can detect is 1 least-significant bit (LSB) of the data type signalled by the IO Device's GSDML. The choice of data type and the engineering range of the device jointly set the resolution visible to the application:

For a weighing cell transmitter, the published "resolution" is usually given in display counts (e.g., 100 000 d for a 50 kg cell = 0.0005 kg/d). To get the wire-side resolution right, specify a transmitter that publishes its primary value as a 32-bit signed integer (DINT) or 32-bit float (REAL) at the full 100 000-d count. TIA Portal will then place the value into a tag of the corresponding type, and no further bit-level math is required to read individual counts.

Resolution Math: From Counts to Engineering Units

The wire-level step (1 LSB) becomes a physical step through the device's published scale factor. Use:

For a 32-bit signed value (N = 31 significant bits, codomain size = 2³¹) scaled to 0–50 000 kg:

This is the smallest deterministic step the controller can register. Mechanical noise, thermal drift, and ADC quantisation in the transmitter typically dominate; the bus is rarely the limiting factor for weighing applications. For perspective, a 24-bit ADC (common in weighing transmitters) yields 16 777 216 codes, which over a 50 000 kg range equates to ≈ 0.003 kg/LSB at the ADC. The PROFINET wrapper adds no further quantisation if the transmitter publishes the full 24-bit count in a 32-bit slot.

Engineering Workflow in TIA Portal

After installing the device's GSDML (TIA Portal V18 / V19 / V20) the slot structure is fixed. To verify the data path and the resolution budget:

1. Open the device's Properties → Device view; confirm the slots list matches the GSD.
2. Open Properties → IO tags; map each slot to a tag name and PLC data type (BYTE, INT, DINT, REAL, etc.).
3. Open Properties → PROFINET interface → Real-time settings; set the send clock (1 ms for 1 kHz update, 4 ms typical for weighing).
4. Open Properties → Module parameters; on a weighing transmitter, set the integer scale, units (kg, g, t), and the status-word bits to match the device's manual.
5. Compile the hardware configuration and download. In the online view, force the IO tags to verify wire-level data integrity.
6. Optionally assign the IO Device's PROFINET name and IP from TIA Portal's "Assign PROFINET device name" wizard.

Sample SCL snippet for scaling a 32-bit signed integer to engineering units when the device sends a raw count in the %IW area:

// Raw DINT from PROFINET input area
// "iwWeightRaw" is mapped from slot 1, subslot 1
#rGross_kg := DWORD_TO_REAL(UDINT#0)
             + DWORD_TO_REAL("iwWeightRaw")
               * (50 000.0 / 2 147 483 647.0); // unsigned map
#bValid := "iwWeightRaw".%X15;                // bit 15 = status valid

For a REAL type (32-bit float), no scaling is required in the PLC; the engineering value arrives in the tag as written by the device.

Practical Example: Weight Cell Integration

A 50 t load cell cluster with 100 000 d display resolution and a PROFINET transmitter (e.g., a Siemens SIWAREX WP241 / WP251 or a HBM FIT / AED class device) is integrated as follows:

• Slot 0: device head module (empty data)
• Slot 1: 4 bytes input — gross weight (DINT, 0.5 kg/LSB typical)
• Slot 2: 4 bytes input — net weight (DINT)
• Slot 3: 2 bytes input — status word (UINT)
• Slot 4: 2 bytes input/output — control word / commands (UINT)

Total IO footprint: 12 bytes input + 2 bytes output per device. The bus cycle at 4 ms send-clock consumes ~28 µs of line time per device, leaving ample headroom for 30+ load cells on a single PROFINET line of the CPU 1513-1 PN. Even with 128 devices of the same type populated, the total is 1 536 bytes input + 256 bytes output — well within the 8 192-byte per-segment budget and inside the 1 440-byte per-device limit per slot aggregate.

Cycle-Time Budget

Use the following dimensional check before commissioning:

With N_devices = 30 at T_device_update = 100 µs, a fast IRT-capable switch, and 200 µs of guard band, T_total ≈ 3.2 ms, comfortably under a 4 ms send clock. The same formula with 128 devices at 100 µs gives ≈ 13 ms, which mandates a 16 ms send clock to stay below the watchdog. This is the typical engineering trade-off: device count vs. update rate.

PROFINET Conformance Classes and Their Impact

The CPU 1513-1 PN supports the following PROFINET conformance classes (per IEC 61784-2):

• CC-A — RT, basic diagnostics, non-realtime mixed. Default for the AM03.
• CC-B — adds MRP redundancy, device-level diagnostics, and SNMP. Required for ring topologies.
• CC-C — adds IRT bandwidth reservation. Required for motion and isochronous applications.
• CC-D — adds S2 system redundancy. Only the 6ES7513-1AM03-0AB0 supports this; the 6ES7513-1AL02-0AB0 does not.

For weighing and other non-motion applications, CC-B with a 4–8 ms send clock is usually sufficient. The send clock is a global parameter on the controller's PROFINET interface and applies to all ARs (Application Relationships) on the segment.

Cable and Topology Constraints

Although this is not strictly a PROFINET protocol limit, the physical layer sets the upper bound on device count and segment length. For copper PROFINET (100BASE-TX, Cat 5e or better):

For installations exceeding 100 m between devices, use PROFINET over fibre (100BASE-FX) with SC or LC connectors via a media converter or a PROFINET switch with integrated fibre uplinks. The CPU 1513-1 PN does not have native fibre ports; an external switch is required.

Verification and Diagnostics

After download, run the following checks before handing the system over to operations:

1. Online → Diagnostics → PROFINET diagnostics: confirm the device state is green; no submodule diagnostics pending.
2. Watch table: monitor the raw IO tags, apply a known load to the cell, and verify the LSB-to-kg conversion matches the device's published spec.
3. Trace: record the input image over 10 s and verify the cyclic update; check for any glitches or hold-last-value events.
4. Web server of the CPU ("http://<CPU-IP>/") → "Diagnostics" tab to inspect port counters, discard rate, jitter, and active ARs.
5. PG / PC Ethernet statistics: confirm zero CRC errors, zero late collisions, and zero symbol errors on the PROFINET port.
6. PROFINET name and IP audit: each device's PROFINET name must match the project; mismatches are the single most common commissioning fault.

Troubleshooting Matrix

Glossary of Key Terms

• AR (Application Relationship)—the cyclic data channel established between the controller and a device; consumes one of the controller's AR slots.
• CR (Communication Relationship)—a record-level channel within an AR, used for acyclic read/write of parameters and diagnostics.
• GSDML—XML device description file (General Station Description, Markup Language) that defines the slot structure, parameters, and diagnostics of a PROFINET device.
• Send clock—fundamental cycle time of the PROFINET IRT/RT schedule, set on the controller and shared by all ARs.
• Watchdog—time within which the controller must refresh a device's output data; if missed, the device enters fail-safe state.
• Submodule—synonym for a slot-level module that publishes a defined IO length.

FAQ