Thingy:91 Asset Tracker V2 GNSS doesn't get a fix when connecting to a specific operator

Hi,

Hope everything is fine with you!

There are three operators covering my workplace,

24007 tele2 --- PSM eDRX good ---
24008 Telenor --- PSM eDRX not supported ---
24001 telia --- PSM eDRX not supported ---

When I say `not supported`, I mean there is output `PSM parameter update: TAU: 3240, Active time: -1`.

I am working with GNSS recently, and found a strange issue,

when the thingy:91 connects to 24001, GNSS will fail to get a fix with a high possibility, around 3/4 GNSS location service fails,

but when thingy:91 connects to 24007, GNSS will always get fixes successfully.

At first, I think it could be that 24001 doesn't support PSM/eDRX, this will affect the GNSS because GNSS shares the same antenna with the LTE-M.

But then I found when thingy:91 connects to 24008, it still can get location fixes continuously and successfully.

I checked the paging time window by using `AT%XPTW?`, it is the same for both 24001 and 24008.

So my question is what is the key point to affect the GNSS function in this case for 24001 and 24008?

Any help will be much appreciated! Thanks!

BR,

Peng

Parents Reply Children
  • BTW, about the trace log, can I decode it with some tools? or it is only available for the Nordicsemi?

  • peng.cheng said:
    BTW, about the trace log, can I decode it with some tools? or it is only available for the Nordicsemi?

    You can use the Trace Collector v2 found in the nRF Connect for Desktop. This will allow you to convert the file to PCAP which you can open in Wireshark. 

    peng.cheng said:
    The SIM card is the iBASIS purchased together with the Thingy:91 board.

    Could you please try with a local SIM i.e. Telenor or Telia SIM. It might be that the iBasis SIM is not allowed. Have a look at the iBasis eSIM International Coverage Update

  • Hi,

    Thank you for the Trace Collector v2 tip.

    I can try to get a local SIM, this may cost some time.

    But correct me if I am wrong, but PSM seems not very important in my case (though I don't trust my gut feeling in this case).

    Thingy:91 can get GNSS fixes when connecting to 24008 which doesn't support PSM in a residential area that is a bit far away from the city center (the first test place).

    But in the meantime, Thingy:91 can't get GNSS fixes when connecting to 24007 which supports PSM in some places in the city center (the second test place). ([01:33:03.299,591] [0m<dbg> modem_module: lte_evt_handler: PSM parameter update: TAU: 1152000, Active time: 20)

    So I am a bit confused which is the key point that affects the GNSS. Could you please help to check the logs that if there is something wrong? Thanks!

    BR,

    Peng

  • Sorry, I got too focused on the eDRX issue. 

    It is important to know that the GPS receiver operation is time multiplexed with LTE modem, and it is possible to use the GPS and QZSS receiver to obtain position either while the LTE is in RRC Idle mode or power saving mode (PSM), or when the LTE modem is completely deactivated. Also note, GPS signals do not usually penetrate ceilings or other structures. For best GPS performance, Nordic Thingy:91 should be used outside in an open space, far from sources of interference and other structures that may block the signals.

    Where are you performing the tests of the GPS? 


  • No worries!

    I tested in mainly two places,

    one is  in a residential area that is a bit far away from the city center,

    the other is on the top floor of an 8-floor building near the city center,

    both two places are outside places and have no visual blocks to the sky.

Related