ModemManager using QMI doesnt always work in the first attemp.

[José]

Is there a way to know when is late enough to issue the connect
request? Im trying to get an embedded system connected to cellular
network on boot, so the commands are getting issued as soon as
ModemManager detects the modem.

Also, you said this could be due to the SIM reading errors that appear
early in the log. I am only having problems with the Telit LE910-EUG
modem, which does not read my Movistar nor the Yoigo SIM, and reads
the Vodafone SIM with those errors. Do you know if there could be any
differences between these SIMs that could explain that? Also, do you
know if there is any limitations to which SIMs can a modem read?
(because I am using those SIM cards with other modems with no problem)

Thanks for the answers.

On Mon, Jan 18, 2016 at 4:32 PM, Aleksander Morgado
<aleksander at aleksander.es> wrote:
> On Mon, Jan 18, 2016 at 4:13 PM, José <Joseddg92 at gmail.com> wrote:
>> This issue happens intermitently the first time I try the mmcli -m 0
>> --simple-connect command.
>>
>> When it fails, issuing 'mmcli -m 0 --simple-connect' again properly connects.
>>
>> Is there a way to fix this?
>
> If the issue is that the modem gets unregistered during the connection
> setup, which is what was seen in the last debug log, then I guess
> there's little we can do but to fail the connection attempt :/ Maybe
> you're issuing the Connect request too early while the modem is still
> getting registered properly in the network?
>
> --
> Aleksander
> https://aleksander.es