Hi there (sorry for my bad english, as always)

I disassembled my tyro79: too small and too racing.
I was after a more complex quad so i saved only motors and VTX and ordered a compass and a Noxe V1 with barometer.

The frame is a nice, light Kbat 136, i've enlarged the motor mounts holes to fit the 1607 motors...

-NOXE V1 UPDATED FC
-HAKRC 20A ESC
-EACHINE TYRO79'S VTX
-FOXEER RAZER MICRO CAM
-BEITIAN BN-180 GPS
-GY-271 MAG
-1607 2800KV MOTORS


Well
i flashed with the latest firmware after an accurate welding job, i calibrated all the stuff and all seems fine, the issue is the rear right motor that stops when i use the throttle.
(Dshot 150-300-600)

Trying Oneshot (125 & 42) the motors start to run in sequence (FR-RR-RL-FL)  with the fourth that starts at full throttle.

Any Idea?
Many thanks in advance.

here the "status", in attachment, the Dump

# status

System Uptime: 64 seconds
Current Time: 2041-06-28T01:04:00.000+00:00
Voltage: 11.86V (3S battery - OK)
CPU Clock=96MHz, GYRO=MPU6000, ACC=MPU6000, BARO=BMP280, MAG=QMC5883
STM32 system clocks:
 SYSCLK = 96 MHz
 HCLK   = 96 MHz
 PCLK1  = 48 MHz
 PCLK2  = 96 MHz
Sensor status: GYRO=OK, ACC=OK, MAG=OK, BARO=OK, RANGEFINDER=NONE, OPFLOW=NONE, GPS=OK
Stack size: 6144, Stack address: 0x20020000, Heap available: 1828
I2C Errors: 0, config size: 6468, max available config: 16384
ADC channel usage:
  BATTERY : configured = ADC 2, used = ADC 2
     RSSI : configured = ADC 3, used = none
  CURRENT : configured = ADC 1, used = none
 AIRSPEED : configured = none, used = none
System load: 5, cycle time: 506, PID rate: 1976, RX rate: 49, System rate: 9
Arming disabled flags: RX CLI
VTX: not detected

You might have a DMA resource conflict. Unfortunately, I am not familiar enough with INav to find out what DMA is assigned where?

My friend, can you explain what is a "DMA res. conflict"?
Is this issue fixable, in some way?

When you use dshot, each motor requires its own DMA assignment. In betaflight, you can check the DMA assignment by typing "resource" in CLI. But I not 100% sure how to do it with INAV. A DMA conflict is when 2 motors shares the same DMA. In betaflight, you can resolve the conflict by remapping resource, but I know you cannot do that in INav.

I will look into it more, on how INAV assigns the DMA for your FC.

Your problem might not be DMA conflict. Let do so troubleshooting. Can you spin the motor individually with the motor tab with oneshot and dshot?

First, thanks for your time, my friend.

Concerning DSHOT:
With the motor tab i can't spin the motor 3.
Arming, all four motors spin, the third stops once the throttle is raised.

Concerning ONESHOT:
With the motor tab i can spin all four motors.
Arming, the motors start to run, in sequence.

Concerning MULTISHOT:
With the motor tab, i can spin all four motors.
Arming, first start the Front Right motor, then the others.

Maybe i can try flashing with BF... so i'll see what happens?

(11-Dec-2020, 02:10 PM)finnigan Wrote: Maybe i can try flashing with BF... so i'll see what happens?

That is worth a try.

Done.
In BF i can arm all four motors and it works.
But i want INAV, on this toy :-(

It looks like the use of the NOXE F4 V1 flight controller with INAV is still work-in-progress which clearly still has some problems to be ironed out. See the following GitHub issue...

https://github.com/iNavFlight/inav/issues/5867

(11-Dec-2020, 07:00 PM)finnigan Wrote: Done.
In BF i can arm all four motors and it works.
But i want INAV, on this toy :-(

So there must some kind of resource conflict. When I have time, I will flash INav one of my FC and see if I see something.

(11-Dec-2020, 07:16 PM)SnowLeopardFPV Wrote: It looks like the use of the NOXE F4 V1 flight controller with INAV is still work-in-progress which clearly still has some problems to be ironed out. See the following GitHub issue...

https://github.com/iNavFlight/inav/issues/5867

You are right... here something more, but i don't understand:

https://github.com/iNavFlight/inav/pull/5958

I can't seem to find out how to view the DMA resource. Does sounds like the firmware is still a working progress.

(11-Dec-2020, 08:16 PM)finnigan Wrote: You are right... here something more, but i don't understand:

https://github.com/iNavFlight/inav/pull/5958

If you read from the following post downwards you will see that no-one managed to get DSHOT working successfully with 4 motors...

https://github.com/iNavFlight/inav/issue...-658057891

Then if you read the final post referencing the DSHOT issue (HERE) you will see that the person who submitted the pull request you linked to said he just released the FLYWOOF411 target with DSHOT enabled anyway, even though it appears to be troublesome. So there is no resolution to the problem in the currently released FLYWOOF411 target for INAV. One of us might be able to figure something out with a custom firmware build but whoever tries that really needs a NOXE V1 FC to test stuff with and I certainly don't have one unfortunately.

(11-Dec-2020, 09:18 PM)SnowLeopardFPV Wrote: If you read from the following post downwards you will see that no-one managed to get DSHOT working successfully with 4 motors...

https://github.com/iNavFlight/inav/issue...-658057891

Then if you read the final post referencing the DSHOT issue (HERE) you will see that the person who submitted the pull request you linked to said he just released the FLYWOOF411 target with DSHOT enabled anyway, even though it appears to be troublesome. So there is no resolution to the problem in the currently released FLYWOOF411 target for INAV. One of us might be able to figure something out with a custom firmware build but whoever tries that really needs a NOXE V1 FC to test stuff with and I certainly don't have one unfortunately.

So if you had the FC, you think can make a functional custom firmware?
(and MANY thanks for your kind aid)

(11-Dec-2020, 08:16 PM)finnigan Wrote: You are right... here something more, but i don't understand:

https://github.com/iNavFlight/inav/pull/5958

When you make a comment on github, it is best you give more details of your problem.