Hello Yacine, quite difficult to answer. By the way -there is a PNDeviceApp version 1.20.6 available to update. But 1.20.5 fullfills as well the PN requirements - checked and certified. The descripted behaviour must not be rootcaused by the ctrlX. Think of the traffic loads on the network and the unpriored setup most likely beeing present on the Controller. PN-Fielbus comm. as well as Non-PNbus traffic by engineering tools are transported on the line/s. It the load is close its capacity limit the next one will the judge for its traffic-amount. I am not that familiar with the PN-controller and PNSwitch setup, but assume that no Priorication for Fieldbus-com takes place. And the bandwidth is completed occupied. Before talking about network.analysis... what about the appearing situation... Is there e.g. an coincidence of network-breakdown and a startinga engineering-session with the ctrlX or other Devices? ... or browser based communication with our or other webUIs? The comm. capacity of the ctrlX-PND is around 100MBit - fieldbus and tcpip rest of engineering etc. Would it be possible to choose testwise other an alternative connections for the Non-PN related parts (Eth0/XF10?). These loads would be neglected on the PN-part? Bye
... View more
