Factory I/O can connect to a simulated Siemens PLC on another computer, but the standard S7-PLCSIM v13–17 driver requires PLCSIM and Factory I/O to run on the same computer. For a two-computer setup, use S7-PLCSIM Advanced or expose S7-PLCSIM to the network with NetToPLCSim and connect through Factory I/O’s S7-1200/1500 standard driver. TIA Portal is used to configure the PLC project; the connection choice depends on the simulator and driver, not simply on whether TIA Portal is installed on a separate machine.
Read the two-computer connection symptom
If Factory I/O cannot connect when it runs on a different computer from S7-PLCSIM, first identify which Factory I/O driver is selected. The S7-PLCSIM v13–17 driver is designed for the same-computer arrangement and requires a special function block (FC) in the simulated project. Moving Factory I/O to another computer does not make that driver a network driver.
For a remote arrangement, choose one of the two stated alternatives:
| Arrangement | Factory I/O driver path | Key constraint |
|---|---|---|
| S7-PLCSIM and Factory I/O on one computer | S7-PLCSIM v13–17 driver | Requires both applications on the same computer and the required special FC. |
| S7-PLCSIM Advanced across computers | Use the applicable simulator connection path | Use PLCSIM Advanced for the split-computer setup. |
| S7-PLCSIM exposed to the network using NetToPLCSim | S7-1200/1500 standard driver | NetToPLCSim exposes the simulator to Factory I/O over the network. |
Separate the engineering project from the PLC connection
TIA Portal is where the PLC project is created and configured. Factory I/O exchanges data with the running simulated PLC through a Factory I/O driver. In the single-computer PLCSIM v13–17 arrangement, the special FC is part of the simulator-specific setup. In the networked alternative, NetToPLCSim exposes S7-PLCSIM so Factory I/O can use its S7-1200/1500 standard driver.
This distinction matters during troubleshooting: a working TIA Portal project does not by itself establish that Factory I/O can reach the simulated CPU. Check the selected Factory I/O driver and the simulator exposure path separately.
Choose the remote simulation procedure
- Decide whether both applications can run on one computer. If yes, use the S7-PLCSIM v13–17 driver and the project setup that includes the required special FC.
- If Factory I/O must run on a different computer, choose either S7-PLCSIM Advanced or NetToPLCSim. Do not use the same-computer PLCSIM driver as if it were the network connection path.
- For the NetToPLCSim option, configure NetToPLCSim to expose S7-PLCSIM to the network, then select Factory I/O’s S7-1200/1500 standard driver.
- Start the simulated PLC and the selected network exposure method before testing from Factory I/O. Confirm that the PLC project is running and that the target CPU and network endpoint in the driver configuration correspond to the simulator being exposed. Read the required endpoint values from the actual simulator and driver configuration rather than copying guessed addresses.
- Run the PLC logic and initiate the Factory I/O connection. If the connection does not establish, verify the driver choice and simulator exposure first, then check network reachability between the computers and the configured endpoint.
Verify the connection with live PLC data
Use these checks in order; a successful connection indication alone does not prove that the intended PLC logic is exchanging the expected signals.
- Driver selection: the S7-1200/1500 standard driver is selected for the NetToPLCSim path; the S7-PLCSIM v13–17 driver is used only when Factory I/O and PLCSIM are on the same computer.
- Simulator exposure: for the networked PLCSIM option, NetToPLCSim is configured to expose the running simulator. The expected reading is an active, correctly targeted simulator endpoint in the exposure and driver configurations.
- Connection state: Factory I/O reports an established connection to the target simulator. If it does not, compare the configured target with the endpoint actually exposed and check computer-to-computer reachability.
- Data exchange: change a known input in Factory I/O and observe the corresponding PLC input or logic response in TIA Portal; then verify that a PLC output change appears in Factory I/O. The expected result is matching state changes in both directions.
Avoid driver and network-path mismatches
A frequent mistake is to move Factory I/O to another computer but retain the S7-PLCSIM v13–17 driver. That driver’s same-computer requirement remains in force. Another is to configure NetToPLCSim but leave Factory I/O on the PLCSIM-specific driver instead of the S7-1200/1500 standard driver.
Also distinguish network reachability from PLC data exchange. An endpoint that appears reachable does not prove that the selected Factory I/O driver is communicating with the intended simulated CPU or that the expected signals are mapped. Confirm live input and output changes after the connection is established.
Factory I/O and TIA Portal connection FAQs
How do I connect Factory I/O to S7-PLCSIM on another computer?
Use S7-PLCSIM Advanced or expose S7-PLCSIM with NetToPLCSim. For the NetToPLCSim path, select Factory I/O’s S7-1200/1500 standard driver.
How do I use the S7-PLCSIM v13–17 driver?
Run Factory I/O and S7-PLCSIM on the same computer and use a project containing the required special FC. This driver is not the split-computer network path.
Can TIA Portal run on a different computer from Factory I/O?
The connection decision concerns Factory I/O’s driver and the simulated PLC. For a split-computer setup, use PLCSIM Advanced or the NetToPLCSim and S7-1200/1500 standard-driver path.
How do I troubleshoot a Factory I/O connection failure?
Check that the selected driver matches the simulator arrangement, confirm the simulator is running and exposed, then compare the configured endpoint and verify network reachability.
How do I verify Factory I/O is exchanging PLC data?
Change a known Factory I/O input and observe the PLC response in TIA Portal, then change a PLC output and confirm the corresponding Factory I/O state changes.