Also the output for serving cell AT Command says just LTE (with wget data
transferring exactly same output):
edge2@dai-edge2:~$ sudo mmcli -m 0 --command='AT+QENG="servingcell"'
response: '+QENG:
"servingcell","NOCONN","LTE","FDD",262,01,1925706,243,3050,7,5,5,5D5,-107,-16,-71,7,255,-32768,14'
--
Federico Murciano
B.Sc. Telecommunications Engineer
federico.murci...@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
DAI-Labor - Distributed Artificial Intelligence Laboratory Chief Executive
Director: Prof. Dr. Dr. h.c. Sahin Albayrak
________________________________________
Von: ModemManager-devel <modemmanager-devel-boun...@lists.freedesktop.org> im
Auftrag von Federico Murciano <federico.murci...@dai-labor.de>
Gesendet: Dienstag, 6. Oktober 2020 11:33
An: Carl Yin(殷张成)
Cc: modemmanager-devel@lists.freedesktop.org
Betreff: AW: 5G connection establishment
Hi Carl,
Sorry I did not see this message before. I tried what you said, downloading a
file with wget and check nas-get-system-info but this is the response, which is
exactly the same than before trying to download anything:
edge2@dai-edge2:~$ sudo qmicli -d /dev/cdc-wdm0 -p --nas-get-system-info
[/dev/cdc-wdm0] Successfully got system info:
WCDMA service:
Status: 'none'
True Status: 'none'
Preferred data path: 'no'
LTE service:
Status: 'available'
True Status: 'available'
Preferred data path: 'no'
Domain: 'cs-ps'
Service capability: 'cs-ps'
Roaming status: 'off'
Forbidden: 'no'
Cell ID: '26367750'
MCC: '262'
MNC: '01'
Tracking Area Code: '1493'
Voice support: 'yes'
IMS voice support: 'yes'
eMBMS coverage info support: 'no'
eMBMS coverage info trace ID: '65535'
Cell access: 'all-calls'
Registration restriction: 'unrestricted'
Registration domain: 'not-applicable'
SIM reject info: 'available'
I also tried to scan for the available networks and this is the output,
actually 5G should appear there right? Any solution for this issue? ANy help is
more than welcome:
edge2@dai-edge2:~$ sudo mmcli -m 0 --3gpp-scan
---------------------
3GPP scan | networks: 26202 - Vodafone (lte, available)
| 26202 - Vodafone (umts, available)
| 26203 - o2 - de (umts, forbidden)
| 26203 - o2 - de (lte, forbidden)
| 26201 - TDG (umts, available)
| 26201 - Telekom.de (lte, current)
If this helps, this is the model and status of the modem, which should be able
to connect to 5G. I tried using the quectel connect manager and it mainly
connected to LTE but some short periods it was connected to 5G (Photo attached):
edge2@dai-edge2:~$ sudo mmcli -m 0
-----------------------------------
General | dbus path: /org/freedesktop/ModemManager1/Modem/0
| device id: f5f2f59fdd6ff07da224bef28cbf8fae32f85653
-----------------------------------
Hardware | manufacturer: Quectel
| model: RG500QEA_VH
| firmware revision: RG500QEAAAR10A03M4G
| carrier config: Commercial-DT-VOLTE
| carrier config revision: 0A011F1F
| h/w revision: 20000
| supported: gsm-umts, lte, 5gnr
| current: gsm-umts, lte, 5gnr
| equipment id: 866897040136758
-----------------------------------
System | device:
/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1
| drivers: option1, qmi_wwan
| plugin: quectel
| primary port: cdc-wdm0
| ports: cdc-wdm0 (qmi), ttyUSB0 (qcdm), ttyUSB2
(at), wwan0 (net),
| ttyUSB1 (gps), ttyUSB3 (at)
-----------------------------------
Numbers | own: 4915170017468
-----------------------------------
Status | lock: sim-pin2
| unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3),
sim-puk2 (10)
| state: connected
| power state: on
| access tech: lte
| signal quality: 65% (recent)
-----------------------------------
Modes | supported: allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 3g, 4g; preferred: 4g
| allowed: 3g, 4g; preferred: 3g
| allowed: 5g; preferred: none
| allowed: 3g, 5g; preferred: 5g
| allowed: 3g, 5g; preferred: 3g
| allowed: 4g, 5g; preferred: 5g
| allowed: 4g, 5g; preferred: 4g
| allowed: 3g, 4g, 5g; preferred: 5g
| allowed: 3g, 4g, 5g; preferred: 4g
| allowed: 3g, 4g, 5g; preferred: 3g
| current: allowed: 4g, 5g; preferred: 5g
-----------------------------------
Bands | supported: utran-1, utran-3, utran-6, utran-5,
utran-8, utran-9,
| eutran-1, eutran-2, eutran-3, eutran-4,
eutran-5, eutran-7, eutran-8,
| eutran-12, eutran-13, eutran-14,
eutran-17, eutran-18, eutran-19,
| eutran-20, eutran-25, eutran-26,
eutran-28, eutran-29, eutran-30,
| eutran-32, eutran-34, eutran-38,
eutran-39, eutran-40, eutran-41,
| eutran-42, eutran-43, eutran-48,
eutran-66, eutran-71, utran-19
| current: utran-1, utran-3, utran-6, utran-5,
utran-8, eutran-1,
| eutran-3, eutran-5, eutran-7, eutran-8,
eutran-18, eutran-19,
| eutran-20, eutran-26, eutran-28,
eutran-32, eutran-34, eutran-38,
| eutran-39, eutran-40, eutran-41,
eutran-42, eutran-43, utran-19
-----------------------------------
IP | supported: ipv4, ipv6, ipv4v6
-----------------------------------
3GPP | imei: 866897040136758
| operator id: 26201
| operator name: Telekom.de
| registration: home
-----------------------------------
3GPP EPS | ue mode of operation: csps-1
-----------------------------------
SIM | dbus path: /org/freedesktop/ModemManager1/SIM/0
-----------------------------------
Bearer | dbus path: /org/freedesktop/ModemManager1/Bearer/0
--
Federico Murciano
B.Sc. Telecommunications Engineer
federico.murci...@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
DAI-Labor - Distributed Artificial Intelligence Laboratory Chief Executive
Director: Prof. Dr. Dr. h.c. Sahin Albayrak
________________________________________
Von: ModemManager-devel <modemmanager-devel-boun...@lists.freedesktop.org> im
Auftrag von Carl Yin(殷张成) <carl....@quectel.com>
Gesendet: Mittwoch, 30. September 2020 03:24
An: Federico Murciano; Sebastian Sjoholm
Cc: modemmanager-devel@lists.freedesktop.org
Betreff: 答复: 5G connection establishment
Hi
We make patch to libqmi to get 5G service info,
https://gitlab.freedesktop.org/carlyin/libqmi/-/tree/nr5g
If you start data trasfer(like wget ), the 5G modem will auto register
to 5G NSA, and you will get response as next:
If NOT, you need to catch QXDM LOG,and send to the 5G modem vendor.
# qmicli -d /dev/cdc-wdm0 -p --nas-get-system-info
[/dev/cdc-wdm0] Successfully got system info:
LTE service:
5G NSA Available: 'yes'
DCNR Restriction: 'no'
5G SA service:
Status: 'none'
True Status: 'none'
Preferred data path: 'no'
> -----邮件原件-----
> 发件人: ModemManager-devel
> [mailto:modemmanager-devel-boun...@lists.freedesktop.org] 代表 Federico
> Murciano
> 发送时间: Wednesday, September 30, 2020 3:47 AM
> 收件人: Sebastian Sjoholm <sebastian.sjoh...@gmail.com>
> 抄送: modemmanager-devel@lists.freedesktop.org
> 主题: AW: 5G connection establishment
>
> 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?
>
>
> --
> Federico Murciano
> B.Sc. Telecommunications Engineer
> federico.murci...@dai-labor.de<mailto:tobias.doer...@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.sjoh...@gmail.com>
> Gesendet: Dienstag, 29. September 2020 20:07
> An: Federico Murciano
> Cc: Reinhard Speyerer; modemmanager-devel@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.murci...@dai-labor.de<mailto:federico.murci...@dai-labor.de>>
> wrote:
> Hi Reinhard,
>
> Thanks for your reply. I still get the same output:
>
> edge1@dai-edge1:~$ sudo mmcli -m 1 '--command=at+qeng="servingcell"'
> error: command failed:
> 'GDBus.Error:org.freedesktop.ModemManager1.Error.Connection.NoCarrier: No
> carrier'
>
> edge1@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.murci...@dai-labor.de<mailto:federico.murci...@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-boun...@lists.freedesktop.org<mailto:modemmanage
> r-devel-boun...@lists.freedesktop.org>> im Auftrag von Reinhard Speyerer
> <rs...@arcor.de<mailto:rs...@arcor.de>>
> Gesendet: Dienstag, 29. September 2020 19:00
> An: Federico Murciano
> Cc:
> modemmanager-devel@lists.freedesktop.org<mailto:modemmanager-devel@li
> sts.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.murci...@dai-labor.de<mailto:federico.murci...@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.sjoh...@gmail.com<mailto:sebastian.sjoh...@gmail.com>>
> > Gesendet: Dienstag, 29. September 2020 05:37
> > An: Nick B
> > Cc: Federico Murciano;
> >
> modemmanager-devel@lists.freedesktop.org<mailto:modemmanager-devel@li
> s
> > ts.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
> <nickberr...@icloud.com<mailto:nickberr...@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@lists.freedesktop.org<mailto:ModemManager-devel@l
> > > ists.freedesktop.org>
> > > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
> > _______________________________________________
> > ModemManager-devel mailing list
> >
> ModemManager-devel@lists.freedesktop.org<mailto:ModemManager-devel@li
> s
> > ts.freedesktop.org>
> > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
> _______________________________________________
> ModemManager-devel mailing list
> ModemManager-devel@lists.freedesktop.org<mailto:ModemManager-devel@li
> sts.freedesktop.org>
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
> _______________________________________________
> ModemManager-devel mailing list
> ModemManager-devel@lists.freedesktop.org<mailto:ModemManager-devel@li
> sts.freedesktop.org>
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
> _______________________________________________
> ModemManager-devel mailing list
> ModemManager-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
_______________________________________________
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
_______________________________________________
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
