This patch add supported modes loading in Telit plugin.
---
plugins/telit/mm-broadband-modem-telit.c | 173 +++
1 file changed, 173 insertions(+)
diff --git a/plugins/telit/mm-broadband-modem-telit.c
b/plugins/telit/mm-broadband-modem-telit.c
index 77b1800..3866e54
This patch series adds supported and current modes loading for Telit plugin
Daniele Palmas (2):
plugin: telit: add supported modes loading
plugin: telit: add current mode loading
plugins/telit/mm-broadband-modem-telit.c | 186 +++
1 file changed, 186 insertions
This patch add supported modes loading in Telit plugin.
---
plugins/telit/mm-broadband-modem-telit.c | 104 +++
1 file changed, 104 insertions(+)
diff --git a/plugins/telit/mm-broadband-modem-telit.c
b/plugins/telit/mm-broadband-modem-telit.c
index 77b1800..5b3d18c
This patch adds current modes setting in Telit plugin
---
plugins/telit/mm-broadband-modem-telit.c | 98
1 file changed, 98 insertions(+)
diff --git a/plugins/telit/mm-broadband-modem-telit.c
b/plugins/telit/mm-broadband-modem-telit.c
index d4b0a42..0127314
Hi Aleksander,
2016-04-08 13:11 GMT+02:00 Aleksander Morgado <aleksan...@aleksander.es>:
> On Thu, Apr 7, 2016 at 12:57 PM, Daniele Palmas <dnl...@gmail.com> wrote:
>> The error seems to be triggered by this:
>>
>> ModemManagere[30896]: [1460023605.
Hi Aleksander,
2016-04-08 16:42 GMT+02:00 Aleksander Morgado :
> When we were completing tasks in idle, the logic was like this:
>
> * Schedule task completion in idle
> * self->priv->task = NULL
> * (idle) Task completion callback called
>
> This meant that the
Hi Carlo,
2016-04-11 10:55 GMT+02:00 Daniele Palmas <dnl...@gmail.com>:
> Hi Aleksander,
>
> 2016-04-08 17:14 GMT+02:00 Aleksander Morgado <aleksan...@aleksander.es>:
>> On Fri, Apr 8, 2016 at 4:55 PM, Daniele Palmas <dnl...@gmail.com> wrote:
>>> 201
Hi Aleksander,
2016-04-08 17:14 GMT+02:00 Aleksander Morgado <aleksan...@aleksander.es>:
> On Fri, Apr 8, 2016 at 4:55 PM, Daniele Palmas <dnl...@gmail.com> wrote:
>> 2016-04-08 16:42 GMT+02:00 Aleksander Morgado <aleksan...@aleksander.es>:
>>> When we were
)) {
+ MM_SERIAL_ERROR_RESPONSE_TIMEOUT) ||
+g_error_matches (error,
+ MM_SERIAL_ERROR,
+ MM_SERIAL_ERROR_SEND_FAILED)) {
return FALSE;
}
--
2.7.0
Regards,
Daniele
2016-04-07 9:24 GMT+02:00 Daniele Palmas <dnl...@gmail.com>:
&g
This patch adds section for building Telit common code and modifies
Dell section for using Telit library
---
plugins/Makefile.am | 28 ++--
1 file changed, 22 insertions(+), 6 deletions(-)
diff --git a/plugins/Makefile.am b/plugins/Makefile.am
index 018b696..31d222a
This patch moves init and port grabbing functions to a separate file
to allow functions call from Dell plugin
---
plugins/telit/mm-common-telit.c | 318
plugins/telit/mm-common-telit.h | 40 +
plugins/telit/mm-plugin-telit.c | 300
Hi Aleksander,
2016-04-27 21:20 GMT+02:00 Aleksander Morgado <aleksan...@aleksander.es>:
> On Wed, Apr 27, 2016 at 9:04 PM, Aleksander Morgado
> <aleksan...@aleksander.es> wrote:
>> On Wed, Apr 27, 2016 at 4:36 PM, Daniele Palmas <dnl...@gmail.com> wrote:
>>&g
Hi Aleksander,
2016-04-27 21:41 GMT+02:00 Daniele Palmas <dnl...@gmail.com>:
> Hi Aleksander,
>
> 2016-04-27 21:20 GMT+02:00 Aleksander Morgado <aleksan...@aleksander.es>:
>> On Wed, Apr 27, 2016 at 9:04 PM, Aleksander Morgado
>> <aleksan...@aleksander.es>
'
| registration: 'unknown'
-
SIM | path: '/org/freedesktop/ModemManager1/SIM/0'
-
Bearers | paths: 'none'
Daniele Palmas (3):
dell: forbid 413c/81ba modem in order to use Telit plugin
telit: add support
This patch adds the udev rule for using device 413c/81ba with Telit
plugin (dynamic port configuration)
---
plugins/telit/77-mm-telit-port-types.rules | 4
1 file changed, 4 insertions(+)
diff --git a/plugins/telit/77-mm-telit-port-types.rules
b/plugins/telit/77-mm-telit-port-types.rules
413c/81ba is a Dell branded Telit modem that is better driven by Telit
plugin. This patch avoids the modem to be taken by Dell plugin.
---
plugins/dell/mm-plugin-dell.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/plugins/dell/mm-plugin-dell.c b/plugins/dell/mm-plugin-dell.c
index
This patch adds the udev rules for supporting GE910 (PID 0x22)
---
plugins/telit/77-mm-telit-port-types.rules | 4
1 file changed, 4 insertions(+)
diff --git a/plugins/telit/77-mm-telit-port-types.rules
b/plugins/telit/77-mm-telit-port-types.rules
index c0119c6..36a4f99 100644
---
GE910 family supports #PORTCFG layouts different than HE910
family ones.
This patch properly tags GE910 ports according to Telit document
"GE910 Family Ports Arrangements, 1vv0301049"
---
plugins/telit/mm-common-telit.c | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
This patch series adds support for Telit GE910.
Full startup log at http://pastebin.com/Bpx4XEFy
Daniele Palmas (2):
telit: add udev rules for supporting GE910
telit: add GE910 #PORTCFG layouts
plugins/telit/77-mm-telit-port-types.rules | 4
plugins/telit/mm-common-telit.c
GE910 is a 2g only modem and when queried for bands it returns
only a 2g set of bands:
--> 'AT#BND=?'
<-- '#BND: (0-3)OK'
Current regex fails, since it considers the 3g bands block mandatory.
A similar problem happens for current bands.
This patch modifies the regular expressions for properly
QMI_PROTOCOL_ERROR_NOT_SUPPORTED as another error for
which the new pin checking status way is tried.
The output with the patch is:
http://pastebin.com/JVdZuVMn
Daniele Palmas (1):
broadband-modem-qmi: add QMI_PROTOCOL_ERROR_NOT_SUPPORTED case for pin
status checking
src/mm-broadband-modem-qmi.c | 5 -
1 file
Telit LE922A does not like the legacy way for checking pin status, but
instead of returning QMI_PROTOCOL_ERROR_INVALID_QMI_COMMAND, it returns
QMI_PROTOCOL_ERROR_NOT_SUPPORTED, making the modem not to be fully
initialized.
This patch adds QMI_PROTOCOL_ERROR_NOT_SUPPORTED as another error for
2017-03-24 17:38 GMT+01:00 Aleksander Morgado <aleksan...@aleksander.es>:
> On Fri, Mar 24, 2017 at 3:33 PM, Daniele Palmas <dnl...@gmail.com> wrote:
>> So LN930 was a "special" modem, in the sense that was never produced
>> with Telit VID.
>
> D
Hi Aleksander,
2017-03-24 15:33 GMT+01:00 Daniele Palmas <dnl...@gmail.com>:
> Hi Aleksander,
>
> 2017-03-24 14:48 GMT+01:00 Aleksander Morgado <aleksan...@aleksander.es>:
>> Vendor specific plugins that support QMI or MBIM based devices need to
>> handle the cr
Hi Aleksander,
2017-03-24 14:48 GMT+01:00 Aleksander Morgado :
> Vendor specific plugins that support QMI or MBIM based devices need to
> handle the creation of these modems themselves.
>
> https://bugs.freedesktop.org/show_bug.cgi?id=100372
> ---
>
> Hey Carlo and
Hi Aleksander (resending with all included),
2017-03-13 20:05 GMT+01:00 Aleksander Morgado <aleksan...@aleksander.es>:
> On Mon, Mar 13, 2017 at 6:29 PM, Daniele Palmas <dnl...@gmail.com> wrote:
>>> With this patch on, a Telit RS232 modem still needs the udev tag in
Hi Dan,
2017-04-03 21:52 GMT+02:00 Dan Williams :
> Looks like a C error from the AT#PSNT codepath; all the docs
> I can find indicate that AT+SERVICE returns only an integer and
> no commas:
Confirmed, when this command is supported as far as I know there is
only one integer.
Hi Aleksander,
2017-03-11 13:29 GMT+01:00 Aleksander Morgado :
> 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
Hi Salvador,
2017-03-10 13:38 GMT+01:00 Penalva, Salvador :
> Hi Aleksander,
>
> Sorry for the delay but I was trying to debug a little more the logs to
> isolate the problem.
>
> Answering to your question: We use SimpleConnect command inside a script but
> we don't
Hi Shijo and Aleksander,
2017-08-17 12:14 GMT+02:00 Aleksander Morgado :
> On Thu, Aug 17, 2017 at 2:45 AM, Jose, Shijo wrote:
I just realized you're working with a MBIM modem. So the "No AT port
available to run command" may actually
Hi Kelvin,
2017-07-19 14:51 GMT+02:00 Kelvin :
> Hi
>
>> According to logs shared by Kelvin, the modem seems to be properly
>> replying
>
>
> Thanks, yes QMI commands seem to be working now but it fails to register on
> a network.
>
> I've tried a SIM card for a different
Hi Kelvin,
2017-07-28 10:10 GMT+02:00 Kelvin :
> Hi,
>
>>
>> > And --3gpp-scan on that card showed 'available' for all networks.
>> >
>> > Thanks for any hints,
>>
>> Sorry, I'm not a qmi protocol expert so maybe I'm missing something,
>> but those seem not to be useful to me
Hi Lars,
2017-07-19 13:43 GMT+02:00 Lars Melin :
> On 2017-07-19 16:48, Kelvin wrote:
>>
>>
>> If I'm not wrong qmi_wwan is trying to bind to interface 5, but
>> rmnet
>> is on 2 (that has been wrongly taken by option). Which kernel
>> version
>>
HI Aleksander,
2017-06-28 18:44 GMT+02:00 Aleksander Morgado <aleksan...@aleksander.es>:
> Hey Daniele,
>
> See comments below.
>
> On 28/06/17 16:07, Daniele Palmas wrote:
>> ---
>> plugins/telit/mm-common-telit.c | 64
>> +++--
---
plugins/telit/mm-broadband-modem-telit.c | 285 ++-
1 file changed, 131 insertions(+), 154 deletions(-)
diff --git a/plugins/telit/mm-broadband-modem-telit.c
b/plugins/telit/mm-broadband-modem-telit.c
index 55deeed..2054b0c 100644
---
---
v2: address GTask cancellation issues highlighted by Aleksander
---
plugins/telit/mm-common-telit.c | 65 +++--
1 file changed, 30 insertions(+), 35 deletions(-)
diff --git a/plugins/telit/mm-common-telit.c b/plugins/telit/mm-common-telit.c
index
---
plugins/telit/mm-common-telit.c | 64 +++--
1 file changed, 29 insertions(+), 35 deletions(-)
diff --git a/plugins/telit/mm-common-telit.c b/plugins/telit/mm-common-telit.c
index 1e43588..cfd3292 100644
--- a/plugins/telit/mm-common-telit.c
+++
2017-08-07 11:04 GMT+02:00 Aleksander Morgado :
>>> I can confirm that LE866-SV1 uses Telit custom 3GPP2 PDU format: there
>>> should be a PDU example in the AT commands user guide (see +CMGS
>>> 3GPP2), while EU variants use 3GPP.
>>
>> Thanks for the
Hi Aleksander and José,
2017-08-04 15:24 GMT+02:00 Aleksander Morgado :
> Hey José, Carlo & Daniele
>
> On Fri, Aug 4, 2017 at 10:27 AM, José wrote:
>> I am trying the same thing with the Telit LE866. With that modem I am
>> able to send SMSs in
Hi Josè,
2017-08-04 16:18 GMT+02:00 José <josedd...@gmail.com>:
> On Fri, Aug 4, 2017 at 4:14 PM, Daniele Palmas <dnl...@gmail.com> wrote:
>>
>> as far as I remember 3GPP pdu should be supported, but maybe this
>> could depend on firmware customizations.
>>
2017-08-07 9:50 GMT+02:00 José <josedd...@gmail.com>:
>
> On Mon, Aug 7, 2017 at 9:46 AM, Daniele Palmas <dnl...@gmail.com> wrote:
>> I can confirm that LE866-SV1 uses Telit custom 3GPP2 PDU format: there
>> should be a PDU example in the AT commands user guide
2017-08-07 10:39 GMT+02:00 Daniele Palmas <dnl...@gmail.com>:
> 2017-08-07 10:24 GMT+02:00 Aleksander Morgado <aleksan...@aleksander.es>:
>>>>> I can confirm that LE866-SV1 uses Telit custom 3GPP2 PDU format: there
>>>>> should be a PDU example in the
Telit LTE modems could reply to +WS46=? with:
+WS46: (12,22,25,28-31)
This patch extends +WS46=? response parser to support ranges.
---
Hi,
current mm log is
Jun 15 15:04:04 L2122 ModemManager[831]: (ttyACM0): --> 'AT+WS46=?'
Jun 15 15:04:04 L2122 ModemManager[831]: (ttyACM0): <-- ''
Jun 15
Hi Aleksander,
2017-06-16 10:39 GMT+02:00 Aleksander Morgado <aleksan...@aleksander.es>:
> Hey Daniele,
>
> On Fri, Jun 16, 2017 at 10:11 AM, Daniele Palmas <dnl...@gmail.com> wrote:
>> Telit LTE modems could reply to +WS46=? with:
>>
>> +WS46: (12,22,2
Telit LTE modems could reply to +WS46=? with:
+WS46: (12,22,25,28-31)
This patch extends +WS46=? response parser to support ranges.
---
v2: used mm_parse_uint_list as suggested by Aleksander
---
src/mm-modem-helpers.c | 25 -
src/tests/test-modem-helpers.c | 32
2017-06-16 15:56 GMT+02:00 Aleksander Morgado <aleksan...@aleksander.es>:
> On 16/06/17 14:57, Daniele Palmas wrote:
>> Telit LTE modems could reply to +WS46=? with:
>>
>> +WS46: (12,22,25,28-31)
>>
>> This patch extends +WS46=? response parse
Telit LTE modems use #PSNT: 4 for LTE access technology,
and #PSNT: 5 for unknown access technology, while HSDPA
modems use #PSNT: 4 for unknown access technology.
This patch fixes those #PSNT values interpretation according
to the modem capabilities.
---
Hi,
this patch needs commit
Hi Aleksander and Rowan,
2017-09-19 18:53 GMT+02:00 Aleksander Morgado :
>>
>>
>> Interesting, in the testing lab they noticed that they only saw this being a
>> problem when ModemManager was running. But if your telling me that it’s
>> related to the modules firmware...
Hi Rowan,
2017-09-20 16:36 GMT+02:00 Rowan Hamilton :
>
> Please see the attached logs. In the file entitled:
> ModemManager_waiting_on_prl_update_from_carrier.txt you can see that a #905
> comes in but we never get a #909. I'm thinking that its not relaying these
> #9xx
Hi Carsten,
Il giorno ven 22 feb 2019 alle ore 12:12 Stelling2 Carsten
ha scritto:
>
> Hi,
>
> I must correct me, modem type is LE910-EU1 as Reinhard assumed. Sorry for
> this confusion.
> As a workaround for testing, we send AT+WS46 commands via D-Bus, but that
> seems possible only, if MM
Il giorno mer 27 feb 2019 alle ore 11:22 Aleksander Morgado
ha scritto:
>
> >
> > But setting the preferred mode fails.
> >
> > mmcli -m 0 --set-preferred-mode=2G
> > error: setting preferred mode requires list of allowed modes
> >
>
> This is expected; you only want to set a "preferred mode" if
Hi Bjørn,
Il giorno lun 10 dic 2018 alle ore 14:25 Bjørn Mork ha scritto:
>
> As for Qualcomm based modems: Haven't yet seen any docs for the PCIe
> interface there either. So I'll assume it is similar to the Intel one.
related to Qualcomm I guess this development
Hi Carsten,
Il giorno mar 19 nov 2019 alle ore 14:24 Daniele Palmas
ha scritto:
>
> Hi Carsten,
>
> Il giorno mar 19 nov 2019 alle ore 10:10 Stelling2 Carsten
> ha scritto:
> >
> > Hi,
> >
> > I've just updated MM from 1.10.0 to 1.12.0 with the resu
Carsten
> > To: "modemmanager-devel@lists.freedesktop.org"
> > ,
> > "Daniele Palmas (dnl...@gmail.com)"
> > Subject: AW: Set allowed mode to 2G, 3G, 4G not working
> >
> > Hi,
> >
> > I've just updated MM from 1.10.0 to 1.12.
feedback, such that this feature can be released.
>
> Thank you for your help.
>
> Carsten
>
> -Ursprüngliche Nachricht-
> Von: ModemManager-devel
> [mailto:modemmanager-devel-boun...@lists.freedesktop.org] Im Auftrag von
> Stelling2 Carsten
> Gesendet:
hether not having GNSS location info
> from either PDS or LOC service is expected in Telit devices or not.
> @Daniele Palmas could you help with that?
>
Yes, the C1 supports the LOC service, as well as LM940/960 and FN980.
Regards,
Daniele
> Cheers!
>
> --
> Aleksander
> http
Hi Aleksander,
Il giorno gio 7 mag 2020 alle ore 17:45 Aleksander Morgado
ha scritto:
>
> Hey Daniele,
>
> > > > > Then we need to debug why we were not able to get any LOC indication
> > > > > with NMEA traces in David's setup.
> > > >
> > > > > David, could you retry to setup the location
Hi Aleksander and David,
Il giorno mar 5 mag 2020 alle ore 17:14 Aleksander Morgado
ha scritto:
>
> Hey Daniele & David
>
> > > Then we need to debug why we were not able to get any LOC indication
> > > with NMEA traces in David's setup.
> >
> > > David, could you retry to setup the location
Hi Aleksander and David,
Il giorno mar 5 mag 2020 alle ore 17:14 Aleksander Morgado
ha scritto:
>
> Hey Daniele & David
>
>
> Daniele, any idea why we're not receiving NMEA traces via QMI
> indications in this case? Do you see something wrong in the sequence
> to enable the GNSS location
Hi Michal,
Il ven 9 ott 2020, 04:05 Michał Mazur ha scritto:
> Hi Aleksander,
>
> Thank you for the reply. As you suggested I created MMPortRmnet to handle
> data port setup:
>
> https://gitlab.freedesktop.org/mkm/ModemManager/-/commit/b25310666e41a19150fe2b18ff3b7cce73f9129a
> It includes all
mandatory to get the most out of the
modem.
> > 3. MM query qmap-version, ep-type, iface-id,
> > dll_data_aggregation_max_size from rmnet physic driver
> > 4. MM send QMIWDS_ADMIN_SET_DATA_FORMAT_REQ to modem.
> > 5. MM get ul_data_aggregation_max_siz
Hi,
Il giorno lun 19 ott 2020 alle ore 09:57 Aleksander Morgado
ha scritto:
>
> Hey,
>
> > > > I seem we have done for "QMI based on QTRT" in libqmi.
> > > > For QUALCOMM's data services, there are lots of QMI library,
> > > > and libqmi used a more simply solution. (in fact, if
Hi Aleksander,
Il giorno lun 13 lug 2020 alle ore 10:08 Aleksander Morgado
ha scritto:
>
> Hey!
>
> > > > This particular device has a second port configuration (1bc7:1102),
> > > > which which looks like this:
> > > >
> > > > /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=atmel-ehci/3p, 480M
Hi Mark,
Il giorno lun 13 lug 2020 alle ore 15:17 Mark Deneen
ha scritto:
>
> Daniele,
>
> > @Mark, did you check if there's a more recent firmware update than the
> > one you are using?
>
> I'm running 37.00.210-B038-P0C.21, but I'm having trouble
> understanding if any of the available
t isn't a complete
> solution, and I think we should try to find some other way to handle
> this if possible.
>
> I find it very very weird that the modem doesn't reply a CONNECT
> response after the ATD, that would be a very weird firmware bug! Maybe
> the TTY we're using for conne
Hi Bjørn,
Il giorno lun 26 apr 2021 alle ore 18:23 Bjørn Mork ha scritto:
>
> Bjørn Mork writes:
>
> > Sorry, i do not think these issues are related to ModemManager at all.
>
> This is a test from freshly booted modem, MM not running:
>
> root@finn:~# qmicli -p -d /dev/cdc-wdm0
Hi Aleksander,
Il giorno mar 4 mag 2021 alle ore 00:34 Aleksander Morgado
ha scritto:
>
> Hey Dan & all,
>
> The send-delay property allows us to send the characters in an AT
> command one by one, with some delay in between them. Right now the
> default configuration of the send-delay property
Hi Aleksander,
Il giorno sab 27 feb 2021 alle ore 10:47 Aleksander Morgado
ha scritto:
>
> Hey
>
> > > I've been working on updating ModemManager to allow setting up QMAP
> > > data aggregated links transparently, either with qmi_wwan
> > > add_mux/del_mux or with qmi_wwan+rmnet
Hi Aleksander,
Il giorno gio 9 set 2021 alle ore 11:28 Aleksander Morgado
ha scritto:
>
> Hey hey,
>
> This is a new major release of ModemManager, which will be the base for the
> 1.18.x stable series (the new "mm-1-18" branch in git). The release has been
> tagged as "1.18.0".
>
> This is
Hi Aleksander,
Il giorno lun 2 ago 2021 alle ore 16:41 Aleksander Morgado <
aleksan...@aleksander.es> ha scritto:
> Hey all,
>
> I've been testing with all my modems for the next 1.18 release, and
> for the QMI and MBIM ones I've done tests with and without
> multiplexing support (i.e.
Hi Amol,
Il giorno lun 11 ott 2021 alle ore 15:03 Amol Lad ha scritto:
>
> Hi Daniele,
>
>
>
> I’m patched my MM 1.18.2 with your MR (LN920 Initial Support) and testing
> LN920 in MBIM mode. I’m noticing that the “supported” and “current” bands are
> not shown in “mmcli -m 0” output and below
Hi Amol,
Il giorno ven 8 ott 2021 alle ore 10:18 Amol Lad ha scritto:
>
> Hi,
>
> LN920 is a new modem from Telit. Any suggestions, how can I add compositions
> rules for this modem in plugins/77-mm-telit-port-types.rules?
>
> lsusb output is available here:
>
gt; Thanks
>
> Amol
>
>
>
> From: Amol Lad
> Sent: Monday, 11 October 2021 6:34 PM
> To: 'Daniele Palmas' ; 'ModemManager (development)'
>
> Subject: LN920: MBIM Bands not shown (MM 1.18.2)
>
>
>
> Hi Daniele,
>
>
>
> I’m patched my MM 1.
Il giorno mar 12 ott 2021 alle ore 14:26 Amol Lad ha scritto:
>
>
> > Anyway, it would be better also to fix #BND=? management for those
> > setups where qmi is not used.
> >
>
> I've started on this and shall submit a MR in a day or two..
>
Thanks! Meanwhile I'm going to look at the qmi way.
Hi Aleksander and Amol,
Il giorno mar 30 nov 2021 alle ore 09:54 Aleksander Morgado
ha scritto:
>
> If this works for you in MBIM I guess it's because the AT commands to
> change bands using the Telit shared utils do wait for the band change
> to take effect before going on. Ma
Hi Juan,
Il giorno mar 23 nov 2021 alle ore 11:03 Aleksander Morgado
ha scritto:
>
> Hey,
>
> >
> > I am trying to debug the reset sequence of my modem (I've posted today
> > a separate message about this).
> >
> > I was wondering if there is a way to trace the communication between
> > MM and
Hi Amol,
Il giorno ven 5 nov 2021 alle ore 04:12 Amol Lad ha scritto:
>
> Hi,
>
> We're not getting network time using mmcli -time command. I'm not sure if it
> is something specific to my setup or an issue. However, I do get correct
> network time when using Sierra modem with the same SIM
agement in Telit
plugin).
Its default should be #NITZ=7,0 (meaning automatic update already enabled).
Is it possible that, for some reason, your modem had automatic update disabled?
Regards,
Daniele
> Thanks
> Amol
>
> -Original Message-
> From: Daniele Palmas
> Sent: S
Hi Aleksander and Carsten,
Il giorno sab 12 feb 2022 alle ore 01:02 Aleksander Morgado
ha scritto:
>
> Hey,
>
> >
> > I'm struggling to connect to a private Vodafone APN using MM and NM.
> >
> > Modem Telit LE910-EU1 (MBIM)
> > ModemManager 1.18.6
> > libmbim 1.18.4
> > libqmi 1.30.2
> >
Hi Amol,
Il giorno lun 25 lug 2022 alle ore 07:34 Amol Lad ha scritto:
>
> Hi Daniele,
>
>
>
> Can we use latest MM 1.18.10 release to test Telit FN990 (USB 3.1 host
> interface) or we should use git main? Is this chip now fully supported in MM?
>
I've been testing FN990 through main, never
Hi Alexey,
Il giorno mer 31 ago 2022 alle ore 14:43 Alexey Orishko
ha scritto:
>
> Hi,
>
> I'm implementing ecm support in telit plugin (baseline: latest main).
if it's not a reserved piece of information, which Telit model are you using?
Regards,
Daniele
> Somehow modem goes in
Hello Peter,
Il giorno mer 7 set 2022 alle ore 16:00 Peter Naulls
ha scritto:
>
>
> Based upon the similar models, this appears to be correct. This is against
> ModemManager 1.18.10:
>
> --- plugins/telit/77-mm-telit-port-types.rules.orig 2022-09-07
> 09:51:25.186228559 -0400
> +++
Hi Koen,
Il giorno gio 11 ago 2022 alle ore 15:24 Koen Vandeputte
ha scritto:
>
> Hi All,
>
> I'm currently working on adding MHI support within OpenWRT. (kernel 5.15.59)
>
> I have a few modems laying around here:
>
> - Sierra Wireless EM9191
> - Telit FN980
> - Fibocom FM150-AE
>
> On all 3 of
Hi Koen,
Il giorno ven 12 ago 2022 alle ore 15:26 Koen Vandeputte
ha scritto:
>
>
> On 12.08.22 10:55, Daniele Palmas wrote:
> > Hi Koen,
> >
> > Il giorno gio 11 ago 2022 alle ore 15:24 Koen Vandeputte
> > ha scritto:
> >> Hi All,
> >>
>
Amol,
Il giorno lun 28 nov 2022 alle ore 13:22 Aleksander Morgado
ha scritto:
>
> > > Attaching full log and relevant portion seems below. No it's not
> > > regression. I just loaded 1.20.2 mainly for 5g support.
> > >
> >
> > I've got a bunch of changes fixing this and adding modes retrieval
Hi Amol,
Il giorno mar 3 gen 2023 alle ore 06:36 Amol Lad ha scritto:
>
> Hi,
>
> I get the following error when enabling NMEA in FN990 with MM 1.20.4 (It
> comes with 1.18.6 as well). I do not recall seeing this with Telit LN920 so
> looks like this is something FN990 specific. Please advise.
; 37 : NG-RAN and E-UTRAN
> 38 : NG-RAN, E-UTRAN and UTRAN
> 40 : NG-RAN and UTRAN
>
>
> From: Aleksander Morgado
> Sent: Monday, November 28, 2022 4:03 PM
> To: Amol Lad
> Cc: Daniele Palmas ; ModemManager (development)
>
> Subject: R
Hello,
Il giorno mer 3 mag 2023 alle ore 15:12 Christian Schneider
ha scritto:
>
> Hello,
> I have a Telit LE910C1-EU modem. It is recognized and calls/SMS work,
> but when I establish an online connection, eg. with
> mmcli -m 0 --simple-connect "apn=internet.telekom"
> ModemManager crashes. The
Hi Aleksander,
Il giorno mar 23 mag 2023 alle ore 14:43 Aleksander Morgado
ha scritto:
>
> Hey all,
>
> The modemmanager.org site now includes a document explaining details
> about the MBIM protocol and the new Microsoft extensions (e.g. for 4G
> and 5G specific features):
>
>
89 matches
Mail list logo