Re: MC7455 not listed as usb device any more after reboot

On Fri, 2017-03-17 at 11:57 +, Thomas Lang wrote: > Hi all, > perhaps you have seen this bug before. I’m using the MC7455 with a > linux system after normal power cycle (unplugged power) the mc 7455 > can be found  with lsusb: > > > > go@ubuntu:~$ lsusb > > Bus 003 Device 003: ID 1199:9071

MC7455 not listed as usb device any more after reboot

Hi all, perhaps you have seen this bug before. I’m using the MC7455 with a linux system after normal power cycle (unplugged power) the mc 7455 can be found with lsusb: go@ubuntu:~$ lsusb Bus 003 Device 003: ID 1199:9071 Sierra Wireless, Inc. Bus 003 Device 002: ID 0438:7900 Advanced Micro

Re: [PATCH] iface-modem-3gpp: use mm_3gpp_parse_operator_id() instead of custom code

On Fri, Mar 17, 2017 at 10:11 PM, Dan Williams wrote: > --- > src/mm-iface-modem-3gpp.c | 43 --- > 1 file changed, 8 insertions(+), 35 deletions(-) > LGTM > diff --git a/src/mm-iface-modem-3gpp.c b/src/mm-iface-modem-3gpp.c > index

[PATCH] iface-modem-3gpp: use mm_3gpp_parse_operator_id() instead of custom code

--- src/mm-iface-modem-3gpp.c | 43 --- 1 file changed, 8 insertions(+), 35 deletions(-) diff --git a/src/mm-iface-modem-3gpp.c b/src/mm-iface-modem-3gpp.c index d38c4ca..8b93550 100644 --- a/src/mm-iface-modem-3gpp.c +++ b/src/mm-iface-modem-3gpp.c @@

MC7455 not listed as usb device anymore after reboot

Hi all, perhaps you have seen this bug before. I’m using the MC7455 with a linux system after normal power cycle (unplugged power) the mc 7455 can be found with lsusb: go@ubuntu:~$ lsusb Bus 003 Device 003: ID 1199:9071 Sierra Wireless, Inc. Bus 003 Device 002: ID 0438:7900 Advanced Micro

MC7455 not listed as usb device anymore after reboot

Hi all, perhaps you have seen this bug before. I’m using the MC7455 with a linux system after normal power cycle (unplugged power) the mc 7455 can be found with lsusb: go@ubuntu:~$ lsusb Bus 003 Device 003: ID 1199:9071 Sierra Wireless, Inc. Bus 003 Device 002: ID 0438:7900 Advanced Micro

Re: Cinterion 'simstatus'

On Fri, Mar 17, 2017 at 1:19 PM, Colin Helliwell wrote: > I fear this may not be all that straight-forward to tackle - dunno if it's > just them, but Cinterion seem to have great mastery in implementing different > AT Command sets! > AT^SSET is available on the

Re: SIM hot swap with SIM locked

On Fri, Mar 17, 2017 at 4:55 PM, Carlo Lobrano wrote: > mar 17 16:45:15 D2040 ModemManager[3946]: (ttyACM0): --> > 'AT+GCAP' > mar 17 16:45:15 D2040 ModemManager[3946]: (ttyACM0): <-- '' > mar 17 16:45:15 D2040 ModemManager[3946]: (ttyACM0): <-- '+GCAP: >

Re: SIM hot swap with SIM locked

On Fri, Mar 17, 2017 at 2:16 PM, Carlo Lobrano wrote: > Short update that might highlight better the problem. When the Modem is > re-probed after SIM is removed, the "parse_caps_gcap" receives NULL strings, > even if we can see the reply on the logs > > mar 17 14:08:40 D2040

Re: Unexpected COPS format

On Fri, 2017-03-17 at 16:13 +, Colin Helliwell wrote: > > On 17 March 2017 at 15:02 Colin Helliwell > ms.com> wrote: > > > > > On 17 March 2017 at 14:16 colin.helliw...@ln-systems.com wrote: > > > > > > I’m reviewing the info fetched on my modems, and one of them

Re: Unexpected COPS format

On Fri, 17 Mar 2017 14:16:50 - wrote: > I'm reviewing the info fetched on my modems, and one of them is giving an > unusual format for "AT+COPS=3,2;+COPS?" : > >+COPS: 0,2,"00320033003400310035",0 > > > > This seems to be some sort of 'wide char' hex

Re: Unexpected COPS format

> On 17 March 2017 at 15:02 Colin Helliwell > wrote: > > > On 17 March 2017 at 14:16 colin.helliw...@ln-systems.com wrote: > > > > I’m reviewing the info fetched on my modems, and one of them is giving an > > unusual format for “AT+COPS=3,2;+COPS?” : > > > >

Re: SIM hot swap with SIM locked

Sorry, I made a mistake copying the log in the previous email mar 17 16:45:15 D2040 ModemManager[3946]: (ttyACM0): --> 'AT+GCAP' mar 17 16:45:15 D2040 ModemManager[3946]: (ttyACM0): <-- '' mar 17 16:45:15 D2040 ModemManager[3946]: (ttyACM0): <-- '+GCAP: +CGSM,+DS,+FCLASS,+MS,+ESOK' mar 17

Re: Unexpected COPS format

> On 17 March 2017 at 14:16 colin.helliw...@ln-systems.com wrote: > > I’m reviewing the info fetched on my modems, and one of them is giving an > unusual format for “AT+COPS=3,2;+COPS?” : > >    +COPS: 0,2,"00320033003400310035",0 > > This seems to be some sort of ‘wide char’ hex

Unexpected COPS format

I'm reviewing the info fetched on my modems, and one of them is giving an unusual format for "AT+COPS=3,2;+COPS?" : +COPS: 0,2,"00320033003400310035",0 This seems to be some sort of 'wide char' hex representation of "23415" [which is what I'd expect]. The modem's AT spec doesn't say

Re: Own number

On Fri, Mar 17, 2017 at 2:13 PM, wrote: > Is there anything in MM which attempts to fetch the modem’s own phone > number? I see a line for it in ‘mmcli –m 0’, but unsure where it > could/would/might obtain this (seems to be somewhere in the ‘libmm’ stuff?). The

Re: SIM hot swap with SIM locked

Short update that might highlight better the problem. When the Modem is re-probed after SIM is removed, the "parse_caps_gcap" receives NULL strings, even if we can see the reply on the logs mar 17 14:08:40 D2040 ModemManager[7410]: (ttyACM0): --> 'AT+GCAP' mar 17 14:08:40 D2040

Own number

Is there anything in MM which attempts to fetch the modem's own phone number? I see a line for it in 'mmcli -m 0', but unsure where it could/would/might obtain this (seems to be somewhere in the 'libmm' stuff?). ___ ModemManager-devel mailing

Re: Cinterion 'simstatus'

> On 09 March 2017 at 08:02 Aleksander Morgado wrote: > > On Wed, Mar 8, 2017 at 9:29 PM, Reinhard Speyerer wrote: > > > > I'll look for a command which can achieve the same test - perhaps the > > > function could switch over to the alternative if it

Re: [PATCH] telit: enable 'SIM ready' notifications with #QSS=2

> Maybe it wouldn't be a bad idea to keep track of which operations may > fail due to SIM being busy, and perform automatic retry later if we > get that specific error, something like that. If the information can be updated later and it's not needed soon, it's a good idea. On Fri, 17 Mar 2017 at

Re: [PATCH] telit: enable 'SIM ready' notifications with #QSS=2

Well, before "#QSS: 3" you can expect some errors accessing the SIM, but it's not forbidden, and in fact we got some errors sometimes, like "SIM Busy" On Fri, 17 Mar 2017 at 10:38 Aleksander Morgado wrote: > On Fri, Mar 17, 2017 at 10:35 AM, Carlo Lobrano

RE: [PATCH] telit: lock/unlock CSIM operations by default

Thank you all, You have all been really helpful and quick and the patch seems to do its job perfectly! Salvador -Original Message- From: Aleksander Morgado [mailto:aleksan...@aleksander.es] Sent: jueves, 16 de marzo de 2017 22:35 To: Carlo Lobrano; Penalva, Salvador; Daniele Palmas

Re: [PATCH] telit: enable 'SIM ready' notifications with #QSS=2

On Fri, Mar 17, 2017 at 10:35 AM, Carlo Lobrano wrote: > mar 17 09:07:10 D2040 ModemManager[23597]: Waiting up to 5 seconds for SIM > readiness (#QSS: 3) > mar 17 09:07:15 D2040 ModemManager[23597]: After SIM unlock: SIM readiness > timeout 5 expired. Continuing... > mar 17

Re: [PATCH] telit: enable 'SIM ready' notifications with #QSS=2

In this test it took 35 seconds (I was testing 5 seconds timeout here, with some more debug logs), but I think it's SIM's content dependent mar 17 09:07:10 D2040 ModemManager[23597]: Waiting up to 5 seconds for SIM readiness (#QSS: 3) mar 17 09:07:15 D2040 ModemManager[23597]: After SIM unlock:

Re: 'port forced close' after failed ppp

> On 16 March 2017 at 16:23 Dan Williams wrote: > > On Thu, 2017-03-16 at 13:36 +, Colin Helliwell wrote: > > > > On 14 March 2017 at 14:18 Colin Helliwell > > ms.com> wrote: > > > > > > > On 13 March 2017 at 09:53 Colin Helliwell

Re: [PATCH] telit: enable 'SIM ready' notifications with #QSS=2

On Fri, Mar 17, 2017 at 10:23 AM, Carlo Lobrano wrote: > > I tested your patch and it seems working fine, even if #QSS: 3 always > arrives very late respect any acceptable timeout (the modem reads all SIM > values, even sms, before signaling QSS:3). > Moreover, this change

Re: MBIM plugin question

On Fri, Mar 17, 2017 at 7:50 AM, Skateboarding Boy wrote: > I am new to modem manager. I'd like to know if MBIM interterface requires a > correct plugin to work. The MBIM support is built-in ModemManager itself, no external plugin required. -- Aleksander