-
Nice to have the TBM850 and love it !!
Just an issue regarding the GNS530 and the Flightsim Builder GNS530 hardware
The "PROC" and "CDI"buttons work fine in the cockpit but not with my "PROC" and "CDI" buttons on the flight sim builder GNS530
not a big issue.
For info it work fine with the F28 or other aircraft with GNS530 so may be just something to activate somewhere...
Thanks
Pascal -
@pap This might not be useful at all (and you might have resolved your problem already). I don't have the Flightsimbuilder version of the GNS530, but do have the RealSimGear one. I just set it up to work with Spad.next and manually assigned all commands to it. The TBM uses only the default Asobo assignments, and it works perfectly for me. So it could be a FSB assignment issue? I'm not sure how the software works for the command mapping compared to RSG.
-
@paintedfloors thank you. I will give it a try
-
@paintedfloors Well the Asobo command for the AS530 did not work for me.
The PROC button is the only one which does not work on the FSB GNS530 where it works for any other aircraft with GNS 530 equipped...
I sent a message to FSB support and wait for their answer ;-)
Thanks anyway
Pascal -
Hi All,
I seem to recall hearing about this issue in my King Air, which is my other aircraft that uses dual 530's. I'm not sure why only some of the buttons would work, but I believe the problem with the default bindings is that when there is one 530, it is named "AS530", while when there are two, they are named "AS530_1", and "AS530_2". This means that ">H:AS530_CDI_Push", becomes ">H:AS530_1_CDI_Push" for the first unit, and ">H:AS530_2_CDI_Push" for the second unit. Whatever causes the problem, I know we sorted it out for the users in the past. If that does not work for you, please contact JF tech support, and they can use their knowledge database to find the solution that worked in the past.
Hope that helps,
Nick C.
