Current we have 1 tia portal project connecting a S7-1515F with multiple ET200SP's by (F)I-device for normal and safety communication. The S7-1515F complete's the safety loop and keep track of the zones. For the rest the ET200SP's run self depended.

For future installations we want to seperate the CPU programs to their own project files and make them "default". So that during manufacturing of the devices, software can be downloaded with a small config file. This without needing to change things in the software before or after.

This is because we want the devices to be able to work in multiple projects and that we only have to update the config file of that CPU on moving the device to a other project.

For normal communication between CPU's i can make this working by just defining the IP adress to talk to in a config file of each CPU.

But for safety communication i need HW identifiers that are ofcourse unknown or duplicate because the software doesnt know of the other CPU's in the network.

So my question is how can i get safety communication with an "unidentified" CPU of wich only the IP-adress is known?

And when this is impossible does somebody have a genius idea for solving this "issue"?

With kind Regards

Rik de Vette