MC7710 "forgetting" RAT

[Martin Anderseck]

Hi,

Aleksander Morgado <aleksander at aleksander.es> wrote on 04.02.2014 
12:04:16:

> Oops, yeah, you should have used --timeout=300 or so in the mmcli
> call, otherwise it will stop after 30s by default.

Okay, tried that for the simple-connect, too, but then I get a timeout 
from the network when the selrat issue is there.

> > I tried the --set-allowed-modes and --set-current-bands flags for 
mmcli
> > which you mentioned in your first reply. With the latter one I can set
> > "any". For other bands I get a QMI protocol error (25):
> > 'DeviceUnsupported'
> Long time since I last tried setting up bands, so not sure what's the
> status about that. Actually, last time I tried I bricked my UML290 and
> now it's in some weird state...

Luckily my MC7710 is still alive but furthermore it didn't do much with 
this command.

> > With --set-allowed-modes=3G or 4G it tells me
> > error: couldn't set current modes:
> > 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported: 
Cannot
> > change modes: only one combination supported'
> You need to check which are the supported Mode combinations that you
> currently have, in the "mmcli -m 0" output. In QMI devices, we have to
> play with both Capabilities and Modes to change between different
> ones.

I think I understand what the problem is: Only *one* mode is supported so 
there's no need and no possibility to change this to anything else. But 
still I wonder why I shouldn't be allowed to change its preferred mode:
  Modes    |      supported: 'allowed: 2g, 3g, 4g; preferred: none'
           |        current: 'allowed: 2g, 3g, 4g; preferred: none'

> E.g. if you have Capabilities=Lte, you will only be able to set Modes=4g
> And if you have Capabilities=Gsm+Umts+Lte, you can likely set e.g.
> Modes=2G+3G+4G and Preferred=4g

Thank you for this short but helpful explanation!

> > Are these things that might work --with-newest-qmi?
> Nope. Newest QMI commands support other newer commands, but mainly for
> NAS (e.g. signal quality retrieval and things like that). But I'd
> suggest not to use that compile option, I don't think I've tested it
> enough.

Okay, so I'll leave it for now.

> My MC7710 has revision 03.05.19.04ap; don't think I've seen that issue
> in this version.

I used to be happy with that version, too, until I had to put the modem 
into our target system (Nexcom industrial PC) where everything came up 
correctly but none of the existing ports were accessible. Therefore an 
update was necessary.

> Can you run "qmicli -d /dev/cdc-wdm0 --get-service-version-info" and
> get which are the QMI service versions supported in your firmware? I
> wouldn't mind a NAS version newer than 1.21, which is the last one I
> have.

NAS is still at 1.21, for the rest:
[/dev/cdc-wdm0] Supported versions:
        ctl (1.5)
        wds (1.12)
        dms (1.7)
        nas (1.21)
        qos (1.3)
        wms (1.4)
        pds (1.10)
        auth (1.1)
        at (1.1)
        voice (2.1)
        cat2 (2.0)
        uim (1.4)
        pbm (1.4)
        sar (1.0)
        unknown [0x1a] (1.0)
        cat (2.0)
        rms (1.0)

Summarized it looks like the modem still has some problems with its RAT. 
In one test this morning I set it to 7 (GSM, UMTS, LTE), reset it and 
afterwards it was at 6 (LTE only). In another try it worked and in still 
another try I had the invalid RAT setting again. So I suspect it to be a 
firmware issue.

Martin
 
National Instruments Dresden GmbH; Geschäftsführer (Managing Directors): Dr. Tim Hentschel, Dr. Thorsten Dräger; Sitz (Registered Office): Dresden; HRB (Commercial Register No.): 22081; Registergericht (Registration Court): Dresden

This email and any attachments are intended only for the person to whom this email is addressed and may contain confidential and/or privileged information. If you received this email in error, please do not disclose the contents to anyone, but notify the sender by return email and delete this email (and any attachments) from your system.