<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 again,<br class=""><div><br class=""></div><div>I did some more work and now I am able to connect manually (without ModemManager). All that’s required is the AT^SWWAN=1,1 command if the APN is already correctly configured. I checked this via AT+CGDCONT?. Note, that this only works for CID=1. After changing the APN for CID=1, the modem must be forced to re-attach since the modem auto-attaches after power-up. More on this can be found in the chapter “Attaching to LTE Networks” in AT manual. Another interesting fact is that the modem appends a string to the APN after it has attached, in my case “<span style="font-family: Arial; font-size: 11pt; white-space: pre-wrap;" class="">.mnc009.mcc242.gprs</span>”. I’m not sure if this is common.</div><div><br class=""></div><div>In order to debug the command sequence issued by ModemManager, I extracted all commands sent by the ModemManager from the debug logs incl. their timing. I then replayed them with the same (similar) timing manually from a script, i.e. without ModemManager running. I made sure that the modem was freshly booted in both cases. Curiously, when replaying the commands, the AT^SWWAN commands succeeds. This leaves me a little puzzled.</div><div><br class=""></div><div>Does ModemManager issue commands concurrently? I saw in the logs both “device open count is 2 (open)” and “device open count is 3 (open)”. Could that mean that sometimes two AT commands are sent at the same time?</div><div><br class=""></div><div>Best regards,</div><div>Sven</div></body></html>