Jan Gromeš

@studiofuga sorry it took so long to get back to this. In summary, I tried the following options to resolve this. 1. Providing a `getIRQ` method so that the user...

@phretor it would, unfortunately it's not enough, a significant rework would be needed to make everything consistent, so that only cached or non-cached parameters are used.

@rdforrest very cool! The low frequency range AX5043 can achieve is one of its most interesting features.

I recently tried reproducing this issue, but I was unable to do so. While there still are random packet being received, they all return CRC error now, so I'm not...

@TomD53 well this is a bit of a skeleton in my closet ... This entire thing started a few years ago due to issues I saw on STM32 with long...

@IhorNehrutsa all the work that was done is already on the development branch (https://github.com/jgromes/RadioLib/tree/development), but that's all there is so far.

Basic LoRaWAN support was added, see https://github.com/jgromes/RadioLib/blob/master/examples/LoRaWAN/LoRaWAN_End_Device/LoRaWAN_End_Device.ino It's been tested against a Waveshare SX1302 gateway connected to TTN. Caveats: 1. ~~Only supports LoRaWAN 1.0~~ 1.1 implemented as well 2. ~~Only...

@StevenCellist LoRaWAN mandates AES-128, which has 16-byte keys. I chose to represent them as ASCII strings. A 16-character string will be 32 symbols when represented as hexadecimals numbers. I have...

@StevenCellist All RadioLib protocols run on any of its supported transceivers (there are some exceptions caused by hardware, but that's beside the point). The number of possible combinations is huge,...

@klemzi I don't think this is the same problem. Your signal is very strong, RSSI -19 dBm, SNR > 8 dB suggests you have the devices right next to each...