Error in ^SMONP output of PLS8-E | Telit Cinterion IoT Developer Community
June 15, 2020 - 11:09am, 1120 views
When camped on a non3G-cell, the PLS8-E with software 03.017 produces defective output regarding neighboring 3G-cells (^SMONI just for information). In the case of camping on a 2G cell, the output seems only syntactically defective, the values seem correct, but in case of camping on a 4G cell, the output is totally screwed. The PSC is probably not correct, Ec/n0 is way too big, RSCP is way too small, Squal seems wrong too, and SRxLev is missing.
^SMONI: 4G,1650,3,10,10,FDD,262,03,E8EF,162CA1B,194,61,-62,-8,NOCONN
4G:
(...)
2G:
(...)
3G:
10737,26,45.0,-510,56,
10737,23,200.0,-670,40,
10737,31,160.0,-630,44,
10786,---,-----,----,--
(UARFCN,PSC,EC/n0,RSCP,SQual,SRxLev)
^SMONI: 2G,706,-54,262,03,E6B7,4C87,41,41,3,2,E,0,-106,NOCONN
2G:
(...)
3G:
10737 390-17.5, -72
10737 369-24.0, -83
(UARFCNn,PSCn,EC/n0n,RSCPn)
4G:
(...)
Hello,
Could you check the firmware version with ATI1 command?
Please also note that there are 2 versions of SMONP reply - the standard and enhanced and that the number of parameters displayed for the neighbouring cell depends on what type of cell the module is registered to.
Best regards,
Bartłomiej
Hi,
here we go:
ati1
Cinterion
PLS8-E
REVISION 03.017
A-REVISION 01.000.09
I know that at^smonp and at^smonp=255 SHOULD give me different output versions, but, unfortunately:
at^smonp
4G: (...)
2G: (...)
3G:
10737,14,70.0,-530,54,
10737,12,95.0,-560,51,
at^smonp=255
4G: (...)
2G: (...)
3G:
10737,14,60.0,-500,57,
10737,12,80.0,-520,55,
OK
According to the manual (Version 03.016 from February 23, 2016) this should be UARFCN,PSC,EC/n0,RSCP,SQual,SRxLev,set,rank
Lets see:
UARFCN - seems OK
PSC - wrong. This PSC is not used nearby
EC/n0 - could never be 60 or 80
RSCP - could never be in that range
SQual - could not be in that range
SRxLev,set,rank - are missing
Hello,
I did some tests with the same firmware version and I was able to see the similar outputs as in your case. If it is important for you to monitor the neighboring cells of other RATs I suggest you to report this issue to your local Thales M2M sales or distributor. Maybe they can offer you an alternative.
Regards,
Bartłomiej