PLS8-E: serving cell, TX_power error? | Telit Cinterion IoT Developer Community
June 19, 2017 - 2:40pm, 2229 views
Hello,
We've found out that our PLS8-E device is reporting strange values for TX_power parameter in serving cell information. In two consecutive requests of the cell information (AT^SMONI=255) we receive one common value and other one with a possibly erroneous value:
06/19/2017 12:25:55 PM 4G,...,...,20,20,FDD,...,...,8602,...,...,-10,-68,-8,CONN
06/19/2017 12:25:56 PM 4G,...,...,20,20,FDD,...,...,8602,...,...,-32768,-68,-6,CONN
As it can be seen, first value (-10) seems to be normal, while the value given just one second after that (-32768) is not comprehensible. I see no more detailed information for this parameter in the documentation.
What could be the reason for the strange RX level values given by the command?
Best regards,
Raul.
Hello,
How often do you get such value? Have you seen any other strange values of this parameter?
You are right that there is not much about this parameter in the AT commands specification. It should be possible to find more about transmission power in 3GPP documentation.
I have checked that decimal value 32768 equals 8000 hex and 1000000000000000 bin so it is distinctive and out of range. So it must have a special meaning. Which must be that the real measurement is not available at the moment similarly to ber or rssi where 99 means not known or not detectable.
Best regards,
Bartłomiej
Hello,
That value is received quite often, 2-3 ***** out of 10 requests approximately, however it's always the same strange value, no other rare values are given, so probably you are right and it's just a special value meaning there's no valid value to be showed.
Thanks for your answer.
Best regards,
Raul.
Hello,
In a meantime we have also tested this and have also seen this value.
I think that there is a reason why you see it so frequently - as it's used uplink power it can only be measured when there is an uplink transmission at the moment of measurement. And the transmission is not continuous. So you should ignore this value and treat it as no value.
Regards,
Bartłomiej
Hello,
Fine, thanks for additional info.
Regards,
Raúl Suárez.