URC mistaken for solicited responce

[matthew stanger]

You're good at what you do mate, thanks! You want a patch? I think just
might be our slow antique hardware though to be honest.

On Fri, May 18, 2018 at 2:57 PM, Aleksander Morgado <
aleksander at aleksander.es> wrote:

> 2018-04-25T07:35:16.132117 ModemManager[1797]: <debug> (ttyACM1)
> device open count is 2 (open)
> 2018-04-25T07:35:16.143804 ModemManager[1797]: <debug> (ttyACM1): -->
> 'AT+CIND?<CR>'
> 2018-04-25T07:35:16.876211 ModemManager[1797]: <debug> (ttyACM1): <--
> '<CR><LF>+CIEV: 1,2<CR><LF>'
> 2018-04-25T07:35:16.955301 ModemManager[1797]: <debug> (ttyACM0): <--
> '<CR><LF>+CIEV: 1,2<CR><LF>'
> 2018-04-25T07:35:19.121047 ModemManager[1797]: <debug> (ttyACM1)
> device open count is 3 (open)
> 2018-04-25T07:35:19.134009 ModemManager[1797]: <debug> (ttyACM1)
> device open count is 4 (open)
> 2018-04-25T07:35:19.146082 ModemManager[1797]: <debug> (ttyACM1)
> device open count is 3 (close)
> 2018-04-25T07:35:19.155738 ModemManager[1797]: <debug> (ttyACM1): -->
> 'AT^SWWAN?<CR>'
> 2018-04-25T07:35:20.317705 ModemManager[1797]: <debug> (ttyACM0): <--
> '<CR><LF>+CIEV: 1,3<CR><LF>'
> 2018-04-25T07:35:20.398151 ModemManager[1797]: <debug> (ttyACM1): <--
> '<CR><LF>+CIND:
> 0,2,1,1,1,0,1,0<CR><LF><CR><LF>OK<CR><LF><CR><LF>+CIEV:
> 1,3<CR><LF><CR><LF>+CIEV: psinfo,6<CR><LF><CR><LF>+CREG:
> 5,"1611","0217BCC",2<CR><LF><CR><LF>+CGREG:
> 5,"1611","0217BCC",2<CR><LF><CR><LF>+CIEV: psinfo,10<CR><LF>'
> 2018-04-25T07:35:20.413390 ModemManager[1797]: <debug> Modem
> /org/freedesktop/ModemManager1/Modem/0: access technology changed
> (hsdpa, hsupa -> umts)
> 2018-04-25T07:35:20.427281 ModemManager[1797]: <debug> Modem
> /org/freedesktop/ModemManager1/Modem/0: access technology changed
> (umts -> hsdpa, hsupa)
> 2018-04-25T07:35:20.438959 ModemManager[1797]: <warn>  checking if
> connected failed: Couldn't parse ^SWWAN response: '+CIND:
> 0,2,1,1,1,0,1,0'
>
> Look at the AT+CIND? we send at 07:35:16. There's no reply to that one
> in 3s, so we just keep on with our logic, and the response to the
> +CIND? comes when we're waiting for the AT^SWWAN response.
> We should make the AT+CIND? command timeout longer than 3s; in this
> case something like 4s or 5s would have been enough.
>
> --
> Aleksander
> https://aleksander.es
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20180518/d032b4b4/attachment.html>