I'm implementing a nice frequency hopping mechanism for my comms, so I change the rx/tx channel on transmitter and receiver at the same time, but every time I do that I'm losing any pending packets on the FIFO buffer.
This is made worse because I'm reading and processing them asynchronously, taking full advantage of the FIFO. And my stuff has really short packets: my largest packet is 10 bytes, the FIFO is 64!.

I know the IC has a frequency hopping mechanism built-in, but even the datasheet just plain says "just do it on the MCU". So there must be a quick way to quickly change the channel?

Hi @ZakKemble,
First , thanks for providing such a comprehensive and documented library for Si446x which is linked and pretty much being used by every person using this chip.

I'm facing a wierd issue and wanted to check with you for help. I'm using the niceRF4463 module and am trying to use your library. (And have tried the library provided with the module)

I'm consistently seeing a high on the MISO line and when I try to fetch the part info i am only getting 1s (255 or 65535) for all the fields in the info structure.

I've tried a lot of things but just can figure what could be the issue here that MISO just isn't being pulled low at any time. Would be grateful if you can share any insight.

Hi,
I need to transfer timelapse photo from ESP32 Cam to the main controller at 500 meters or more.
My use case is in farm where we esp32 cam upload vegetable photos to server. The photo is around 50kB to 100kB.
Is Si446x a feasible solution? I go through several Lora model(Or similar), only Si446x allow the biggest air rate.

Hi, this is an issue I'd noticed occasionally when using an AVR 328p, and recently found to be a deal-breaker when using a much faster STM32F1.

Some interrupts on the micro side don't fire, so the interrupt line keeps low (confirmed with oscilloscope) and no further interrupts are triggered. As a result, everything stops working.

I was able to recover from this state by physically reconnecting the interrupt wire. I also tried adding an external pull-up but no help.
Is this a possible bug in the library or am I missing something?
Are we assuming that the pin falling interrupt will fire eventually, or should the library check for the interrupt pin being low before continuing?

I was trying to get this (the Arduino) version running on an ESP8266 using the ArduinoIDE and had the following issue.

SI446X_INTERRUPTS is not defined in Si466x_config.h but in Si466x.cpp therefore (at least my compiler) did not respect its value when defining the SI466X_NO_INTERRUPT macro in Si466x.h. Therefore the interrupts were never disabled for me and I got some endless loops.
Moving the SI446X_INTERRUPTS to the config header got things working.

Side note for anyone else trying to get this running on an ESP:
Seems to be working so far, but if you are using the included examples make sure to feed the watchdog ESP.wdtFeed(); in any long/endless loop, otherwise your ESP will reset

Hi, I'm trying your library with a pair of cheap Si4463 and ran into problems. I'm using a variation on the IRQ example, and when sending a simple 2 byte message [3|9], what I get on the other side is [2|3]. The received buffer size is correct, and sometimes, due to glitching it reports a bigger buffer and I can peek [2|3|9|0|0|0|0]. So the message is there, but there's something wrong with the reading/writing.

Any tips?

Trying to get a carrier wave on a si4463 and Arduino UNO, and trying to detect it with a cc308+
I'm successfully talking to the chip and printing to the serial monitor, though when I try to

  si446x_info_t* info;
  Si446x_getInfo((si446x_info_t*)info);

It appears to freeze up at this point, and I stop getting anything printed to the Serial.
Other things like Si446x_getState, Temprature, and getProperty apear to work fine. (I added getProperty to Si446x.h).
I created a function to setProperty((SI446X_PROP_GROUP_MODEM<<8) | 0x00, 0x18); to the library and I'm calling that from the arduino code, I'm reading the property before and after and can see the property getting changed.
however I'm not picking anything up on the cc308+.
Do I still need to send a command to start transmitting? if so what command arguments need to be sent?
I think I partially understand what's going on with setting properties and the si446x api, ie in the above you're ORing the group (MODEM 0x20) and the index (MODTYPE 0x00) and setting it to 0x18. I'm not quite seeing what the 0x18 is though.

This was helpful: https://cu-taber.github.io/Si4463-API/#details_prop_grp_MODEM
but I feel like I'm being dense with understanding what the hex values that we're setting it to are.