Siemens S7 collector

basic settings these settings are used by the collector to successfully connect to the siemens s7 device or gateway host description hostname or ip address of the s7 device or gateway required yes example 192 168 0 10 this defines the network address of the siemens plc or gateway that the collector connects to port description tcp port of the s7 device or gateway required no default 102 port 102 is the standard iso on tcp (rfc 1006) communication port for siemens s7 controllers rack description the rack number of the s7 cpu required no default 0 slot description the slot number of the s7 cpu required no default 2 for most siemens s7 300, s7 400, s7 1200, and s7 1500 systems, the cpu is located in slot 2 advanced settings these settings are specific to the s7 communication layer and not part of the shared base collector configuration timeout description tcp connect and read timeout in milliseconds required no default 10000 idletimeout description tcp idle timeout in milliseconds set to 0 to disable required no default 60000 retryinitialbackoffms description initial backoff time for connection retries in milliseconds required no default 500 retrymaxbackoffms description maximum backoff time for connection retries in milliseconds required no default 5000 measurement settings the measurement settings define how the collector reads data points from siemens plc memory memoryaddress description absolute s7 memory address in step 7 (dot) or kepware (comma) syntax required yes examples bit db1 dbx0 1 or i0 byte db1 dbb2 word db1 dbw4 double word db1 dbd8 array db1 dbw0 dbw8 string db2,string100 20 use non optimized data blocks (dbs) for consistent addressing ranges must stay within one db and align to element size bit ranges are not supported plcdatatype description the datatype of the plc value required yes example real rules bool requires a bit index in the address string length must come from the address ranges must align with element size ( word=2 , dword/dint/real=4 ) for step 7 dbd addresses, this determines whether to interpret as dword , dint , or real collectioninterval description poll interval in milliseconds required yes default 1000 collectionoffset description offset in milliseconds relative to the 0th second required yes default 0 collector health s7 specific collector health messages see for all generic collector health messages you can find the collector health and collector history in the detail view on the right when selecting a collector in the historian admin webpage error initializing collector an error occurred when initializing the siemens s7 collector this indicates that a setting is misconfigured or the s7 device/gateway is unreachable during initialization error connecting to s7 device the collector failed to establish a connection with the s7 device or gateway disconnected timeout the collector lost connection to the s7 device due to a tcp timeout or communication failure siemens s7 communication notes firmware compatibility siemens s7 plc firmware upgrades can impact data collection please contact factry support before performing firmware upgrades firmware updates may change the protocol behavior or security model of the plc optimized block access (s7 1200 / s7 1500) newer siemens plcs (especially s7 1200 and s7 1500 ) use optimized block access , which dynamically changes the memory layout the s7 collector uses static memory addressing , reading data directly from fixed plc memory regions when “optimized block access” is enabled, these addresses can change after plc program modifications, causing measurements to fail to ensure compatibility in tia portal , disable “optimized block access” db → properties → general → optimized block access → off in cpu properties → protection , enable "permit access with put/get" ✔️ only non optimized data blocks (dbs) are supported by the s7 collector https //flows nodered org/node/node red contrib s7 older plcs (s7 300, s7 400) do not have optimized block access and are fully compatible block reads siemens s7 devices read multiple tags in blocks the collector automatically groups measurements together and reads as many tags as possible in one request to reduce communication overhead this block read optimization minimizes plc communication load and improves performance