V16 stuck on AWIS frequency

The expanding range of MGL's innovative RF avionics
Forum rules
Please keep your posts friendly and on topic. No politics or discussions of a controversial nature not related to our favorite subject of flying and avionics. Offending posts may be removed or moderated.
Post Reply
paulvs
Posts: 11
Joined: Mon Feb 15, 2021 4:25 am
Location: Western Australia

V16 stuck on AWIS frequency

Post by paulvs »

The V16 gets stuck on the frequency when listening to the Automated Weather Information Service broadcast, even when both the active and standby frequencies are changed to a different frequency. The only way that I've been able to get the radio to switch away from the AWIS frequency is to transmit on another frequency. Anyone else have this problem?
Building Vans RV-6A and flying Aeroprakt A-22 with V16/Vega. Still thinking about avionics for the RV.
Tasmag
Posts: 63
Joined: Wed Sep 09, 2020 6:23 am

Re: V16 stuck on AWIS frequency

Post by Tasmag »

I have had this happen a couple of times, one trigger seems to be flipping the channels while scanning and the primary was receiving a broadcast.

Mike
paulvs
Posts: 11
Joined: Mon Feb 15, 2021 4:25 am
Location: Western Australia

Re: V16 stuck on AWIS frequency

Post by paulvs »

Thanks Mike.
I just noticed that there was a firmware update 100719 (V1 REL 10) that "Improved scanning behavior if new frequencies pushed while scanning". I wonder if that update will fix the problem? The firmware in my V16 is version 151018 (V1 REL 6) which is older than the above.

I would need to make a special harness and partially disassemble the panel to upload the firmware, so it's not so easy that I would just try it without being relatively certain that it will be an improvement.
Building Vans RV-6A and flying Aeroprakt A-22 with V16/Vega. Still thinking about avionics for the RV.
Tasmag
Posts: 63
Joined: Wed Sep 09, 2020 6:23 am

Re: V16 stuck on AWIS frequency

Post by Tasmag »

I have the latest firmware, except for the one released a couple of days ago.

I haven't noticed it happen lately so I suspect the update did improve that particular problem.

Mike
Post Reply