NT151 (the new Gateway) - mapping generation failure due to hardcoded GUIDs of <Status> signals in Process Data.

In the new NT151 Gateway device there is an allowed combination Port X2: PROFINET IO Device, Port X3: PROFINET IO Device. In this case the Profinet IO Device DTM is instantiated both as basenet and subnet DTM.

When selecting the two networks in NT151 "Settings" page - there is an error (PNIODevice hardcoded GUIDs.png):

"Trying to add key 'CE6124B1-7019-4a23-8CE1-E2F6B71E1DFB', object 'Subnet, Status, CE6124B1-7019-4a23-8CE1-E2F6B71E1DFB', 'Basenet, Status, CE6124B1-7019-4a23-8CE1-E2F6B71E1DFB' already exists under this key. -> Device: netTAP[NT 151-RE-EN]<>(#2) "

For the "mapping" - the process data of the two DTMs is used. Referring to CPNIODeviceDTM::Export method - the GUIDs of Status signals are hardcoded, hence are the same for base network and subnetwork.

Expected: new GUIDs for systemTag-s of the status signals in every new DTM instance.

A check how it is for other DTMs, e.g. EtherCAT Slave - the GUIDs are saved and loaded from project. On new instance - new GUIDs are generated.