November 2013 - OvmsDev - Open Vehicles

12.5 Volt warning... Volt.
by Nikki Gordon-Bloomfield 19 Nov '13

19 Nov '13

Our Volt’s OVMS has got a little crazy over the 12 volt battery, I suspect because it’s getting colder, so the charge level will naturally drop a little. The Volt’s 12V battery has not dropped below 12.5 volts as far as I can tell. Any idea why it’s going crazy with the OVMS CRITICAL warnings? Nikki. Nikki Gordon-Bloomfield http://about.me/aminorjourney/bio email: nikki(a)littleCollie.com tel: +44 7901 553308

2 2

Still having major comms problems
by Matt Beard 18 Nov '13

18 Nov '13

My OVMS unit is still very flaky - to the point where it is severely limiting my ability to test the changes I have made to the iMiev code. The unit no longer even responds to SMS text messages. The most recent entries in the server logs are as follows: {"h_data":"#68 A got error Broken pipe","h_recordnumber":"10055","h_timestamp":"2013-11-14 12:24:51"}, {"h_data":"#88 A got error Broken pipe","h_recordnumber":"10448","h_timestamp":"2013-11-14 12:38:00"}, {"h_data":"#88 A got error Broken pipe","h_recordnumber":"10458","h_timestamp":"2013-11-14 12:38:18"}, {"h_data":"#51 A got error Broken pipe","h_recordnumber":"12368","h_timestamp":"2013-11-14 13:40:20"}, {"h_data":"#71 A got error Broken pipe","h_recordnumber":"13440","h_timestamp":"2013-11-14 14:04:25"}, {"h_data":"#101 A got error Broken pipe","h_recordnumber":"19708","h_timestamp":"2013-11-14 16:57:57"}] Any ideas?

3 3

12V battery alerts
by Rolf Welde Skeie 15 Nov '13

15 Nov '13

Hi, I'm getting 12V battery alerts ala: "MP-0 PAALERT!!! 12V BATTERY CRITICAL (13.2V, ref=14.7V)" So the 1.5V hardcoded difference between charged and non-charged state seems to be too low. The battery is working just fine and has been tested without any issues, but seems to stabilize at approx. 12.8V. Is this a global issue; are others experiencing this as well? If this is a issue only relevant to my car: would it make sense to allow for controlling some of these kind of values through parameters? BTW, I believe the Think City module could be put in the production builds, it seems to be working fine. Best regards -- Rolf Welde Skeie Solåsen 27, 5223 Nesttun, Norway +47 92403016 / rwskeie(a)gmail.com

6 16

APNS push subscriptions on iOS 7
by Mark Webb-Johnson 12 Nov '13

12 Nov '13

Just noticed that _new_ APNS push subscriptions don't seem to be working on iOS 7. Something has changed and broken things. Existing subscriptions seem fine, so this only affects new installs. I swear this worked during the betas, but seems to have stopped a few weeks ago). Maybe iOS 7.0.x rather than 7.0.0? I'm looking into it, but the migration to iOS 7 is non-trivial, due to the layout and graphical widget changes. The way toolbars work is dramatically different. Regards, Mark.

1 0

Inaccurate car_parktime / car_time
by Håkon Markussen 12 Nov '13

12 Nov '13

Hi, The car_time is incremented in the state_ticker1 (approx once every second). However I've noticed that this is extremely inacurate Today I started a stopwatch when parking the car, and compared it to the car_parktime in the iOS app: - Stopwatch: 8:00 (eight hours) - car_parktime: 6:01 (six hours and one minute A difference of 1 hour and 59 minutes during 8 hours! I wonder if this could be done in an other way? E.g. by pulling the time from the GPS? Best regards. Håkon Markussen

6 12

Leaf current build
by Nikki Gordon-Bloomfield 11 Nov '13

11 Nov '13

My OVMS module arrived yesterday, so I'm going to be setting it up for the LEAF this week. Is the current leaf version on Git hub? Can someone send me the flash-ready firmware? Nikki. Sent from my iPhone

3 2

Feeling brave / foolish
by Mark Webb-Johnson 10 Nov '13

10 Nov '13

Feeling brave / foolish, I sat in my car with a CAN-USB adaptor and spoofed the vehicle error codes from 0 .. 999. The VDS in the car shows me the corresponding error message for each code. Scary, but seems to work well. I’ve now documented another approximately 200 error codes for the Tesla Roadster, and committed to github. My personal favourites are: 720=900A discharge limit exceeded 721=863A discharge limit esceeded 722=805A discharge limit exceeded 723=300A discharge limit exceeded 724=200A discharge limit exceeded 730=750A discharge warning 731=450A discharge warning; power limited 732=300A discharge warning; power limited 733=200A discharge warning; power limited Some things really should be treated more as a ‘target’ than an error ;-) and also: 23=SHUTTING DOWN PULL OVER SAFELY The vehicle ‘chime’ for that one was quite a bit different from the normal soft chime, and the use of capitol letters is unique to that message. I can only suggest that the appropriate action is to get out of the car and ‘duck and cover’, after news of recent events. Also of particular interest are: 725=190A charge limit exceeded 726=75A charge limit exceeded 727=60A charge limit exceeded ...as Tesla Motors Club is discussing upcoming 80A Pilot Signal support for the Tesla Roadster. 0..999 covers about half the codes we’ve seen. I’ll have a go at spoofing/logging the others next weekend. Regards, Mark.

1 0

Change to API for vehicle poll0 and poll1 functions
by Mark Webb-Johnson 08 Nov '13

08 Nov '13

I just committed a change to all vehicle modules, to change the api for the poll0() and poll1() functions. 1aaa0a3 Move can bus low level register access to vehicle.c, out of individual vehicle modules The new API sets up: unsigned int can_id; // ID of can message unsigned char can_filter; // CAN filter unsigned char can_datalength; // The number of valid bytes in the can_databuffer unsigned char can_databuffer[8]; // CAN message bytes prior to the calls to poll0() and poll1(). So, the individual vehicle modules no longer need to (and no longer are able to) access the low-level CAN bus registers in any way. I tried to move all the vehicle modules to the new mechanism, but there seemed to be significant differences in the way each module did things. Hopefully the work I did was ok and hasn’t broken anything, but please check your respective modules to make sure they still work. Overall, we’ve saved about 500-to-600 bytes of flash doing this. I’ve labelled this 2.6.1, as it has the capacity to break things. Regards, Mark.

2 1

2 years of OVMS
by Mark Webb-Johnson 06 Nov '13

06 Nov '13

The OVMS github repository was created two years ago, on 2nd November 2011. Since then, there have been 845 commits to the repository, two sub-repositories created (for the iOS and Android Apps), a side-project spun off (CAN-RE-TOOL), and a whole lot of fun. To celebrate this, we are going to be publishing some 'stories of OVMS' - highlighting some of the more inventive ways people are using OVMS. A lot of tinkering, hacking, and gluing together different frameworks. If anyone has any story to share, please send it in. The more, the merrier. Regards, Mark.

1 0

Potential new OVMS user/tester UK Volt
by Steve Ashton 05 Nov '13

05 Nov '13

Hi I have been following the mailing list for a few weeks as I have recently bought a Volt and have just seen the OVMS kit is back in stock in the UK. If I buy the Volt OVMS kit and a suitable programmer, what functions are available out of the box? Do I need anything more to start using the kit? Is there any active development progressing with the Volt? Any further help with "getting started" would be appreciated. I have not coded anything since s/360 went out of fashion but am happy to help with testing if that helps. Steve Ashton

2 2