July 2016 - 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

OVMS v3
by Mastro Gippo 20 May '17

20 May '17

Hi all, I'd like to resurrect an old conversation. As we know, the current PIC is quickly running out of resources and maybe it's time to switch to a better platform. Two CAN buses are now desirable too. A microSD slot and direct USB connectivity wouldn't hurt either. I will probably have to design a similar hardware for myself, so I'd like to contribute to the OVMS by sharing the HW platform if you want; no strings attached of course, if you decide that there's no need for the upgrade, I'll keep on working on my project by myself! :) That said, I'd like to throw a few ideas to the table. - MCU: I'd like to use an STM32 micro. They seem to be emerging as the standard choice for diy ARM projects, and this offers a few interesting opportunities: -Programming it in c/c++ with the manufacturer CMSIS standard libraries (boring) -Programming it with the mbed.org SDK. Unfortunately no dev boards are available with dual CAN bus, but it will be easy to move to the correct micro of the same series once most of the software is ironed out on a dev board like the https://mbed.org/platforms/ST-Nucleo-F302R8/ -Programming it with an RTOS. NuttX would be my choice, as it's the one used in the Ardupilot Pixhawk platform, and I'd like to learn it. This would mean a steeper starting curve, but a lot of flexibility later as a lot of stuff is handled on the OS level (network stacks, SD card & filesystems, multitasking...). FreeRTOS is a nice option too. I'd like to use the STM32F405RG as it's the most similar to the one found on the Pixhawk, but of course I'm biased because of that, and that micro is quite overkill for the task. We can of course use a lower specced part and lose some RTOS fuctionality as long as it has 2 CAN buses. - MODEM: I have no experience in this field; is the SIM908 still a good choice or does anyone think that we should try new platforms? I like this, but I don't know if the price puts it out of budget: http://www.telit.com/telit/Pulsar/en_US.Store.display.1001./ge864-gps On the bright side, it can be programmed in python, so we can offload some of the work to the modem. This *could* allow us to free some space on the PIC, and keep that platform without changing MCU.. - Enclosure: I think that, even with the new MCU, we can still fit the old enclosure. Is that ok, or should we think about a more automotive-friendly one? Maybe waterproof for the twizy? And that's it. I think that the core SW developers should voice their opinion, as there is a lot of work to be done on that front. A huge problem will be keeping backwards compatibility to add features for the v2 users, so we should discuss about this too. Regards MG

18 70

Nissan Leaf Climate Control
by Tom Parker 25 Dec '16

25 Dec '16

I sent a pull request with Nissan Leaf remote climate control support. I also wrote up a quick blog post with a photo of my gen 1 wakeup circuit: https://carrott.org/blog/archives/158-OVMS-Nissan-Leaf-Remote-Climate-Contr… I'll post a schematic of the circuit. Gen 2 doesn't require any hardware modifications. I added #define CMD_ClimateControl 43 // (ON or OFF) with argument 'on' and 'off'. I'm using temporary hack to enable climate control via the homelink buttons. If CMD_ClimateControl is suitable, could we add support in the Apps for a better button to toggle it on and off? I see there is a car_doors5bits.HVAC to signal that climate control is on, but I don't think that is exposed in the android interface. This would be a good candidate to provide feedback that the climate control is on.

3 5

ATT: car_chargekwh rescaled
by Michael Balzer 31 Jul '16

31 Jul '16

Hi everyone, ref: https://github.com/openvehicles/Open-Vehicle-Monitoring-System/commit/a20cd… Changing the car_chargekwh scale from 1 kWh to 1/10 kWh was necessary to make this info useful for small batteries. Unfortunately the Java clients (Apps) while not even using this field will break on replacing the integer value by a float, as the Java int parser will throw an exception instead of parsing just the integer part. So the value remains unscaled in the message to not break compatibility with installed Apps. Clients evaluating the field need to scale the value themselves. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

1 0

SIM808 not communicating
by Tom Parker 25 Jul '16

25 Jul '16

Hi, I've got one of the new OVMS modules with the SIM808 cellular module to put in a friends car and I'm having some trouble making it work. It does get a GPS location, I haven't included that in the transcript below. I'm reasonably sure I'm using the SIM808 firmware instead of the SIM908 firmware. I'm using the SIM card that is working in my older module with SIM908. I see the following on the serial port when I send it the register command: AT+CGNSINF +CGNSINF: 1,0,20160717082302.000,,,,0.00,0.0,0,,,,,,2,0,,,34,, OK AT+CREG?;+CIPSTATUS;+CCLK?;+CSQ +CREG: 1,1 STATE: IP INITIAL +CCLK: "04/01/01,00:07:42+48" +CSQ: 19,0 OK +CMT: "+<my cell phone number>","","16/07/17,20:23:36+48",145,4,0,0,"+<some other cell phone number>",145,13 REGISTER OVMS AT+CMGS="+<my cell phone number>" > Your phone has been registered as the owner. ERROR AT+CREG?;+CIPSTATUS;+CCLK?;+CSQ +CREG: 1,1 STATE: IP INITIAL I went through the setup process using the diag port for feedback instead of the sms responses and switched on the GPRS, which didn't work either: AT+CLPORT="TCP","6867" OK AT+CIPSTART="TCP","api.openvehicles.com","6867" OK CONNECT OK AT+CIPSENDMP-C 0 QRG/M9iLIp+XEVajAB2v8t JIBS2rw2cub6ssu5QY4C7Q== xxxxxx DATA ACCEPT:63 CLOSED AT+CIPCLOSE ERROR Any thoughts? I haven't yet looked communications of my working module to compare. Does anyone have a firmware or tutorial that sends a fixed sms message to test the cellular module?

3 4