The rate at which the DASU publishes its output when it does not change is taken for the refresh rate of the IASIO that the ASCE produces. The rates of the IASIOs produced by all other ASCEs running into the DASU are ignored but must be written in the CDB.
To simplify the editing of the CDB we could make the refresh rate of the IASIOs option and assign a refresh rate to the DASU.
A very similar problem is in the configuration of the plugin (now only possible on JSON): each moitor point value and alarm produced by the monitored sytem and sent by the plugin to the core has a assigned refresh rate.It would be probably enough to assign a derired refresh rate to the plugin and, if it is the case, allow a different refresh rate for selected monitor point values and alarms.
The rate at which the DASU publishes its output when it does not change is taken for the refresh rate of the IASIO that the ASCE produces. The rates of the IASIOs produced by all other ASCEs running into the DASU are ignored but must be written in the CDB. To simplify the editing of the CDB we could make the refresh rate of the IASIOs option and assign a refresh rate to the DASU.
A very similar problem is in the configuration of the plugin (now only possible on JSON): each moitor point value and alarm produced by the monitored sytem and sent by the plugin to the core has a assigned refresh rate.It would be probably enough to assign a derired refresh rate to the plugin and, if it is the case, allow a different refresh rate for selected monitor point values and alarms.