Support new version of NOXE F4 FC

[FranzAr]

Current Behavior

The NOXE F4 FC from Banggood has been updated to a new version labeled "V1". The "old" target NOX does not work on that new hardware version.

Desired Behavior

Support new version "V1" as this FC is quite inexpensive and very small. Ideal for very limited space and light builds.

Suggested Solution

Betaflight seems to support this FC with the target Flywoo F411 and on the Flywoo website there is an iNav version 2.3.0 downloadable for this target. I flashed this to the new NOXE board and it seems to work fine. Maybe this could be a good starting point.

Who does this impact? Who is this for?

Everyone who needs a inexpensive and very small FC for iNav :-)

Additional context

iNav download from Flywoo: https://flywoo.net/products/flywoo-goku-f411-micaro-stack Noxe F4 at Banggood: https://www.banggood.com/de/20x20mm-Upgrade-Betaflight-F4-Noxe-V1-Flight-Controller-AIO-OSD-5V-8V-BEC-w-Barometer-and-Blackbox-for-RC-Drone-p-1310419.html

[mirov]

OK, thanks for that info. I wasn't sure if S.A. wanted some AC coupling or something.

On Wed, Jan 27, 2021 at 3:45 PM Eliel Romancini notifications@github.com wrote:

I actually am not sure what the CAM-C pin is connected to on the NOXE V1 board, but I also assumed that's what I'd be using for the VTX control only to find out that it wasn't working for me. The TX2 pin however seems to work just fine. Does anyone know what the CAM-C pin is connected to or the circuitry behind it ? … <#m-1430876041994525226> -Russ On Wed, Jan 27, 2021 at 2:21 PM Mooiweertje @.> wrote: TX2 doesn't work? Op wo 27 jan. 2021 23:16 schreef Eliel Romancini @. >: > my target.h file serial section looks like this: > > // * UART *** > #define USE_VCP > > #define USE_UART1 >

define UART1_TX_PIN PB6 > #define UART1_RX_PIN PB7 > > #define USE_UART2 >

define UART2_TX_PIN NONE //PA2 > #define UART2_RX_PIN PA3 > > #define

USE_SOFTSERIAL1 > #define SOFTSERIAL_1_TX_PIN PA2 // Clash with TX2, possible to use as > S.Port or VTX control > #define SOFTSERIAL_1_RX_PIN PA2 > > #define SERIAL_PORT_COUNT 4 // VCP, USART1, USART2, SS1 > #define DEFAULT_RX_TYPE RX_TYPE_SERIAL > #define SERIALRX_PROVIDER SERIALRX_SBUS > //#define SERIALRX_PROVIDER SERIALRX_IBUS > > #define SERIALRX_UART SERIAL_PORT_USART2 > > And I've used both SBUS/IBUS and Smart Audio. The SA wire from the VTX > solders to the TX2 pad. > > -Russ > > Sorry for my inability, but according to the BetaFlight target, the PB10 > pin is used for CAM_CC (where there is an output on the board for this > pin), which I will not use. > > So I ask, could you use PB10 instead of PA2 for SoftSerial1 and leave PA2 > for UART2? > > Would that work?: > > #define SOFTSERIAL_1_TX_PIN PB10 > #define SOFTSERIAL_1_RX_PIN PB10 > > #define UART2_TX_PIN PA2 > > — > You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub > <#5867 (comment) https://github.com/iNavFlight/inav/issues/5867#issuecomment-768614741>, or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AI6F3A443KY554K45P632K3S4CGDZANCNFSM4ODYCGZA

. > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5867 (comment) https://github.com/iNavFlight/inav/issues/5867#issuecomment-768617469>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJFJKUHJJO4GYRWXQWVS53S4CGYHANCNFSM4ODYCGZA .

Simple RC filter, i just checked the sign on the plate, If you remove the capacitor and put a wire in place of the resistor, we will have a direct output

[image: IMG_20210127_202847] https://user-images.githubusercontent.com/29925558/106068796-f0de3500-60df-11eb-828d-571249bc17dc.jpg [image: IMG_20210127_203730] https://user-images.githubusercontent.com/29925558/106068825-fdfb2400-60df-11eb-8f37-2b6f76f45e6f.jpg

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/5867#issuecomment-768653026, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJFJKTELHASOYB34C5QL73S4CQRRANCNFSM4ODYCGZA .

[elielmarcos]

To enable DSHOT on S3, did anyone try to set the dmatag to 1?

DEF_TIM(TIM1, CH3, PA10, TIM_USE_MC_MOTOR | TIM_USE_FW_SERVO, 0, 1), // S3_OUT 2,6

What is the purpose of the dmatag?

[mirov]

Actually I'm also interested in a general mini-tutorial that tells me what each of the fields are for this line. The first three are clear, the next not as much, and the last two I have no idea of the implications. And the comments are a complete mystery to me !

-Russ

On Thu, Jan 28, 2021 at 10:26 AM Eliel Romancini notifications@github.com wrote:

To enable DSHOT on S3, did anyone try to set the dmatag to 1?

DEF_TIM(TIM1, CH3, PA10, TIM_USE_MC_MOTOR | TIM_USE_FW_SERVO, 0, 1), // S3_OUT 2,6

What is the purpose of the dmatag?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/5867#issuecomment-769284730, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJFJKTZXTYJDVKG2XUT2E3S4GT6HANCNFSM4ODYCGZA .

[elielmarcos]

Actually I'm also interested in a general mini-tutorial that tells me what each of the fields are for this line. The first three are clear, the next not as much, and the last two I have no idea of the implications. And the comments are a complete mystery to me !

Tutorial YouTube Paweł Spychalski

INAV, Resource Mapping, Motors, Servos and Timers

Custom INAV Targets - resource mapping without resource mapping

but the last two fields are not explained

[mooiweertje]

Build with D-Shot support (S3). Build with PPM on led pin and TX2 added. For me to have two UARTS for GPS and DJI telemetry and PPM for RC receiver. The build is the same as the one in repo except for PPM moved to LED pin, LED support is gone, TX2 added and S3 raised DMAtag.

Test carefully! This fix is only tested on the bench.

jnav_2.6.0.2_FLYWOOF411.zip

I tried to enable SBUS on S3, RSSI, LED and CURRENT through softserial but no luck so far.

[elielmarcos]

Build with D-Shot support (S3). Build with PPM on led pin and TX2 added. For me to have two UARTS for GPS and DJI telemetry and PPM for RC receiver. The build is the same as the one in repo except for PPM moved to LED pin, LED support is gone, TX2 added and S3 raised DMAtag.

jnav_2.6.0.2_FLYWOOF411.zip

I tried to enable SBUS on RSSI, LED and CURRENT through softserial but no luck so far.

I made the change you said dmatag = 1 on S3 and everything worked, without locking engine 3 !!!

Congratulations, you are the guy;)

[mooiweertje]

Congratulations, you are the guy;)

Thanks, Test carefully!

[mooiweertje]

I'm trying to switch to HGLRC-Zeus-F722-mini to get more UARTS. https://www.banggood.com/20mm-HGLRC-Zeus-F722-mini-MPU6000-3-6S-F7-betaflight-Flight-Controller-w-or-OSD-Barometer-BLACKBOX-5UARTS-For-DJI-Air-Unit-Caddx-vista-FPV-Racing-RC-Drone-Freestyle-Quad-p-1651471.html

[Finnigan1971]

jnav_2.6.0.2_FLYWOOF411.zip

so this is a working firmware for my quad??? I don't speak english well but i understand that: -motor3 issue/dshot is now fixed -TX2 is working

is this correct?

[Finnigan1971]

auto-reply: EUREKA!

[mooiweertje]

Would anyone like to submit a pull request for these changes?

target.zip

[vaicekas]

Test carefully! This fix is only tested on the bench.

jnav_2.6.0.2_FLYWOOF411.zip

Thank you so much for your work! Now all engines are running as they should. So far, I’ve only tried it on the table. Maybe you could check the SDA and SCL pads? I am trying to connect a magnetometer to them, but it is not recognized. Thank you once again.

[Finnigan1971]

SDA & SCL work pefectly, i tested the quad some day ago and all seems working fine

[vaicekas]

Thanks for a confirmation. I will look for problems on my side ;)

[Finnigan1971]

Congratulations, you are the guy;)

Thanks, Test carefully!

Thanks once again, you did a GREAT work and you make me really happy. I tested the quadcopter in Angle and Horizon, it needs some PID tuning for even better performances but flies really well. Airmode is less invasive than in Betaflight. GPS works fine and the compass as well: this weekend i'll try Althold-Poshold and RTH, then i'll let you know.

[breadoven]

Anyone work out the voltage limit for the Current sensor input, 3.3V or 5V perhaps ?

[Finnigan1971]

any chance to have a 2.6.1 versiion of this stuff? Will be amazing!

[s2kaka]

where is softserial pad of this board? i want to use it for wing.

[breadoven]

where is softserial pad of this board? i want to use it for wing.

TX2 by default. If this is no good you can use the LED pin with a custom firmware build. Not sure which other pins can be assigned to soft serial.

[s2kaka]

where is softserial pad of this board? i want to use it for wing.

TX2 by default. If this is no good you can use the LED pin with a custom firmware build. Not sure which other pins can be assigned to soft serial.

Thank you, where I can get custom FW build? I want to use it for tiny wing and want 2 soft serial for runcam and smart audio.

[breadoven]

As far as I'm aware this board only supports a single soft serial port.

[mooiweertje]

any chance to have a 2.6.1 version of this stuff? Will be amazing!

If someone creates a pull request with the files in target.zip the changes will be part of the future releases, I mentioned this on februari 1.

target.zip

[s2kaka]

I just open a pull request at #6890 (Sorry that first time I open a pull request . )

any chance to have a 2.6.1 version of this stuff? Will be amazing!

If someone creates a pull request with the files in target.zip the changes will be part of the future releases, I mentioned this on februari 1.

target.zip

[mooiweertje]

!! Test carefully !! Untested merge so please let us know if it's good or not.

jnav_2.6.1.4_FLYWOOF411.zip

[mooiweertje]

any chance to have a 2.6.1 versiion of this stuff? Will be amazing!

What are the 2.6.1 features you are amazed about?

[s2kaka]

!! Test carefully !! Untested merge so please let us know if it's good or not.

jnav_2.6.1.4_FLYWOOF411.zip

Cornfirm it worked on Wing mixer, without softserail . 2 uart . TX2 for Fport ; Tx1+Rx1 for GPS, Need 1 softserial TX for Runcam control or smart audio. need to test outside. thanks for develope.

[UnchartedBull]

Hi guys,

I do have an issue with this FC and SoftSerial. I'm using an F.Port receiver (uninverted) on TX2, which is working fine and a GPS on UART1 which is also working fine. I'm now trying to get IRC Tramp to work with SoftSerial.

I tried with SoftSerial on RX2 and on CAM-C (with the resistors removed and a cable in place instead). Neither does work though. Tramp is working fine when I wire it up directly to TX2 (and temporarily remove the receiver). My changes so far:

target.h:

#define USE_UART2
#define UART2_TX_PIN            PA2
#define UART2_RX_PIN            NONE

#define USE_SOFTSERIAL1
#ifdef FLYWOOF411_V2
#define SOFTSERIAL_1_TX_PIN     PB6     // Clash with TX2, possible to use as S.Port or VTX control
#define SOFTSERIAL_1_RX_PIN     PB7
#else
#define SOFTSERIAL_1_TX_PIN     PA3     // Clash with RX2
#define SOFTSERIAL_1_RX_PIN     NONE
#endif

#define USE_SOFTSERIAL2
#define SOFTSERIAL_2_TX_PIN     PB10     // Clash with CAM_C
#define SOFTSERIAL_2_RX_PIN     NONE

#define SERIAL_PORT_COUNT       5       // VCP, USART1, USART2, SS1

target.c:

DEF_TIM(TIM5, CH4, PA3,  TIM_USE_ANY,   0, 1), //  RX2    1,0
DEF_TIM(TIM2, CH3, PB10, TIM_USE_ANY,   0, 0), //  CAM_C    1,0

Here is also the branch in my fork with the changes: https://github.com/UnchartedBull/inav/tree/noxe-f4. I'd really appreciate any help. Thanks!

[fruitsmen]

Hello... 1)Not work F.Port (FrSky R9mm) on FC "Noxe V1 F4" Tx2 (serial). I use FW iNav 2.5-2.6. What could be? p.s. On Matek F4 and F7 work fine.

2)How can i use SoftSerial for DjiFPV (air unit),what pins?

Best regards.

[mooiweertje]

This board has two UARTS. For instance you can use one for GPS and the other for DJI FPV. That leaves PPM on the LED pin for your RC receiver .

[elielmarcos]

Hello... 1)Not work F.Port (FrSky R9mm) on FC "Noxe V1 F4" Tx2 (serial). I use FW iNav 2.5-2.6. What could be? p.s. On Matek F4 and F7 work fine.

2)How can i use SoftSerial for DjiFPV (air unit),what pins?

Best regards.

Hi,

1) I use F.port on Noxe F4 V1 and I have no problems. Check serialrx_inverted and serialrx_halfduplex.

PS. I use RX R9MM, because R9Mini does not have a Non-Inverted SmartPort and cannot work with Noxe F4 V1

[fruitsmen]

F.Port work on modified FW.Thanks my friends.

[mooiweertje]

YW

[Fraggs150]

Quick query, which firmware version (stable) would be best for using with a conventional rudder,elevator,aileron type plane (3 servo outputs 1 motor output) ? Thanks in advance

[s2kaka]

Version 3.0.0! Test carefully!

Binary: jnav_3.0.0.6_FLYWOOF411.zip

thank you so much! Can i ask where is softserial pad?

[mooiweertje]

Would anyone like to submit a pull request for these changes? The iNav devs keep carrying bugs from one version to the next.

target.zip

[s2kaka]

new F4 NOXE V2 was release https://www.aliexpress.com/item/33057738988.html?spm=2114.12057483.detail.3.7266479c7pdlin

[Finnigan1971]

new F4 NOXE V2 was release https://www.aliexpress.com/item/33057738988.html?spm=2114.12057483.detail.3.7266479c7pdlin

yes, the day after i purchased a complete noxeV1 stack

https://it.aliexpress.com/item/32887868108.html?spm=a2g0s.9042311.0.0.44f34c4dHOfuhy

[mirov]

It is different, but is there anything compelling about V2 ? It seems like the BECs have changed, but much else ?

On Mon, Jul 5, 2021 at 1:35 AM andrea @.***> wrote:

new F4 NOXE V2 was release

https://www.aliexpress.com/item/33057738988.html?spm=2114.12057483.detail.3.7266479c7pdlin

yes, the day after i purchased a complete noxeV1 stack

https://it.aliexpress.com/item/32887868108.html?spm=a2g0s.9042311.0.0.44f34c4dHOfuhy

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/5867#issuecomment-873919938, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJFJKQYCEOHJYK76YRJEPLTWFVFFANCNFSM4ODYCGZA .

[mitsu199]

nice to meet you all. I connected gps to uart1 and f.port to uart2. Which pad should Soft Serial 1 be soldered to work? I want to control VTX using software Serial1. Please let me know.

[mooiweertje]

V0 is for sale still on AliExpress. https://nl.aliexpress.com/i/32885145565.html

[mirov]

Nah, you can configure other pins to be bit-banged "soft" serial pins. It is not a good idea to use these for your receiver or GPS but if there's a comm error for a moment talking to the VTX it isn't catastrophic (it is likely you get more serial coms bit width jitter with this approach than a real uart). I think you still need to find a pin that has a timer that is otherwise unused associated with it.

On Mon, Jul 19, 2021 at 10:32 PM Mooiweertje @.***> wrote:

As far as I know iNav only supports UART functions on actual UART pins/pads.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/5867#issuecomment-883072625, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJFJKRSU46NZNFPXLHUYTTTYUC7JANCNFSM4ODYCGZA .

[mirov]

Well you can't do it exclusively in the configurator (as perhaps you can in Betaflight). You need to build a custom image and compile your own firmware. Then in the configurator you can add the soft serial in the ports page (just like the "real" uarts).

In the target.h file I added these lines:

define SOFTSERIAL_1_TX_PIN PA1 // use the CURT pad for

soft serial for smart audio

define SOFTSERIAL_1_RX_PIN PA1

    #define SERIAL_PORT_COUNT       4       // VCP, USART1, USART2, SS1

and that should do it IIRC.

I feel your pain though, the F411 is nice and small, but you run out of UARTs really fast. And if you are trying to have I2C ports and real UART to hook up to a MAG and GPS there are very few options. Dig back through this thread and I provide the .hex files (and I think the target.h / .c files) for the FLYWOOF411 that I have used frequently.

On Mon, Jul 19, 2021 at 10:47 PM Mooiweertje @.***> wrote:

Nah, you can configure other pins to be bit-banged "soft" serial pins. It is not a good idea to use these for your receiver or GPS but if there's a comm error for a moment talking to the VTX it isn't catastrophic (it is likely you get more serial coms bit width jitter with this approach than a real uart). I think you still need to find a pin that has a timer that is otherwise unused associated with it. … <#m-2246865305537985002> On Mon, Jul 19, 2021 at 10:32 PM Mooiweertje @.***> wrote: As far as I know iNav only supports UART functions on actual UART pins/pads. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5867 (comment) https://github.com/iNavFlight/inav/issues/5867#issuecomment-883072625>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJFJKRSU46NZNFPXLHUYTTTYUC7JANCNFSM4ODYCGZA .

Then explain to Mitsu how you do this configuration in iNav configurator.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/5867#issuecomment-883083413, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJFJKVHDDMM27Y4GH73GLTTYUEYBANCNFSM4ODYCGZA .

[mooiweertje]

@mirov Is it still generically usable when there is a softserial setup on the curr pad and on UART2? Let's say I make such a build. Is it possible to configure in iNav configurator:

1. UART2 softserial RC receiver with telemetry together with current on current pad.
2. UART2 softserial RC receiver with telemetry together with VTX TX softserial on current pad.
3. UART2 any uart device (MSP for instance) with VTX TX softserial on current pad.

I don't see any timer setup which you suggested to make as well.

[s2kaka]

soft serial on tx2 is not work for Smart audio. can someone show me where is softsearial port on this FC

[s2kaka]

Version 3.0.1! Test carefully!

Binary: jnav_3.0.1.8_FLYWOOF411.zip

what is different with flywoof411 in inav config?

[Finnigan1971]

Hi again i'm testing a new Noxe V1 and i can use only the 2.6.1 configurator (my PC doesn't run the latest version) with the JNAV 2.6.2 custom firmware.

I have some small issues:

1) Led strip don't work 2) the buzzer starts to beep few seconds after the battery is plugged. 3) I use a switch+throttle down to arm the drone. If i disarm it i cannot re-arm again, i have to unplug the battery to re-arm.

Any tip?

[Finnigan1971]

@Finnigan1971 Can you try this build to see if LED strip works? jnav_3.0.1.10_FLYWOOF411.zip When PPM is chosen, PPM works on the LED pin (I just tried) and I expect LED is working now too when it is chosen and PPM is off.

My friend, I would be happy to help you but unfortunately due an obsolete PC i cannot run the latest configurators. Actually i use a 2.6.1 Config and a 2.6.2 firmware.

In the next days i'll try to install the latest config on another pc i'll have soon

I'll let you know. And what about the disarm issue and the beeper?

[Finnigan1971]

@Finnigan1971 Can you try this build to see if LED strip works? jnav_3.0.1.10_FLYWOOF411.zip When PPM is chosen, PPM works on the LED pin (I just tried) and I expect LED is working now too when it is enabled and PPM is off.

Hi again, finally i have the 3.0.1 Configurator installed. -i'll try your build asap

[Finnigan1971]

I just flashed the stuff with your build.

When i activate GPS in the config and i plug the battery, the board starts to beep (and the beeper as well) and don't stop. Led strip won't work.

[Finnigan1971]

Do you have PPM disabled?

i just selected "led strip" on on the config. i don't know how to disable PPM, i'm a real newbie