[Ovmsdev] Not processing canbus frames anymore

[Michael Iimura]

I also appear to be having this issue. My module will pick up all the data
that I expect when it first boots, but shortly after, metrics are stale and
the web interfaces show a bunch of question marks. I used to have stability
problems and the module would keep rebooting, but I think I fixed that by
bringing the xtensa up to date in my build environment.
I assumed all the issues I was having were due to my programming, but I'm
having doubts that it's actually picking up and processing all the frames.
CAN logging to SD card and streaming to SavvyCAN through WiFi seem to work
well.

Another issue I'm having is that my GPS is no longer working. I never got
my T-mobile SIM properly activated but the GPS used to work. Now the module
is just in this loop:

I (20386793) cellular: State: Enter Identify state
I (20387153) cellular: Identified cellular modem: SIM5360/SIMCOM SIM5360
(include US and EU variants)
I (20387153) cellular: Set modem driver to 'SIM5360'
I (20387153) cellular: State: Enter PoweredOn state
I (20403153) housekeeping: 2022-03-16 19:25:08 PDT (RAM: 8b=78740-82120
32b=12344 SPI=3384268-3417604)
I (20407153) cellular: State: Enter MuxStart state
I (20485693) ovms-server-v2: Incoming Msg: MP-0 AFA
I (20485693) ovms-server-v2: Send MP-0 a
I (20527143) cellular: State: Enter PoweringOn state
I (20527143) cellular: Set modem driver to 'auto'
I (20527143) cellular-modem-auto: Power Cycle 2000ms
I (20557143) cellular: State: Enter PoweringOn state
I (20557143) cellular-modem-auto: Power Cycle 4000ms
I (20563803) cellular: State: Enter Identify state
I (20564153) cellular: Identified cellular modem: SIM5360/SIMCOM SIM5360
(include US and EU variants)
I (20564153) cellular: Set modem driver to 'SIM5360'
I (20564153) cellular: State: Enter PoweredOn state
I (20584153) cellular: State: Enter MuxStart state
I (20703153) housekeeping: 2022-03-16 19:30:08 PDT (RAM: 8b=78740-82120
32b=12344 SPI=3384268-3417632)
I (20704143) cellular: State: Enter PoweringOn state
I (20704143) cellular: Set modem driver to 'auto'
I (20704143) cellular-modem-auto: Power Cycle 2000ms
I (20734143) cellular: State: Enter PoweringOn state
I (20734143) cellular-modem-auto: Power Cycle 4000ms
I (20740793) cellular: State: Enter Identify state
I (20741153) cellular: Identified cellular modem: SIM5360/SIMCOM SIM5360
(include US and EU variants)
I (20741153) cellular: Set modem driver to 'SIM5360'
I (20741153) cellular: State: Enter PoweredOn state
I (20761153) cellular: State: Enter MuxStart state

and the status page shows:
MODEM Status Model: SIM5360 Network Registration: Unknown Provider: Signal:
0 dBm Mode: State: MuxStart Mux: Status down PPP: Not running GPS: Not
running

All troubleshooting suggestions welcomed.

- Mike

On Wed, Mar 16, 2022 at 12:25 PM Craig Leres <leres at xse.com> wrote:

> On 3/16/22 10:54, Craig Leres wrote:
> > I have a v3.3 module in my Corvette and recently got it back on the road
> > but I find that following the sim7600 modem testing I did a few weeks
> > ago, it doesn't seem to be processing canbus frames. When the car is
> > running, the module does not appear to update soc or vin although this
> > used to work.
>
> Nevermind; I changed the vehicle type, change it back, and rebooted the
> module and it seems to be working again.
>
> I'm still interested in the mod sum -> [vehicle] -> type difference though.
>
>                 Craig
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20220316/88e02cd2/attachment.htm>