XMONITOR does not show all parameters

[fastfox]

Hi,

When I first start the modem and connect to NW. XMONITOR AT command shows data like this:

%XMONITOR: 5,"","","24412","C739",9,20,"0017E878",4,6154,71,40,"","11100000","11100000

After ~2minutes, I have sent some data and requested PSM. When the command is issued again the data looks like this:

%XMONITOR: 5,"","","24412","C739",9,20,"0017E878",,,,,"","00010000","00111001"

So e.g. SNR is not present in the response. Strangely enough 

%XSNRSQ: 40

XSNRSQ command issued just before or after XMONITOR command does show the SNR. To me this implies that there is SNR known by the modem even if it is in power save mode.

So is this undocumented feature or a bug in XMONITOR or something else?

What I am trying to achieve is to get some basic info from NW connection quality, used operator etc. XMONITOR seemed like a perfect fit, but it does not seem to work how I expect.

[Håkon Alseth]

Hi,

 

So e.g. SNR is not present in the response. Strangely enough 

 This is because you're in PSM mode, as you mention: 

After ~2minutes, I have sent some data and requested PSM

The device is now in sleep mode, not communicating with the eNB, thus the signal level would be invalidated after a while. Once you go out of PSM and communicate again, the signal level shall be valid again. 

XSNRSQ command issued just before or after XMONITOR command does show the SNR. To me this implies that there is SNR known by the modem even if it is in power save mode.

XSNRSQ is reporting back a number that is "old" and isn't guaranteed to be valid once you start communicating with the eNB again. I'll report this back to the developers so that they can evaluate if this is intended behavior or not.

 

Kind regards,

Håkon

[fastfox]

Ok, you are right. XSNRSQ has a cache XMONITOR does not. I changed the logic to use the XMONITOR just before requesting PSM and now I get what I want.

Thanks.