-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
applications: asset_tracker_v2: Add support for AGPS when configuring for AWS IoT #5097
applications: asset_tracker_v2: Add support for AGPS when configuring for AWS IoT #5097
Conversation
applications/asset_tracker_v2/src/cloud/cloud_codec/json_common.h
Outdated
Show resolved
Hide resolved
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
5b15c84
to
6bc3c2c
Compare
I'm taking over this PR while @simensrostad is on vacation. Note that the PR is based on PR #4609. Updated with a commit that does some Kconfig refactoring for nRF Cloud library. @jayteemo and @plskeggs, please have a look if those changes look okay with you. I'll soon add the same commit and one more doing similar for P-GPS in #5099. |
applications/asset_tracker_v2/src/cloud/cloud_codec/aws_iot_codec.c
Outdated
Show resolved
Hide resolved
6bc3c2c
to
2d16498
Compare
Rebased on top of #4609 and addressed review comments |
2d16498
to
60b70a2
Compare
44e711a
to
e8636f0
Compare
e8636f0
to
4c69dd7
Compare
applications/asset_tracker_v2/src/cloud/cloud_codec/json_common.h
Outdated
Show resolved
Hide resolved
applications/asset_tracker_v2/tests/json_common/src/json_validate.h
Outdated
Show resolved
Hide resolved
applications/asset_tracker_v2/src/cloud/cloud_codec/json_common.c
Outdated
Show resolved
Hide resolved
The nRF Cloud Kconfig file had become quite large, so it's now split into separate files for each of the "sub-API"s that are offered. At the same time, the nRF Cloud A-GPS parsing APIs are made independant of the nRF Cloud MQTT transport being enabled. Signed-off-by: Jan Tore Guggedal <jantore.guggedal@nordicsemi.no>
4c69dd7
to
e790a47
Compare
Add support requesting and receiving AGPS data when configuring for AWS IoT. Closes CIA-374 Signed-off-by: Simen S. Røstad <simen.rostad@nordicsemi.no>
faedffd
to
c577312
Compare
@coderbyheart Review comments addressed, thanks. |
How do I get this to work in the Asset Tracker V2 application? I'm running the nRF connect SDK v.2.1.1 and I've set the following flags together with the overlay-aws.conf file: Is there some other flag I need to set in my configuration file? |
Hi @sebgus. Please create a support ticket on https://devzone.nordicsemi.com/ for this matter. Our support team will assist you as soon as possible. |
Hi @simensrostad ! Thanks for the quick reply. Does my AWS endpoint need some special configuration? |
A-GPS is enabled by default for all configurations. You don't need to set
To enable A-GPS with AWS you need to pipe A-GPS requests/responses from AWS to nRF Cloud. The nRF Asset Tracker project has documentation for this, https://nordicsemiconductor.github.io/asset-tracker-cloud-docs/v2.1.x/docs/cloud-protocol/DeviceDataAndConfiguration.html?highlight=agps#a-gps-and-p-gps-data |
Add support requesting and receiving AGPS data when configuring for
AWS IoT.
Closes CIA-374