RUTX11 cell lock and carrier aggregation problem

Hello all!

I need your help on annoying behaviour with a RUTX11 (Firmware version RUTX_R_00.07.07.1 , Internal modem firmware version EG06ELAR04A20M4G )

If there’s no active cell lock (I mean, after issuing in CLI

gsmctl -A 'AT+QCFG="NWSCANMODE",3,1'
gsmctl -I
gsmctl -A 'AT+QNWLOCK="common/lte",0'

) then carrier aggregation works but it often doesn’t pick the best cellID (either as primary or as aggregated one).
On the contrary, If I force the modem to lock onto the best signal cell (I mean issueing in CLI

gsmctl -A 'AT+QCFG="NWSCANMODE",3,1'
gsmctl -I
gsmctl -A 'AT+QNWLOCK="common/lte",2,*EARFCN*,*PCI*'

) then it will stuck on that CellID but it won’t aggregate other carrier anymore.

just as an example of sub optimal carrier selection

Given this scenario

root@RUTX11:~# gsmctl -I
"neighbourcell intra","LTE",1850,306,-10,-79,-50,0,-,-,-,-,-
"neighbourcell intra","LTE",1850,407,-20,-92,-63,0,-,-,-,-,-
"neighbourcell intra","LTE",1850,286,-19,-89,-63,0,-,-,-,-,-
"neighbourcell intra","LTE",1850,434,-20,-91,-61,0,-,-,-,-,-
"neighbourcell inter","LTE",3025,247,-19,-102,-75,0,-,-,-,-
"neighbourcell inter","LTE",3025,312,-9,-95,-76,0,-,-,-,-
"neighbourcell inter","LTE",3025,246,-8,-91,-75,0,-,-,-,-

the modem hook the worst B7 (with obvious drawbacks) even restarting the connection.

What’s wrong? How can I solve this problem (if I can)?
TIA you all.

This topic was automatically closed after 15 days. New replies are no longer allowed.