SDK 1.8.0 The AT#XAGPS=1,1 command doesn't working

Hello, I am using board nRF9160-dk (sdk 1.8.0).
I need to get geolocation data using AGPS, for this I use the following sequence of AT commands:

AT%XSYSTEMMODE=1,0,1,0
AT%XMAGPIO=1,0,0,1,1,1574,1577
AT%XCOEX0
AT+CEREG=5
AT+CPSMS=1
AT+CFUN=1
AT#XNRFCLOUD=1
AT#XAGPS=1,1

But always on the command AT#XAGPS=1,1 I get the answer "ERROR".
What's my mistake? And why just "AT#XGPS=1,1" works correctly.

Parents

0 Øyvind over 4 years ago

Hello,

The #XAGPS command runs the GNSS together with the nRF Cloud A-GPS service. This requires access to nRF Cloud through the LTE network for receiving A-GPS data.

Have you connected to nRF Cloud?

Kind regards,
Øyvind
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

0 Stas Jis over 4 years ago in reply to Øyvind

Hello,
To connect to the cloud service, use the command: AT#XNRFCLOUD=1.
In response we get:

<< OK
<< #XNRFCLOUD: {"desired":{"pairing":{"state":"paired","topics":{"d2c":"prod/669fbe44-b8e6-41e1-b298-6afb63e45691/m/d/nrf-352656108600480/d2c","c2d":"prod/669fbe44-b8e6-41e1-b298-6afb63e45691/m/d/nrf-352656108600480/c2d"}},"nrfcloud_mqtt_topic_prefix":"prod/669fbe44-b8e6-41e1-b298-6afb63e45691/"},"config":{"GPS":{"enable":false}}}
<< #XNRFCLOUD: 1,0

Reply

0 Stas Jis over 4 years ago in reply to Øyvind

Hello,
To connect to the cloud service, use the command: AT#XNRFCLOUD=1.
In response we get:

<< OK
<< #XNRFCLOUD: {"desired":{"pairing":{"state":"paired","topics":{"d2c":"prod/669fbe44-b8e6-41e1-b298-6afb63e45691/m/d/nrf-352656108600480/d2c","c2d":"prod/669fbe44-b8e6-41e1-b298-6afb63e45691/m/d/nrf-352656108600480/c2d"}},"nrfcloud_mqtt_topic_prefix":"prod/669fbe44-b8e6-41e1-b298-6afb63e45691/"},"config":{"GPS":{"enable":false}}}
<< #XNRFCLOUD: 1,0

Children

0 Øyvind over 4 years ago in reply to Stas Jis
Hello,
I've just tested on my side. Are you using the precompiled firmware?

In the pjr.conf of the Serial LTE Modem, you will need to enable AGPS (disabled by default).

# nRF Cloud based location services CONFIG_SLM_AGPS=y

Note that the SLM uses RTT to print the Application log, which you can access via Segger J-Link RTT Viewer.

# Segger RTT CONFIG_USE_SEGGER_RTT=y CONFIG_RTT_CONSOLE=y CONFIG_UART_CONSOLE=n CONFIG_LOG_BACKEND_RTT=y CONFIG_LOG_BACKEND_UART=n

Kind regards,
Øyvind
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Øyvind over 4 years ago in reply to Stas Jis
Hello,
I've just tested on my side. Are you using the precompiled firmware?

In the pjr.conf of the Serial LTE Modem, you will need to enable AGPS (disabled by default).

# nRF Cloud based location services CONFIG_SLM_AGPS=y

Note that the SLM uses RTT to print the Application log, which you can access via Segger J-Link RTT Viewer.

# Segger RTT CONFIG_USE_SEGGER_RTT=y CONFIG_RTT_CONSOLE=y CONFIG_UART_CONSOLE=n CONFIG_LOG_BACKEND_RTT=y CONFIG_LOG_BACKEND_UART=n

Kind regards,
Øyvind
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

0 Stas Jis over 4 years ago in reply to Øyvind

I'm using the newly downloaded "Serial lte monitor" project (for sdk 1.8).
We use an external GPS antenna (everything is works in the simple GPS version):

2022-02-13T15:29:38.138Z DEBUG modem >> AT+CFUN?
2022-02-13T15:29:38.161Z DEBUG modem << 0
2022-02-13T15:29:38.166Z DEBUG modem << OK
2022-02-13T15:29:39.493Z DEBUG modem >> AT
2022-02-13T15:29:39.510Z DEBUG modem << OK
2022-02-13T15:29:58.677Z DEBUG modem >> AT%XSYSTEMMODE=0,0,1,0
2022-02-13T15:29:58.696Z DEBUG modem << OK
2022-02-13T15:30:14.790Z DEBUG modem >> AT%XMAGPIO=1,0,0,1,1,1574,1577
2022-02-13T15:30:14.812Z DEBUG modem << OK
2022-02-13T15:30:23.556Z DEBUG modem >> AT%XCOEX0
2022-02-13T15:30:23.574Z DEBUG modem << OK
2022-02-13T15:30:34.637Z DEBUG modem >> AT+CFUN=31
2022-02-13T15:30:34.656Z DEBUG modem << OK
2022-02-13T15:30:42.636Z DEBUG modem >> at#xgps=1,1
2022-02-13T15:30:42.654Z DEBUG modem << OK
2022-02-13T15:31:23.751Z DEBUG modem << #XGPS: 32.706002,35.172615,169.329712,32.686913,0.458134,0.000000,"2022-02-13 15:31:24"

I checked configuration settings, CONFIG_SLM_AGPS setting is enabled. I apply all the settings from the config file:

# General config
CONFIG_LOG=y
CONFIG_LOG_DEFAULT_LEVEL=3
CONFIG_STACK_SENTINEL=y
CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_RING_BUFFER=y

# Segger RTT
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_UART=n

# Network
CONFIG_NETWORKING=y
CONFIG_NET_SOCKETS=y
CONFIG_NET_NATIVE=n

# Modem library
CONFIG_NRF_MODEM_LIB=y
# Align the max FD entry to NRF_MODEM_MAX_SOCKET_COUNT(8)
CONFIG_POSIX_MAX_FDS=8
# Enable below for modem trace
#CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y

# Use GPIO
CONFIG_GPIO=y
CONFIG_GPIO_NRFX=y
CONFIG_GPIO_NRF_P0=y

# UART interface
CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y
CONFIG_NRFX_TIMER2=y

# Stacks and heaps
CONFIG_MAIN_STACK_SIZE=4096
CONFIG_HEAP_MEM_POOL_SIZE=16384
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096

# Device power management
CONFIG_PM_DEVICE=y

# FOTA
CONFIG_HTTP_PARSER_URL=y
CONFIG_FOTA_DOWNLOAD=y
CONFIG_FOTA_DOWNLOAD_PROGRESS_EVT=y
CONFIG_DFU_TARGET=y
CONFIG_DOWNLOAD_CLIENT=y
CONFIG_DOWNLOAD_CLIENT_STACK_SIZE=4096
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_IMG_MANAGER=y

# FLASH
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_MPU_ALLOW_FLASH_WRITE=y
CONFIG_IMG_ERASE_PROGRESSIVELY=y

# Settings
CONFIG_SETTINGS=y
CONFIG_SETTINGS_FCB=y
CONFIG_FCB=y

# nRF Cloud
CONFIG_CLOUD_API=y
CONFIG_NRF_CLOUD_MQTT=y
CONFIG_NRF_CLOUD_FOTA=n
CONFIG_NRF_CLOUD_AGPS=y
CONFIG_NRF_CLOUD_PGPS=y
CONFIG_NRF_CLOUD_CELL_POS=y
CONFIG_NRF_CLOUD_LOG_LEVEL_INF=y
CONFIG_DATE_TIME=y
CONFIG_MODEM_INFO=y
CONFIG_MODEM_INFO_ADD_DATE_TIME=n
CONFIG_AT_MONITOR=y
CONFIG_MODEM_JWT=y
# Use "nrf-<IMEI>" as the default device_id format
# Use "<device_uuid>" as the device_id format by below
#CONFIG_NRF_CLOUD_CLIENT_ID_SRC_INTERNAL_UUID=y

#
# SLM-specific configurations
#
CONFIG_SLM_CUSTOMIZED=n
CONFIG_SLM_LOG_LEVEL_INF=y
CONFIG_SLM_EXTERNAL_XTAL=n
CONFIG_SLM_START_SLEEP=n
# Use UART_0 (when working with PC terminal)
CONFIG_UART_0_NRF_HW_ASYNC_TIMER=2
# Use UART_2 (when working with external MCU)
#CONFIG_SLM_CONNECT_UART_2=y
#CONFIG_UART_2_NRF_HW_ASYNC_TIMER=2
# nRF Cloud based location services
CONFIG_SLM_AGPS=y
CONFIG_SLM_PGPS=y
CONFIG_SLM_CELL_POS=n

Now I see that for the AT#XNRFCLOUD=1 command, the expected response "#XNRFCLOUD: 1.0" does not come (only "OK").

The command for AGPS (AT#XAGPS=1,1) does not work either.

0 Øyvind over 4 years ago in reply to Stas Jis

What does the application log print?

Stas Jis said:
I checked configuration settings, CONFIG_SLM_AGPS setting is enabled. I apply all the settings from the config file:

Was this enabled in the initial issue also?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

0 Stas Jis over 4 years ago in reply to Øyvind

Øyvind: What does the application log print?

2022-02-16T07:48:40.622Z INFO Application data folder: C:\Users\stas\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2022-02-16T07:48:40.798Z DEBUG App pc-nrfconnect-linkmonitor v2.0.0 official
2022-02-16T07:48:40.799Z DEBUG App path: C:\Users\stas\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2022-02-16T07:48:40.799Z DEBUG nRFConnect 3.10.0, required by the app is (^3.8.0)
2022-02-16T07:48:40.799Z DEBUG nRFConnect path: C:\Users\stas\AppData\Local\Programs\nrfconnect\resources\app.asar
2022-02-16T07:48:40.799Z DEBUG HomeDir: C:\Users\stas
2022-02-16T07:48:40.800Z DEBUG TmpDir: C:\Users\stas\AppData\Local\Temp
2022-02-16T07:48:47.733Z INFO Modem port is opened
2022-02-16T07:48:47.791Z DEBUG modem >> AT+CFUN?
2022-02-16T07:48:54.464Z DEBUG modem << Ready
2022-02-16T07:48:56.893Z INFO Modem port is closed
2022-02-16T07:48:59.948Z INFO Modem port is opened
2022-02-16T07:48:59.985Z DEBUG modem >> AT+CFUN?
2022-02-16T07:49:00.011Z DEBUG modem << +CFUN: 0
2022-02-16T07:49:00.031Z DEBUG modem << OK
2022-02-16T07:49:20.369Z DEBUG modem >> AT%XSYSTEMMODE=1,0,1,0
2022-02-16T07:49:20.394Z DEBUG modem << OK
2022-02-16T07:49:27.696Z DEBUG modem >> AT%XMAGPIO=1,0,0,1,1,1574,1577
2022-02-16T07:49:27.718Z DEBUG modem << OK
2022-02-16T07:49:33.026Z DEBUG modem >> AT%XCOEX0
2022-02-16T07:49:33.046Z DEBUG modem << OK
2022-02-16T07:49:38.567Z DEBUG modem >> AT+CEREG=5
2022-02-16T07:49:38.587Z DEBUG modem << OK
2022-02-16T07:49:44.705Z DEBUG modem >> AT+CPSMS=1
2022-02-16T07:49:44.724Z DEBUG modem << OK
2022-02-16T07:49:50.463Z DEBUG modem >> AT+CFUN=1
2022-02-16T07:49:50.513Z DEBUG modem << OK
2022-02-16T07:49:52.064Z DEBUG modem << +CEREG: 2,"026F","00332521",7
2022-02-16T07:49:53.603Z DEBUG modem << +CEREG: 5,"026F","00332521",7,,,"00011110","11100000"
2022-02-16T07:49:53.645Z DEBUG modem >> AT+COPS=3,2
2022-02-16T07:49:53.683Z DEBUG modem << OK
2022-02-16T07:49:53.711Z DEBUG modem >> AT+COPS?
2022-02-16T07:49:53.741Z DEBUG modem << +COPS: 0,2,"42502",7
2022-02-16T07:49:53.751Z DEBUG modem << OK
2022-02-16T07:49:53.809Z DEBUG modem >> AT%XCBAND
2022-02-16T07:49:53.821Z DEBUG modem << %XCBAND: 3
2022-02-16T07:49:53.828Z DEBUG modem << OK
2022-02-16T07:49:53.856Z DEBUG modem >> AT+CGDCONT?
2022-02-16T07:49:53.876Z DEBUG modem << +CGDCONT: 0,"IP","IBASIS.IOT","10.160.220.88",0,0
2022-02-16T07:49:53.883Z DEBUG modem << OK
2022-02-16T07:49:53.915Z DEBUG modem >> AT+CGACT?
2022-02-16T07:49:53.931Z DEBUG modem << +CGACT: 0,1
2022-02-16T07:49:53.936Z DEBUG modem << OK
2022-02-16T07:50:04.552Z DEBUG modem >> AT#XNRFCLOUD=1
2022-02-16T07:50:04.578Z DEBUG modem << OK
2022-02-16T07:53:55.524Z DEBUG modem >> AT
2022-02-16T07:53:55.550Z DEBUG modem << OK
2022-02-16T07:54:06.952Z DEBUG modem >> AT#XAGPS=1,1
2022-02-16T07:54:06.970Z DEBUG modem << ERROR
2022-02-16T07:54:06.975Z ERROR Error: AT#XAGPS=1,1
 failed

Was this enabled in the initial issue also?

The CONFIG_SLM_AGPS configuration option was not initially enabled. After activating this option, "segger embedded studio" showed that there were changes in the project was rebuilt and flash to the board.