On Wed, Mar 15, 2017 at 12:19 AM, Aleksander Morgado
wrote:
> Wrap the AT+CSIM=XX commands between lock (CSIM=1) and
> unlock (CSIM=0) operations.
>
> This seems to avoid the TTY lockup seen in several different Telit
> modules.
>
>
On Sat, Mar 11, 2017 at 1:29 PM, Aleksander Morgado
wrote:
> The telit plugin is based on two main ways of checking the purpose of
> each port: udev tags flagging specific interfaces (with info taken
> from Windows .inf drivers), or otherwise using AT#PORTCFG? to query
>
On Mon, Mar 13, 2017 at 5:34 PM, Dan Williams wrote:
>> If a device reports "LTE" in the list of current capabilities, we'll
>> set EPS network supported by default. This will enable CEREG
>> registration checks for AT based devices.
>>
>> If a device reports only "LTE" in the
On Thu, Mar 16, 2017 at 1:24 PM, Engel, Mike wrote:
> Changing the modem USB profile makes the modem work with the modemmanager
> version we are using.
If you end up using the u-blox plugin, MM should be able to handle the
connection regardless of the mode.
--
Aleksander
On Thu, 2017-03-16 at 13:36 +, Colin Helliwell wrote:
> > On 14 March 2017 at 14:18 Colin Helliwell > ms.com> wrote:
> >
> > > On 13 March 2017 at 09:53 Colin Helliwell > > tems.com> wrote:
> > >
> > > > On 13 March 2017 at 09:06 Colin
> On 14 March 2017 at 14:18 Colin Helliwell
> wrote:
>
> > On 13 March 2017 at 09:53 Colin Helliwell
> > wrote:
> >
> > > On 13 March 2017 at 09:06 Colin Helliwell
> > > wrote:
> > >
> > > >
Hi Aleksander,
Thanks for your quick reply. I will have a look to see if the unlock attempt is
performant or not. Also will I have a look into the latest source code in your
repo and that plu-in.
Changing the modem USB profile makes the modem work with the modemmanager
version we are using.
Hey Mike,
On Thu, Mar 16, 2017 at 11:46 AM, Engel, Mike wrote:
> We are using the UBlox L-210 modem with ModemManager 1.6.4 and the ACM
> interface we getting the following error message.
>
> ModemManager[852]: [1489583434.054490]
>
Hi all,
We are using the UBlox L-210 modem with ModemManager 1.6.4 and the ACM
interface we getting the following error message.
ModemManager[852]: [1489583434.054490]
[../../ModemManager-1.6.4/src/mm-port-serial-at.c:459] debug_log(): (ttyACM0):
<--
'OK'
ModemManager[852]:
> Is this extra "#QSS: 1" indication maybe a way the modem has to say
> "SIM ready" when it has been configured with "#QSS=1" instead of
> #QSS=2? If it happens just after SIM-PIN unlock, it could very well
> be.
I think the same, but it shouldn't do it. #QSS: 0/1 are for physical
changes on SIM,
On Thu, Mar 16, 2017 at 10:58 AM, Carlo Lobrano wrote:
> Sorry for the late reply, but I was double checking this change because of
> the last paragraph in +CSIM reference:
>
>> After the locking of the SIM-ME interface (AT+CSIM=1) the SIM will be
>> accessible only by
On Thu, Mar 16, 2017 at 10:57 AM, Daniele Palmas wrote:
> Tested with GL865 and working fine
>
> daniele@L2122:~$ mmcli -m 0
>
> /org/freedesktop/ModemManager1/Modem/0 (device id
> 'e31ff4d485c411511410e55f1f682373f9f68e2f')
> -
> Hardware |
Hi all,
Sorry for the late reply, but I was double checking this change because of
the last paragraph in +CSIM reference:
> After the locking of the SIM-ME interface (AT+CSIM=1) the SIM will be
> accessible only by AT+CSIM commands (#QSS: 0). The GSM and GPRS services
> will be automatically
Hi Aleksander (resending with all included),
2017-03-13 20:05 GMT+01:00 Aleksander Morgado :
> On Mon, Mar 13, 2017 at 6:29 PM, Daniele Palmas wrote:
>>> With this patch on, a Telit RS232 modem still needs the udev tag in
>>> the appropriate port to
14 matches
Mail list logo