Closed Erik84750 closed 3 years ago
Partly solved,.. I think: after discovering rare single nanosecond spikes on the reset line, the scope was put on the 3V rail: same. Changed power supply (lab PSU, 2A); spikes gone initially. Those single spikes correspond to the time when reception stops. But still present although less frequent.
Would there be a limit to what can be done within the void onReceive(int packetSize) ? And to what can be done in the main loop?
Then likely your board doesn't supply enough power. Arduino Nano?
Pro Mini 3.3V 8MHz supplied by lab PSU 3.3V 5A limit.
Using the original LoRaReceiverCallback.ino program it lasted 52 runs before that too stopped. Is this then a hardware issue?
You can try a Uno or esp32?
Power issue may affect TX not RX. TX uses more power than RX.
My esp32 can listen for packets in months.
Must indeed be hardware issue; for hours being run now on 2x UNO with Dragino LoRa shield ( https://wiki.dragino.com/index.php?title=Lora_Shield ), no issues.
Replaced the hardware of my initial test (Pro Mini 8MHz and LoRa module) and working perfectly for hours now. So this definitely was a hardware issue. Great library, callback provision is a fantastic add-on, thank you.
Must indeed be hardware issue; for hours being run now on 2x UNO with Dragino LoRa shield ( https://wiki.dragino.com/index.php?title=Lora_Shield ), no issues.
Glad it works.
When code is added to the void onRceive(int packetsize) function this causes reception to halt after a number of runs. Incoming data consists of 14 bytes: two characters, 1 integer (2byte) and 2 floats (4byte). These need to be parsed: see code below. In the main loop there obviously is also code that needs to be executed.
Tried but failed to help:
I refer also to issue #341: the implementation of DIO0 interrupt call; there it is explained how this library functions to get receive callback works.
How could this issue be best resolved?
[code] `
` [/code]