Hello everyone,
I have encountered an issue using ModemManager 1.16.8 via dbus.
In my case there is a need to send periodic AT commands to a Cinterion
modem to get infos about connection.
For example AT^SMONI is ok and the response is not empty. However I would
like to get also the response from A
Hey,
> I have encountered an issue using ModemManager 1.16.8 via dbus.
> In my case there is a need to send periodic AT commands to a Cinterion modem
> to get infos about connection.
> For example AT^SMONI is ok and the response is not empty. However I would
> like to get also the response from
Hey!
> I am using ModemManager with u-blox TOBY-L210 for a while now with older
> versions of ModemManager (1.7.x). I did some patches and home-brew code to
> make that combination work.
> I now want to switch to newer versions of MM (1.18), benefit from the good
> work on MM, and do it "the ri
Hey,
I am using ModemManager with u-blox TOBY-L210 for a while now with older
versions of ModemManager (1.7.x). I did some patches and home-brew code to make
that combination work.
I now want to switch to newer versions of MM (1.18), benefit from the good work on MM,
and do it "the right way"
Hey,
> In general, I think that the way that ublox intended to use the Toby-L2
> does not really match the way that MM works: In its application notes,
> ublox suggest to set the default bearer setting and then just to use the
> already connected context.
> If I map that to MM / NM, that would mea
Hello,
I have a successful internet connection with mmcli, but there is no AT
port. So I cannot send AT commands.
Hardware | manufacturer: Sierra Wireless, Incorporated
|model: Sierra Wireless EM9191
System | device:
/sys/devices
Hey!
> I have a successful internet connection with mmcli, but there is no AT port.
> So I cannot send AT commands.
>
> Hardware | manufacturer: Sierra Wireless, Incorporated
>|model: Sierra Wireless EM9191
>
> System | device:
