We have the MC7354 working quite well with Verizon in both 3G and LTE modes.
Using Ubuntu 15.10 with bone stock NM+MM.
We had to pursue special authorization though and jump through various
bureaucratic hoops to get it activated.
You won't be able to simply insert a SIM and go with the MC7354,
On Tue, 19 Jan 2016 00:31:51 +0100
Aleksander Morgado wrote:
> On Mon, Jan 18, 2016 at 10:15 PM, Glenn Washburn
> wrote:
> > "curl -v --interface wwan0 http://www.google.com";
>
> You're binding the request to the wwan interface, which I assume it's
> because it isn't the default route.
>
> Tr
Response parsing was being done in different places for AT and QCDM subclasses;
in the case of AT it was being done early, before returning the byte array in
the mm_serial_port_command_finish() response. In the case of QCDM, it was being
done after mm_serial_port_command_finish(), and that was forc
On Mon, Jan 18, 2016 at 10:15 PM, Glenn Washburn
wrote:
> "curl -v --interface wwan0 http://www.google.com";
You're binding the request to the wwan interface, which I assume it's
because it isn't the default route.
Try to disable the reverse path filtering, something like:
# for i in /proc/sys/n
Dan Williams writes:
> On Mon, 2016-01-18 at 15:15 -0600, Glenn Washburn wrote:
>> Hi All,
>>
>> I've had a ton of headaches getting my MC7354 on Verizon's M2M data
>> network. Using NM+MM I can get the interface to come up with an IP,
>> so
>> it seems as though I'm connected to verizon's netw
On Mon, 2016-01-18 at 15:15 -0600, Glenn Washburn wrote:
> Hi All,
>
> I've had a ton of headaches getting my MC7354 on Verizon's M2M data
> network. Using NM+MM I can get the interface to come up with an IP,
> so
> it seems as though I'm connected to verizon's network. However, when
> I
> run "
On Mon, Jan 18, 2016 at 9:53 PM, Dan Williams wrote:
>> > So wouldn't that also blow away the next messages in the buffer for
>> > something like cancellation or random internal MM errors?
>> >
>>
>> If we've got unsolicited messages interleaved with the response,
>> those
>> should have been proc
On Sun, 2016-01-17 at 18:24 +0100, Aleksander Morgado wrote:
> On 17/01/16 16:55, Dan Williams wrote:
> > > When valid responses were returned to the caller of the serial
> > > > command, the
> > > > caller itself was responsible for removing from the GByteArray
> > > > the
> > > > data that
> > >
On Mon, 2016-01-18 at 16:55 +0100, José wrote:
> I was not sure what caused the 'limited' registration state... I am
> going to check if there is any firmware updates available and try
> that.
>
> They all are nanoSIM. Not sure if there is any errors when using
> Movistar and Yoigo SIMs, I will t
I was not sure what caused the 'limited' registration state... I am
going to check if there is any firmware updates available and try
that.
They all are nanoSIM. Not sure if there is any errors when using
Movistar and Yoigo SIMs, I will try it out and check the logs as soon
as I can.
Thanks for y
On Mon, Jan 18, 2016 at 4:39 PM, José wrote:
> Is there a way to know when is late enough to issue the connect
> request? Im trying to get an embedded system connected to cellular
> network on boot, so the commands are getting issued as soon as
> ModemManager detects the modem.
>
In theory the Si
Is there a way to know when is late enough to issue the connect
request? Im trying to get an embedded system connected to cellular
network on boot, so the commands are getting issued as soon as
ModemManager detects the modem.
Also, you said this could be due to the SIM reading errors that appear
e
On Mon, Jan 18, 2016 at 4:13 PM, José wrote:
> This issue happens intermitently the first time I try the mmcli -m 0
> --simple-connect command.
>
> When it fails, issuing 'mmcli -m 0 --simple-connect' again properly connects.
>
> Is there a way to fix this?
If the issue is that the modem gets unr
This issue happens intermitently the first time I try the mmcli -m 0
--simple-connect command.
When it fails, issuing 'mmcli -m 0 --simple-connect' again properly connects.
Is there a way to fix this?
On Wed, Nov 18, 2015 at 10:42 AM, Aleksander Morgado
wrote:
> On Tue, Nov 17, 2015 at 11:20 PM
---
plugins/telit/77-mm-telit-port-types.rules| 4 +
plugins/telit/mm-broadband-modem-telit.c | 86 +
plugins/telit/mm-modem-helpers-telit.c| 372 +-
plugins/telit/mm-modem-helpers-telit.h| 58
plugins/telit/tests/test-mm-mo
Hi,
here is a new proposal implementation for load_supported_bands interface
for Telit modems.
Best regards,
Carlo
Carlo Lobrano (1):
[Telit plugin] add load_supported_bands interface
plugins/telit/77-mm-telit-port-types.rules| 4 +
plugins/telit/mm-broadband-modem-telit.c
16 matches
Mail list logo
