April 2013 - OvmsDev - Open Vehicles

i-Miev/C-Zero/iOn
by Thomas Bergo 25 Jan '14

25 Jan '14

Hi As a owner of a i-Miev I'm interested in OVMS support for the i-Miev/C-Zero/iOn EV. Has anyone looked into supporting those EV? I'm planing to start looking into adding support for those EV. And asking for help to add a vehicle plug-in module stub for those cars, so that naming and so on is correct. Best regards Thomas B

15 105

Re: [Ovmsdev] OVMS VIN 4E9->4F1->4E1 (was OVMS VIN 4E9->4F1)
by Mark Webb-Johnson 07 Aug '13

07 Aug '13

Michael, OK. I found some old logs you sent me before and these show: 7.628 R11 4E9 E1 80 00 04 6C 00 7.637 R11 514 47 31 52 39 36 45 34 39 8.647 R11 4F1 41 A1 01 A1 00 36 08 88 The 514 looks fine. But, both 4E9 and 4F1 look wrong. In particular, the 4F1 has '41 A1 01 A1 00' - which is what we are seeing for your VIN. But, id #4E1 has: 8.694 R11 4E1 43 55 31 31 36 34 38 39 If the VIN was in 4E1 and 514, that would give us: 8.694 R11 4E1 43 55 31 31 36 34 38 39 7.637 R11 514 47 31 52 39 36 45 34 39 Or, CU116489G1R96E49 for your car. For RScott, his logs show: 41966.094 R11 4E1 42 55 31 30 32 36 38 39 41966.110 R11 514 47 31 52 44 36 45 34 36 Or, BU102389G1RD6E36 for his car. Is that correct? Reading back through the old eMails, I find this from RScott: > The VIN can be constructed by taking the number "1" and converting the CAN IDs 4E9 and 514 to ASCII. So with "4E1 4255313032363839" and "514 4731524436453436", you would end up with 42 55 31 30 32 36 38 39 47 31 52 44 36 45 34 36, where 42 is ASCII for B, 55 is U, etc. So, I think the whole 4E9 was just a typo, as 4E1 is what is mentioned later in the same sentence. I've committed the code with 4E1 into github now. It works ok on my simulator, and hopefully should be ok in your car now. Can you try? Regards, Mark. On 26 Dec, 2012, at 9:12 PM, Mark Webb-Johnson <mark(a)webb-johnson.net> wrote: > Michael, > > I've put this up on my test bench, set to VA vehicle type, and setting my simulator to 500Kbps CAN speed, then transmitting the following three messages once a second: > > ID#206 A0 10 00 00 00 00 00 00 > ID#4F1 42 55 31 30 32 36 38 39 > ID#514 47 31 52 44 D6 45 34 36 > > Then, with the module in SETUP mode, I get: > > S MODULE? > # Module: > VehicleID:TESTCAR > VehicleType:VA > Units:K > Notifications:IP > > DIAG > # DIAG > > # Firmware: 2.1.1/VA/V2 > # SWITCH: 1 > # 12V Line: 14.0 V > # Signal: 0 > > # VIN: BU102689G1RD6E46 (VA) > # SOC: 64% (0 ideal, 0 est miles) > > That all looks ok. > The message from your car is: > > GERMANVOLT rx msg F 2.1.1/V2,A??,24,0,VA,E-Plus > > 00000040 20 6d 73 67 20 46 20 32 2e 31 2e 31 2f 56 32 2c | msg F 2.1.1/V2,| > 00000050 41 a1 01 a1 2c 32 31 2c 30 2c 56 41 2c 45 2d 50 |A...,21,0,VA,E-P| > 00000060 6c 75 73 0a |lus.| > > Your VIN is showing up as 41,A1,01,A1 - as you say: wrong. > > But, the firmware version and car type look ok. Not sure why they would not show up in the App. Perhaps the corrupt VIN# is messing up interpretation of that message? Perhaps the high bit on the A1 is messing it up. > > Not sure what is going on in your car itself. Can you check any captures you have for the exact id#4F1 and id#514 messages you have, and let me know? > > Regards, Mark. > > On 21 Dec, 2012, at 9:33 PM, mikeljo(a)mac.com wrote: > >> Hi, >> >> thanks. >> >> Works. Get the correct infos from my car. >> Implement the SOC calculation from my previous mail. >> >> - GPS ok >> - SOC ok >> >> BUT: >> - no VIN >> - No Car Type >> - no car firmware >> >> Here some Pics from the App: >> >> <IMG_1075.PNG> >> <IMG_1076.PNG> >> <IMG_1077.PNG> >> <IMG_1078.PNG> >> >> >> The App is the 1.3.2 compiled from the git. This is NOT the one from the Store!? >> >> BTW: You see the GSM Signal is -113dBm. When one door is open i got -87dBm. Heavy attenuation. >> I think i must mount the antenna outside the car. GPS is ok. >> >> >> Bye >> michael >> >> >> Am 21.12.2012 um 02:19 schrieb Mark Webb-Johnson <mark(a)webb-johnson.net>: >> >>> Michael, >>> >>> Parameter #14 (PARAM_VEHICLETYPE) holds the selected vehicle type. This can be set either from the smartphone apps, or via the SMS MODULE command. >>> >>> Regards, Mark. >>> >>> On 21 Dec, 2012, at 4:31 AM, mikeljo(a)mac.com wrote: >>> >>>> Hi, >>>> >>>> i checked it out. It compiles without error. >>>> But i think i missed something: how to switch between the cars? I know you do something, but couldn't find the howto. >>>> I found the ROM Parameter "VA" in "vehicle.c", but how to put this in the ROM? >>>> SMS Command? >>>> >>>> Sorry. >>>> >>>> Bye >>>> Michael >>>> >>>> >>>> Am 20.12.2012 um 15:08 schrieb Mark Webb-Johnson <mark(a)webb-johnson.net>: >>>> >>>>> Michael J: >>>>> >>>>> The following commit should fix this: >>>>> >>>>> * 269cd4f (HEAD, origin/master, origin/HEAD, master) Ampera VIN 4E9->4F1 >>>>> >>>>> Can you check the code now in master head, and see if it has everything you need. It builds and compiles on v2 hardware, but you'll need to change the compiler flags to get it building on v1 (just change TESLAROADSTER to VOLTAMPERA). >>>>> >>>>> What was the end result of the SOC range changes? Any ideas on the solution? >>>>> >>>>> Regards, Mark. >>>>> >>>>> On 6 Nov, 2012, at 5:28 AM, mikeljo(a)mac.com wrote: >>>>> >>>>>> Hi mark, >>>>>> >>>>>> do you think at the VIN? >>>>>> >>>>>> 1 + 514 + 4F1 >>>>> >>>> >>> >> >

11 85

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

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

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

Topping off twizy
by Nikki Gordon-Bloomfield 29 Apr '13

29 Apr '13

Hi folks, Just noticed a bug with the release firmware which sets the topping off flag when the car reaches 10 percent. Any thoughts? Nikki P.s. Michael, could you please send me the twizy firmware I should have right now? Want to make sure I have the latest version! N Sent from my iPhone

2 6

App messages stopped
by Michael Balzer 28 Apr '13

28 Apr '13

Mark, I do not get any new messages or message notifications from the Android App. Messages are sent correctly by the car and can be seen using the perl client, but the App ignores them. My message tab has become *huge*. Maybe some list storage limit has been reached? Is there a way to discard old messages? Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

2 6