I am currently trying to map my buttons on mobiflight to control my upper panel with my Rowsfire A102. All attempts I have made to convert from the Fenix profile with the pushbuttons have failed(Although all switches and push button lights are working).

There is a preset for these events in the mobiflight software for APU Master and APU Start which works, however there are not any presets for any other button on the upper panel.

It was suggested that the preset code comes from the proprietary FS Labs WASM module and to contact FS Labs for help.

the preset codes are:

(>K:FSL.EVENT.OVHD.APU.MASTER.PUSH)

(>K:FSL.EVENT.OVHD.APU.START.PUSH)

 

Can someone help me find the info I need to create the preset codes for all push buttons so I can complete configuring?

Hi April, 

 

Please see here: 

 

 

More events are being added with every update. (The overhead will be complete with the next update we issue). 

Any timeframe on that? Its missing APU Bleed, Fuel pumps, Bat 1 and 2 push, and external power.

I'm interested to, just buy rowfire 106 but don't want use it with fenix 😁

I have an A106 v2 profiles for FS labs A321 neo

Working on A107 v2 this week.

Wow, could you share?

here is what I have so far for FS Labs A321neo. PWS is inop because there is no mouseract for it and FS labs has not released the K event for it yet. I am not an expert at this but should work.

Rowsfire A102 FSlabs A321-ovhd(PWS INOP).mcc Rowsfire-A106 V2.0-FSLabsA321-Micro OVH Panel Pro.mcc

working on A107 V2 now.

9 hours ago, April McDonald said:

here is what I have so far for FS Labs A321neo. PWS is inop because there is no mouseract for it and FS labs has not released the K event for it yet. I am not an expert at this but should work.

Rowsfire A102 FSlabs A321-ovhd(PWS INOP).mcc 42.94 kB · 0 downloads Rowsfire-A106 V2.0-FSLabsA321-Micro OVH Panel Pro.mcc 50.65 kB · 0 downloads

Thank You so Much!!!

Good News! I have made an A107 config!

Not so good news: Fire Test buttons for engines 1, 2, and APU are inop because there is no mouseract or input event available in behaviors under developer mode just like pws on my A102. This means we must wait patiently for FS Labs to release the next Hardware Interface Excel spread sheet and hope it is on there. 

Last I started using Beta version of Mobiflight so if this doesn't work consider to switching to Beta(I love it, much easier to diagnose problems with it.)

Rowsfire-A107 V2.0-FSLabs-Mini OVH Panel (FIRE TESTS INOP).mfproj

Remember that is for A107 v2 only. V3 has a separate operating profile.

Here are the Variables for Firetest Engine 1, Engine 2 and APU:

72236 (>K:ROTOR_BRAKE)
72240 (>K:ROTOR_BRAKE)
72244 (>K:ROTOR_BRAKE)

 

15 hours ago, Thomas Henke said:

Here are the Variables for Firetest Engine 1, Engine 2 and APU:

72236 (>K:ROTOR_BRAKE)
72240 (>K:ROTOR_BRAKE)
72244 (>K:ROTOR_BRAKE)

Thank you, Thomas. how did you get these if you don't mind me asking? Ctrl G did not show them for me and I looked everywhere.

Here is my complete A107 v2 config file, enjoy! 

Rowsfire-A107 V2.0-FSLabs-Mini OVH Panel.mfproj

I've forgotten it, April.
I've made a profile for the A107 V2 two months ago. I had the same problem as you and did not get the fire test buttons working.

I searched a lot, but somewhere in the internet I found the variables finally. But as said, I don't remember where. 

 

 

Thanks for the V2 profile.

Just wondering if you know how easy it is to convert to V3?

Thanks

Hi everybody

 

I am associated with John Clarke, kindly i request a profile for the V3 please

On 11/29/2025 at 1:52 AM, John Clarke said:

Thanks for the V2 profile.

Just wondering if you know how easy it is to convert to V3?

Thanks

Pretty easy once you figure out the correct mouseracts.

can somone send the V3 profile

 

On 1/13/2026 at 10:43 PM, Kacper Kozlowski said:

can somone send the V3 profile

 

A small nudge from my end for this V3 version as well... 
I've been trying to figure out how this works, but having a lot of struggles understanding the hardware list, and getting something useful in MF. 
Any guidance is very much appreciated  

 

 

Hello

Is there any progress regarding A107 V.3? Could you please finalize it?

Thank you very much and I wish you good work.

Regards