Need method to get expected payload length from Reg 0x22 in SX1276 modem while in LoRa implicit header mode

[snowrodeo]

There are two(?) ways to set the payload length in implicit header mode
setImplicit(length) and setReceived(timeout, flags, flags, length)

However there is no way to explicitly report on this length without using a SPI read from the register in God mode.

Request that a getImplicit method is added to return the number of payload bytes while in implicit more or 0 if not in implicit header mode

[jgromes]

The same argument can be applied to any parameter that is being configured - that would be a very large amount of new methods to be added. There is currently an open issue for that (#622), though to be honest, I'm not sure that this is the right way forward.

Is there a specific scenario in which you would need to retrieve this value except for checking the radio settings when debugging?

[snowrodeo]

It is not super critical, and if it is a lot of work, not needed. This was more of an request (for debugging) because I could not seem to set the value correctly and didn’t have a way to get it. If we could solve the setting, then this isn’t needed. Thanks! From: Jan Gromeš ***@***.***> Date: Saturday, December 14, 2024 at 5:38 AM To: jgromes/RadioLib ***@***.***> Cc: Erik Olson ***@***.***>, Author ***@***.***> Subject: Re: [jgromes/RadioLib] Need method to get expected payload length from Reg 0x22 in SX1276 modem while in LoRa implicit header mode (Issue #1344) The same argument can be applied to any parameter that is being configured - that would be a very large amount of new methods to be added. There is currently an open issue for that (#622<#622>), though to be honest, I'm not sure that this is the right way forward. Is there a specific scenario in which you would need to retrieve this value except for checking the radio settings when debugging? — Reply to this email directly, view it on GitHub<#1344 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAN3UDW25JVKTDHBXQDOLBD2FQYFVAVCNFSM6AAAAABTN3RA7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBTGEYTGNZRGQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[jgromes]

It just opens a can of worms that I don't yet know how to resolve. Since this is only for debugging, we will stick with only having this accessible via godmode for now. Also #1345 has been resolved properly.