> On 21 May 2017 at 13:54 Aleksander Morgado <aleksan...@aleksander.es> 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]: <debug> [1495448002.187999] [src/mm-port-serial-at.c:462] debug_log(): (ttyMux1): --> 'AT+CMER=?<CR>' May 22 11:13:22 wg daemon.info ModemManager[831]: <debug> [1495448002.199794] [src/mm-port-serial-at.c:462] debug_log(): (ttyMux1): <-- 'AT+CM' May 22 11:13:22 wg daemon.info ModemManager[831]: <debug> [1495448002.202536] [src/mm-port-serial-at.c:462] debug_log(): (ttyMux1): <-- 'ER=?<CR>' May 22 11:13:22 wg daemon.info ModemManager[831]: <debug> [1495448002.216859] [src/mm-port-serial-at.c:462] debug_log(): (ttyMux1): <-- '<CR><LF>+CMER: (1,2),0,0,(0-1),0<CR><LF>' May 22 11:13:22 wg daemon.info ModemManager[831]: <debug> [1495448002.219054] [src/mm-port-serial-at.c:462] debug_log(): (ttyMux1): <-- '<CR><LF>OK<CR><LF>' May 22 11:13:22 wg daemon.info ModemManager[831]: <debug> [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]: <debug> [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. _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
