![]() Every manufacturer implements RSSI in a different way. The same values don't necessarily mean anything for other manufacturer receivers. That's because OpenTX is heavily sponsored by FrSky. (1, 08:34 PM)SnowLeopardFPV Wrote: The RSSI alarms in OpenTX are arbitrary values and generally reflect what low RSSI values on FrSky receivers are the danger zones. What are these numbers? When I'm far away and RSSIdBm is -100 and RSSI 25% then the alarms are not triggered.Ĭould anyone explain me what these 45 and 42 mean? How they relate to BetaFlight OSD RSSIdBm or RSSI? Nice.īetaFlight OSD has RSSIdBm and it perfectly corresponds to Crossfire Nano 1RSSI sensor (I guess that it is just reading of that sensor)īetaFlight OSD also has RSSI (in %) which I also understand - 0% is -130dBm (minimum sensitivity for Crossfire Nano) and 100% is something like 0dBm (aka 1mW), this is also described in Crossfire manual:įor example when RSSIdBm is -65 then RSSI is 50% which makes perfect sense to me.īut what I don't understand are the default 45 and 42 RSSI alarms in OpenTX. I understand what is dBm it is simply a projection of mW onto exponential function and thanks to that it maps huge range between 1×1039 W - 0.056 zW to a human readable numbers (-192.5) - 420. If you need to install the gi.I'm testing limits of my Tango 2 + Crossfire Nano. GLib.timeout_add_seconds(discovery_time, end_discovery) """Write device and rssi values to a log file"""ĭev_log.write(f'Device seen) ![]() You could modify the code to take an action when a particular address and RSSI value is found. This example scans for 60 seconds and writes the device address and RSSI value to a file. In the example below I have used pydbus as the library to access BlueZ's D-Bus API. Getting the RSSI value on a Raspberry Pi is supported by the BlueZ device API.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |