(15-Apr-2023, 02:37 PM)mstc Wrote: You would run a wire to bridge the battery pads of the two boards (+ to + and -  to -). I would run battery plug to the AIO first  and then to the ESC. AIOs have smaller solder pads, so it might be tight to fit two wires (especially that GEPRC board the two pads are very close together, I had one short out when it was bumped), you could try one on top and other on the bottom. Otherwise running the battery plug to the ESC first and then to the AIO should also work.

Hey,

so I got this to work, but there seems to be a problem with betaflight in terms of the motor order. The motor next the one that's giving me problems (3) won't spin when I remap the LED. But when I undo the mapping, everything is fine again, which of course puts me back in square one. Here's the before and after motor resource:

Before mapping:
resource MOTOR 1 B04
resource MOTOR 2 B05
resource MOTOR 3 B06
resource MOTOR 4 B07
resource MOTOR 5 B03
resource MOTOR 6 B10
resource PPM 1 A03
resource LED_STRIP 1 A08

After mapping:
resource MOTOR 1 B04
resource MOTOR 2 B05
resource MOTOR 3 B06
resource MOTOR 4 A08
resource MOTOR 5 B03
resource MOTOR 6 B10
resource PPM 1 A03
resource LED_STRIP 1 B07

If I leave motor 4 "empty" betaflight won't accept it being so, and the whole thing just doesn't work anyway. The problem may be related to the fact that I originally had to change the orientation of the board, but I doubt that could be it, and I don't even have the original resource configuration. Any suggestions?

res

Does motor 3 or motor 4 have issues on the AIO? If it is motor 3, then you should remap motor 3 to the LED pin. Also the LED pin should then be soldered to the signal wire of your alternate ESC.

If you have changed the orientation of your board, then maybe you have also remapped motor order using BF. In which case the motor numbers may not correspond to the numbers as printed on the board. You would need to spin up the motors one by one in BF to confirm which BF motor number (not board printed number) is the problem motor you want to remap.

(15-Apr-2023, 06:45 AM)voodoo614 Wrote:
They are tiny pin. Mission impossible. If you still interested, I would look for a component they might connect to. Here are the pins you would be interested in.

MOTOR1_PIN           B4
MOTOR2_PIN           B5
MOTOR3_PIN           B6
MOTOR4_PIN           B7

Hi,

so I got this to work using the remapping-to-the-LED pad method, but there seems to be a problem with betaflight in terms of the motor order. The burnt-out esc is on motor 4; the motor next to it (3) is no longer responding after the remapping, but when I undo the led mapping, 3 is fine again and of course 4 remains dead. Here's the before and after motor resource:

Before mapping:
resource MOTOR 1 B04
resource MOTOR 2 B05
resource MOTOR 3 B06
resource MOTOR 4 B07
resource MOTOR 5 B03
resource MOTOR 6 B10
resource PPM 1 A03
resource LED_STRIP 1 A08

After mapping:
resource MOTOR 1 B04
resource MOTOR 2 B05
resource MOTOR 3 B06
resource MOTOR 4 A08
resource MOTOR 5 B03
resource MOTOR 6 B10
resource PPM 1 A03
resource LED_STRIP 1 B07

If I leave motor 4 "empty" betaflight won't accept it being so, and the whole thing just doesn't work anyway. Any suggestions?

It sounds like you might have a DMA conflict. Can you type "resource" in CLI and post what it say?

(16-Apr-2023, 10:15 PM)voodoo614 Wrote: It sounds like you might have a DMA conflict. Can you type "resource" in CLI and post what it say?

I undid the LED mapping pending a solution:


# 
# Building AutoComplete Cache ... Done!
# 
# resource
resource BEEPER 1 B02
resource MOTOR 1 B04
resource MOTOR 2 B05
resource MOTOR 3 B06
resource MOTOR 4 B07
resource MOTOR 5 B03
resource MOTOR 6 B10
resource PPM 1 A03
resource LED_STRIP 1 A08
resource SERIAL_TX 1 A09
resource SERIAL_TX 2 A02
resource SERIAL_RX 1 A10
resource SERIAL_RX 2 A03
resource I2C_SCL 1 B08
resource I2C_SDA 1 B09
resource LED 1 C13
resource LED 2 C14
resource SPI_SCK 1 A05
resource SPI_SCK 2 B13
resource SPI_MISO 1 A06
resource SPI_MISO 2 B14
resource SPI_MOSI 1 A07
resource SPI_MOSI 2 B15
resource ADC_BATT 1 B00
resource ADC_CURR 1 B01
resource OSD_CS 1 B12
resource GYRO_EXTI 1 A01
resource GYRO_CS 1 A04
resource USB_DETECT 1 C15

You might have to post a dump. I don't see the DMA assignment.

I just need to see the resources, timer and DMA. You can truncate the rest.

(17-Apr-2023, 12:30 AM)voodoo614 Wrote: I just need to see the resources, timer and DMA. You can truncate the rest.

# dma
dma ADC 1 1
# ADC 1: DMA2 Stream 4 Channel 0
dma pin B04 0
# pin B04: DMA1 Stream 4 Channel 5
dma pin B05 0
# pin B05: DMA1 Stream 5 Channel 5
dma pin B06 0
# pin B06: DMA1 Stream 0 Channel 2
dma pin B07 0
# pin B07: DMA1 Stream 3 Channel 2
dma pin B03 0
# pin B03: DMA1 Stream 6 Channel 3
dma pin B10 0
# pin B10: DMA1 Stream 1 Channel 3
dma pin A00 0
# pin A00: DMA1 Stream 2 Channel 6
dma pin A02 0
# pin A02: DMA1 Stream 0 Channel 6
dma pin A08 0
# pin A08: DMA2 Stream 6 Channel 0
# resource
resource BEEPER 1 B02
resource MOTOR 1 B04
resource MOTOR 2 B05
resource MOTOR 3 B06
resource MOTOR 4 B07
resource MOTOR 5 B03
resource MOTOR 6 B10
resource PPM 1 A03
resource LED_STRIP 1 A08
resource SERIAL_TX 1 A09
resource SERIAL_TX 2 A02
resource SERIAL_RX 1 A10
resource SERIAL_RX 2 A03
resource I2C_SCL 1 B08
resource I2C_SDA 1 B09
resource LED 1 C13
resource LED 2 C14
resource SPI_SCK 1 A05
resource SPI_SCK 2 B13
resource SPI_MISO 1 A06
resource SPI_MISO 2 B14
resource SPI_MOSI 1 A07
resource SPI_MOSI 2 B15
resource ADC_BATT 1 B00
resource ADC_CURR 1 B01
resource OSD_CS 1 B12
resource GYRO_EXTI 1 A01
resource GYRO_CS 1 A04
resource USB_DETECT 1 C15
# timer
timer A03 AF3
# pin A03: TIM9 CH2 (AF3)
timer B04 AF2
# pin B04: TIM3 CH1 (AF2)
timer B05 AF2
# pin B05: TIM3 CH2 (AF2)
timer B06 AF2
# pin B06: TIM4 CH1 (AF2)
timer B07 AF2
# pin B07: TIM4 CH2 (AF2)
timer B03 AF1
# pin B03: TIM2 CH2 (AF1)
timer B10 AF1
# pin B10: TIM2 CH3 (AF1)
timer A00 AF2
# pin A00: TIM5 CH1 (AF2)
timer A02 AF2
# pin A02: TIM5 CH3 (AF2)
timer A08 AF1
# pin A08: TIM1 CH1 (AF1)

(17-Apr-2023, 12:30 AM)voodoo614 Wrote: I just need to see the resources, timer and DMA. You can truncate the rest.

While I was waiting for your response, I further researched DMA conflict and found that the bitbang setting would solve the problem. I set bitbang to on and the motor now spins. Do I keep it on "ON" or "Auto" ?

That is quite interesting. If anything, I would assume that turning bitbang to OFF would resolve the conflict. The reason being, bitbang uses only TIM1 on the F411. TIM8, which is the other option is not available on the F411.
Since TIM1 is assigned to A08, I thought this would be a conflict.

If you are able to remap A08 (LED_STRIP) to motor 4 and was able to get it working with bitbang to ON, I would keep it as ON.

You also mentioned earlier that you cannot unassign LED_STRIP to nothing. You can actually assign it to "NONE".

BTW, can you post the link where you read about turning on bitbang can solve the problem. I am interested.

(17-Apr-2023, 05:35 AM)voodoo614 Wrote: BTW, can you post the link where you read about turning on bitbang can solve the problem. I am interested.

Hey, here's where I found the bitbang "on" info: https://github.com/betaflight/betaflight/issues/11375

generally speaking, are there any potential problems with attaching the AIO to the 4-in-one esc, like a flyaway or any other erratic motor behavior based on the esc "imbalance" ?

Never could figure out timer conflicts, I encountered that motors not showing issue on a ELRS SPI board and had to turn on bitbang, but seem to recall in the final 4.3 release BF updated the FC configs so it wasn't needed. Some nice detailed explanation if you can understand it... but I guess turning on bitbang uses less timer streams for motors so you have less chance of conflict.

In terms of mixing matching ESCs, I don't imagine you would notice any difference as long as they have similar ESC settings, but haven't actually tried it.

Quote:SteveCEvans commented on Feb 4, 2022

Bitbanged DSHOT requires TIM1 or TIM8, and the F411 doesn’t have TIM8. Unfortunately the choice of pin for SOFTSERIAL on this FC means it has to use TIM1 too, so we have to choose one or the other.
4.3 introduces DMA on SPI which is particularly useful for FLASH (black box) access, OSD, and potentially SPI RX as well as the gyro.
Unfortunately there are limited resources available for DMA and if timer based DSHOT is used then four of the sixteen DMA streams get used for MOTOR 1-4. These typically clash with SPI_MISO/SPI_MOSI streams needed for the above DMA. A better option is to use bitbanged DSHOT as this only uses one stream per port (so if your motor pins are on ports A and B, for example you’ll need two streams) and these streams will be on DMA2 which won’t conflict with the SPI DMA streams for SPI 2 and SPI 3.
Alas there’s a bug in F4’s which means that we can’t use bitbanged access on DMA2 at the same time as SPI DMA on DMA2, and typically gyros are on SPI 1 which is on DMA2.
The upshot of this is that in order to get DMA access to OSD/FLASH/SPI RX, on most FCs we have to enable bitbanged DSHOT and lose gyro DMA as a consequence. We also lose anything else that uses TIM1, which may impact SOFTSERIAL or LEDSTRIP.
Careful selection of the pins used for the motors can allow for four MOTOR resources and all the SPI DMA resources at the same time. Then we get the best of everything. The FURYF4OSD got this right!

(17-Apr-2023, 06:54 AM)theon_Jules Wrote: Hey, here's where I found the bitbang "on" info: https://github.com/betaflight/betaflight/issues/11375

generally speaking, are there any potential problems with attaching the AIO to the 4-in-one esc, like a flyaway or any other erratic motor behavior based on the esc "imbalance" ?

Thanks for the link.

There is no problem with using 4-IN-ONE ESC on an AIO FC. Only issue I can see is the weigh. So flying characteristics might feel different. And flight time might be shorten. More so on a light build vs heavier build.

(17-Apr-2023, 01:26 PM)mstc Wrote: Never could figure out timer conflicts, I encountered that motors not showing issue on a ELRS SPI board and had to turn on bitbang, but seem to recall in the final 4.3 release BF updated the FC configs so it wasn't needed. Some nice detailed explanation if you can understand it... but I guess turning on bitbang uses less timer streams for motors so you have less chance of conflict.

In terms of mixing matching ESCs, I don't imagine you would notice any difference as long as they have similar ESC settings, but haven't actually tried it.

SO, timer base Dshot (bitbang off) uses more DMAs (four of them) while bitbang Dshot (bitbang on) uses less (one of them). OP must of had a DMA conflict and therefore resolve the issue by turning on bitbang. Which freed up some DMA.