Hi Guys!

I am a rookie.

I built this myself and it works just fine, except When I apply hard roll it disconnects.

I had broken the first frame, so I order a new one. When i out to tested it in low altitude and the problem is still there. 

I have included the blackbox file, and also a screenshot from my BLHeli. 

https://www.dropbox.com/s/4q2iczhvw2w0r5...6.BBL?dl=0       <<<<<BLACKBOX FILE       




Thank you. 

What disconnects? Your receiver, your VTX feed? What exactly? We need some more specifics.

The blackbox log you uploaded isn't for a flight so is no use unfortunately. It's just for an arm followed by a disarm 1.5 seconds later while still on the ground.

(22-Jan-2020, 02:20 AM)SnowLeopardFPV Wrote: What disconnects? Your receiver, your VTX feed? What exactly? We need some more specifics.

The blackbox log you uploaded isn't for a flight so is no use unfortunately. It's just for an arm followed by a disarm 1.5 seconds later while still on the ground.

I am looking through the goggles,  and when I apply the roll the screen goes black. So I don't know what it is exactly that disconnects. 

All I know is the screen goes black and the quad drops.

is it in „hard rolls“ when you add zero throttle during the flip?
if yes, it could be the „low idle throttle“. i had this problem.
if one prop start to spin backwards to the force of the air and the roll, the esc cant bring it to turn in the right direction, cant recover. (the fc would send 100% th-command but the esc cant handle the situation probably there will be no power for the other parts, causing a blackscreen, not sure about if the blackscreen could be a result of low idle value aswell.)

i didnt watch the logfile, i couldnt watch it directly online, i didnt download. it would be visible if one esc going to 100% throttle output after a low (zero) throttle input and the fallout of the sky comes directly after.

(22-Jan-2020, 12:58 PM)hugnosed_bat Wrote: is it in „hard rolls“ when you add zero throttle during the flip?
if yes, it could be the „low idle throttle“. i had this problem.
if one prop start to spin backwards to the force of the air and the roll, the esc cant bring it to turn in the right direction, cant recover. (the fc would send 100% th-command but the esc cant handle the situation probably there will be no power for the other parts, causing a blackscreen, not sure about if the blackscreen could be a result of low idle value aswell.)

i didnt watch the logfile, i couldnt watch it directly online, i didnt download. it would be visible if one esc going to 100% throttle output after a low (zero) throttle input and the fallout of the sky comes directly after.

Well not necessary a hard roll, but I have never been able to finish a 360 roll. The throttle is how ever on zero when this happens. 

As I mentioned I am really new at this, what type of information can I provide from betaflight perhaps that can help to better identify the problem ?

a dumpfile could give informations, you can run dump in the cli and copypast it here.
a dvr footage could help

(otherwise what i did mention about, you can post your „throttle idle value“, its in the configurations tab at esc settings. what esc protocoll do you use? did you enable motor_stop? this would be visable from the „dump“ aswell)

(22-Jan-2020, 03:12 PM)hugnosed_bat Wrote: a dumpfile could give informations, you can run dump in the cli and copypast it here.
a dvr footage could help

(otherwise what i did mention about, you can post your „throttle idle value“, its in the configurations tab at esc settings. what esc protocoll do you use? did you enable motor_stop? this would be visable from the „dump“ aswell)

„set dshot_idle_value = 550
set dshot_burst = ON
set dshot_bidir = OFF
set dshot_bitbang = AUTO
set dshot_bitbang_timer = AUTO
set use_unsynced_pwm = OFF
set motor_pwm_protocol = DSHOT600“
seems like it shouldnt be what i mentioned, sry. 550 is the default value. increase it shouldent be the reason, only if you would have very low powered motors or to heavy props for the motor...

(22-Jan-2020, 02:20 AM)SnowLeopardFPV Wrote: What disconnects? Your receiver, your VTX feed? What exactly? We need some more specifics.

The blackbox log you uploaded isn't for a flight so is no use unfortunately. It's just for an arm followed by a disarm 1.5 seconds later while still on the ground.

Snow would love to know your opinion on this also.

(23-Jan-2020, 10:19 AM)Seanalami Wrote: Snow would love to know your opinion on this also.

It would be helpful if you have a blackbox log of the actual flight. The one you uploaded unfortunately wasn't for a flight so you probably picked the wrong file. Have a look to see if any of the other log files have any actual flight data in them.

In the meantime, inspect all of your solder connection really carefully with a magnifying glass for poor or dry joints, or where there is a risk of a potential short between wires. Also look for any foreign objects on the circuit board and between pins of components that could cause an intermittent momentary short somewhere. Maybe post some pictures of your wiring / solder joints if you want a second opinion. The fact that the picture goes out and the quad just drops to the ground, it sounds likely that there is either momentary power starvation (brownout) to some of the electronics, or a complete power loss. A blackbox log should show something which helps to identify that.

(23-Jan-2020, 10:36 AM)SnowLeopardFPV Wrote: It would be helpful if you have a blackbox log of the actual flight. The one you uploaded unfortunately wasn't for a flight so you probably picked the wrong file. Have a look to see if any of the other log files have any actual flight data in them.

In the meantime, inspect all of your solder connection really carefully with a magnifying glass for poor or dry joints, or where there is a risk of a potential short between wires. Also look for any foreign objects on the circuit board and between pins of components that could cause an intermittent momentary short somewhere. Maybe post some pictures of your wiring / solder joints if you want a second opinion. The fact that the picture goes out and the quad just drops to the ground, it sounds likely that there is either momentary power starvation (brownout) to some of the electronics, or a complete power loss. A blackbox log should show something which helps to identify that.

Thanks Snow, The soldering has no problem I'm sure of that. 

How do I provide you with the right blackbox log ?

I meant the wiring between the PDB/ESC and the FC, but I can see you have the T-Motor F4 stack which connects together using a T-Motor supplied wiring harness. Re-seat the two connectors by unplugging and re-plugging them, and while you have them disconnected, check for any bent or deformed pins inside the connector sockets.

As for getting the correct blackbox logs, it could prove difficult locating the exact one if you've never cleared any logs off the internal flash memory because they don't usually get given a proper date/time. I usually clear all blackbox logs from my SD card / flash memory before I go on a flying session and then copy them all off when I get back home so I have a folder on my computer containing all the logs that are only for that flying session only. How many logs do you have on the flash memory? If it's not too many then you could upload them all and we could try going through them systematically to see if we can find one that exhibits your reported problem.

(23-Jan-2020, 02:46 PM)SnowLeopardFPV Wrote: I meant the wiring between the PDB/ESC and the FC, but I can see you have the T-Motor F4 stack which connects together using a T-Motor supplied wiring harness. Re-seat the two connectors by unplugging and re-plugging them, and while you have them disconnected, check for any bent or deformed pins inside the connector sockets.

As for getting the correct blackbox logs, it could prove difficult locating the exact one if you've never cleared any logs off the internal flash memory because they don't usually get given a proper date/time. I usually clear all blackbox logs from my SD card / flash memory before I go on a flying session and then copy them all off when I get back home so I have a folder on my computer containing all the logs that are only for that flying session only. How many logs do you have on the flash memory? If it's not too many then you could upload them all and we could try going through them systematically to see if we can find one that exhibits your reported problem.

Yes correct, the Whole stack is brand new. No soldering was needed even to connect the FC to the Air Unit. I simply connected the sockets and I had this problem ever since I started flying it. And maybe I have flown with it maybe 5 times total. 


I have never cleared logs in the BlackBox. I have never attempted even on saving a log from it, the only time was when I did it at the beginning of this post. Which you said It isn't for a flight. 

Could you kindly tell me; How do I save a flight log ?

Keep in mind that blackbox logs don't get deleted automatically from the blackbox SD Card or blackbox flash memory on your FC, so if all the space gets used up, no more log files will get written. So if you have blackbox logging permanently switched on (which I do), then you need to at least do some manual housekeeping once in a while and delete any logs that you no longer need.

This is my procedure for keeping a record of my flights:-

1. As part of me pre-flight preparation before I leave the house to go on a flying session, I delete any DVR footage on the SD Card of my goggles and I also delete any blackbox logs that are present on the blackbox data SD card (or in the FC's blackbox flash memory). Any new logs created from that point on will start back at log file number 00001.
   
   
2. For every flight I do, I record it using the DVR of my goggles. When you disarm the quad at the end of a flight or if it has a  failsafe, one of the items that appears in the statistics page on the OSD at the end is the blackbox log file number. This allows me to correlate each blackbox log file to specific flight.
   
   
3. When I get home, as part of my post-flight procedure, I copy all the DVR footage into a dated folder on my computer along with all the blackbox log files for that flying session. This means that if any of the flights had an issue I have the footage and I know exactly which blackbox log file relates to it.
   

Did you record DVR footage of the flight where you had issues? If you did, fast forward to the end where the stats screen appears and look to see what the "BB LOG NUM" is which will be the number of the blackbox log file for that particular flight. In the example screen shot below, you can see the blackbox log file for that flight was #5.

(24-Jan-2020, 12:21 PM)SnowLeopardFPV Wrote: Keep in mind that blackbox logs don't get deleted automatically from the blackbox SD Card or blackbox flash memory on your FC, so if all the space gets used up, no more log files will get written. So if you have blackbox logging permanently switched on (which I do), then you need to at least do some manual housekeeping once in a while and delete any logs that you no longer need.

This is my procedure for keeping a record of my flights:-

1. As part of me pre-flight preparation before I leave the house to go on a flying session, I delete any DVR footage on the SD Card of my goggles and I also delete any blackbox logs that are present on the blackbox data SD card (or in the FC's blackbox flash memory). Any new logs created from that point on will start back at log file number 00001.
   
   
2. For every flight I do, I record it using the DVR of my goggles. When you disarm the quad at the end of a flight or if it has a  failsafe, one of the items that appears in the statistics page on the OSD at the end is the blackbox log file number. This allows me to correlate each blackbox log file to specific flight.
   
   
3. When I get home, as part of my post-flight procedure, I copy all the DVR footage into a dated folder on my computer along with all the blackbox log files for that flying session. This means that if any of the flights had an issue I have the footage and I know exactly which blackbox log file relates to it.
   

Did you record DVR footage of the flight where you had issues? If you did, fast forward to the end where the stats screen appears and look to see what the "BB LOG NUM" is which will be the number of the blackbox log file for that particular flight. In the example screen shot below, you can see the blackbox log file for that flight was #5.

First off; Thank you for the detailed and quick response. 

I own DJI goggles, so no OSD.

This is what I am going to do and please correct if me if Im wrong; 

1. I am going to erase the current logs
2. I will take her out in the field, fly low altitude and attempt the spin.

This way we will have new data and its only data there. And currently I only Have sd card inside the air unit, do you suggest otherwise ?