I have a DYS 250 folding drone and a Flysky FS-I6X transmitter. I did the binding to the receiver and drone. I ran through the LibrePilot setup for the drone, but when I attempted to set up the transmitter LibrePilot did not see the transmitter. It showed no activity no matter what I did. Is there some loophole that I can jump through to get the transmitter setup to fly the drone? Thanks.
Transmitter issues.
- Thread starter RGMacken
- Start date
Dugdog47
Well-Known Member
Things to check:
1. Is your reciever getting power?
2. Is the reciever bound to the transmitter?
3. Is the reciever connected to a uart on the f.c.?
I've never used LibrePilot but assuming it's like betaflight:
4. In the ports tab click the correct switch for uart that reciever is connected to. (serial rx.)
5. In configuration tab click serial reciever and then click ibus in the drop down window.
1. Is your reciever getting power?
2. Is the reciever bound to the transmitter?
3. Is the reciever connected to a uart on the f.c.?
I've never used LibrePilot but assuming it's like betaflight:
4. In the ports tab click the correct switch for uart that reciever is connected to. (serial rx.)
5. In configuration tab click serial reciever and then click ibus in the drop down window.
1: Receiver is plugged in to the battery pack and also the computer.
2: The transmitter is bound to the receiver and shows that it is connected to the receiver when turned on.
3:My guess is that it is connected.
4:, 5: I’ll have to do a little more looking at the settings.
On my first attempt I was able to complete the throttle setting, but then nothing with the rest. Now there is nothing at all showing on the transmitter.
2: The transmitter is bound to the receiver and shows that it is connected to the receiver when turned on.
3:My guess is that it is connected.
4:, 5: I’ll have to do a little more looking at the settings.
On my first attempt I was able to complete the throttle setting, but then nothing with the rest. Now there is nothing at all showing on the transmitter.
wafflejock
Well-Known Member
I started off with librepilot/openpilot and cc3d hardware but it's been a few years so I don't recall what the configuration was like really, feel like there were wizards that helped get stuff setup but agree way easier to help on betaflight.
Okay so I put the SP racing F3 board in with cleanflight. I can’t get the boot loader patch to apply to the cleanflight. In fact I can’t even find it after I spent the time to download it. I’m about to take a hammer to the drone and forget playing with any bind and fly set ups!
wafflejock
Well-Known Member
Some of the FCs can be more or less of a pain when it comes to getting them into bootloader or Device Firmware Upgrade mode where they are ready to accept a firmware upgrade, what particular FC do you have (link if possible) there is a good chance there is a boot button or two pads you need to short while powering it up to get into DFU mode. Lots of the newer ones will either have a boot button or ability to control rebooting into DFU mode via USB and so don't require the button or pulling some pin on the MCU low during boot.
Once the firmware is flashed the saving config part should work without any hassle but initial firmware writing can be a small nightmare no doubt.
Once the firmware is flashed the saving config part should work without any hassle but initial firmware writing can be a small nightmare no doubt.
wafflejock
Well-Known Member
Okay so the FC is connected to computer via USB and you can connect from the configurator but then from there you see no input on the receiver tab? Also safe to assume the receiver is powered and did binding to the remote and shows some indication when the transmitter is on vs off and powering the receiver up (confirmed binding)? If so the two other things I think need to be set are the UART being used for the receiver and the protocol the receiver uses. I'm primarily used to using betaflight so it's possible there are some other parts, but in betaflight once those two things are set and saved the receiver tab begins to show some sort of input then just need to fix the mapping and rxrange typically.
Correct the transmitter is bound to the receiver and the FC is connected to the computer. I have tried to flash the FC, but it shows an issue with the Bootloader. I’ve done the download of the Zadig and the other download, but I’m not sure how to apply it to the cleanflight program to make it function.
wafflejock
Well-Known Member
Okay so if the cleanflight configurator can't connect then it wasn't flashed from the factory with cleanflight or at least not a version compatible with the configurator you have installed if you bought it recently then it might have betaflight flashed on it as well.
The driver installation is for your OS to be able to make a serial connection that the configurator apps can use. Basically the way the FCs work they have a STM32 chip at their core (generally a black plastic square looking chip with lots of pins around it called a QFP), that STM32 chip only speaks some old school serial protocols natively so there is another chip on there, believe on the SP Racing F3 board it's a Silicon Labs chip that does the serial communication so you need the Silicon Labs driver most likely for the device to show up as a regular Serial port with a COM port.
Looks like some pretty good instructions via video here, once you have the USB drivers installed you should be able to see the COM port in the device manager show up when you plug in the device, if that part is working then should be set to try flashing firmware:
The one below also shows flashing with betaflight
Can see in comments of second vid some people working out issues on getting the virtual com port to show up to connect to the device all about getting the right USB drivers installed and having that show up in device manager then you should be in good shape it looks like
The driver installation is for your OS to be able to make a serial connection that the configurator apps can use. Basically the way the FCs work they have a STM32 chip at their core (generally a black plastic square looking chip with lots of pins around it called a QFP), that STM32 chip only speaks some old school serial protocols natively so there is another chip on there, believe on the SP Racing F3 board it's a Silicon Labs chip that does the serial communication so you need the Silicon Labs driver most likely for the device to show up as a regular Serial port with a COM port.
Looks like some pretty good instructions via video here, once you have the USB drivers installed you should be able to see the COM port in the device manager show up when you plug in the device, if that part is working then should be set to try flashing firmware:
The one below also shows flashing with betaflight
Can see in comments of second vid some people working out issues on getting the virtual com port to show up to connect to the device all about getting the right USB drivers installed and having that show up in device manager then you should be in good shape it looks like