[Ovmsdev] v3 hardware disconnecting from v2 server

[Mark Webb-Johnson]

I think this may be a different issue, and maybe cellular related.

It depends on the network, but the cellular standards do have a mechanism where if the cellular network denies registration to a connecting client, the client is supposed to back-off and not try again for a while. I know SIMCOM supports this, because in the early days we had this with Hologram. This is the “FPLMN” list. You can check the status of that list with:

AT+CRSM=176,28539,0,0,12

The response is a list of cellular network codes that are currently blocked.

The list can be manually cleared with:

AT+CRSM=214,28539,0,0,12,"FFFFFFFFFFFFFFFFFFFFFFFF"

Then power cycling the modem.

> Any advice on which commands to try when it's not connected?


Assuming ‘simcom status’ shows the mux is up and running, then just try to talk to the modem and see what it is doing:

simcom muxtx 3 AT

Just try to get AT command responses first.

If that works, then need to see why it is not connecting. Check network registration status, COPS status, etc.

Regards, Mark.

> On 25 Mar 2018, at 3:39 AM, Tom Parker <tom at carrott.org> wrote:
> 
> On 25/03/18 02:41, Mark Webb-Johnson wrote:
>> What do you mean by ‘disable and reactivate the SIM card’? How are you doing that?
> 
> I have access to Spark's m2m service which allows customers to deactivate and reactivate simcards. The deactivation is immediate, I can see the simcom reports it is disconnected and the ovms starts trying to reconnect. Last time I tried, when I reactivated, the simcom reconnected to the cell phone network but the ovms never re-established a ppp connection. I can send it sms messages and see them show up in the simcom logging so I know some things are working. I last tried this a couple of weeks ago, I'll try again tomorrow.
> 
> I have a range of devices on this service and some of the reconnect while other don't, so the ovms isn't the only one having trouble.
> 
>> The issue I was having was some task (I suspect lwip) gets messed up. Stopping the modem, trying to connect wifi, etc, all just locked up the async console. I think you had the same?
> 
> I've certainly had situations where doing simcom power off causes the async console to freeze, but I've only tried to do that after the cellular is has stopped working.
> 
>> Cellular connectivity should be a different issue. Maybe just can’t connect to the signal - but the logs should tell us more info. We can also directly issue AT commands when the modem is in that state to try to find out why.
> 
> Any advice on which commands to try when it's not connected?
> _______________________________________________
> 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.teslaclub.hk/pipermail/ovmsdev/attachments/20180325/1168391c/attachment.html>