You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using https://github.com/zs6buj/MavlinkToPassthru in relay mode. Discovering sensors results in two RSSI sensors, one provided by M2P and one provided by my RXSR. If I delete the RXSR sensor, it is still used as the rssi source in the telemetry script, despite the only existing RSSI sensor being the one provided by M2P (instance 28). Confirmed by wrapping tin foil around my 2.4ghz antenna - rssi drops massively.
I tried rebooting all hardware and changing models to make sure it wasn't a caching issue. Issue persists.
The text was updated successfully, but these errors were encountered:
Hi, the script has no direct access to OpenTX rssi sensors, I simply use the getRssi() function, no idea why it would return a value not "there" anymore, doen't make sense at all!
Apparently, the "rssi source" setting in the telemetry tab of opentx does more than just the rssi source for alarms.. oops.. configuration issue on my end. I'll add this to the docs for m2p.
I am using https://github.com/zs6buj/MavlinkToPassthru in relay mode. Discovering sensors results in two RSSI sensors, one provided by M2P and one provided by my RXSR. If I delete the RXSR sensor, it is still used as the rssi source in the telemetry script, despite the only existing RSSI sensor being the one provided by M2P (instance 28). Confirmed by wrapping tin foil around my 2.4ghz antenna - rssi drops massively.
I tried rebooting all hardware and changing models to make sure it wasn't a caching issue. Issue persists.
The text was updated successfully, but these errors were encountered: