- OvmsDev - Open Vehicles

OVMS - power drain
by Nigel Jones 11 Jun '14

11 Jun '14

Just as a quick update I thought I'd mention that I've now disconnected OVMS from my Nissan Leaf in order to ascertain the cause of the 12V battery drain I was seeing for several days over the weekend - to the extent of returning after around 8 hours and being unable to even start the car More complete details are at https://speakev.com/threads/nissan-leaf-12v-battery-totally-dead.19/page-4 I was just about to make a similar comment to the one Kevin just made in that thread - namely that I doubt the ovms processor per se is the cause of the drain since even in a tight spin loop due to a bug I can't imagine it's possible to take that much power? I however wouldn't be surprised if ovms polling the CAR bus might be keeping "things" in the car awake, which then causes the drain. There's also a chance it's just co-incidence. My plan is to reintroduce the OVMS at some point where the car is going to sit idle and not needed (working at home, or when I'm up in London by train) and see if the problem reoccurs. Of course it may be a particular sequence of events that gets the car into a state where it's bus is active.. tricky to pin down. regardless switching over to the EV bus is another option. The leafdd seems stable. Nigel. -- ---- Nigel Jones

3 7

Mitsubishi logging problem
by Nikolay Shishkov 08 Jun '14

08 Jun '14

I have been testing the logging for the mitsubishi and noticed a problem with it - no matter if I was charging or driving the log was always showing driving. I have been looking at the code and I think I found the problem. If I understand this correctly in vehicle_mitsubishi_ticker1 function in vehicle_mitsubishi.c file the car_doors1bits.CarON is set depending on wheather there is CAN bus communication. This is unfortunate since the car_doors1bits.CarON (via CAR_IS_ON) is used in the logging.c to determine if the car is "driving"... and if it is, then it is not "charging". I am not sure what the best solution would be: - to set the car_doors1bits.CarON to 0 if the car is charging or - to refactore the logging code to prefer the CAR_IS_CHARGING and test for it first in the various if/else statements. I have not been able to build and test any of this yet. Any comments, ideas, suggestions on how to solve this? Nikolay

3 2

Brown outs, power cuts, connectivity problems
by Nikolay Shishkov 07 Jun '14

07 Jun '14

I am trying to understand how is the ovms supposed to handle brownouts, power interruptions and connectivity problems. The reason is that I think I am getting power cut from the obd port after some time of innactivity. Looking at the code for the logging function it seems (to me) that all variables are held in memory and if the power is cut while logging there is no way to recover the historical data. My quick test today while on a drive confirmed this. Another scenario I am considering is the following - the car has powered down the obd port leaving the ovms with no power. - the driver gets in powering the car and driving off. - this powers up the ovms, but it takes some time to get network access, lock on the gps, etc. One more scenario - loosing GPRS connectivity, and then powering the car down. The car can switch off the power to the obd port and then the log is forgotten. And another observation - the ovms seems to be holding the last known gps position, with no indication of whether the position is valid or not - or maybe the accuracy or/and the time the position was obtained. Any ideas for improvements? Or have I missed something in the logs? Is there any way to make the logging more robust - say store the initial values when changing state in a non volitale memory together with some king of timestamp or another marker? This way if there is a power interruption and the power is restored within say 1 minute the logging could continue the counters like nothing has happened. Any other ideas? Maybe all of the above is addressed in the code and I am just missing it? Nikolay

2 1

Quick update
by Nigel Jones 04 Jun '14

04 Jun '14

Apologies for lack of progress - rather hectic at work, but over lunch I did a quick rebuild of ovms having noticed a little typo I introduced when adding the suggestion from Mark and Tom With the fix battery level is now correctly reported. This is my fully charged 2012 leaf (at around 246 GIDS +/- a few :-( OVMS Nissan Leaf XXXX XXX:Not charging SOC: 88% Ideal Range: 117 km 3:00 PM LEAFDD pictures included This is great news as it gives me confidence the unit/sw is working. -- ---- Nigel Jones

4 7

Twizy 45 and ovms firmware
by Gianluca Magalotti 03 Jun '14

03 Jun '14

Hi first of all I want to introduce myself. I'm a new Twizy 45 owner and a software developer (or at least I was ages ago :-) ). Actually I spend my free time doing some prototyping using Arduino and, now, doing some Twizy hacking as well. I'm interested in contributing at the project as developer and tester for twizy 45. My github id is gluca (https://github.com/gluca) Now the firmware questions: When upgrading firmware which branch should I use? Do I have to rebuild or I will find a pre-build hex file for twizy? In any case, I've downloaded the microchip project and switched to the V2_RT_Production configuration and it builds (I had some trouble in finding the C18 compiler for osx but i've found a 3.40 version). Now I've enabled all switches (OVMS_TWIZY_CFG and OVMS_TWIZY_BATTMON) and created a new configuration (V2_RT_Production_fullfeature). I will use my branch for experiments. Now the dev parts: 1) M2M Sims. I live in Italy and M2M data plan are not (yet?) accessible at reasonable rates. In any cases M2M data plans are "data plan" only and typically do not include sms (at least sending sms). I was wondering if some other way can be provided for alerts and other messaging needs. 2) Twizy 45 settings. I've read both user guide and all the ods files and I think I've found some errors on ods. Specifically ts map break/neutral rpm values for twizy 80 and 45 seems swapped. 3) Roadmap. Is there any roadmap for twizy functionalities I can partecipate in developing/testing? Gianluca Magalotti ITIL V3 Certified email: gianluca(a)magalotti.net Mob: +39 340 7418648 Mob: +39 3474 3474 25 Linkedin: http://www.linkedin.com/in/gianlucamagalotti/

2 1

PICkit changes parameters (EEPROM)
by Michael Balzer 01 Jun '14

01 Jun '14

Hi all, my PICkit2 frequently alters single EEPROM cells on flashing. It's set to "preserve EEPROM" and mostly does so, the effect only for example changes the server parameter from "64..." to "S4...". Other parameter slots also have been affected, my last flash changed my registered phone id, and a forum member reports a change of the first vehicle id byte from "D" to "R". Is there a way to make the flashing process reliably preserve the EEPROM? Thanks, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

2 2

Twizy : Symptomes of a failing charger
by Julien (JaXX) Banchet 30 May '14

30 May '14

Hello, And an extra hello to Twizy Specialists. I'm running into what's believed to be a common Twizy issue concerning the onboard charger Since a big week: during charge, after a few minutes (and for sure if I come back to the car while it's ending charge) the SERV light is on, along with the exclamation point battery icon. Upon departure, the SERV is off, but comes back after a few seconds before going away after 3/4km of driving. From what I read, it's the forthcoming signs of a failing battery charger (hopefully, warranty ends in 3 weeks). Though, most of the people who had this usually noticed a missing fan noise, which I believe I still hear. This does not seem linked to the pretty impressive accident I had a few weeks ago (only plastics involved at first sight, gotta plan the budget for repairs until police enquiry+insurance kick in) So, unless I'm totally nuts, I've ever only seen flatline pwr_curr rates (then decreasing approaching topping off). Simply, I wanted to share with you odd power curves from a charger giving it's last breath: https://www.dropbox.com/s/nmbavtx0r2bku4p/twizy_charge_pblm.png [ Arrived early at work nearly (expected) depleted battery (9%), from 8:40 to 9:17: steady 2400 +/- 50 W, then it drops to 1040W at 9:30, before slowly coming back to 1700W at 9:44 then 1550W since... ] Though I've had the SERV on the last charges, since this morninh, a Stats? command shows Charging, Topping Off, even though the time I walk to the office it didn't get to 11% of SoC, and the ETA, at 8:44 seemed consistent at 199 minutes (now 10:31: ETA Full: 105 minutes, SoC 60%)... odd. "Voilà" That's about it... Gotta call the garage now :-/ Hugs and all! JaXX./.

2 3

Twizy release 3.2.1
by Michael Balzer 30 May '14

30 May '14

Hi all, just checked in Twizy release 3.2.1: https://github.com/openvehicles/Open-Vehicle-Monitoring-System/commit/bd74b… News: - Statistics: avg speed and accel/decel, trip length (car_trip) and SOC usage - New trip efficiency report after driving incl. new stats - RT-PWR-Log and RT-PWR-UsageStats records extended by new stats - New CFG RAMPL command to set ramp rpm/s limits - CFG TSMAP extended by speed coordinates Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

1 0

12V battery fail
by Nigel Jones 30 May '14

30 May '14

Hi, I have no idea if OVMS has any part to play other than in reporting the issue, but I've posted a full description to speakev at https://speakev.com/threads/12v-battery-flat.2373/ Basically I hit a low voltage warning - OVMS notified me via text. - why at such a low threshold when it was too late - no idea yet if ovms may be causing more drain the rest of the info is on the thread nigel. -- ---- Nigel Jones

3 3

H2O Wireless
by Tom Saxton 26 May '14

26 May '14

I just posted info on using a cheap OVMS-compatible cell service reseller, H20 Wireless, on TMC. http://www.teslamotorsclub.com/showthread.php/7716-OVMS-Installation?p=6668 97&viewfull=1#post666897 Hat tip to Cathy for doing the research to find a cheaper provider for us. It looks promising, but the jury is still out. Tom

3 2