Hi again,
Please excuse the continuation of the monologue, but I believe I have found a
good hint if not the reason for the issue at hand. I noticed two things:
1. When NetworkManager wasn’t running on my device, I couldn’t establish the
connection manually.
2. When I talked to the native UART
Hi all,
>> Might this imply that we're talking about the initial bearer and that
>> when MM tries to connect, because it will attempt to close any existing
>> connection, the modem is telling MM "no"?
>>
>> We already know we need to be better about auto-detecting that the
>> initial bearer is ac
> > I actually tried exactly this: I restarted the modem without
> > ModemManager running, sent AT to the modem until I got +PBREADY as
> > part of the reply and then started ModemManager. Unfortunately, this
> > leads to the same behaviour. Same old +CEER: "SM
> > deactivation",187,"Last PDN disco
On Fri, 2019-03-15 at 16:34 +0100, Sven Schwermer wrote:
> Hi all,
>
> > On 15 Mar 2019, at 16:03, matthew stanger
> > wrote:
> >
> > Anyway, the only thing I can think of is a timing issue with the
> > modem
> > firwmare and network registration or initial bearer setup or
> > something
> > like
Hi all,
> On 15 Mar 2019, at 16:03, matthew stanger wrote:
>
> Anyway, the only thing I can think of is a timing issue with the modem
> firwmare and network registration or initial bearer setup or something
> like that. Perhaps MM isn't querying some ready state well enough, or
> the modem isn't
>
> Anyway, the only thing I can think of is a timing issue with the modem
> firwmare and network registration or initial bearer setup or something
> like that. Perhaps MM isn't querying some ready state well enough, or
> the modem isn't fully set up when we're querying because MM isn't
> asking th
On Fri, 2019-03-15 at 14:20 +0100, Sven Schwermer wrote:
> Hi again,
>
> I did some more work and now I am able to connect manually (without
> ModemManager). All that’s required is the AT^SWWAN=1,1 command if the
> APN is already correctly configured. I checked this via AT+CGDCONT?.
> Note, that t
Hi again,
I did some more work and now I am able to connect manually (without
ModemManager). All that’s required is the AT^SWWAN=1,1 command if the APN is
already correctly configured. I checked this via AT+CGDCONT?. Note, that this
only works for CID=1. After changing the APN for CID=1, the mo
Hi Matthew,
Thanks for the update!
> I've had a long back-and-forth with the vendor but basically we still can't
> get the demo board reliably working with basic AT commands.
> In short I'm still working on it but really don't understand why this modem
> model continues to prove so difficult t
>
> I have the same issues with the ELS61 modem. Did you make any progress
> regarding
> this issue?
I've had a long back-and-forth with the vendor but basically we still can't
get the demo board reliably working with basic AT commands.
Could the GPRS/AutoAttach setting (see AT^SCFG) have anythin
Hi Matthew,
I have the same issues with the ELS61 modem. Did you make any progress regarding
this issue? Could the GPRS/AutoAttach setting (see AT^SCFG) have anything to do
with this?
Best regards,
Sven
___
ModemManager-devel mailing list
ModemManager-d
>
> Do you have any clue what is happening?
I'm having the same thing happen here. I'm working this with the Vendor
now. I think there is something from a HW setup that is wrong & not
obvious. This is probably why SWWAN is also failing for you. Will post when
I find out more.
Cheers
On Fri, Feb
>
> You need to call "common_create_bearer (task);" before the return here
A true dark knight, thanks Aleksander!
Ana, try this instead:
>From 43c8870b7478f3e5ccdb70a3fc89edddcef96d67 Mon Sep 17 00:00:00 2001
From: Matthew Stanger
Date: Thu, 14 Feb 2019 08:28:14 -0700
Subject: [PATCH] mm-bb-m-c
Hey,
> Give this a try (note this is just a hack to tmp disable the SWWAN feature &
> hopefully I get the ELS61 soon):
> Branched from 1.8.2:
>
> From 63f9ac8a0db1d8902dd7bef329f441ef4ea86c6b Mon Sep 17 00:00:00 2001
> From: Matt Stanger
> Date: Wed, 13 Feb 2019 20:18:00 -0700
> Subject: [PATCH
Give this a try (note this is just a hack to tmp disable the SWWAN feature
& hopefully I get the ELS61 soon):
Branched from 1.8.2:
>From 63f9ac8a0db1d8902dd7bef329f441ef4ea86c6b Mon Sep 17 00:00:00 2001
From: Matt Stanger
Date: Wed, 13 Feb 2019 20:18:00 -0700
Subject: [PATCH] mm-bb-m-cinterion: D
Hi Mathew,
thank you for contacting. Hopefully you will get the modem soon.
In the meantime, I would appreciate if you send me the patch to turn off
SWWAN, this way we could see if it works without it.
Thank you,
Ana
___
ModemManager-devel mailing
There are a few things we can do from here:
1. I can give you a simple patch to turn off SWWAN so you can just use
ppp. This doesn't really help the greater good but will get you going on
the issue.
2. You'd be the first out of the EU but I have seen carriers(in Asia)
requiring LTE
Hi Ana,
There are quite a few things that catch my eye here. First there are many
AT cmds that need to be updated for this specific modem, many
proprietary AT cmds have changed. Still the SWWAN connection interface is
pretty basic and as-is I think it should be able to work. It'd be great if
you c
Hi Matthew,
I sent the output of the ModemManager in debug mode attached. Here you
have it again. Is this enough or do you need a longer output?
Thank you for your help,
Ana
ModemManager[834]: [1548351439.066265] Simple connect started...
ModemManager[834]: [1548351439.066878]PIN:
Hi Ana,
Can you trying running ModemManager with the 'log-level' set to DEBUG and
shooting me the results.
System | device: '/sys/devices/platform/ahb/50.ohci/usb1/1-2'
On a most likely unrelated note, if your bring up a product heads up that
you'll have trouble with USB 1.x(ohci)
Hello,
I'm trying to make a connection with this LTE modem without success. I'm
not sure if it is related with SWWAN but that is the only special thin I
can identify.
Modem manager version is 1.8.2-1.
The modem is a MC89-LTE.
See attached modem manager output.
/org/freedesktop/ModemManager1/M
21 matches
Mail list logo
