One for the wishlist: Modern radio stack
-
@Martyn Really glad to see you're picking up the GTN750 development!
I wonder what was the consideration to put the GPS 100 aside of it.
Doesn't seem like a useful stack to me and I'd rather like to have the setup like the GNS530 and either a larger GTN750 screen (not sure if they are built larger) or simply a cover for the bottom slot which otherwise is occupied by the transponder.Anyway, looking forward to try it out. :)
-
Same here, very excited to see the GTN750 in the Piper :)
-
It does look very nice but a little odd. You've spent a lot of money getting a GTN750 installed but have penny pinched on leaving the old nav/com 2 radio and ADF :) Would be cool to have the option of more modern units to go with the GTN.
-
@FrontSideBus Yeah, i'd rather get a GNS530+430 stack than a single GTN750 with those antique radios...
-
Best thing imo is to have different options as there are different tastes and preferences out there... for me, to have the old radios plus old GPS is absolutely OK, but I prefer to go with the GNS530 option (modded, of course)... If they come up with a GTN750 option I will rather go with it for sure, and I could maybe switch back to the GNS530 if I could have the option to pare it with a 430 as secondary NAV/COM...
I personally prefer to have modern systems in an old airplane than flying with vintage, old looking instruments... but sure thing there is a lot of people out there that prefer just the opposite... the more options Just Flight is able to offer the more people is going to be potentially interested in their products...
-
@RaulKO For me the perfect combo is the 530+430. The 750+650 are a bit too modern for my tastes. I see why people like them, they have a very easy to use touchscreen interface. But the GNS dual combo gives me all the functionailty i need in a pretty cool package. That's one of the reasons i made the suggestion above. The second is that it seems to me to be the easiest way of adding a relatively modern avionics stack in the Arrow. Both the 530 and the 430 are already modeled in cockpit. I think that all JF needs to do is change some configuration files and make some changes to the EFB. It's probably more complicated than that, but i would have thought it's easier than modelling the 750 and the 650. Either way, it looks like they already modeled the 750, so that's pretty good. I hope they do manage to add the 530+430 option too.
And yeah, i agree. The more options, the better.
-
@Cristi-Neagu good point... I also think that GNS530+430 integration should not be complex in terms of development, considering JF already have them working separately. They should probably need to re-arrange and provide a new 3d cockpit panel layout for the new config, which should have the old COM2/NAV2 receiver removed as well as the new GNS Convo incorporated. Then link the 430 to COM2/NAV2 channels and add the new panel option to the settings pad. Some testing and it should be ready to go...
Probably the most difficult and time consuming job is to provide a new panel layout, since this requires to remodel the 3D mesh of the panel as there will be new 3D knobs in new places... also test how the two GNSs interact with each other and avoid any weird behavior...
Anyway something very feasible so I guess it is really up to Just Flight to do it or not.
Still, GTN750 is a superb alternative that I really look forward to try as soon as they make it available...
-
@Cristi-Neagu :party_popper:
-
@FrontSideBus said in One for the wishlist: Modern radio stack:
@Martyn Fantastic! Awesome!
Are all of these options also being applied to the upcoming Turbo?The Turbo Arrow will share the same configurations
-
I´ve just got v0.4.0 installed and selected the GPS:GNS DUAL option in the tablet menu (all systems offline but the tablet) and I got this error on GNS430 screen - it shows part of the GPS100 buttons as if it was behind the GNS430
-
@vcapra1 issue got fixed. It was a side effect caused by JF Piper Arrow Panel Lights with Uwa Lighting mod, a new version (1.0.4.0a) was released for v0.4.0 and got this issue fixed.