-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RH_RF69 send hang due to waitPacketSent failed #12
Comments
_mode is set in the interrupt routine. Did you connect the right Pin to the interrupt? |
Hi! Did you solve it? I'm having a similar issue with RF95 at the waitPacketSend. I'm using and Arduino Pro Mini Clone with a LoRa Bee. You talk about an interrupt pin. Which one is it? Where should be connected to the Arduino? Right now I have only wired the SPI and D10 as ChipSelect. Which pin of the LoRa Bee is the interrupt? Thank you! |
I have no LoRa Bee, but I recommend to search for the documentation. It could be DIO0. and on the arduino pin 2. This could be changed to 3 in the software setup. The interrupt tells the arduino that the packet was send. |
Thanks! I came back to post I've found the solution to my problem and I see your new answer. Indeed, DIO0 is the interrupt that should be attached to pin 2 of Arduino. This artivle was very helpful: http://cpham.perso.univ-pau.fr/LORA/LoRaDevices.html Also there's a constrcutor in the Lib to specify wich pin of Arduino is CS and wich is IRQ. Defautls are 10 and 2 |
Hi
I have problems with stable transmissions for the RFM69. Initialization seems to be fine, but when I transmit with
_spRFM->send(_spData, 2)
sometimes the call will never come back. It looks like the internal callwaitPacketSend()
is the reason. Does someone know what the reasons are for not returning from waitPacketSend? The comparison inside iswhile (_mode == RHModeTx)
. But what is responsible for not "leaving" the transmission-mode? Can it be that it is something like too much noise on the radio frequency or no receiver found? As far as I understand it is not a confirmed transmission, it is fire and forget?Investigating further, it looks like the interrupt is not called. After that, the mode is for ever RHModexTX (which makes sense). The question is now, what can create such a scenario? Instable power supply? Some time the interrupt is fine, sometimes not.
Has someone an idea?
Kind regards
Pix
The text was updated successfully, but these errors were encountered: