Hello, I have a problem with the configuration of the motors, while I was configuring the direction the escs started playing, I was forced to flash with bheli because it was corrupted, once everything was done ok the only doubt I have is that when I go to test the motors after 2 minutes the 4 in 1 esc flashes red and sounds, i hope for lack of activity? or are there any problems? Thank you

I leave you the video

There is an "inactivity timeout" for ESCs after which beacon tones then start sounding, but it's usually defaulted to 10 minutes and I've only experienced it when leaving an ESC plugged in for 10 minutes without any activity and with no motors spinning. I've never tried leaving the motors spinning for such a long period of time from Betaflight Configurator with no transmitter connected to the receiver, so I don't know if it's normal under those conditions for the motors to just stop spinning and the ESC beacon to start sounding after the "inactivity timeout" period has elapsed.

In the BLHeli (or ESC-Configurator) software, what is the "Beacon Delay" value set to for your ESCs?

(10-Aug-2023, 12:15 PM)SnowLeopardFPV Wrote: There is an "inactivity timeout" for ESCs after which beacon tones then start sounding, but it's usually defaulted to 10 minutes and I've only experienced it when leaving an ESC plugged in for 10 minutes without any activity and with no motors spinning. I've never tried leaving the motors spinning for such a long period of time from Betaflight Configurator with no transmitter connected to the receiver, so I don't know if it's normal under those conditions for the motors to just stop spinning and the ESC beacon to start sounding after the "inactivity timeout" period has elapsed.

In the BLHeli (or ESC-Configurator) software, what is the "Beacon Delay" value set to for your ESCs?

Yes the timeout is 10 minutes, i attach the photo
I have noticed when this happens that the escs are no longer available and the red light flashes, 
I don't want to fly and after a while the escs turn off and fall, I could do a test and arm the quad with minimum throttle and see or in angle at 1 meter in height

My esc :

https://uav-en.tmotor.com/html/2019/ESC_0425/240.html

maybe this Beacon strength voice  number 6

There is definitely something up with your ESC. I just plugged in one of my 5" quads on the the bench which has a Hobbywing BLHeli_32 ESC in it and ran the same test as you by spinning the motors up from Betaflight Configurator with no transmitter connected (bound) to the receiver. My motors were still running after 12 minutes so I just manually stopped them myself. The Beacon Delay time on that quad has been set to 6 minutes, so the motors were still spinning well past that time and even well past what the normal default time of 10 minutes.

Some of your BLHeli_32 settings are different to mine but you are on version 32.7 while I am on version 32.9. That said, all of your BLHeli_32 settings except for a couple appear to be set to their default values for that ESC (text in bold shows non-default values) so I would assume them to be correct. I would suggest updating the ESC to 32.9 if you haven't already done so and try the test again.

If it continues then maybe some kind of protection mechanism is kicking in such as temperature protection and stopping the motors as a result, but motors running at idle with no props on shouldn't be causing the ESC to overheat unless the ESC has some kind of fault.

There are no settings in Betaflight which would cause that sort of behaviour.

Until you get to the bottom of the issue I certainly wouldn't advise flying that quad with that ESC in it.

For reference, here are the BLHeli_32 settings for the ESC in my quad...

Good morning I did some tests and completely resetting the esc with bheli32 and flashing again without maintaining the settings seems to have resolved, Tried for 12 minutes and it doesn't play anymore, I will do further tests in the next few days and see….