Siemens MP377 Profibus Video Streaming: Limits and Alternatives

Overview

Engineers occasionally need to bring a live camera feed to a Siemens Mobile Panel 377 (MP377) HMI in a Profibus-only plant. The naive approach - a Profibus-DP slave 'video camera' GSD - collides with three hard limits: the 244-byte slot size, the deterministic cycle time required for DP, and the absence of an efficient on-board video codec. This reference compiles the Profibus-DP throughput math, the GSD parameter requirements, the runtime video capabilities of the MP377, and the field-proven alternative architectures (Ethernet + thin client, ActiveX with VBScript control, and Sm@rtClient remote display).

This article is written for system integrators specifying mobile panels, plant engineers troubleshooting an existing Profibus video link, and control engineers migrating from fieldbus to Industrial Ethernet for vision applications.

MP377 Hardware and Runtime Capabilities

The MP377 family (Mobile Panel 377) was released by Siemens as the successor to the MP370, with 12-inch and 15-inch TFT touch variants and optional key/membrane fronts. For video integration, the relevant interfaces and runtime characteristics are:

The MP377 Ethernet port is the channel most engineers ultimately use for video. It is connected to the engineering network or, when plant segmentation demands, to a dedicated IP-camera VLAN with a static route back to the controlling PLC.

Profibus DP Throughput and Slot Constraints

Profibus DP-V0/-V1/-V2 all share a hard architectural constraint: each cyclic data exchange (one 'slot') per slave is limited to 244 bytes of input + 244 bytes of output. This is encoded in the protocol, not a configured parameter.

These figures ignore bus master turnaround, gap times (Tid1, Tid2), min slave interval (Tmsi), and watchdog slots. A realistic minimum cycle for a single-slave bus is therefore:

Tcyc_min ≈ Tsdr_max + Tslot_data + Tid1 + Tid2 + Tmsi
where:
  Tsdr_max   = max slave response time (depends on baud, see GSD 'max Tsdr')
  Tslot_data = 244 * 11 bits / baud_rate  (11 bits/byte for UART framing)
  Tid1       = 75 Tbit idle
  Tid2       = 30 Tbit idle
  Tmsi       = typically 1 ms (configurable 1-65000)

For a 12 Mbps link with a 244-byte slot and 1 ms Tmsi, Tcyc_min works out to roughly 0.6-1.5 ms depending on the slave's configured Tsdr. The result is the upper bound for the maximum sustained video throughput through that slot.

What this means for video

A 244-byte payload delivered every 1 ms is 244 kB/s ≈ 1.95 Mbps. That is just enough room for a low-resolution, low-frame-rate compressed stream - provided the encoder fits inside the 244-byte chunk size plus a thin transport header. CIF (352 x 288) at 4-8 fps in H.264 baseline or MJPEG typically needs 300-800 kbps at acceptable quality. So in theory Profibus DP at 12 Mbps with a 1 ms cycle can carry a CIF stream; in practice it cannot, because the MP377 has no H.264 decoder, no buffering model, and no Profibus driver that emulates a streaming socket.

Video Bandwidth vs. Profibus Capacity

Before specifying a Profibus video path, calculate the bandwidth the application actually requires. The rules of thumb in the table below are starting points; production sizes depend on scene complexity, motion content, and encoder tuning.

The Profibus video feasibility check is therefore:

Video_bitrate_kbps < (Slot_bytes * 8 / Tcyc_ms) * 1000
                       = (244 * 8 / Tcyc_ms) * 1000
                       = 1,952,000 / Tcyc_ms

Examples:
  Tcyc = 1.0 ms  -> max 1952 kbps
  Tcyc = 2.0 ms  -> max  976 kbps
  Tcyc = 5.0 ms  -> max  390 kbps
  Tcyc = 10.0 ms -> max  195 kbps

Even with the most optimistic 1 ms cycle, you are at the absolute lower edge of usable compressed video. Below 5 ms cycle, the stream becomes unrecognizable.

GSD File Parameter Configuration

A Profibus 'video camera' GSD must declare DP-V1 (or DP-V2 if isochronous mode is desired), and the slot configuration parameters have to be tuned for the tightest cycle the camera encoder can sustain. The key GSD keywords are:

Example GSD excerpt for a hypothetical 244-byte video slave:

; Profibus GSD - DP-V1 video slave, 244-byte I/O
GSD_Revision = 5
Vendor_Name  = 'Acme Vision'
Model_Name   = 'AV-Cam-DP244'
Revision     = '1.0'
Ident_Number = 0x0AC1

; Slot 1: 244 bytes input, 32 bytes output
Module = 'Video Frame 244B In / 32B Out' 0x10,0x21
EndModule

MaxTsdr_9.6    = 60
MaxTsdr_19.2   = 60
MaxTsdr_45.45  = 60
MaxTsdr_93.75  = 60
MaxTsdr_187.5  = 60
MaxTsdr_500    = 100
MaxTsdr_1.5M   = 150
MaxTsdr_3M     = 250
MaxTsdr_6M     = 450
MaxTsdr_12M    = 800

Min_Slave_Interval = 1
Fail_Safe = 1
Diagnostic_alarm = 1
User_Prm_Data_Len = 4
User_Prm_Data = 0x00,0x00,0x00,0x00  ; default: 320x240 MJPEG

; Extended diagnostics for codec / link errors
Diagnostic_User = 0xA0,0xA1,0xA2,0xA3

On the MP377 side, the camera appears as a DP slave under the connected Profibus master (or as a direct DP master, depending on variant). The 244-byte input area is read into a process tag; the 32-byte output is written to start/stop streaming or trigger snapshots.

Response Time Calculation and Frame Fragmentation

The minimum response time of the camera Profibus slave determines whether the stream is decodable. The simplified single-slave calculation is:

Tcyc = Tsdr + T_tx + Tid1 + Tid2 + Tmsi

T_tx   = N_bits / baud_rate
N_bits = N_bytes * 11            ; 1 start + 8 data + 1 parity + 1 stop
Tsdr   = max slave response delay (from GSD MaxTsdr_b baud)
Tid1   = 75 * Tbit
Tid2   = 30 * Tbit
Tmsi   = min slave interval (GSD, ms)

Example for 12 Mbps, 244-byte payload:
  T_tx    = 244 * 11 / 12e6 = 223.7 µs
  Tsdr    = 800 * Tbit = 66.7 µs (MaxTsdr_12M = 800 Tbit)
  Tid1    = 75 * 83.3 ns = 6.25 µs
  Tid2    = 30 * 83.3 ns = 2.50 µs
  Tmsi    = 1,000 µs
  Tcyc    ≈ 1300 µs (1.3 ms)

With one camera slave and one master, the steady-state cycle is ~1.3 ms. Adding additional DP slaves or a longer Tid pushes the cycle above 2 ms. Once Tcyc exceeds 5 ms, the perceived 'live' quality of a Profibus video stream degrades to slideshow territory.

Frame fragmentation and re-assembly pattern

Because Profibus DP delivers fixed 244-byte chunks but video frames are variable in size, the application must implement a simple fragmentation layer. The standard pattern:

+---------+------------+--------+---------+----------+
|  Byte 0 |  Bytes 1-2 | Byte 3 | Byte 4  | Bytes 5+ |
|  SOF    |  SeqNum    | Type   | Length  | Payload  |
+---------+------------+--------+---------+----------+
SOF    = 0xAA start-of-frame, 0x55 continuation, 0x5A end-of-frame
SeqNum = 16-bit cycle sequence number (wrap-around ok)
Type   = 0x01 MJPEG, 0x02 H.264, 0x03 raw
Length = total bytes in complete frame (big endian)
Payload = up to 239 bytes per cycle

The MP377 VBScript (or the C/C++ runtime behind the ActiveX) reassembles frames by buffering until it sees SOF followed by enough continuation packets and the matching EOF. Re-assembly latency on a 1.3 ms cycle and a 30 kB JPEG frame is approximately:

Packets needed = ceil(30000 / 239) = 126
Total time    = 126 * 1.3 ms = ~ 164 ms

This 164 ms re-assembly delay is in addition to the encoder pipeline latency (~100-300 ms) and the rendering latency on the panel (~50-100 ms). End-to-end 'live' latency is therefore 0.3-0.6 s - acceptable for supervisory use, not for closed-loop control.

Application Strategies and Trade-offs

Given the protocol limits, a Profibus-DP video path must be sized as a strictly supervisory feature, not a closed-loop vision path. The table below compares the practical options:

The Ethernet column dominates the comparison on throughput. The Profibus column only wins in plants where the wiring contract explicitly forbids running Ethernet to field devices, or where the MP377 variant does not have an Ethernet port (rare for the 377 family but possible on some key-only variants).

Recommended Architecture: Ethernet + Thin Client

The field-proven approach is to keep Profibus strictly for control I/O between the S7 PLC and the MP377, and to deploy the camera on a parallel Ethernet segment accessed by the MP377's LAN port. The architecture is:

The PLC remains the Profibus master; the camera and the MP377 both live on a managed Ethernet switch on a dedicated VLAN. Camera control bits (PTZ, snapshot) can still be exchanged between MP377 and the PLC via Profibus tags, but the bulk of the pixel data never touches the fieldbus.

Implementation steps

1. Configure the IP camera with a static address on the camera VLAN (e.g., 192.168.100.50/24).
2. Tag the VLAN on the switch port connected to the MP377.
3. On the MP377, set the LAN adapter to a static address in the same subnet.
4. Deploy an ActiveX video object on the desired screen in WinCC flexible (or TIA Portal).
5. From VBScript, call the ActiveX Play(URL) method with the camera's RTSP or HTTP-MJPEG URL.
6. Route PTZ commands from MP377 keys through Profibus tags to the PLC, then out the PLC's Ethernet port to the camera (or directly from the MP377 Ethernet if policy allows).

ActiveX Player and Profibus Address Mapping

The MP377 runtime hosts ActiveX controls, which is the standard mechanism for video playback. A minimal working pattern in WinCC flexible uses the Microsoft Media Player ActiveX (MSVidCtl) or VLC's ActiveX wrapper. For a vendor-agnostic path, embed a WebBrowser control and load the camera's web UI; this works even on Windows CE 6.0 because the underlying Internet Explorer component renders MJPEG streams via the camera vendor's plugin.

VBScript snippet - start / stop streaming

' On a button press, start streaming from the IP camera
Sub StartStream()
    Dim url
    url = 'rtsp://192.168.100.50:554/stream1'
    ' Or MJPEG over HTTP:
    ' url = 'http://192.168.100.50/mjpg/video.mjpg'

    HMIRuntime.Tags('Camera.URL').Write url
    HMIRuntime.Tags('Camera.Run').Write 1

    ' Trigger the ActiveX to (re)load the URL
    ScreenItems('VideoOCX').URL = url
    ScreenItems('VideoOCX').control.Play
End Sub

Sub StopStream()
    HMIRuntime.Tags('Camera.Run').Write 0
    ScreenItems('VideoOCX').control.Stop
End Sub

Mapping Profibus address to media control

The engineering question of 'how do I associate the Profibus address to media control' resolves to the following pattern:

1. Expose the camera's Profibus slave as a DP device in the PLC hardware configuration (HW Config in Step 7, or device configuration in TIA Portal).
2. Map the 244-byte input area into a PLC DB, e.g., DB200.DBX0.0 length 244.
3. Mirror only the relevant control bytes (status, frame counter, codec ID) into a smaller DB - for example DB200.DBW0 (status word) and DB200.DBD2 (frame counter).
4. On the MP377, create tags that point to those mirrored DB words via the standard Profibus/PN connection to the PLC.
5. Drive the ActiveX's VBScript interface from those tags; do not attempt to render the 244-byte raw stream on the MP377 because there is no decoder for the chosen codec.

The Profibus address thus acts purely as a control/status channel. The actual video data rides on Ethernet. This is the only sane engineering solution for the MP377 platform.

Step 7 and TIA Portal Configuration Procedure

Regardless of whether the MP377 is a DP master or DP slave, the camera DP slave must be added to the master's hardware configuration. The detailed path is:

In SIMATIC Manager (Step 7 V5.5 or earlier)

1. Open HW Config for the PLC station.
2. Right-click the Profibus subnet and choose 'Insert Object > DP Slave'.
3. Browse to the GSD file (Options > Install GSD) and select the camera from the catalog.
4. Drop the camera on the subnet and assign a unique Profibus address (e.g., 7).
5. Open the slot configuration; assign the 244-byte input module to slot 1 and the 32-byte output module to slot 2.
6. Double-click the camera, open 'Parameter Assignment', and set User_Prm_Data to the desired codec/resolution combination (e.g., 0x01 0x01 0x00 0x00 for 320 x 240 H.264 baseline).
7. Save, compile, and download the HW Config to the PLC.
8. Add the input bytes to a process image or a DB - typically DB200, length 244 - so the MP377 connection can read them.

In TIA Portal (V13 or later)

1. Open the project and the PLC's 'Devices & Networks' view.
2. Install the GSD via Options > Manage general station description files (GSD).
3. Drag the camera from the hardware catalog onto the Profibus subnet.
4. Assign the Profibus address and configure slot mapping as above.
5. Open the camera properties, navigate to 'Module parameters', and verify the input/output byte mapping.
6. Compile and download.
7. In the MP377 HMI tags, point the camera status word to DB200.DBW0 (status) and DB200.DBD2 (frame counter).

After download, place the PLC in RUN and use the online diagnostics view to confirm the camera DP slave transitions to 'OK' within one or two watchdog periods. The MP377 tags should reflect valid status bits within one cycle.

Performance Benchmark - Sample Numbers

These are typical numbers from a lab setup with a 244-byte DP video slave running at 12 Mbps on a dedicated segment with one camera and one MP377, no other DP slaves:

The QVGA / CIF sweet spot is the realistic envelope for Profibus video. Anything larger should be moved to Ethernet.

Commissioning, Verification, and Troubleshooting

Use this sequence to validate a Profibus-control-plus-Ethernet-video integration on a live plant:

1. Confirm GSD import: open HW Config, install the camera GSD, drag the device into the Profibus line, save and compile.
2. Verify DP diagnostics: in Step 7 / TIA Portal online diagnostics, confirm 'Slave OK' and no diagnostic interrupts before touching the camera.
3. Check Tcyc with a Profibus monitor (e.g., Softing Profibus Tester, Procentec ProfiHub diagnostic): Tcyc must be < 5 ms for video feasibility.
4. Confirm tag mapping: the MP377 connection to the PLC must include the DB word carrying the camera status; verify with a temporary text field showing the live value.
5. Verify Ethernet path: from the MP377, ping the camera address; latency should be < 5 ms on a managed VLAN.
6. Open the ActiveX test screen and confirm the stream loads within 2-3 s (typical for VLC / MS Media Player cold start).
7. Force a Profibus fault by unplugging the slave; the MP377 should display the 'Camera offline' placeholder within one watchdog period.
8. Capture a 30-second sample of the displayed video and inspect for dropped frames, jitter, or color shifts indicative of buffer underrun.

Troubleshooting matrix

Migration to KTP Mobile and Field Optimization

The MP377 has been superseded by the SIMATIC HMI KTP Mobile (KTP400F Mobile, KTP700F Mobile, KTP900F Mobile). For greenfield projects, prefer the KTP Mobile because it adds:

• ProfiNet as the primary fieldbus (Profibus remains an option on some models via gateway).
• Higher-resolution displays up to 9" with 1280 x 800 pixels.
• Hardware-assisted video decoding on the WEC2013 / WES7E images.
• Native HTML5 rendering of camera web UIs, eliminating the ActiveX layer for many vendors.
• OPC UA server interface for direct camera-PLC handshake.

Migration is straightforward: export the WinCC flexible project, import it into TIA Portal V15.1 or later using the 'Migrate project' wizard, then re-target the panel to the KTP Mobile variant. Camera tags and Profibus/PN addresses are preserved. If you are tied to the MP377 platform for spare-part or certification reasons, the engineering content in this article applies unchanged; only the runtime firmware updates may differ.

Practical optimization tips for Profibus-bound plants

1. Set the camera to constant-CFR mode with a fixed GOP of one I-frame every 30 P-frames. This trades seek responsiveness for steady-state bandwidth.
2. Disable audio on the Profibus stream. Audio doubles the required bandwidth and is rarely useful for supervisory video.
3. Use quarter-CIF (176 x 144) at 4 fps as the floor. At this resolution, H.264 baseline needs roughly 80-150 kbps, well within the 1.95 Mbps ceiling.
4. Tune MaxTsdr_12M to the lowest value supported by the encoder. Each Tbit saved in Tsdr translates directly to shorter cycles.
5. Reserve one slot for 'control' and a separate slot for 'data' if your GSD allows multi-slot slaves. This isolates the start/stop/snapshot byte stream from the high-bandwidth payload.
6. Enable DP-V1 read/write acyclic services for parameter changes (e.g., resolution switching on the fly). Acyclic traffic does not consume cyclic slot bandwidth.
7. Place the camera slave as the only device on a dedicated DP segment. Multi-slave segments steal bandwidth from your video slot.
8. Disable PLC-side diagnostics on the camera slot if the diagnostic alarm fires too frequently; the resulting slot retries add latency.
9. Buffer at least two full frames in the MP377 application before displaying. This masks individual missed cycles.
10. Profile with a Profibus analyzer (Procentec ProfiHub, Softing BC-700-PB) before declaring the system acceptable. Visual inspection of jitter histograms reveals problems a 'looks fine' check misses.

Compliance check against Profibus standards

Verify the timing parameters used in this article against IEC 61158 (Application layer services) and IEC 61784-1 (Profile set CPF 3 / Profibus). The Profibus user organization (PI - Profibus & Profinet International) maintains the formal GSD specification and the DP timing definitions. When in doubt, run your bus through a certified Profibus conformance checker before accepting the video path on a production line.

Frequently Asked Questions