Connection is established and PNController operates with SendClock1ms RR= 8 ->8ms.
PNIOTask is calc cyclically every 1ms. What may be the reason to the connection loss. Is it reasonable on Controller or Device Side?
Instead of increasing the reduction-rate I wanted to set the sendclock directly to 8ms.... that is not supported so far. Any reason that it is greyed out? Failure in gsdml?
It seems that the PNdevice side is reasonable for the HDT failure, since a colleagues operating the PNController with PN-IO newer so that messages.
Could you please provide details of the failure case... what are the criterias to through the failure? is the PN-WD setting basically the criteria? What would be strange since
And what about the "naming" baptiste at the beginning ot the PN Connection. I do not see the given name in the PN-Device... If I could get some further details - that would be great.
Thanks in advance.
So most devices only support a SendClock of 1ms. Some also 2ms 4ms. Larger is not possible. The DHT error means that the send clock of the device was not kept, so the controller closes the connection.
Could you rise the priority of the pn device io task to the highest for a test. -> 0
On ctrlX CORE the PLC task priority has to be in the range of 20 to 39. 20 is the highest priority.
Values out of this range will result in an error message.
thanks to @CodeWasi he did a Profinet capture, after a first investigation, the device send a
Status: Error: "RTA error", "PNIO", "RTA_ERR_CLS_PROTOCOL", "AR consumer DHT/WDT expired (RTA_ERR_ABORT)"
we checked the last cycle times, it's mostly below 8ms.
The observation was, reboot/power cylce the device will not force the issue, reboot/power cylce the controller will force the issue.
The question is, why send the device this abort?
since cc2go mentioned the result of the analysis from Wireshark your feedback will be highly appreciated.
Even with S7-PN-Controller and recommended Prios and unsuspious load DHT expired was monitored.
Thanks in advanve for your cooperation.