top of page

These are my suggestions and may not reflect that of MobiFlight. I can however say, that my sim build is now fully operational using Mobiflight (7.5.3) without any known issues. 

MobiFlight Board Naming
Arduino mega

I currently have 23 Ardunio Megas supported by various Amazon Basic USB 2.0 Powered Hubs. With this many Arduinos it's important to keep device labelling precise and keep good records.

  • Keep both Ardunio Mega Names & Device Names Short as possible

  • Don't use any special characters such as: -/_?"@

  • Avoid spaces if possible

  • DO NOT use the same Name for Boards or Devices.

For example, I Utilise 6 arduino Megas for the MIP/MCP/EFIS. 6 for forward Overhead and 5 for the Aft Overhead. The pedestal currently utilises 8. They are labelled alphabetically:

  • MIP1A

  • MIP2B

  • MIP3C

  • MIP4D

  • MIP5E

  • MIP6F

  • OHD1K

  • OHD2L

  • OHD3M

  • OHD4N

  • OHD5P

  • AOHD1Q

  • AOHD2R

  • AOHD3S

  • AOHD4T

  • AOHD5U

  • PED1V

  • PED2W

  • PED3X

  • PED4Y

  • PED5Z

I have simplified the individual device names such as switches & LEDS too. They are a reflection of the device board name they are attached too. I also utilise the following data sheet to keep track:

MobiFlight Pin Naming

You can see that I have utilised all 52 I/O (input/Output) pins. Looking back this was not a good idea for the following reasons:

  • If I want to add LCD displays I need to use Pins 20 & 21. I would leave this open next time.

  • If a pin fails, there is no room to move to the next pin/additional pin

  • Why not leave a few pins blank so future additions can be easily added

In short, if was to repeat building a whole cockpit again, I would use pin 2-19, 21-50.

Leaving 20/21 available for LCD screens

Pins 51 to 53 for future expansion/failed pins.

Mobiflight Sim Pin Template

Download a blank template for sim Below:


MobiFlight Debug Mode

This is extremely useful for finding out when you flick a switch and you do not know which switch is connected. I usually connect all my LEDS/Buttons to the arduino first, only noting what device is connected to that pin Switch or LED. 

I use debug mode to find out where they connect too. For example, i will flick a switch on the MIP and mobiflight will report back:

B12/MIP2B (the pin & Board)

It will then state either of these two options:

  • Config Found

  • No Config Found

This will depend on if you have entered the offset or setting in the config tab for that device. A great way to see if everything is set up correctly.

Under the Extras/Settings tab at the top of MF is Debug Mode.

Once your done entering all your data, don't forget to make the active line check box is ticked and you hit RUN in Mobiflight after programming!

The final piece of advice that I can give is, when adding or programming 7 Segment displays, If they don't work straight away. Save MobiFlight close and restart. They should then spring to life as you command. Usually buttons and LED's work straight away.




Well that's probably not completely true, but between MF & the Arduino you are limited to the following per ardunio Mega board:

  • 40 LEDS Max

  • 50 Buttons Max

  • 4 sets of daisy chained 7 segment displays with a max of 8 units in a each row.

  • 10 servo's

You can use a mix of any these listed above. Think of it like showing the Arduino board a bit of electrical mercy. Sharing the electrical loads between boards, rather than loading up one board with all high electrical current demands.

Toy Airplane


-  Tips & Tricks

bottom of page