Is the blue light supposed to be very bright on the USB adapter, mine I can barely see. Do these adapters go bad? Does the GUI work better on a pure windows 7 computer?
"Is the blue light supposed to be very bright on the USB adapter"
Not very bright at all until the drone connects.
1.) with USB plugged into the computer, but not the drone (or drone off), and GUI
not running, light should be off.
2.) with USB plugged into the computer, but not the drone (or drone off), but GUI
running, blue light should flicker about a second, off about a second, and repeat. And will be very dim.
3.) USB Plugged into both computer and drone, GUI running, and drone turned on, light should flicker constantly, and be a good bit brighter.
"
Does the GUI work better on a pure windows 7 computer? "
I don't really know. I've run it on a couple dozen machines in both Windows 7 and Windows 10, and never had an issue. The drivers should not have been an issue if your machine is a Windows 10. I think Windows 10 already has the right drivers installed. I don't recall having to install them in a long time.
I found SOME of the Initialization failure codes:
1.) Hi/lo, two short -
Compass failure
2.) Hi/lo, three short -
GPS unit, or any sub-part of the Unit
3/) Hi/lo, six short, followed by one or more "tic" sounds -
ESC failure. The tic sounds are 1 to 4, corresponding to the ESC failed on motor 1 to 4. I can hear Hi/lo and what appears to be 6 short in your video. My hearing is not all that great. Were the six shorts followed by any "tic" sounds?
It also appears that if more than one failure code exists, only the first one is sounded.
Did you have the top shell off between the last good flight and the first time the drone failed to initialize?
I ask because "cut wires" are a common problem when assembling a Q500 shell. The most common wire to get cut will prevent the GUI from connecting to the drone. Different cut wires would also result in the failure code of whatever component the wire serves.