June 2013 - OvmsDev - Open Vehicles

OVMS logo
by Mark Webb-Johnson 06 Jun '17

06 Jun '17

We need to change the OVMS logo, to better reflect the vehicle independence. The existing logo is too much Tesla. Felix has kindly prepared a couple of options for us, attached below. My preference is for the one with the car outline (even though it retains a hint of Tesla), as it emphasizes the vehicle comms aspect. This is quite urgent, as the Teslive people are pushing for artwork. What do you guys/gals think? Regards, Mark

8 14

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

24 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

Twizy to C-Zero
by Nikki Gordon-Bloomfield 01 Jul '13

01 Jul '13

All, I'm just about (hopefully) to sell my Twizy back to the dealer after yet another fault. (Two service light errors and one broken window) I'm likely to switch to either Volt or C-Zero. The latter is my choice, since it's all electric and substantially cheaper to buy. But the Volt may also get a look in if the dealer gives me a good deal. Here in Europe neither have any kind of telematics. I know the Volt is pretty well supported these days. What of the C-Zero? Did anyone start logging? If I do get one, I'm happy to log stuff, but I'll need help decoding it as I'm not very experienced as a coder. I'm more of a…hacker. ;) Nikki. P.S. Renault is trying to blame the two logged errors on my Twizy (multiplexing bus) with OVMS. Know any reason why it would cause any issues? It's not set to write to CAN bus anyway…

3 2

Re: [Ovmsdev] Twizy to C-Zero
by Denis KRAUTH 28 Jun '13

28 Jun '13

Hi Nikki, As an Ampera owner, I have to warn you: if you test drive à Volt, you will order one :-) And the European Ampera/Volt community would love to have you on board: there is still some hacking to do. Denis. Nikki Gordon-Bloomfield <nikki(a)littlecollie.com> a écrit : >All, > >I'm just about (hopefully) to sell my Twizy back to the dealer after yet another fault. (Two service light errors and one broken window) I'm likely to switch to either Volt or C-Zero. The latter is my choice, since it's all electric and substantially cheaper to buy. But the Volt may also get a look in if the dealer gives me a good deal. > >Here in Europe neither have any kind of telematics. I know the Volt is pretty well supported these days. What of the C-Zero? Did anyone start logging? > >If I do get one, I'm happy to log stuff, but I'll need help decoding it as I'm not very experienced as a coder. I'm more of a…hacker. ;) > >Nikki. > >P.S. Renault is trying to blame the two logged errors on my Twizy (multiplexing bus) with OVMS. Know any reason why it would cause any issues? It's not set to write to CAN bus anyway… > > >_______________________________________________ >OvmsDev mailing list >OvmsDev(a)lists.teslaclub.hk >http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

1 0

DIAG port to bluetooth
by Giannis Bakas 27 Jun '13

27 Jun '13

Hi all, is it possible to use a serial to bluetooth dongle on the DIAG port of the module to get data via bluetooth, requesting data with "MSG commands"? What I want to do is to use OVMS like a bridge between my car and my parrot device (Android device) in order to visualize the data I get to the screen. I want to avoid the SIM card and to get data from the server. Best regards, Giannis

2 7

missing the charge connector icon
by Kevin Sharpe ZCW 16 Jun '13

16 Jun '13

I've noticed a number of times that the iPhone app is missing the charge connector icon when a Tesla Roadster standard mode charge has completed. Interestingly, the app is still showing the charge port as white on the 'car' tab indicating (I guess) that power is connected. Removing the connector from the car, closing the flap, opening the flap, and reconnecting will allow the app to recover and continue displaying the connector icon as normal. Sending a chargestart text message will also work (sometimes). I'm using app version 1.3.5 (20130604) and firmware 2.3.1/TR/V2 A stat text returns "Standard – Charging Stopped" Any ideas what's wrong? [cid:B0D1D290-4E82-451F-A385-688AD637CCB9] [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe(a)zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347

2 1

Good News, Everybody!
by Nikki Gordon-Bloomfield 11 Jun '13

11 Jun '13

Just downloaded iOS 7 Beta, and everything from OVMS works :) Nikki.

2 1

Open Vehicles iOS 1.3.5 (20130604)
by Mark Webb-Johnson 07 Jun '13

07 Jun '13

I have just released an experimental build of the Open Vehicles iOS App. This includes Open Charge Map (OCM) integration support. Please note that there is no roll-back procedure for this build. You may be required to un-install and re-install the App again at a later stage (losing settings, and thus having to re-setup your vehicles). We would appreciate your help with testing this build, in particular your participation in this test will allow us to get valuable feedback on any crashes experienced. Regards, Mark. Platform: iOS Version: 1.3.5 (20130604) Team: Open Vehicles Release Date: June 4, 2013 Size: 18.0 MB Expires: 5 months, 2 weeks

5 7

Strange Twizy Message.
by Nikki Gordon-Bloomfield 06 Jun '13

06 Jun '13

Hi guys Just got the following message from my car: "Volts: !SD:4075mV !C1:+4075mV Temps: !SD:225C !M1:-1C" It's about 10 degrees C right now, and SOC is reported as 82 percent. Any ideas what's going on? I can tell the voltage is okay… but the temperature warning??? Nikki.

2 2