MGL Avionics User Forum

Hi I have those 2 problems,
When I power up both Challenger instruments I have all those alarms related to the engine, I acknowledge those alarm on the active screen but they continue to flash on the inactive screen, I have to acept them on that inactive screen also. Is it normal or acknowledging one place should be OK.
Also I have a V16 radio connected to the IBOX and on the active screen it show as COM1 and I can control it from that screen, on the inactive screen the COM1 is shown with a red X above it but I can rotate my buttons to radio control and I can adjust my radio just fine from the inactive screen even if there is a big red X above the COM1 small window. Is there a way to clear that big red X from the COM1 window on the inactive screen.

Thanks
Sylvain April

ensure that both screens have the same setup for your com radio in your serial port routing and setup menu.
Alarms have to be accepted separately. This is due to each screen having private alarm triggers so it is possible that alarms are dedicated to a particular screen.
However it so happens that the next update actually will allow acknowledging alarms across panels - also in case you have one of our intercoms connected you will be able to control the intercom from any panel.

The reason you can change the radios frequency from the inactive panel is that the panel requests the master to change the frequency but as it does not seem to know what kind of radio is connected where it will show you the red cross as it is not receiving anything from the radio.
So if you have selected a MGL radio on say serial port 3 on the active panel then do the same on your inactive panel. Your inactive panel needs to know that anyway in case it becomes the active panel.

BTW, you can broadcast your entire setup to the inactive panel if you like - before you do that from the broadcast menu make sure you select on your inactive panel what kind of setups it is allowed to accept.

Thanks Rainier,

I will set the serial port correctly and will watch for next update for the acknowledge function, although it is not a problem really.

Regards
Sylvain