PilotsDeck/StreamDeck Profile for Fenix A320
Here are the StreamDeck Profiles I use with my PilotsDeck Plugin for the Fenix A320.
It has all the usual Buttons/Switches/Korries from the Overhead, MIP/Glareshield, Pedestal, FCU (working Displays), MCDU (with Full Keyboard) and DCDU to support normal Flight Operations without touching the Mouse! (Including the GSX Menu on your StreamDeck)
They are designed for my SD/XL/Plus Setup:
- MSFS-Fenix320 => The SD Profile which only has supplementary Functions: Changing Views, Monitoring/Calling GSX, UTC Clock and the XPDR
- MSFS-Fenix320-Plus => SD+ Profile with mostly everything that makes Sense to control via the Encoders: FCU, EFIS, Radio, ACP, WXR, Display-/EFB-Brightness, Lights
- MSFS-Fenix320-XL => The XL Profile with all Functionalities. Besides specific Folders for the different Panels/Areas it has Folders for the different Flight-Phases with the most critical/common Controls needed for that Phase.
That means you need at least the StreamDeck XL (or SD+) to get any Use out of it. Please don't ask for SD-Only Profiles - it just got too much to maintain. But you can still use the Plugin and the other Files from this Package to build your own SD Profile customized for your Needs!
The Profiles are for your own and private Usage. You are not allowed to republish / reupload them or any other Package-Content anywhere. The Lua-Scripts can be considered MIT Licensed though (only them, nothing else).
The Package contains the following:
- The mentioned Profiles as .streamDeckProfile Files
- Lua-Files to Control the Fenix & GSX as well as reading some Values from them
- The custom Images used in this Profile (Credits & Thanks to Guenseli)!
- The FenixQuartz Binary required for the Quartz Displays (FCU, Radio, XPDR, ISIS, Rudder, Batteries) to work
Requirements & Setup
Requirements:
- You need to have at least Version 0.7.8 of my PilotsDeck Plugin installed & running
- The Profiles require the Fonts "Digital 7" and "Alte Din 1451 Mittelschrift" installed on your System - you can find them freely in the Internet
- You need a registered (purchased) Copy of FSUIPC7 for all Buttons/Function to work (most should work without)
- Tested with / Designed for Fenix 2.0.0.407
Installation:
- Copy/Extract the Images to the Plugin: %appdata%\Elgato\StreamDeck\Plugins\com.extension.pilotsdeck.sdPlugin\Images
- Double-Click the Profile Files to install them. Make sure to select the correct StreamDeck first in the UI before installing the corresponding Profile (if you have more than one StreamDeck).
- Place the Lua-Files in your FSUIPC7 Application Folder (the Path where you've installed it).
- Check/Change the Path in the GSX_AUTO Script to your Addon Manager Folder!
- Install FenixQuartz. It is recommended to let it setup Auto-Start.
- Setup the Automatic Start for the Lua-Files in your FSUIPC7.ini (make a Backup before editing it).
You can also start the Scripts manually when the Fenix is loaded if you prefer that for any Reason. Make sure the Binary is started with the same Elevation as MSFS!
Note for Upgraders: Note for Upgraders: the myOffsets.txt and GSX_AUTO_FNX.lua Files are not needed anymore and can be deleted.
Automatic Start for Lua-Files:
First you have to start FSUIPC (and close) once so that FSUIPC will add the Lua-Files to it's Configuration. (You can of course add them manually, IF you know how to do that)
IF you have a FSUIPC Profile for the Fenix and it is called "FNX320" as an EXAMPLE, you would need to add the following to your FSUIPC7.ini:
[Auto]
1=Lua GSX_AUTO
[Auto.FNX320]
1=Lua FNX320_AUTO
2=Lua FNX320_SYNC
If your Profile is named differently, change the [Auto.FNX320] to the correct Name.
IF you don't have a FSUIPC Profile for the Fenix (or just don't know what that is), you would need to add the following to your FSUIPC7.ini:
[Auto]
1=Lua GSX_AUTO
2=Lua FNX320_AUTO
3=Lua FNX320_SYNC
Whatever you do, ensure the following: each [Auto] and [Auto.XXX] Section can only exist once. If you already have such Sections, add these Lines to the exisiting Sections. The Number assigned to the Scripts do not matter, but ensure each Number exists only once (in the corresponding Section).
GSX_AUTO - Addon Manager Path:
In order for the Script/Profile to work, you need the check/configure the Path to your "Addon Manager" Installation (where GSX resides). Edit that Line with your real Path in the GSX_AUTO.lua File:
local GSXAUTO_CFG_PATH = "X:/YOURPATH/Addon Manager"
Your Path has to be in the same Way: using Forward-Slashes ( / ), enclosed as String ( " ), must end with the Addon Manager Folder without a trailing Slash.
Setting up the Views:
The Buttons to change Views are based on the vJoy Driver - you can only use these if you have installed that optional Plugin Dependency (manually).
They are mapped to Custom Cameras in MSFS. Map the vJoy Buttons to the "Load Custom Camera" Bindings and Save/Create your Custom Cameras for the respective Button/View (CTRL + ALT + Number). If you already have Custom Cameras defined for the Fenix, map the vJoy Buttons accordingly and/or change the Mapping in the Profiles which Button is triggered.
The preconfigured Mappings are:
| vJoy Button# | Mapping in MSFS | Title in Profile |
| 1 | Load Custom Camera 1 | Captain |
| 2 | Load Custom Camera 2 | Overhead |
| 3 | Load Custom Camera 3 | Pedestal |
| 4 | Load Custom Camera 4 | ECAM / MIP |
| 5 | Load Custom Camera 5 | MCDU |
| 6 | Load Custom Camera 6 | EFB |
| 7 | Load Custom Camera 7 | Eng L (Passenger, front of Engine) |
| 8 | Load Custom Camera 8 | Eng R (Passenger, front of Engine) |
| 9 | Load Custom Camera 9 | Wing L (Passenger View, behind Wing) |
| 10 | Load Custom Camera 0 | Wing R (Passenger View, behind Wing) |
| 11 | Toggle External View | External |
| 12 | Toggle Cockpit View | Cockpit |
FNX320_SYNC
The Script synchronizes the FD-Buttons for both Captain and FO (the FO Side will be set to the Captain Side). If you don't want that, set FNXSYNC_FD_SWITCHES to false on the Top of that File.
FNX320_AUTO
The Init-Function (the "INIT" Button in the GSX Folder) of the Script can be configued on the Top of the File. You can enabled/disable if EFB, Displays, Interior Lights, ACP1 or the Brake are configured through that Function.
For the Brake-Sync to work, you need to set the correct the Joystick- and Button-Number (according to FSUIPC) which is bound to the Parking Brake. Only works on Buttons like on the TCA (constant on or off).
Usage
I hope/think most Buttons should be self-explanatory. They are generaly configured in such a way to trigger the most common Action in the respective Phase. If applicable, they have a long Press for Off, Reset or a second Key. Some Notices:
- The (3-State) Light Switches behave differently depending on Folder
- On "Gate" they are toggled between Low- and Mid-Position.
- On "Taxi" they toggle from Low > Mid <> Up (so they can quickly be triggered when entering/leaving the Runway). A long Press will set to Low.
- On "Flight" they toggle from Low <> Up (so full either full on or off). Except the Strobes ;)
- The Fire Test, CVR Test and TO Conf Buttons are "Hold Switches". So you need to press and hold them as you would do with the Mouse.
- The FCU-Displays are also Buttons. They either toggle between Managed/Selected (normal Press) or toggle things like SPD/MACH, HDG/TRK, Alt Scale (long Press). The VS Display/Button is Pull (normal) or Push (long). On the SD+ Managed/Selected is on pressing the Encoder and the other toggle Functions on the Touch-Display.
- The SD+ has different Pages. You can use the Buttons to navigate between them, or use the Swipe-Feature to go to the next / previous Page - for Example for a quick Switch from FCU to Radio or FCU to EFIS.
- The Radios on the SD+ are done with Encoder-Stacks: Push the Dial to switch between Outer and Inner Knob (a ">" or "<" denotes the current Knob). Tap the Touch-Display to swap Frequencies. (Turn -> Press -> Turn -> Tap)
- The MDCU Menu Keys have long Presses: "INIT DATA" for Example will select the INIT-Page on a normal Press and the DATA-Page on a long Press. The "AOC" Button is a little Key-Sequence which directly takes you to the AOC Menu.
- Generally on other Multi-Position Switches the normal and long Press either are mapped to the different Directions (e.g. normal is UP/ON, long is DOWN/OFF) OR the Action automatically toggles between the usual States.
- Some ECP Buttons in the Phase-Folders have long Press Assignments for other Pages or STS/RCL.
The Usage of the GSX Menu / Buttons is described here.
The only Thing additional in the Fenix Profile is the "INIT" Button. This Button will powerup the Plane and setups the Cockpit:
- Batteries & Ext Power ON
- Hides both EFBs
- Sets Integral, Flood and Dome Lights
- Sets all Displays to 80% Brightness
- Configures ACP1: VHF1 + INT to 100%, CAB+PA selected
- Syncronizes the Position of the Parking Brake to match the Joystick
Additional Notes
FNX320_AUTO
This Script contains the Functions addressed by some Actions in the StreamDeck Profiles, it is essential for some StreamDeck Buttons to work. Some Functions are not used in the Profile (like Engine Masters) - I'll use them for my Thrustmaster TCA.
They are addressed via "LuaToggle:FNX320_AUTO:NUM" in PilotsDeck (or "LuaToggle FNX320_AUTO" with NUM as Parameter in the FSUIPC UI). Which NUMber maps to which Function can be found at the End of the File, if you want to use these Functions for own Buttons or FSUIPC-Mappings!
FNX320_SYNC
This Script is essential for some Buttons / Displays from the StreamDeck Profiles to show their State / Value (Gear Indication, Baro, Landing Light).
The Script (and the Binary) use the FSUIPC Offsets at 0x5400/0x5500 and above to generate Informations for some Buttons - if these are used by some other Addon you have to change them in the Lua and the Profile (and the Configuration File of the Binary). This Offset-Range is normally associated with PMDG/Project Magenta - so it should be safe in most Cases!
GSX_AUTO
The Script is used to integrate the GSX Menu on the StreamDeck and automate some Tasks/Questions in GSX and you only need that if you own GSX. The GSX_AUTO Script is not tied to a specific Aircraft, it can also be used with GSX for other Aircrafts! Don't worry if you use Fenix2GSX: the Script disables Automations for the Fenix.
For a detailed Explanation on its Function / Usage check: https://flightsim.to/file/54256/pilotsdeck-streamdeck-profile-for-gsx-pro
The Script uses FSUIPC Offsets 0x4300 through 0x4533, if theses are already used by something else in your Setup, configure a new Base-Address! Don't forget to change the Addresses in PilotsDeck after that!
FenixQuartz
Quartz uses mostly (99,99%) native Fenix L-Vars now. It is still required for this Profile so that even Users without a registered Copy of FSUIPC can have working Displays.
The Binary can be used with other 3rd Party Software, it is not tied to my Plugin or these Profiles. Check its GitHub Repo for more Information.
1 months ago
1 months ago
Fragtality
EisernUnion
Yes, FenixQuartz is now in version 1.5.
With all the software updates and address changes, I'm having a hard time fixing this SD+ application for the Fenix.
For radios, I've identified new addresses and other factors that become :
COM1
were :
active: 0x5452:8:s STBY: 0x5433:8:s
become :
active: 0x05C4:4:i STBY: 0x05CC:4:i
scalar: 0.000001 Format: 3:%s and 3:%s<
COM2
were :
active : 0x5462:8:s STBY : 0x545A:8:s
become :
active: 0x05C8:4:i STBY: 0x05D0:4:i
scalar: 0.000001 Format: 3:%s and 3:%s<
It works, I modify the frequencies and their positions using the encoders in MSFS but not on Stream Deck+unless I swap active/Stby.
1 months ago
1 months ago
Fragtality
PhMI
Now, the buttons and encoders on the Fenix model work, but the value display on Stream Deck+ (FCU, EFIS, RMP) no longer does.
1 months ago
1 months ago
Fragtality
PhMI
2 months ago
2 months ago
Fragtality
YangHS
Sounds like the Fenix A320 Block 2 will include some very similar GSX automations so I wouldn't be surprised if they borrowed them from you.
Thanks 😀
2 months ago
2 months ago
Fragtality
sgmess
merci
3 months ago
3 months ago
Fragtality
fullenwarth
4 months ago
4 months ago
Fragtality
vrouleau
4 months ago
4 months ago
Fragtality
Sysrek
5 months ago
5 months ago
misc
SeptemberWasp
I have just one minor problem, which may or may not have something to do with the profile, but the problem started after I installed it (Sorry if I am barking up the wrong tree!):
During and after pushback with GSX:
After releasing the parking brake, the "Interrupt pushback" menu pops up, and after setting the parking brake, the "Interrupt pushback" menu pops up again. When the "Have a good trip" message finally appears after pushback, the "Select parking at ..." menu pops up.
None of these happened before I installed the profile. Could those "pop-ups" have something to do with it?
5 months ago
5 months ago
Fragtality
misc
8 months ago
8 months ago
Fragtality
ThrottleHold
8 months ago
8 months ago
Fragtality
vanislepilot
But I still have the following problem:
Settings the airpressure with the baro-knob on the streamdeck-plus is not synchronized with the Fenix. Does someone have an idea what could be the reason and how to solve this problem?
8 months ago
8 months ago
Fragtality
Bratwurstflyer
I have just one problem what i could not solve.
It's about the landing lights... in all 3 places ( Taxi and Flight) the "LAND" switch is not working.
9 months ago
9 months ago
Fragtality
kwieser76
Could someone make an installation video for this? It's all a bit confusing for those of us new to FSUIPC.
11 months ago
Which Step exactly confuses you?
11 months ago
Fragtality
NZLighting