#Nomad as RX - ELRS.lua does not show "OTHER DEVICES"

53 messages · Page 1 of 1 (latest)

full cobalt
#

I reflashed my RM Nomad as RX by copying the nomad TX target json file and editing the RX/TX to 3/1. After referencing the correct RX unified firmware, it is working fine. The TX and RX are communcating and there is RC outputs detected on the flight controller.

What I currently have an issue is that when using the ELRS script on the transmitter, the "other devices" sub-menu is missing as I want to adjust the power output.

hushed quailBOT
# full cobalt I reflashed my RM Nomad as RX by copying the nomad TX target json file and editi...

✨AI-Generated response✨

I am not familiar with the RadioMaster Nomad as an RX. The "Other Devices" option in the ELRS Lua script is used to change the configuration of connected devices e.g. the receiver module. The lack of "Other Devices" can be caused by the lack of TX Backpack functionality. Please see the Backpack Info for for a list of currently supported devices.


-# {'cause': 'thread creation'}

abstract lark
full cobalt
#

i cannot change it as it is in mavlink mode

#

2:1

abstract lark
full cobalt
#

it is super weird everything works except for other devices including putting the RX into wifi mode

#

the LUA script has been updated and everything is running 3.5.4

abstract lark
#

are you seeing a C in the top right corner of the expressLRS Lua Script?

full cobalt
#

yes

#

0/333

#

it is in 333 full mode as a simple baseline

abstract lark
#

I don't really care about that..

#

I'm just asking for that C in the top right-most corner

full cobalt
#

it has the C

abstract lark
#

so closing the lua script and relaunching it over again doesn't show "Other Devices"?

full cobalt
#

no

#

and cycling the power doesnt change things

#

this transmitter has that option when running other recievers

abstract lark
#

what if you set the TX back to Normal Mode, instead of MAVLink?

#

likewise, set the receiver into CRSF mode, via the webUI..

#

then let them connect/sync, change settings and THEN put both back into MAVLink mode

full cobalt
#

ill have a check

#

no joy

#

same behaviour

abstract lark
#

that's awfully quick

full cobalt
#

and checked it with a power cucle

#

yea i have it all setup in front of me

abstract lark
#

including putting receiver into wifi mode and setting the protocol back to CRSF?

full cobalt
#

yes i have a uart connectoin to reflash the firmware

#

it is a bench setup

abstract lark
#

who said anything about reflashing firmware?

full cobalt
#

yea sorry i missed a few steps

#

i flash to set the wifi to 1 seocnd time out so i can get to it really fast and reflash again

abstract lark
full cobalt
#

i have a script that does it so hbit

abstract lark
#

but reflashing doesn't change the protocol settings on the receiver.. unless you reflash via uart with erase before flash enabled

#

Receiver sending back telemetry is all it needs to show the "Other Devices"

full cobalt
abstract lark
# full cobalt

is "Force Telemetry" disabled?
though if there's a C in the top right corner, then it should be disabled already

full cobalt
#

i am typing too fast and being confusing so i think the pictures will be easier

abstract lark
full cobalt
#

another nomad

#

on a rm pocket

abstract lark
full cobalt
#

pocket -> nomad -> nomad -> px4 (mavlink)

#

i have tried both 3.75 and 5.25M

abstract lark
#

set it to 5.25M.. if that still doesn't do it, then I've no other idea..

full cobalt
#

it is currently set to 5.25

#

😦

lyric olive