Interesting to hear the comments about the cold. Not tried the RN2483 myself but LoRa devices such as the RFM9xs seem to work quite well in high altitude balloons where it can get real cold.
I have temperature cycled my own trackers quite a bit in the freezer down to -20C or so, never had a problem. I use 62Khz bandwidth and so the capture range is circa 15Khz, never see them drift that much.
One issue to be aware of is that the crystals used have a fairly low drive, for low current operation, and as such could be sensitive to small amounts of condensation on the modules causing significant frequency shifts, I presume you are all conformal coating the modules to reduce the risk of this ?
And to comment my own post, once a receiver has picked up one packet, its easy enough to use AFC to keep it locked. I have had my trackers running at 7.8Khz bandwidth from room temperature down to -20C (the freezer again) and it works just fine. The AFC keeps the receiver within circa 1khz or less of the transmitter frequency.
The RN2483 ‘cold problem’ existed in the first generation… haven’t hear anyone with an rn2483A based node that experienced problems below -5 … so I guess that problem is solved.
I have a Seeeduino LoRaWAN based node with a 3.7V LiPo battery and a BME280 module, currently reporting -6.2°C, so based on my experience, a LiPo battery should be OK there. But indeed, it’s protected from rain
I suspect that’s a bug in your code somewhere, not handeling the negative values right because I have never seen a module stopping at exactly zero degrees.
Tx = RN2483 until now no problem
update last night was a very cold night in Holland -7 (some of you will laugh) and I was curious what will happen to the RN2483 based node… in short nothing, it just worked.
I am not doing anything (myself) with code in Nodes.
Loaded the default LPP sketch on them in december, and that’s it
I am first going to finish my DB & Dashboard, then will see what to do with the remaining 6 virgin Nodes on the shelf (which, I suspect, are not A Nodes)
support and updating process for RF explorer products is excellent !
still need to test further the RAK magic stick 8 dbm 868 antenna.
first things first… installing and updating the spectrum analyzer/ rf generator and rf explorer.
updates under win 10 … pfffffffff ,seems that my second screen don’t work anymore on my laptop
worked fine under ubuntu…
#include "LowPower.h"
...
void loop()
{
...
// Sleep radio
rf95.sleep();
//USBDevice.detach(); doesn't work on 32u4
// Disable USB clock
USBCON |= _BV(FRZCLK);
// Disable USB PLL
PLLCSR &= ~_BV(PLLE);
// Disable USB
USBCON &= ~_BV(USBE);
// ATmega32U4 sleep
LowPower.powerDown(SLEEP_8S, ADC_OFF, BOD_OFF);
// Reattach USB to have Serial working again
USBDevice.attach();
}
Found in RocketScream forum here. The most important bit being disabling the USB, which saved a lot.
I’ve also had some attempts at removing the voltage regulator and bridging the 5V/3.3V pins. (Note: that you really need to program via ISP after this)
Here are the results with the Adafruit code above:
I have been able to replicate the same power usage with LMIC lib. The only additions I’ve made to the TTN ABP example code is changing pins, adding LowPower lib sleep and disabling the USB with same code as above.
these are the two I’ve tested, the one without the dipswitches is cheap, but not very accurate and I had to buy a seperate switch
the whole idea was to test if a customer/installer could set a node interval from the outside, but there are better , more accurate, ways over the network
where is that coming from… which lib ? or can you post the contents of that routine. I am using the HPD13A btw from BSFRANCE LoRa32U4II and using the code below
what am I missing… lowest consumption I get with this code is