KCELL=1 GSM Neighboring Cell or Servicing Cell seem swapped

IoT Modules Legacy HL Series
1

Using the HL-8548 wtih 5.5.25 version of the firmware (and 5.5.23) it is observed the GSM serving cell and neighboring cell report may be swapped in the AT Command Sheet.

The reason, I see multiple “serving cells” for GSM and only one “neighboring cell”

I know there were some changes for KCELL in 5.5.25, but it did not seem to change anything here.

Also many of the values for RSSI GSM and TimingAdvance GSM appear out of range.

When in GSM only I also see some invalid tower types being reported for UMTS. Values of 105 and 237 come up every now and then. These we ignore as there are no UMTS towers at this point (all values are also 0).

1 Like
2

Hi robvice,

I did not see such issue with my dev-kit, could you share me your AT log?
Here’s my log for your reference:

ATI3
RHL85xx.5.5.25.0.201804161340.x6250_2
OK
AT+KSRAT=1
OK
+CGREG: 1,“2540”,“7ACA”,3,“02”
+CGREG: 1,“2540”,“7ACA”,3,“02”
AT+COPS?
+COPS: 0,0,“CHN-UNICOM”,0
OK
AT+CGREG?
+CGREG: 2,1,“2540”,“7ACA”,3,“02”
OK
AT+KCELL=0
+KCELL: 7,
0,688,25,64f010,2540,7aca,25,255, //0 GSM serving cell
1,783,57,64f010,2540,7c3d,24, //1 GSM neighbor cell
1,641,13,64f010,2540,7acc,14, //1 GSM neighbor cell
1,640,38,64f010,2540,ffff,11, //1 GSM neighbor cell
1,690,255,64f010,ffff,ffff,0, //1 GSM neighbor cell
1,645,255,64f010,ffff,ffff,0, //1 GSM neighbor cell
1,648,255,64f010,ffff,ffff,0 //1 GSM neighbor cell
+KCELL: 0
OK

3

Turned out to be a parsing issue on my side with trying to manage GSM and UMTS. Thanks for confirming

4

I have a similar question on the HL7800 here - do you have any insights?
https://forum.sierrawireless.com/t/thanks-for-spending-time-with-us/19099