Hello everyone I just connect my 5205 tracker update the firmware (fw RAK811_HF_trackerboard_V2.0.1.9.bin) and perform the otaa process to connect the device to TheThingsNetwork but the association failed (Join Failed!).
In my application I receive the data from dev addr and app eui, only that.
I saw some comments about the fw and the violation of the time of use of the air. Therefore, I would like to know or recommend me which fw to use or how to modify the time of sending messages.
I am also very interested in feedback on power consumption. Did someone validate the announced values ?
It looks like the announced value is fake and the RAK node is not able to work at low power.
I have raised the issue on the RAK forum but did not get any real feedback in the last 2 months.
I cannot recommend to use their product if power consumption is an important requirement.
I have little knowledge about the RAK5205 but reading about that it does not reach its advertised sleep mode power consumption the following could play a role:
Is a circuit diagram of the board available? A circuit diagram would allow to check if the advertised low-power/deep sleep current is possible at all, from hardware perspective.
A circuit diagram would of course help.
Quoting the sleep current for a GPS based tracker is rather academic anyway. The greatest amount of power will be consumed by the GPS aquiring a fix.
Based on a 10 minute GPS fix and transmission cycle the GPS they are using will consume around 19mAhr in a day, an average of 790uA.
Above linked topic on RAK forum mentions a measured low-power/sleep mode current for the board of 1.5mA while the advertised low power current is 14.5uA.
Schematic for the 5205:
Thanks.
With no connection to the GPSs Vbkp pin, if you want to use hot fixing you can only use software shutdown of the GPS and that only reduces current to 500uA. Maybe the schematic is in error here.
There is a power switch to turn off the power to the GPS, which would reduce its sleep current to 0. However turn the power on and the GPS is starting from cold, with a typical run time of 40 plus seconds at 33mA, very battery unfriendly.
I can confirm that V_BCKP (pin 6) is not connected (measured with multimeter) to VCC_3V3 (nor GPS_3V3, nor VBATT nor VBIN) .
One would expect it to be connected to VCC_3V3 (which is battery powered). I also do not see a solder jumper that could enable it.
With some soldering craftmanship V_BCKP may be manually connected to VCC_3V3. According to the datasheet that would draw 15 uA (@3.0V) backup current for the MAX-7Q.
The power for the GPS can be switched off completely (with PA15), so if correctly switched off the GPS should not contribute to the measured 1.5mA in ‘low power’ / sleep.
15uA would be about right for a Ublox in software shutdown, but I was going on the GITHUB for the RAK 5206 which says they are using a L76. This matches the schematic.
If they swapped to a Ublox MAX 7Q, then they ought not to have left Vbckp floating, from the 7Q datasheet;
“If no backup supply voltage is available, connect the V_BCKP pin to VCC_IO (or to VCC if not avaiable)”
I have a RAK5205 VER.B board here with a Ublox MAX-7Q.
The GPS switch off with PA15 is flawed because it does not disconnect the RX line input to the GPS. This means the RX line will be powering the GPS via the GPS module input protection circuitry. You can work around this HW limitation by disabling the serial port in software putting the pin in input mode.
Anyone tested sleep current on the new fw?
My RAK5205 won’t do anything with this new firmware. Am I missing something?
I have a WisTrio-Lora RAK5205 rev B.
Regards,
Andre
Sorry for bothering… Solved.
cool… what did you ‘missed’ ?
Reading the updated manual… Tried to upload “old” way…
Missed the need for updating de BOOT section 
