No GPS fix on Thingy:91 when using iBasis or O2 sim card in UK

[JBT]

Hi,

We're trying to evaluate the nRF9160 in the East of the UK, where there is the O2/LTE-M network.

We can get an LTE-M connection, though there is no PSM or eDRX possible in either the iBasis sim card or in an O2 sim card.  Unfortunately, nobody in O2 has ever heard of LTE-M or IoT and there 'contact' page' does not work...  There are no contact phone numbers.

The GPS unit does not work, either when using the onboard antenna (for which we believe there are wrong matchign components) or when using an external antennGNSS antenna.

Is there an evaluation board where the GPS works?

Should we switch to the nRF9160 DK ?

We found an errata saying that the wrong matching antenna components were used on the Thingy:91

How was a product released with the wrong matchign components?

Didn't somebody take it outside and see if it worked?

Shoudl we build our own board?

Thanks

James

[JONATHAN LL]

Hi James,


The O2 SIM should provide you whit GPS functionality when using the asset tracer application on the Thingy:91 in the UK, iBasis on the other side has the PSM/eDRX problem witch results in no GPS functionality in the asset tracker example. 

O2 is part of Telefonica and they support nationwide LTE-M coverage. https://www.gsma.com/iot/deployment-map/#GB lists the operators and what they support and where. 

There is however a different example that gets GPS data but it does not connect to the cloud. what it does is print out the data over UART. If you just want to test GPS. 


How did you program the Thingy:91? 

What version of the Thingy:91 do you have? (on the sticker underneath the cover right under the PCA20035)

I am sorry I cant do much about the contact page at O2 but I will do my best to solve your problem and I believe we can find a solution.
 
Regards,
Jonathan

[JBT]

Version is: PCA20035/1.4.0/2020.24

Regarding PSM/eDRX, I am not CONVINCED that it works with *any* sim card yet in the UK.  Unfortunately, it is just impossible to say though as O2 are totally unhelpful and there is literally nobody to ask...  We have tried both native SIM cards and the iBasis - none work with PSM or eDRX.  Unfortunately there is nothing technical available from O2.  It's just advertising hype with smily people.

Also, note that O2 does NOT yet provide nationwide coverage of LTE-M. LIKE YOU SAY. They have about 1/2 of the country supported - the Eastern side.  We are lucky to be included in the side that does currently support it.  FYI: The coverage map is as follows: https://www.o2.co.uk/business/support/network-support/lte-status-checker.  e.g. even some of the large module vendors cannot yet test ay end-product unless they drive to the other side of London or use a simulator.

After several sessions on the weekend and today, we managed to get ONE (1) fix.  The rest of the time, it seems that the device either cannot see satellites or the signal is just too weak to receive anything, when using that onboard antenna.  We have tried both your cloud platform and a direct connection via the LTE Link Monitor, when the Thingy is connected to a laptop computer in the open space, with a clear view of the UK sky.  Yes, we pressed the button for 10-seconds. 

We just used flashed the latest/default firmware downloaded from your site using your tools.

Note - the satellite reception is excellent here.  I have another EVK from an alternative module maker which works perfectly and there are indeed plenty of satellites in view at all times.

Regards

James

[JBT]

I have attached your log output

====================

[01:42:54.872,863] 

[0m<inf> gps_control: GPS started successfully. Searching for satellites 

[0m

[01:42:54.881,439] 

[0m<inf> gps_control: to get position fix. This may take several minutes.

[0m

[01:42:54.889,953] 

[0m<inf> gps_control: The device will attempt to get a fix for 360 seconds, 

[0m

[01:42:54.898,773] 

[0m<inf> gps_control: before the GPS is stopped. It's restarted every 900 seconds

[0m

[01:42:54.907,989] 

[0m<inf> gps_control: or as soon as 30 seconds later when movement occurs.

[0m

[01:42:54.916,870] 

[0m<inf> asset_tracker: GPS_EVT_SEARCH_STARTED

[0m

[01:42:54.923,156] 

[0m<dbg> nrf9160_gps.gps_thread: A-GPS data update needed

[0m

[01:42:54.930,419] 

[0m<inf> asset_tracker: GPS_EVT_AGPS_DATA_NEEDED

[0m

[01:42:54.936,920] 

[1;33m<wrn> asset_tracker: A-GPS request was sent less than 1 hour ago

[0m

[01:42:55.531,158] 

[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 2 result = 0

[0m

[01:42:55.543,182] 

[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 952 result = 0

[0m

[01:42:55.866,943] 

[0m<dbg> nrf9160_gps.gps_thread: Waiting for time window to operate

[0m

[01:42:55.875,000] 

[0m<inf> asset_tracker: GPS_EVT_OPERATION_BLOCKED

[0m

%CESQ: 28,1,3,0

[01:42:57.642,333] 

[0m<dbg> aws_fota.on_publish_evt: Received topic: prod/a17c818b-a4ab-4cdd-8c45-f03b510301ab/m/d/nrf-352656101420100/c2d

[0m

[01:42:57.654,846] 

[0m<dbg> aws_fota.on_publish_evt: received an unhandled MQTT publish event on topic: prod/a17c818b-a4ab-4cdd-8c45-f03b510301ab/m/d/nrf-352656101420100/c2d

[0m

[01:42:57.670,349] 

[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBLISH: id = 16372 len = 1864

[0m

[01:42:57.680,603] 

[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 9

[0m

[01:42:57.688,201] 

[0m<dbg> nrf_cloud.event_handler: NRF_CLOUD_EVT_RX_DATA

[0m

[01:42:57.695,220] 

[0m<inf> asset_tracker: CLOUD_EVT_DATA_RECEIVED

[0m

[01:42:57.702,087] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.710,632] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.719,146] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.727,661] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.736,053] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.744,415] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.752,929] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.761,413] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.769,775] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.778,320] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.786,834] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.795,349] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.803,741] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.812,133] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.820,770] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.829,132] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.837,677] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.846,191] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.854,583] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.862,976] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.871,368] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.879,760] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.888,305] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.896,636] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.905,029] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.913,482] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.921,875] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.930,267] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.938,629] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.947,143] 

[0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2

[0m

[01:42:57.955,078] 

[0m<inf> asset_tracker: A-GPS data processed

[0m

[01:43:01.447,662] 

[0m<dbg> nrf9160_gps.gps_thread: GPS has time window to operate

[0m

[01:43:01.455,352] 

[0m<inf> asset_tracker: GPS_EVT_OPERATION_UNBLOCKED

[0m

[01:43:01.462,158] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 0 Using: 0 Unhealthy: 0

[0m

[01:43:01.471,069] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 6181

[0m

[01:43:02.447,845] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 0 Using: 0 Unhealthy: 0

[0m

[01:43:02.456,726] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 6182

[0m

[01:43:03.447,875] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 0 Using: 0 Unhealthy: 0

[0m

[01:43:03.456,756] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 6183

[0m

[01:43:04.447,906] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 0 Using: 0 Unhealthy: 0

[0m

[01:43:04.456,787] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 6184

[0m

[01:43:05.447,967] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 0 Using: 0 Unhealthy: 0

[0m

[01:43:05.456,878] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 6185

[0m

[01:43:06.447,906] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 0 Using: 0 Unhealthy: 0

[0m

[01:43:06.456,787] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 6186

[0m

[01:43:07.447,662] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 0 Using: 0 Unhealthy: 0

[0m

[01:43:07.456,542] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 6187

[0m

[01:43:08.448,028] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 0 Using: 0 Unhealthy: 0

[0m

[01:43:08.456,909] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 6188

[0m

[01:43:09.448,028] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 0 Using: 0 Unhealthy: 0

[0m

[01:43:09.456,909] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 6189

[0m

[01:43:10.448,059] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 0 Using: 0 Unhealthy: 0

[0m

[01:43:10.456,939] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 6190

[0m

[01:43:11.447,814] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 0 Using: 0 Unhealthy: 0

[0m

[01:43:11.456,695] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 6191

[0m

[01:43:12.447,998] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 0 Using: 0 Unhealthy: 0

[0m

[01:43:12.456,848] 

[0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 6192

[0m

[JBT]

Sorry for the mes - tyhis is what you output and I do not have the time or patience to re-format.

[JBT]

We have reported the kit as faulty to Digikey, whih have issued a refund and we will try to get this going on a custom PCB or with the other kit, which hopefully works or at least has been tested.

[JONATHAN LL]

Here is a tip on how to get the data easily from the nRF Connect - LTE Link Monitor whiteout having to do a lot of reformatting. I can still read the log fine, no worries.

In the lower right corner there are 3 buttons, one of them opens up the logfile as a simple txt file. Then you can attach the txt file instead. 
Here is a picture:



Regards,
Jonathan