[PATCH 2/4] broadband-modem: query +CMER format before enabling/disabling

Colin Helliwell colin.helliwell at ln-systems.com
Mon May 22 11:26:05 UTC 2017


> On 22 May 2017 at 12:22 Aleksander Morgado <aleksander at aleksander.es> wrote:
> 
> On Mon, May 22, 2017 at 12:36 PM, Colin Helliwell
> 
> <colin.helliwell at ln-systems.com> wrote:
> 
> > > Don't blindly try '+CMER=3,0,0,1' to enable and '+CMER=0' to disable
> > > Mobile Equipment Event Reporting. We now query the device for the
> > > 
> > > supported formats and use that info to build commands that will work.
> > 
> > I've just tried this set of patches on Cinterion EHS5:
> > 
> > May 22 11:13:22 wg daemon.info ModemManager[831]:  [1495448002.187999] [src/mm-port-serial-at.c:462] debug_log(): (ttyMux1): --> 'AT+CMER=?'
> > May 22 11:13:22 wg daemon.info ModemManager[831]:  [1495448002.199794] [src/mm-port-serial-at.c:462] debug_log(): (ttyMux1): <-- 'AT+CM'
> > May 22 11:13:22 wg daemon.info ModemManager[831]:  [1495448002.202536] [src/mm-port-serial-at.c:462] debug_log(): (ttyMux1): <-- 'ER=?'
> > May 22 11:13:22 wg daemon.info ModemManager[831]:  [1495448002.216859] [src/mm-port-serial-at.c:462] debug_log(): (ttyMux1): <-- '+CMER: (1,2),0,0,(0-1),0'
> > May 22 11:13:22 wg daemon.info ModemManager[831]:  [1495448002.219054] [src/mm-port-serial-at.c:462] debug_log(): (ttyMux1): <-- 'OK'
> > May 22 11:13:22 wg daemon.info ModemManager[831]:  [1495448002.219853] [src/mm-broadband-modem.c:2610] set_unsolicited_events_handlers(): (ttyMux1) Setting 3GPP unsolicited events handlers
> > May 22 11:13:22 wg daemon.info ModemManager[831]:  [1495448002.220244] [src/mm-broadband-modem.c:2911] modem_3gpp_enable_unsolicited_events(): Skipping +CMER enable command: not supported
> > 
> > Which is pretty much what I'd expect, btw - albeit that it's AT doc doesn't actually mention CMER at all.
> > 
> > Don't have my BGS2 board with me at the mo' - it requires 3,0,0,2 . Will advise asap.
> 
> Oh, wait, there's something wrong. The EHS5 here supports modes 1 and
> 2 and that wasn't considered, we should have tried any of those. Let
> me fix the logic and add some more debugging logs.
> 

Oh, see what you mean. As I say, docs don't mention CMER support - but I'll gladly try summat out.


More information about the ModemManager-devel mailing list