Hey,
+thaller
>> > I did some further testing and while ModemManager is continually
>> reporting the serial port can't be opened, I was able to connect to the port
>> and send AT commands to the modem and the modem responded. This
>> means there is something in ModemManager that is triggering
> -Original Message-
> From: Aleksander Morgado [mailto:aleksan...@aleksander.es]
> Sent: Monday, August 20, 2018 4:33 PM
>
> > I did some further testing and while ModemManager is continually
> reporting the serial port can't be opened, I was able to connect to the port
> and send AT
> I did some further testing and while ModemManager is continually reporting
> the serial port can't be opened, I was able to connect to the port and send
> AT commands to the modem and the modem responded. This means there is
> something in ModemManager that is triggering these messages and
> -Original Message-
> From: Matthew Starr
> Sent: Monday, August 06, 2018 11:36 AM
>
> > -Original Message-
> > From: Matthew Starr
> > Sent: Thursday, July 19, 2018 2:22 PM
> > To: 'Aleksander Morgado'
> >
> > > -Original Message-
> > > From: Aleksander Morgado
> -Original Message-
> From: Aleksander Morgado [mailto:aleksan...@aleksander.es]
> Sent: Thursday, July 19, 2018 2:16 PM
>
> Hey,
>
> On Thu, Jul 19, 2018 at 3:47 PM, Matthew Starr
> wrote:
> > I am running ModemManager 1.8.0 and NetworkManager 1.8.0 on an
> embedded device with the
Hey,
On Thu, Jul 19, 2018 at 3:47 PM, Matthew Starr wrote:
> I am running ModemManager 1.8.0 and NetworkManager 1.8.0 on an embedded
> device with the Linux OS built by buildroot. I am using a u-blox TOBY-R200
> cell modem connected over USB with virtual serial interfaces /dev/ttyACM0
>
