Hi All,
KRC4 KSS 8.6
I had a question regarding tool changes with CIP safety and the activation and reactivation of safety configurations. What I am looking to avoid is the need to reactivate the safety configurations on tool change over. For example if I have a substantial set of tools that get swapped around on machines and each tool has a project tied to it (reason for this is because there are some substantial differences between some tool operations), but all of the tools are declared in each project and projects safety setup and all have the ability to touch off the reference position in the exact same location and the safety configuration being the same across all. Am I correct in saying that each tool would then need the same inbuilt IO hardware for the safety configuration not to be needed to get reactivated on each change over since the IO will vary (only the addition of removal of a input or output slice) or is it possible to define worst case i.e. tool with the most IO that would cover the IO requirements of all the other tools in the hardware configuration (input and output byte sizes) or would this need reactivation of the safety config the same as if on Ethercat when a slice gets added or removed?
Thanks