Configuring a Siemens S7 collector

the siemens s7 collector in factry historian allows you to connect directly to siemens s7 plcs or gateways using the native s7 protocol it retrieves process data from the plc, stores it in factry historian, and makes it available for trending, reporting, and analysis this collector is ideal for factories where siemens plcs form the backbone of the automation layer, and where you want a direct, lightweight connection without relying on an intermediary opc server prerequisites before configuring the siemens s7 collector, make sure you have the following permissions in factry historian to manage collectors see docid\ ez9donskd c prf8sfmo an installed siemens s7 collector if not yet installed, follow docid\ iv4 sd56tdxcqkrkcj4kv network connectivity between the collector host and the siemens s7 plc (port 102 must be reachable) access to the plc project in tia portal to verify that the required communication settings are enabled a configured docid\ cdfwrrm xeb6biyuwi0rt to store collected data if you’re setting up an s7 collector for the first time, we recommend reviewing the docid\ q4eksijb5aut99amnuobt reference documentation for background on supported firmware versions, block access settings, and communication modes configure the collector after installation, the collector appears in the collectors overview in factry historian when first started, it will show an initial initial state, meaning it is connected to historian and awaiting configuration to begin configuration, select the siemens s7 collector and click edit you can now specify the connection details host enter the ip address or hostname of the siemens plc or gateway you want to connect to example 192 168 0 10 ensure that the collector host can reach this address over the network port the tcp port used for s7 communication default 102 this is the standard port for siemens iso on tcp (rfc 1006) communication and usually does not need to be changed rack and slot specify the rack and slot of the cpu module in your siemens plc hardware configuration default values rack = 0 slot = 2 for most siemens s7 300, s7 400, s7 1200, and s7 1500 devices, the cpu is located in slot 2 timeout and retry settings you can fine tune connection stability and recovery behavior timeout – tcp connection and read timeout in milliseconds (default 10 000) idletimeout – idle connection timeout in milliseconds (default 60 000, set 0 to disable) retryinitialbackoffms – initial reconnect delay (default 500 ms) retrymaxbackoffms – maximum reconnect delay (default 5 000 ms) for most environments, these defaults are sufficient and should not be changed unless advised by support after entering all fields, click save to store the configuration expected outcome after saving, a green start button appears in the top right corner of the collector page click start to launch the collector when the connection is established, the status changes to collecting the collector will begin reading configured measurements from the plc and forwarding data to historian if the collector remains in initial or error state, check your connection parameters or refer to the troubleshooting section below adding measurements follow the guide on docid\ hzhr shbufehwda80ucqw limits a single s7 collector can handle thousands of measurements, depending on polling interval, plc load, and network conditions the collector automatically groups measurements and reads multiple tags in blocks to minimize communication overhead if you experience performance issues at high frequency (≤ 1000 ms), consider increasing polling intervals for non critical tags splitting measurements across multiple collectors grouping related signals within the same data block to benefit from efficient block reads troubleshooting siemens s7 collector if the collector fails to connect confirm that the plc is reachable from the collector host on port 102 ensure the rack and slot numbers correspond to the cpu configuration verify in tia portal → cpu properties → protection that “permit access with put/get” is enabled check the collector logs in the historian web interface for specific error messages