- OvmsDev - Open Vehicles

TESLIVE
by Mark Webb-Johnson 12 May '13

12 May '13

As you may be aware, there is a TESLIVE (Tesla Motors Club / Tesla Motors Corp collaboration) event coming up in Fremont, California - 12th, 13th and 14th July 2013. OVMS has been offered a booth (to show what we have and do), but I can't make it. I would love to go, but it is just bad timing for me, as well as an awful long way to go just for this event. So, I'm opening it up - anyway interested in handling this for us? Based on the limited information I've been given, the expo part of the conference will be on two of the days and the booth would have to be manned for three or four hours on each of those two days. It would mean manning the booth, demonstrating OVMS, perhaps offering firmware upgrades and/or installation advise. You would also get to attend the event itself. Open Vehicles would pay for the booth, as well as one attendance fee for whoever does this for us (assuming you are one of the lucky 300 - and I'm not sure if exhibitors get priority or need to pay for the conference part). If more than one wants to do it, that is fine by me - share the load (and discount the attendance). Supposedly we'll know more about the exhibitor side of things on this coming Friday. Please eMail me (mark(a)openvehicles.com) or respond here, if you can help. Regards, Mark.

2 2

OVMS Android 3.1.3 - beta
by Mark Webb-Johnson 11 May '13

11 May '13

Need some help here. I just noticed that maps are not working on the google play version, because the api key is wrong. Good grief, google are driving me crazy. First they obsolete c2dm, so we can't get c2dm keys any more. That caused a month delay jumping through hoops to get the Play store app transferred between accounts. Then, we find that you need the original signing keyring to update a google play app, even if they transferred the app to you. That was another week of grief. Now, I find that the api v1 we are using for google maps has been obsoleted, so we can't get keys any more. And, I find that the api key it used is tied to the signing keyring (see [2], above). Arrgh! Goto step 5. Anyway, all hoops have been jumped through now, and I have a beta. It has: First draft French localisation First draft Dutch localisation First draft German localisation First draft Norwegian localisation Maps api key fix Experimental landscape support (ugly on small screens, but marginally better than nothing) One minor fix (to make it work on Parrot Asteroid) There are a few localisation strings not working, which I should have fixed tonight, and landscape is only marginally useful, but it is workable. I'd like to rush this (once localisation is ok) through beta on to play. The beta is available for side load at: http://www.openvehicles.com/downloads/OVMS.3.1.3.beta5.apk (for this specific beta) or http://www.openvehicles.com/downloads/ovms.apk (symlink to latest latest beta) It is signed with the latest Google Play key, so should be able to be installed over your google play version without any loss of data, and there won't be any of that double-notification c2dm mess from before. I'll try to keep future betas working the same way. Regards, Mark. P.S. There is something magical about sitting in my car, setting valet mode via my Parrot Asteroid SMART 2DIN head unit, and watching the VDS change.

1 0

Release Firmware
by Mark Webb-Johnson 08 May '13

08 May '13

China is bugging me for final firmware for the next batch of hardware. I need to get them this early next week. I've committed what I need for the Tesla Roadster (and framework). Last outstanding small change to make is to send CAC as 999.99, rather than the current 99999, using Tom's new library function. Michael B & J: can you check Twizzy and Volt/Ampera, to see if everything is ok with current firmware or there is anything you need changed? I plan to cut release candidate for 2.3.1 on Sunday. Regards, Mark.

4 30

Fwd: [Open-Vehicle-Monitoring-System] Driven km and Charge done message (#105)
by Mark Webb-Johnson 08 May '13

08 May '13

Michael (J), I merged this. I'm a unsure about the message when charge is done part. You have it set to alert whenever a charge completes (even if normally up to 100% SOC), which is not normally. We would usually only alert if the charge is interrupted. Michael B: What do you do for Twizy on this? Do we need a standard option that the user can set to be alerted whenever a charge is completed (no matter succeed / fail)? Regards, Mark. Begin forwarded message: > From: "Michael J." <notifications(a)github.com> > Subject: [Open-Vehicle-Monitoring-System] Driven km and Charge done message (#105) > Date: 3 May, 2013 3:55:48 AM GMT+08:00 > > Add CAN ID with driven km on Battery for calc for expected km > Add Messagen when Charhe is done > > Commit Summary > > Driven km and Charge done message > File Changes > > M vehicle/OVMS.X/net_msg.c (1) > M vehicle/OVMS.X/vehicle_voltampera.c (32) > Patch Links: > > https://github.com/markwj/Open-Vehicle-Monitoring-System/pull/105.patch > https://github.com/markwj/Open-Vehicle-Monitoring-System/pull/105.diff

4 6

Not OVMS, but perhaps interesting to some
by Mark Webb-Johnson 05 May '13

05 May '13

The one thing that really bugs me about the Parrot Asteroid SMART is the lack of physical volume control buttons. The roadster doesn't have steering wheel audio controls, so UNIKA is not a possibility. Parrot make a bluetooth steering wheel remote for the Asteroid tablet, but it won't work on the SMART (they say it will later this year). It is Android and that means the Parrot supports USB keyboards using the HID protocol. So: https://github.com/markwj/hidmedia Using a PIC18F2550 (US$6 @mouser) usb-capable micro controller, I threw together a workable hand built prototype. It has a d-pad, two function keys and a mode switch. At the moment, I've got it programmed as mode 0 directional control and mode 1 media control. In directional control mode, it behaves like up, down, left, right, enter, esc, menu, etc - useful for navigating around the Android screens. In media control mode, the two top buttons are volume decease/increase, and the others will be for previous song, next song, play/pause, stop, mute, etc. There is a little led that currently blinks when you press a key. Still some tuning to do, finding the correct media control codes, but not bad for a few hours work at the weekend - with my six year old daughter as a little helper she told me she wants to be me when she grows up :-) At the moment, volume control and directional control is perfect, but media pause/play and song navigation still a work-in-progress (I need to find the correct HID codes). Last thing would be to 3D print a nice box. Or, I could try to work out how that 4pin UNIKA connector works.

1 0

OVMS Android goes live
by Mark Webb-Johnson 04 May '13

04 May '13

@OpenVehicles: OVMS Android App back in Google Play - out of beta and supporting hi-res modern phones and latest EVs. https://t.co/7K8m0IeB27

1 0

OVMS TPMS on Tesla Roadster - New Jersey area
by Mark Webb-Johnson 30 Apr '13

30 Apr '13

We've got some users interested in looking at the CAN bus activity for the TPMS tool. The work will be in the New Jersey, USA, area. The users doing the work are experienced with Tesla and OVMS, but not developers and don't have any CAN-USB tools. Is there anyone in New Jersey with a CAN-USB adaptor, knowledge to tap the car bus, and time? Regards, Mark.

2 3

Woo hoo, play comes through
by Mark Webb-Johnson 30 Apr '13

30 Apr '13

After much struggling, the play store has come through with the changes they needed to make, and the OVMS Android app should be able to go back live on play tonight. I'll send the link when I have it. Existing users should automatically get upgraded (or sidegraded depending on how you look at it). Regards, Mark.

2 2

Charging and Driving Logs
by Mark Webb-Johnson 29 Apr '13

29 Apr '13

I have wanted to implement charging and driving logs, for some time now. The idea is the car will record 'drives' and 'charges' and report them back as historical records. This will be independent of the vehicle module, so should work for all supported vehicles. For each drive, we need: End time [4 bytes] Duration (seconds) [2 bytes] Drive mode [1 byte] Start location [8 bytes] End location [8 bytes] Distance driven [2 bytes] kWh used [2 bytes] For each charge, we need: End time [4 bytes] Duration (seconds) [2 bytes] Charge mode [1 byte] Charge location [8 bytes] Current available [1 byte] Current used [1 byte] Voltage [2 bytes] Result (completed, stopped, failed) [1 byte] kWh used [1 byte] That is 27 bytes per drive, or 21 bytes per charge. The problem is that GPRS connectivity may not be there at the end of the drive or charge, so we need to store these records. RAM would be good, but we only have 429 bytes left (and I think 256 bytes of that may be stack). EEPROM is also possible, but full of parameters at the moment. I'm thinking of using the top 4 parameters (#20 through #23) - these appear to be free at the moment, and would give us 128 bytes of permanent storage. Easiest would be 32 bytes for each record. This would be turned on with a FEATURE_CARBITS (suggestion: 0x80), so it would default off (for privacy). Comments / suggestions? Regards, Mark.

2 2

Parrots
by Mark Webb-Johnson 29 Apr '13

29 Apr '13

"Tesla Roadster - Any song, any time". Accompanying YouTube video: http://www.youtube.com/watch?v=1gYApR6PfyY&feature=player_embedded The blank space in the above pictures is for OVMS - once I get it working. This is no 17" display, but it is fully programmable, incredibly powerful, and just amazing for tech-heads. The thought of having OVMS running on this has me salivating... Some notes: I bought a US Parrot Asteroid SMART head unit, and Alpine HCE-C115 backup camera set. I rooted the parrot with Framaroot (I think I should rephrase that for our Australian readers, but what-the-heck). I SU'd the parrot with SuperSU. I installed the google frameworks and google play. Thence, google maps, youtube, etc. I use ADW Launcher Ex as my launcher, with ADW.Elegent theme. I use Android Speedometer as the speedometer display. I use Smart Volume Control+ for speed-based volume adjustment. I use PullOpen Settings for a pop-up volume control. I use TomTom for navigation (maps onboard), or Google Maps / Waze for Internet-based navigation. It has iGO for US-based users (maps onboard), but no iGO maps for Hong Kong (so I use TomTom). The facebook app is on, as it is needed by other apps which do facebook sign-on. No, I haven't 'checked in' to my car yet. Parrot Asteroid has Spotify and voice control apps available (either included or downloadable from their market), but I am experimenting with Utter as a very open and configurable solution. Spotify just launched in Hong Kong. US$6/month - any song, any time (tm). I got help installing this - just didn't want to mess with the roadster side of things too much. Had to re-wire a new audio harness, but everything needed was in the car (even though the head-unit side plug was the same, +12V and GND were the only two wires on the Alpine and Parrot harnesses that matched - all the others had to be swapped around). Mappings can be worked out by looking at the diagrams on the back of the Alpine and Parrot head units. An alternative to cutting-up the old Alpine-Tesla harness is to make an adaptor cable (1xfemale and 1xmale head-unit side connector and 16 wires). The backup camera in my car was a HCE-C107D, which only connects to Alpine head units. I purchased a discounted HCE-C115, which comes with a little adaptor box to convert the proprietary Alpine connector to standard RCA video (which then plugs in to the Parrot). There is a setting buried three deep in the advanced settings page of the parrot, which turns on/off the launching of the reversing camera app when you put the car in reverse. You can arrange how you want, but we put (a) the laptop cable (for rooting and sideloading) under the fuse box, (b) the 3G dongle in the centre console (using existing usb extension cable from Alpine), (c) the gps dongle able the car's speedometer cluster, and (d) the iPhone cable driver-side beside the steering wheel. We put the Parrot noise-cancelling microphone above the rear-view mirror (between the mirror and the root). A brilliant location (very hidden and very good sound pickup). Apps that come from Google Play are not tagged as usable when driving (even if they are), and the Parrot will stop you using them when not parked. Solution is to ground the parking-brake line at the head unit side to disable the nanny. Postives: Almost everything. Negatives: Only two: (1) There is no hard volume control (so I'm trying to work out a gesture based volume control that works in all the apps) - the pop-up volume controller is not amazing, and (2) I wish Parrot had just put standard stock Android on this with Google Play (rooting was not hard, but just a hassle). Conclusion: This is a unit for tech-heads, unless you are happy with the base functionality provided (iGO maps, Spotify and a currently-limited number of apps in the Asteroid marketplace). Regards, Mark.

3 3