Right now there's no way to change the FiO2 and flow rate alarm limits in the firmware, from a frontend action. The alarm limits are locked at the maximum possible range for those values, so alarms should never trigger. What we actually need is to automatically change the alarm limits to be some tolerance range around the FiO2 and flow rate parameter settings; whenever the parameter settings change, the alarm limits should be updated. This could be done either from ParametersService (not elegant) or from AlarmLimitsService (better, but could there be some kind of synchronization issue? Maybe not, if we can guarantee the AlarmLimitsService always runs immediately after ParametersService and before parameter updates are actuated by the valves; I think we can make this guarantee).
Right now there's no way to change the FiO2 and flow rate alarm limits in the firmware, from a frontend action. The alarm limits are locked at the maximum possible range for those values, so alarms should never trigger. What we actually need is to automatically change the alarm limits to be some tolerance range around the FiO2 and flow rate parameter settings; whenever the parameter settings change, the alarm limits should be updated. This could be done either from ParametersService (not elegant) or from AlarmLimitsService (better, but could there be some kind of synchronization issue? Maybe not, if we can guarantee the AlarmLimitsService always runs immediately after ParametersService and before parameter updates are actuated by the valves; I think we can make this guarantee).