I've had this Falcon 130mm frame for quite some time and have almost started to build it several times. Really wanted to have it done before this past winter's indoor sessions. Have been torn contemplating what FC to use on it. I've thought about BrainFPV RE1, SPR F3 EVO with a SPR F3OSD, DTFc, BetaFlight F3, and several others along the way. Even started documenting the build once with an SPR F3 EVO and some other motors that ended up in OWL #1.
I've wanted to dabble in KISS but really didn't like the thought of having to jump through alot of the hoops I've heard about when flashing ESCs and FCs. Also heard there were driver compatibility issues between KISS and many other boards I use. Well, most of that appears to be in the past now, and with the release of the AIOv2, I finally took the leap and ordered the KISS CC. Seems like the frame and FC are a perfect match for each other. Will be making use of the T-Motor F20 4100kv motors that were in Owl #1 for a spell but have to lengthen the motor wires since I had shortened them and used individual ESCs on the owl. Still debating what direction to go for OSD/VTX Contemplating using the Diatone SP3 combo board that is configured and ready to complete BabyTri #2. Looks like another perfect match for this build. Then throw a Runcam Swift Mini on it and call it a day. Top and Bottom view of the boards:
KISS board showed up this week, and had to work through the initial "Uhhh, Hey Beavis, how do I get this thing to work?" moment. HAD to download DfuSeDemo in order to flash the firmware as the boards still do not ship with any firmware and the DFU driver that comes with that tool is also required. Managed to download it "without" using one of my spam users or email accounts. First click from the downloads section of flyduino took me to another site to download the files. That site tried to extract my whole life history, firstborn son, etc, but after doing a back arrow in my browser and clicking the link again, the file downloaded without providing any of the info. WOOT! I installed it, but "DID NOT" install the drivers (or the other "required" STM drivers for that matter). Instead, I waited until the board was detected by windows and let it automatically install the wrong driver. Next, I went into the device manager and FORCED it to the correct "OLD" DFU driver that is loaded into the program directory of DfuSeDemo. HOLY SMOKES IT WORKED! Driver conflicts avoided and I have verified that connections to all my other FCs and the KISS are working correctly. Uploaded firmware and now was able to connect via the KISS Gui. That leads to the next hurdle. Activation.... yeah, it didn't recognize the serial number of the board, which meant sending an email to flyduino telling them to make my board valid.... Half a day later, got email saying to try again. Activation successful and now able to configure the FC and flash the ESCs. I like to take build one step at a time and verify all parts work BEFORE starting the actual build. Saves time and energy of having to debuild/rebuild/repair/build several times. All pieces are working so on to the actual build...
More to come as the build progresses....
Cheers!
LitterBug
I've wanted to dabble in KISS but really didn't like the thought of having to jump through alot of the hoops I've heard about when flashing ESCs and FCs. Also heard there were driver compatibility issues between KISS and many other boards I use. Well, most of that appears to be in the past now, and with the release of the AIOv2, I finally took the leap and ordered the KISS CC. Seems like the frame and FC are a perfect match for each other. Will be making use of the T-Motor F20 4100kv motors that were in Owl #1 for a spell but have to lengthen the motor wires since I had shortened them and used individual ESCs on the owl. Still debating what direction to go for OSD/VTX Contemplating using the Diatone SP3 combo board that is configured and ready to complete BabyTri #2. Looks like another perfect match for this build. Then throw a Runcam Swift Mini on it and call it a day. Top and Bottom view of the boards:
KISS board showed up this week, and had to work through the initial "Uhhh, Hey Beavis, how do I get this thing to work?" moment. HAD to download DfuSeDemo in order to flash the firmware as the boards still do not ship with any firmware and the DFU driver that comes with that tool is also required. Managed to download it "without" using one of my spam users or email accounts. First click from the downloads section of flyduino took me to another site to download the files. That site tried to extract my whole life history, firstborn son, etc, but after doing a back arrow in my browser and clicking the link again, the file downloaded without providing any of the info. WOOT! I installed it, but "DID NOT" install the drivers (or the other "required" STM drivers for that matter). Instead, I waited until the board was detected by windows and let it automatically install the wrong driver. Next, I went into the device manager and FORCED it to the correct "OLD" DFU driver that is loaded into the program directory of DfuSeDemo. HOLY SMOKES IT WORKED! Driver conflicts avoided and I have verified that connections to all my other FCs and the KISS are working correctly. Uploaded firmware and now was able to connect via the KISS Gui. That leads to the next hurdle. Activation.... yeah, it didn't recognize the serial number of the board, which meant sending an email to flyduino telling them to make my board valid.... Half a day later, got email saying to try again. Activation successful and now able to configure the FC and flash the ESCs. I like to take build one step at a time and verify all parts work BEFORE starting the actual build. Saves time and energy of having to debuild/rebuild/repair/build several times. All pieces are working so on to the actual build...
More to come as the build progresses....
Cheers!
LitterBug
With the release of KISS V2, the whole procedure of flashing, gui, etc is changing, yet again. Playing with a V2 and quickly found that there is a need for a new 2.0 GUI. Firmware version: KISSFCV2F7-1.3RC32s S/N: ####3532-3####116-003##### (Activated). Flashing is no longer done with the funky DFUse utility for the V2. 
