Configuring Modbus RTU/ASCII on Siemens SICAM P50 via RS485

Overview: Communication Options on the Siemens SICAM P50/55

The Siemens SICAM P50 (formerly branded SIMEAS P50, device family 7KG77) is a panel-mount power and energy meter intended for substations, feeder monitoring, and power-quality trending at the LV/MV boundary. It exposes four on-board serial protocols selectable from its front-panel or configuration tool:

• Modbus RTU – binary, 8-bit, CRC-16, master/slave.
• Modbus ASCII – 7-bit printable, LRC-8, master/slave.
• IEC 60870-5-103 – protection-equipment companion standard, used in substation automation.
• Siemens Serial ASCII – proprietary, documented only inside legacy SIMATIC CP441 manuals (entry ID 1137419), intended primarily for SIMATIC S7-300/400 backplanes and not freely redistributable.

For any non-SIMATIC host — including LabVIEW, Python, .NET, or third-party RTUs — the practical candidates collapse to the two Modbus variants. IEC 60870-5-103 has very limited process-data support on the P50 and was designed for protection IED interchange, not general SCADA polling.

Protocol Decision Matrix: RTU vs ASCII vs IEC 60870-5-103 vs Siemens ASCII

Recommended Choice: Modbus RTU over RS485

For a LabVIEW 8.6 host that polls the SICAM P50 once per second, Modbus RTU is the correct selection. The justification is:

1. Public, free documentation. Siemens publishes the full register map, function-code support, and exception responses in the manual at SICAM P50/55 – 7KG77 Communication Protocol Modbus Manual (entry ID 109752374). No NDA, no SIMATIC dependency.
2. Compact binary framing. At 9600 bit/s, an 8-word input register read (Function Code 04) is ~25 ms end-to-end, leaving a 975 ms idle window in a 1 Hz poll — even with 8-E-1 parity, an inter-frame gap, and a half-duplex RS485 turnaround.
3. LabVIEW ecosystem. NI ships the Modbus Library for LabVIEW (2013 and later; installable into 8.6 via the ni-modbus.llb drop-in). It exposes MB Master Query and MB Master Response Parse VIs that wrap the CRC-16 directly, eliminating the most common LabVIEW ↔ Modbus implementation bug.
4. ASCII is not faster for your use case. ASCII doubles the on-wire byte count for every register. The extra ~13 ms per transaction is irrelevant at 1 Hz, but ASCII also halves the parity coverage and forces a 7-bit data path that complicates serial-port configuration in LabVIEW on Windows COM ports. There is no engineering reason to prefer it.
5. IEC 60870-5-103 is the wrong tool. On the P50, IEC 60870-5-103 is intended for protection-IED interoperability and reports only a small subset of measurements in standard information numbers. The full instantaneous-value table is reachable only through Modbus.

RS485 Physical Layer and P50 Port Pinout

The SICAM P50/55 exposes one serial port on the rear terminal block, configurable in firmware as RS485 (2-wire half-duplex) or RS232. For multi-drop or for any cable longer than 3 m, use RS485.

Recommended RS485 bus configuration for a single-P50 link to a LabVIEW PC:

• Topology: point-to-point daisy-chain, no stubs > 0.3 m.
• Termination: 120 Ω at each end of the bus, switched on only if the bus length exceeds ~10 m at 19200 bit/s or ~3 m at 115200 bit/s.
• Bias: 680 Ω pull-up to +5 V on A, 680 Ω pull-down to GND on B — required on the P50 side because the meter does not fail-safe bias internally on all firmware revisions.
• Converter: isolated USB-to-RS485 (e.g., NI USB-485, FTDI USB-RS485-WE-1800-BT) — isolation protects the meter ground from PC ground loops, which are the single most common cause of intermittent Modbus timeouts.
• Shield: grounded at the PC end only; leave the P50 shield terminal floating to break ground loops.

Modbus Configuration Parameters on the P50

Set the following parameters via the front keypad (MENU → COMM) or the SICAM Pxxx Parameter tool before polling. The values below are the recommended defaults for a 1 Hz LabVIEW host:

SICAM P50 Modbus Register Map (Selected)

The complete map is in the manual at entry 109752374. The most-requested values for a 1 Hz dashboard are listed below. All values are 16-bit Modbus registers; multi-word values are big-endian (high word first).

Read every quantity you need in a single Function Code 04 request rather than chaining single-register reads. A request for 16 input registers starting at 0x0000 returns all voltages and currents in one frame:

// Function Code 04 — Read Input Registers
// Address range: 0x0000 to 0x000F (16 registers)
// RTU frame (hex), Unit ID = 1:
01 04 00 00 00 10 F1 C0
// Bytes:  [UnitID] [FC] [StartHi] [StartLo] [QtyHi] [QtyLo] [CRClo] [CRChi]

CRC-16 / Modbus Verification

The RTU integrity check is CRC-16 with polynomial 0xA001 (reflected 0x8005), initial value 0xFFFF. LabVIEW 8.6 has no built-in Modbus CRC VI, so implement it once as a sub-VI. The following pseudocode is bit-for-bit equivalent to the reference implementation in the manual:

function ModbusCRC16(byte[] buf, int len) -> uint16:
    crc = 0xFFFF
    for i = 0 to len-1:
        crc = crc XOR buf[i]
        for j = 0 to 7:
            if (crc AND 0x0001) != 0:
                crc = (crc >> 1) XOR 0xA001
            else:
                crc = crc >> 1
    // Return low byte first, then high byte on the wire
    return crc

Verification example: frame 01 04 00 00 00 10 must transmit with CRC bytes F1 C0 (low byte first). If LabVIEW produces anything else, check the byte order of the CRC register write — most off-by-one bugs live there.

LabVIEW 8.6 Implementation Skeleton

1. Open the serial port. Use VISA Open with the COM resource of your USB-RS485 converter. Set baud rate = 9600, data bits = 8, parity = 0 (None), stop bits = 10 (i.e., 1 stop bit — the VISA cluster is in 0.1-stop-bit units), flow control = 0 (None), and termination char = 0x00 (do not auto-terminate; you need the silent gap to mark frame end in RTU).
2. Build the request. Append the two CRC bytes from the sub-VI above to 01 04 00 00 00 10 and write with VISA Write.
3. Read the response. Use VISA Read with a count of 37 (1 UnitID + 1 FC + 1 byte-count + 32 data + 2 CRC = 37). A timeout of 1000 ms is appropriate for 9600 bit/s.
4. Validate the CRC. Run the response through the same CRC sub-VI; the result over the bytes preceding the CRC field must be 0x0000.
5. Unpack registers. Swap the byte order of each 16-bit word to little-endian (the wire is big-endian) and apply the scale factor from the register table.
6. Throttle to 1 Hz. Use a Wait (ms) of 1000 in a While Loop. Do not rely on VISA timing alone — the P50 will hold the bus for ~25 ms per transaction, but the inter-frame gap and Windows scheduler jitter can otherwise pile up.
7. Exception handling. If the response FC has bit 7 set (e.g., 0x84), look up the exception code:\li>

Verification Procedure

1. Loopback test the cable. With the P50 disconnected, short A to B at the meter end. Every byte you write must come back. Confirms polarity, termination, and converter direction control.
2. Single-register read. Issue Function Code 04, start 0x0000, quantity 1. Expected frame: 01 04 02 HH LL CRC CRC. If you receive silence, the unit ID is wrong (try scanning 1–247) or the termination character on VISA is eating the first byte (set it to 0x00 or disable).
3. Validate scale. Compare the L1-N voltage reading against a handheld DMM at the same terminals. The Modbus value should be 10× the DMM reading (scale 0.1 V).
4. Burn-in test. Run the 1 Hz poll loop for at least 1 hour and log exception count and CRC error count. < 0.1 % exception rate is normal on RS485; higher rates point to a grounding or bias issue.
5. Three-phase sanity check. Compute apparent power S = √3 · V_LL · I from the read values and compare to the meter's own S register. Discrepancies > 2 % usually indicate a CT/PT wiring polarity reversal on one phase, not a Modbus problem.

Troubleshooting Matrix

Field Notes and Best Practices

• Document the parameter set. Photograph the front panel after every COMM change. P50 firmware revisions have shipped with different default baud rates across the 7KG77 family.
• Use a dedicated USB port. USB hubs and docking stations introduce additional latency. Plug the RS485 converter directly into the PC.
• Avoid mixing protocols on the same bus. The P50 will not negotiate; if another device on the same RS485 pair uses a different protocol or baud rate, every device will fail.
• Keep frame sizes small. Even though the P50 supports a full 125-register FC 04 read, splitting the dashboard into two or three 16-register reads is more robust against single-bit errors and easier to re-parse in LabVIEW.
• Plan for Modbus ASCII as a fallback. If you ever need to read the meter through a terminal emulator or a 7-bit serial path (e.g., some radio modems), ASCII works identically except for the LRC-8 checksum and the : / CR LF framing.
• Record firmware version. Certain register ranges — particularly the energy counters — are firmware-dependent. Note the version printed on the meter label and reference the matching revision of the manual at 109752374.