Use impulse rc driver fixer with kiss gui windows#If you plug in a new one and Windows happens to pick the wrong driver, then things get difficult. Somehow it seems that the each Kiss FC is treated as a different device and has to have the correct driver linked to it. I found a different laptop that would connect to it. Use impulse rc driver fixer with kiss gui drivers#I'm not exactly sure how Windows maps drivers to devices, but I've had problems where my normal field laptop connects to several Kiss V1s without problem, but wouldn't connect to another V1. It's only the V2 with the F7 chip that avoids that. Yeah, the CC is still F3 and requires DFU mode. That was the only way I got it to connect It runs fine now. What did work in the end was to use the Win8 STM, Virtual Com Port driver on the Win7 machine. I tried this on two Win7 machines a 32bit and 64bit but nothing worked. I recently bought an KISS CC (AIO) and it absolutely refused to connect to the GUI, no new port was ever detectedīy the GUI, although a KISS V1 worked perfectly and several other FC's of different types all worked perfectly in BF. The Chrome-app won't work on any of the newer devices or firmware. If you have done this, you will likely have to delete the driver that is currently associated with the Kiss V2 and then try connecting from scratch.Įdit: also make sure you are using the latest stand-alone GUI. Generally that will do exactly the wrong thing - it will change the driver to that needed by most BF boards. To my knowledge there is no way (and certainly no value) to connect vi the BF configurator.Įdit: do not use the Impulse RC driver fixer. Use impulse rc driver fixer with kiss gui windows 7#I have found that Windows 7 automatically does it correctly, but I think on a Mac you might have to do it manually. You do need the right driver associated with the device. Not impossible, but certainly a lot more effort than the V2. The V1 still flies awesome, but there you need to boot into DFU mode and use DfuseDemo to load hex files. In my opinion this is the single biggest advantage of the V2 over the V1. The new GUI will connect and flash new firmware directly. He has a V2, so you do not need DFU mode. If you've never done it before it can be daunting, but it gets easier There's other info but that to start, should get you on the right track. Open to see if the device is running and in the correct mode without any issues. Unless the drivers are working correctly nothing will ever happen, that's why you need to have Device Manager Then follow the BF instructions on the Firmware Flasher tab / page. With BF and Hex files you still need to be in DFU mode. See Philipp Seidel flashing tutorial here ~ If there is an error of any kind you need to sort out the driver first, run the driver in the STM folder, Win Prog-Files. In device manager (Win) it must show as a new device in DFU mode, without errors (yellow triangle etc) And get the Virtual Com Port driver as well, the STMicroelectronics one, links are all there. dfu file.Įnter with Boot pins shorted or Button pushed at power-up.Then you'll need DeFuse Demo from STM. You need the device in DFU mode (bootloader) to Flash stuff into it, the.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |