AXC F 2152 Watchdog Logic

Hey All,
We’re utilising an AXC F 2152 with .NET 6 running on it. Via a C++ application, running as the plcNext runtime, we start-up and have 2-way comms with the .NET 6 application to provide it will access to the real-time IO (write/read). We’re not utilising any other plcNext tasks etc (i.e. from plcNext Engineer).
Recently we’ve had what appears to be the Watchdog trigger. Even following a soft reset (i.e. sudo reboot), the watchdog appears to remain. The only way to fully reset the watchdog is to perform a full power down restart via the circuit breakers.
We’re wanting to understand:

                                          1. How does the watchdog function (i.e. what could be triggering it)
                                          2. Where the watchdog logs reason for it's triggering
                                          3. What log files on the filesystem would contain pertinent information to track down the root cause?

It is worth noting that the logs under /var/log appear to clear every reboot as they’re written to RAM-backed storage?
Cheers,
Joseph

Hello Joseph,
please see the answers to you questions below.
How does the watchdog function (i.e. what could be triggering it)
→ The Watchdog is a digital system failure detection function, in this case in control application. The WD will be triggered, e.g. if the program runs in endless loop or into deadlock.

Where the watchdog logs reason for it 's triggering
->You can find the diagnostic entries in „/opt/plcnext/logs/Output.log“ data on the PLCnext Target or Notification Logger in the PLCnext Engineer IDE.

What log files on the filesystem would contain pertinent information to track down the root cause?
→ Please find the detailed root cause in „/opt/plcnext/logs/Output.log“ data on the PLCnext Target. You can use the WinSCP-Tool or SSH-Connection to the PLCnext Target for file access.

If nothing is against it, we can create a ticket and analyze the cause of failure together?

BR Eduard