Troubleshooting WinAC RTX 2010 NIC Submodule Detection

The Intel PRO/1000 PT Dual Port adapter works for ordinary Windows network communication but does not appear under WinLC Properties > Submodule > Available interfaces in the reported WinAC RTX (F) 2010 installation, V4.6 + SP3 + Upd1. That distinction matters: Windows recognizing a network card does not by itself make the card an available WinLC submodule for PROFINET IO.

Identify the missing WinLC interface stage

WinAC hardware configuration and Windows network configuration answer different questions. Windows can load a driver and use an adapter for communication while WinLC's available-interface list omits it. The Windows test confirms that the operating system recognizes the device; the WinLC list is the relevant test for whether this configuration can select the interface as a PROFINET IO submodule.

In the reported setup, a laptop running TIA Portal V15.1 and WinCC communicated with the PC, but the card was absent from the WinLC submodule list. That communication success does not establish that the NIC is supported for WinAC's PROFINET IO use. Keep the two outcomes separate when diagnosing the fault.

1. Open the WinLC properties and inspect Submodule > Available interfaces.
2. Record whether the Intel adapter is absent there, rather than treating successful Windows communication as proof of WinLC availability.
3. Confirm that the intended task is PROFINET IO communication with the ET 200 SP, which requires a selectable WinLC interface in this configuration.

Check: The fault is isolated to WinLC interface availability if Windows can use the adapter but the WinLC available-interface list remains empty or does not list that adapter.

Separate Windows recognition from WinAC eligibility

Adapter detection has at least two gates in this case: Windows must install and expose the network interface, and WinAC must recognize it as a supported submodule. Passing the first gate does not guarantee passage through the second. A missing Windows driver is a host configuration problem; an adapter that works in Windows but is absent from WinLC points toward WinAC support or configuration compatibility.

Check: For this reported PC, Device Manager showed the card. Verify its presence in Windows Network Connections as well; if Windows exposes it but WinLC still omits it, continue with compatibility rather than repeating ordinary network connectivity tests.

Verify the Windows adapter installation

Before judging WinAC compatibility, confirm that Windows has installed the NIC driver and exposes the adapter as a network connection. A device entry alone and a functioning network interface are not identical checks. The diagnostic path proposed for this problem is to inspect both Device Manager and Network Connections.

1. Inspect Device Manager and confirm that the Intel adapter is present without an installation problem.
2. Open Windows Network Connections and confirm that Windows lists the adapter there.
3. Test the ordinary communication path that already works, but record it only as evidence of Windows-level connectivity—not as proof that WinAC supports the adapter for PROFINET IO.

If the adapter is missing from Network Connections, correct the Windows installation first. If it appears in both Windows views and still does not appear under WinLC, stop cycling through basic driver checks and compare the hardware against the WinAC-specific support information.

Check: The expected prerequisite is an adapter visible as a network connection in Windows and functioning for the ordinary PC-to-laptop communication described in the setup. This result permits the WinAC compatibility check; it does not close it.

Compare the exact NIC with the WinAC configuration

WinAC may accept a narrower set of network adapters for its submodule interface than Windows accepts for general networking. Use compatibility information for the exact WinAC RTX (F) 2010 release and installed update level, rather than inferring support from a related chipset name or from Windows operation.

The reported adapter is an Intel PRO/1000 PT Dual Port NIC. Its chipset marking is 82571GB rather than 82571EB. Intel documentation quoted in the setup says the 82571GB is functionally equivalent to the 82571EB, and the 82572GI to the 82572EI. Functional equivalence between chipset variants does not establish that WinAC lists or supports either adapter as an available submodule. The adapter model, chipset, driver, and WinAC release are distinct items to compare against the applicable compatibility information.

1. Record the full adapter model and chipset marking from the installed card or Windows device details.
2. Record the installed WinAC version exactly as shown: V4.6 + SP3 + Upd1.
3. Check WinAC-specific documentation or compatibility records for that release and configuration; do not substitute a Windows driver listing or a chipset-equivalence statement for an explicit WinAC support check.
4. If the documentation does not resolve the model, test a documented supported interface or supported PC configuration and inspect the same WinLC list.

Check: A compatible candidate should be named or otherwise identified as supported for the relevant WinAC configuration and should appear in Available interfaces. If documentation does not identify the Intel adapter and it remains absent, treat it as unsupported for this configuration until a supported alternative passes the listing test.

Resolve the WinAC RTX (F) hardware question

The “F” designation raised a separate concern in the reported discussion: whether a failsafe configuration requires specially certified hardware. That concern was not resolved by the observed NIC behavior. Do not diagnose the missing adapter as a certification failure, or dismiss the F designation as irrelevant, without checking the requirements for the exact failsafe configuration.

Check the WinAC RTX (F) documentation for hardware restrictions that apply to the configured controller and for any distinction between supported hardware and safety-related certification. These are separate questions: a component can be absent because WinAC does not support it for the interface role, while a safety configuration may impose additional system-level requirements. The discussion also distinguished hardware support from software certification, but it did not establish a universal rule for this installation.

Check: The expected result is a documented answer for the precise WinAC (F) configuration: whether the candidate PC/NIC is supported and whether the safety configuration imposes additional requirements. If either remains unclear, choose a configuration explicitly documented for the intended use rather than treating the F label alone as the cause.

Select and configure a supported interface path

If the Intel adapter is not available to WinLC, changing Windows connectivity settings will not make an unsupported device a WinAC submodule. The practical alternatives raised for this setup were a CP 1616 or CP 1604 network card, or a SIMATIC IPC configuration. These are candidates to evaluate, not guarantees for every WinAC release or configuration.

SIMATIC IPC models mentioned as having worked in other installations were IPC427C, IPC677C, and IPC427D. Match any candidate model and network interface to the exact WinAC version and failsafe requirements before purchase or deployment; a model name alone does not establish a supported configuration for this PC.

1. Choose a card or IPC configuration identified as supported for the required WinAC release and PROFINET IO role.
2. Install and expose the interface in Windows, then reopen WinLC hardware properties.
3. Select the interface only after it appears under Submodule > Available interfaces, and complete the PROFINET IO configuration for the intended ET 200 SP connection.

A virtual machine with a custom BIOS was also mentioned as a training approach, with an explicit warning that it is not endorsed or approved by Siemens. Keep that option separate from a supported production design; do not treat a reported training workaround as a supported hardware configuration.

Check: Before proceeding to network commissioning, the selected candidate must appear by its interface entry in the WinLC available-interface list. If it does not, return to the exact hardware/software compatibility decision rather than assuming that installation or Windows communication is sufficient.

Verify the complete PROFINET IO path

Seeing an interface in the list proves only that WinLC can offer it for configuration. It does not by itself prove that the configured controller communicates with the ET 200 SP. Commission the interface and verify both configuration selection and actual device communication.

1. Confirm that the chosen NIC is visible in Windows Device Manager and Network Connections.
2. Confirm that the same interface appears and is selected in WinLC under Submodule > Available interfaces.
3. Check the WinAC hardware configuration for the intended PROFINET IO connection to the ET 200 SP.
4. Run the intended communication test and inspect the controller and device diagnostics for a successful, stable connection; use the displayed diagnostic status rather than inferring success from the Windows laptop connection.

Final check: The installation passes when the adapter is Windows-visible, selectable as a WinLC submodule, configured for the intended PROFINET IO path, and the ET 200 SP is reported communicating in the controller/device diagnostics.

Frequently asked questions