Re: Restrict Operator Selection

[Attie Grande]

Hi Aleksander,

Many thanks for your reply - I'll give it a go!

Attie


On Fri, 24 Feb 2023 at 17:35, Aleksander Morgado
 wrote:
>
> Hey,
>
> >
> > We have some devices in far away locations, using roaming IoT-focused SIM 
> > cards.
> > In some situations we find that modems will roam to very expensive
> > networks, when a cheaper alternative is available in that area.
> >
> > Is there an interface to set the operator MCC / MNC via `mmcli`?
> > The AT command would be `AT+COPS=1,2,${MCCMNC}`, but you can't issue
> > AT commands unless debug mode is enabled.
> >
> > From the documentation, I'm not convinced
> > `--3gpp-register-in-operator=MCCMNC` is what I'm after...
> > i.e: does it do the equivalent of above? ... is it a "one-time
> > request" or even a "try manual, fallback on auto".
> > If this is indeed what I'm after, but it needs to be issued
> > periodically, then that's fine.
> > Equally, if it's persistent, how would we cancel this? (reboot / power
> > cycle the modem?)
> >
>
> --3gpp-register-in-operator=MCCMNC should be equivalent to
> AT+COPS=1,2,${MCCMNC} (i.e. manual registration)
> --3gpp-register-in-home should be equivalent to AT+COPS=0 (i.e. auto
> registration)
>
> Now, that is not completely true I'm afraid, because when those APIs
> were developed, I recall that we introduced a change where we would
> say 'if we're in auto and we're asked to register in a specific
> MCCMNC, we won't issue a new +COPS command to explicitly restrict to
> that MCCMNC as we're already registered'. I think someone tried to fix
> that some years ago to make it equivalent to the COPS command without
> that extra logic, but I don't think it was ever changed. We should
> change that.
>
> --
> Aleksander

Re: ModemManager and Quectel RM520N-GL

[Peter Naulls]

On 3/2/23 14:21, Patrick Kosiol wrote:

Hi,

It appears my ModemManager cannot initialize the Quectel RM520N-GL modem with 
the messages
 [01775.270989] [modem0] couldn't start parent initialization: 
Couldn't open ports during modem initialization: Couldn't get primary port
 [01775.275716] [modem0] modem couldn't be initialized: Failed to load 
current capabilities: Couldn't peek client for service ‘nas'

Perhaps someone has an idea what the reason might be? That would help me very 
much.



I'm not seeing the USB serial devices for your modem, i.e, /dev/ttyUSBx.  It may 
be that you need a usb_modeswtich invocation.  ModemManager won't pick it up 
until these exist.

Re: Temperature of modem

[Tom Isaacson]

Thanks. Is there any risk in calling qmicli functions when ModemManager is
in charge of the modem?


On Sat, Feb 25, 2023 at 6:29 AM Aleksander Morgado <
aleksande...@chromium.org> wrote:

> On Tue, Feb 14, 2023 at 2:44 AM Tom Isaacson 
> wrote:
> >
> > Using "qmicli --nas-swi-get-status" I can get the temperature of the
> modem:
> >
> > [/dev/cdc-wdm0] Successfully got status:
> > Common Info:
> > Temperature: '32'
> > Modem mode: 'online'
> > System mode: 'lte'
> > IMS registration state: 'full-srv'
> > Packet service state: 'attached'
> > LTE info:
> > Band: '(null)'
> > Bandwidth: '10'
> > RX channel: '6300'
> > TX channel: '24300'
> > EMM state: 'registered'
> > EMM sub state: '0'
> > EMM connection state: 'rrc-idle'
> >
> > But I can't find this in ModemManager. Is it just not implemented or
> > is there some limitation that prevents it?
> >
>
> Just not implemented, we don't have any defined API for that.
>
> --
> Aleksander
>


-- 
Tom Isaacson