<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Am 22.11.19 um 10:56 schrieb Michael Balzer:<br>
<blockquote type="cite"
cite="mid:31a93b72-7b0b-32e7-8c2b-61789f486558@expeedo.de">
<div class="moz-cite-prefix">Am 22.11.19 um 07:25 schrieb Craig
Leres:<br>
</div>
<blockquote type="cite"
cite="mid:9bd41f57-f5e7-4ef2-42fb-73c90f2928fe@xse.com">
<pre class="moz-quote-pre" wrap="">As I understand it, there is no control over simcom power just control
of an input to simcom that requests that it powers off (or on). So is
the problem that it's possible to wedge the simcom in such a way that it
ignores the control input?
</pre>
</blockquote>
<br>
Most likely.<br>
</blockquote>
<br>
… IF you've verified the modem really ignores the power down signal.<br>
<br>
You cannot do so only by watching the OVMS log, as the UART RX may
also be lost somehow. You need to check the blue LED on the modem
board.<br>
<br>
If it's a UART issue, the OVMS cannot detect any modem response and
will also loop in the power up states.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:822175a5-f5ab-18ce-d1bc-b4216549092c@xse.com">On
2019-11-22 01:56, Michael Balzer wrote:
<br>
<blockquote type="cite">What firmware version do you have on the
SIMCOM?
<br>
</blockquote>
<br>
The one that most recently wedged is... wedged again:
<br>
<br>
OVMS# simcom cmd AT+CGMR
<br>
ERROR: SIMCOM command channel not available!
<br>
</blockquote>
<br>
That may be a MUX state bug, or you may have hit the time between
MUX init and established channels. See simcom::txcmd().<br>
<br>
<br>
<blockquote type="cite"
cite="mid:822175a5-f5ab-18ce-d1bc-b4216549092c@xse.com">
But in a new way, the gps is working and the modem is registered
with the network:
<br>
<br>
PPP: Not connected
<br>
Last Error: User Interrupt
<br>
</blockquote>
<br>
"User Interrupt" triggers me… I had this a few days ago during the
night (with wifi network in use), the module needed a reboot to
recover:<br>
<br>
<blockquote><tt>2019-11-19 04:05:14 CET I (40641522) simcom: PPP
Connection disconnected</tt><br>
<tt>2019-11-19 04:05:15 CET I (40642022) simcom: Lost network
connection (+PPP disconnect in NetMode)</tt><br>
<tt>2019-11-19 04:05:15 CET I (40642022) simcom: State: Enter
NetLoss state</tt><br>
<tt>2019-11-19 04:05:15 CET I (40642032) gsm-ppp: Shutting down
(hard)...</tt><br>
<tt>2019-11-19 04:05:15 CET I (40642032) gsm-ppp: PPP is shutdown</tt><br>
<tt>2019-11-19 04:05:15 CET D (40642062) events:
Signal(system.modem.netloss)</tt><br>
<tt>2019-11-19 04:05:15 CET D (40642102) events:
Signal(system.modem.down)</tt><br>
<tt>2019-11-19 04:05:15 CET I (40642102) netmanager: Set DNS#2
0.0.0.0</tt><br>
<tt>2019-11-19 04:05:15 CET I (40642112) netmanager: MODEM down
(with WIFI client up): staying with WIFI client priority</tt><br>
<tt>2019-11-19 04:05:15 CET D (40642152) events:
Signal(network.modem.down)</tt><br>
<tt>2019-11-19 04:05:15 CET D (40642192) events:
Signal(network.interface.change)</tt><br>
<tt>2019-11-19 04:05:20 CET I (40647522) gsm-ppp: StatusCallBack:
<b>User Interrupt</b></tt><br>
<tt>2019-11-19 04:05:20 CET I (40647522) gsm-ppp: PPP connection
has been closed</tt><br>
<tt>2019-11-19 04:05:20 CET D (40647532) events:
Signal(system.modem.down)</tt><br>
<tt>2019-11-19 04:05:20 CET I (40647532) netmanager: Set DNS#2
0.0.0.0</tt><br>
<tt>2019-11-19 04:05:15 CET I (40651022) simcom: State timeout,
transition to 5</tt><br>
<tt>2019-11-19 04:05:15 CET I (40651022) simcom: State: Enter
NetWait state</tt><br>
<tt>2019-11-19 04:05:15 CET I (40651022) gsm-nmea: Startup</tt><br>
<tt>2019-11-19 04:05:15 CET D (40651092) events:
Signal(system.modem.netwait)</tt><br>
<tt>2019-11-19 04:05:27 CET I (40655022) simcom: State: Enter
NetStart state</tt><br>
<tt>2019-11-19 04:05:27 CET D (40655062) events:
Signal(system.modem.netstart)</tt><br>
<tt>2019-11-19 04:05:56 CET I (40684022) simcom: State timeout,
transition to 14</tt><br>
<tt>2019-11-19 04:05:57 CET I (40684022) simcom: State: Enter
PowerOffOn state</tt><br>
<tt>2019-11-19 04:05:57 CET I (40684022) gsm-ppp: Shutting down
(soft)...</tt><br>
<tt>2019-11-19 04:05:57 CET I (40684022) gsm-ppp: StatusCallBack:
<b>User Interrupt</b></tt><br>
<tt>2019-11-19 04:05:57 CET I (40684022) gsm-ppp: PPP connection
has been closed</tt><br>
<tt>2019-11-19 04:05:57 CET I (40684032) gsm-ppp: PPP is shutdown</tt><br>
<tt>2019-11-19 04:05:57 CET I (40684032) gsm-nmea: Shutdown
(direct)</tt><br>
<tt>2019-11-19 04:05:57 CET I (40684042) gsm-mux: Stop MUX</tt><br>
<tt>2019-11-19 04:05:57 CET I (40684052) simcom: Power Cycle</tt><br>
<tt>2019-11-19 04:05:58 CET D (40685102) events:
Signal(system.modem.down)</tt><br>
<tt>2019-11-19 04:05:58 CET I (40685102) netmanager: Set DNS#2
0.0.0.0</tt><br>
<tt>2019-11-19 04:05:58 CET D (40685142) events:
Signal(system.modem.down)</tt><br>
<tt>2019-11-19 04:05:58 CET I (40685142) netmanager: Set DNS#2
0.0.0.0</tt><br>
<tt>2019-11-19 04:05:58 CET D (40685162) events:
Signal(gps.lock.lost)</tt><br>
<tt>2019-11-19 04:05:58 CET D (40685192) events:
Signal(system.modem.lostgps)</tt><br>
<tt>2019-11-19 04:05:58 CET D (40685222) events:
Signal(system.modem.stop)</tt><br>
<tt>2019-11-19 04:05:58 CET I (40685222) netmanager: Set DNS#2
0.0.0.0</tt><br>
<tt>2019-11-19 04:05:58 CET D (40685262) events:
Signal(egpio.output.0.high)</tt><br>
<tt>2019-11-19 04:05:58 CET D (40685322) events:
Signal(egpio.output.0.low)</tt><br>
<tt>2019-11-19 04:05:59 CET I (40687022) simcom: State timeout,
transition to 2</tt><br>
<tt>2019-11-19 04:06:00 CET I (40687022) simcom: State: Enter
PoweringOn state</tt><br>
<tt>2019-11-19 04:06:00 CET I (40687022) simcom: Power Cycle</tt><br>
<tt>… looping from here in power up until reboot …</tt><br>
</blockquote>
<br>
I haven't found documentation on PPPERR_USER.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:822175a5-f5ab-18ce-d1bc-b4216549092c@xse.com"><br>
Ok, both of the modules I have in cars are 35316B07SIM5360A. My
third module is the one I swapped simcoms in and is
LE11B02SIM7500A (physical label says 7600A).
<br>
<br>
I registered with techship.com and have the firmware update tool.
But the only rar files I see look like they're for the European
SIM5360?
<br>
</blockquote>
<br>
They only seem to have the E version. There are some other
directories on simcom.ee, but no firmware for you it seems.<br>
<br>
Maybe we need to ask SIMCOM to provide updates?<br>
<br>
But it also doesn't look like there's some documented issue with the
modem being stuck ignoring PWRKEY. I'd first look for bugs on our
side.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:822175a5-f5ab-18ce-d1bc-b4216549092c@xse.com">
Tomorrow I'll try to pull my car modules and determine if the
modem boards have the pullup resistor or not.
<br>
<br>
One last thing I'm confused about is the pullup resistor on the
MEM_EN line. I don't see it on v3.1 or v3.2 schematics? I tried to
complare the pdfs from github visually and the only difference I
see is in the A0Z1280CI circuit (and I remember Mark saying they
added a choke to the power supply).
<br>
</blockquote>
<br>
It's on the main board, at the MAX7317.<br>
<br>
Regards,<br>
Michael<br>
<br>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>