5G connection establishment
Sebastian Sjoholm
sebastian.sjoholm at gmail.com
Wed Sep 30 03:00:27 UTC 2020
On Tue, Sep 29, 2020 at 9:47 PM Federico Murciano <
Federico.Murciano at dai-labor.de> wrote:
> Hi Sebastian,
>
>
> Did you set up something manually to get the ENDC connection or did it
> connect in this mode automatically? I can only connect to LTE. Some tips to
> manage to connect to 5G?
It is automatically as long as the 5G NR is found and can be attached,
there is no configuration that needs to be done for this.
But make sure that you take the printout directly after or during the data
session, to make sure that you get the right state.
Otherwise the logging, as Carl suggested would be only way to see what is
going on.
-Sebastian
>
>
> --
> Federico Murciano
> B.Sc. Telecommunications Engineer
> federico.murciano at dai-labor.de<mailto:tobias.doersch at dai-labor.de>
> Tel. +49 (0) 30/314 -74 025
> Future in touch.
> DAI-Labor
> Technische Universität Berlin
> Fakultät IV – Elektrotechnik & Informatik Sekretariat TEL 14
> Ernst-Reuter-Platz 7
> 10587 Berlin, Germany
>
> www.dai-labor.de<http://www.dai-labor.de/>
>
> DAI-Labor - Distributed Artificial Intelligence Laboratory Chief Executive
> Director: Prof. Dr. Dr. h.c. Sahin Albayrak
>
> ________________________________
> Von: Sebastian Sjoholm <sebastian.sjoholm at gmail.com>
> Gesendet: Dienstag, 29. September 2020 20:07
> An: Federico Murciano
> Cc: Reinhard Speyerer; modemmanager-devel at lists.freedesktop.org
> Betreff: Re: 5G connection establishment
>
> Hi,
>
> I don't have MM installed, but when using minicom on the AT port,
>
> at+qeng="servingcell"
> +QENG: "servingcell","NOCONN"
> +QENG: "LTE","FDD",235,96,11A8801,270,225,1,5,5,D9,-75,-5,-52,24,-
> +QENG:"NR5G-NSA",235,96,330,-64,345,-11
> OK
>
> Regards,
> Sebastian
>
>
> On Tue, Sep 29, 2020 at 7:47 PM Federico Murciano <
> Federico.Murciano at dai-labor.de<mailto:Federico.Murciano at dai-labor.de>>
> wrote:
> Hi Reinhard,
>
> Thanks for your reply. I still get the same output:
>
> edge1 at dai-edge1:~$ sudo mmcli -m 1 '--command=at+qeng="servingcell"'
> error: command failed:
> 'GDBus.Error:org.freedesktop.ModemManager1.Error.Connection.NoCarrier: No
> carrier'
>
> edge1 at dai-edge1:~$ sudo mmcli -m 1 --command=at+qeng="servingcell"
> error: command failed:
> 'GDBus.Error:org.freedesktop.ModemManager1.Error.Connection.NoCarrier: No
> carrier'
>
>
> --
> Federico Murciano
> B.Sc. Telecommunications Engineer
> federico.murciano at dai-labor.de<mailto:federico.murciano at dai-labor.de>
> Tel. +49 (0) 30/314 -74 025
> Future in touch.
> DAI-Labor
> Technische Universität Berlin
> Fakultät IV – Elektrotechnik & Informatik Sekretariat TEL 14
> Ernst-Reuter-Platz 7
> 10587 Berlin, Germany
>
> www.dai-labor.de<http://www.dai-labor.de>
>
> DAI-Labor - Distributed Artificial Intelligence Laboratory Chief Executive
> Director: Prof. Dr. Dr. h.c. Sahin Albayrak
>
> ________________________________________
> Von: ModemManager-devel <modemmanager-devel-bounces at lists.freedesktop.org
> <mailto:modemmanager-devel-bounces at lists.freedesktop.org>> im Auftrag von
> Reinhard Speyerer <rspmn at arcor.de<mailto:rspmn at arcor.de>>
> Gesendet: Dienstag, 29. September 2020 19:00
> An: Federico Murciano
> Cc: modemmanager-devel at lists.freedesktop.org<mailto:
> modemmanager-devel at lists.freedesktop.org>; Sebastian Sjöholm
> Betreff: Re: 5G connection establishment
>
> On Tue, Sep 29, 2020 at 02:40:31PM +0000, Federico Murciano wrote:
> > Si Sebastian,
> >
> > When I run the at+qeng=???servingcell??? command with mmcli as:
> >
> > sudo mmcli -m 0 --command=at+qeng=???servingcell???
> >
> > I get the following error:
> >
> > GDBus.Error:org.freedesktop.ModemManager1.Error.Connection.NoCarrier: No
> carrier'
> >
> > Do you know why am I getting it?
> >
> > Thank you!
> >
>
> Hi Federico,
> you have to take shell quoting into account:
>
> $ echo sudo mmcli -m 0 --command=at+qeng="servingcell"
> sudo mmcli -m 0 --command=at+qeng=servingcell
> $ echo sudo mmcli -m 0 '--command=at+qeng="servingcell"'
> sudo mmcli -m 0 --command=at+qeng="servingcell"
>
> Regards,
> Reinhard
>
> > --
> > Federico Murciano
> > B.Sc. Telecommunications Engineer
> > federico.murciano at dai-labor.de<mailto:federico.murciano at dai-labor.de>
> > Tel. +49 (0) 30/314 -74 025
> > Future in touch.
> > DAI-Labor
> > Technische Universität Berlin
> > Fakultät IV ??? Elektrotechnik & Informatik Sekretariat TEL 14
> Ernst-Reuter-Platz 7
> > 10587 Berlin, Germany
> >
> > www.dai-labor.de<http://www.dai-labor.de>
> >
> > DAI-Labor - Distributed Artificial Intelligence Laboratory Chief
> Executive Director: Prof. Dr. Dr. h.c. Sahin Albayrak
> >
> > ________________________________________
> > Von: Sebastian Sjöholm <sebastian.sjoholm at gmail.com<mailto:
> sebastian.sjoholm at gmail.com>>
> > Gesendet: Dienstag, 29. September 2020 05:37
> > An: Nick B
> > Cc: Federico Murciano; modemmanager-devel at lists.freedesktop.org<mailto:
> modemmanager-devel at lists.freedesktop.org>
> > Betreff: Re: 5G connection establishment
> >
> > Hi,
> >
> > When using NSA (ENDC) the anchor will always be LTE, so for the modem
> LTE will be the primary network.
> >
> > The NR will only be used for the user plane, and activated only during
> data session, but even during data session signalling (control plane) will
> be on LTE.
> >
> > Depending on network setup, the NR session will be disconnected right
> after the data session. At some it can be instant, other might have longer
> timeouts.
> >
> > On RM500 you can check with at+qeng=???servingcell??? and on SIM8200
> at+cpsi? to see if the additional NR cell is connected after or during data
> session.
> >
> > Regards,
> > Sebastian
> >
> > @Mobile
> >
> > > On 29 Sep 2020, at 00:21, Nick B <nickberry17 at icloud.com<mailto:
> nickberry17 at icloud.com>> wrote:
> > >
> > > ???Hey,
> > >
> > > Just for the record, I am having the excat same experience in
> Australia with at Quectel RM500Q-GL and SIMCOM SIM8200EA-M2. Is there any
> debugging info that would be helpful?
> > >
> > > Best,
> > > Nick
> > > _______________________________________________
> > > ModemManager-devel mailing list
> > > ModemManager-devel at lists.freedesktop.org<mailto:
> ModemManager-devel at lists.freedesktop.org>
> > > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
> > _______________________________________________
> > ModemManager-devel mailing list
> > ModemManager-devel at lists.freedesktop.org<mailto:
> ModemManager-devel at lists.freedesktop.org>
> > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
> _______________________________________________
> ModemManager-devel mailing list
> ModemManager-devel at lists.freedesktop.org<mailto:
> ModemManager-devel at lists.freedesktop.org>
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
> _______________________________________________
> ModemManager-devel mailing list
> ModemManager-devel at lists.freedesktop.org<mailto:
> 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/20200930/7ee726fd/attachment.htm>
More information about the ModemManager-devel
mailing list