Issues Connecting to Telit LE910 through ModemManager, but not qmicli

[Ben Eck]

I'm using QMI, so don't think MBIM support is the issue. However, I updated
to MM 1.8, and everything works now!

Ben Eck

Embedded Systems Engineer

OneRain

The Rainfall Company

1531 Skyway Drive | Unit D | Longmont | Colorado 80504

Toll Free  1-800-758-RAIN (7246)

Phone +1-303-774-2033

Fax +1-303-774-2037

E-mail ben.eck at onerain.com

www.onerain.com <https://onerain.com/>

Follow us on LinkedIn <https://www.linkedin.com/company/onerain> and
Facebook <https://www.facebook.com/onerain.inc/>

An AE Monitoring member company


On Fri, Mar 1, 2019 at 9:58 AM Stelling2 Carsten <
Carsten.Stelling2 at goerlitz.com> wrote:

> Hi Ben,
>
> depending on the access technology, you have to update to MM 1.10 which
> supports the default EPS bearer for LTE.
> We had connection problems with LTE and Vodafone GDSP cards in 1.8 for
> that reason, but 1.10 fixed this problem.
> I use Telit LE910 EU-1 on an embedded system with MM 1.10.0 and libmbim
> 1.18.0 and it works like a charm.
> I use the AT#USBCFG=3 configuration for MBIM.
>
> Carsten
>
> -----Ursprüngliche Nachricht-----
> Von: ModemManager-devel [mailto:
> modemmanager-devel-bounces at lists.freedesktop.org] Im Auftrag von
> Aleksander Morgado
> Gesendet: Freitag, 1. März 2019 10:21
> An: Ben Eck
> Cc: ModemManager (development)
> Betreff: Re: Issues Connecting to Telit LE910 through ModemManager, but
> not qmicli
>
> >  I am working on creating a mobile embedded linux device using an LE910
> module. I have been successful in using it to connect to the internet using
> qmicli tools, however, I'd like to have more sophisticated network
> management using ModemManager and NetworkManager. Unfortunately, I'm having
> some trouble connecting with ModemManager. I issue the command:
> >
> > mmcli -m 0 --simple-connect="apn=VZWINTERNET"
> >
> > but am getting the error " Modem not yet registered in a 3GPP network...
> will recheck" and eventually "3GPP registration check timed out". Any idea
> what could be causing this? It seems very much like a bug in either
> ModemManager or the modem firmware, if I'm able to connect using just
> qmicli. Registering the network manually using "mmcli -m 0
> --3gpp-register-in-operator=311480" also doesn't work. "qmicli -d
> /dev/cdc-wdm0 --nas-get-serving-system" indicates that the modem is
> registered.
> >
> > In case its helpful, I'm running ModemManager 1.6.10 and here's the
> output of mmcli -m 0:
> >
>
> Are you able to get a full ModemManager debug log?
> https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/
>
>
> --
> Aleksander
> https://aleksander.es
> _______________________________________________
> ModemManager-devel mailing list
> ModemManager-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20190313/d2a33024/attachment.html>