December 2012 - OvmsDev - Open Vehicles

Twizy module 2.1
by Michael Balzer 11 Dec '12

11 Dec '12

https://github.com/dexterbg/Open-Vehicle-Monitoring-System/commit/e527b9088… - temperature function updated to new formula (A - 40) - cell alert thresholds changed to fixed absolute deviations 3 °C temperature / 100 mV (watch thresholds = stddev as before) - battery monitor reset now bound to "key on" event instead of full charge cycle - cell mean value / deviation calculations now done with rounding - battery text alert now also sent by MSG protocol ("PA") and triggered immediately after every alert status change - Twizy battery monitor compiler switch: OVMS_TWIZY_BATTMON current ressource usage: 6% RAM (193 byte) + 10% ROM -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

2 2

Twizy
by Mark Webb-Johnson 10 Dec '12

10 Dec '12

Twizy support seems to be coming along nicely, thanks to the amazing work Michael is doing. Some good functionality there already. I'm starting to see some Twizy users register on openvehicles.com. Perhaps the word is getting out? Some questions / requests: Michael: Can you let me have the details on the cable pinouts and parts you are using at the moment? Is it a standard cable, or are you having to make something up? How is charge control on the Twizy done? Is there any way of stopping or starting (topup) a charge from within the car, or is it just controlled by plugging? Any chance of can bus control of this? Can anyone help with the car images for the Twizy? There are lots of nice images available, but they need to be photoshopped to the right dimensions and transparent background png. Regards, Mark.

5 17

Developer documentation
by Michael Balzer 03 Dec '12

03 Dec '12

Mark, Michael, I have written down some first hints for new developers, including some kick-off steps to get going and all of the "little problems" that gave me some headache up to now -- or at least those I haven't yet erased from my memory ;-) https://github.com/dexterbg/Open-Vehicle-Monitoring-System/blob/v2/docs/Fir… Mark, I know you've already begun on the firmware API documentation. Maybe we can put the docs together to get a complete developer documentation. Please comment and/or extend. Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

1 0

Twizy module V2.0: battery monitoring
by Michael Balzer 02 Dec '12

02 Dec '12

Hi all, first release of the battery monitoring system: https://github.com/dexterbg/Open-Vehicle-Monitoring-System/commits/v2 - PEM and motor temperatures - Battery cell temperatures: 7 cell modules of 2 cells each (overall battery temperature = average of modules) - Battery pack and cell voltages - Battery monitoring system: - history of min/max/max deviation during usage cycle - ...tagging of suspicious cells (dev > std dev) - ...tagging of cell alerts (dev > 2 * std dev) (thresholds may need refinement) - ...sends SMS+MSG on alert state change - First draft of battery state data MSG protocol extension (to be discussed on the developer list) - Development/debug utility: CAN simulator w/ battery data sim data can be injected any time by issuing the DEBUG command with desired sim data chunk number (i.e. SMS "DEBUG 12" / MSG "200,12") - Minor code cleanups & bug fixes If other Twizy OVMS users are here, I really could use some feedback on this. Especially on the watch/alert thresholds. I have to gather more real data to see if we need a configuration for the alert sensitivity, or if we need to introduce some minimum deviation level. I also sometimes got single deviations that must be completely wrong, although I implemented two levels of value consistency assertion. I'm still searching for the source of those. As the Apps do not support this feature yet, please send me your SMS outputs, i.e. - "BATT" (same as last alert if you get some) - "BATT V" - "BATT VD" - "BATT T" - "BATT TD" Thanks! Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

1 1

Volt/Ampera SOC and more
by Michael Jochum 01 Dec '12

01 Dec '12

Hi, i implement the following code into the FW: unsigned int soc_largest = 56028; // this is from mark, readout from the logs unsigned int soc_smallest = 13524; // this too unsigned int v; v = (can_databuffer[1]+(unsigned int) can_databuffer[0] << 8); if ((v<soc_smallest)&&(v>0)) v=soc_smallest; if (v>soc_largest) v=soc_largest; car_SOC = (char)((v-soc_smallest)/((soc_largest-soc_smallest)/100)); i got funny Outputs in the iPhone app. Something between 0 and 100%. Not match to the real state. Full can display as 0% or 20, or...... Empty can show as 100%, or something else. This code (org. mark) works: car_SOC = (char)((can_databuffer[1]+((unsigned int) can_databuffer[0] << 8))/644); With this i got 21-87% for the soc. BTW: i thing it is a good idea to deactivate the minSOC warning. It is not nessary for the Volt/Ampera. I activate the internal GPS (OVMS_INTERNALGPS) and get the position from my car. GREAT WORK. I got no Info about the VIN, the OVMS FW and the car type in the iPhone App. 1.3.2 build from the git. Bye michael

3 2