03-Jul-2017, 12:53 AM
I have a highly modified EACHINE Wizard with Betaflight 3.1.6, the only part of the Wizard that I havent upgraded or changed is the frame, the Matek PDB, and the SP Racing F3 Flight Controller. As the title states, I am having issues with my X6B receiver all of a sudden.
Up until today, I have had no issues for months. I use the Flysky FS-I6X Controller with X6B Receiver using IBUS in UART3 on my SP Racing F3 FC. Under the RX tab within my FS-I6X controller there are 2 options in regards to "sensors," I assume this is telemetry options? One option is "List Sensors" and lists the sensors that are detected as well as shows their corresponding values in real time. It listed maybe 6 sensors or so, all of which seemed to be working properly and accurately. The other option is "Choose Sensors" which lets you choose any 3 of the sensors listed in the previous menu to be displayed on the Main flight screen of my I6X. Up until today I have always had TX Voltage and RSSI Displayed and everything worked great. Today I thought I went to view the available sensors to see what other info was available to me purely out of curiosity. Some of the sensors I was clueless to what they are displaying. So I chose RSSI, TX Voltage, and Ext Voltage as the sensors to be displayed. I wanna say EXT Voltage is battery voltage but I could be wrong. I then powered everything off to run to the store. When I got back, my controller and transmitter could no longer communicate whatsoever. No info, as far as the sensors go, was being received by my controller. No signal strength. I could not arm my quad or do anythkng for that matter. I also tried to rebind my transmitter and receiver many times which did not work at all. I then had to leave for work. I know my FS-I6X is fine as my Tiny Whoop still works great.
So my quesion is, does anyone know if certain sensors, when selected, interfere with normal operation of the X6B causing zero connection between TX and RX? Powering on and off does nothing, binding does nothing, the only thing I have not tried is changing the Displayed Sensors back to what they were or to different ones. The receiver is getting power and correct voltage. It wouldn't really make much sense if I selected a sensor to be displayed that caused this issue as on the "List Sensors" screen it shows all of them, functioning at the same time, with their realtime data reading. So if this is the case, that means they all work fine but only certain ones can be displayed on the home screen.
I will be home in a few hours and plan on switching the displayed sensors back to what they were to see if this fixes it but I would be shocked if it did as it wouldn't make much sense.
I made 2 other alterations I made between it working fine and not working in Betaflight. I changed small_angle to 180 so i could arm in a tree when it happens again and the voltage was reading .1 low so i bumped it up 1. That way Betaflight got a more accurate reading of the battery voltage. After shit stopped working I changed both of those back to their defaults and it did nothing to fix it as I predicted.
Any ideas or help would be greatly appreciated. I could care less about telemetry on my controller. I was purely curious about the other sensors and how their value s would change. Now I just wanna be able to rip some packs like the rest of us.Thanks for any information, help, or ideas.
Up until today, I have had no issues for months. I use the Flysky FS-I6X Controller with X6B Receiver using IBUS in UART3 on my SP Racing F3 FC. Under the RX tab within my FS-I6X controller there are 2 options in regards to "sensors," I assume this is telemetry options? One option is "List Sensors" and lists the sensors that are detected as well as shows their corresponding values in real time. It listed maybe 6 sensors or so, all of which seemed to be working properly and accurately. The other option is "Choose Sensors" which lets you choose any 3 of the sensors listed in the previous menu to be displayed on the Main flight screen of my I6X. Up until today I have always had TX Voltage and RSSI Displayed and everything worked great. Today I thought I went to view the available sensors to see what other info was available to me purely out of curiosity. Some of the sensors I was clueless to what they are displaying. So I chose RSSI, TX Voltage, and Ext Voltage as the sensors to be displayed. I wanna say EXT Voltage is battery voltage but I could be wrong. I then powered everything off to run to the store. When I got back, my controller and transmitter could no longer communicate whatsoever. No info, as far as the sensors go, was being received by my controller. No signal strength. I could not arm my quad or do anythkng for that matter. I also tried to rebind my transmitter and receiver many times which did not work at all. I then had to leave for work. I know my FS-I6X is fine as my Tiny Whoop still works great.
So my quesion is, does anyone know if certain sensors, when selected, interfere with normal operation of the X6B causing zero connection between TX and RX? Powering on and off does nothing, binding does nothing, the only thing I have not tried is changing the Displayed Sensors back to what they were or to different ones. The receiver is getting power and correct voltage. It wouldn't really make much sense if I selected a sensor to be displayed that caused this issue as on the "List Sensors" screen it shows all of them, functioning at the same time, with their realtime data reading. So if this is the case, that means they all work fine but only certain ones can be displayed on the home screen.
I will be home in a few hours and plan on switching the displayed sensors back to what they were to see if this fixes it but I would be shocked if it did as it wouldn't make much sense.
I made 2 other alterations I made between it working fine and not working in Betaflight. I changed small_angle to 180 so i could arm in a tree when it happens again and the voltage was reading .1 low so i bumped it up 1. That way Betaflight got a more accurate reading of the battery voltage. After shit stopped working I changed both of those back to their defaults and it did nothing to fix it as I predicted.
Any ideas or help would be greatly appreciated. I could care less about telemetry on my controller. I was purely curious about the other sensors and how their value s would change. Now I just wanna be able to rip some packs like the rest of us.Thanks for any information, help, or ideas.