May-25th-2020, 09:24 AM
Hello, your understanding is not correct.
If you want to read/write data sets from/to an S7 PLC like your Windows TIA portal software is doing it during programming session or diagnostics then you do NOT need fieldbus nodes and you have to use S7 Comm nodes instead. These nodes support a subset of the functiond a TIA portal software supports. For this the netPI and IP address needs to be in the same subnet as you TIA Portal Windows PC and connected to the same Ethernet switch for example. Then the S7comm nodes can access to the PLC at the same time as your TIA portal software.
In contrast of this previous use case is if you want to exchange process data from PLC I/O buffers with a PROFINET IO slave like with Beckhoff IO or Wago IO devices, then you need the fieldbus nodes. The Fieldbus nodes let the netPI simulating IO data that can be exchanged with Node-RED forth and back.
Thx
Armin
If you want to read/write data sets from/to an S7 PLC like your Windows TIA portal software is doing it during programming session or diagnostics then you do NOT need fieldbus nodes and you have to use S7 Comm nodes instead. These nodes support a subset of the functiond a TIA portal software supports. For this the netPI and IP address needs to be in the same subnet as you TIA Portal Windows PC and connected to the same Ethernet switch for example. Then the S7comm nodes can access to the PLC at the same time as your TIA portal software.
In contrast of this previous use case is if you want to exchange process data from PLC I/O buffers with a PROFINET IO slave like with Beckhoff IO or Wago IO devices, then you need the fieldbus nodes. The Fieldbus nodes let the netPI simulating IO data that can be exchanged with Node-RED forth and back.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
