Hey Artur,

>   I am wondering if I may get some insight on the GPS refresh rate.  When I 
> change the rate from the default 30 seconds to say, 5, the utc timestamp on 
> the nmea string does not change.  When I disable the location gathering and 
> re-enable it  the timestamp updates once.  Seems like the refresh rate is not 
> being honored.  I do realize that the ModemManager from the debian 
> repositories is old.  Would I need to update it manually to fix the GPS 
> refresh rate?
>
> Does the modem need to be moving physically and not be stationary for the GPS 
> location time to update?
>
> Distro: Debian Buster 10.7 (Vanilla)
> Modem: Sierra Wireless EM7455 (latest generic firmware)
> Modem Manager Version: 1.10.0
> MetworkManager: 1.14.6
>

This issue has nothing to do with the MM version in use, I'm afraid.
The problem is that what you're configuring in MM is not really what
you're assuming it's being configured :)

The "SetGpsRefreshRate()" method configures how often the GPS
information is updated in the DBus interface, and is by default 30s.
See 
https://www.freedesktop.org/software/ModemManager/api/latest/gdbus-org.freedesktop.ModemManager1.Modem.Location.html#gdbus-method-org-freedesktop-ModemManager1-Modem-Location.SetGpsRefreshRate

E.g. the GPS NMEA traces may be reported every 1s by the modem; but MM
only published them in DBus every 30s (or whatever other time was
specified in SetGpsRefreshRate(). If you configure a value of 0 in
SetGpsRefreshRate(), the rate of publishing in DBus will be equal to
the rate used by the modem to report the NMEA traces.

Also, worth noting, this publishing rate is only applicable if
"signals_location" is enabled in the Setup() call. This is also for
security purposes; because Properties and Signals (e.g.
PropertiesUpdated) are not protected by polkit rules, while methods
are. If you're using only the GetLocation() method,
SetGpsRefreshRate() is basically useless.

What you're looking for is a way to tell the modem how often it should
send the NMEA traces, and unfortunately there is no way to request
that via MM API. There is some ongoing draft work on what that API
could look like, thinking not only on the NMEA rate but also in being
able to configure which NMEA traces are required. Please check
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/325

-- 
Aleksander
https://aleksander.es
_______________________________________________
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Reply via email to