Storing RX ID ?

Hi,

I started having a look at the FlySky AFHDS 2A protocol
www.deviationtx.com/forum/protocol-devel...l-as-used-i10-i6-it4

RX ID (32 bit) needs to be stored on the TX after bind, how can I store it ?
I thought of protocol options, but that's not very clean, do we have another way to store values ?

why are protocol options the wrong place? this seems like an ideal place to me. I assume there is no reason to view this value? We should enhance the protocol options to have a non-visible storage, which you could then use. Alternatively, can the fixedid be used for this value? Do we need both a fixed-id and a Rx-Id?

Yes, that would be better to hide it.

RX ID is sent by the RX at bind time then it needs to be sent by the TX in every packets.

Then it is the fixed id...

No, a TX ID is also required.
www.deviationtx.com/forum/protocol-devel...6-it4?start=20#46630

Oops!

Sorry to revive this thread, but I need a solution for that.

Until now I used protocol options to store RXID for my afhds2a test builds but there're some issues with that:
- it shouldn't be user modifiable
- I need to store a 32 bit value, looks like only 16 bit (int16_t) can be used for option items so:
- I've to use 2 16 bit values, this is becoming a problem because:
- that takes 2 protocol option "slots", which are limited to 4 per protocol (NUM_PROTO_OPTS), and now I'm running out of slots for a new option (SBUS output enabled/disabled)

Do we already have an existing solution for this issue ?
If not, maybe we could add a function to ProtoCmds eg case PROTOCMD_GETMISCOPTIONS and a .proto_miscopts[] field to the Model struct ?