Thingy:91

RE: Thingy:91

stevenminnick — Thu, 15 Aug 2019 15:49:04 GMT

No I didn't, thanks for the link, I will try that.

RE: Thingy:91

Hoang — Thu, 15 Aug 2019 05:37:13 GMT

Have you tried: https://devzone.nordicsemi.com/f/nordic-q-a/49650/asset_tracker-does-not-work-with-firmware-v1-0-0/200311#200311

RE: Thingy:91

stevenminnick — Wed, 14 Aug 2019 20:20:18 GMT

I'm not sure if this is the ideal place to ask about cloud_connect failed

But I'm getting the same thing.

RE: Thingy:91

mschweig — Wed, 14 Aug 2019 13:58:15 GMT

Hi, I have the same problem - went trough the same tasks but I am getting errors when compiling.

Any hints?

Kind regards,

Manuel

RE: Thingy:91

Hoang — Fri, 09 Aug 2019 05:34:52 GMT

Hi MJD093: removed it when i used thingy:91, the MAGPIO settings just define for PCA10090, I dont know how about other boards! Bjørn Kvaale

RE: Thingy:91

MJD093 — Thu, 08 Aug 2019 15:17:00 GMT

Bjorn Kadding or removing? From the code snippet that was linked in the verified answer, wouldn’t that not use the MAGPIO settings if the board was anything other than PCA10090?

RE: Thingy:91

Bjørn Kvaale — Thu, 08 Aug 2019 12:24:59 GMT

It seems this issue has been resolved by removing this AT command:

AT\%XMAGPIO=1,0,0,1,1,1574,1577

RE: Thingy:91

Hoang — Thu, 08 Aug 2019 12:11:53 GMT

Hi Bjørn Kvaale, MJD093

I found the reason. It is my fault:

#ifdef CONFIG_BOARD_NRF9160_PCA10090NS
#define AT_MAGPIO      "AT\%XMAGPIO=1,0,0,1,1,1574,1577"
#endif

with THINGY:91, must remove: AT\%XMAGPIO=1,0,0,1,1,1574,1577

Then, GPS will work.

Thanks so much,

Mvh

Hoang Nguyen

RE: Thingy:91

Hoang — Wed, 07 Aug 2019 08:45:25 GMT

Thanks so much for your info, MJD093, Regards

RE: Thingy:91

MJD093 — Tue, 06 Aug 2019 13:26:35 GMT

If you view the NMEA sentences, it will show you all the information GPS uses.

https://www.gpsinformation.org/dale/nmea.htm

I believe the value in question is under sentence GSA which handles Satellite status. It can return a value of 1, 2 or 3 with regards to fix type. So you can detect the satellites but it can still return a value of 1 for no fix. GSA specifies how many satellites are used in the fix solution which will be reflected in the printk information.

RE: Thingy:91

Hoang — Tue, 06 Aug 2019 13:18:17 GMT

Thanks so much MJD093

RE: Thingy:91

MJD093 — Tue, 06 Aug 2019 13:16:27 GMT

Ignore the first result, its a ghost response and isn't accurate, the results after the first scan are accurate to the state of the GPS modem.

Not all satellites will be used, detecting satellites is not the same using them to get a fix.

RE: Thingy:91

Hoang — Tue, 06 Aug 2019 13:13:38 GMT

and, sometimes, I got results look like that:

SPM: NS image at 0xc000
SPM: NS MSP at 0x200247a0
SPM: NS reset vector at 0x14431
SPM: prepare to jump to Non-Secure image.
***** Booting Zephyr OS build v1.14.99-ncs2-495-ga8933a2ead01 *****
Staring GPS application
Socket created
Getting GPS data...
[1B][1;1H[1B][2JTracking: 3 Using: 0 Unhealthy: 1
Seconds since last fix 0

Scanning [|] [1B][1;1H[1B][2JTracking: 3 Using: 0 Unhealthy: 1
Seconds since last fix 0

Scanning [/] [1B][1;1H[1B][2JTracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 1

Scanning [-] [1B][1;1H[1B][2JTracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 1

Scanning [\] [1B][1;1H[1B][2JTracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 2

Scanning [|] [1B][1;1H[1B][2JTracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 2

Scanning [/] [1B][1;1H[1B][2JTracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 3

or:

Scanning [/] [1B][1;1H[1B][2JTracking: 4 Using: 0 Unhealthy: 0
Seconds since last fix 476

Scanning [-] [1B][1;1H[1B][2JTracking: 4 Using: 0 Unhealthy: 0
Seconds since last fix 477

Scanning [\] [1B][1;1H[1B][2JTracking: 4 Using: 0 Unhealthy: 0
Seconds since last fix 477

Scanning [|] [1B][1;1H[1B][2JTracking: 4 Using: 0 Unhealthy: 0
Seconds since last fix 478

Scanning [/] [1B][1;1H[1B][2JTracking: 4 Using: 0 Unhealthy: 0
Seconds since last fix 478

Scanning [-] [1B][1;1H[1B][2JTracking: 4 Using: 0 Unhealthy: 0
Seconds since last fix 479

Scanning [\] [1B][1;1H[1B][2JTracking: 4 Using: 0 Unhealthy: 0
Seconds since last fix 479

Scanning [|] [1B][1;1H[1B][2JTracking: 4 Using: 0 Unhealthy: 0
Seconds since last fix 480

Scanning [/] [1B][1;1H[1B][2JTracking: 4 Using: 0 Unhealthy: 0
Seconds since last fix 480

Scanning [-] [1B][1;1H[1B][2JTracking: 4 Using: 0 Unhealthy: 0
Seconds since last fix 481

Tracking: 4 but Using: 0 !!??

I cant understand it

RE: Thingy:91

MJD093 — Mon, 05 Aug 2019 14:15:48 GMT

That's very odd 😕

RE: Thingy:91

Hoang — Mon, 05 Aug 2019 12:11:16 GMT

I got nothing now, even with and without an external antenna, maybe the weather is so bad now :(

Scanning [|] [1B][1;1H[1B][2JTracking: 0 Using: 0 Unhealthy: 0
Seconds since last fix 508

RE: Thingy:91

Hoang — Mon, 05 Aug 2019 11:35:35 GMT

Hi MJD093

Ja, THINGY:91 has the U:FL connect, I will try to test with an external antenna

RE: Thingy:91

MJD093 — Mon, 05 Aug 2019 10:08:50 GMT

Ok, i think the issue isn't the SiP but GPS reception strength. That is an incredibliy long time to get a fix with 4-5 satellites in view.

The Thingy is a smaller PCB size so stands to reason that with less ground area, the receptivity of GPS antenna is also going to suffer some what. It will be less effective than the pca10090 which has a larger ground plane and more likely to fit correctly to the reference design of the Molex antenna.

The GPS receiver clearly works on the Thingy:91 as it does see satellites but it can't make that all important fix. This is either an issue with the GPS sensistivity or the conditions on the ground that are hampering GPS fixes.

Have you looked at the antenna circuit to see if there is a U.FL connector on it? If there is, try an external antenna and see if the results change.

RE: Thingy:91

Hoang — Mon, 05 Aug 2019 09:57:03 GMT

Hi Bjørn Kvaale

I tried to test with: ncs_v1.0.0_joakim\nrf\samples\nrf9160\gps for both nRF9160 DK and THINGY:91.

(put 2 of them in the same place, outside)

nRF9160 DK got fix

but THINGY:91 NO ( it got fix only 1time/10times testing)

and here are the logfiles:

for nRF9160 DK:

devzone.nordicsemi.com/.../nrf9160DK.txt

for thingy:91

devzone.nordicsemi.com/.../thingy91.txt

I hope I can have time to help me

Thanks

Regards

Mhv

Hoang Nguyen

RE: Thingy:91

leey — Thu, 01 Aug 2019 23:17:23 GMT

figure out on how to build it using command line.

same issues; several compilation issues using board type of nrf9160_pca20035

RE: Thingy:91

leey — Thu, 01 Aug 2019 21:31:58 GMT

Hello Everyone,

Got 1x Thingy91.

I have been using nRF9160 DK versio 0.7.0; all work; no issue; able to build etc...; I am using Nordic Segger version 4.18.

Try similar thing with Thingy91; I have copied the boards/arm/dir to the appropriate location(ie. the nrf9160_pca20035 dir).

So far, having an issue in creating Nordic Segger project; and if one is successful(eg. the simple gps app), it has compilation error etc...

So not sure whether this is Nordic Segger issue or other issue ?

Anyone has a short readme on how to build without using Nordic Segger 4.18 IDE ?

Thanks.

Lee

RE: Thingy:91

Bjørn Kvaale — Thu, 01 Aug 2019 12:57:18 GMT

I believe the antenna circuit is correctly matched. Not sure I can provide any info on the Thingy:91 GPS circuit, as it is not publicly available yet.

RE: Thingy:91

Bjørn Kvaale — Thu, 01 Aug 2019 12:54:13 GMT

cloud error 111 relates to missing certificates. If you have already connected your 91 DK to the nRF Cloud, you can use the procedure provided here to recover the missing certificates.

RE: Thingy:91

Bjørn Kvaale — Thu, 01 Aug 2019 12:48:19 GMT

Nope, no external GPS antenna is needed. I am taking a look at this case & will get back to you soon. Good to hear at least that you did not get the nrf cloud 111 error, which is related to deleted certificates.

RE: Thingy:91

Hoang — Thu, 01 Aug 2019 12:46:36 GMT

Bjørn Kvaale,

I got the problem when I run asset_tracker on nRF9160 DK: ( It worked yesterday)

SPM: NS image at 0x18200
SPM: NS MSP at 0x2002b4f8
SPM: NS reset vector at 0x20d09
SPM: prepare to jump to Non-Secure image.
***** Booting Zephyr OS build v1.14.99-ncs2-rc4-495-ga8933a2ead01 *****
[00:00:00.245,544] [1B][0m<dbg> nrf9160_gps.init: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577[1B][0m
Asset tracker started
[00:00:00.256,652] [1B][0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100264319[1B][0m
[00:00:00.265,930] [1B][0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100264319/shadow[1B][0m
[00:00:00.277,618] [1B][0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: $aws/things/nrf-352656100264319/shadow/get/accepted[1B][0m
[00:00:00.290,222] [1B][0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100264319/shadow/get/rejected[1B][0m
[00:00:00.302,795] [1B][0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100264319/shadow/update/delta[1B][0m
[00:00:00.315,734] [1B][0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100264319/shadow/update[1B][0m
[00:00:00.327,606] [1B][0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100264319/shadow/get[1B][0m
Connecting to LTE network. This may take several minutes.
[00:00:02.424,591] [1B][0m<dbg> lte_lc.at_handler: recv: +CEREG: 2,"765D","0110C303",7
[1B][0m
[00:00:03.684,783] [1B][0m<dbg> lte_lc.at_handler: recv: +CEREG: 5,"765D","0110C303",7
[1B][0m
Connected to LTE network
[00:00:03.968,078] [1B][0m<dbg> nrf_cloud_transport.nct_connect: IPv4 Address 0x82492d34[1B][0m
cloud_connect failed: -111
LTE link disconnect
Shutdown modem

RE: Thingy:91

MJD093 — Thu, 01 Aug 2019 12:14:11 GMT

Ok so you have or haven't gotten the Thingy:91 to acquire a lock? Little confused here 😅