The
Graphical
User
Interface is a generic term for the configuration software for whatever
Multirotor
Flight
Controller (also a generic term) you may be using; the USBasp is the little dongle itself.
In a nutshell, The USBasp is this: a generic USB> Serial Adapter connected to an Atmel microprocessor which is itself flashed with a bootstrap program which allows it to load a firmware file into itself, then send that firmware file out over the ribbon cable to another Atmel microprocessor so it can be flashed with updated Firmware (The "OS" and "Application Software" of the controller combined into one big bit of code) which addresses bug-fixes and adds new functionality. The USBasp is the most popular "dongle" for programming Atmel microprocessors; the SiLabs Programming Stick is a similar device for their products, but you can even program a plain-jane Arduino to do the same thing for either family.
This interface can ALSOact as a serial communications "Bridge" to the processor's non-volatile memory or NVRAM (A tiny bit of solid-state "hard-drive" storage where things like your configuration settings for the MFC or in the case of my 9XR transmitter, where my actual model profiles are stored); so that things can be modified in an application, then "written" to the NVRAM so that the whole new configuration replaces the existing one. As soon as you reboot, the new settings are there. The GUI makes it all pretty transparent once you get the USBasp talking to your computer; it's just a matter of ticking off settings then clicking "Update" to send that to the MFC.
Most of them can even be programmed in a live setting, so you can be working on the thing on your bench and bench-test while observing live data from the MFC. The whole thing is a LOTlike using an OBDIIscanner on your car, only the people who make this stuff don't have to contend with car manufacturers trying to hide everything you want to work with.
mnem
