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

nRF Cloud Map + AGPS sample

It appears that when publishing AGPS data to  nRF Cloud, the map does not appear as it did back in July. Is there any extra end-device configuration that needs to be done to make that happen? I'm currently using a nearly stock version of the nrf_cloud_agps sample.

Thanks! Slight smile

P.S. This may be due to me using the Asset Tracker example with the first device previously. If there's  a way to enable it though without the full Asset Tracker demo, that would be awesome!

Parents
  • Hi Jared,

    the map does not appear as it did back in July.

    Do you mean that the map do no appear at all? (just a blank screen)

    If the device do not send the GPS position to nRF Cloud then the map does not appear at all. 

    e.g. A successful GPS FIX.

    I: ---------       FIX       ---------
    I: Time to fix: 20 seconds
    I: Longitude:  5.399481
    Latitude:   61.362466
    Altitude:   10.276114
    Speed:      0.118597
    Heading:    0.000000
    Date:       09-07-2020
    Time (UTC): 08:52:29
    
    I: -----------------------------------
    D: Tracking SV 29:     used,     healthy
    D: Tracking SV  5:     used,     healthy
    D: Tracking SV  9:     used,     healthy
    D: Tracking SV 21: not used,     healthy
    D: Tracking SV 26:     used,     healthy
    D: Tracking: 5 Using: 4 Unhealthy: 0
    D: Seconds since last fix 0
    D: NMEA: Position fix
    I: GPS position sent to cloud

    If you take a modem trace we can exactly see why this is.



    I suspect that this has to do with SIM + network configuration.

    The nrf cloud agps sample tries to request and get PSM, but some networks can refuse this. 
    Therefore I suggest that you try to run the sample without requesting PSM to see if this could be the case.

    You could also set this to false then you get LTE to send whenever it can.



    Best regards,
    Martin L. 

  • Hey Martin,

    It seems to be acquiring a fix. The cloud also appears to be receiving the data as well.

    I suspect that this has to do with SIM + network configuration.

    I'm running on Verizon at the moment which is a bit different than my first round of testing.

    The nrf cloud agps sample tries to request and get PSM, but some networks can refuse this. 
    Therefore I suggest that you try to run the sample without requesting PSM to see if this could be the case.

    You could also set this to false then you get LTE to send whenever it can.

    Let me try these suggestions and I'll get back to you. Hopefully it will fix it!

  • Hi Jared,

    Thank you very much for the additional information.
    The limitation looks to be on the cloud front end unfortunately.
    The reason is that it is missing a "deviceinfo" object in the shadow in the nrf cloud UI-code.
    The workaround is that you run the asset_tracker from a later stage (e.g. the master branch) first so it can send the "deviceInfo"-object to the shadow. 

    So after you have connected with the asset_tracker application and then try out your sample you should be able to see the map info. 

    I will report this internally to see if we can figure out how we can solve this on the cloud side.

    Thank you.

    best regards,

    Martin L.

Reply
  • Hi Jared,

    Thank you very much for the additional information.
    The limitation looks to be on the cloud front end unfortunately.
    The reason is that it is missing a "deviceinfo" object in the shadow in the nrf cloud UI-code.
    The workaround is that you run the asset_tracker from a later stage (e.g. the master branch) first so it can send the "deviceInfo"-object to the shadow. 

    So after you have connected with the asset_tracker application and then try out your sample you should be able to see the map info. 

    I will report this internally to see if we can figure out how we can solve this on the cloud side.

    Thank you.

    best regards,

    Martin L.

Children
Related