Hi, I just got my OVMS with 4G modem yesterday and installed in my 2014 Nissan Leaf. I'm in New Zealand, and the Hologram SIM seems to be working fine. I am still waiting for my GPS antenna to be shipped (I ordered all parts from Fasttech, but when they saw there would be a delay with the GPS antenna they sent the rest of the bundle ahead, which was very nice of them). Overall I think the installation documentation is very good. At this stage I have not installed an SD card (it doesn't seem likely I will need it). I have also installed and connected the Android app. I can remotely start/stop the A/C (after unplugging TCU and checking the module setting to enable CAN writes). I have managed to stop/start charging. I have a few questions / notes post-install..
1) The web GUI status has several times shown that the system has rebooted due to crash. e.g:
Last boot was 23866 second(s) ago Time at boot: 2022-02-05 09:26:11 NZDT This is reset #25 since last power cycle Detected boot reason: Crash (12/12) Reset reason: Task watchdog (6) Crash counters: 25 total, 0 early Last crash: abort() was called on core 0 Backtrace: 0x4008e676 0x4008e911 0x400e93f8 0x40084152 Event: ticker.1@esp32wifi 0 secs WDT tasks: IDLE0 Version: 3.3.001-33-g58d01654/factory/main (build idf v3.3.4-848-g1ff5e24b1 Dec 27 2021 00:03:08)
- Is this something I should try to investigate further? (and if so, how?) Do those crash logs get automatically sent to developers, or should I file an issue somewhere?
2) I have not managed to lock/unlock the car doors via remote (I have saved a PIN in the web UI under Config->Vehicle). At one point it seemed as if sending the lock command induced the car to repeatedly attempt to start charging a few times each minute! (the charger was plugged in and the car had recently completed it's own charge-to-80% process). Regarding the unlock, if I connect via SSH and "log monitor" while attempting to lock/unlock there are some messages like this:
E (25058111) can: can1: intr=4254296 rxpkt=4252420 txpkt=980 errflags=0x8000d9 rxerr=0 txerr=8 rxinval=0 rxovr=0 txovr=0 txdelay=10 txfail=439 wdgreset=0 errreset=0 E (25058111) can: can1: intr=4254307 rxpkt=4252420 txpkt=980 errflags=0x8440d9 rxerr=0 txerr=96 rxinval=0 rxovr=0 txovr=0 txdelay=10 txfail=439 wdgreset=0 errreset=0 E (25058111) can: can1: intr=4254312 rxpkt=4252420 txpkt=980 errflags=0x204c00 rxerr=0 txerr=128 rxinval=0 rxovr=0 txovr=0 txdelay=10 txfail=439 wdgreset=0 errreset=0 E (25058111) can: can1: intr=4254312 rxpkt=4252420 txpkt=980 errflags=0x204c00 rxerr=0 txerr=128 rxinval=0 rxovr=0 txovr=0 txdelay=10 txfail=440 wdgreset=0 errreset=0
that appear among a flurry of other I and W messages. Are they indicative of a problem? Any idea how to get the door lock working?
3) Is there any user manual for the Android App? In particular any documentation on what the mysterious "Features" page is for and what the feature numbers mean? (I am guessing/hoping it controls app features, and it would be nice to remove/disable both Homelink and the Valet since neither of them are relevant to me).
Cheers,
Len.
Len,
1) You should ask that in the Nissan Leaf sub forum / open an issue with the Leaf developers on Github. Prepare to provide details, especially module logs, so you'll need an SD card.
2) You should ask that in the Nissan Leaf sub forum. The log messages do not indicate an issue, they are normal for a CAN bus going offline.
3) "Features" are a V2 compatibility function & explained in the V2 user manual(s). They control some vehicle / module configuration parameters.
Regards,
Michael
Thanks Michael. I've scrounged an SD card and will install that.
I found in the user manual that (at least for the Nissan Leaf) features #10 and #11 are for SOC Charge Limit and Range Charge Limit, respectively. It would be great if the app could show textual labels for features that are known. Presumably for the server to have sent the feature value (e.g. 75% it could also send the label?)
(Edit: I was browsing around the github repos and saw that exactly this has been implemented, guess it will magically arrive when the next app release comes arount. Neat!)