[Ovmsdev] SIMCOM PPP

Tue Nov 14 22:10:03 HKT 2017

I managed to repeat this using a phone hotspot that I could turn on/off, server v2 start, and wifi mode client. Strange that it didn’t crash on the first stop/start cycle, but on the second.

I’ve pushed a patch to enable the Web Server and MDNS Service to be disabled via menuconfig. Could you try:

Component / OVMS / Component / Web Server -> Disable
Component / OVMS / Component / MDNS -> Disable
Edit main/console_telnet.cpp and comment-out the AddClient in WifiUp(), and DeleteChildren in WifiDown()

I’m not 100% sure where the problem is (it could be a component, or it could be a memory/stack issue), but let’s try to narrow down the issue by disabling those first.

With telnet, MDNS, and WebServer disabled, the only network service should be ovms_server_v2.

See if you can then recreate the problem?

For me:

Disabling MDNS didn’t solve the problem
Disabling MDNS+WebServer didn’t solve the problem
Disabling MDNS+WebServer+Telnet DID solve the problem

With just wifi + ovms_server_v2, it seems more stable for me. Can you try, and let me know?

Regards, Mark.

> On 14 Nov 2017, at 5:59 PM, Tom Parker <tom at carrott.org> wrote:
> 
> On 06/11/17 01:48, Michael Balzer wrote:
>> Works in Germany with Hologram & roaming via Telekom.de:
> 
> I found the Hologram sim works in New Zealand via Vodafone, but the modem doesn't seem to healthy. Most of the time the OVMS doesn't successfully establish communication with the modem. I can see that the modem has 3.3V between pin 1 and pin 28, and pin 15 is being toggled during the power cycle, but it only gets to 2.8V. Most of the time I get the following over and over in the logs.
> 
> I (75539) simcom: State timeout, transition to 2
> I (75539) simcom: State: Enter PoweringOn state
> I (75539) simcom: Power Cycle
> D (76539) SIMCOM tx: 41 54 0d 0a AT..
> ...
> D (85539) SIMCOM tx: 41 54 0d 0a AT..
> I (85539) simcom: State timeout, transition to 2
> I (85539) simcom: State: Enter PoweringOn state
> I (85539) simcom: Power Cycle
> 
> It seems to work rarely and randomly, or maybe I have a bad connection in my board? How would I go about diagnosing this?
> 
> I did find that if you forget to connect the antenna it doesn't connect to the cell network when it does work! That took an embarrassing amount of time to notice.
> 
>> …but the ip stack seems to crash on CREG 2:
> 
> Mine connected to the v2 server and then crashed, the stack trace looks the same as yours and the register content is similar.
> 
> I (69196) ovms-server-v2: Send MP-0 S0,K,0,0,stopped,standard,0,0,0,0,0,0,0,21,0,0,0,0,0.00,0,0,0,0,-1,0,0,0,0,0,0,0,0.00,0.00,0
> D (69206) SIMCOM ppp rx: 19 ac 50 18 39 08 47 00 00 00 4e 73 4d 50 53 74 ..P.9.G...NsMPSt
> D (69206) SIMCOM ppp rx: 70 39 4e 67 3d 3d 0d 0a 61 3d 7e                p9Ng==..a=~
> D (69206) SIMCOM ppp tx: 7e 21 45 00 00 ae 00 06 00 00 ff 06 e1 1a 0a aa ~!E.............
> D (69206) SIMCOM ppp tx: c7 0f bc 8a 4b e5 54 0f 1a d3 00 00 19 ac a5 ce ....K.T.........
> D (69206) SIMCOM ppp tx: 2f 10 50 18 16 98 e6 d4 00 00 4e 73 4d 50 53 74 /.P.......NsMPSt
> D (69216) SIMCOM ppp tx: 70 30 4e 78 32 65 47 7a 66 43 4e 79 2f 72 6d 44 p0Nx2eGzfCNy/rmD
> D (69216) SIMCOM ppp tx: 62 6b 36 6f 4c 35 71 71 56 39 46 38 71 47 51 46 bk6oL5qqV9F8qGQF
> D (69226) SIMCOM ppp tx: 66 79 73 38 50 77 69 34 73 53 72 37 4e 63 4c 54 fys8Pwi4sSr7NcLT
> D (69236) SIMCOM ppp tx: 4d 74 71 32 46 34 67 44 65 62 6d 33 50 2b 5a 6a Mtq2F4gDebm3P+ZjGuru Meditation Error of type LoadProhibited occurred on core  1. Exception was unhandled.
> Register dump:
> PC      : 0x401724d9  PS      : 0x00060330  A0      : 0x8017251a A1      : 0x3ffdaec0
> 0x401724d9: ip4_route at /home/ubuntu/esp/esp-idf/components/lwip/core/ipv4/ip4.c:250 (discriminator 2)
> 
> A2      : 0x0000f01d  A3      : 0x00000000  A4      : 0x3ffead48 A5      : 0x3f42695c
> A6      : 0x00000008  A7      : 0x3ffdb0e8  A8      : 0x801724cd A9      : 0x3ffdaea0
> A10     : 0x00000000  A11     : 0x00000000  A12     : 0x3ffdca38 A13     : 0x3ffdb0d0
> A14     : 0x00000004  A15     : 0xab9423a7  SAR     : 0x00000018 EXCCAUSE: 0x0000001c
> EXCVADDR: 0x0000f0d2  LBEG    : 0x4000c349  LEND    : 0x4000c36b LCOUNT  : 0x00000000
> 
> Backtrace: 0x401724d9:0x3ffdaec0 0x40172517:0x3ffdaee0 0x40170706:0x3ffdaf00 0x4016ad7b:0x3ffdaf40 0x4016ad9d:0x3ffdaf70 0x4016ae3e:0x3ffdaf90 0x4016b29c:0x3ffdafb0 0x4016e9d6:0x3ffdafd0 0x4016ea17:0x3ffdaff0 0x40177441:0x3ffdb010 0x40177805:0x3ffdb030 0x4017784c:0x3ffdb050 0x4017a9e5:0x3ffdb070 0x4017773c:0x3ffdb090 0x4017deba:0x3ffdb0b0 0x4017def6:0x3ffdb0d0 0x401795c9:0x3ffdb0f0 0x4017b005:0x3ffdb110 0x4017b0b0:0x3ffdb130 0x401793eb:0x3ffdb150 0x40177269:0x3ffdb170 0x4019e244:0x3ffdb1a0 0x4019e391:0x3ffdb1c0 0x40165999:0x3ffdb1e0
> 0x401724d9: ip4_route at /home/ubuntu/esp/esp-idf/components/lwip/core/ipv4/ip4.c:250 (discriminator 2)
> 
> 0x40172517: ip4_route_src at /home/ubuntu/esp/esp-idf/components/lwip/core/ipv4/ip4.c:159
> 
> 0x40170706: tcp_rst at /home/ubuntu/esp/esp-idf/components/lwip/core/tcp_out.c:1336 (discriminator 4)
> 
> 0x4016ad7b: tcp_abandon at /home/ubuntu/esp/esp-idf/components/lwip/core/tcp.c:1630
> 
> 0x4016ad9d: tcp_abort at /home/ubuntu/esp/esp-idf/components/lwip/core/tcp.c:1630
> 
> 0x4016ae3e: tcp_netif_ipv4_addr_changed_pcblist at /home/ubuntu/esp/esp-idf/components/lwip/core/tcp.c:1630
> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20171114/be863bec/attachment.htm>