[Ovmsdev] Modem link-drop crash
mark at webb-johnson.net
Tue Dec 26 08:15:01 HKT 2017
Seems much better for me now. 36+ hours connected. One network disconnection and reconnected automatically:
I (66104434) ovms-server-v2: Send MP-0 S100,K,0,0,done,standard,200,160,0,0,0,0,13,4,0,0,0,0,160.00,0,0,0,0,-1,0,0,0,0,0,400,0,0.00,400.00,100
I (66104444) ovms-server-v2: Send MP-0 D0,0,5,22,30,25,0,1000000,0,66101,22,0,0,0,1.01099,0,0,0,22,0
I (66618624) simcom: CREG Network Registration: Searching
I (66619474) simcom: Lost network connection (NetworkRegistration in NetMode)
I (66619474) simcom: State: Enter NetLoss state
I (66619474) gsm-ppp: Shutting down (hard)...
I (66619474) ovms-server-v2: Network is down, so disconnect network connection
E (66619474) ovms-server-v2: Status: Error: Disconnected from OVMS Server V2
I (66619474) gsm-ppp: StatusCallBack: User Interrupt
I (66619474) gsm-ppp: PPP connection has been closed
I (66628474) simcom: State timeout, transition to 5
I (66628474) simcom: State: Enter NetWait state
I (66629474) ovms-server-v2: Status: Waiting for network connectivity
I (66638504) simcom: CREG Network Registration: RegisteredRoaming
I (66639474) simcom: State: Enter NetStart state
I (66640524) simcom: PPP Connection is ready to start
I (66641474) simcom: State: Enter NetMode state
I (66641474) gsm-ppp: Initialising...
I (66647124) gsm-ppp: StatusCallBack: None
I (66647124) gsm-ppp: status_cb: Connected
I (66647124) gsm-ppp: our_ipaddr = 10.170.204.16
I (66647124) gsm-ppp: his_ipaddr = 10.64.64.64
I (66647124) gsm-ppp: netmask = 255.255.255.255
I (66647124) gsm-ppp: our6_ipaddr = ::
I (66649474) ovms-server-v2: Status: Network connectivity established
I think we will still probably need an PPP overall connection attempt counter. If PPP can’t be brought up N times, then power cycle the modem and start from scratch. The SIMCOM SIM908/808 modems certainly seemed to require that to be able to recover 100% of the time.
> On 25 Dec 2017, at 5:40 PM, Tom Parker <tom at carrott.org> wrote:
> On 24/12/17 19:53, Mark Webb-Johnson wrote:
>> Can you guys try updating both your ESP IDF (based on open vehicles 2.1 repo) and ovms v3 firmware. See if it is more reliable? I will leave mine running now, to see if there is any improvement for long-lived connections.
> I updated and went for a drive on GSM. The v2 server reported telemetry for 10 minutes and then it stopping talking. I don't know why it stopped.
> I've now got it on my desk connected to my laptop and it's been working for 20 minutes. I've just unplugged the antenna so we'll see how well it works (signal is strong here so it remains connected, but hopefully this simulates changing cell towers or something).
> I've also found that you can connect with a terminal emulator at 155200 baud and it doesn't reset the ovms (make monitor does reset it) so hopefully next time it stops communicating while driving I'll be able to see what is wrong.
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OvmsDev