[napo7]

Hi !

Me again with my sp racing F3

First things first... I'm trying to connect my PPM receiver to my board :
I've connected the PPM output pin to the correct pin (I/O pin N°3), the receiver is correctly detected by BetaFlight...

In LibrePilot, I've setup in the INPUT for each channel "PPM", and the channel number, but the green box on top of the window still says "no activity" even when I move the sticks...

Is there another place to setup the receiver to say it's a PPM one ?

Got another problem setting LED (WS2812B), and GPS (NEO 6M), but will make 2 other threads .

Thanks !

[mr_w]

Can you check System tab, HwSPRacingF3Settings uavo, there is IOPorts member, try selecting any of the options that include PPM.

Same HwSPRacingF3Settings has LEDPort which enables WS2812B strip.

Just remember to hit the SAVE button (red UP button at top toolbar) after making changes.

[napo7]

It seems that I've modified too much parameters : the board doesn't boot anymore : I've reflashed FW + BL, but the red light stays on instead of blinking...
Is there a way to erase EEPROM settings ?

[mr_w]

The board which fails to boot multiple times should automatically boot in "safe" mode - using default Hw settings.

[napo7]

That's it ! I'm not stubborn enought !
I've rebooted 4 times and it booted !

I've set the LED and PPM in the settings tab, now the remote is detected, and the led blinks !!
Sooo much problems solved at one time !!!!

Now I have to set the GPS receiver... Which UART port can I use ? Or which one should I avoid ?

[mr_w]

I believe there are some difference with regards which port is 5V tolerant and which is not - that you should pay attention when connecting GPS (depending on what voltage it uses).

But for the start, I'd just complete basic setup and make well flyable, before stepping up to GPS flight modes.

[napo7]

That's not a bad idea 

I'm finishing the basic setup !

See you soon 

[napo7]

So... I'm disappointed  with arming...
I've tried "yaw right", "accessory 0" (which is binded to my SW A), but the led still blinks WHITE almost 2x a second... When armed, it should blink blue ?

I've got all but 1 informations set to GREEN in flight data : CPU is orange ("cpu load has been higher than 95%").

Why can't I arm the board ?

Thanks again

Edit : I've checked in the system tab, the cpu load is always at 90% !?
Is that normal for a F3 board ??
On beta flight, cpu was about 10% load ?
Also, RX status bar on GCS is on RED : about 1040-1050 all the time ?