<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Regarding the UART frame errors:<br>
<ol>
<li>disabling GPS doesn't change anything</li>
<li>splitting the status poll into two queries doesn't change
anything</li>
<li>issuing a UART HW FIFO reset
(<a class="moz-txt-link-freetext" href="https://github.com/espressif/esp-idf/commit/5404252e803f5489a72119a3ad41b580f2881a2a">https://github.com/espressif/esp-idf/commit/5404252e803f5489a72119a3ad41b580f2881a2a</a>)
doesn't change anything</li>
<li>explicitly setting the mode to standard UART doesn't change
anything<br>
</li>
<li>performing a deep sleep instead of a standard reboot doesn't
change anything</li>
<li>brute force writing a cycle of all 1's and all 0's twice to
the full UART1 register range before driver init doesn't change
anything<br>
</li>
</ol>
<br>
Apparently, the ESP32 UART has some kind of hardware flaw leading to
an ESP32 reset actually not doing a full UART reset.<br>
<br>
<ul>
<li><a class="moz-txt-link-freetext" href="https://www.esp32.com/viewtopic.php?t=4701">https://www.esp32.com/viewtopic.php?t=4701</a></li>
<li><a class="moz-txt-link-freetext" href="https://github.com/espressif/esp-idf/commit/5404252e803f5489a72119a3ad41b580f2881a2a">https://github.com/espressif/esp-idf/commit/5404252e803f5489a72119a3ad41b580f2881a2a</a></li>
<li><a class="moz-txt-link-freetext" href="https://github.com/espressif/esp-idf/commit/f482e9e54ce83e249e46f5ee082f6ffb61431339">https://github.com/espressif/esp-idf/commit/f482e9e54ce83e249e46f5ee082f6ffb61431339</a></li>
<li>…some were lucky with this patch:
<a class="moz-txt-link-freetext" href="https://esp32.com/viewtopic.php?f=2&t=4725">https://esp32.com/viewtopic.php?f=2&t=4725</a> …we are not.</li>
</ul>
<p><br>
</p>
<blockquote type="cite"> //Due to hardware issue, we can not use
fifo_rst to reset uart fifo.<br>
//See description about UART_TXFIFO_RST and UART_RXFIFO_RST in
<<esp32_technical_reference_manual>> v2.6 or later.</blockquote>
<br>
There is apparently no method to perform a full UART HW reset, at
least I haven't found one. It seems this is an issue we cannot fix
(in software).<br>
<br>
But I now don't think this is a new issue, and this also affects
modules quite differently, no idea depending on what circumstances:
on the current run, my car module has lots of FIFO overflows &
quite some MUX framing errors, but not a single UART frame error.<br>
<br>
IOW, I don't think we should let that block the release.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 09.09.22 um 14:23 schrieb Michael
Balzer:<br>
</div>
<blockquote type="cite"
cite="mid:a9d16ded-2b62-a56a-8f15-d1f5dbf133fe@expeedo.de">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
A related issue -- I remember wanting to ask this before: why do
we receive all NMEA sentences three times / on three MUX channels?<br>
<br>
Apparently they come in on channels 1, 3 and 4 -- stumbled across
this again because this now leads to these also being added to a
cellular command response:<br>
<br>
<font face="monospace">OVMS# cell cmd AT+CMUX?<br>
+CMUX: 0,0,5,118,0,0,600<br>
OK<br>
$GPRMC,114516.00,A,xxx.139223,N,xxx.391678,E,0.0,,090922,0.9,W,A*07<br>
$GNGNS,114516.00,xxx.139223,N,xxx.391678,E,AAN,11,1.0,324.4,47.0,,,V*68</font><br>
<br>
<br>
<font face="monospace">V (3388221) gsm-mux: ProcessFrame(CHAN=1,
ADDR=05, CTRL=ff, FCS=bf, LEN=78)<br>
D (3388231) gsm-nmea: Incoming RMC:
$GPRMC,114516.00,A,xxx.139223,N,xxx.391678,E,0.0,,090922,0.9,W,A*07<br>
V (3388231) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=fa, LEN=78)<br>
V (3388231) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f7, LEN=78)<br>
<br>
V (3388241) gsm-mux: ProcessFrame(CHAN=1, ADDR=05, CTRL=ff,
FCS=b1, LEN=82)<br>
D (3388241) gsm-nmea: Incoming GNS:
$GNGNS,114516.00,xxx.139223,N,xxx.391678,E,AAN,11,1.0,324.4,47.0,,,V*68<br>
V (3388251) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=f4, LEN=82)<br>
V (3388261) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f9, LEN=82)<br>
<br>
V (3393221) gsm-mux: ProcessFrame(CHAN=1, ADDR=05, CTRL=ff,
FCS=bf, LEN=78)<br>
D (3393231) gsm-nmea: Incoming RMC:
$GPRMC,114521.00,A,xxx.139223,N,xxx.391676,E,0.0,,090922,0.9,W,A*0D<br>
V (3393231) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=fa, LEN=78)<br>
V (3393231) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f7, LEN=78)<br>
<br>
V (3393241) gsm-mux: ProcessFrame(CHAN=1, ADDR=05, CTRL=ff,
FCS=b1, LEN=82)<br>
D (3393241) gsm-nmea: Incoming GNS:
$GNGNS,114521.00,xxx.139223,N,xxx.391676,E,AAN,11,1.0,324.4,47.0,,,V*62<br>
V (3393251) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=f4, LEN=82)<br>
V (3393261) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f9, LEN=82)<br>
<br>
</font><br>
This also produces a lot of unnecessary stress on the ESP's RX
buffer, doesn't it?<br>
<br>
Channel 1 is the dedicated NMEA channel, 3 is POLL and 4 is CMD. I
don't see why channels 3 & 4 are used for these by the modem,
but I also cannot find any command meant to configure this.<br>
<br>
Any idea on this?<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">Am 09.09.22 um 13:14 schrieb Michael
Balzer:<br>
</div>
<blockquote type="cite"
cite="mid:8939480a-6502-acb5-a758-d6ae90c66712@expeedo.de">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
Mark,<br>
<br>
(am I the only one experiencing this?)<br>
<br>
I've had multiple times of temporarily frozen modem
communication over the last days on my car module. That's new,
so I think we should try to fix that before releasing.<br>
<br>
On my bench module there's a clear correlation between the
extended status query and the frame errors. It's also not
related to the NMEA messages, I've checked that, they come at
another second.<br>
<br>
Log excerpts below.<br>
<br>
With frame errors responses also occasionally get corrupted,
e.g.<br>
<font face="monospace">D (204251) cellular: mux-rx-line #3:
Hologram",7</font><br>
<br>
I think the extended status responses now very often cause an
overflow on the RX buffer when coming in together. Solution
could be to split the queries and distribute over 2-3 seconds.<br>
<br>
I don't know if that will also fix the strange cold/warm boot
difference with this, but maybe that's simply because the modem
is faster with getting back to the network after a reboot, so
the status responses become large quickly.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<font face="monospace">D (204211) cellular: mux-tx #3:
AT+CREG?;+CGREG?;+CEREG?;+CCLK?;+CSQ;+CPSI?;+COPS?<br>
W (204251) gsm-mux: Frame error: EOF mismatch (CHAN=55,
ADDR=df, CTRL=ff, FCS=35, LEN=133)<br>
V (204251) gsm-mux: Frame dump: f9 df ff ff bf bf dd ff f9 0d
ff af 0d 0a 2b 43 | ..............+C<br>
V (204251) gsm-mux: Frame dump: 50 53 49 3a 20 4c 54 45 2c 4f
6e 6c 69 6e 65 2c | PSI: LTE,Online,<br>
V (204251) gsm-mux: Frame dump: 32 36 32 2d 30 32 2c 30 78 42
30 46 35 2c 31 33 | 262-02,0xB0F5,13<br>
V (204251) gsm-mux: Frame dump: 31 37 39 34 31 32 2c 34 34 38
2c 45 55 54 52 41 | 179412,448,EUTRA<br>
V (204251) gsm-mux: Frame dump: 4e 2d 42 41 4e 44 31 2c 31 30
30 2c 34 2c 34 2c | N-BAND1,100,4,4,<br>
V (204251) gsm-mux: Frame dump: 2d 39 32 2c 2d 31 31 35 32 2c
2d 38 37 35 2c 31 | -92,-1152,-875,1<br>
V (204251) gsm-mux: Frame dump: 34 0d 0a 34 f9 f9 0d ff ed 0d
0a 2b 43 52 45 47 | 4..4.......+CREG<br>
V (204251) gsm-mux: Frame dump: 3a 20 31 2c 35 0d 0a 0d 0a 2b
43 47 52 45 47 3a | : 1,5....+CGREG:<br>
V (204251) gsm-mux: Frame dump: 20 31 2c 35
0d | 1,5. <br>
V (204251) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=da, LEN=25)<br>
D (204251) cellular: mux-rx-line #3: Hologram",7<br>
V (208231) gsm-mux: ProcessFrame(CHAN=1, ADDR=05, CTRL=ff,
FCS=bf, LEN=78)<br>
V (208241) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=fa, LEN=78)<br>
V (208251) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f7, LEN=78)<br>
V (208251) gsm-mux: ProcessFrame(CHAN=1, ADDR=05, CTRL=ff,
FCS=b1, LEN=82)<br>
V (208271) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=f4, LEN=82)<br>
<br>
…<br>
<br>
V (233271) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=f4, LEN=82)<br>
V (233271) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f9, LEN=82)<br>
D (234211) cellular: mux-tx #3:
AT+CREG?;+CGREG?;+CEREG?;+CCLK?;+CSQ;+CPSI?;+COPS?<br>
W (234211) cellular: UART frame error<br>
W (234211) cellular: UART frame error<br>
W (234211) cellular: UART frame error<br>
W (234211) cellular: UART frame error<br>
W (234231) gsm-mux: Frame error: EOF mismatch (CHAN=63,
ADDR=ff, CTRL=ea, FCS=2c, LEN=53)<br>
V (234231) gsm-mux: Frame dump: f9 ff ea 5f ff b7 ff fd ff b9
df fd bf f9 ff fd | ..._............<br>
V (234231) gsm-mux: Frame dump: fb ff f9 f9 a9 f9 0d ff af 0d
0a 2b 43 50 53 49 | ...........+CPSI<br>
V (234231) gsm-mux: Frame dump: 3a 20 4c 54 45 2c 4f 6e 6c 69
6e 65 2c 32 36 32 | : LTE,Online,262<br>
V (234231) gsm-mux: Frame dump: 2d 30 32 2c
30 | -02,0 <br>
V (234241) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=a7, LEN=124)<br>
D (234241) cellular: mux-rx-line #3: +CREG: 1,5<br>
D (234241) cellular: mux-rx-line #3: +CGREG: 1,5<br>
D (234241) cellular: mux-rx-line #3: +CEREG: 1,5<br>
D (234241) cellular: mux-rx-line #3: +CCLK:
"22/09/09,12:52:41+08"<br>
D (234241) cellular: mux-rx-line #3: +CSQ: 13,99<br>
V (234241) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=da, LEN=25)<br>
D (234251) cellular: mux-rx-line #3: +COPS: 0,0,"vodafone.de
Hologram",7<br>
V (238231) gsm-mux: ProcessFrame(CHAN=1, ADDR=05, CTRL=ff,
FCS=bf, LEN=78)<br>
V (238241) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=fa, LEN=78)<br>
<br>
…<br>
<br>
V (293251) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f7, LEN=78)<br>
V (293251) gsm-mux: ProcessFrame(CHAN=1, ADDR=05, CTRL=ff,
FCS=b1, LEN=82)<br>
V (293271) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=f4, LEN=82)<br>
V (293271) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f9, LEN=82)<br>
D (294211) cellular: mux-tx #3:
AT+CREG?;+CGREG?;+CEREG?;+CCLK?;+CSQ;+CPSI?;+COPS?<br>
W (294211) cellular: UART frame error<br>
W (294211) cellular: UART frame error<br>
W (294211) cellular: UART frame error<br>
W (294241) gsm-mux: Frame error: EOF mismatch (CHAN=59,
ADDR=ef, CTRL=db, FCS=2b, LEN=117)<br>
V (294241) gsm-mux: Frame dump: f9 ef db df ef df f7 cb f9 ff
ff db 7f fd ff ff | ................<br>
V (294241) gsm-mux: Frame dump: f9 0d ff af 0d 0a 2b 43 50 53
49 3a 20 4c 54 45 | ......+CPSI: LTE<br>
V (294241) gsm-mux: Frame dump: 2c 4f 6e 6c 69 6e 65 2c 32 36
32 2d 30 32 2c 30 | ,Online,262-02,0<br>
V (294241) gsm-mux: Frame dump: 78 42 30 46 35 2c 31 33 31 37
39 34 31 32 2c 34 | xB0F5,13179412,4<br>
V (294241) gsm-mux: Frame dump: 34 38 2c 45 55 54 52 41 4e 2d
42 41 4e 44 31 2c | 48,EUTRAN-BAND1,<br>
V (294241) gsm-mux: Frame dump: 31 30 30 2c 34 2c 34 2c 2d 39
36 2c 2d 31 31 35 | 100,4,4,-96,-115<br>
V (294241) gsm-mux: Frame dump: 35 2c 2d 38 37 33 2c 31 34 0d
0a 34 f9 f9 0d ff | 5,-873,14..4....<br>
V (294241) gsm-mux: Frame dump: ed 0d 0a 2b
43 | ...+C <br>
V (294251) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=da, LEN=25)<br>
D (294251) cellular: mux-rx-line #3: Hologram",7<br>
V (298231) gsm-mux: ProcessFrame(CHAN=1, ADDR=05, CTRL=ff,
FCS=bf, LEN=78)<br>
V (298241) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=fa, LEN=78)<br>
V (298241) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f7, LEN=78)<br>
V (298251) gsm-mux: ProcessFrame(CHAN=1, ADDR=05, CTRL=ff,
FCS=b1, LEN=82)<br>
V (298261) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=f4, LEN=82)<br>
V (298271) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f9, LEN=82)<br>
<br>
…<br>
<br>
V (323251) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f7, LEN=78)<br>
V (323261) gsm-mux: ProcessFrame(CHAN=1, ADDR=05, CTRL=ff,
FCS=b1, LEN=82)<br>
V (323271) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=f4, LEN=82)<br>
V (323271) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f9, LEN=82)<br>
D (324211) cellular: mux-tx #3:
AT+CREG?;+CGREG?;+CEREG?;+CCLK?;+CSQ;+CPSI?;+COPS?<br>
W (324231) gsm-mux: Frame error: EOF mismatch (CHAN=29,
ADDR=77, CTRL=fb, FCS=45, LEN=125)<br>
V (324231) gsm-mux: Frame dump: f9 77 fb ef 5f ff bb ed fb bb
db ff b7 fb cf ff | .w.._...........<br>
V (324231) gsm-mux: Frame dump: bf d9 ff bb f9 0d ff b1 0d 0a
2b 43 50 53 49 3a | ..........+CPSI:<br>
V (324231) gsm-mux: Frame dump: 20 4c 54 45 2c 4f 6e 6c 69 6e
65 2c 32 36 32 2d | LTE,Online,262-<br>
V (324231) gsm-mux: Frame dump: 30 32 2c 30 78 42 30 46 35 2c
31 33 31 37 39 34 | 02,0xB0F5,131794<br>
V (324231) gsm-mux: Frame dump: 31 32 2c 34 34 38 2c 45 55 54
52 41 4e 2d 42 41 | 12,448,EUTRAN-BA<br>
V (324241) gsm-mux: Frame dump: 4e 44 31 2c 31 30 30 2c 34 2c
34 2c 2d 31 30 39 | ND1,100,4,4,-109<br>
V (324241) gsm-mux: Frame dump: 2c 2d 31 31 36 36 2c 2d 38 37
34 2c 31 31 0d 0a | ,-1166,-874,11..<br>
V (324241) gsm-mux: Frame dump: c2 f9 f9 0d ff ed 0d 0a 2b 43
52 45 47 | ........+CREG <br>
V (324241) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=da, LEN=25)<br>
D (324241) cellular: mux-rx-line #3: Hologram",7<br>
V (328231) gsm-mux: ProcessFrame(CHAN=1, ADDR=05, CTRL=ff,
FCS=bf, LEN=78)<br>
V (328241) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=fa, LEN=78)<br>
V (328251) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f7, LEN=78)<br>
<br>
…<br>
<br>
V (353251) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f7, LEN=78)<br>
V (353251) gsm-mux: ProcessFrame(CHAN=1, ADDR=05, CTRL=ff,
FCS=b1, LEN=82)<br>
V (353271) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=f4, LEN=82)<br>
V (353271) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f9, LEN=82)<br>
D (354211) cellular: mux-tx #3:
AT+CREG?;+CGREG?;+CEREG?;+CCLK?;+CSQ;+CPSI?;+COPS?<br>
W (354211) cellular: UART frame error<br>
W (354211) cellular: UART frame error<br>
W (354211) cellular: UART frame error<br>
W (354211) cellular: UART frame error<br>
V (354231) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=34, LEN=93)<br>
D (354231) cellular: mux-rx-line #3: +CPSI:
LTE,Online,262-02,0xB0F5,13179412,448,EUTRAN-BAND1,100,4,4,-122,-1184,-874,9<br>
V (354241) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=a7, LEN=124)<br>
D (354241) cellular: mux-rx-line #3: +CREG: 1,5<br>
D (354241) cellular: mux-rx-line #3: +CGREG: 1,5<br>
D (354241) cellular: mux-rx-line #3: +CEREG: 1,5<br>
D (354241) cellular: mux-rx-line #3: +CCLK:
"22/09/09,12:54:41+08"<br>
D (354251) cellular: mux-rx-line #3: +CSQ: 13,99<br>
V (354251) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=da, LEN=25)<br>
D (354251) cellular: mux-rx-line #3: +COPS: 0,0,"vodafone.de
Hologram",7<br>
V (358231) gsm-mux: ProcessFrame(CHAN=1, ADDR=05, CTRL=ff,
FCS=bf, LEN=78)<br>
V (358241) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff,
FCS=fa, LEN=78)<br>
V (358251) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff,
FCS=f7, LEN=78)<br>
<br>
</font><br>
<br>
<br>
<br>
<div class="moz-cite-prefix">Am 08.09.22 um 07:15 schrieb Mark
Webb-Johnson:<br>
</div>
<blockquote type="cite"
cite="mid:2FD58BC2-63CE-4DD6-83FA-E5404B1946BF@webb-johnson.net">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
Michael,
<div class=""><br class="">
</div>
<div class="">I reviewed:</div>
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding:
0px;" class="">
<div class="">$ git diff
2b25287fbef5fa968236cb8e556ea11da7c8f579
components/ovms_cellular components/simcom</div>
</blockquote>
<div class="">
<div><br class="">
</div>
<div>But can’t see anything really related to frame errors,
other than the two extra CGREG and CEREG output lines once
every thirty seconds.</div>
<div><br class="">
</div>
<div>Maybe an existing issue re-occurring?</div>
<div><br class="">
</div>
<div>Do you think this should block our release of 3.3.003
to ‘main’ release?</div>
<div><br class="">
</div>
<div>Regards, Mark.</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 4 Sep 2022, at 4:17 PM, Michael Balzer
<<a href="mailto:dexter@expeedo.de"
class="moz-txt-link-freetext" moz-do-not-send="true">dexter@expeedo.de</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="content-isolator__container">
<div class="protected-part">
<div class="protected-title">Signed PGP part</div>
<div class="protected-content">
<meta http-equiv="Content-Type"
content="text/html; charset=UTF-8" class="">
<div class=""> I'm seeing an issue with the
current build, but not sure if that's new
& related to the latest changes or just
coincidentally has become more severe somehow:<br
class="">
<br class="">
On a cold boot, modem communication is mostly
fine, nearly no UART frame errors, and
messages received by the modem are fine.<br
class="">
<br class="">
After the first warm reboot, initial modem
messages are garbled, and lots of UART frame
errors occur right from the beginning of modem
communication.<br class="">
<br class="">
This looks like some part of the serial
communication now doesn't get fully reset on a
reboot. Log attached.<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Am 03.09.22 um
11:37 schrieb Michael Balzer:<br class="">
</div>
<blockquote type="cite"
cite="mid:2b006739-ebbb-267f-d858-d5941d1d555f@expeedo.de"
class="">
<meta http-equiv="Content-Type"
content="text/html; charset=UTF-8"
class="">
EAP release also done on <a
href="http://ovms.dexters-web.de" class=""
moz-do-not-send="true">ovms.dexters-web.de</a>.<br
class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Am 01.09.22 um
02:53 schrieb Mark Webb-Johnson:<br
class="">
</div>
<blockquote type="cite"
cite="mid:8E0F25CA-0E64-437E-9730-C51728905311@webb-johnson.net"
class="">
<meta http-equiv="Content-Type"
content="text/html; charset=UTF-8"
class="">
Sounds good. I think this is important
enough to make a formal release so I will
arrange that.
<div class=""><br class="">
</div>
<div class="">I have made a 3.3.003, and
released to EAP on <a
href="http://api.openvehicles.com/"
class="" moz-do-not-send="true">api.openvehicles.com</a>.
We can <span style="caret-color: rgb(0,
0, 0);" class="">target a main release
for next week.</span></div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark.</div>
<div class="">
<div class=""><br class="">
</div>
<div class="">P.S. <span
style="caret-color: rgb(0, 0, 0);"
class="">I have a bunch of unrelated
enhancements to CAN logging to
commit, but those can wait.</span></div>
<div class=""><font class=""><span
style="caret-color: rgb(0, 0, 0);"
class=""><br class="">
</span></font>
<blockquote type="cite" class="">
<div class="">On 31 Aug 2022, at
10:27 PM, Michael Balzer <<a
href="mailto:dexter@expeedo.de"
class="moz-txt-link-freetext"
moz-do-not-send="true">dexter@expeedo.de</a>>
wrote:</div>
<br
class="Apple-interchange-newline">
<div class="">
<div class="">
<div
class="content-isolator__container">
<div class="protected-part">
<div class="protected-title">Signed
PGP part</div>
<div
class="protected-content">Looks
good:<br class="">
<br class="">
Model: SIMCOM_SIM7600G<br
class="">
Revision:
SIM7600M21-A_V2.0<br
class="">
D (80128) cellular: mux-tx
#3:
AT+CREG?;+CGREG?;+CEREG?;+CCLK?;+CSQ;+CPSI?;+COPS?<br class="">
D (80158) cellular:
mux-rx-line #3: +CPSI:
LTE,Online,262-02,0xB0F5,12829697,303,EUTRAN-BAND20,6300,3,3,-93,-969,-701,17<br
class="">
D (80168) cellular:
mux-rx-line #3: +CREG: 1,5<br
class="">
D (80168) cellular:
mux-rx-line #3: +CGREG:
1,5<br class="">
D (80168) cellular:
mux-rx-line #3: +CEREG:
1,5<br class="">
D (80168) cellular:
mux-rx-line #3: +CCLK:
"22/08/31,11:15:03+08"<br
class="">
D (80168) cellular:
mux-rx-line #3: +CSQ:
21,99<br class="">
D (80168) cellular:
mux-rx-line #3: +COPS:
0,0,"<a
href="http://vodafone.de/"
class=""
moz-do-not-send="true">vodafone.de</a>
Hologram",7<br class="">
<br class="">
Model: SIMCOM_SIM5360E<br
class="">
Revision: SIM5360E_V3.5<br
class="">
D (74307) cellular: mux-tx
#3:
AT+CREG?;+CCLK?;+CSQ;+CPSI?;+COPS?<br class="">
D (74327) cellular:
mux-rx-line #3: +CPSI:
GSM,Online,262-02,0x011f,14822,4
EGSM 900,-69,0,38-38<br
class="">
D (74337) cellular:
mux-rx-line #3: +CREG: 1,5<br
class="">
D (74337) cellular:
mux-rx-line #3: +CCLK:
"22/08/31,11:19:47+08"<br
class="">
D (74337) cellular:
mux-rx-line #3: +CSQ:
22,99<br class="">
D (74337) cellular:
mux-rx-line #3: +COPS:
0,0,"<a
href="http://vodafone.de/"
class=""
moz-do-not-send="true">vodafone.de</a>
Hologram",0<br class="">
<br class="">
Model: SIMCOM_SIM7600G<br
class="">
Revision:
SIM7600M21-A_V2.0.1<br
class="">
D (324279) cellular:
mux-tx #3:
AT+CREG?;+CGREG?;+CEREG?;+CCLK?;+CSQ;+CPSI?;+COPS?<br
class="">
D (324309) cellular:
mux-rx-line #3: +CPSI:
LTE,Online,262-01,0x34B9,29268996,36,EUTRAN-BAND3,1444,3,3,-147,-1213,-889,8<br
class="">
D (324319) cellular:
mux-rx-line #3: +CREG: 1,1<br
class="">
D (324319) cellular:
mux-rx-line #3: +CGREG:
1,1<br class="">
D (324319) cellular:
mux-rx-line #3: +CEREG:
1,1<br class="">
D (324319) cellular:
mux-rx-line #3: +CCLK:
"22/08/31,12:22:05+08"<br
class="">
D (324319) cellular:
mux-rx-line #3: +CSQ:
11,99<br class="">
D (324319) cellular:
mux-rx-line #3: +COPS:
0,0," congstar",7<br
class="">
<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
Am 31.08.22 um 10:41
schrieb Mark Webb-Johnson:<br
class="">
<blockquote type="cite"
class="">I’ve made some
further revisions. Now
in latest edge -49
release.<br class="">
<br class="">
Grateful for feedback on
this, please.
Particularly with
SIM5360 (which should be
unaffected, but …).<br
class="">
<br class="">
Regards, Mark.<br
class="">
<br class="">
<blockquote type="cite"
class="">On 26 Aug
2022, at 10:17 PM,
Michael Balzer<<a
href="mailto:dexter@expeedo.de"
class="moz-txt-link-freetext" moz-do-not-send="true">dexter@expeedo.de</a>>
wrote:<br class="">
<br class="">
Signed PGP part<br
class="">
From testing on my
three modules here in
Germany, looks good:<br
class="">
<br class="">
Model: SIMCOM_SIM7600G<br
class="">
Revision:
SIM7600M21-A_V2.0<br
class="">
D (151128) cellular:
mux-tx #3:
AT+CREG?;+CGREG?;+CEREG?;+CCLK?;+CSQ;+CPSI?;+COPS?<br
class="">
D (151158) cellular:
mux-rx-line #3: +CPSI:
LTE,Online,262-02,0xB0F5,13179412,448,EUTRAN-BAND1,100,4,4,-93,-1141,-864,14<br
class="">
D (151168) cellular:
mux-rx-line #3: +CREG:
1,5<br class="">
D (151168) cellular:
mux-rx-line #3:
+CGREG: 1,5<br
class="">
D (151168) cellular:
mux-rx-line #3:
+CEREG: 1,5<br
class="">
D (151168) cellular:
mux-rx-line #3: +CCLK:
"22/08/26,09:13:51+08"<br
class="">
D (151168) cellular:
mux-rx-line #3: +CSQ:
13,99<br class="">
D (151168) cellular:
mux-rx-line #3: +COPS:
0,0,"<a
href="http://vodafone.de/"
class=""
moz-do-not-send="true">vodafone.de</a>
Hologram",7<br
class="">
<br class="">
Model: SIMCOM_SIM5360E<br
class="">
Revision:
SIM5360E_V3.5<br
class="">
D (143784) cellular:
mux-tx #3:
AT+CREG?;+CCLK?;+CSQ;+CPSI?;+COPS?<br
class="">
D (143804) cellular:
mux-rx-line #3: +CPSI:
GSM,Online,262-02,0x011f,14822,4 EGSM 900,-66,0,41-41<br class="">
D (143814) cellular:
mux-rx-line #3: +CREG:
1,5<br class="">
D (143814) cellular:
mux-rx-line #3: +CCLK:
"22/08/26,09:24:20+08"<br
class="">
D (143814) cellular:
mux-rx-line #3: +CSQ:
23,99<br class="">
D (143814) cellular:
mux-rx-line #3: +COPS:
0,0,"<a
href="http://vodafone.de/"
class=""
moz-do-not-send="true">vodafone.de</a>
Hologram",0<br
class="">
<br class="">
Model: SIMCOM_SIM7600G<br
class="">
Revision:
SIM7600M21-A_V2.0.1<br
class="">
D (9625359) cellular:
mux-tx #3:
AT+CREG?;+CGREG?;+CEREG?;+CCLK?;+CSQ;+CPSI?;+COPS?<br
class="">
D (9625389) cellular:
mux-rx-line #3: +CPSI:
LTE,Online,262-01,0x34B9,29268999,268,EUTRAN-BAND8,3749,2,2,-112,-1042,-791,15<br
class="">
D (9625399) cellular:
mux-rx-line #3: +CREG:
1,1<br class="">
D (9625399) cellular:
mux-rx-line #3:
+CGREG: 1,1<br
class="">
D (9625399) cellular:
mux-rx-line #3:
+CEREG: 1,1<br
class="">
D (9625399) cellular:
mux-rx-line #3: +CCLK:
"22/08/26,12:40:14+08"<br
class="">
D (9625399) cellular:
mux-rx-line #3: +CSQ:
15,99<br class="">
D (9625399) cellular:
mux-rx-line #3: +COPS:
0,0," congstar",7<br
class="">
<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
Am 26.08.22 um 08:53
schrieb Mark
Webb-Johnson:<br
class="">
<blockquote
type="cite" class="">Thanks.<br
class="">
<br class="">
I think anyone in
USA using Hologram
on T-Mobile would
benefit from this. I
just worry I break
something else.<br
class="">
<br class="">
Regards, Mark.<br
class="">
<br class="">
<blockquote
type="cite"
class="">On 26 Aug
2022, at 2:46 PM,
Craig Leres<<a
href="mailto:leres@xse.com" class="moz-txt-link-freetext"
moz-do-not-send="true">leres@xse.com</a>>
wrote:<br
class="">
<br class="">
<br class="">
On 8/25/22 23:34,
Mark Webb-Johnson
wrote:<br class="">
<blockquote
type="cite"
class="">I’ve
been fighting a
problem for the
past few months
with
registration
getting denied
on T-Mobile in
USA using
Hologram and our
new 4G SIM7600G
modem. Without
cellular
connectivity at
home, it hasn’t
been easy to
recreate this,
but I found a
solution:<br
class="">
</blockquote>
I've been seeing
intermittent
netreg errors
lately; I've
booted this
version on a
couple of my
modules...<br
class="">
<br class="">
<span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>Craig<br
class="">
</blockquote>
_______________________________________________<br class="">
OvmsDev mailing list<br
class="">
<a
href="mailto:OvmsDev@lists.openvehicles.com"
class="moz-txt-link-freetext" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br
class="">
<a
class="moz-txt-link-freetext"
href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev"
moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br
class="">
</blockquote>
--<br class="">
Michael Balzer *
Helkenberger Weg 9 *
D-58256 Ennepetal<br
class="">
Fon 02333 / 833 5735 *
Handy 0176 / 206 989
26<br class="">
<br class="">
<br class="">
<br class="">
</blockquote>
<br class="">
_______________________________________________<br class="">
OvmsDev mailing list<br
class="">
<a
href="mailto:OvmsDev@lists.openvehicles.com"
class="moz-txt-link-freetext" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br
class="">
<a
class="moz-txt-link-freetext"
href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev"
moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br
class="">
</blockquote>
<br class="">
-- <br class="">
Michael Balzer *
Helkenberger Weg 9 *
D-58256 Ennepetal<br
class="">
Fon 02333 / 833 5735 *
Handy 0176 / 206 989 26<br
class="">
<br class="">
</div>
</div>
<br class="">
<iframe
class="content-isolator__isolated-content"
sandbox="allow-scripts"
scrolling="auto"
style="border:none;display:block;overflow:auto;"
data-src="data:text/html;charset=UTF-8;base64,PGlmcmFtZS1jb250ZW50IGRhdGEtaWZyYW1lLWhlaWdodD0idHJ1ZSI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188QlI+T3Ztc0RldiBtYWlsaW5nIGxpc3Q8QlI+T3Ztc0RldkBsaXN0cy5vcGVudmVoaWNsZXMuY29tPEJSPmh0dHA6Ly9saXN0cy5vcGVudmVoaWNsZXMuY29tL21haWxtYW4vbGlzdGluZm8vb3Ztc2RldjxCUj48L2lmcmFtZS1jb250ZW50Pg=="
width="200" height="10"></iframe></div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
<br class="">
<fieldset
class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br class="">
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
<br class="">
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br class="">
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
</div>
<span
id="cid:0B507B8A-6B06-4EFA-A9DB-809432A7D035"><220904-UART-frame-errors.txt></span></div>
</div>
<br class="">
<iframe class="content-isolator__isolated-content"
sandbox="allow-scripts" scrolling="auto"
style="border:none;display:block;overflow:auto;"
data-src="data:text/html;charset=UTF-8;base64,PGlmcmFtZS1jb250ZW50IGRhdGEtaWZyYW1lLWhlaWdodD0idHJ1ZSI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188QlI+T3Ztc0RldiBtYWlsaW5nIGxpc3Q8QlI+T3Ztc0RldkBsaXN0cy5vcGVudmVoaWNsZXMuY29tPEJSPmh0dHA6Ly9saXN0cy5vcGVudmVoaWNsZXMuY29tL21haWxtYW4vbGlzdGluZm8vb3Ztc2RldjxCUj48L2lmcmFtZS1jb250ZW50Pg=="
width="200" height="10"></iframe></div>
</div>
</blockquote>
</div>
<br class="">
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
</body>
</html>