How-to
Connecting an HMI panel to an S7-300 MPI port with a PG
Short answer
Yes: wire the panel's RS-485 port to the CPU's MPI/DP port and run the Siemens S7 MPI driver, with no communication module. Put a PROFIBUS connector with a PG socket on that port, hang the PC adapter on the socket, give every node a unique address and one common baud rate, and STEP 7 stays online while the panel runs.
On this page
Yes, without buying a communication module. The 6ES7 315-2AG10-0AB0 (CPU 315-2 DP) exposes an MPI/DP interface that runs MPI by default, and a Weintek MT6100i panel reaches it straight from its RS-485 serial port using the Siemens S7 MPI driver. STEP 7 stays online at the same time when the panel lands on a PROFIBUS bus connector with a PG socket and the PC adapter sits in that socket. What makes or breaks the combination is three numbers, not hardware: one unique address per node, one baud rate for every node, and a highest-station setting that covers them all.
Use the MPI/DP port, not the DP port #
The CPU 315-2 DP carries two bus interfaces on its front, both 9-pin D-sub and easy to confuse. The MPI/DP port ships in MPI mode and is the intended connection point for panels and programming devices. The DP port beside it is a dedicated PROFIBUS DP master interface for remote I/O, and an MPI-protocol panel does not run there.
| Port | Default role | Use it for the panel? |
|---|---|---|
| MPI/DP | MPI: PG, panel, other S7 stations | Yes — this is the intended connection |
| DP | PROFIBUS DP master toward remote I/O | No — leave it for the fieldbus |
The decision: the panel goes on the MPI/DP port in MPI mode, even on a training CPU whose DP port sits empty. On the current controller generation the same job is done over Ethernet, covered in Connecting an HMI Panel to an S7-1500 PLC.
Why no module is needed #
MPI rides on an RS-485 physical layer (TIA/EIA-485), the same differential pair PROFIBUS uses. That standard wants a multidrop trunk, never a star; one twisted pair plus reference ground with A and B consistent end to end; and termination at the two physical ends only. The CPU already holds the MPI controller, and the MT6100i has an RS-485 port with a Siemens S7 MPI driver option in its project configuration, so the electrical layer and the protocol layer are both covered before you buy anything.
Only cable and settings remain. The panel side lands on terminals rather than a D-sub, so wire it from the connection diagram published for that panel family over S7 MPI instead of assuming a straight DB9-to-DB9 mapping. Because the bus is multidrop, a second panel later is one more drop on the same trunk, not a second port; the trunk discipline is the one in How to Share One RS-485 PLC Port Between Multiple HMIs.
Wire the panel and the PC onto one segment #
- Read the CPU's stored MPI parameters before touching hardware (HW Config, CPU properties, MPI interface). A used CPU keeps whatever the last project stored; the factory values are address 2, 187.5 kbit/s and highest MPI address 31, but the stored values are what the port runs.
- Fit a PROFIBUS bus connector with a PG socket to the CPU's MPI/DP port, the 9-pin D-sub type documented with and without the socket.
- Land the panel cable in that connector's cable entry. On the CPU-side D-sub, pin 3 is line B and pin 8 is line A; the panel-side terminals follow the panel's connection diagram.
- Set the connector's terminating-resistor switch to ON only if the CPU is a physical end of the segment. Terminate the two ends, never a middle connector.
- Plug the PC's MPI/PROFIBUS adapter (a CP5711 is one) into the PG socket.
- In STEP 7, open Set PG/PC Interface, select that adapter, and set its baud rate to the bus rate. The PC-side parameters are the ones walked through in the MPI/DP setup guide for a CP 5611.
An MPI segment without repeaters is good for 50 m and 32 nodes at that speed, so a bench or a cabinet door sits comfortably inside both limits.
Addresses and baud rate that must match #
| Setting | Where it lives | Rule |
|---|---|---|
| CPU MPI address | HW Config, CPU properties | Unique on the segment |
| Panel station address | Panel project, S7 MPI driver settings | Unique, different from CPU and PC |
| PC address | Set PG/PC Interface | Unique; 0 is the usual choice |
| Baud rate | All three places above | Identical on every node |
| Highest MPI address | CPU MPI properties | At least the largest address in use |
Read the CPU's values out of HW Config rather than trusting labels or memory, and never park two nodes on one number: a duplicate address is the classic cause of a panel that times out the moment a PC joins.
Worked example: one CPU, one panel, one PC #
Take the CPU at its factory 2, give the PC 0 in Set PG/PC Interface, set the panel's station address to 3, and leave all three at 187.5 kbit/s.
- Largest address in use: max(2, 0, 3) = 3.
- Highest MPI address 31 is at least 3, so the factory setting stands; spare room = 31 − 3 = 28 addresses for a second panel or a drive added later.
- Node count: 3 of the 32 the segment allows.
The decision: change nothing on the CPU, set the panel to 3 and the PC to 0, and walk away. If a node is ever numbered above the highest-station setting, the bus does not poll it — keep every address at or below 31, or raise that setting in the CPU properties first.
Checks that prove the connection #
- Panel alone on the bus: live tag values in the project, no communication fault.
- PC in the PG socket, Accessible Nodes in STEP 7: the CPU at 2 and the panel at 3 both listed.
- Go online and open a block: the HMI keeps updating while the PC holds its connection.
- Download a block: the stop/start transition briefly interrupts the panel, which recovers when the CPU returns to RUN. That is the one step the machine feels, so download only when the controlled equipment tolerates a CPU stop.
- Unplug the PC from the PG socket: the panel runs on, confirming the tap is a service connection and not part of the trunk.
What breaks an MPI segment with a panel and a PG #
- Duplicate address: two nodes claiming one number make the bus unstable, and it is the most common reason a working panel starts timing out when a PC joins.
- Baud mismatch: a node at the wrong speed never joins and can disturb the traffic that is running.
- Wrong termination: a terminated middle connector or two open ends produce reflections and dropped telegrams.
- Swapped A and B: a permanently dead link, not an intermittent one.
- The DP port used by mistake: identical connector, different protocol, so read the marking beside the socket.
Timeouts that grow with bus traffic rather than appearing at connect point to loading on the link; the diagnosis sequence in Why an HMI Freezes or Updates Slowly Over Serial applies line for line. For a 315-2 DP that loses the port in service, start with the steps for resolving MPI/DP communication loss on a CPU 315-2 DP.
Questions asked
Can the MT6100i connect to a 6ES7 315-2AG10-0AB0 without a communication module?
Yes. The 315-2 DP CPU carries the MPI interface on board and the panel has an RS-485 port, so a cable is the only hardware. Wire the panel to the CPU's MPI/DP port and select the Siemens S7 MPI driver in the Weintek project; the dedicated DP port is not involved.
Can STEP 7 be online while the panel stays connected?
Yes. Screw a PROFIBUS connector with a PG socket onto the CPU's MPI/DP port, land the panel's A and B wires in its cable entry, and plug the PC adapter, a CP5711 for example, into the PG socket. The PC is then just another node at its own address, so both stay on the bus at once.
Which port on the 315-2 DP takes the panel?
The MPI/DP port, in MPI mode. The second port is a dedicated PROFIBUS DP master interface for remote I/O, and an MPI-protocol panel will not run there. Both ports are 9-pin D-sub, so read the marking beside the connector before wiring.
What addresses and baud rate should the three nodes use?
Leave the CPU on its factory settings unless HW Config shows otherwise: address 2, 187.5 kbit/s, highest MPI address 31. Give the PC address 0 and the panel address 3. Every node must differ, every node must run the same baud rate, and no address may sit above the highest-station setting.
How do I add a second panel later?
MPI is a multidrop RS-485 bus, so a second panel is another drop on the same trunk, not a second port. Daisy-chain through the connectors, give it an unused address such as 4 at the same baud rate, and keep the 120 Ω termination switched on only at the two physical ends.