November 2012 - OvmsDev - Open Vehicles

Joining forum without a TMC account
by John Hatchett 13 Nov '12

13 Nov '12

I was wanting to join the forum at openvehicles.com but the form for creating a new user account requires "TMC Forum User" . Now that OVMS is expanding beyond the Tesla, can the requirement be removed or do I need to go get a TMC Forum account as well?

2 1

GM Can Codes
by Michael Jochum 13 Nov '12

13 Nov '12

Hi, didi anybody know these documents? http://www.doc88.com/p-848519526314.html http://www.doc88.com/p-361144209421.html or: http://engineers.ihs.com/document/abstr ... AAAAAAAAAA i know they are older and cost money. Did anybody have them? bye Michael

1 0

General issue: metric system ;-)
by Michael Balzer 09 Nov '12

09 Nov '12

I hesitate to touch anything outside the can module yet, but I would like to store range values in kilometers. Reason: my car uses km and I'm losing precision if converting them to integer (!) miles. 1 mi = 1.609 km Are there any thoughts on this? Could it be just a labeling switch or does the server/app protocol need miles? Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

2 2

Twizy / 500 kbps CAN lockups
by Michael Balzer 09 Nov '12

09 Nov '12

During my tests I had two times some sort of a CAN lockup, i.e. everything worked except the CAN reception -- was fixed by switching the car off + on. I'm not sure yet what caused that, it (of course) did not happen again since I included a first debug output of the RXERRCNT... I saw the 1 mbps setup does not follow the intrepid timing calculator standard parameters but increases prop delay from 1 to 3 and decreases phase 1 from 5 to 3. A similar change to the 500 kbps parameters though did not work with the Twizy. Do you have any hints on debugging this? My current setup for 500 kbps is: // 500 kbps -- tool recommendation + multisampling: BRGCON1 = 0x00; BRGCON2 = 0xFA; BRGCON3 = 0x07; Thanks, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

3 5

Last SOC usage range + odometer
by Michael Balzer 09 Nov '12

09 Nov '12

Mark, https://github.com/dexterbg/Open-Vehicle-Monitoring-System/commit/a0fd188a5… contains two change to the STAT SMS I would recommend as a common extension: 1) Odometer status -- very useful if you keep a charging log. (btw, am I blind or does the current Android App lack the odometer info?) 2) SOC current usage min+max: I need to maintain these values for full charge detection and for range calculation during charging. I included this into the SMS for debug at first hand, but now I think this is an interesting info to keep. If you think it's too Twizy specific, here's another idea: As the net modules should not need to know about car specific variables, maybe the new framework could also use some output gathering hooks within the car module, so there's a clean way to add some car specific data to SMS and server output? Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

1 0

Re: [Ovmsdev] Graphics for Holden Volt
by Mark Webb-Johnson 09 Nov '12

09 Nov '12

Bruce, They look good. I'll try them in the App later. Regards, Mark P.S. Message was too big for the mailing list, and I haven't released, to avoid everyone getting this big message. I'll put the graphics in github and people can get them there if they need. On 9 Nov, 2012, at 6:57 PM, "Bruce McMillan" <brucemcmillan(a)exemail.com.au> wrote: > Hi Mark, > > Please find attached artwork for the Holden Volt (Australian Version). > Hope they are suitable. > > car_holdenvolt_black.png > car_holdenvolt_crystalclaret.png > car_holdenvolt_silvernitrate.png > car_holdenvolt_urbanfresh.png > car_holdenvolt_whitediamond.png > > ol_car_holdenvolt_black.png > ol_car_holdenvolt_crystalclaret.png > ol_car_holdenvolt_silvernitrate.png > ol_car_holdenvolt_urbanfresh.png > ol_car_holdenvolt_whitediamond.png > > map_car_holdenvolt_black.png > map_car_holdenvolt_crystalclaret.png > map_car_holdenvolt_silvernitrate.png > map_car_holdenvolt_urbanfresh.png > map_car_holdenvolt_whitediamond.png > > Notes: > - Right Hand Drive > - Just 5 external colours for 2013 version for the Holden Volt > Black, Crystal Claret, Silver Nitrate, Urban Fresh, White Diamond. > - the x-ray is the same graphic as the Ampera that is already on your site although this version is RH drive > - the map is a reduced size of the x-ray graphic > > > Regards, Bruce. > > <car_holdenvolt_black.png> > <car_holdenvolt_crystalclaret.png> > <car_holdenvolt_silvernitrate.png> > <car_holdenvolt_urbanfresh.png> > <car_holdenvolt_whitediamond.png> > <map_car_holdenvolt_black.png> > <map_car_holdenvolt_crystalclaret.png> > <map_car_holdenvolt_silvernitrate.png> > <map_car_holdenvolt_urbanfresh.png> > <map_car_holdenvolt_whitediamond.png> > <ol_car_holdenvolt_black.png> > <ol_car_holdenvolt_crystalclaret.png> > <ol_car_holdenvolt_silvernitrate.png> > <ol_car_holdenvolt_urbanfresh.png> > <ol_car_holdenvolt_whitediamond.png>

1 0

Internal GPS now available
by Michael Balzer 05 Nov '12

05 Nov '12

For those driving budget cars without onboard GPS (like the Twizy ;): https://github.com/dexterbg/Open-Vehicle-Monitoring-System/commit/600e08634… Internal GPS integration: - optionally use internal SIM908 GPS instead of car GPS (note: needs GPS antenna) controlled by new compiler switch: OVMS_INTERNALGPS - will poll for GPS data once per second while driving (speed > 0) else once every 5 minutes to be able to trace theft / transportation - reduced Google maps SMS to just coordinates for compatibility with Google Maps App This commit contains no Twizy specific changes, should be suitable for any other car without GPS on CAN bus. @List: I'm a bit frustrated about having to reinvent atof(). I gave up on the lib version, it just produced funny float values (not 0 or something explainable). Found nothing helpful on the web, definitely no type, prototype or linker problem. A new Twizy commit is also there, not much of a change though. Using the internal GPS with a decent antenna works like a charm though, quite accurate and fast. I intend to use the altitude to calculate a better energy usage / range estimation, as the Twizy estimation drops too fast when driving uphills. Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

2 2

Vehicle Images
by Mark Webb-Johnson 04 Nov '12

04 Nov '12

For new vehicles, to get the images into the apps, we need images in a similar size, orientation and layout. The images are: 1] The car front-angle view. 654x302 pixels, high quality PNG format. One for each colour to be supported. The background must be transparent. If you have problems with aspect ratio, try to keep the width the same, and leave space on the top/bottom. 2] The car xray view, 304x606 pixels, high quality PNG format. One for each colour to be supported. The background must be transparent. You should try to keep the wheels in approximately the same position as the attached picture (in particular if your vehicle supports TPMS). If you have problems with aspect ratio, try to keep the height the same, and leave space on the sides. 3] Car map images. 96x96 pixels, medium quality PNG format. One for each colour to be supported. Car must be pointing upwards (north). The background must be transparent. If you have problems with aspect ratio, try to keep the height the same, and leave space on the sides. 4] Name of vehicle type We also need the official name and model of the vehicle type (eg. Tesla Roadster, Nissan Leaf, Volt Ampera, etc). 5] File naming The files should be named as follows: car_<type>_<colour>.png (for the car front-angle view) ol_car_<type>_<colour>.png (for the car X-ray view) map_car_<type>_<colour>.png (for the car map image) The <type> is the vehicle type (e.g.; roadster, ampere, twizy, etc). The <colour> is the official colour name (e.g.; thundergray, crystalred, lithiumwhite, electricblue, etc). Once we have artwork in the correct format, putting it in the apps is trivial. The primary problem is finding artwork of appropriate quality and style, with a transparent background. Regards, Mark.

1 1

Debug logging via diag serial port
by Michael Balzer 03 Nov '12

03 Nov '12

I wanted to get some direct debug logging. It took me some time to figure out the diag port only echoes what is sent from the SIM908 to the PIC18, I first thought it tapped RX+TX so I could see the complete communication. Next problem was the modem switches echos off (after COPS I think), so I need to re-enable them at least once in a while. I'm now using this scheme in can_state_ticker1(): #ifdef OVMS_DEBUG // CAN debug log via DIAG port SIM908 command echo: // ATT: could be a problem for running data transfers, // should not be enabled for production/live firmware images! net_puts_rom( "ATE1\r" ); sprintf( net_scratchpad, (rom far char*) "# ERR=%u SOC=%u RNG=%u SPD=%d PWR=%d CHG=%u\r", RXERRCNT, can_soc, can_range, can_speed, can_power, car_chargestate ); net_puts_ram( net_scratchpad ); #endif My questions: am I right with the suspected problem, and is there a better way? Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

2 1

Team Twizy
by Michael Balzer 03 Nov '12

03 Nov '12

Hi everybody, to introduce myself, I'm Michael Balzer from Germany. My regular work is web application and database development, and I'm an electric mobility enthusiast. I fell in love with the Renault Twizy about a year ago and got mine about four months ago. I had been working with some other folks on the german Twizy forum on decoding the Renault Twizy CAN messages (for german results see https://docs.google.com/spreadsheet/ccc?key=0AoKQUT5BY_r5dGJ4c0c2dTBPeGRzMn…) when Thomas Kreisel pointed me to the OVMS about three months ago. I had to wait for the new hardware, but now I'm ready to join :-) I haven't been doing embedded development for some time, and the PIC18 + SIM908 are completely new to me, so please be patient if I ask stupid things. I've just finished a first working can module for the Twizy based on the 1.5.1 code. It's able to read SOC, range, speed and battery power usage. It derives charging states from these and triggers SMS alerts accordingly on charging interrupts etc.. Communication with the Android (market) App is working as well, so this is actually already quite useable... ...thanks to all your great work, of course! :-) Mark, I forked on github as "dexterbg". First commit is checked in, have a look if you like. Now to my questions... Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

2 1