Please find it below:
--
General | path: /org/freedesktop/ModemManager1/Modem/0
| device id: a0193c11c5ea6e80f76bf9e745d04925de2e0867
--
Hardware | manufacturer: Sierra Wire
Hey,
>
> I'm testing MM 1.18.2 release and finding that the supported bands and
> current bands are shown empty. I'm using EM7511 modem in MBIM mode in OpenWRT
> framework (with QMI over MBIM enabled). The bands are displayed correctly in
> an older MM release (1.12.6). Please let me know what
Hey,
On Fri, Oct 1, 2021 at 5:52 PM Frederic Martinsons
wrote:
>
> Last try of the day, I built a ModemManager with WITH_NEWEST_QMI_COMMANDS
> enable and things goes pretty well since I got lot of more update than before
> (see log joined)
>
> Looking at the code implied, this is expected becau
On Fri, Oct 1, 2021 at 5:15 PM Frederic Martinsons
wrote:
>
> I just tested to grow the threasholds_data to have better granularity (I used
> { -90, -80, -70, -60, -58, -56, -54, -52, -50 } ) and like the comment in the
> code said, my modem didn't like is 😉
>
> I got a "couldn't enable signal s
Hey
On Fri, Oct 1, 2021 at 3:50 PM Frederic Martinsons
wrote:
>
> Ok thanks for the tips, should I issue a merge request with the modified
> threshold ?
>
Yes please, that would be good.
>
> I my application needs to have a rapid refresh rate of signal quality, do you
> think it will be corre
Last try of the day, I built a ModemManager with WITH_NEWEST_QMI_COMMANDS
enable and things goes pretty well since I got lot of more update than before
(see log joined)
Looking at the code implied, this is expected because there are more thresholds
and they have better granularity ({ -100, -97,
I just tested to grow the threasholds_data to have better granularity (I used {
-90, -80, -70, -60, -58, -56, -54, -52, -50 } ) and like the comment in the
code said, my modem didn't like is 😉
I got a "couldn't enable signal strength indications: 'QMI protocol error (19):
'ArgumentTooLong''"
B
Ok thanks for the tips, should I issue a merge request with the modified
threshold ?
I my application needs to have a rapid refresh rate of signal quality, do you
think it will be correct (I means without impact on modem
connectivity/stability) to send regularly mmcli --signal-get (the equival
Hey,
> So I tried on my own computer and it was the same, as you suggested I
> activated extended signal interface every 10s and by moving around I managed
> to make the RSSI moved from -59 dBm to -75 dBm and the signal quality stays
> not updated.
>
> If I understand correctly, this is an expe
So I tried on my own computer and it was the same, as you suggested I activated
extended signal interface every 10s and by moving around I managed to make the
RSSI moved from -59 dBm to -75 dBm and the signal quality stays not updated.
If I understand correctly, this is an expected behavior with
Hi,
I'm testing MM 1.18.2 release and finding that the supported bands and current
bands are shown empty. I'm using EM7511 modem in MBIM mode in OpenWRT framework
(with QMI over MBIM enabled). The bands are displayed correctly in an older MM
release (1.12.6). Please let me know what additional
> If you cannot physically remove the antenna for the testing, can you
> at least move the modem around? You may also enable the extended
> signal interface with e.g. a 10s rate and see if the reported RSSI
> values change across the thresholds you configured. The key to
> understand is whether we
>
> I did your suggested modifications (patches mm-broadband-modem-qmi.c) and it
> seems to change nothing (I keep getting my signal quality "cached" and I
> don't see "Signal Strength" indications beside in the beginning of modem
> initialization)
>
If you cannot physically remove the antenna
> It's a EG25, I assume in miniPCIe format? Do you have access to the antenna
> connectors?
Nope, it is an USB dongle
(https://developers.soracom.io/en/start/connect/soracom-onyx-lte/) and I made a
typo, it is an EC25 not EG25 (I was tricked by mmcli output and the modem
revision which is EG25
Hey,
>
> > But what do you want? Do you want the extended signal interface
> > information, or do you want the percentage value (which is probably
> > what you were using when AT protocol was being used).
>
> I want the percentage value for the moment (to keep backward compatibility
> with what w
15 matches
Mail list logo
