> On 09 March 2017 at 08:02 Aleksander Morgado <aleksan...@aleksander.es> wrote: > > On Wed, Mar 8, 2017 at 9:29 PM, Reinhard Speyerer <rs...@arcor.de> wrote: > > > > I'll look for a command which can achieve the same test - perhaps the > > > function could switch over to the alternative if it gets an > > > 'unsupported' error? (My modems give a "+CME ERROR: 22") > > > > Maybe AT^SSET would be worth a try as it was already supported by TC63 > > modems: > > > > AT^SSET=1 > > OK > > AT+CPIN=xxxx > > OK > > ^SSIM READY > > AT^SSET=0 > > OK > > That's a totally acceptable thing indeed. We could enable AT^SSET=1 > early in the initialization and just wait for ^SSIM to be reported, > maybe adding some additional "fallback wait time" in the case it isn't > received, or something like that. >
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 BGS2 module, but not on the [later!] EHS5.... :S _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
