Telit LE910C1 - GPS integration

David Khouya dakhouya at gmail.com
Fri May 8 16:02:18 UTC 2020


Hi Aleksander,

Thanks @Daniele for the feedback!

> Could you clone and build the following libqmi branch?
>
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/115
>
> Once you have it, you'll be able to configure the NMEA traces via qmicli,
e.g.:
> $ sudo qmicli -d /dev/cdc-wdm1 -p --loc-set-nmea-types="gga|gsa|gsv"
>
> And once you have done that, could you re-run ModemManager to see if
> we do receive the NMEA traces this time?

It seems to work now with your fix!
Note that I tried with the firmware 25.00.212  1  [Feb 03 2017 10:00:00]
and I didn't got any gps fixes. But it was working with the AT cmds. I did
an update of the firmware to 25.20.217  1  [Aug 23 2019 01:00:00] and now
everything works fine.

~# mmcli -m 0 --location-get
  --------------------------
  3GPP |      operator code: *
       |      operator name: *
       | location area code: *
       | tracking area code: *
       |            cell id: *
  --------------------------
  GPS  |               nmea: $GPGGA,,,,,,0,,,,,,,,*66
       |                     $GNGSA,A,1,,,,,,,,,,,,,,,*00
       |                     $GPGSA,A,1,,,,,,,,,,,,,,,*1E
       |                     $GPVTG,,T,,M,,N,,K,N*2C
       |                     $GPRMC,,V,,,,,,,,,,N*53
       |                     $GNGNS,,,,,,NNNN,,,,,,*53

example of trace received
ModemManager[997]: [/dev/cdc-wdm0] received message...
<<<<<< RAW:
<<<<<<   length = 41
<<<<<<   data   =
01:28:00:80:10:01:04:4B:06:26:00:1C:00:01:19:00:24:47:50:52:4D:43:2C:2C:56:2C:2C:2C:2C:2C:2C:2C:2C:2C:2C:4E:2A:35:33:0D:0A
ModemManager[997]: [/dev/cdc-wdm0] received generic indication
(translated)...
<<<<<< QMUX:
<<<<<<   length  = 40
<<<<<<   flags   = 0x80
<<<<<<   service = "loc"
<<<<<<   client  = 1
<<<<<< QMI:
<<<<<<   flags       = "indication"
<<<<<<   transaction = 1611
<<<<<<   tlv_length  = 28
<<<<<<   message     = "NMEA" (0x0026)
<<<<<< TLV:
<<<<<<   type       = "NMEA String" (0x01)
<<<<<<   length     = 25
<<<<<<   value      =
24:47:50:52:4D:43:2C:2C:56:2C:2C:2C:2C:2C:2C:2C:2C:2C:2C:4E:2A:35:33:0D:0A
<<<<<<   translated = $GPRMC,,V,,,,,,,,,,N*53

ModemManager[997]: <debug> [1588951506.354989] [NMEA]
$GPRMC,,V,,,,,,,,,,N*53

Thanks for your help!


On Thu, May 7, 2020 at 1:00 PM Aleksander Morgado <aleksander at aleksander.es>
wrote:

> Hey David,
>
> > > > >
> > > > > With all enable it only shows the 3GPP info with mmcli -m 0
> --loction-get
> > > >
> > > > Daniele, any idea why we're not receiving NMEA traces via QMI
> > > > indications in this case? Do you see something wrong in the sequence
> > > > to enable the GNSS location gathering?
> > > >
> > >
> > > The sequence is missing request QMI_LOC_SET_NMEA_TYPES that is not in
> > > libqmi. The request is needed to indicate which NMEA sentences should
> > > be enabled.
> > >
> >
> > Ah! good to know, thanks. I'll add that. Do you know since when is
> > this a requirement? I don't think any other modem I tested with
> > required this message explicitly.
> >
>
> Could you clone and build the following libqmi branch?
> https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/115
>
> Once you have it, you'll be able to configure the NMEA traces via qmicli,
> e.g.:
> $ sudo qmicli -d /dev/cdc-wdm1 -p --loc-set-nmea-types="gga|gsa|gsv"
>
> And once you have done that, could you re-run ModemManager to see if
> we do receive the NMEA traces this time?
>
> --
> Aleksander
> https://aleksander.es
>


-- 
*David Khouya*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20200508/8dcc4fab/attachment.htm>


More information about the ModemManager-devel mailing list