search

iNavFlight / inav

INAV: Navigation-enabled flight control software
https://inavflight.github.io
GNU General Public License v3.0
3.2k stars 1.49k forks source link

HW - Support F4-based targets #130

Closed digitalentity closed 8 years ago

digitalentity commented 8 years ago

Some support for F4 is done by @sambas already, it has to be ported to iNav

Linjieqiang commented 8 years ago

Great~! I'm going to design a flight control board for this firmware.The detailed list includes STM32F407,MPU9250,M8N GPS,MS5611~!

digitalentity commented 8 years ago

@Linjieqiang amazing! My few cents regarding new FC:

  1. Please consider using MPU6500 as it doesn't include the magnetometer
  2. Place the gyro on SPI bus for faster communication
  3. You may want to use MS5607 baro - it's much cheaper and accurate enough
  4. If you are going to design a GPS module as well, please consider using NXP MAG3110 chip as HMC mag chips are EOL
  5. Don't include a voltage regulator onboard. It takes space and makes the FC less crash-proof
  6. Use level shifters (3.3V - 5V) for SONAR Echo and LEDSTRIP pins to make operation noise-proof.
brat002 commented 8 years ago

Please, add support of Sparky 2.0.

ScienceFaction commented 8 years ago

Please add support for elle0 http://1bitsquared.com/products/elle0-autopilot http://wiki.paparazziuav.org/wiki/Elle0 Its an F4 board with the sensors on an spi bus designed for paparazzi. As paparazzi is open source getting the necessary porting info may be straight forward.

digitalentity commented 8 years ago

@Linjieqiang @ScienceFaction @brat002 I don't have any F4-based hardware to debug and test so this proibably won't happen any time soon. Sorry.

ScienceFaction commented 8 years ago

@digitalentity How about if I get you an elle0?

digitalentity commented 8 years ago

@ScienceFaction Then I'll get it working in INAV in a month or two (depending on how much time I have to spare). Drop me a message (my email address is in my GitHub profile).

martinbudden commented 8 years ago

Closing, duplicate of issue https://github.com/iNavFlight/inav/issues/274