GPS with Sierra Wireless, Incorporated Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A (cdc-wdm0)

[Aleksander Morgado]

Hey,

> I'm trying to get the GPS data from my modem, but I receive "strange"
> character as output:
>
> mmcli -m 0  --location-status
>    --------------------------------
>    Location |         capabilities: 3gpp-lac-ci, gps-raw, gps-nmea,
> agps-msa, agps-msb
>             |              enabled: 3gpp-lac-ci, gps-nmea
>             |              signals: no
>    --------------------------------
>    GPS      |         refresh rate: 3600 seconds
>             | supported assistance: xtra
>             |   assistance servers:
> http://xtrapath2.izatcloud.net/xtra3grc.bin
>             | http://xtrapath3.izatcloud.net/xtra3grc.bin
>             | http://xtrapath1.izatcloud.net/xtra3grc.bin
>
>
> mmcli -m 0  --location-get
>    -----------
>    GPS | nmea: ¤ÅAΦUiΔΠ,,1aBéØΠ,X0aBEΓΩ5f4P
>        |       ¤ÅA:t(ΔΠ,X0aBéøΠ,X0aBéØΠ*lXi
>        |       ¤ÅA2Ej_Π,(1aRÇØΠNX0YDEΓΩ2ù5P
> Λ     |       ¤ÅA:4*ΔΠAXDaBéØΠ,X0aBéØΠ,X0a"%L"
>
>
> mmcli -m 0  --location-get
>    -----------
>    GPS | nmea: ¤ÅA2Ej_Π,(1aRÇØΠNX0YDEΓΩ2ù5P
> Ξ,TÖ1SAøΞ,¿ÖaΦ&ÅA:4JΩΠ4XHaΦføΠ1h0_ΓùØΘ6h0aΦùÅΠ1j0Ç¥'øΠ,dDaΦf
>        |       ¤ÅAΦUiΔΠ,,1aBéØΠ,X0aBEΓΩ5f4P
>        |
> ¤ÅA:4JΩΠ3XLaΦFøΠ2l0£cùØΘ9b0a"&ÅΠ7n0_cFøΠ,fDa2ùÅΠ3¿XaBeøΘ,bPa"ùMΣ,TÖ£SA
> Λ     |       ¤ÅA:4*ΔΠAXDaBéØΠ,X0aBéØΠ,X0a"%L"
>        |       ¤ÅA:t(ΔΠ,X0aBéøΠ,X0aBéØΠ*lXi
> Ξ,TÖΘSALΞ,lXa$FÅA:4JΩΠ3XHaΦFøΠ1p0ÇSùKΣ8b0a"&øΠ1n0Ç¥'
> Ξ,TÖ£SAøΞ,dDa"FÅA:4JΩΠ3XDaΦFøΠ0j0£#ùØΣ9h0a$F
> Θ,TÖ!TALÆ,nÖa"FÅA:4JΩΠ4XLaΦføΠ2h0£sùKΣ5h0a"&
> Π1pDaBELΣ,bÖaΦùNΞ,TÖ1TAXHaΦføΠ1d0ΘsùØΣ8n0aΦù
>
> Under the item "Info" the modem-manager-gui in the network I can see the
> operator (Iliad), the operator code (22250) and so on, but under the
> Location item both the 3GPP (0/0/0/0/0) and the GPS location
> (0,000/0,000/0,000) are empty.
>
> SO Linux Ubuntu 20.04, mmcli 1.12.8
>

Please update to libqmi to 1.24.12, I believe this issue happens due
to the CRLF on the NMEA traces being filtered out, and so libqmi
attempts to parse the string with a different encoding.

-- 
Aleksander
https://aleksander.es