You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding a way for FGw to handle annunciation messages has been talked about.
There is a lot more to this than it first seems. How do we deal with intermittent conditions? Do we allow overrides? Which program determines when settings have been exceeded (i.e. Low Oil Pressure?) Or do we just make it a message handler? Do we tag messages into groups (engine alarms could be separate from system alarms) or is that too complex for an airplane?
Personally, I think it need not deal with what actually causes an alarm/warning condition rather deal with distribution, clearing and logging of the messages. Let the devices or plugins that are closer to the problem determine what is an alarm and what isn't.
The text was updated successfully, but these errors were encountered:
Adding a way for FGw to handle annunciation messages has been talked about.
There is a lot more to this than it first seems. How do we deal with intermittent conditions? Do we allow overrides? Which program determines when settings have been exceeded (i.e. Low Oil Pressure?) Or do we just make it a message handler? Do we tag messages into groups (engine alarms could be separate from system alarms) or is that too complex for an airplane?
Personally, I think it need not deal with what actually causes an alarm/warning condition rather deal with distribution, clearing and logging of the messages. Let the devices or plugins that are closer to the problem determine what is an alarm and what isn't.
The text was updated successfully, but these errors were encountered: