Give every device the PROFINET name and IP from the architecture drawing, set each panel's I/O start bytes to match its hardware layout sheet, paste the PLC tag table from Excel and check each tag against its terminal, then prove every I/O in a Factory Acceptance Test (FAT).
- Names and IPs come from the architecture drawing, typed once in the Network view
- Each panel gets its own byte block (MCP 0, RIO_1 10, RIO_2 20, RIO_3 30) that matches its hardware layout sheet
- Tags are pasted from Excel per panel and checked against every terminal
- The FAT proves each I/O from field device to MTP700 before the panel leaves the workshop
One real job, four animated steps: a skid conveyor line with a main control panel (MCP), three ET 200SP remote I/O stations (RIO_1 to RIO_3) and an MTP700 Unified Comfort panel. Each step uses the same names, addresses and terminals, so what you configure is exactly what you test.
Your TIA Selection Tool parts list is the input: transfer the station from TIA Selection Tool, or add each order number from the hardware catalog. Then check on the real panel that every nameplate matches the list (MLFB decoder), note the firmware, and confirm the memory card and front connectors are fitted.
Set the PROFINET Device Name and IP Address from the Architecture
Every box on the architecture drawing becomes a device in the Network view, with the name and IP written on the drawing. Press play or click any device.
Properties › PROFINET interface [X1] › Ethernet addresses
| Device | PROFINET name | IP address | |
|---|---|---|---|
| Engineering PC | — | 192.168.0.100 | ✓ |
| SCALANCE XC208 | mcp-switch | 192.168.0.3 | ✓ |
| SINAMICS G120 | vfd-tt-01 | 192.168.0.21 | ✓ |
| CPU 1511-1 PN | mcp-plc | 192.168.0.1 | ✓ |
| MTP700 Unified | mcp-hmi | 192.168.0.2 | ✓ |
| RIO_1 · ET 200SP | rio-01 | 192.168.0.11 | ✓ |
| RIO_2 · ET 200SP | rio-02 | 192.168.0.12 | ✓ |
| RIO_3 · ET 200SP | rio-03 | 192.168.0.13 | ✓ |
Address plan from the architecture drawing. Every device on one subnet, no duplicates.
Configure the I/O Byte Addresses and Match Each Panel Drawing
Open each panel in the Device view and set every module's start byte to the address printed on its hardware layout sheet: MCP from byte 0, RIO_1 from 10, RIO_2 from 20, RIO_3 from 30.
Orange callouts are the addresses on the drawing. Each one turns green when the Device view matches it. The first ET 200SP module sits on a light BaseUnit (new potential group); the others use dark BaseUnits.
Want to practise this on real hardware?
Read real panel drawings, configure S7-1500 with ET 200SP and an MTP700, then run a FAT. Pune classroom or online.
Copy-Paste PLC Tags from Excel and Match Each Terminal
One tag table per panel. Copy Name, Data type and Address from Excel, paste them into the PLC tag table, then check every tag against its terminal on the drawing.
- Add a tag table per panel:
MCP_IO,RIO_1_IO,RIO_2_IO,RIO_3_IO. - Copy the tag rows, click the Name cell of <Add new>, press Ctrl+V. Then paste the comments into the first Comment cell.
- Compile the tag table. A duplicate name or address turns red.
Excel formulas for building the tag sheet
| A | B | C | D | E | F | |
|---|---|---|---|---|---|---|
| 1 | Prefix | Signal | Name | Data type | Address | Comment |
| 2 | RIO_1_OPB_1_ | Emergency_Stop | RIO_1_OPB_1_Emergency_Stop | Bool | %I10.0 | RIO_1 OPB_1 Emergency Stop |
| 3 | RIO_1_OPB_1_ | Auto_Mode_Selected | RIO_1_OPB_1_Auto_Mode_Selected | Bool | %I10.1 | RIO_1 OPB_1 Auto Mode Selected |
| 4 | RIO_1_OPB_1_ | Manual_Mode_Selected | RIO_1_OPB_1_Manual_Mode_Selected | Bool | %I10.2 | RIO_1 OPB_1 Manual Mode Selected |
| … | Formulas in row 2, filled down: C2 =SUBSTITUTE(A2&B2," ","") D2 Bool E2 ="%I"&($H$1+INT((ROW()-2)/8))&"."&MOD(ROW()-2,8) F2 =SUBSTITUTE(TRIM(A2)&B2,"_"," ") with the start byte (10) in H1 | |||||
| Mistake in the sheet | What it produces | Fix |
|---|---|---|
Joining with a space: =CONCAT(A2," ",B2) | MCP_ Emergency_Stop: a name with a space, which must be quoted everywhere and breaks text-based imports | Join without a separator and strip spaces: =SUBSTITUTE(A2&B2," ","") |
| Prefix typed with stray spaces | Some rows MCP_OPB_2_ Emergency_Stop, others without: inconsistent names for the same signal | Same formula; then sort column C and look for odd ones out |
| Spelling in the signal column | TC_Forword_Position, PRB_16_Dleivery_Permission copied into every station | Spell-check column B once before filling down |
| Generic names without a station prefix | Ten tags called Emergency_Stop; TIA Portal refuses duplicates | Always prefix with station and device: RIO_2_OPB_5_ |
Full electrical drawing sheets: OPB_1 and PRB_1 motor feeder
Animated FAT Test of Every I/O
Download, go online, then prove each signal end to end: field device › terminal › module channel › PLC tag › MTP700. Inputs are operated by hand; outputs are forced with the motor loads isolated.
MTP700 · I/O diagnostics
FAT vs SAT
| FAT (Factory Acceptance Test) | SAT (Site Acceptance Test) | |
|---|---|---|
| Where | Panel builder or integrator workshop | Customer plant, after installation |
| Field devices | OPB stations connected, sensors and motors simulated or bench-mounted | Real conveyors, sensors and skids |
| Proves | Wiring, configuration, addressing, tags, HMI and alarms | The complete line works with real product |
| Signed by | Integrator tester and customer witness | Commissioning engineer and plant owner |
Full FAT sign-off sheet (17 tests)
| ID | Test | How to test | Acceptance criterion | Result |
|---|---|---|---|---|
| Panel power and safety | ||||
| F-01 | Hardware matches configuration | Go online, Online & diagnostics on MCP, RIO_1, RIO_2, RIO_3 and the G120 | All stations green; no "configured and actual module differ" message | |
| F-02 | MCB trip feedbacks | Switch off each MCB in turn (e.g. -F23 Ethernet switch, -F24 I/O 24 V) | Matching MCP_..._MCB_Trip_Feedback goes to 0 and the MTP700 raises the alarm. For the PLC and HMI MCBs check the alarm log after power returns | |
| F-03 | Emergency stop chain | Press the E-stop on the MCP and on every OPB, one at a time | Emergency_Healthy drops, all motor commands drop, tower lamp red and hooter on; restart only after Fault reset | |
| Network and stations | ||||
| F-04 | Address plan | Accessible devices scan from the engineering PC | Every name and IP matches the address plan table | |
| F-05 | Remote station loss | Unplug the cable between RIO_1 and RIO_2, then reconnect | RIO_2 and RIO_3 both reported failed (line topology), their outputs go to 0, MTP700 shows station fault; both return automatically | |
| F-06 | Drive communication | Unplug the G120 cable; reconnect | VFD_Communication_Fault set and alarm shown; clears after reconnect and Fault reset | |
| Field I/O | ||||
| F-07 | OPB push buttons and selectors | Operate every device on each OPB; watch the MTP700 I/O diagnostics screen | Only the matching tag changes. Auto/Manual selector: exactly one of the two contacts is 1 | |
| F-08 | Lamp test | Press Lamp_Test_Push_Button on MCP and on each OPB | All push button lamps and all tower lamp colours light while held | |
| F-09 | Entry and exit sensors | Hold a metal target in front of each sensor on PRB_1 to PRB_16 | Entry_Sensor / Exit_Sensor of the correct roller bed goes to 1 | |
| F-10 | Motor direction | Manual mode, press Manual forward on PRB_1 (loads connected, guards on) | Forward_On_Command = 1, -K11 pulls in, Contactor_On_Feedback = 1, rollers turn forward | |
| F-11 | Contactor feedback fault | Lift the -K11 aux feedback wire, then command forward | Contactor_On_Feedback_Fault after Motor_Contactor_On_Timer expires; motor command dropped; alarm on MTP700 | |
| F-12 | MPCB trip | Switch off -Q11 while PRB_1 is running | MPCB_Trip_Fault, motor stops, alarm names PRB_1 and RIO_1 | |
| MTP700 HMI | ||||
| F-13 | Screens and navigation | Open every screen from the navigation bar | No screen shows #### or a missing-tag symbol; values update live | |
| F-14 | Alarms | Raise three different faults, acknowledge from MTP700 and from the Fault acknowledge push button | Alarm text matches the tag comment, timestamps correct, acknowledge works from both places | |
| F-15 | Tower lamp and hooter | Run auto, switch to manual, create a fault, press Hooter off | Green in auto, yellow in manual, red flashing on fault, hooter silenced by Hooter_Off_Push_Button | |
| Documentation | ||||
| F-16 | Tag table audit | Cross-reference all PLC tags; search tag names for spaces | Every tag has type, address and comment; no spaces, no duplicates, no unused addresses | |
| F-17 | Archive and sign-off | Archive PLC + MTP700 project (.zap), record firmware, attach this sheet and the I/O list | Signed by tester and customer witness; punch list closed | |
Every failed test goes on a punch list with cause and fix, and is re-tested before sign-off. On conveyor panels the usual FAT failures are two adjacent terminals swapped on an OPB, an E-stop wired NO instead of NC, a feedback contact taken from the wrong auxiliary block, and a PROFINET name typed differently on the station and in the project.
If a station stays red after download
| Error / symptom | Likely cause | Fix |
|---|---|---|
| "No accessible devices found" | PC on a different subnet or wrong adapter selected | Set the PC IP to 192.168.0.100 and pick the right PG/PC interface |
| RIO station red, "device name not assigned" | Name on the ET 200SP head differs from the project | Online & diagnostics > Assign PROFINET device name, choose the station from the list |
| RIO_2 and RIO_3 both fail together | Cable or port fault between RIO_1 and RIO_2 (line topology) | Check the RIO_1 port 2 and RIO_2 port 1 link LEDs |
| "Configured device does not match the actual module" | A different module or firmware in the slot | Correct the Device view to match the hardware layout sheet |
| MTP700 fields show #### or tags never update | Missing HMI connection, wrong PLC in the connection, or DB member not accessible from HMI | Recreate the HMI connection; tick Accessible from HMI/OPC UA on the DB member |
| A tag shows the wrong value in the watch table | Wrong address typed or pasted | Compare with the wiring sheet column for that terminal |
MTP700 overview screen used during the FAT
Frequently asked questions
What is device configuration in TIA Portal?
It's the step where you build a virtual representation of your real hardware — the CPU and every I/O, communication and power module — in the Device view, and set network parameters like the PROFINET device name and IP address, before writing or downloading any program logic.
How do I set a Siemens PLC's IP address for the first time?
Go online with the CPU, open Online & diagnostics, and use "Assign IP address" to write the intended address directly to an unconfigured CPU. From then on, the address can also be set in the project's Device view under PROFINET interface properties.
What is a PLC tag, and why not just use the address directly?
A PLC tag is a symbolic name mapped to a hardware address and a data type. Programs written entirely in raw addresses (like %I0.0) are much harder to read and maintain than ones using clear names like StartButton_PB1, especially once a project has hundreds of I/O points.
Why does my download fail with "configured device does not match"?
The physical module installed in that slot is different from what's configured in the Device view — a different order number, or a firmware version outside the configured range. Update the Device view to match the real part, or install the part that was originally configured.
Can I copy PLC tags from Excel into TIA Portal?
Yes. Arrange Name, Data type and Address as adjacent columns, copy them, click the Name cell of the first empty row in the PLC tag table and press Ctrl+V. Paste comments separately into the Comment column. For bulk edits you can also Export a tag table to Excel, fill it, and Import it back.
Which software do I need for the MTP700 Unified Comfort panel?
The MTP700 is a WinCC Unified panel, configured in TIA Portal with WinCC Unified. Use TIA Portal V17 or later and match the device image version in the project to the one on the panel.
What is a FAT after PLC configuration?
A Factory Acceptance Test is a documented test, done at the panel builder's facility before shipping, that checks the configured hardware matches the drawings, every I/O point reaches the correct PLC tag and HMI screen, and faults such as an MPCB trip, a missing contactor feedback or a lost remote I/O station are detected and alarmed.
How do I bring a TIA Selection Tool configuration into TIA Portal?
Either transfer the station from TIA Selection Tool into your TIA Portal project with the tool's export, or build it by hand by searching each order number from the TIA Selection Tool parts list in the TIA Portal hardware catalog. In both cases check every order number and firmware version against the module nameplates, then set the PROFINET device names, IP addresses and I/O start addresses from your own drawings.
Should I use automatic or fixed I/O addresses in TIA Portal?
Fixed address blocks per station, for example RIO_1 from byte 10 and RIO_2 from byte 20, keep addresses readable and leave room for spare cards. With automatic addressing every module gets the next free bytes in the order it was inserted, so a card added later can end up far away from the rest of its station.
Can I edit the automatically assigned I/O addresses?
Yes. TIA Portal assigns addresses automatically as modules are added, but every module's start address can be edited manually in the Device view if a project standard calls for specific address ranges.