<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi all,<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 15 Mar 2019, at 16:03, matthew stanger <<a href="mailto:stangerm2@gmail.com" class="">stangerm2@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Anyway, the only thing I can think of is a timing issue with the modem<br class="">firwmare and network registration or initial bearer setup or something<br class="">like that. Perhaps MM isn't querying some ready state well enough, or<br class="">the modem isn't fully set up when we're querying because MM isn't<br class="">asking the right question. NOt sure what else it could be. </blockquote><div class="">Wonderful observation there. Just realized this modem's boot ready URC is '+PBREADY'. There's nothing in MM to support(minus ublox plugin) this cmd, which would imply that MM would be sending cmd's before the module is ready.</div><div class=""><br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> I made sure that the modem was freshly booted in both cases. </blockquote><div class="">That'd be the main difference, you waited.</div><div class=""><br class=""></div><div class="">To test this theory out all you need to do is stop MM, plugin/start your modem give it ~20 sec's to be sure. Then start MM and see if the connection now works. Let me know if that work and then we can go from there.</div></div></div></blockquote></div><br class=""><div class="">I actually tried exactly this: I restarted the modem without ModemManager running, sent AT to the modem until I got +PBREADY as part of the reply and then started ModemManager. Unfortunately, this leads to the same behaviour. Same old +CEER: "SM deactivation",187,"Last PDN disconnection not allowed”</div><div class=""><br class=""></div><div class="">Sven</div></body></html>