Hi, We have a custom design using an nRF9160.
We can connect and program the device using a jLink though the debug port.
How can we connect the LTE link monitor to the board to transfer AT commands?
Currently our PCB only has access to P0.18 and P0.19 for debug (this can be modified in the next PCB revision).
Can these be re-programmed or are they part of the soft device?
Thanks
Hi Hakon,
I tried it on my DK and it worked on the analyser on ports 10/11.
Then I swapped to another serial interface and it worked so I guess is must the interface.
However I need to program the certs, send AT commands to the modem etc. so I think I have the wrong port?
Is it just a change of uart or do I need to do more?
Thanks Ian
Hi,
Yano said:However I need to program the certs, send AT commands to the modem etc. so I think I have the wrong port?
There's certain AT commands that cannot be provided once the modem is active (CFUN=1), writing certificates is one of these.
I would recommend that you use at_client instead of asset_tracker to write certificates into the modem.
Kind regards,
Håkon
Hi Håkon,
I honestly don't know what is going on here.
It's not the application that's the problem, we just don't get responses to any AT command.
I attached an analyser to the Tx and Rx pins and found there was not TX from our RS232 adapter.
But there always is RX (output from the nRF9160DK) and that never fails.
It seems the RS232 adapter seems to stop outputting when it is used by LTE link monitor!?
It does work reliably (sends AT commands and get responses back from the nRF9160DK) when we use a separate serial terminal application, but as soon as we move that over to LTE link monitor the serial port stops TXing?
We need to unplug and re-attach the USB for it to start TX'ing again?
I can only assume that the LTE link monitor is sending some USB command to the adapter when it connects that stops it TXing?
The device we are using is an FTDI TTL-232R-3V3 cable and we have tried swapping it out.
Any ideas?
Thanks Ian
Hi Ian,
Yano said:I attached an analyser to the Tx and Rx pins and found there was not TX from our RS232 adapter.
But there always is RX (output from the nRF9160DK) and that never fails.
It seems the RS232 adapter seems to stop outputting when it is used by LTE link monitor!?
It does work reliably (sends AT commands and get responses back from the nRF9160DK) when we use a separate serial terminal application, but as soon as we move that over to LTE link monitor the serial port stops TXing?
That is strange. In another terminal, does it respond with "OK" and so-forth? Do you have a printout from the second terminal?
Could you try the at_client sample, with the override for the uart0 pins, and see if this works in lte link monitor as well? Remember to properly disconnect the COM-port in the other terminal program before opening up a new one.
Kind regards,
Håkon
Hi Hakon,
below is the output from my terminal application com3 on my PC.
As you can see I send a AT+CGSN (echo is off on my terminal) and I receive the IMEI and OK.
If I disconnect from the com port and move over to LTE monitor I get no response.
Attached is a video showing what happens.
Ian
[00:01:39.552,947] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 0 Using: 0 Unhealthy: 0[0m
[00:01:39.561,889] [0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 99[0m
[00:01:40.553,039] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 0 Using: 0 Unhealthy: 0[0m
[00:01:40.562,072] [0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 100[0m
*** Booting Zephyr OS build v2.4.99-ncs1 ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0x10000
I: Jumping to the first image slot *** Booting Zephyr OS build v2.4.99-ncs1 ***
[00:00:00.212,341] [0m<inf> asset_tracker: Asset tracker started[0m
[00:00:00.218,536] [0m<inf> watchdog: Watchdog timeout installed. Timeout: 60000[0m
[00:00:00.226,104] [0m<inf> watchdog: Watchdog started[0m
[00:00:00.231,445] [0m<inf> watchdog: Watchdog feed enabled. Timeout: 30000[0m
[00:00:00.241,027] [0m<dbg> nrf_cloud_transport.nct_settings_set: Settings key: p_sesh, size: 4[0m
[00:00:00.249,938] [0m<dbg> nrf_cloud_transport.nct_settings_set: Read setting val: 1[0m
[00:00:00.266,479] [0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = imme-352656106114500[0m
[00:00:00.275,817] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/imme-352656106114500/shadow[0m
[00:00:00.287,567] [0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: imme-352656106114500/shadow/get/accepted[0m
[00:00:00.299,133] [0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/imme-352656106114500/shadow/get/rejected[0m
[00:00:00.311,828] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/imme-352656106114500/shadow/update/delta[0m
[00:00:00.324,798] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/imme-352656106114500/shadow/update[0m
[00:00:00.336,700] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/imme-352656106114500/shadow/get[0m
[00:00:00.348,724] [0m<inf> asset_tracker: Connecting to LTE network.[0m
[00:00:00.355,407] [0m<inf> asset_tracker: This may take several minutes.[0m
352656106114500
OK
352656106114500
OK
352656106114500
OK
+CEREG: 2,"2332","02574A20",9,0,0,"11100000","11100000"
[00:00:06.189,331] [0m<inf> asset_tracker: LTE cell changed: Cell ID: 39275040, Tracking area: 9010[0m
+CSCON: 1
[00:00:06.656,707] [0m<inf> asset_tracker: RRC mode: Connected[0m
+CEREG: 5,"2332","02574A20",9,,,"00000010","00000111"
[00:00:07.822,845] [0m<inf> asset_tracker: Connected to LTE network.[0m
[00:00:07.829,498] [0m<inf> asset_tracker: Connecting to cloud, attempt 1 of 8[0m
[00:00:07.836,914] [0m<inf> asset_tracker: Cloud connection request sent.[0m
[00:00:07.843,872] [0m<inf> asset_tracker: Connection response timeout is set to 30 seconds.[0m
[00:00:07.852,661] [0m<inf> asset_tracker: Network registration status: Connected - roaming[0m
[00:00:07.861,175] [0m<inf> asset_tracker: PSM parameter update: TAU: 4200, Active time: 4[0m
[00:00:07.869,812] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING[0m
[00:00:07.878,356] [0m<inf> asset_tracker: CLOUD_EVT_CONNECTING[0m
[00:00:08.292,541] [0m<dbg> nrf_cloud_transport.nct_connect: IPv4 address: 54.84.146.201[0m
[00:00:08.300,842] [0m<dbg> nrf_cloud_transport.nct_mqtt_connect: MQTT clean session flag: 0[0m
[00:00:08.317,718] [0m<inf> asset_tracker: DATE_TIME_OBTAINED_NTP[0m
[00:00:15.679,016] [0m<inf> nrf_cloud_transport: Using socket send timeout of 60 seconds[0m
[00:00:15.687,316] [0m<dbg> nrf_cloud.nrf_cloud_run: Cloud connection request sent.[0m
[00:00:16.036,926] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_CONNACK: result 0[0m
[00:00:16.045,959] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 2[0m
[00:00:16.053,649] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTED[0m
[00:00:16.062,164] [0m<inf> asset_tracker: CLOUD_EVT_CONNECTED[0m
[00:00:16.068,206] [0m<inf> asset_tracker: Persistent Sessions = 1[0m
[00:00:16.074,615] [0m<dbg> nrf_cloud_fsm.connection_handler: Previous session valid; skipping nct_cc_connect()[0m
[00:00:16.084,960] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 4[0m
[00:00:16.092,712] [0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 5678 opcode = 0 len = 0[0m
[00:00:16.103,271] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5[0m
[00:00:16.635,955] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 5678 result = 0[0m
[00:00:16.645,874] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5[0m
[00:00:17.134,246] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBLISH: id = 37220 len = 318[0m
[00:00:17.145,690] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5[0m
[00:00:17.153,381] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_RX_DATA[0m
[00:00:17.160,858] [0m<inf> asset_tracker: CLOUD_EVT_DATA_RECEIVED[0m
[00:00:17.168,182] [0m<inf> cloud_codec: [cloud_search_config:941] Found cfg item GPS, enable
[0m
[00:00:17.179,931] [0m<dbg> nrf_cloud_transport.nct_dc_endpoint_set: nct_dc_endpoint_set[0m
[00:00:17.188,537] [0m<dbg> nrf_cloud_fota.publish: Topic: prod/2ddfc1a3-8f03-4de5-988e-04f82d932d0d/imme-352656106114500/jobs/req[0m
[00:00:17.200,531] [0m<dbg> nrf_cloud_fota.publish: Payload (4 bytes): [""][0m
[00:00:17.208,740] [0m<dbg> nrf_cloud_transport.nct_dc_endpoint_get: nct_dc_endpoint_get[0m
[00:00:17.219,329] [0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 7890 opcode = 1 len = 362[0m
[00:00:17.230,743] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 7[0m
[00:00:17.238,433] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_USER_ASSOCIATED[0m
[00:00:17.246,643] [0m<inf> asset_tracker: CLOUD_EVT_PAIR_DONE[0m
[00:00:17.252,746] [0m<inf> asset_tracker: CLOUD_EVT_FOTA_ERROR[0m
[00:00:17.877,166] [0m<dbg> nrf_cloud_fota.nrf_cloud_fota_mqtt_evt_handler: MQTT_EVT_PUBACK: msg id 8767[0m
[00:00:18.237,091] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 7890 result = 0[0m
[00:00:18.247,100] [0m<dbg> nrf_cloud_fsm.cc_tx_ack_handler: Previous session valid; skipping nct_dc_connect()[0m
[00:00:18.257,385] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 9[0m
[00:00:18.265,075] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_READY[0m
[00:00:18.272,369] [0m<inf> asset_tracker: CLOUD_EVT_READY[0m
[00:00:18.279,388] [0m<dbg> nrf9160_gps.configure_antenna: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1565,1586[0m
[00:00:18.289,398] [0m<dbg> nrf9160_gps.configure_antenna: COEX0 set: AT%XCOEX0=1,1,1565,1586[0m
[00:00:18.298,126] [0m<dbg> nrf9160_gps.open_socket: GPS socket created, fd: 1232491587[0m
[00:00:18.306,365] [0m<inf> gps_control: GPS initialized[0m
[00:00:18.311,859] [0m<inf> asset_tracker: Starting GPS[0m
[00:00:18.360,595] [0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 1 opcode = 1 len = 627[0m
[00:00:18.372,619] [0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 2 opcode = 1 len = 57[0m
[00:00:18.385,528] [0m<inf> gps_control: Enabling PSM[0m
[00:00:18.391,876] [0m<inf> gps_control: PSM enabled[0m
[00:00:18.397,827] [0m<dbg> nrf9160_gps.enable_gps: GPS mode is enabled[0m
[00:00:18.409,667] [0m<dbg> nrf9160_gps.start: GPS operational[0m
[00:00:18.415,649] [0m<inf> gps_control: GPS started successfully. Searching for satellites [0m
[00:00:18.424,316] [0m<inf> gps_control: to get position fix. This may take several minutes.[0m
[00:00:18.432,983] [0m<inf> gps_control: The device will attempt to get a fix for 360 seconds, [0m
[00:00:18.441,894] [0m<inf> gps_control: before the GPS is stopped. It's restarted every 30 seconds[0m
[00:00:18.451,263] [0m<inf> asset_tracker: GPS_EVT_SEARCH_STARTED[0m
[00:00:18.457,641] [0m<dbg> nrf9160_gps.gps_thread: A-GPS data update needed[0m
[00:00:18.464,843] [0m<inf> asset_tracker: GPS_EVT_AGPS_DATA_NEEDED[0m
[00:00:19.410,003] [0m<dbg> nrf9160_gps.gps_thread: Waiting for time window to operate[0m
[00:00:19.418,090] [0m<inf> asset_tracker: GPS_EVT_OPERATION_BLOCKED[0m
[00:00:19.471,435] [0m<inf> asset_tracker: Sending A-GPS request[0m
[00:00:19.514,587] [0m<inf> asset_tracker: A-GPS request sent[0m
[00:00:22.597,412] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 1 result = 0[0m
[00:00:22.607,757] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 2 result = 0[0m
[00:00:22.617,675] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 4 result = 0[0m
[00:00:22.627,532] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBLISH: id = 37220 len = 1037[0m
[00:00:22.638,092] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 9[0m
[00:00:22.645,782] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_RX_DATA[0m
[00:00:22.653,228] [0m<inf> asset_tracker: CLOUD_EVT_DATA_RECEIVED[0m
[00:00:22.660,400] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.668,975] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.677,581] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.686,126] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.694,732] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.703,369] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.711,914] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.720,550] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.729,278] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.737,854] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.746,520] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.755,065] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.763,580] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.772,155] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.780,761] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.789,550] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.798,095] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.806,701] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.815,338] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.823,852] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.832,519] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.841,125] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.849,731] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.858,428] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.867,034] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.875,549] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.884,216] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.892,761] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.901,397] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.910,003] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.918,609] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 3[0m
[00:00:22.963,836] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 7[0m
[00:00:22.972,473] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 8[0m
[00:00:22.981,018] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 1[0m
[00:00:22.989,501] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 4[0m
[00:00:22.998,077] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 9[0m
[00:00:23.006,042] [0m<inf> agps: A-GPS data successfully processed[0m
[00:00:23.012,573] [0m<inf> asset_tracker: A-GPS data processed[0m
[00:00:23.018,920] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBLISH: id = 37220 len = 1926[0m
[00:00:23.029,571] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 9[0m
[00:00:23.037,200] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_RX_DATA[0m
[00:00:23.044,708] [0m<inf> asset_tracker: CLOUD_EVT_DATA_RECEIVED[0m
[00:00:23.052,795] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.062,438] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.071,990] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.081,573] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.091,217] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.100,860] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.110,595] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.120,117] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.129,608] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.139,099] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.148,651] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.158,294] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.167,816] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.177,551] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.187,072] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.196,685] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.206,451] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.215,911] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.225,524] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.235,137] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.244,720] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.254,394] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.263,977] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.273,498] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.283,325] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.292,938] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.302,581] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.312,072] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.321,594] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.331,115] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.340,698] [0m<dbg> nrf9160_gps.agps_write: Sent A-GPS data to modem, type: 2[0m
[00:00:23.348,663] [0m<inf> agps: A-GPS data successfully processed[0m
[00:00:23.355,224] [0m<inf> asset_tracker: A-GPS data processed[0m
