I am working with two different QMI modems (Telit LE910 and Sierra MC7710
in QMI mode) and experimenting one issue with both of them.
After boot I try to establish the connection:
ModemManager &
(wait for the modem to be detected)
mmcli -m 0 --simple-connect="apn=.."
This somtimes works, but mos
On Thu, Nov 12, 2015 at 1:15 PM, José wrote:
>
> I am working with two different QMI modems (Telit LE910 and Sierra MC7710 in
> QMI mode) and experimenting one issue with both of them.
>
> After boot I try to establish the connection:
>
> ModemManager &
> (wait for the modem to be detected)
> mmc
On Thu, 12 Nov 2015 13:15:16 +0100
José wrote:
> ModemManager &
> (wait for the modem to be detected)
> mmcli -m 0 --simple-connect="apn=.."
>
> This somtimes works, but most of the time fails.
My crystal ball says to wait 1-2 minutes for the modem's firmware to
finish its boot sequence befor
Sorry for the delay.
This is the debug log for the Telit LE910 with a Vodafone SIM:
http://pastebin.com/U7EBv8sr
The test case is:
- Boot the device
- Issue: mmcli -m 0 --simple-connect=apn=ac.vodafone.es
This command returns: error: couldn't connect the modem: 'The connection is
closed'
On Thu
On Tue, 2015-11-17 at 18:10 +0100, José wrote:
> Sorry for the delay.
>
> This is the debug log for the Telit LE910 with a Vodafone SIM:
> http://pastebin.com/U7EBv8sr
>
> The test case is:
> - Boot the device
> - Issue: mmcli -m 0 --simple-connect=apn=ac.vodafone.es
> This command returns: erro
Seems like the log I gave was not complete. Here is a better one:
http://pastebin.com/Y24a9Y8W
At line 1849 seems like ModemManager decides to abort the connection, I am
not sure why.
On Tue, Nov 17, 2015 at 11:20 PM, Dan Williams wrote:
> On Tue, 2015-11-17 at 18:10 +0100, José wrote:
> > So
On Tue, Nov 17, 2015 at 11:20 PM, Dan Williams wrote:
> On Tue, 2015-11-17 at 18:10 +0100, José wrote:
>> Sorry for the delay.
>>
>> This is the debug log for the Telit LE910 with a Vodafone SIM:
>> http://pastebin.com/U7EBv8sr
>>
>> The test case is:
>> - Boot the device
>> - Issue: mmcli -m 0 -
On Wed, Nov 18, 2015 at 9:14 AM, José wrote:
> Seems like the log I gave was not complete. Here is a better one:
>
> http://pastebin.com/Y24a9Y8W
>
> At line 1849 seems like ModemManager decides to abort the connection, I am
> not sure why.
During the connection attempt the modem gets unregistere
I have emptied my data plan so now I am in 'limited plan' mode. Could that
be the issue?
If after that failure, i repeat the mmcli -m 0 --simple-connect=apn=
ac.vodafone.es command, it does connect and works (with poor speeds beacuse
of the limited plan mode)
On Wed, Nov 18, 2015 at 10:48 AM, Ale
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
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
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: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
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, 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
The problem only occurs if the LE910 was in low power mode (AT+CFUN=4) when
plugged to the embbeded device. Does ModemManager manage power state modes?
Should it automatically full enable the modem (AT+CFUN=1) when issuing
mmcli --simple-connect?
I am going to test with a new firmware I have recei
On 19/01/16 10:13, José wrote:
> The problem only occurs if the LE910 was in low power mode (AT+CFUN=4) when
> plugged to the embbeded device. Does ModemManager manage power state modes?
> Should it automatically full enable the modem (AT+CFUN=1) when issuing
> mmcli --simple-connect?
>
Yes, tha
I have update to the last firmware (17.01.522 1 [Oct 16 2014
07:00:00]) and the issue is still reproducible.
I am almost sure that the issue is related to power management.
When the modem is in AT+CFUN=4, trying to enable it with ModemManager
(mmcli -m 0 -e) does not work. Trying to change the
On Tue, Jan 19, 2016 at 4:51 PM, José wrote:
> I have update to the last firmware (17.01.522 1 [Oct 16 2014
> 07:00:00]) and the issue is still reproducible.
>
> I am almost sure that the issue is related to power management.
>
> When the modem is in AT+CFUN=4, trying to enable it with ModemMana
Looking at
http://cgit.freedesktop.org/ModemManager/ModemManager/tree/plugins/telit/mm-plugin-telit.c?id=1.4.12
seems like the Telit plugin only handles tty port, but I am using QMI
with the Telit LE910. Should it still be using the Telit plugin?
The following lines appear at the log (in this ord
Hey!
On Tue, Jan 19, 2016 at 6:36 PM, José wrote:
> Looking at
> http://cgit.freedesktop.org/ModemManager/ModemManager/tree/plugins/telit/mm-plugin-telit.c?id=1.4.12
> seems like the Telit plugin only handles tty port, but I am using QMI
> with the Telit LE910. Should it still be using the Telit
Hi José, Aleksander,
my two cents here
> I have also noticed that ModemManager uses not documented AT+CFUN
modes:
>
> root at ccimx6sbc:~# mmcli -m 0 --set-power-state-off
> ModemManager[791]: Modem powered off... may no longer be
accessible
> successfully set new power state in the modem
>
On Tue, Jan 19, 2016 at 9:55 PM, c.lobr...@gmail.com
wrote:
>
>> I have also noticed that ModemManager uses not documented AT+CFUN modes:
>>
>> root at ccimx6sbc:~# mmcli -m 0 --set-power-state-off
>> ModemManager[791]: Modem powered off... may no longer be accessible
>> successfully set new powe
On Tue, Jan 19, 2016 at 5:34 PM, Aleksander Morgado
wrote:
>
> Yes, it should be using the Telit plugin.
>
>
I was adding the udev rules for the LE910 in the
77-mm-telit-port-types.rules file when I saw the following comment:
# NOTE: Qualcomm Gobi-based devices like the LE920 should not be handl
Hey,
>>
>> Yes, it should be using the Telit plugin.
>>
>>
>
> I was adding the udev rules for the LE910 in the
> 77-mm-telit-port-types.rules file when I saw the following comment:
>
> # NOTE: Qualcomm Gobi-based devices like the LE920 should not be handled
> # by this plugin, but by the Gobi plu
On Wed, Jan 20, 2016 at 11:32 AM, Aleksander Morgado
wrote:
>
> Actually, why don't you try to get the modem fully connected manually
> with qmicli or qmi-network and see if you still see the same issues
> when ModemManager's logic is not around?
>
With qmicli and qmi-network the problem persist.
26 matches
Mail list logo
