RAK4631 turns off intermittently

WisBlock
1

I have a WisBlock RAK4631 assembly with GPS module RAK12500.
Software loaded is Mashtastic 2.5.18. (This is my third RAK4631 assembly) In Settings/Device/ Heartbeat LED(green) is turned off. Assembly consists of 19007/4630/1921 modules
The issue I am facing is that after booting up cold board (powered by USB-C (5.2VDC) all works well for about 4-6 minutes.
Then the board turns off, looks to be asleep as the red LED blinks at a .6 second rate mostly and Bluetooth connection drops and will not reconnect. Just before it shuts down the green LED starts to blink rapidly for about a second then the current drops to zero. 30-90 seconds before the green LED starts to blink and the system goes to sleep the current intermittently drops to zero many times. The red LED then blinks slowly at .6secs with random burst both very dimly with current at zero (below what I can measure) Now and then there is a current flow of about 0.03A… The assembly never wakes up. If the reset button is pressed the system boots and works normally for about 60-110 seconds then the process starts over again and it goes to sleep.
This does not happen with display or no display connected without the GPS module connected. Only when the GPS module is connected.
I have looked to see if there is some setting (like go to sleep in X seconds) but have not seen such.
These are new parts just delivered in the last few weeks and this is the first assembly and programming. Using Win11 I have also done an erase (file for 6.1.1) and reprogramming three times (using the Meshtastic flash app).
Current: @5.22VDC
First cold boot:
Receive 0.05A-0.07A mostly 0.06A
Transmit 0.17A-0.21A mostly 0.18A

After pressing reset the current is lower that after a good boot: 0.03-0.06A mostly 0.03A

So looks to be the GPS module unless I am missing something.
Forgive the prattling on but wanted to give as much info as possible.
Anyone have any ideas? Thanks

Edit:
Is it normal to have the red LED flashing all the time?
My new RAK Pocket V2, which is the same board, does not do this but this board does…

2

We are not developing or maintaining the Meshtastic firmware. We can give only limited support related to hardware problems.

Did you try Meshtastic factory reset?

Please flash hardware test firmware (not Meshtastic based), connect over USB with a serial terminal application and share the output here.
The hardware test will check important parts of the WisBlock and report over USB the results.

WB_HW_Test_V1.1.8.uf2.zip (186.4 KB)

Additional question, where did you install the RAK12500? In Slot A, B, C or D?
WIth Meshtastic, the RAK12500 should be in Slot A.

3

Thanks for your reply.
Yes, I did a erase and reprogram using the files provided in Flash.mashtastic. (see line just before Current readings in my message.

I have been installing the GPS board in slot D as it looks to be the only slot that has the a screw mounting for this size board.

I flashed the erase file (nrf_erase2.uf2) again and flashed the file (WB_HW_Test_V1.1.8.uf2) from the zip link provided.
Below is the output file. I have removed many of the data blocks as the board was searching for Sats to shorten the results.
I am not sure what
“[GNSS] GNSS timeout 2000” is indicating.
Other than that, looks ok I think.
Also removed detail of exact location which was reporting correctly from 5 Sat fix on.

Note: The Sat antenna is looking at sats through a window that is three pane and coated. As a thin film coater I know these coatings are deposited with alternate layers of metal so there is attenuation. Antenna is looking at the western sky.

[EPD] Left LOW
[EPD] Middle LOW
[EPD] Right LOW
[EPD] Button status suggests no EPD
[EPD] No RAK14000 EPD
[SCAN] Found sensor at I2C1 0x3C
[SCAN] Found sensor at I2C1 0x42
[SCAN] Found 2 I2C devices
[GNSS] UBLOX found on I2C
[FLASH] Flash Write-Read test #1
[FLASH] Flash Write-Read test #1 success
[FLASH] Read send time from flash 10000
[FLASH] Flash Write-Read test #2
[FLASH] Flash Write-Read test #2 success
[SX1262] SyncWord = 2414
[SX1262] LoRa transceiver ok
[APP] Battery 4.20 V
[APP] Timer wakeup
[APP] Try GNSS
[GNSS] poll_gnss
[GNSS] GNSS timeout 2000
[GNSS] Using RAK12500
[GNSS] Sat: 0 Fix: No Fix
[GNSS] Lat: -56.4866 Lon: 123.6935
[GNSS] Alt: 734043.77
[GNSS] HDOP: 284.92
[GNSS] No valid location found

Truncated Below FIX is after 25 mins

[APP] Tmer wakeup
[APP] ry GNSS
[GNSS] poll_gnss
[GNSS] GNSS timeout 2000
[GNSS] Using RAK12500
[GNSS] Sat: 5 Fix: Fix type 3D
[GNSS] Lat: 42.XXXX Lon: -72.XXXX
[GNSS] Alt: 40.09
[GNSS] HDOP: 2.05
[GNSS] Sat: 5 Fix: Fix type 3D
[GNSS] Lat: 42.XXXX Lon: -72.XXXX
[GNSS] Alt: 44.07
[GNSS] HDOP: 2.05
[GNSS] No valid location found
[APP] Battery 4.30 V
[APP] Send P2P packet
[APP] P2P TX finished

Truncated Below FIX is after 40 mins

[APP] Timer wakeup
[APP] Try GNSS
[GNSS] poll_gnss
[GNSS] GNSS timeout 2000
[GNSS] Using RAK12500
[GNSS] Sat: 9 Fix: Fix type 3D
[GNSS] Lat: 42.XXXX Lon: -72.XXXX
[GNSS] Alt: 50.83
[GNSS] HDOP: 1.22
[APP] Battery 4.29 V
[APP] Send P2P packet
[APP] P2P TX finished

Truncated Below FIX is after 55 mins

[APP] Timer wakeup
[APP] Try GNSS
[GNSS] poll_gnss
[GNSS] GNSS timeout 2000
[GNSS] Using RAK12500
[GNSS] Sat: 12 Fix: Fix type 3D
[GNSS] Lat: 42.XXXX Lon: -72.XXXX
[GNSS] Alt: 42.08
[GNSS] HDOP: 0.82
[APP] Battery 4.27 V
[APP] Send P2P packet
[APP] P2P TX finished

4

Good news, there is no hardware problem.

Meshtastic expects the RAK12500 in Slot A as it is using the PPS signal from the GNSS chip.
Try to switch RAk12500 into Slot A. It will fit there, it covers Slot B and the mounting screw goes into the thread of Slot B. But that is ok.

1 Like
5

Ok thanks for the reply. A shame to loose slot B…
Have made the change and it does not turn off now so that is a good thing.
Then did erase and reflash of WB_HW_Test_V1.1.8.uf2 file
No sure if “GNSS timeout 2000” is normal
Did another Erase and reflash to latest Meshtastic and all works well. Has been running as a test bed for 24 hours.
Thanks for all your help on this issue.
Is there a document that show what slots that each addon can (or can’t) be installed at?
Thanks again…

[APP] Timer wakeup
[APP] Try GNSS
[GNSS] poll_gnss
[GNSS] GNSS timeout 2000
[GNSS] Using RAK12500
[GNSS] Sat: 15 Fix: Fix type 3D
[GNSS] Lat: 42.XXXX Lon: -72.XXXX
[GNSS] Alt: 29.09
[GNSS] HDOP: 0.76
[APP] Battery 4.29 V
[APP] Send P2P packet
[APP] P2P TX finished
[APP] Timer wakeup
[APP] Try GNSS
[GNSS] poll_gnss
[GNSS] GNSS timeout 2000
[GNSS] Using RAK12500
[GNSS] Sat: 16 Fix: Fix type 3D
[GNSS] Lat: 42.XXXX Lon: -72.XXXX
[GNSS] Alt: 28.60
[GNSS] HDOP: 0.76
[APP] Battery 4.28 V
[APP] Send P2P packet
[APP] P2P TX finished

6

GNSS timeout is normal if you are indoors (cannot receive satellite signals) or do not have an antenna attached.

For help which slots to use, have a look at the Meshtastic Designer.
It is not perfect, but it gives you some help when placing modules.

7

Ok thanks, Will do that…

8

I just wanted to say thank you for this bit of information.

I was having a very similar problem with my newly purchased Rakwireless Meshtastic starter kit.

I also purchased the gps module along with the starter kit.

Like the other poster mentioned, I too thought that the gps board would only fit in “Slot D” on the back side of the WisBlock board, because to my mind it seemed “incorrect” to cover “Slot B”.

My system was randomly shutting down, going into deep sleep permanently; displaying a message on the USB serial console, that the button had been pressed.

I found this forum thread by chance following some Google search results.

I moved the 12500 gnss/gps board from Slot D to Slot A, and so far; the board has now been up for 30 minutes as of typing this reply. Whereas with the gps board on the back of the WisBlock board in Slot D, it wouldn’t stay up for more than 5-8 minutes, max.

This seems like information that should be shared more prominently, that the gps add-on board cannot be installed in Slot D, even though that seems like the most proper place to put it from a physical form factor perspective.

I bought the Rakwireless hardware, based on watching several YouTube videos where Rakwireless sent review kits to some of the more popular Meshtastic YouTubers for reviews.

As a suggestion, perhaps if you send future kits to other YouTubers; you could include a note to ask them to point out that the module placement is important, as well as Begee’s explanation from this thread as to why it is important…?…

I thought I had defective hardware, and was about to send my kit back and request a replacement.

A big Thank You to everyone who contributed to this thread. It definitely seems to have solved the problem I was having; and I hope that by my adding my reply here and being maybe a little more verbose than necessary, that maybe it will help someone else out in the future.

9

The RAK12500 GNSS module is using a GPIO as PPS output, which is the same as the Meshtastic user button when plugged into Slot D.

When using Meshtastic firmware you are limited to Slot A for the RAk12500.

10

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.