Help! Racing quad - Diatone GT-M530 - motors cutting-out

mastermalpass

Elite member
A few months ago, I was showing my Diatone GT-M530 to a colleague when the motors would cut mid-flight and it would drop. This happened more and more as I tried to fly it and so I called it and looked online for help. Apparently it was a connection issue, solution being to take the props off, get the motors spinning and poke it with a stick until the location of the bad connection becomes apparent...

Of course, my problem wouldn't be that simple, would it? 😂 The GT M530 seems quite happy being poked, flexed, violently shaken and repeatedly whacked with a light bouncey object without any motor-cut-off problems. The problem would eventually happen and I was stumped as to what caused it each time. Eventually, when filming it in hopes the Quad specialists on here might know what can cause this, I stumbled across the cause of the issue; specifically when in Angle (auto-level) mode, if I tilt it close to 90° the motors cut out. Has anyone else had this issue before? It has been flying fine for ages since it was last plugged in, this issue hasn't appeared after an update or anything, rather after I moved house and it spent ages sitting in a box.


Oh also, I just ran another test - pushing the pitch and roll axis to max both ways, to see if the attempt to change orientation is what's causing the issue. I found that pushing the stick to max when in auto-level mode does not replicate the cut-out issue.
 

Merv

Site Moderator
Staff member
Great video, indeterminate problems are the most difficult to diagnose.

I’d like to see if there is anything wonky with the main battery and connecting wires. Power up the quad and wiggle the main battery wires to see if something is loose. I’ve had occasions where the main battery plug is not making a good connection, I needed to spread the pins a bit to fix the problem.
 

agupt108

Member
A few months ago, I was showing my Diatone GT-M530 to a colleague when the motors would cut mid-flight and it would drop. This happened more and more as I tried to fly it and so I called it and looked online for help. Apparently it was a connection issue, solution being to take the props off, get the motors spinning and poke it with a stick until the location of the bad connection becomes apparent...

Of course, my problem wouldn't be that simple, would it? 😂 The GT M530 seems quite happy being poked, flexed, violently shaken and repeatedly whacked with a light bouncey object without any motor-cut-off problems. The problem would eventually happen and I was stumped as to what caused it each time. Eventually, when filming it in hopes the Quad specialists on here might know what can cause this, I stumbled across the cause of the issue; specifically when in Angle (auto-level) mode, if I tilt it close to 90° the motors cut out. Has anyone else had this issue before? It has been flying fine for ages since it was last plugged in, this issue hasn't appeared after an update or anything, rather after I moved house and it spent ages sitting in a box.


Oh also, I just ran another test - pushing the pitch and roll axis to max both ways, to see if the attempt to change orientation is what's causing the issue. I found that pushing the stick to max when in auto-level mode does not replicate the cut-out issue.
Not sure if this is the same problem but for me the motor (rc plane) on full throttle spins well for a minute and then stops followed by one beep of the esc. I haven't figured out how to fix it
 

mastermalpass

Elite member
Great video, indeterminate problems are the most difficult to diagnose.

I’d like to see if there is anything wonky with the main battery and connecting wires. Power up the quad and wiggle the main battery wires to see if something is loose. I’ve had occasions where the main battery plug is not making a good connection, I needed to spread the pins a bit to fix the problem.

Hmm... If it were the battery I'd be expecting a full reboot, not just a motor cut and also for the issue to occur outside of auto-level mode. But I'll give the battery cables a tug and see if that does anything.
 

LitterBug

Techno Nut
Moderator
I have a question and a comment based on the video.
What firmware is running on the quad, and what version of the firmware?
The beep is not from the ESCs, but rather the FC. The tones are disarm tones. You need to find out what the error message is that it is complaining about and solve that issue. It is possible that with low throttle, the Firmware is disarming because it is passing 90 degrees. If you have FPV set up on it, look to see if there are any error messages being thrown on the FPV screen when it beeps/stops

Regards,
LitterBug
 

mastermalpass

Elite member
I have a question and a comment based on the video.
What firmware is running on the quad, and what version of the firmware?
The beep is not from the ESCs, but rather the FC. The tones are disarm tones. You need to find out what the error message is that it is complaining about and solve that issue. It is possible that with low throttle, the Firmware is disarming because it is passing 90 degrees. If you have FPV set up on it, look to see if there are any error messages being thrown on the FPV screen when it beeps/stops

Regards,
LitterBug

Hmm... I'll have to plug it in and find out. I flashed the FC when I first got this back in 2019. I'll check the FPV feed and see if any reports come through there.

If I replicate this issue while plugged into Betaflight, is there somewhere I can check for FC error messages in there?
 

LitterBug

Techno Nut
Moderator
Hmm... I'll have to plug it in and find out. I flashed the FC when I first got this back in 2019. I'll check the FPV feed and see if any reports come through there.

If I replicate this issue while plugged into Betaflight, is there somewhere I can check for FC error messages in there?
Chances are, you will not be able to arm while plugged in. Especially if running Betaflight.
 

mastermalpass

Elite member
Chances are, you will not be able to arm while plugged in. Especially if running Betaflight.

I think I remember Betaflight having an arm-lock safety feature that could be disabled. I definitely remember spooling up the motors when plugged in. I just can't remember if that was via the transmitter as well as, or just the channel testing via betaflight alone.
 

Tench745

Master member
I know very little about quads, so these are somewhat generic stabs in the dark for others more knowledgeable to build off of.
I know my Tiny Whoop has a setting where you can set the maximum angle at which the quad will arm (so it can't arm while upside down or whatever) perhaps it is somehow disarming because of a similar parameter?

In the theatre, the software we use for automating moving scenery uses a PID loop and there is failsafe in the program that stops the winch and gives a "position error" if the actual movement of the winch isn't keeping up with where the software thinks it should be. I don't know if any flight controller has a similar functionality, but maybe your FC is telling the quad to do something it can't do (or can't do fast enough) so it throws an error and shuts down?
 

CappyAmeric

Elite member
Since it is a 4-in1 ESC, it could be an ESC desync.

I would update to BetaFlight 4.4 first (you will need to update BetaFlight Configurator to the latest Windows/Mac version), then in the Presets tab, select UAVTech’s 5 inch profile and apply it.

Make sure you backup your BetaFlight configuration before updating. You can do that using BetaFlight Configurator’s backup feature, or using the CLI command DUMP ALL and save to text file.

If that does not fix it, check that there are no solder cracks where the battery leads connect to the ESC, and also reseat the connector wiring harness between the ESC and flight controller.
 

CappyAmeric

Elite member
You can also check your ESC for problems with BLHeli_32 configurator software you can do it with the Chrome plug in or stand alone Windows/Mac software.
 

henry9823

New member
Betaflight may have included an arm-lock safety feature that could be turned off, if memory serves. I distinctly recall the motors spinning up after being plugged in. I just can't recall if that was done through the transmitter as well or just through betaflight for the channel testing.
 

mastermalpass

Elite member
Well, this has been a journey already! Went to plug in, 'Could not connect to serial' or whatever. Run ImpulseRC Driver Fixer, 'Unexpected number of devices found'. Other forums people reported having issues with solder blobs, so I took the stack apart and removed what looked like tiny hairs or something, probably not causing the issue, but you never know. Put it back together again, still no joy!

Finally saw someone mention the boot button. Plugged quad in while holding the boot button down for a bit. Then ran ImpulseRC... SUCCESS!

Betaflight still being funny tho, restarted PC... Okay now Betaflight can actually connect to the Quad. Time to update the firmware. So far, so good. Having trouble reading the inputs from the transmitter though. Looks like having done a clean firmware install, I need to reconfigure all that. Now I re-binded the quad, that's definitely sorted. But I cannot get the inputs to appear on the receiver page.

I've got my Ports configured as follows:
1676061872573.png


And here's what I have selected on the receiver page.
1676061450667.png

1676062173400.png


Can someone remind me how to get a Spektrum DX6i to talk to a Fury F4 S Flight Controller? I'm bound via a Spektrum FPV Racing Serial Receiver 3.3v Autobind, by the way.

My motor protocol is DSHOT600 as well, can't remember what I used to have it set as.
1676062144104.png
 

CappyAmeric

Elite member
Is your Spektrum receiver soldered to RX 1 on your flight controller?

What version of BetaFlight did you update to?
 

mastermalpass

Elite member
Is your Spektrum receiver soldered to RX 1 on your flight controller?

What version of BetaFlight did you update to?

The Fury F4S doesn't appear to have an RX1. The receiver is soldered to the same spot it's always been, three contacts opposite the USB port. I think I've drawn these on accurate to my set up.

Mamba_F405.png


I got a fresh install of Betaflight this evening. Windows 64bit, 4.4.0 I think, like you advised. Installs to program files and runs from my PC instead of being an app on Google Chrome, how long has it been like that for, then?
 

CappyAmeric

Elite member
The Fury F4S doesn't appear to have an RX1. The receiver is soldered to the same spot it's always been, three contacts opposite the USB port. I think I've drawn these on accurate to my set up.

View attachment 234756

I got a fresh install of Betaflight this evening. Windows 64bit, 4.4.0 I think, like you advised. Installs to program files and runs from my PC instead of being an app on Google Chrome, how long has it been like that for, then?

In BetaFlight, go to the Receiver tab, in the Serial Receiver Provider dropdown, select SPEKTRUM2048, reboot. Start your transmitter, connect a LIPO and move the sticks and see if your receiver is responding in the Receiver tab of BetaFlight.

Also, is your receiver model the SPM4650 or SPM4648? If the SPM4648, then it should be wired up to the 3.3v pad, not the 5v pad. The SPM4648 manual says "3.3v only".