OpenFMB uses separate profile for "status" vs events. The DNP3 plugin was using clearing events when it was "integrity" scanning and events were being missed.
Now, the default in the configuration is to have no startup integrity scan at all, and then have separate static data vs event scans.
The user can choose to enable unsolicited mode, or configure an event scan.
This modifies the schema for the dnp3-master plugin so be sure to regenerate it and fix the differences in VS code.
OpenFMB uses separate profile for "status" vs events. The DNP3 plugin was using clearing events when it was "integrity" scanning and events were being missed.
Now, the default in the configuration is to have no startup integrity scan at all, and then have separate static data vs event scans.
The user can choose to enable unsolicited mode, or configure an event scan.
This modifies the schema for the
dnp3-masterplugin so be sure to regenerate it and fix the differences in VS code.