Sign in to follow this  
aerdt

Radios dead on approach?

Recommended Posts

My radios and NAV died on me for the second time upon approach and I have no clue what could have caused this. The radios work just fine enroute and on final approach, everything dies on me. I cannot even change the frequencies anymore and my VOR/ILS don't ident or work.I am using the PMDG 737 with FS2Crew and FSInn - any ideas??Thanks a lot.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hi,That's a very strange issue. Does it happen every time?What key assignment do you have set for the Avionics Master switch?Also, I suggest that you try making a flight without FSINN and see if you can reproduce it.All the best,Bryan

Share this post


Link to post
Share on other sites

Well, I have learned from the FSInn forum that there apparently is an issue with radios/NAV and FSCopilot. I have uninstalled FSCopilot, but I still have the same symptoms.I really don't touch the keyboard during the flight, except for sending messages via FSInn and to arm the speedbrake (shift /). Very weird.

Share this post


Link to post
Share on other sites

Hi,Pls send me an email at:admin@fs2crew.comThanks,Bryan

Share this post


Link to post
Share on other sites

I thought there was a know problem with FSinn and Fs2crew not playing well together. I had weird problems, ditched FSinn and have had no problems since.Fsinn, was supposed to be patched, but I don't if it has yet.Darren

Share this post


Link to post
Share on other sites

FSINN caused serious problems when used with FS2Crew and the Level-D 767.As far as I know, FSINN resolved these issues in their latest patch.Cheers,Bryan

Share this post


Link to post
Share on other sites

My problem with the unresponsive radios/NAV has been resolved. It was my shortcut that I used as my VATSIM "push to talk" button.If you hold it longer than 8 seconds, it'll execute a Windows fix macro and FS/PMDG does not like that! I simply used another "push to talk" button and voila... no problems anymore.

Share this post


Link to post
Share on other sites

Thanks for sharing,I would never have thought of that one.Cheers,Bryan

Share this post


Link to post
Share on other sites

Update: It happened again and I do not have any clue why.... *boohoo*I was flying from KDEN to KPHX, wanted to switch radios for approach. Not working - dead! I tried flipping the battery switch on and off - nothing. No reaction at all. APU - on/off, negative. I did switch radios on my VATSIM flight a few times, but just after the "In Range" Checklist everything died on me. I will try a complete re-install.

Share this post


Link to post
Share on other sites

This is just a wild guess, but you might also want to take a look at your FSUIPC, perhaps update it or re-install it as well.Bryan

Share this post


Link to post
Share on other sites

Byran,I just completed another flight and the same thing happened again. Can you tell me what switches are being operated by the F/O after the "In Range" checklist until the final approach? Something happens after the "In Range" check list until I am ready to incept the localizer.I am sure, it is purely my fault, but I cannot locate the problem. I think it has to do something with the APU, bleed or general electric supply. I followed the instruction line-by-line and read everything a million times - everything seems to work, except radio tuning on approach.Thanks a lot!

Share this post


Link to post
Share on other sites

Hi,The things the FO does depends on what type of approach you are you flying.Precision ILS, Monitored Precision, Non Precision, Monitored Non Precision or Visual.See if you can reproduce it again, but this time leave the radio panel open and constantly change the nav frequencies until the radio goes dead and let me know:1. The type of approach you flying.2. The exact altitude at which the radios go dead.3. Your cruise Altitude.4. The TDZE for your arrival runway.I can't reproduce this issue, so it's really hard for me to say. I personally suspect it's an obscure PMDG or FSUIPC issue.Also, try making flights without using Squawkbox... maybe SB is causing this issue on your system? However, a lot of people are using FS2Crew with Squawkbox and have no problems, so who knows. Cheers,Bryan

Share this post


Link to post
Share on other sites

I also had FSINN installed and had problems with it. After I uninstalled the program I noticed that FSCo Pilot was still on themenu bar. I found the dll module in FS9 modules folder, but when I tried to remove it the file waas protected and would not leet medelete it. This could be the problem. I still can't get SB3 to work so I gave up oline flying until I get some answers. I have no problems when flying offline.

Share this post


Link to post
Share on other sites

Hi Skyhog,Best address that one to the FSINN support people.You may have load Windows in safe mode to get rid of that dll.Cheers,Bryan

Share this post


Link to post
Share on other sites

Hi Bryan,I just flew my PMDG 737-700 with FS2Crew again and, guess what? It happened again. I was flying an offline precision ILS approach at KCLE (cruise alt FL320, TDZE was 791ft). Shortly after the in range checklist, in between passing the transition altitude and the landing announcement, the FO does *something* that cuts power to the radios and ATC.Once I flip the battery switch manually, everything is back.Any ideas? This is a squeaky clean install without FSInn.Thanks,Pat

Share this post


Link to post
Share on other sites

Hello Pat,I don't know what more I can say I'm afraid. Whatever is causing this strange phenomenon is not in the FS2Crew code or everyone would experience it and you'd see ten posts a day on the subject.I thought you had it working before after changing your keyboard assignment for the Vatsim push to talk button?All I can suggest is that you take another look at your FSUIPC settings. I suspect the problem is somewhere in your FSUIPC/PMDG. All the best,Bryan

Share this post


Link to post
Share on other sites

Hi Bryan and thanks for being patient with me.I did another flight yesterday and I am sure that it is just something that I have been doing wrong and I am trying to pinpoint it as accurately as I can.Everything works great, until I start the approach. Shortly after the "In Range" checklist and after passing the transition altitude, the F/O seems to shut off the APU or does 'something'. He annouces the transition altitude and wham: no ATC, no electrical supply. What is it? It's gotta be something that is coded in FS2Crew. I'll look more closely again tonight. Once I start the APU again and bring APU Gen and then the Engine Generators online, everything is fine.I follow everything in the checklist to the line. Start APU, bring APU GEN Online, APU Bleed On, Engine Bleeds Off, Isolation Valve Auto - the rest is handled by the F/O. After starting the engines, I bring the Engine Generators online. During taxi the F/O asks me, if I want to shut off the APU and usually I do tell him to. After that, I am not touching anything APU/Gen/Bleed related anymore and pretty much don't touch the keyboard, except for joystick assignments for flaps, views, speed brake arm and gear. Maybe I am missing something!?I re-installed FSUIPC, the PMDG (after PMDG removal) and FS2Crew. Pretty much everything is standard here.Thanks a lot.Pat

Share this post


Link to post
Share on other sites

Hi Pat,It's not coded in FS2Crew or, as I say, everyone would have this problem.What other addons are you running, and are you changing window modes (full screen to window mode, etc) during the flight?Try this: Make a flight without FS2Crew and see if you can reproduce the problem.If you can reproduce the problem, make a flight with FS2Crew but leave the overhead panel open right before the Trans Level, run the In Range checklist, and see if any switches get moved on the Overhead.Cheers,Bryan

Share this post


Link to post
Share on other sites

I'm running some other add-ons: Flight Keeper, ASV, Ultimate Traffic, Ultimate Terrain, Flight Environment, Active Camera, FS Genesis Landclass, aiport add-ons, FSPax (hmmm, that's all I can think of). I haven't installed Ivap or FSInn after the re-install yet. Sometimes I do switch from fullscreen mode to windowed to bring up my VAs ACARS for messages (although I could just to get it displayed).Without FS2Crew, everything works fine. I'll look again tonight and look closely, if I notice something in the overhead. I am sure, it's just a trivial error on my end or, as you said, everyone else would have the problem. I just have not been able to pinpoint it. ;-)Thanks again!

Share this post


Link to post
Share on other sites

Hi,Try doing a flight but make sure you don't alt-tab. Don't switch window modes. Try that.Bryan

Share this post


Link to post
Share on other sites

Well, I completed a successful flight without any abnormalities. The problem, so it seems, was a weird assignment for the "avionics" switch. It was initially empty. I suspect the setting got somehow corrupted. I set it to some exotic key combination before the flight and everything worked perfectly. ;-)Thanks, Bryan, for all your help.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this