RAK5010 Loop not working

Good morning,

Since several days, i’m trying to make my RAK5010 to work in loop mode. The command I wrote, to send a single message are perfectly working :

at+scan=cellular
> +COPS: (1,"F SFR","SFR","20810",0),(2,"Orange F","Orange F","20801",0),(1,"F-Bouygues Telecom","BYTEL","20820",0),,(0,1,2,3,4),(0,1,2) 

at+set_config=cellular:(AT+COPS=1,0,"Orange F",0)
> OK
at+set_config=cellular:(AT+QICSGP=1,1,"NXT17.NET","","",1) 

at+set_config=cellular:(AT+QIACT=1)
> OK

at+set_config=cellular:x.x.x.x:2000:Orange F:Orange:NXT17.NET:0
> OK

at+send=cellular:54554
> OK

After that, i would like to send data automatically, so i sent this :

at+set_config=cellular:(AT+QIDEACT=1) # to disable previous opened context
at+set_config=cellular:x.x.x.x:2000:Orange F:Orange:NXT17.NET:0
at+set_config=cellular:send_interval:1,150000
at+set_config=device:restart

The device is restarting every 150s to send packet :

 [01:21:55.831,000] <info> app: app_task!!!
 0> [01:21:55.834,000] <info> app: wdt_timer_handler wdt feed
 0> [01:23:01.402,000] <info> app: GMS_PowerUp
 0> 
 0> [01:24:56.394,000] <info> app: Gsm_SetEchoCmd ret= -1
 0> 
 0> [01:24:57.501,000] <info> app: AT+QGPSCFG= ret= 0
 0> 
 0> [01:25:30.961,000] <info> app: AT+QGPS ret= 0
 0> 
 0> [01:26:03.753,000] <info> app: LIS3DH_GetWHO_AM_I = 51
 0> [01:26:03.890,000] <info> app: opt3001:manufacture_id=5449 device_id=3001
 0> 
 0> [01:26:20.296,000] <info> app: shtc3 id = 2119
 0> [01:26:20.316,000] <info> app: wdt_timer_handler wdt feed
 0> [01:26:20.329,000] <info> app: cmd_len = 11
 0> [01:26:20.332,000] <info> app: CMD = AT+COPS=?
 0> 
 0> [01:26:20.753,000] <info> app: wdt_timer_handler wdt feed
 0> [01:33:31.822,000] <info> app:  
 0> +COPS: (1,"F SFR","SFR","20810",0),(2,"Orange F","Orange F","20801",0),(1,"F-Bouygues Telecom","BYTEL","20820",0),,(0,1,2,3,4),(0,1,2) 
 0>  
 0> OK
 0> [01:33:31.832,000] <info> app: wdt_timer_handler wdt feed
 0> [01:33:31.845,000] <info> app: cmd_len = 37
 0> [01:33:31.848,000] <info> app: CMD = AT+COPS=1,0,"F-Bouygues Telecom",0
 0> 
 0> 
 0> [01:33:33.132,000] <info> app: wdt_timer_handler wdt feed
 0> [01:33:33.463,000] <info> app:  
 0>  
 0> ERROR 
 0> 
 0> [01:33:33.468,000] <info> app: wdt_timer_handler wdt feed
 0> [01:33:33.481,000] <info> app: cmd_len = 31
 0> [01:33:33.484,000] <info> app: CMD = AT+QICSGP=1,1,"BYTEL","","",1
 0> 
 0> [01:33:34.521,000] <info> app: wdt_timer_handler wdt feed
 0> [01:33:34.716,000] <info> app:  
 0> OK
 0> [01:33:34.720,000] <info> app: wdt_timer_handler wdt feed
 0> [01:33:34.732,000] <info> app: cmd_len = 12
 0> [01:33:34.735,000] <info> app: CMD = AT+QIACT=1
 0> 
 0> [01:33:35.137,000] <info> app: wdt_timer_handler wdt feed
 0> [01:34:30.149,000] <info> app:  
 0>  
 0> ERROR 
 0> 
 0> [01:34:30.170,000] <info> app: pressure = 988 hPa
 0> 
 0> [01:34:30.211,000] <info> app: acceleration x = -886.00
 0> [01:34:30.215,000] <info> app: acceleration y = 24.00
 0> [01:34:30.218,000] <info> app: acceleration z = -456.00
 0> [01:34:30.237,000] <info> app: light strength = 177.27
 0> [01:34:30.602,000] <info> app: temperature = 23.69
 0> [01:34:30.606,000] <info> app: humidity = 36.39
 0> [01:34:30.620,000] <info> app: cmd_len = 20
 0> [01:34:30.623,000] <info> app: CMD = AT+QGPSGNMEA="GGA"
 0> 
 0> [01:34:34.726,000] <info> app: cmd_len = 20
 0> [01:34:34.729,000] <info> app: CMD = AT+QGPSGNMEA="GGA"
 0> 
 0> [01:34:38.833,000] <info> app: cmd_len = 20
 0> [01:34:38.836,000] <info> app: CMD = AT+QGPSGNMEA="GGA"
 0> 
 0> [01:34:42.939,000] <info> app: cmd_len = 20
 0> [01:34:42.942,000] <info> app: CMD = AT+QGPSGNMEA="GGA"
 0> 
 0> [01:34:47.045,000] <info> app: cmd_len = 20
 0> [01:34:47.048,000] <info> app: CMD = AT+QGPSGNMEA="GGA"
 0> 
 0> [01:34:51.152,000] <info> app: cmd_len = 20
 0> [01:34:51.155,000] <info> app: CMD = AT+QGPSGNMEA="GGA"
 0> 
 0> [01:34:52.104,000] <info> app: gps Latitude(0-N,1-S):0,4547.092579
 0> [01:34:52.111,000] <info> app: gps Longitude(0-E,1-W):0,308.398170
 0> [01:35:21.639,000] <info> app: Battery Voltage = 4.10 V !
 0> 
 0> [01:35:21.674,000] <info> app: gsm_cmd: AT+QIOPEN=1,0,"TCP","*x.x.x.x*",2000,0,1
 0> [01:35:21.678,000] <info> app: wdt_timer_handler wdt feed
 0> [01:35:21.689,000] <info> app: cmd_len = 46
 0> [01:35:21.692,000] <info> app: CMD = AT+QIOPEN=1,0,"TCP","*x.x.x.x*",2000,0,1
 0> 
 0> [01:35:23.223,000] <info> app: wdt_timer_handler wdt feed
 0> [01:35:23.243,000] <info> app:  
 0> OK

You can see in this example, I tried to change the Orange operator to Bouygues, because I have a telit SIM that can switch. It is not working neither. Yesterday on my tries, I had this “ERROR” only on QIACT command. What am i doing wrong?

Thank you by advance

Hi,

It looks you want to use Orange F. Before start it , you set
at+set_config=cellular:x.x.x.x:2000:Orange F:Orange:NXT17.NET:0
But when restart, it chooses F-Bouygues Telecom… This should happen. It use data what you set to flash. So I advise erase the flash and flash new version.
https://downloads.rakwireless.com/en/Cellular/RAK5010/Firmware/

Then:
at+set_config=cellular:x.x.x.x:2000:Orange F:Orange:NXT17.NET:0
at+set_config=cellular:send_interval:1,150000
at+set_config=device:restart

Hello, thanks for the answer.

It seems you didn’t see my last paragraph. I tried with Orange and with Bouygues, and I had the same result (config with Orange, cannot connect to Orange, then config with Bouygues, and cannot connect to Bouygues). I didn’t showed you the right couple commands/logs, my bad

OK,I see. If you use the 2G, the task will work fine. I think the best way is to connect your server with single command step by step. You may see this topic. I explain with CHINA MOBILE(2G).

If success, then try to use the task with correct parameters config.

I did as follow, and I was perfectly able to send message. But when it comes to loop automatically with this:

at+set_config=cellular:x.x.x.x:2000:Orange F:Orange:NXT17.NET:0
at+set_config=cellular:send_interval:1,150000

I have the errors i sent in the first message

Could you show the entire log ? I want to check which step is error. The at order is simple, so entire log is good to analysize.