- OvmsDev - Open Vehicles

Hello, & Nissan Leaf support
by Nigel Jones 29 Apr '14

29 Apr '14

Hey there....... I just wanted to pop in and give a quick wave... I've had my (leased) nissan leaf Gen.1 for 2 years and love it. I've got hold of a leafdd to keep a closer eye on battery level but am especially interested in OVMS for monitoring/recording data in near real time. I am aware there's no supported leaf support yet, though I do know some work was done. There's also been some work on the CAN bus(es) by the guy working on leafdd, and other projects over at mynissanleaf.com I'm a developer by background, even if my current job role is more around integration & architecture so there seemed to be a match here - has a leaf to try, interested in getting hands dirty with the code. So my plan is to get hold of some OVMS hardware, take a look through the code (I have done a git clone already), review this mailing list & see how I can contribute, specifically in terms of the leaf specific support. It's been a while since I've had the C compiler out but it used to be my bread and butter (mostly working on voice/telecoms systems including embedded HW, though much more sophisticated) Rome wasn't built in a day, and I have a full time job & other commitments but planning to give this a shot. It's only fair to mention I do work in IT for IBM UK, but this activity is purely on personal time (with agreement by my employer of no conflict of interest). Anyway - Hi! http://about.me/planetf1 -- ---- Nigel Jones

5 11

[Dev] SoC from logs
by Julien (JaXX) Banchet 29 Apr '14

29 Apr '14

Hello, This could be a question for Nikki, as it has been blogged at http://www.aminorjourney.com/?p=259 But having kept all of GPS and PWR logs for the last 6/7 months, I would love to enrich my database and thingspeak (http://things.tools.jaxx.org/) charts with a SoC level field. (my thingspeak is closed off for public, don’t wanna give away my cars’ availability for robbery ;-) ) And as silly as it may sound, I can’t see how to determinate that (without issuing a Stats? command by text), it’s probably right under my nose, but hey… It’s like lego parts, you never find the part you look for until you've moved on to something else. I’d extrapolate nice efficiency (W/km %/km) graphs Can anyone point me in any direction? Thanks in advance. -- Julien (JaXX) Banchet

2 1

Industry Attempting To Stop DIY EVSE
by Kevin Sharpe 31 Mar '14

31 Mar '14

Some interesting developments in the UK with an attempt by the UK EVSE Manufacturers to prevent DIY EVSE; http://speakev.com/threads/industry-attempting-to-stop-diy-evse.1615/ I intend to fight this but suspect it might be something for OVMS to watch closely. Kevin Sharpe | Founder & Patron | Zero Carbon World, a UK Registered Charity

3 5

Firmware 2.6.5
by Jack West 19 Mar '14

19 Mar '14

After upgrading to 2.6.5 (V2/TR) I am experiencing some trouble using ACC. Is there a revised document detailing commands and usage? I suspect user error. I downloaded 2.6.5 from Git and compiled myself. ACC PARAMS would not set an ACC location until I used the ACC HERE command. After successfully loading PARAMS and enabling ACC the charge appeared to start as planned. However the charge did not complete as it seems the car overrode the ACC command with a previously defined timed charge. It looks like virtually no charging took place even after the car's timer should have started. Possibly unrelated but maybe relevant is that the car would not start after unplugging charge cable. Charge port door had to be cycled and then car would start. I also notice what appears to be garbage in PARAMETER 15 (COOLDOWN). No cooldown commands have been issued and the garbage looks very similar to data in ACC location#1. No other ACC locations have been defined. Jack

2 2

v2.6.5 Firmware
by Mark Webb-Johnson 10 Mar '14

10 Mar '14

http://www.openvehicles.com/node/136 Vehicle firmware v2.6.5 has been pushed to github. It is tagged (as v2.6.5) and we have uploaded pre-built .hex files in the vehicle/firmware directory. 2014-03-10 2.6.5 Firmware 2.6.5 # Change car_tmotor to signed int # Call vehicle_fn_poll0() in OVMS_POLLER, if no poll list defined # Twizy release 3.2.0 # EEPROM CFG profile storage (3 custom profiles) # CFG profile management commands: LOAD, SAVE, INFO # CFG profile selection & display via simpl # Tesla Roadster: Treat TBattery as signed # ACC: Add a RADIUS parameter, supporting geo-fencing per acc locations # ACC: Route MSG commands through to ACC (for special handling) # ACC: Support charge, stop, and cooldown overrides 2014-01-19 2.6.2 Firmware 2.6.2 # Remove duplicate car_stale_* decrements in individual vehicle modules # Updates to vehicle_thinkcity # Mitsubishi: tbergo changes 1.5 ... 1.8 # Move can bus low level register access to vehicle.c, # (out of individual vehicle modules) # OBDII: Implementation using new vehicle polling framework # Structural changes to support new vehicle polling framework # Changes to crypt_md5 library to save 62 bytes of initialised ram # GSM clock polling, Request, and sync, GSM time # Fix to doors2 bits # Some work on nissan leaf # Fixed QC detection and 12V alarm issue # Twizy V3.0.2: CFG TSMAP allows 0..100 for levels 2..4 # Twizy version 3.1.0: # TSMAP: levels 1..4 now allow 0% # Power map generator extended for pwr max lo/hi, added sanity check # Renamed command "POWER" to "DRIVE", "TORQUE" to "POWER", # Changed param handling # Twizy 3.1.1: # SDO segmented upload support (readsdo_buf) # new command: CFG READS (read string), CFG WRITEO (write only) # Error counter hardening (counter reset by CFG command) # Twizy V3.1.2: # access to SEVCON logs / monitoring # new command: MSG 209 = CMD_ResetLogs # new command: MSG 210 = CMD_QueryLogs # active faults log included with fault alert # added Twizy client scripts # Switch to extended mode compilation # car_ambient_temp, car_tpem, car_tmotor and car_tpms_t to signed int

1 0

Compilation issues, OVMS.X/v2_RT with Battmon and Cfg
by Julien (JaXX) Banchet 03 Mar '14

03 Mar '14

Hi, Willing to use Michael’s last commit featuring "save/load sevcon profile » commands, I pulled the latest code and went to MPLab X IDE v2 (c18 v3.40). Alone it compiles fine. But if I add OVMS_TWIZY_BATTMON and OVMS_TWIZY_CFG (to a duplicated from V2_RT_Production conf) to the definitions I end up on a : "/Applications/microchip/mplabc18/v3.40/bin/mplink" -p18f2685 -w -m"build/memorymap" -u_EXTENDEDMODE -z__MPLAB_BUILD=1 -u_CRUNTIME -l "/Applications/microchip/mplabc18/v3.40/bin"/../lib -o dist/Copy_of_V2_RT_Production/production/OVMS.X.production.cof build/Copy_of_V2_RT_Production/production/UARTIntC.o build/Copy_of_V2_RT_Production/production/crypt_base64.o build/Copy_of_V2_RT_Production/production/crypt_hmac.o build/Copy_of_V2_RT_Production/production/crypt_md5.o build/Copy_of_V2_RT_Production/production/crypt_rc4.o build/Copy_of_V2_RT_Production/production/led.o build/Copy_of_V2_RT_Production/production/net.o build/Copy_of_V2_RT_Production/production/net_msg.o build/Copy_of_V2_RT_Production/production/net_sms.o build/Copy_of_V2_RT_Production/production/ovms.o build/Copy_of_V2_RT_Production/production/params.o build/Copy_of_V2_RT_Production/production/utils.o build/Copy_of_V2_RT_Production/production/inputs.o build/Copy_of_V2_RT_Production/production/diag.o build/Copy_of_V2_RT_Production/production/vehicle_twizy.o build/Copy_of_V2_RT_Production/production/vehicle.o build/Copy_of_V2_RT_Production/production/vehicle_none.o build/Copy_of_V2_RT_Production/production/logging.o MPLINK 4.40, Linker Device Database Version 1.3 Copyright (c) 1998-2011 Microchip Technology Inc. Error - section 'VEHICLE' can not fit the section. Section 'VEHICLE' length=0x00000043 Errors : 1 make[2]: *** [dist/Copy_of_V2_RT_Production/production/OVMS.X.production.hex] Error 1 make[1]: *** [.build-conf] Error 2 make: *** [.build-impl] Error 2 Can actually all the Definitions fit ? Am I doing anything wrong or is my setup wrong? Thanks, Julien. PS: Twizy ravaged friday night, they took everything but the OVMS, breaking the glovebox, including half of the smartphone holder making it useless even for the stealer… cool :( -- Julien (JaXX) Banchet

2 2

EMC / CE certificate + Fasttech SimpleConsole?
by Michael Balzer 24 Feb '14

24 Feb '14

Hi everyone, the SimpleConsole stirrs up a lot of new requests and interest over here. Most german users though would like to buy a pre-configured ready-to-use OVMS package for the Twizy (I suppose it's similar for other vehicles and countries). Unfortunately reselling the OVMS is not legal in the EU, because the hardware lacks the CE / EMC (electromagnetic conformity) certificate. I am happy with the OVMS staying an explicit hobbyist project, but a CE / EMC certificate would at least make it possible to sell an OVMS package if the user explicitly accepts that there are no warranties. Is there any chance this could happen? A german hardware developer took the OVMS (V2) to his EMC laboratory, with (his words) disastreous results -- he literally blasted the PIC with some required EM pulse test... Also, a professional SimpleConsole build from Fasttech would be really cool and helpful. What is required for this? Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

7 14

Nissan Leaf
by Mark Webb-Johnson 23 Feb '14

23 Feb '14

Attached is a first-run at Nissan Leaf support, with a few values read from the bus passively: Speed Headlight status Park / Drive status SOC I’ve also pushed this to github (along with a large number of other small changes). The Nissan Leaf support is proving really hard for me. I don’t have the car, or much CAN bus data, and the public documentation is contradictory and incomplete. End result is that I am just guessing, and completely unable to test my guesses. Anyway, please try it and let me know if any of those figures show up with any sense of accuracy at all. Going forward, I really need some CAN bus dumps from a Nissan Leaf. Specifically: Car idle Car plugged in and charge started Car charging Charge interrupted Driving Driving as close to a constant speed of 10 kph as possible Driving as close to a constant speed of 20 kph as possible Driving as close to a constant speed of 30 kph as possible Car parked, but on Car parked, coming out of park into drive gear Car stopped, coming out of drive gear into park Car in park gear, then handbrake applied For each of those, both with and without a T connector and LeafSpy running would be helpful. I’m guessing the logs can be gotten from monitor-all mode with an OBDII adaptor. There is not too much data on the can bus and that should be fast enough. If anyone can help with the above, please let me know. Regards, Mark.

9 20

Re: [Ovmsdev] Twizy release 3.2.0, binary params, SimpleConsole
by Julien (JaXX) Banchet 17 Feb '14

17 Feb '14

Repost/reply to the ML since non-personnal and worthy, (damn reply button :-/ ) ------------------------------------------------------ De: Michael Balzer dexter(a)expeedo.de Répondre: Michael Balzer dexter(a)expeedo.de Date: 16 février 2014 at 18:00:38 À: Julien (JaXX) Banchet jaxx(a)jaxx.org Sujet: Re: [Ovmsdev] Twizy release 3.2.0, binary params, SimpleConsole > Hi Julien, > > Am 16.02.2014 16:46, schrieb Julien (JaXX) Banchet: > > Again, « woohahaaaa!!! » I suppose, without diving into the code, that it can only switch > non-pre-op needing settings (recup for instance, tsmap/ramps, not power/speed), > and that’s a Sevcon « limitation » ? > Yes, but I check what can be done depending on the Twizy state and do > that -- see user manual. Yep, gathered that from the code too since :) Lots of conditionnal checks :) > > > What can we do with the DIAG port ? I’ve read in some commits that, because of lack of memory > headroom, it has lost some functionality… > > I have dozens of arduino/atmel based boards, some MiniPro sized with onboard rf12b > radios for extra connectivity and I would like to build an alarm system (and why not have > extra environmental sensors) that, with the help of the DIAG port, would send me SMS alerts > along with the car protecting itself on demand (Electrocution, Poisoneous Gas, abrasive > steel cable to cut a hand off etc…). > > Would it be possible that the DIAG port still exposes comms with the GSM stack (if it isn’t > RX only) ? > > Could it be logged to OVMS under a RT-CUSTOM-A/B/C... log ? > > > > Sorry but besides a few initial settings, I’m kinda bit lost to what’s possible to do > with the DIAG port. > Well, that's something you better post on the list, but basically the > DIAG port just taps the communication from GSM modem to PIC. You can > only get output to the port by enabling the echo mode (ATE) and then > sending something to the modem that will not work as a modem command. I was afraid of that... afraid of tampering with the GSM module, even if it doesn’t do anything, I wouldn’t like it to get hung, and my two first SIM900 based boards (including a geogram one) haven’t given me much fate in them until now. But well. If though I inject, intentionally, some AT commands (SMS for example), that shouldn’t be a problem right ? The OVMS wouldn’t mind ? There is potentially a risk of command collision (Would have to implement a « Not too soon or late to send anything » routine by listening the serial) > > For example a comment line starting with "#" -- I have used this for > debug output on the DIAG port regardless of the actual DIAG mode, so I > think you should be able to use that method to send data to an attached > Arduino or the like. > > Caveat is the slow line speed (9600 baud), and you need to re-enable ATE > from time to time. > Noted :) > > > JaXX > > (Despite tweaks, though driving cool, managed nearly 80km range, almost more than > default) > ...and that's also been reported by Twizy 80 drivers. Some really get > more range, I suppose that's if the higher recuperation has a chance to > really get at work. I have though noticed, possibly my mind going nuts, that even though the car has been filled up, that there is some recup for the first minutes (odd since the battery being in theory full, there’s nowhere to store the energy), and sometimes, even under 90% charge, I have little to no recup for some periods… It’s mainly between a feeling and a strong impression, but I’m sharing it in case anyone else has noticed it. > > Regards, > Michael -- Julien (JaXX) Banchet

2 1

Twizy release 3.2.0, binary params, SimpleConsole
by Michael Balzer 16 Feb '14

16 Feb '14

Hi everyone, just checked in my latest additions: https://github.com/openvehicles/Open-Vehicle-Monitoring-System/commit/90407… This also includes a first support for using parameter slots for binary data. The base64 encoding does not work for me, as I need to store the SEVCON profiles which are already larger than even 32 bytes. So the par_setbin() and par_getbin() calls can use adjacent param slots for binary data. I'm not happy with having to protect binary param slots hard coded from the text functions, but had no time for a dynamically vehicle adaptive configuration. Another common addition contained is a howto document on building a simple switch/LED console for the OVMS. I use this on the Twizy to switch SEVCON profiles directly, i.e. during driving I can now quickly disable recuperation if encountering black ice. Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

1 0