I use the Wingman Profiler. It has been a long time (January) when I set it up and to be honest I don't recall how I was able to map the commands from the keyboard to the buttons. I think I called Logitech tech support during working hours and a rep walked me through it.

The commands I have mapped to the stick are as follows:

Button 1: Trigger
Button 2: Bomb and Rocket Release
Button 3: Used as shift button
Button 4: Target Closest Enemy
Button 5: Target Closest Ground Object
Target Next Enemy (Shifted)
Button 6: Target Next Ground Object
Target Previous Enemy (Shifted)
Button 7: Deselect Target (Escape Key)
Button 8: Flaps Up
Pilot Map (Shifted)
Button 9: Flaps Down
Landing Gear (Shifted)

POV: I created a file EAW POV with front, left, right and rear views with snap views to the NE, NW, SE and SW to take advantage of the eight-way hat switch.

I found two benefits of this method with EAW.

First of all, the button mapping is recorded into the EAW ini file which makes it easy to save my settings if I decide to reinstall EAW. I have done several times, moving it to different locations on my hard drive (or even a different computer). I just drop my backup copy of the EAW.ini file and at least my button mapping is ready to go. Its a lot of work to go through all the button mapping again.

With the Wingman profiler, I have to do all the programming again if I move a game to a different location (a different partition or even another hard drive) as the Wingman profile is linked to the exe file of each game. I have not managed to find a way to change the link in the profile. If there is an easier way to do this, someone please enlighten me.

The other problem I found using both the Wingman Profiler and the Sidewinder Profiler is that if I program a command such as "look behind" (check six) on the hat switch, a "identify target" command programmed into a stick button wouldn't work as long as the hat switch was toggled back. For some reason, this particular command was blocked. I could still padlock with the keyboard but I like to have everything on the stick.

By letting the EAW profiler to handle all the commands, I don't get any conflicts.

I try and program all my flight sims to use the same buttons for similar actions.

Programming Zoom in and Zoom out buttons really enhances the view of the planes taking damage and make sure you put a "lap view" button somewhere so you can glance down to watch your temperature gauge and artificial horizon (handy in a spin when in the clouds) even if you are "no cockpit" view. Let go of the button and your view snaps back up to whatever view you had before looking down.