On Tue, 2015-09-01 at 00:38 +0100, João M. S. Silva wrote:
> On 08/31/2015 09:03 PM, Dan Williams wrote:
> > serial ports and may be designated /dev/ttyS0. Do you have
> > any /dev/ttySx ports and if so can you talk to the modem with them?
>
> Yes, I communicate for instance with miniterm.py /dev
On 08/31/2015 09:03 PM, Dan Williams wrote:
serial ports and may be designated /dev/ttyS0. Do you have
any /dev/ttySx ports and if so can you talk to the modem with them?
Yes, I communicate for instance with miniterm.py /dev/ttyS0 115200.
*Maybe*. ModemManager supports standard 3GPP AT comm
On Mon, 2015-08-31 at 20:23 +0100, João M. S. Silva wrote:
> Thanks for the explanation.
>
> On 08/31/2015 07:59 PM, Dan Williams wrote:
> > Not quite correct. ModemManager does not use D-Bus to talk to the
> > modem; it uses D-Bus to talk to client applications. To talk to the
>
> So, when I u
On Mon, Aug 31, 2015 at 8:38 PM, Highland, Glenn
wrote:
> Our device is running ModemManager v1.4.6 against a Telit HE910-D modem
> (rev. 12.00.024). We’ve been quite successful
>
> in expediting data transfer via IP through the cell network (no problems
> there), but we’re having considerable di
Hello all,
Our device is running ModemManager v1.4.6 against a Telit HE910-D modem (rev.
12.00.024). We've been quite successful
in expediting data transfer via IP through the cell network (no problems
there), but we're having considerable difficulty
getting SMS messages to be received by the d
Thanks for the explanation.
On 08/31/2015 07:59 PM, Dan Williams wrote:
Not quite correct. ModemManager does not use D-Bus to talk to the
modem; it uses D-Bus to talk to client applications. To talk to the
So, when I use mmcli (client application), I am using the DBus to talk
to the ModemMa
On Mon, 2015-08-31 at 19:37 +0100, João M. S. Silva wrote:
> Hi,
>
> I am using ModemManager to control an HSDPA modem:
>
> $ lsusb
> Bus 001 Device 004: ID 12d1:1001 Huawei Technologies Co., Ltd.
> E169/E620/E800 HSDPA Modem
>
> But now we are testing this device: SIM800L from SIMCom.
>
> Thi
On Mon, Aug 31, 2015 at 2:17 PM, Raul Suarez Moreno
wrote:
> [947188221.161321] [mm-iface-modem-3gpp.c:751]
> mm_iface_modem_3gpp_run_registration_checks(): Running registration checks
> (CS: 'yes', PS: 'yes', EPS: 'no')
Looks like the modem was detected, but wasn't flagged as supporting
4G: it'
Hi,
I am using ModemManager to control an HSDPA modem:
$ lsusb
Bus 001 Device 004: ID 12d1:1001 Huawei Technologies Co., Ltd.
E169/E620/E800 HSDPA Modem
But now we are testing this device: SIM800L from SIMCom.
This modem understands AT commands that we send through a terminal
program, like
On Mon, 2015-08-31 at 17:52 +0100, Raul Suarez Moreno wrote:
> Hi Dan! Yes, I could rebuild the project. What patches should I apply? FYI,
> I'm currently using MM 1.4.8 version, may I move to 1.4.10?
Probably not required; first lets try the attached patch.
Dan
> On Mon, Aug 31, 2015 at 5:09 PM
On 08/26/2015 05:51 PM, Harald Jung wrote:
I've built a version with ModemManager started seperatly from
NetworkManager.
I can check it tommorow with a notebook, which has this problem.
Did it work?
--
João M. S. Silva
___
ModemManager-devel mailing
Hi Dan! Yes, I could rebuild the project. What patches should I apply? FYI,
I'm currently using MM 1.4.8 version, may I move to 1.4.10?
On Mon, Aug 31, 2015 at 5:09 PM, Dan Williams wrote:
> On Mon, 2015-08-31 at 13:17 +0100, Raul Suarez Moreno wrote:
> > Finally, ModemManager detected my modem.
On Thu, 2015-08-27 at 11:41 +0200, Aleksander Morgado wrote:
> Hey everyone,
>
> The 1.4.x series is 1 year old now, and we have quite some new things
> in git master since then (e.g. A-GPS & Voice APIs, the Dell
> plugin...).
>
> Do you guys think it would be a good idea to feature-freeze git ma
On Mon, 2015-08-31 at 13:17 +0100, Raul Suarez Moreno wrote:
> Finally, ModemManager detected my modem. Problem was the udev startup
> script, udevd was not being correctly initiated.
>
> Now, "mmcli -L" shows my modem device correctly. I could enable it and even
> send a text SMS, but I am not be
On Fri, 2015-08-21 at 12:06 +0200, Aleksander Morgado wrote:
> On Thu, Aug 20, 2015 at 6:43 PM, Dan Williams wrote:
> > CDMA-capable modems (like a Sierra EM7355) will fail to even enable,
> > because the internal CDMA code tries to initialize using AT commands and
> > that fails because many MBIM
Finally, ModemManager detected my modem. Problem was the udev startup
script, udevd was not being correctly initiated.
Now, "mmcli -L" shows my modem device correctly. I could enable it and even
send a text SMS, but I am not being successful at using "mmcli -m 0
--simple-connect", always getting:
16 matches
Mail list logo