<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="font-family:"Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif;font-size:14.6667px;background-color:rgb(255, 255, 255);display:inline !important">> It's a EG25, I assume
in miniPCIe format? Do </span><span style="font-family:"Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif;font-size:14.6667px;background-color:rgb(255, 255, 255);display:inline !important">you
have access to the antenna connectors?</span><br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="font-family:"Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif;font-size:14.6667px;background-color:rgb(255, 255, 255);display:inline !important"><br>
</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="font-family:"Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif;font-size:14.6667px;background-color:rgb(255, 255, 255);display:inline !important">Nope, it is an USB dongle
(<a href="https://developers.soracom.io/en/start/connect/soracom-onyx-lte/" id="LPlnk">https://developers.soracom.io/en/start/connect/soracom-onyx-lte/</a>) and I made a typo, it is an EC25 not EG25 (I was tricked by mmcli output and the modem revision which
is EG25GGBR07A07M2G)</span></div>
<div class="_Entity _EType_OWALinkPreview _EId_OWALinkPreview _EReadonly_1">
<div id="LPBorder_GTaHR0cHM6Ly9kZXZlbG9wZXJzLnNvcmFjb20uaW8vZW4vc3RhcnQvY29ubmVjdC9zb3JhY29tLW9ueXgtbHRlLw.." class="LPBorder442132" style="width: 100%; margin-top: 16px; margin-bottom: 16px; position: relative; max-width: 800px; min-width: 424px;">
<table id="LPContainer442132" role="presentation" style="padding: 12px 36px 12px 12px; width: 100%; border-width: 1px; border-style: solid; border-color: rgb(200, 200, 200); border-radius: 2px;">
<tbody>
<tr valign="top" style="border-spacing: 0px;">
<td>
<div id="LPImageContainer442132" style="position: relative; margin-right: 12px; height: 160px; overflow: hidden;">
<a target="_blank" id="LPImageAnchor442132" href="https://developers.soracom.io/en/start/connect/soracom-onyx-lte/"><img id="LPThumbnailImageId442132" alt="" height="160" style="display: block;" width="160" src="https://developers.soracom.io/assets/images/base-station.svg"></a></div>
</td>
<td style="width: 100%;">
<div id="LPTitle442132" style="font-size: 21px; font-weight: 300; margin-right: 8px; font-family: wf_segoe-ui_light, "Segoe UI Light", "Segoe WP Light", "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif; margin-bottom: 12px;">
<a target="_blank" id="LPUrlAnchor442132" href="https://developers.soracom.io/en/start/connect/soracom-onyx-lte/" style="text-decoration: none; color: var(--themePrimary);">Soracom Onyx LTE Dongle Setup Guide | SORACOM Developers</a></div>
<div id="LPDescription442132" style="font-size: 14px; max-height: 100px; color: rgb(102, 102, 102); font-family: wf_segoe-ui_normal, "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif; margin-bottom: 12px; margin-right: 8px; overflow: hidden;">
The plan01s SIM is a 3-in-1 design that allows you to conveniently break out the SIM card into standard/mini (2FF), micro (3FF), and nano (4FF) form factors. As the Onyx LTE dongle uses the nano (4FF) size, take care to remove the nano SIM card size when removing
it from its packaging.</div>
<div id="LPMetadata442132" style="font-size: 14px; font-weight: 400; color: rgb(166, 166, 166); font-family: wf_segoe-ui_normal, "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif;">
developers.soracom.io</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
> <span style="font-family:"Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif;font-size:14.6667px;background-color:rgb(255, 255, 255);display:inline !important">See<span> </span></span><a href="https://modemmanager.org/docs/modemmanager/debugging/#qmi-proxy-or-mbim-proxy-debug-logs" style="margin:0px;font-size:14.6667px;font-family:"Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif;background-color:rgb(255, 255, 255)">https://modemmanager.org/docs/modemmanager/debugging/#qmi-proxy-or-mbim-proxy-debug-logs</a></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks for the pointer, I'll do that.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="appendonsend"></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
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)</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Note: Since the log of MM and qmi_proxy took around 1MB , I choose to tar them, I hope it will not be refused by the mail engine.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Aleksander Morgado <aleksander@aleksander.es><br>
<b>Sent:</b> Friday, October 1, 2021 9:55 AM<br>
<b>To:</b> Frederic Martinsons <frederic.martinsons@sigfox.com><br>
<b>Cc:</b> modemmanager-devel@lists.freedesktop.org <modemmanager-devel@lists.freedesktop.org><br>
<b>Subject:</b> Re: Signal quality not updated with Quectel EG25 through QMI</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">Hey,<br>
<br>
><br>
> > But what do you want? Do you want the extended signal interface<br>
> > information, or do you want the percentage value (which is probably<br>
> > what you were using when AT protocol was being used).<br>
><br>
> I want the percentage value for the moment (to keep backward compatibility with what we got when using ppp). But I'll look at extended signal interface in the future<br>
><br>
<br>
Ok.<br>
<br>
> > Have you done tests e.g.<br>
> > disconnecting antennas and such, to see if those indications are<br>
> > emitted?<br>
><br>
> Nope, I didn't test that (and I don't know how)<br>
><br>
<br>
While you have debug logs on, you could physically disconnect the<br>
antenna from the modem. It's a EG25, I assume in miniPCIe format? Do<br>
you have access to the antenna connectors?<br>
<br>
> > If possible, please debug that with MM debug level<br>
> > enabled and also with the qmi-proxy running in verbose mode (in case<br>
> > the problem is a failure in the indication forward done by the proxy).<br>
><br>
> Sure, I joined the full log of ModemManager but I didn't find how to make qmi-proxy verbose so I patch
<a href="https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/blob/1.28.8/src/qmi-proxy/qmi-proxy.c">
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/blob/1.28.8/src/qmi-proxy/qmi-proxy.c</a> to set verbose_flag to TRUE<br>
> src/qmi-proxy/qmi-proxy.c · 1.28.8 · Mobile broadband connectivity / libqmi<br>
> QMI modem protocol helper library<br>
> gitlab.freedesktop.org<br>
<br>
See <a href="https://modemmanager.org/docs/modemmanager/debugging/#qmi-proxy-or-mbim-proxy-debug-logs">
https://modemmanager.org/docs/modemmanager/debugging/#qmi-proxy-or-mbim-proxy-debug-logs</a><br>
<br>
> From what I see in the log, there is no Signal indications, just a few "Get Packet Statistics"<br>
<br>
That may very well be because the signal didn't change too much; i.e.<br>
it stayed in the ranges defined for which we want signal indication<br>
updates. I've reviewed the log, and found that the thresholds given<br>
are very wrong I think:<br>
<br>
<<<<<< TLV:<br>
<<<<<< type<br>
= "Signal Strength Indicator" (0x10)<br>
<<<<<< length = 7<br>
<<<<<< value<br>
= 01:05:B0:D8:00:28:50<br>
<<<<<<<br>
translated = [ report = 'yes' thresholds = '{ [0] = '-80 ' [1] = '-40<br>
' [2] = '0 ' [3] = '40 ' [4] = '80 '}' ]<br>
<br>
The signal strength indicator allows configuring thresholds in the<br>
-127,+127 range (dBm), with a minimum of 5; but that doesn't mean we<br>
should evenly distribute the thresholds in that range. The docs don't<br>
say anything about this being RSSI, but I would have assumed it is,<br>
and in normal user setups we definitely don't expect any RSSI above 0!<br>
Could you edit mm-broadband-modem-qmi.c, method<br>
common_enable_disable_unsolicited_events_signal_strength(), and update<br>
the array of thresholds like this?<br>
<br>
static const gint8 thresholds_data[] = { -110, -100, -90, -80, -70 };<br>
<br>
Variations in the antenna connection done manually should definitely<br>
trigger QMI indications reporting the signal quality updates if those<br>
thresholds are configured.<br>
<br>
P.D. it's probably time we start integrating the "newest QMI commands"<br>
support by default.<br>
<br>
-- <br>
Aleksander<br>
<a href="https://aleksander.es">https://aleksander.es</a><br>
</div>
</span></font></div>
<p>Your privacy is important to us. Please see our <a href="https://www.sigfox.com/en/privacy-and-cookies-policy">
Privacy Notice</a> for further details. The information contained in this Message is confidential. If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this Message in error, please delete it and all
copies from your system and notify the sender immediately by return message. Any use of information contained in this Message not in accordance with its intended purpose, any dissemination or disclosure (either whole or partial), is prohibited unless expressly
authorized. Email communication cannot be guaranteed to be timely secure, error or virus-free. The sender cannot be held responsible for any alteration, errors or omissions, which arise as a result.</p>
<p></p>
<p>..................................................................................................................</p>
<p></p>
<p>La protection de vos données personnelles est primordiale pour notre établissement. Merci de consulter notre
<a href="https://www.sigfox.com/en/privacy-and-cookies-policy">notice sur la protection des données personnelles
</a>pour plus d’informations. Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires. Les informations qui y figurent sont confidentielles. Si vous n'êtes pas le destinataire de ce Message, il
vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support
que ce soit. Veuillez également en avertir immédiatement l'expéditeur par retour du Message. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse.
Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, soient sécurisées ou dénuées de toute erreur ou virus. L'expéditeur ne peut être tenu responsable des modifications, erreurs ou omissions qui pourraient
en résulter.</p>
<p></p>
</body>
</html>