Motors not spinning. Error at 100%

[tawdry shadow]

Hey guys, I've solder motors to the ESC, turned everything ON (with battery) connect everything with USB to BetaFlight Configurator... my controller is connected to the receiver (ELRS) and I can see response on BF configurator but motors are not spinning. Here is video: https://www.awesomescreenshot.com/video/22454050?key=d25f1f5e9e8dc4495823c198d90c6014
Motors I'm using: Rcinpower Wasp Major 22.6-6.5 - 1860kv
Stack: H743 Dual Gyro HD FC + ESC 60A BLHeli_32 4in1
BF Configurator: 10.10.0-RC1
Firmware: 4.5.0. but also tried on older ones 4.4.3. and 4.3.0. (original)
Tried on DSHOT 300 and 600.

Not sure what else I could try.
Looking for assist.

[pliant sundial]

Um, in that video, are you just wiggling the quad around at first? What's causing the motor revs to move? (Is it you using the controller?). I also don't see any error % in the video?

I did see something similar recently and a re-flash of the ESCs solved the problem, but it was showing % errors.

I would try turning off the esc sensor toggle too, just as a test.

Are you getting the standard start-up tones when you plug the quad into a battery?

[tawdry shadow]

No, I'm just using Radiomaster Boxer controller connected to ELRS to 'control' motors.
I reflashed to two older versions but did not help.
I tried to turn off everything (as well as ESC_SENSOR) but did not help.
I have custom beeper soldered on (I will upload video)... I can hear three beeps + one very short. Check my next video in a few minutes.

[cobalt root]

maybe bad solder, shorrt-circuit, bad smooke-stopper, bad lipo-coonection. something not right with power leads somewhere. be careful dont kill your hardware

[tawdry shadow]

status
MCU H743 (Rev.V) Clock=480MHz, Vref=3.31V, Core temp=48degC
Stack size: 2048, Stack address: 0x2001fff8
Configuration: CONFIGURED, size: 3827, max available: 131072
Devices detected: SPI:2, I2C:0
Gyros detected: gyro 1, gyro 2 locked dma
GYRO=BMI270, ACC=BMI270
OSD: MAX7456 (30 x 13)
BUILD KEY: 6d12c8dd2e60806c4832ed8c3207d18d (4.5.0-zulu)
System Uptime: 116 seconds, Current Time: 2023-11-14T20:01:49.685+00:00
CPU:6%, cycle time: 308, GYRO rate: 3246, RX rate: 15, System rate: 9
Voltage: 2292 * 0.01V (6S battery - OK)
I2C Errors: 0
FLASH: JEDEC ID=0x00ef4018 16M
GPS: connected, UART4 57600 (set to 57600), configured, version = M10
Arming disable flags: RXLOSS CLI MSP

dma show
Currently active DMA:

DMA1 Stream 0: DSHOT_BITBANG 2
DMA1 Stream 1: DSHOT_BITBANG 4
DMA1 Stream 2: SPI_SDO 1
DMA1 Stream 3: SPI_SDI 1
DMA1 Stream 4: SPI_SDO 2
DMA1 Stream 5: SPI_SDI 2
DMA1 Stream 6: SPI_SDO 3
DMA1 Stream 7: SPI_SDI 3
DMA2 Stream 0: ADC 1
DMA2 Stream 1: ADC 3
DMA2 Stream 2: SPI_SDO 4
DMA2 Stream 3: SPI_SDI 4
DMA2 Stream 4: FREE
DMA2 Stream 5: FREE
DMA2 Stream 6: LED_STRIP
DMA2 Stream 7: FRE

And DUMP file: https://pastebin.com/eayUg602

If this can be helpful.

[tawdry shadow]

Is there a way to check this with multimeter? I'm not so advanced so I might need help with it.

[cobalt root]

youtbe will tell multimetering motors and ESC, i have negligable experience.
if it were me i'd unplug FC, set it aside.
investigate lipo leads / solders on ESC.
look for solder-blobs as well between any components, FETs, etc.
try your smoke-stopper the same as your video without FC. if it still does it similarly, then problem exists before FC connector.

[tawdry shadow]

without FC I'm getting 3 beeps... it should be like that?

[cobalt root]

yes. but when you wiggle wires, any reboots?

3 beeps indicates power-up. unless you replaced with "music".

[tawdry shadow]

nope, it is soldered very hard.
But what I'm getting is beeping from multimeter all three motor wires together.
Separate motors are not beeping, and none of the motor wires are beeping with the battery cables.

but the motors are soldered already

from the visual perspective, I do not see any connections between pads

[cobalt root]

make sure no motr screws are touching enameled motor windings.
ESC will beep the 3 beeps (indicating boot up).
FC will beep the final 2 beeps (indicating initialized/sunchronized)
FC/betaflight/ESC-UI/Transmitter will control spinning.
when you wiggled you wires and things changed, this indcates some connection problem.

if you are lucky, it' just your connection on the smoke-stoper or power plugs

[tawdry shadow]

make sure no motr screws are touching enameled motor windings. --> as I can see, there are no screws that could potentially be attached to the motors
ESC will beep the 3 beeps (indicating boot up). --> it beeps 3 times
FC will beep the final 2 beeps (indicating initialized/sunchronized) --> it beeps 2 times
*FC/betaflight/ESC-UI/Transmitter will control spinning. - *
when you wiggled you wires and things changed, this indcates some connection problem. --> I'm wiggling the motor wires pretty hard but it does not reset or indicate to some problem
if you are lucky, it' just your connection on the smoke-stoper or power plugs --> short stoper v2 from VIFLY gives me green LED.

I might try with the local community and see if there is someone near me who can check the settings as well as soldering.

Thanks a lot mate. I have no more idea of what to try.

[pliant sundial]

When you say you've flashed, have you flashed the ESCs themselves?

[tawdry shadow]

Hmmm... To be honest I am not 100% sure on what you mean. 🤔

I connected FC to PC opened betaflight configurator and flash.

[pliant sundial]

OK, cool. The ESCs themselves, run firmware that can be flashed etc. Although I do not recommend doing it if you're new to it all, they can be flashed through a thing called BLHeli Suite.

Secondly, I presume you are trying this motor testing without a smoke stopper plugged in? Mine cuts my motors off if I leave it in place.

I do see that @cobalt root mentioned something about wiggling wires changing something? If so, I'd stop everything and sort out all connections before doing anything else - even resoldering.

[tawdry shadow]

Soo... Do you think I should try it? With BLHeli...or should ask someone local to help me with it?

I always used short stopper when turning it on. I did not tried it without (but BF config. Says 22-23V).

Wiggling wires does not make any changes. I get no extra beeps or restarts.

It is soldered very hard. Wires can not be moved.

[pliant sundial]

It might just be that your smoke stopper is tripping and stopping your motors - BUT be very sure there is nothing wrong with your wiring before removing it - I cannot stress this enough and I take no blame if you blow something up. Just bear in mind that smoke stoppers can trip when attempting to test motors.

Normally, if a smoke stopper is to blame, you might see some small amount of movement from one motor before it trips.

But you might not too.

[tawdry shadow]

Yes, I understand. I will not blame you for anything.

[pliant sundial]

If you are confident that your wiring is all OK, I would try it without a smoke stopper.

BUT only if you're sure your wiring is OK.

[tawdry shadow]

Yes, I see some very small moves at the motors when I press start button on Smoke stopper.

[pliant sundial]

Sorry, do you mean they move a little then don't work after that?

[tawdry shadow]

Yes, it is very hard to see it but I can feel it under fingers when I hold it.

I will try to record it tomorrow.

[pliant sundial]

Well, I would probably try without a smoke stopper - I didn't realise you were using one this whole time. But it is up to you.

[tawdry shadow]

Thanks a lot. I will update you tomorrow if I fixed it. Cheers!

[pliant sundial]

Good luck.

[cobalt root]

okay, i suppose i misinterpreted this video as a connection problem as if it lost power unexpectely. so sorry.

[tawdry shadow]

@pliant sundial I just tried without the short saver, but did not help. Motors are not spinning

[pliant sundial]

Okay, without seeing all of the wiring, etc, it is very hard to make a determination as to what the problem may be.

If you have a GPS connected, I would disconnect it just in case the GPS unit is spamming any of the UART ports and thus interfering with something else. The basic idea here is to reduce the quad to the simplest you can get it to see if you can get the motors to spin.

It may also be as simple as flashing the ESCs but it is very hard for me to tell from just reading here.

[tawdry shadow]

Thanks @pliant sundial I will try piece by piece. I am also uploading video of the turning the fpv ON so everyone can see that the motors make a small move.

[pliant sundial]

Do you have a receiver in that quad yet?

I am not hearing the final two beeps on the boot up.

This could indicate that the flight controller is not communicating with the ESC.

(Or that it is only getting partial communication)

Okay so we discussed the receiver above, so you do have one. The fact that I’m not hearing the last two tones makes me wonder about a few things. Did you have to make a wiring harness to connect the ESC to the flight controller? Or did it come with a premade cable? Is the stack sold as a pair (flight controller and ESC)

[tawdry shadow]

Yes. The happymodel ep1 dual tcxo elrs 2.4g is soldered to it. And it works. I know that because I was able to bind it with my radiomaster boxer controller, and I can see the changes in the BetaFlight config.

[tawdry shadow]

Connector with 8 pins (I think) came in the stack package.

Here is the diagram: https://skystars-rc.com/wp-content/uploads/2022/10/Skystars-H743-60A-FlyStack-2.jpg

[pliant sundial]

So, the lack of the last two tones indicates to me that the flight controller is not communicating with the ESCs. I have seen differing opinions on what the last two tones mean but it is my understanding that they do indicate a connection with the flight controller in one way or the other. Given you are not hearing those two tones I do not believe that your flight controller is communicating with your ESC. I may be wrong but it is interesting that I am not hearing those tones.

I would check that everything is plugged into everything correctly (and into the right places) and try again. Pay close attention to the plug wiring to make sure that it makes sense.

[tawdry shadow]

Thanks buddy. I will try it.

[pliant sundial]

I am not sure that the motors tab in betaflight would even work if you have no communication with your ESCs but I find this whole thing somewhat interesting.

In order to see if beta flight can see your ESC. You can try using the BLHeli suite. I think you should do this first just to make sure you can even see your ESCs

[cobalt root]

yes, the 8-pin ESC to FC harness must be wired correctly. otherwise betaflight firmware/configurator and/or ESC configurator I will never communicate to ESC.
make sure dshot300 or dshot600 is set in motors tab.

[tawdry shadow]

Update: 8-pin connector cable (ESC to FC) was not wired correctly but came as default already plugged cable. Factory problem.
Motors are spinning now 🙂

[pliant sundial]

Can you please rename this thread and include the word ‘Solved’ and/or add a Solved tag? And well done.

[cobalt root]

awesome, i suspected connections, but at the same time, did not suspect a paired-stack to have mis-pinned 4in1 cable.
i've seen factories send bad configs/documentation quite often. pilots typically know to re-pin cables if they are separate products. but i've never seen a paired fc/esc-stack to have a mis-pinned 4in1.

[tawdry shadow]

I would never check it if a guy would not tell me to check how cable plug is setup. Then I relized black wire does not go to the GDN 😮 But okay, we made it 😄