stevegreenspan

Hi Jean-Luc, Thank you for your response. After wandering through many posts regarding this issue, I found a user's solution that worked, although I am baffled as to why this needs to be done to get the Turbo Arrow to recognize the flight plan in the GTN750 and follow it. A user posted that after selecting the Turbo Arrow and airport in X-Plane and loading it in the simulator, then immediately selecting Developer, Reload Aircraft right before turning anything on in the cockpit, everything going forward for the flight using the GTN750 works well, and the aircraft follows the entered flight plan after switching to NAV. I'm not sure why this occurs but its a work-around to get the Turbo Arrow to recognize the flight plan and use GPS navigation. Works great after doing the above sequence at the beginning of the flight. Thanks again. Steve

Greetings, Forgive me for being a newbie with RXP and the GTN 750. I've been flying the Just Flight PA28 Turbo Arrow for X-Plane for some time now and am very familiar in operating it. I decided to "upgrade" and move to the GTN 750. I purchased and installed it, and it fit right into the panel with no issues. After doing some Garmin training and watching videos of others, I was able to create flight plans and procs within the 750. I also performed a couple of flights using the GPS, which followed the flight plan and thought all was well.... until it wasn't. Something happened and now I cannot get the Turbo Arrow to engage and start following my active flight plan. I am not sure if there is something wrong in my settings for the GTN 750, my flight plan or if the issue is with the Turbo arrow itself. I need some advice and guidance for anyone familiar with the Turbo Arrow and GTN 750 integration. 1. Just Flight Turbo Arrow 1.8.1 2. Reality-XP GTN 750 2.5.29.0 3. On the GTN 750, flight plan is active and fully displayed on the map, with waypoints and airport endpoints. GPS is active, displayed at the bottom. 4. On the Turbo Arrow panel, AP is switched on, HDG is switched on (per other posts), selector is full left on NAV. Yet the aircraft does not engage when NAV is switched on, and I cannot go direct to a waypoint. I'm not sure if I'm doing something wrong or if there is an inherent issue with the Just Flight Turbo Arrow itself, as I saw in posts from last year. Any assistance is greatly appreciated..... Steve

Hi MySound, Is it the FS2Crew Command Center or the FS2Crew Product Manager that opens up on Windows start? Steve

John, After releasing the parking on the CRJ, can you visually confirm that the parking brake was actually released (lower pedestal)? I had this issue early on due to another binding on my keyboard for the parking brake that keeping it set on. What happens if you use the mouse and cursor to release? You mentioned that chocks were removed. Visual confirmation from camera view outside? Steve

Great! Thanks Bryan! S.

I also should have mentioned, I don't know why the cockpit camera did an immediate "Look Right" after I pressed the secondary button for GA. That was uncommanded. Steve (Disregard: that was commanded, a conflict in my keyboard settings...)

Continued from above,,,, Flaps did go to 3, from Full. I had to take over manually and start bringing gear and flaps up, as there are no button options to raise either. I got some overspeeds since I was trying to figure out everything. Steve

Glyn and Bryan, Happy Holidays to you both.... After a couple of attempts to find the issue for the AP1 turning off at Go Around, I finally got it to fail, and confirm that there is something going on, possibly in my procedures or possibly in the A320NX itself. Again, I use Voice Control primarily for my flights and never Button Control, so I had to reintroduce myself to Button with a few practice flights. I was able to figure out how to record videos, but my results were sort of blurry, so apologies. What's interesting in the video is that upon engaging Go Around with the secondary button, I heard Manual Flight called out and the AP1 turned off. I did not press to disconnect. (Continued next post...)

I will see what I can do. I haven't created or posted videos, typically only screenshots. Steve

Glyn, Can you try using a different secondary key mapping to see if the issue follows to the new key. I think you mentioned that you use "M" now for secondary. See if we can isolate this.... Steve

I heard the FO speak at the initiation of the GA although the higher engine noise on my speakers drowns him out, so not sure what was said, assuming the start of the GA process. In any event the Go Around followed the steps above successfully although I had to manually retract the flaps in stages through the sim itself and not on my hardware. I do have hardware for flaps, the Thrustmaster TCA quadrant and addons. However they are not used for the A320NX since the FO controls flaps on my command using Voice Control. I did not disable them in the settings for Button Control since I was not aware that I may have had to do that, hence the reason there may have been a hardware conflict and no flap retraction. My testing and results using Button Control show that in my configuration, the AP and AT remain on during the Go Around process. Steve

I tried the same approach using Button Control. I'm a Voice Control guy, so I am a bit rusty in using Button, but was successful for the entire flight On approach I went to GA using the mapped secondary key and it followed the GA procedure to start the level off and then climb at TOGA. AP stayed on. However flaps stayed at Full, expected the FO to move to Flaps 3 .

I'm using Voice Control so there is a difference there, no other hardware inputs from me other than pushing the throttles to TOGA manually and then back to LVR CLB. I am using the Thrustmaster TCA pack as well. The FO moves the flaps up one notch, from Full to Flaps 3. Do your hardware bindings for the GA and TOGA have any other flight control selections, such as trim? Steve

Glyn & Bryan, I attempted to reproduce this issue by simulating the same approach into Manchester runway 23R, as Glyn had shown in the video. I am not having the issue with the AP turning off during the Go Around procedure. AP1 only was on during approach (No AP2 autoland). At minimums called for Go Around Flaps Manually moved throttles to TOGA FO moved the flaps up one notch Called for landing gear up Aircraft leveled and accelerated to climb Throttles to LVR CLB Climbed to missed approach altitude and leveled off Sidestick was not moved during the procedure. The Go Around process in FS2Crew operated perfectly and I followed the missed approach path for another landing attempt, successful. Result: AP1 remained on the entire missed approach procedure. Glyn, I cannot reproduce this. What was different in your steps, if anything? What hardware are you using for throttles? Steve

I'll download the new Product Manager and retest. Much appreciation.... S.