- OvmsDev - Open Vehicles

Android App release
by Michael Balzer 13 Dec '15

13 Dec '15

I haven't got any bug reports from users regarding my V3.11 beta releases. I've only had some occasional minor icon layout issues with my five year old Android 2.3 device, but no problems with my newer devices. So I think we can release the current version to the play store. Mark, do you need some more info for this? A summary of changes since the last public release? Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

3 11

Kia Soul EV version 0.1
by Robert Cotran 13 Dec '15

13 Dec '15

Hi all, I'm replying to Micheal Balzer's email from yesterday. I wasn't on the mailing list until late yesterday afternoon, hence I'm not able to click reply. I've got a Kia Soul EV 2016 in Canada which doesn't have the UVO services, so this is of great interest to me. I have the OVMS kit in front of me, but I'm a total newbie, so I'm reading through some guides to get started. Just wanted to say that I'll gladly be the guinea pig for this. What I'd REALLY like is to have a way to remotely turn on the climate control system to warm up/cool down the car at will. Hopefully that's a remote possibility. Tracking it is cool, but controlling it is even better. I'm used to a Tesla (my other car), so I am quite spoiled. I did get Micheal's firmware installed on the OVMS and hooked it up to the car but it's not booting properly (based on status LEDs). Can that be because of the firmware or is the bootup sequence separate from the car-control code? The LEDs flash like - 10 Green, 9 Green, 10 Green, 9 Green, then a few reds, then green and red flash together really fast. I tried sending text messages to the board and no dice. Any help would be appreciated, looking forward to getting this working! Robert

6 25

Add ChaDeMo and CSS to car_chargemode
by Geir Øyvind Vælidalo 09 Dec '15

09 Dec '15

Hi guys, I would like to have ChaDeMo and CSS added to car_chargemode, and maybe Type 1 and Type 2 too. Then we can display those names in the apps and maybe even add images for those charge plugs. I would propose this: 0x00 - Standard 0x01 - Storage 0x02 - ??? 0x03 - Range 0x04 - Performance 0x05 - ChaDeMo 0x06 - CSS 0x07 - J1772 Type 1 0x08 - Mennekes Type 2 What to you guys think? Would it be problematic for the server and/or apps if suddenly the Kia Souls stated sending chargemode 0x05? Best regards, Geir

7 9

Twizy 45 data request
by Michael Balzer 06 Dec '15

06 Dec '15

@Twizy 45 owners: I need the following SEVCON register data to prepare a new tuning option: CFG READ 6075 00 CFG READ 4641 02 Thanks! Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

3 8

Building with free C18 compiler
by Matt Beard 19 Nov '15

19 Nov '15

Have I missed a decision to no longer support the free C18 compiler - or has it been like that for ages? I am trying to fix an issue in the iMiev code, but can no longer build 2.6.5 due to needing the full compiler and no way am I paying £300 for it. Matt Beard

9 13

C2DM is deprecated, no new sign-ups
by Lee Howard 16 Nov '15

16 Nov '15

I've got my own OVMS server going. However, I wasn't seeing notifications on my phone (Android) since moving away from tmc.openvehicles.com. Looking at the ovms_server.pl code it appears that ovms_server.conf requires this section: [c2dm] email=<email> password=<password> accounttype=<unknown> [This "c2dm" section, along with the "server", "master", and "log" sections are undocumented in the docs/HOWTO.server.txt file.] Okay, so it would seem that I need to set-up a C2DM account with Google and put that info into the conf file. But, Google has deprecated C2DM in favour of Google Cloud Messaging (GCM), and Google is not granting any new C2DM accounts... http://developer.android.com/google/gcm/c2dm.html Is the C2DM account used by tmc.openvehicles.com a generic account that can be used by other OVMS servers? I suspect that it is a private account. If so, then push notifications for Android users on independent servers will necessarily require a transition to GCM. Thanks, Lee. -- *Lee Howard* *Mainpine, Inc. Chief Technology Officer* Tel: +1 866 363 6680 | Fax: +1 360 462 8160 lee.howard(a)mainpine.com | www.mainpine.com

4 10

Need help with CAN-polling.
by Geir Øyvind Vælidalo 15 Nov '15

15 Nov '15

Hi guys, I have a problem with getting the OVMS to fetch TPMS data from my Kia. This is what I do to get the data using ELM327 and a “terminal” on my iPhone: >atcra 7de OK >21 06 7DE 10 22 61 06 00 25 A7 CB 7DE 21 00 37 00 00 00 25 3E 7DE 22 93 00 37 00 00 00 25 7DE 23 9D F5 00 37 00 00 00 7DE 24 25 3F 65 00 37 00 00 It returns the data I need, but when I add this to the poll-list in OVMS: { 0x7df, 0x7de, VEHICLE_POLL_TYPE_OBDIIGROUP, 0x06, { 60, 10, 0 } }, // TMPS I get no response :-( I’ve tried different module id’s but I don’t quite understand which one the ELM uses. I’ve added several other polls without any problems to the Kia code, and I’m pretty sure the problem isn’t in the poll0-code, as i’ve only added a case 0x7de, and it never seems to trigger. Any tips or ideas? Best regards, Geir

2 2

Kia Soul EV development
by Michael Balzer 01 Nov '15

01 Nov '15

List, I'm pleased to introduce the dedicated OVMS Kia Soul developer (he should have subscribed by now): please welcome Geir :-) > Gesendet: So 1. Nov 2015, 00:32 > Von: goev_no05 > An: dexter > > Hi Michael! > > I've been playing a lot with the code today :D It works quite well, > although the VIN is shifted three bytes so I'm missing the first > characters. The DEBUG 1 and 5 seem to be off too, but it just seem > like they might be off by only one byte. I think so because I can > fetch the aux battery voltage from row 4 byte 4, instead of byte 5 as > should be expected. This is a little strange as it seems to be the > same code as VIN. But I will look into these matters tomorrow! > > I've added a lot of new data to your code: In my version I now show > the correct SOC (V0.2 shows the BMS SOC which is around 4% lower), > Odometer, aux battery voltage, correct charging power (it looks right > at least for 230V systems). I'm also setting the charging modes based > on the charging power and I copied the Range/Ideal range code from the > Twizy and adapted it to the Kia. I think I will copy the CA-setting > too, as they seem to be quite useful. > > I feel that I have quite a good understanding of the system now, so if > you want, I can relieve you from the Kia Soul-development :) > > I am also subscribing to the ovms-developer list, so hopefully I don't > need to bother you here anymore ;) > > Good night, and take care! > > Geir As the OBD polling support for modes 02, 10 & 21 basically works, I now have pushed my latest changes including Kia V0.2 to the main repository. The Kia VIN currently needs to be cut by 3 bytes because the car_vin can only take 17 chars. As RAM is tight I decided to omit the first three chars. There would be space for a 20 bytes car_vin, but then the VIN is not that important IMO. You're right, the aux battery voltage should be in row 4 byte 5, and there is no intended offset, so that might be a bug. Glad to have you on board :-) Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

3 2

Twizy release 3.6.1
by Michael Balzer 28 Oct '15

28 Oct '15

Package: http://dexters-web.de/f/tw/OVMS-Twizy-3.6.1.zip Changes: see tag "V3.6" in the user guide Framework V2.7.4: - New compiler switches to disable framework functions: OVMS_NO_CHARGECONTROL OVMS_NO_CTP OVMS_NO_SMSTIME OVMS_NO_VEHICLE_ALERTS (all need to be set for Twizy build) - Potential buffer overflow fix in net_msg_forward_sms() - Fix stp_l2f() for negative values - Fix SMS MSG wrapper for long commands Framework V2.8.1: - Make COPS more lenient - Support GPRS DNS Twizy V3.6.0: - New: All power values now based on real battery power (current * voltage) - Battery current sums + min/max moved to separate fields - STAT command extended by grid energy drain estimation - RT-GPS-Log extended by BMS limits, auto power levels and battery current min/max - RT-PWR-Log extended by battery coulomb counts (Ah) - "RT-PWR-UsageStats" is now "RT-PWR-Stats", fields reordered and units converted (to save space), coulomb count discharge/charge sums added (Ah) - Rework & bug fixes in auto power adjustment - Auto RECUP power adjustment extended by 100% reference power (ATT: CFG RECUP parameters changed!) - New: auto DRIVE power adjustment (ATT: CFG DRIVE parameters changed!) - New: CFG CLEAR = clear SEVCON diagnostic logs - Now using GSM time (NET_FN_CARTIME) for more accurate parking times - New: feature #14 & 64 = send notification on charge starts - Fixed charge time estimation for SOC > 94% - ISR performance optimization - car_SOC no longer rounded to avoid 99.5% == 100% - Trip end odometer saved & used for RT-PWR-Log charge entries - Fixed auto power minprc calculation with default (-1) - Fixed auto power calculations for default minprc values - Changed auto recup level to scale levels configured - car_SOC no longer rounded to avoid 99.5% == 100% - Trip end odometer saved & used for RT-PWR-Log charg Twizy V3.6.1: - Fix: battery alert state also remembered for IP notification - Fix: compiling without OVMS_TWIZY_CFG - ideal range calculated with temperature influence approximation - Battery capacity estimation - Charge start restarts SOC window (to get most recent BMS SOC) - Charge interruption no longer restarts power sums & SOC window -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

4 4

Kia Soul EV version 0.1
by Michael Balzer 07 Oct '15

07 Oct '15

Hi everyone, I just checked in the initial version of the Kia Soul EV vehicle support: https://github.com/openvehicles/Open-Vehicle-Monitoring-System/commit/803e4… This is completely untested, as I do not have a Kia Soul to test with, and Alex and Tyrel who did the CAN analysis do not have their OVMS modules yet. If anyone has the option to test this, the firmware build is here: http://dexters-web.de/f/kiasoul/OVMS-KiaSoul-0.1.zip Vehicle ID is "KS". CAN write access is necessary only for the VIN, which is fetched using the framework OBDII poller. Of course, a code audit is also very welcome. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

1 0