22-Aug-2020, 08:20 PM (This post was last modified: 22-Aug-2020, 08:21 PM by alexsidles.)
I have a similar issue to user Octo from the May 17 2020 thread "Tinyhawk 2: Is it bricked?" However, there are enough differences that I thought I would ask in a new thread.
After my Tinyhawk 2's moderate crash onto grass, FPV continued to work, but the FC would no longer boot correctly. When I plug in a battery to the FC, I get a partial boot: there are three beeps, followed by two blue lights, six green lights, and a red light. The light cycle repeats once, then all lights cease. The three beeps do not repeat. There is no additional sequence of beeps (as there would be during a full boot). Replacing fresh batteries does not change any of this.
Once the FC's partial boot is complete, the drone's rotors do not start. I cannot arm the drone. After a while, even FPV connectivity was lost and once lost could not be restored. Once FPV connectivity was lost, the headset just showed static. Replacing fresh batteries does not change any of this.
At one point, I plugged in a fresh battery and got the same partial boot (three beeps, light cycle, then nothing). But then, the rotors started to spin very, very slowly—perhaps 90 RPM (slow enough to track the individual blades by eye while they rotated). I was worried I might be causing damage, so I unplugged the battery from the FC. When I plugged a fresh battery into the FC, all I got was the same partial boot but no further movement in the rotors or any other component.
Plugging the FC into a computer via USB does not work. BFC does not recognize the FC as an FC once the FC is plugged into the computer. The computer does not appear to recognize the FC as a USB device. No lights or beeps come on the FC when I plug it in to the computer via USB. The FC is totally non-responsive to being plugged in via USB. It also does not work to hold down the FC's power button while plugging the FC into a computer via USB.
I unscrewed the FC to investigate. All components appear to be properly soldered into place. Like user Octo, there is a small, chipped component on the FC—in fact, the exact same damaged component Octo had on his FC. I will try to attach a picture below, with a yellow arrow pointing to the chipped component.
Any thoughts on what could be the matter?
Thanks,
Alex
After my Tinyhawk 2's moderate crash onto grass, FPV continued to work, but the FC would no longer boot correctly. When I plug in a battery to the FC, I get a partial boot: there are three beeps, followed by two blue lights, six green lights, and a red light. The light cycle repeats once, then all lights cease. The three beeps do not repeat. There is no additional sequence of beeps (as there would be during a full boot). Replacing fresh batteries does not change any of this.
Once the FC's partial boot is complete, the drone's rotors do not start. I cannot arm the drone. After a while, even FPV connectivity was lost and once lost could not be restored. Once FPV connectivity was lost, the headset just showed static. Replacing fresh batteries does not change any of this.
At one point, I plugged in a fresh battery and got the same partial boot (three beeps, light cycle, then nothing). But then, the rotors started to spin very, very slowly—perhaps 90 RPM (slow enough to track the individual blades by eye while they rotated). I was worried I might be causing damage, so I unplugged the battery from the FC. When I plugged a fresh battery into the FC, all I got was the same partial boot but no further movement in the rotors or any other component.
Plugging the FC into a computer via USB does not work. BFC does not recognize the FC as an FC once the FC is plugged into the computer. The computer does not appear to recognize the FC as a USB device. No lights or beeps come on the FC when I plug it in to the computer via USB. The FC is totally non-responsive to being plugged in via USB. It also does not work to hold down the FC's power button while plugging the FC into a computer via USB.
I unscrewed the FC to investigate. All components appear to be properly soldered into place. Like user Octo, there is a small, chipped component on the FC—in fact, the exact same damaged component Octo had on his FC. I will try to attach a picture below, with a yellow arrow pointing to the chipped component.
Any thoughts on what could be the matter?
Thanks,
Alex