Gemalto is now part of the Thales Group, find out more.

You are here

Network selection issue on PHS8-P | Thales IoT Developer Community

August 29, 2016 - 12:29pm, 3548 views

Hi.

We are using PHx8 modules in most of our products. 

Recently we discovered a strange problem regarding network selection.

Module version information:

ati1

Cinterion

PHS8-P

REVISION 03.001

A-REVISION 01.001.07

OK

The problem that we are seeing is that the module does NOT select any RAT > 0, it is only registring to GSM networks. But I know for a fact that there are ULTRAN networks available. Note that below I have produced some output from a single device, we have more then 30 devices that behave in the same way.

Initial network scan when the device is only connecting to GSM:

at+cops=2

OK

at+creg?

+CREG: 0,0

 

OK

at^snmon="iun

ERROR

at^snmon="ins",2

^SNMON: "INS",0,1,3,"410C","2AFC","24024",35,31,"-47"

^SNMON: "INS",0,1,3,"2BEA","2AFC","24024",39,17,"-79"

^SNMON: "INS",0,1,3,"3F86","2AFC","24024",66,15,"-83"

^SNMON: "INS",0,1,3,"410D","2AFC","24024",43,14,"-86"

^SNMON: "INS",0,1,3,"1583","2338","24001",90,14,"-87"

^SNMON: "INS",0,1,3,"406B","2AFC","24024",49,13,"-90"

^SNMON: "INS",0,1,3,"16DD","2338","24001",78,11,"-92"

^SNMON: "INS",0,1,3,"2BE9","2AFC","24024",53,10,"-94"

^SNMON: "INS",0,1,3,"3EC9","2AF9","24024",64,8,"-97"

^SNMON: "INS",0,1,3,"172A","2338","24001",93,7,"-100"

^SNMON: "INS",0,1,3,"E4B9","2338","24001",79,6,"-101"

^SNMON: "INS",0,1,3,"E985","2338","24001",80,7,"-101"

^SNMON: "INS",0,2

^SNMON: "INS",0,4

^SNMON: "INS",0,8

^SNMON: "INS",0,16

^SNMON: "INS",0,32

^SNMON: "INS",0,64

^SNMON: "INS",0,128

^SNMON: "INS",0,256

 

OK

But forcing the device to select a ULTRAN network (without changing location) gives me following output:

at+cops=1,2,24001,2

OK

at+cops?

+COPS: 1,2,"24001",2

 

OK

at+csq

+CSQ: 26,99

 

OK

at+csq

+CSQ: 26,99

 

OK

at^smoni

^SMONI: 3G,10836,205,-4.0,-59,240,01,0073,073CB0E,32,55,NOCONN

 

OK

at^snmon="ins",2

^SNMON: "INS",0,1,3,"410C","2AFC","24024",35,31,"-48"

^SNMON: "INS",0,16,2,"001364C6","0186","24008",10638,18,"-77",332

^SNMON: "INS",0,1,3,"2BEA","2AFC","24024",39,17,"-80"

^SNMON: "INS",0,16,2,"0013C862","0186","24008",10563,16,"-81",332

^SNMON: "INS",0,16,2,"0013C85F","0186","24008",10613,15,"-84",332

^SNMON: "INS",0,1,3,"3F86","2AFC","24024",66,15,"-84"

^SNMON: "INS",0,16,2,"0013C85C","0186","24008",10588,16,"-85",332

^SNMON: "INS",0,1,3,"410D","2AFC","24024",43,15,"-86"

^SNMON: "INS",0,1,3,"1583","2338","24001",90,14,"-86"

^SNMON: "INS",0,1,3,"406B","2AFC","24024",49,13,"-89"

^SNMON: "INS",0,1,3,"410B","2AFC","24024",63,12,"-90"

^SNMON: "INS",0,1,3,"271D","2AF9","24024",41,12,"-90"

^SNMON: "INS",0,1,3,"16B0","2338","24001",87,13,"-91"

^SNMON: "INS",0,1,3,"271B","2AF9","24024",58,12,"-91"

^SNMON: "INS",0,1,3,"16DD","2338","24001",78,12,"-94"

^SNMON: "INS",0,1,3,"2829","2AF9","24024",74,10,"-95"

^SNMON: "INS",0,16,2,"0013B988","0186","24008",10613,9,"-95",478

^SNMON: "INS",0,1,3,"3F87","2AFC","24024",57,9,"-96"

^SNMON: "INS",0,1,3,"1400","2338","24001",85,9,"-96"

^SNMON: "INS",0,2,3,"3ADF","2338","24001",676,9,"-97"

^SNMON: "INS",0,1,3,"172A","2338","24001",93,7,"-99"

^SNMON: "INS",0,128,2,"003C8549","1234","24001",3084,7,"-100",440

^SNMON: "INS",0,1,3,"E7EB","10DC","24001",84,7,"-100"

^SNMON: "INS",0,128,2,"003C8509","1234","24001",3084,6,"-101",49

^SNMON: "INS",0,1,3,"E985","2338","24001",80,7,"-101"

^SNMON: "INS",0,128,2,"003C9E1F","1234","24001",3084,5,"-104",62

^SNMON: "INS",0,4

^SNMON: "INS",0,8

^SNMON: "INS",0,32

^SNMON: "INS",0,64

^SNMON: "INS",0,256

Now all of sudden it does see ULTRAN networks? Why did it not choose one before, or even see one?

Hopefully someone here can give me some insight. 

Also please tell me if there any more information that could be usefull, I have access to a device and can easiliy run some more AT commands.

Best Regards

Mirza