[Ovmsdev] v3 hardware disconnecting from v2 server

[Tom Parker]

On 06/02/18 12:42, Tom Parker wrote:

> It feels like the simcom state machine has a bug where it thinks that 
> it is connected but actually it isn't, so it never reconnects. This 
> bug appears to persist over simcom power cycles. I've now got verbose 
> logging turned on and I've removed modemmanager on my data logging 
> laptop so hopefully I'll have some more information about the cause.

Attached is another log file. Here the server v2 code and the simcom 
noticed that it was disconnected which I haven't seen before, but the 
simcom never reconnected.

See the attached file for the earlier and later messages, the 
AT+CREG?... loop quoted below went on for about 15 minutes without 
reconnecting, and doing a power simcom off followed by on did not make 
it reconnect. Pressing the button made it connect straight away. I 
believe I was stationary when power cycling and then resetting the whole 
module.

Why is "simcom: rx line" not always sometimes printed? If you look 
further back and forward in the log you'll see it decoding most of the 
AT command responses. Is this the simcom response parser? It looks like 
the AT+CREG?... are being sent but sometimes the results aren't be 
interpreted, so the simcom code doesn't know it is connected?

+CSQ: 1,99 suggests there is very low signal? That might explain the 
disconnections. My antenna is poor (a wifi rubber ducky with an RP-SMA 
adapter, I could switch to a proper antenna too but then my problem 
might go away and we wouldn't be able to collect debug information). 
After the reboot the signal quality was only +CSQ: 2,99 and it 
reconnected fine.

OVMS > V (4235393) simcom: tx: f9 0d ff 3b 41 54 2b 43 52 45 47 3f 3b 2b 
43 43 | ...;AT+CREG?;+CC
V (4235393) simcom: tx: 4c 4b 3f 3b 2b 43 53 51 3b 2b 43 4f 50 53 3f 0d 
| LK?;+CSQ;+COPS?.
V (4235393) simcom: tx: 0a cf f9                                        
| ...
V (4235403) simcom: rx: 41 54 2b 43 52 45 47 3f 3b 2b 43 43 4c 4b 3f 3b 
| AT+CREG?;+CCLK?;
V (4235403) simcom: rx: 2b 43 53 51 3b 2b 43 4f 50 53 3f 0d             
| +CSQ;+COPS?.
V (4235413) simcom: rx: 0d 0a 2b 43 52 45 47 3a 20 30 2c 31 0d 0a 0d 0a 
| ..+CREG: 0,1....
V (4235413) simcom: rx: 2b 43 43 4c 4b 3a 20 22 31 38 2f 30 32 2f 30 39 
| +CCLK: "18/02/09
V (4235413) simcom: rx: 2c 31 38 3a 31 35 3a 33 30 2b 35 32 22 0d 0a 0d 
| ,18:15:30+52"...
V (4235413) simcom: rx: 0a 2b 43 53 51 3a 20 30 2c 39 39 0d 0a 0d 0a 2b 
| .+CSQ: 0,99....+
V (4235413) simcom: rx: 43 4f 50 53 3a 20 30 2c 30 2c 22 32 64 65 67 72 
| COPS: 0,0,"2degr
V (4235413) simcom: rx: 65 65 73 22 2c 32 0d 0a 0d 0a 4f 4b 0d 0a       
| ees",2....OK..
OVMS > simcom statusV (4245393) simcom: tx: f9 0d ff 3b 41 54 2b 43 52 
45 47 3f 3b 2b 43 43 | ...;AT+CREG?;+CC
V (4245393) simcom: tx: 4c 4b 3f 3b 2b 43 53 51 3b 2b 43 4f 50 53 3f 0d 
| LK?;+CSQ;+COPS?.
V (4245393) simcom: tx: 0a cf f9                                        
| ...
V (4245423) simcom: rx: 41 54 2b 43 52 45 47 3f 3b 2b 43 43 4c 4b 3f 3b 
| AT+CREG?;+CCLK?;
V (4245423) simcom: rx: 2b 43 53 51 3b 2b 43 4f 50 53 3f 0d             
| +CSQ;+COPS?.
V (4245463) simcom: rx: 0d 0a 2b 43 52 45 47 3a 20 30 2c 31 0d 0a 0d 0a 
| ..+CREG: 0,1....
V (4245463) simcom: rx: 2b 43 43 4c 4b 3a 20 22 31 38 2f 30 32 2f 30 39 
| +CCLK: "18/02/09
V (4245463) simcom: rx: 2c 31 38 3a 31 35 3a 34 30 2b 35 32 22 0d 0a 0d 
| ,18:15:40+52"...
V (4245473) simcom: rx: 0a 2b 43 53 51 3a 20 31 2c 39 39 0d 0a 0d 0a 2b 
| .+CSQ: 1,99....+
V (4245473) simcom: rx: 43 4f 50 53 3a 20 30 2c 30 2c 22 32 64 65 67 72 
| COPS: 0,0,"2degr
V (4245473) simcom: rx: 65 65 73 22 2c 32 0d 0a 0d 0a 4f 4b 0d 0a       
| ees",2....OK..
OVMS > simcom status
SIMCOM
   Network Registration: Searching
   State: NetWait
   Ticker: 1570
   User Data: 0
   Mux Open Channels: 4
   PPP Not Connected
   PPP Last Error: User Interrupt
   GPS: disabled
   GPS time: disabled
   NMEA (GPS/GLONASS) Not Connected
OVMS > server v2 status
Error: Disconnected from OVMS Server V2

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ovms_2018-02-09T03_56_08+0000.log.bz2
Type: application/x-bzip
Size: 147523 bytes
Desc: not available
URL: <http://lists.teslaclub.hk/pipermail/ovmsdev/attachments/20180212/e17cbc33/attachment-0001.bin>