betaflight
betaflight copied to clipboard
joelucid
Led Status
Hi, I'm new here so forgive me if this has already been stated and this is the wrong thread.
I just flashed my SP Racing Pro F3 v1 board with the BF 4.1.1 PE with RPM filtering firmware. I didn't see anywhere mention the LED support was removed, however, my LED boards haven't been working since the update.
Is this a bug or has the support been removed?
Also is it possible to remove something else to enable VTX tables again? It's my only way of controlling my VTX right now
Again thank you Joe for all the work you do.
My main reason for upgrading to 4.1.1 was to add an ExpressLRS receiver to UART 2 and RPM filtering with my Bluejay ESCs.
Hi, I'm new here so forgive me if this has already been stated and this is the wrong thread.
I just flashed my SP Racing Pro F3 v1 board with the BF 4.1.1 PE with RPM filtering firmware. I didn't see anywhere mention the LED support was removed, however, my LED boards haven't been working since the update.
Is this a bug or has the support been removed?
Also is it possible to remove something else to enable VTX tables again? It's my only way of controlling my VTX right now
Again thank you Joe for all the work you do.
My main reason for upgrading to 4.1.1 was to add an ExpressLRS receiver to UART 2 and RPM filtering with my Bluejay ESCs.
LED strip function for F3 removed since 3.5.x. If you can build firmware, it's very easy to remove and add missing features. I usually remove blackbox(this use huge space of flash) function and add others. Blackbox is just easiest way, if you eyes on source code you might find other really meaningless features for SPRF3. So you add/remove features and repeat build, you can make optimal firmware and keep blackbox. But anyway, SPRF3 is too hard to keep logging blackbox with RPMFilter. In my experience, SPRF3 has very low clock speed that hardly run 4K/2K with RPM filtering even maxim overclock. Mine was not stable with RPM filtering. I thought it's better to replace another FC than waste time.
And vtxtable, SPRF3 don't have BetaflightOSD, so I didn't use that. But it's also very easy to adding like LED Strip. Maybe you can keep LED strip and vtxtable when remove blackbox function. or how about just use CLI command switching VTX without vtxtable.
Anyway my final thought is SPRF3 is not for recently quads. I've take out all SPRF3 from quads, and using for fixedwing with INAV olderversion, and it still works good for fixedwing. OMNIBUSF3 performs good for quads with RPMFiltering, but SPRF3 can't.
Thank you for getting back to me Joe. Ah okay. I'll look into how to build the firmware. Is there a good place I could start?
Yes removing the blackbox seems a good way to go.
I've got the VTX table working as I'm running ExpressLRS to change the VTX channel via lua script.
If I remove the blackbox and replace with Leds it should be fine.
I have it overclocked at 120mhz running 4k2k. It seems okay and stable but this is my first quad and I'm not used to anything different.
I'm saving up to be able to build a freestyle quad from scratch. Then I'll have a newer FC.
Thank you again for your help.
On Fri, 14 Oct 2022, 3:32 pm aQuaplug, @.***> wrote:
Hi, I'm new here so forgive me if this has already been stated and this is the wrong thread.
I just flashed my SP Racing Pro F3 v1 board with the BF 4.1.1 PE with RPM filtering firmware. I didn't see anywhere mention the LED support was removed, however, my LED boards haven't been working since the update.
Is this a bug or has the support been removed?
Also is it possible to remove something else to enable VTX tables again? It's my only way of controlling my VTX right now
Again thank you Joe for all the work you do.
My main reason for upgrading to 4.1.1 was to add an ExpressLRS receiver to UART 2 and RPM filtering with my Bluejay ESCs.
LED strip function for F3 removed since 3.5.x. If you can build firmware, it's very easy to remove and add missing features. I usually remove blackbox(this use huge space of flash) function and add others. Blackbox is just easiest way, if you eyes on source code you might find other really meaningless features for SPRF3. So you add/remove features and repeat build, you can make optimal firmware and keep blackbox. But anyway, SPRF3 is too hard to keep logging blackbox with RPMFilter. In my experience, SPRF3 has very low clock speed that hardly run 4K/2K with RPM filtering even maxim overclock. Mine was not stable with RPM filtering. I thought it's better to replace another FC than waste time.
And vtxtable, SPRF3 don't have BetaflightOSD, so I didn't use that. But it's also very easy to adding like LED Strip. Maybe you can keep LED strip and vtxtable when remove blackbox function. or how about just use CLI command switching VTX without vtxtable.
Anyway my final thought is SPRF3 is not for recently quads. I've take out all SPRF3 from quads, and using for fixedwing with INAV olderversion, and it still works good for fixedwing. OMNIBUSF3 performs good for quads with RPMFiltering, but SPRF3 can't.
— Reply to this email directly, view it on GitHub https://github.com/joelucid/betaflight/issues/12#issuecomment-1278390431, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3R56GB552O6TQ5LLKGDPALWDDA2JANCNFSM6AAAAAARCY2TVQ . You are receiving this because you authored the thread.Message ID: @.***>
@LeKestral
https://github.com/betaflight/betaflight/wiki/Building-Betaflight-on-Windows,-the-Linux-subsystem-way
add/ remove features "src/main/target/SPRACINGF3/target.h" references "src/main/target/common_pre.h"
FC CPU usage will highly increase when powering ESCs with RPM filtering. In my case 4k/2k(minimum looptime for dynamic filter) + RPM filtered on CPU usage almost 70% even before arming. And looptime was not precise as RPM filtering setup reference. When I flip few times, it was falls with rolling. I didn't know CPU usage was reason or not, but flying well after I disable RPM filter.
Good luck
Oh wow! I seem to be hitting 19% CPU usage before arming and around 30% - 40% when armed even with the Accelerometer enabled.
I definitely have RPM filtering enabled.
Thank you. I'll try that and hopefully get my LEDs working again.
On Sat, 15 Oct 2022, 1:30 am aQuaplug, @.***> wrote:
@LeKestral https://github.com/LeKestral
https://github.com/betaflight/betaflight/wiki/Building-Betaflight-on-Windows,-the-Linux-subsystem-way
add/ remove features "src/main/target/SPRACINGF3/target.h" references "src/main/target/common_pre.h"
FC CPU usage will highly increase when powering ESCs with RPM filtering. In my case 4k/2k(minimum looptime for dynamic filter) + RPM filtered on CPU usage almost 70% even before arming. And looptime was not precise as RPM filtering setup reference. When I flip few times, it was falls with rolling. I didn't know CPU usage was reason or not, but flying well after I disable RPM filter.
Good luck
— Reply to this email directly, view it on GitHub https://github.com/joelucid/betaflight/issues/12#issuecomment-1278943374, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3R56GANZHM4ONULOWUXVGTWDFG73ANCNFSM6AAAAAARCY2TVQ . You are receiving this because you were mentioned.Message ID: @.***>
@LeKestral Oh is it? I have wrong memory cause I did it long time ago :) And if you have problem with build firmware, I'll send you my firmware. It include almost all dropped features from F3, but vtxtable not included. Anyway it's not hard to anyone who know and search in github :) And I didn't familliar with github, here seems doesn't have attaching file menu.
Goodluck!
That would be great. I've had a look at the Betaflight GitHub link. Forgive me for being a little slow as I'm mostly unfamiliar with coding and building firmware. I think I can understand it given enough time.
That would be great if I could have a look at your firmware if that's okay?
Essentially the current one is perfect if I could just remove the blackbox and keep the VTX table and LED support
On Sat, 15 Oct 2022, 9:16 pm aQuaplug, @.***> wrote:
@LeKestral https://github.com/LeKestral Oh is it? I have wrong memory cause I did it long time ago :) And if you have problem with build firmware, I'll send you my firmware. It include almost all dropped features from F3, but vtxtable not included. Anyway it's not hard to anyone who know and search in github :) And I didn't familliar with github, here seems doesn't have attaching file menu.
Goodluck!
— Reply to this email directly, view it on GitHub https://github.com/joelucid/betaflight/issues/12#issuecomment-1279692621, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3R56GFVCAMIOKYRVU6BF6LWDJR5LANCNFSM6AAAAAARCY2TVQ . You are receiving this because you were mentioned.Message ID: @.***>
@LeKestral Ah I found way to attach file on here. I was blind ;) betaflight_SPRACINGF3_4.1.1_WT.zip
Sorry I don't have F3 source files anymore, but just firmware file. I think I included LED feature, but not tested, and included dropped features for better flight like integrated yaw control, absolute control, rc smoothing and other features F4 has. But curtainly not included vtxtable in this firmware. Anyway, it has SA and TR vtx control, so you can control VTX with Betaflight LUA script on your transmitter. vtxtable is just a preset, you can control vtx without vtxtable. or just use oldschool way using CLI command. like this set vtx_band = 5 set vtx_channel = 3 set vtx_power = 2
Oh awesome thank you so much! Yep I've been using the Lua script to change VTX channel, power etc. But if it doesn't need the VTX table that's perfect! Thank you again.
I'll reach out if I run into any issues
On Sun, 16 Oct 2022, 10:02 pm aQuaplug, @.***> wrote:
@LeKestral https://github.com/LeKestral Ah I found way to attach file on here. I was blind ;) betaflight_SPRACINGF3_4.1.1_WT.zip https://github.com/joelucid/betaflight/files/9793976/betaflight_SPRACINGF3_4.1.1_WT.zip
Sorry I don't have F3 source files anymore, but just firmware file. I think I included LED feature, but not tested, and included dropped features for better flight like integrated yaw control, absolute control, rc smoothing and other features F4 has. But curtainly not included vtxtable in this firmware. Anyway, it has SA and TR vtx control, so you can control VTX with Betaflight LUA script on your transmitter. vtxtable is just a preset, you can control vtx without vtxtable. or just use oldschool way using CLI command. like this set vtx_band = 5 set vtx_channel = 3 set vtx_power = 2
— Reply to this email directly, view it on GitHub https://github.com/joelucid/betaflight/issues/12#issuecomment-1279926029, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3R56GE4IDPQ57KMYYWSG2LWDPAA7ANCNFSM6AAAAAARCY2TVQ . You are receiving this because you were mentioned.Message ID: @.***>