jaanton
Roadster NA #1026
I got my new 3.3 Module with 3.3 modem and have yet to get the modem to work.
It all works with my home WiFi network with the modem turned off. But when I turn on the modem (I'm using Hologram BTW) in a couple minutes it crashes.
Looking in the logs, it seems that the ppp is coming up just briefly sometimes getting an ip address in the 10.x.x.x range, but then looses it. reporting UserInterrupt in the log. I'm attaching the screen shot of the crash indication.
I'm not used to reading the log files, it would sure be nice if a reboot message was put in the log so it's clear that a crash happened. Since that information is in the dashboard I would think that should be in the log as well.
I drove away from my home WiFI and tried it again in a different location which might get better cellular signal, but it crashed again turning on the modem via my cell phone connecting to the access point of the module.
I've tried a bunch of stuff, booting the eap release (seems to be older than the factory/stable release) and I tried my friends' ovms 3.3.001 build and that crashed also. I have some logs but I'm not going to post them because they have sensitive information. Sigh.
I could take my old 3.1 board, upgrade it's software and move the modem there, but I feel this is a software problem mostly. Even if I'm having dropped cellular connections, the module shouldn't crash.
I moved to the new 3.3 board from my 3.1 by backing up the state on my sd card, moving it to the new module and recovering that backup state. That worked well, but I'm a little uncertain if that might be my problem i.e. if there is some incompatibility between 3.1 backups and 3.3 recovery.
Anyone with similar problems?
It all works with my home WiFi network with the modem turned off. But when I turn on the modem (I'm using Hologram BTW) in a couple minutes it crashes.
Looking in the logs, it seems that the ppp is coming up just briefly sometimes getting an ip address in the 10.x.x.x range, but then looses it. reporting UserInterrupt in the log. I'm attaching the screen shot of the crash indication.
I'm not used to reading the log files, it would sure be nice if a reboot message was put in the log so it's clear that a crash happened. Since that information is in the dashboard I would think that should be in the log as well.
I drove away from my home WiFI and tried it again in a different location which might get better cellular signal, but it crashed again turning on the modem via my cell phone connecting to the access point of the module.
I've tried a bunch of stuff, booting the eap release (seems to be older than the factory/stable release) and I tried my friends' ovms 3.3.001 build and that crashed also. I have some logs but I'm not going to post them because they have sensitive information. Sigh.
I could take my old 3.1 board, upgrade it's software and move the modem there, but I feel this is a software problem mostly. Even if I'm having dropped cellular connections, the module shouldn't crash.
I moved to the new 3.3 board from my 3.1 by backing up the state on my sd card, moving it to the new module and recovering that backup state. That worked well, but I'm a little uncertain if that might be my problem i.e. if there is some incompatibility between 3.1 backups and 3.3 recovery.
Anyone with similar problems?