2013-04-01 2.2.5 Firmware 2.2.5 ### Fixes for charge notification logic on VA ### Show charge, trunk and alarm notifications in DIAG mode ### Speed, parking, and general tidy-ups for VA ### Switch ambient temperature to PID 0x801f for VA ### Auto-calibration for 12V line reading ### Twizy version 2.6.1 - power line plug-in detection ### Add car_doors5 for rear doors, frunk and 12v charging ### 12v alert by MSG protocol fix ### Rework of 12V reference logic - Filters out single peaks / misreadings - Sends "OK" alerts if voltage level restores w/o charging - 15 minutes calmdown before taking new ref voltage - No alerts while car is on ### ESS SOC DIAG (for TR) ### Initial support for CAC in TR and TZ modules ### Experimental Tazzari (TZ) module ### Experimental Nissan Leaf (NL) module
If you are doing a new upgrade to the OVMS and App can you add the ability to open the trunk form the App ? This would be quite useful.
RD11,4.2876,100,88,0,6E,0,FF,FF,38 RD11,4.2879,100,89,0,FF,FF,7F,FF RD11,4.2882,100,95,4,7,64,93,A,E,12 RD11,4.4957,402,FA,0,C3,84,2,2,87,F RD11,4.9180,100,96,6B,0,2,21,C,0,0 RD11,4.9184,420,0,88,88 RD11,4.9187,588,0,0,84 RD11,4.9190,280,0,0,3,0,0,0,0,0 RD11,4.9192,1A0,0,0,0,0 RD11,4.9195,590,1,0,0,0,0,0,0,0 RD11,4.9876,100,88,0,6E,0,FF,FF,38 RD11,4.9879,100,89,0,FF,FF,7F,FF RD11,4.9882,100,95,4,7,64,93,A,E,12 RD11,5.5045,402,FA,0,C3,84,2,2,87,F RD11,5.6850,100,80,60,BB,0,64,0,A3,0 RD11,5.6853,100,81,0,0,0,DC,D6,60,51 RD11,5.6855,100,82,12 RD11,5.6858,100,83,3,0,0,9B,4,D2,9 RD11,5.6860,100,84,3,0,0,EF,3D,36,32 RD11,5.6863,100,85,1,E6,0,89,0 RD11,5.6866,100,A4,53,46,5A,52,45,38,42 RD11,5.6869,100,A5,31,35,42,33,30,30,30 RD11,5.6873,100,A6,35,36,39 RD11,5.6953,100,86,0,93,1,F0,FF,FF,FF RD11,5.6956,100,87,21,FF,FF,0,0,0,0 RD11,5.6958,100,88,0,6E,0,FF,FF,38 RD11,5.6962,100,89,0,FF,FF,7F,FF RD11,5.6965,100,95,4,7,64,93,A,E,12 RD11,5.6968,100,8B,7,8,82,15,7,16,1E RD11,5.6971,100,8D,0,93,1,C9,0,C8,0 RD11,5.7131,100,93,0,FF,FF,0,0,0,0 RD11,5.7211,100,A3,14,13,0,0,0,16 RD11,5.7213,100,94,0 RD11,5.7217,100,97,0,13,0,84,2,2,0 RD11,5.7219,100,9B,FA,67,79,6,48,36,8 RD11,5.7221,100,9C,FA,87,F RD11,5.7225,100,9D,FA,13,0,EC,E4,0,0 RD11,5.7229,100,7,64 RD11,5.9677,100,96,6B,0,2,21,C,0,0 RD11,5.9682,420,0,88,88 RD11,5.9684,588,0,0,84 RD11,5.9689,280,0,0,3,0,0,0,0,0 RD11,5.9692,1A0,0,0,0,0 RD11,5.9694,590,1,0,0,0,0,0,0,0 RD11,5.9779,400,1,1,0,0,0,0,4C,1D RD11,6.0000,100,96,6B,80,2,21,C,0,0 RD11,6.4291,100,88,0,6E,0,FF,FF,38 RD11,6.4294,100,89,0,FF,FF,7F,FF RD11,6.4297,100,95,4,7,64,93,A,E,12 RD11,6.5228,402,FA,0,C3,84,2,2,87,F RD11,6.9778,100,96,6B,80,2,21,C,0,0 RD11,6.9783,420,0,88,88 RD11,6.9786,588,0,0,84 RD11,6.9789,280,0,0,3,0,0,0,0,0 RD11,6.9791,1A0,0,0,0,0 RD11,6.9795,590,1,0,0,0,0,0,0,0
RD11,22.0186,100,88,0,6E,0,FF,FF,38 RD11,22.0189,100,89,0,FF,FF,7F,FF RD11,22.0192,100,95,4,7,64,93,A,E,12 RD11,22.0197,420,0,88,88 RD11,22.0200,588,0,0,84 RD11,22.0203,280,0,0,3,0,0,0,0,0 RD11,22.0205,1A0,0,0,0,0 RD11,22.0208,590,1,0,0,0,0,0,0,0 RD11,22.2086,100,96,6B,0,2,21,C,0,0
i noticed that the OVMS stopped working on my Roadster. I have been experiencing the 12v issue and a Ranger is coming out on Monday to fix it. My question is does the OVMS run off of power from the 12v battery? If it does, can it contribute to it loosing power?
I have not yet analyzed VMS logs, but will do so late today or tomorrow. However, in the meantime, I ask: what is the BT (90F above) actually ? Is it possibly the coolant temperature (it felt "warm", but not 90F) ? Is it the maximum of one temp sensor in the ESS ? If the latter is the case, would an average temperature (or reporting min/max/average) serve us better ? Is there a bug in the code ?
No ... I think that's the next planned release ... not sure what happened to 2.4, but AFAIK 2.3.2 is latest.
Ok ... so it appears we are seeing TmaxBrick. The next question revolves around the CoolDown feature for version 2.5.2. What will be the parameter that controls termination of the CoolDown ? Could Tmax represent a value too far out of line with Tave ? Would it be a "waste" to continue cooling ? Will there be adequate safeguards against drawing down SOC ( for example being plugged in to 120V, or not being plugged in (if that's possible) ) ?
It also appears that the Temps (as reported by OVMS ) are stale after the car sitting overnight. What safeguards will 2.5.2 have to avoid this ? ( Or is there a FEATURE I have missed to avoid stale temps ? )
BTW, this Roadster 1.5 with 2.3.2/TR/V2 does not report CAC ... should it ?
P.S.: Regarding "waste": Even after the Roadster had terminated A/C compressor cooling and (later) reached full STD Mode, OVMS still reported BT of 88F. 88F (31C) is not really a "bad number", but care should be used to avoid "over-cooling". ( My assumption is that the 88F was *NOT* a stale number while still charging, because I observed the Motor Temp changing (up and down -- remember this is a 1.5 ), but the "morning after" BT was also 88F, while actual TmaxBrick was 27C (80.6F).
I live in a part of China and tend to avoid anything with a number 4 in it. I'm not superstitious, but (when in Rome)...
Sounds good Is the 13A something of a (british/HK) household current limit, or enforced for distinguishing a cooldown cycle (good idea) ? Or some other reason ? If the VDS was limited to 12A, will it still enforce 13A, and will it revert to 12A for manually initiated charging ?- - - Updated - - -
At the moment, cooldown is controlled by a minimum-temperature (maxbrick) and maximum time (charge duration) parameter. Defaults for these are in ovms.h:
ovms.h:#define COOLDOWN_DEFAULT_TEMPLIMIT 31
ovms.h:#define COOLDOWN_DEFAULT_TIMELIMIT 60
but can be controlled with parameter #15 (PARAM_COOLDOWN) as templimit:timelimit.
Personally, I am concerned with TmaxBrick, not the average. I want to try to cooldown until the hottest part of the pack is as cool as I want. The cooldown itself is done at 13A, so should not load up too much SOC% in the timelimit time.
Regarding stale temps, the car will turn off its own temperature-monitoring subsystem when it goes to sleep - the temperatures in the app will appear stale. If you want to check those, the only way is to wake up the car (either by physically pressing a door handle / opening charge port, etc, or remotely by tapping on the boot of the car in the App and choosing 'wakeup'). Whenever the car is charging, it is awake and temperatures are available, so this isn't a problem for cooldown.
Sounds good Is the 13A something of a (british/HK) household current limit, or enforced for distinguishing a cooldown cycle (good idea) ? Or some other reason ? If the VDS was limited to 12A, will it still enforce 13A, and will it revert to 12A for manually initiated charging ?
When is 2.5.2 release expected ?
Thanks to your PMs I have learned to turn on CAN-WRITE and can now wake-up the car to get current temps. By-the-way, other than OAT, while CAN-WRITE was OFF, even opening a door did *NOT* update the PEM/Motor/Batt temps -- neither did opening charge-port, even though its status was updated to "white" on the App. Only "major messing" with the VDS did that (while CAN-WRITE was off).
CAC: Again thanks to your PMs, I have CAC in "STAT?" responses so far. Won't expect to see it in the Android App until I drive it tomorrow and complete a charge.
( Thank You ! )