FANUC PROFINET to Siemens S7 in TIA Portal: GSDML, Device Name, and the Slot Map That Stops PRIO-620

You have a FANUC R-30iB or R-30iB Plus with a Profinet board, a Siemens S7-1200 or S7-1500 PLC, both wired into the same managed switch, and TIA Portal refuses to bring up the connection. Maybe you see “GSDML Device type doesn’t match” in the device view. Maybe the link is green but every byte reads zero. Maybe PRIO-620 PNIO station deactivated keeps popping up on the teach pendant every minute. At Probot Systems, this is one of the most common commissioning calls we get from plants that mix Siemens process logic with FANUC robotic cells, and there is a predictable order of failure modes.

This post is written for controls and integration engineers working between a FANUC R-30iB or R-30iB Plus (Mate Plus and CRX-30iA included) and a Siemens S7-1200, S7-1500, or S7-300 PLC. It applies whether you are running TIA Portal V14 through V19 or the older Step 7 V5.5.

How FANUC Profinet actually works under TIA Portal

Profinet is not Ethernet/IP with a different label. The IO controller (PLC) addresses the IO device (FANUC) by device name, not by IP address. The IP shows up on the wire, but the DCP protocol uses the configured PNIO Name as the binding key. If you assign the wrong name on the FANUC side, TIA cannot pair the device to its slot in the project, and the connection never completes, even if pings work.

The official FANUC alarm code manual states for PRIO-620: “The device whose Show error when deactivated setting is ON is deactivated. Remedy: Check the station specified the station number, and activate it.” That sentence reads as if the fix is on the FANUC side, but in practice 80% of the time the device was deactivated by the IO controller because the project view in TIA does not match the live device, usually a GSDML or slot mismatch.

The data flow on a healthy connection looks like this: TIA Portal compiles a project against a specific GSDML for the FANUC board model (for example gsdml-v2.42-fanuc-a05b2600s536v940p2p-20220518.xml for an A05B-2600-S536 on V9.40). The PLC pushes that configuration to the device by name. The device must report back a matching slot layout, or the connection drops.

Most common causes, in order of probability

1. GSDML revision does not match firmware on the FANUC board. The most frequent failure. A robot running V9.40/79 firmware needs a 2022 GSDML. An older V9.10 robot needs the 2018 GSDML. The forum thread Profinet Fanuc Board Setup Issues is the canonical example: an S7-1500 cannot pair the FANUC board because TIA says “GSDML Device type doesn’t match”.
2. Device name mismatch. TIA sets one name in the project (fanuc-station-1), the FANUC config screen has a different name (fanuc1), and Profinet refuses to bind. Visible from TIA’s online accessible devices view.
3. Slot/module count or sizes wrong on one side. A 32-byte input module configured in TIA but 16 bytes on the FANUC will drop the connection at startup. The HELP NEEDED: CRX10iA PROFINET communication with Siemens S1200 PLC thread walks through this exact mismatch on a CRX10iA with R30iB Mini Plus.
4. F-modules (safety) wired wrong. If you have F-DI/F-DO modules, the F-iPar CRC must match between PLC and robot. The F_iPar_CRC Check thread covers this. Standard data may run while safety drops independently.
5. Two IO controllers on the same subnet. A Siemens HMI configured as a Profinet IO controller in addition to the main PLC will fight for the FANUC. Only one IO controller per device.
6. VLAN tagging or multicast filtering on a managed switch. Less common but real. Profinet needs the DCP layer to reach the device unfiltered.

How to set this up correctly

Step 1. Read the firmware version on the FANUC Profinet board. On R-30iB Plus that is MENU > 4 STATUS > Version ID > F2 NEXT to find the option string. Match it to the GSDML you load in TIA. The order code itself (A05B-2600-S536 for instance) tells you which family, but the firmware suffix tells you which GSDML revision.

Step 2. In TIA Portal, install that exact GSDML under Options > Manage general station description files. Delete any older GSDML for the same board family to avoid TIA picking the wrong one. Then add the FANUC from the catalog into the project’s PROFINET IO network.

Step 3. On the FANUC, set the device name under MENU > I/O > PROFINET (M) > Settings. The thread R-30iB MATE PLUS IO-DEVICE Configuration emphasizes that name (not IP) is the primary binding identifier. Type the same string in TIA’s PROFINET device properties.

Step 4. Configure slot modules on both sides. If you want 32 bytes IN / 32 bytes OUT plus a 12-byte F-module, configure exactly that on both sides, in the same slot order. Save and download to PLC.

Step 5. Cold start the FANUC. Profinet binds at boot, not on the fly. If you change device name or slot config and reset only, the controller will keep reporting the old configuration.

Step 6. Watch the TP alarm log. A clean connect shows PRIO-619 or PRIO-625 “connection established”. If you see PRIO-620, the IO controller deactivated the station, almost always because of one of the mismatches above.

How to fix it when PRIO-620 keeps firing

GSDML mismatch fix. Pull the GSDML that matches the FANUC firmware. The A05B-2600-S536/A05B-2690-J084 Profinet to S7-1200 Gen2 thread documents which GSDMLs pair to which order codes. Delete the old module from the TIA project, re-add from the new GSDML, redo your tag mapping (TIA does not migrate tags between GSDML revisions), and recompile.

Device name mismatch fix. Use TIA’s “Assign device name” function over the live network. Right-click the FANUC in the project view, choose “Assign device name”, let TIA browse and rewrite the name on the live FANUC. Saves you a trip to the teach pendant.

Slot count or size fix. Edit the FANUC side, not the PLC side, if at all possible. The PLC project carries downstream consequences (tag references, AOIs). On the FANUC, MENU > I/O > PROFINET (M) > Slot Config lets you set per-slot byte sizes. Match TIA exactly.

F_iPar safety CRC mismatch. This is its own rabbit hole. The CRC has to be identical on both ends including module order, F-destination address, and PROFIsafe timeouts. The Fanuc Profinet Configuration thread shows the slot-1 safety module failing while slots 2 and 3 (DI/DO) run cleanly. If standard data is healthy and only safety fails, focus on the F-parameter assistant in TIA, not on the rest of the Profinet stack.

Two scanners fix. Look for HMIs, drive systems, or test laptops with TIA running in simulation that may be acting as IO controllers. Disable Profinet on every device but the intended PLC.

When to call a specialist

PROFINET-to-FANUC is one of those problems where the failure is not in any one place but in the disagreement between two configurations. If you have matched GSDML, name, and slot map, and the connection still will not stay up, the next layers are F-iPar CRC, network topology (multiple IO controllers, VLAN), or the rare case where the FANUC Profinet option file itself is corrupt and needs a fresh load.

For brownfield jobs where you are dropping a FANUC cell into a Siemens-house line, the cleanest result comes from documenting the GSDML, slot map, and PROFIsafe parameters before either side is touched. contact us if you want a pre-startup audit of the Profinet config, or set up a maintenance preventive contract so PRIO-620 is caught in monthly health checks rather than at 2am.

Related errors to check

• PRIO-621 PNIO(D) device is not running: same family, FANUC side did not start. Often the option file or firmware needs a fresh load.
• PRIO-622 PNIO(C) controller is not running: appears when the FANUC is configured as an IO controller (rare but valid) and cannot reach its devices.
• PRIO-623 PNIO(C) not in operation mode: start mode set wrong on the FANUC IO controller side.
• PRIO-624 PNIO(C) mod number mismatch: textbook slot map disagreement.

Probot Systems is a FANUC integrator based in Lévis, Quebec. We commission Profinet links between FANUC robots and Siemens PLCs across Canadian and US plants, and our engineers carry the GSDML library across firmware revisions so the matching is not done over Google. contact us for a Profinet integration project, or before a controller upgrade that may break GSDML pairing on a running cell.