This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

A-GPS using SUPL doesn't work

DK: v0.9.0
nrf: v1.2.0
supl fw: v0.5.2
modem fw: v1.2.0
OS: Windows10

I'm trying to use assited GPS in "gps" sample program, but it doesn't work. This is log. There is no comments about SUPL.

*** Booting Zephyr OS build v2.1.99-ncs1  ***
Staring GPS application
Socket created
Getting GPS data...
Tracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 0

Scanning [|] Tracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 0

Scanning [/] Tracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 1

Scanning [-] Tracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 1

Scanning [\] Tracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 2

Scanning [|] Tracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 2

Scanning [/] Tracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 3

Scanning [-] Tracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 3

Scanning [\] Tracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 4

Scanning [|] Tracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 4

Scanning [/] Tracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 5

Scanning [-] Tracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 5

Scanning [\]

prj.conf

CONFIG_BSD_LIBRARY=y
CONFIG_STDOUT_CONSOLE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_AT_CMD=y
CONFIG_AT_NOTIF=y

# Enable SUPL client support
CONFIG_SUPL_CLIENT_LIB=y # Set y 

# Networking
CONFIG_NETWORKING=y
CONFIG_NET_SOCKETS_OFFLOAD=y
CONFIG_NET_SOCKETS=y
CONFIG_NET_SOCKETS_POSIX_NAMES=y
CONFIG_NET_SOCKETS_SOCKOPT_TLS=y

# Disable native network stack to save some memory
CONFIG_NET_NATIVE=n

# Main thread
CONFIG_HEAP_MEM_POOL_SIZE=2048
CONFIG_MAIN_STACK_SIZE=4096

In main.c,

supl_init function is executed successfully.
gps_data->data_id value is always 1 or 2 and it isn't set 3.

Any help?

Parents

0 Håkon Alseth over 5 years ago

Hi,

It seems that the configuration has not been applied properly. After printing "Getting GPS data" it should fetch AGPS data if SUPL is enabled.

Could you try to re-import the gps project (with clean build folder) to see if this helps?

Kind regards,

Håkon
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Yusuke over 5 years ago in reply to Håkon Alseth

I can't get SUPL data even when I re-imported the project... I attached additional info below. Do you have any advice? Thank you in advance.

I'm using iBasis SIM

a-gps.zip
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Håkon Alseth over 5 years ago in reply to Yusuke

Hi,

I think that your west is out-dated. Could you try "pip3 install west --upgrade" and see if it starts working?

Also, could you try the latest version of SES-NE (nordic edition) to see if the behavior when compiling is similar?

You could try to use west to build as well, "cd samples/nrf9160/gps && west build -b nrf9160_pca10090ns".

Kind regards,

Håkon
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

0 Yusuke over 5 years ago in reply to Håkon Alseth

>I think that your west is out-dated. Could you try "pip3 install west --upgrade" and see if it starts working?

This works out! Thank you so much!

I tried AGPS with iBasis SIM and got this error.

New AGPS data requested, contacting SUPL server, flags 59
Established LTE link
ip adc2:4cc0:: (c04cc2ad) port 7276
Starting SUPL session

ULP encoding length: 38
Bytes sent: 38
Bytes received: 34
ULP ossDecode success, choice 3
SUPL server responded using version 2.0.4
SUPL response received
ULP encoding length: 57
Bytes sent: 57
Bytes received: 708
ULP ossDecode more input 4
Bytes received: 1416
ULP ossDecode more input 4
Bytes received: 2124
ULP ossDecode more input 4
Bytes received: 2832
ULP ossDecode more input 4
Bytes received: 3067
ULP ossDecode success, choice 5
Injected AGPS data, flags: 1, size: 16
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 2, size: 72
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 3, size: 32
Injected AGPS data, flags: 8, size: 4
Injected AGPS data, flags: 4, size: 8
Injected AGPS data, flags: 6, size: 144
No location data available
Injected AGPS data, flags: 7, size: 16
MCC location info injected, MCC: 440
        Lat: 4603642 Lon: 2132664
        Unc semiminor: 127
        Unc semimajor: 127
        Confidence: 90
        Orientation: 0
SUPL POS received
read again
read again
read again
read error: -1
ULP ossDecode fail 5
SUPL error: 1
ULP encoding length: 34
Sending SUPL message failed, bytes_sent: -1
SUPL session internal resources released
SUPL session finished
Done

Also I tested the same program with another SIM. Then I got another error.

New AGPS data requested, contacting SUPL server, flags 59
Established LTE link
Failed to resolve hostname supl.google.com on IPv4, errno: 0)

Can you give me any help?

0 Håkon Alseth over 5 years ago in reply to Yusuke

Hi,

Yusuke said:
I tried AGPS with iBasis SIM and got this error.

Does it give this error every time? Are you connecting over LTE M1, or NB1?

We have seen some stability issues when using this in combination with NB1.

Yusuke said:
Also I tested the same program with another SIM. Then I got another error.

failure to resolve the hostname usually indicates that the vendor does not provide DNS. Is this over NB-IoT? If yes, can you try setting CONFIG_LTE_LEGACY_PCO_MODE=y?

Kind regards,

Håkon
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

0 Yusuke over 5 years ago in reply to Håkon Alseth

I was intending to use LTE-M. This is prj.conf and there is no command related to NB-IoT or M1.

Do I miss anything?

CONFIG_BSD_LIBRARY=y
CONFIG_STDOUT_CONSOLE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_AT_CMD=y
CONFIG_AT_NOTIF=y

# Enable SUPL client support
CONFIG_SUPL_CLIENT_LIB=y

# Networking
CONFIG_NETWORKING=y
CONFIG_NET_SOCKETS_OFFLOAD=y
CONFIG_NET_SOCKETS=y
CONFIG_NET_SOCKETS_POSIX_NAMES=y
CONFIG_NET_SOCKETS_SOCKOPT_TLS=y

# Disable native network stack to save some memory
CONFIG_NET_NATIVE=n

# Main thread
CONFIG_HEAP_MEM_POOL_SIZE=2048
CONFIG_MAIN_STACK_SIZE=4096

CONFIG_LTE_LOCK_BANDS=y
CONFIG_LTE_LOCK_BAND_MASK="10000000"

0 Yusuke over 5 years ago in reply to Yusuke

when I append these lines, I got an error. Any tip?

CONFIG_LTE_LINK_CONTROL=y
CONFIG_LTE_NETWORK_MODE_LTE_M_GPS=y

*** Booting Zephyr OS build v2.1.99-ncs1  ***
Staring GPS application
Failed to initialize modem

Reply

0 Yusuke over 5 years ago in reply to Yusuke

when I append these lines, I got an error. Any tip?

CONFIG_LTE_LINK_CONTROL=y
CONFIG_LTE_NETWORK_MODE_LTE_M_GPS=y

*** Booting Zephyr OS build v2.1.99-ncs1  ***
Staring GPS application
Failed to initialize modem

Children

0 Yusuke over 5 years ago in reply to Yusuke

>failure to resolve the hostname usually indicates that the vendor does not provide DNS.

This means SIM Card vendor right? I'm using MVNO SIM card
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Håkon Alseth over 5 years ago in reply to Yusuke

Hi,

Yusuke said:
This means SIM Card vendor right? I'm using MVNO SIM card

Yes, it might be that the network provider doesn't provide a DNS.

Yusuke said:
when I append these lines, I got an error. Any tip?

This is because the application requires to set certain things before enabling the modem. By adding those settings, you are actually starting up the modem before entering the main function. If you need to change the XSYSTEMMODE, you can do this in gps/src/main.c file, at the top.

Does the AGPS procedure always fail with iBasis, or just "once in a while"?

Kind regards,

Håkon
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Yusuke over 5 years ago in reply to Håkon Alseth

>Yes, it might be that the network provider doesn't provide a DNS.

SIM vendor says SIMs can be used with Google DNS 8.8.8.8 and 8.8.4.4

>Does the AGPS procedure always fail with iBasis, or just "once in a while"?

it always fails
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

0 Yusuke over 5 years ago in reply to Yusuke

How can I set DNS manually?

I guess I need to fix something around this in supl_support.c

int open_supl_socket(void)
{
	int err;
	int proto;
	u16_t port;
	struct addrinfo *addr;
	struct addrinfo *info;

	proto = IPPROTO_TCP;
	port = htons(SUPL_SERVER_PORT);

	struct addrinfo hints = {
		.ai_family = AF_INET,
		.ai_socktype = SOCK_STREAM,
		.ai_protocol = proto,
		/* Either a valid,
		 * NULL-terminated access point name or NULL.
		 */
		.ai_canonname = NULL,
	};

	err = getaddrinfo(SUPL_SERVER, NULL, &hints, &info);
	if (err) {
		printk("Failed to resolve hostname %s on IPv4, errno: %d)\n",
			SUPL_SERVER, errno);
		return -1;
	}

0 Håkon Alseth over 5 years ago in reply to Yusuke

Hi Yusuke,

You can set the DNS manually by adding the lines posted in this thread:

https://devzone.nordicsemi.com/f/nordic-q-a/50029/nrf9160-modem-firmware-v1-0-0-setting-custom-dns-server/235419#235419

Note that this must be called before the lte link is established.

For the iBasis scenario, could you try to increase the CONFIG_MAIN_STACK_SIZE to see if this affects the behavior?

Kind regards,

Håkon
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel