In a project we have the following configuration:
Each ModeHandler has his own IPC with his respective HMI Modulo.
To represent the diag in each HMI we have to add the EventList on each ModeHandler. At this point everithing is correct each panel throw his own errors.
Problem comes qhen you confirm one of those errors. The EventClear is appied at top level ModeForwarder, that means that all errors are confirmed. That is very risky becose you are confirmed diagnostics that you didn't read and even can cause damages on the modules that you aren't seeing.
You should't confirm the errors of the modules that are not under your control.
In this example is we are using V1 but we have same issue on V2.
The similar behaviour apply to the EasyPanel. PanelToken parameter is not used in a subtree, then you cannot instance for the right Token. Token control will.
Is planned to correct this?
Can we do something to improve it?
Solved! Go to Solution.
That is not the intended behavior. The HMI only sets the EventClear variable at the ModeHandler corresponding to the HMI instance, not at the ModeForwarder. We will investigate if we can reproduce a misbehavior on the PLC side and get back to you.
You're right we test it. The HMI write the correct EventClear on the PLC Mode Handler Extension but internlly the PLC clear all events of the ModeHandler and even on the Mode Forwarder.
I'm very embarrassed 😔.
We found the root cause of this behaviour.
acknowButtonRTrig(Clk:=Module.Extension[ModuleInstIdx.FU1].EventClear OR Module.Extension[ModuleInstIdx.FU2].EventClear OR Module.Extension[ModuleInstIdx.FU3].EventClear OR Module.Extension[ModuleInstIdx.FU4].EventClear); EventClear := _acknowButtonRTrig.Q;
This was written in the code. I didn't find yesterday.
Sorry for make you lose time, and many thanks for your quick response and support.