MobiFlight Community Support

Welcome to the forum for MobiFlight! Feel free to reach out to the community in case you have questions, issues or just want to share great ideas or details about your latest home cockpit project.

You like MobiFlight? Donate via PayPal and support the MobiFlight development. Thanks! 

05/03/2024 - This forum is read-only

The community support for MobiFlight has moved exclusively over to our Discord server. Register for free and enjoy more interactive functions like image and video upload, voice chat. More than 7,000 registered users around the world make it a great experience!

See you on our MobiFlight Community Discord server.

A HUGE Thank You to everyone who participated in the forum, especially obviously to Pizman and Stephan who did an outstanding job over so many years providing an incredible service to the MobiFlight community.

The forum is still providing a lot of good content, hence we keep this information accessible.

icon
Avatar
rodri_go
Posts: 1
Good morning, and thanks for creating Mobiflight :love: , I am starting my simulator and when assembling the electronics I have had a couple of ideas that I think would improve the control of servos and stepper motors.

An idea would be to be able to use A4988 or Drv8825 drivers for stepper motors, I think it is a good improvement, since these drivers allow current regulation directly on the motors and only use 2 arduino pins.

Another improvement that I can think of is to be able to use the pca9685 card, which allows up to 16 servos to be controlled using the I2C protocol, so we would also save arduino pins and there would be fewer cables through the system.

Regards.
2019-12-20 07:58
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Hi
Welcome to Mobiflight and thank you for your ideas.

Pretty sure Sebastian ( Godfather from Mobiflight ;) ) will comment this himself.

Basicly i can say our policy is pretty simple..... If a Element can not be done at the moment then those things are Top Prior on the List.
If a element still can be done but only verry difficult or in a poor result then this is medium prior.
If a new feature request just have the advantage to save arduino Pins or wire work then this is normaly lowest prior or basicly not planed to implement.
Here the main policy is that Number of Megas is not limited and costs are low.... So its no mater if we use 5,10 or 20 Megas in a Cockpit.


Some Examples:
- 14/16 Segment Displays ...... High Prior cause not possible at the moment but needed for lots of Cockpits.

- Blinking Mode for LED ...... Medium Prior. Possible with a good precondition aalready today but difficult and not 100% real. So we like it but we not rudimentary need it.

- Matrix for Buttons so we can make 64 Inputs with just 16 Pins .... Low Prior / Not planed anyway..... Simply use 2 Megas to get the same result !


Whatever.... Every new inspiration is good. If you like please join us in Bitbucket. there you can Open Requests directly and get involved in the develop process.
Good Luck !
2019-12-20 14:55
icon