RAK5010 (BG95-M3, RUI v3.0.0.15) reboots on any cellular data operation

Cellular Boards RAK5010
1

Issue:
On a single RAK5010 with the Quectel BG95-M3 modem, stock firmware (at+version = RUI v3.0.0.15), the modem registers fine but any operation that actually uses the cellular data path fails and reboots the device. Registration, signal and IP assignment are all fine; context activation / opening a socket / sending are not.

Setup:

  • RAK5010, Quectel BG95-M3 modem, stock firmware RUI v3.0.0.15
  • SIM: 1NCE, APN iot.1nce.net, no user/pass
  • Network: registers automatically on Vodafone NL LTE-M (+COPS: 0,0,"vodafone NL",8)
  • Powered from USB and a fully charged LiPo at the same time (battery 4.1 V)
  • Serial console with the DTR/DSR settings from the docs, 115200
  • Goal: use the built-in cellular tracker loop (cellular:send_interval) to send GPS + sensor data to my own TCP server (server confirmed reachable from the internet)

Details:
What works:

  • +CSQ: 26,99
  • +CGATT: 1
  • +CGPADDR: 1,100.65.x.x (gets an IP)
  • sensors and battery read fine

What fails:

  1. The board powers off completely during cellular commands — no LED, USB serial does not re-enumerate, I have to unplug both USB and the LiPo to recover it. This happens even on at+set_config=cellular:(AT+QICSGP=1), which is only a query. at+scan=cellular also reboots the device.

  2. Manual send fails. After at+set_config=cellular:<ip>:<port>:a:a:iot.1nce.net:8, the command at+send=cellular:test123 returns +QIOPEN: 0,567 (socket has been closed), throws ERROR plus some garbage bytes, and reboots (APP RDY). Nothing arrives at my server.

  3. The tracker loop never connects. With send_interval:1:150000 set and the device outside for 20+ minutes, it never opens a connection to my server, and never gets a GPS fix.

  4. Long AT commands get truncated. The cellular:<ip>:<port>:<op>:<op>:<apn>:<net> line loses everything after a space in a field, and drops trailing characters if the whole line is longer than ~60 chars. I only got the full command (with the :8 net type) to register after shortening the operator fields to single letters.

  • Is this a known problem with RUI v3.0.0.15 on the BG95-M3 units?
  • Is there a newer firmware, and can I flash it without an SWD probe (BLE DFU, USB, or the RAK Serial Port Tool)?
  • Does the tracker loop require a GPS fix before it transmits anything?
  • Is there a supported way to read back the stored cellular: config? (at+get_config=cellular: returns ERROR:RUI_AT_UNSUPPORT 1.)

Happy to post full serial logs.

2

Welcome to the forum @sempie
The only problem I could think about is that the battery is not able to provide enough current.
What type of battery do you have connected to the RAK5010, what is its charging status and what is the capacity of the battery?
Did you try a different battery?

There is no newer “official” firmware available for the RAK5010 with the BG95-M3.