February 2013 - OvmsDev - Open Vehicles

12V A/D conversion
by Michael Balzer 25 Feb '13

25 Feb '13

Mark, I got some 12V alerts during the last 3 days. Checking the 12V reading after the alerts showed normal level, so I'm trying to figure out if they were false alerts. Last alert was about 2 hours ago, alerting about 11.0 V -- my check only a few minutes later showed 12.1 V again... I've read into the PIC18 doc on the A/D conversion (chapter 19). AFAIS inputs_voltage() differs from the example in two ways: 1) the example does not turn off the converter after reading the result (but I understand the ADRES register should keep the result) 2) the example step 3 says "wait for acquisition time if required", it seems our function currently does not wait. "To determine acquisition time, see Section 19.1 “A/D Acquisition Requirements”. After this acquisition time has elapsed, the A/D conversion can be started." Section 19.1 contains an equation based on hardware parameters I don't know. Can you please have a look and tell if missing that wait time could lead to false measurements? Thanks! Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

2 1

GeoSIM user guide
by Mark Webb-Johnson 23 Feb '13

23 Feb '13

I've created a short user guide for the GeoSIM option: https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/O… Source .docx is in github along with .pdf. Regards, Mark.

1 0

ODBII source
by Nikki Gordon-Bloomfield 22 Feb '13

22 Feb '13

Guys, Does anyone have a good parts source for ODBII connectors? I'll need to make a special one for the Leaf, since the CAN bus we need is on different pints to the ODBII-OVMS cable I already have. Any tips for a good quality ODBII connector with solder tabs? Cheers, Nikki.

3 2

Introduction - Tazzari Zero
by Patrick Kapsch 15 Feb '13

15 Feb '13

Hi everyone, My name is Patrick and I've been a silent reader of this list for some time now. A few weeks ago I bought three OVMS modules: one for my Ampera, one for the Twizy and a third one for my third Car - A Tazzari Zero. Most of the europeans should have heard of it. It's a smaller EV from italy. As the OVMS now works well in the Ampera and the Twizy, I started the reverse engineering of the Tazzari CAN messages today. There are two ports on the car: one for the controller data, and the other one for the BMS. The last one is of interest for the module, so I managed to log my first data from the Bus. I should mention that the ports are no OBDII connectors but instead the so called AMP Superseal. I borrowed the maintenance Kit from my car dealer and checked the cable wiring for future replication of the connection cable - no big deal. I'm no coder and so I have to rely on you guys for the coding work that needs to be done in order to get this to work. I heard mark saying on Transport Evolved that the implementation of a new car is just 20% of the work, so I hope someone is willing to go that last bit for me as I will do my very best to document the CAN messages. In my first log I just found a hand full of counters or some kind of timer data that counts upwards or downwards periodically, as well as three very stable but not static values. I have the proprietary maintenance handheld device in hand with which one can read out all the data provided on this port. What I now plan to do is build some sort of Y-Adapter-Cable to attach both devices - the handheld and the CAN logger to the port. This way I should be able to log the messages from the device as well as the answers from the BMS as it requests these. I feel pretty confident that I'll be decoding almost every value provided. I'm absolutely amazed by this project and how far it has come and I'm very happy to contribute to this. Please feel free to share your thoughts on this. Regards from Germany, Patrick Kapsch

4 5

OCM Integration to OVMS
by Mark Webb-Johnson 12 Feb '13

12 Feb '13

http://www.teslamotorsclub.com/showthread.php?p=274218 Originally Posted by Kevin Sharpe Project launched to add Charging Station locations and status to OVMS using the www.openchargemap.org OpenChargeMap database. https://www.freelancer.com/projects/Mobile-Phone-iPhone/Update-open-App-wit… Update an open App with new features | Android | iPhone | Mobile Phone | User Interface / IA Kevin: Thanks for helping out with this - such integration could be amazingly useful. Users: A short summary is that we're trying to integrate live range to the OVMS car location map, and to show all charging stations within range. Clicking on a station will bring up further detail. Once that basic work is done, we're planning to look at how we can integrate the charging events, correlated with OCM charger location, to feedback charge results (both good and bad) to OCM. There is a requirements spec at the link Kevin provided, with more detail. Regards, Mark

1 0

OpenXC
by Michael Balzer 07 Feb '13

07 Feb '13

I just heard about this on EVTV: http://openxcplatform.com/ Currently just a simple CANbus interface, but interestingly with official support by Ford, and EVTV says GM is about to join. Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

2 1

Homelink (roadster)
by Mark Webb-Johnson 07 Feb '13

07 Feb '13

From TMC forums: http://www.teslamotorsclub.com/showthread.php/4774-Home-link What I have noticed is this: when I press the Homelink button on the car and I am too far away from the gate, the gate doesn't open. When I push the Homelink button on the OVMS from too far away, the gate doesn't open either. BUT when I continue driving towards the gate, it then opens without pushing the Homelink button a second time. I am within line of sight of the gate the entire time. When I try this on my garage door, I push the OVMS button about a hundred yards away from the garage. I am down a hill and around a corner from the garage--completely out of sight. When I turn the bend and crest the hill and am in sight of the garage--20 yards away, the door then opens without pushing the button again. This does not happen when I push the Homelink button in the car that far away. For the garage door to open with the Homelink button on the car, I have to be 20 yards away and in line of sight. And either way, the garage door can be opened from 20 yards away, but the gate only 5 yards away. A big but consistent difference in distance. So I don't really have longer range with the OVMS, I can just push the button further away from the gate/garage. But the gate/garage starts opening the same distance from the car whether I use the OVMS or car Homelink button. The OVMS just seems a lot cooler! Go figger. My reply: Comments here about OVMS homelink vs VDS homelink are bizarre. The OVMS homelink just sends exactly the same codes as the VDS homelink. The reason I know is because we got the codes by looking at those sent by the VDS. The codes are sent on the CAN bus to the homelink unit, which then just does the transmission. Perhaps this is a "bug" in OVMS? Perhaps there is a "start homelink" and "stop homelink" code and we're only sending the first one. I'll raise it on the developers forum. The code descriptions we have are: Home Link B1=0x09 B2=0x00 B3=Homelink device (0x00, 0x01 or 0x02) N.B. mstegen is also seeing another message on the CAN bus just before this message, 0x09 0x02 0x00, not sure if it's important. markwj suspects perhaps some sort of wakeup message. Mstegen (or someone else with can-usb and homelink) - can you have a double-check of this. If you press the VDS homelink button, what _exactly_ do we see? Is it 09/02/<device> then 09/00/<device>, or 09/00/<device> then 09/02/<device>? Is there any difference if you hold down the VDS homelink button? Thanks, Mark.

1 0

Re: [Ovmsdev] Android App
by Mark Webb-Johnson 07 Feb '13

07 Feb '13

Just a note to acknowledge all the submissions I've had (both personal and to the list) on the Android App. Thanks for your help testing this. I'm not individually acknowledging each feedback message, to keep the volume of messages on the list reasonable. I am collecting all the feedback. Most of the points made so far are very quick and easy to fix. Mostly just cosmetic. I hope to get another update, with these fixes made, over the weekend. So far, it looks like the App works just fine, and I don't think we need many more betas. I may just try to make the arrangements to get it into the Play store directly. Regards, Mark. > Von: ovmsdev-bounces(a)lists.teslaclub.hk [mailto:ovmsdev-bounces@lists.teslaclub.hk] Im Auftrag von Mark Webb-Johnson > Gesendet: Montag, 21. Januar 2013 14:58 > An: OVMS Developers > Betreff: [Ovmsdev] Android App > > > I'm glad to be able to (finally) announce that the new Android App is finally ready for public beta. We're calling it v3.1.1. > > The source code is all in github (for the brave), and there is an APK that can be side-loaded on Android devices, via this link: > > http://www.openvehicles.com/downloads/OVMS.3.1.1.beta.apk > > Functionality wise, it is pretty much on a par with the iOS App. All the core functions are there and, most importantly, the virtual car layer is complete and up-to-date. We've got HOMELINK support (yay!) as well as all the new function and parameter settings. It does have the artwork for the Volts and Amperas, but no Twizy yet (sorry, that slipped through the cracks, but we'll get it in the next build). The App should support any 2.3+ Android phone, and should scale its displays to pretty much any resolution out there. Tablet support is implemented by making them look like big phones. > > There are a few things still incomplete (as previously pointed out at the start of this project): > > No social group support on the map > No cellular usage > Some recent artwork missing (this is easy, and will come in the next beta release) > > These will come, but weren't considered essential for this first release. The most important is to get the Android App up to the same level of functionality as the iOS App, so that they can both be brought forward. > > I think if you want to install this, you first need to uninstall the Play store version. You will probably have to re-setup your vehicle as well. If you have problems with the beta, you can always uninstall it, and roll-back to the Play store version. > > Please send feedback back to this list. > > Regards, Mark. > >

4 9

Model S (and other) APIs
by Mark Webb-Johnson 03 Feb '13

03 Feb '13

I've been interested in the possible use of OVMS Apps to control multiple cars of different types - not necessarily just with OVMS modules. This allows us to extend the manufacturer's offering, and is real nice for those with more than one car in their garage. GM/OnStar now have a published API (although are not permitting this to be used against real cars until late 2013). The Leaf carwings API has been reverse engineered. Now, some guys are reverse engineering the Tesla Model S RESTfull API. http://www.TeslaMotorsClub.com/showthread.php?t=13410 http://docs.timdorr.apiary.io/ Perhaps the neatest way of doing this is by gatewaying at the server - no change to Apps necessary. But, I worry that the providers will rate limit requests from a single IP. Doing it at the server allows for all sorts of cool stuff (e.g.; timed pre-heat). We could also do this in the Apps themselves. But, my question is what is the legality of this? I suspect that it would be a contravention of the DMCA? I read that GM/OnStar stopped (or persuaded to stop) the VoltStats guy to stop - and he is now using a very restricted API just for him. What about Nissan? Looking at the Model S API, it would be about an evening's work to do a server gateway. Scarily simple. Regards, Mark

1 0

Power usage / sleep mode
by Michael Balzer 02 Feb '13

02 Feb '13

Mark, List, yesterday my Twizy was temporarily dead... because of the OVMS power usage. I had not driven for 5 days. The Twizy has a very small 12V battery with only 14 Ah capacity, and it only gets charged while charging the Twizy and while driving (from the main battery). The OVMS with GPS activated needs a constant current of ~110 mA according to my measurement, thus sucking that battery empty within 4-5 days, maybe fewer. I'll make the power warning much more prominent in the Twizy user guide. Have there been any considerations yet about using the sleep mode of the PIC and/or SIM chipset? Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

3 25