[mr_w]

I have pushed some updates in F3 branch (which is still work in progress, but getting tested daily):

- ADC driver, so reading analog voltage/current/rssi sensors is now possible.
- Fix for settings save error / hang.
- Fix for usart initialization error that prevented some protocols from working (for example MSP for osd, etc).
- Fix for usb cdc (virtual com port) baud rate negotiation - so ComBridge is now working again.

[mr_w]

Update: March 16, 2017:
- WS2811 led strip driver is now included (Betaflight port ). Notifications are the same as on F4 boards (Revo, Sparky2) [ https://librepilot.atlassian.net/wiki/display/LPDOC/Setup+WS281x+Led - with exception that configuration is not HWSettings > WS2811LED_Out, but rather HWBoardNameSettings -> LEDPort ]
- make package will build package with F3 firmware only

[Daxo]

OMG, this is so awesome!!!

LibrePilot is the best, but it was lacking support for at least f3 boards, mostly because of newer fc hardware designs which are more practical overall.

Big thumbs up for doing this, LP is all I want to use and now there's hope

Thank you!  

[mr_w]

Update: April 28, 2017:
- New branch name - it is now https://bitbucket.org/mindnever/librepilot/branch/LP-512_F3_board_support
- PikoBLX board support
- Fixed PPM input on SPracingF3 EVO
- Merged in newest next
- Merged in DSHOT support
- Merged in LP-480
- make package builds all boards again

[trike_flyer]

Hello

Thank you for the link to here mr_w.  After reading through the posts I went looking for a board I would want to use.  Here is a link to what I want to go with or something like it.

https://www.banggood.com/Mini-20x20mm-PBF3-EVO-6DOF-F3-Flgiht-Contorl-Board-with-MPU6000-SPI-5V-3A-BEC-Support-Soldering-ESC-p-1108332.html

Will it work with the F3 code? 

Thanks for the help.

TF

[mr_w]

This layout looks very similar to PikoBLX and as it seems it identifies itself as pikoblx to betaflight, so yes, I'd say its a pretty good bet that it will work just fine.

[mr_w]

There are some updates to F3 branch, which will hopefully be merged in next soon enough.

Update May 30, 2017:
- again new branch name (sorry), now accessible from pull-request: https://bitbucket.org/librepilot/librepilot/pull-requests/426 or as directly here https://bitbucket.org/mindnever/librepilot/branch/LP-512_Support_F3_boards
- tinyFISH FC board support

[fboriero]

mmmm so is there any possibility to control this board with the joystick trough bluetooth telemetry?
I mean... there is no yaw estimation at all???

Thanks for your time

[mr_w]

There are joysticks that allow you to twist the stick around Z axis, and that is commonly used for yaw control. So yes, controlling should be possible.

[f5soh]

Initial F3 support branch merged to next

Windows build:
https://drive.google.com/open?id=0B5d_9OcqQj8BdWxJYjY0N08yMm8

Attached files are .hex bootloaders to be flashed using Betaflight software.

[TheOtherCliff]

Nice!  I am getting an itch to scratch.  I have an F3 mini (Tarot TL150H1).  I was going to take out the F3 and put a Nano in it, but I may try the F3 LP code now. 

[TheOtherCliff]

What are the chances of getting PathPlanner running in the F3 branch?  Maybe reduce the EKF rate (PIOS_SENSOR_RATE) to 300Hz or so.  Some versions may need to run without baro.

Are there other large issues?  Memory?

[f5soh]

Not sure the F3 branch will help you, seems the Tarot TL150H1 uses a "Naze32 like" and F1.
http://www.flyingtech.co.uk/electronics/tarot-spare-part-mini-flight-controller-t120130140150

[mr_w]

The F3 regarding CPU usage is pretty much the same as F1. It runs just slightly faster on same Mhz, so usage is still pretty high. There is space for improvement (overall in LP) on that. Autotune when running makes the CPU alarm orange. Not really an issue, but still.


Free ram is pretty low too (around 6k I'd say), cause of the stabilization code which is from Revo family, and not simplified one used on cc3d.

[ehrans]

how to make it work on a spracingf3  (not evo) flashed bl already, but atached cgs doesn't recognize it.

thx