February 2017 - 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

3.1.2 short lived connections and high data usage
by Mark Webb-Johnson 01 Mar '17

01 Mar '17

I’ve had a report from a user of 3.1.2 firmware reporting short connections and high data usage (reconnecting to server every few minutes). Logs look like this: 2017-02-11 22:27:42.936568 +0800 info main: #76 - - rx MP-C 0 (redacted) (redacted) VID 2017-02-11 22:27:42.937997 +0800 info main: #76 C VID crypt session key (redacted) 2017-02-11 22:27:42.938251 +0800 info main: #76 C VID tx MP-S 0 (redacted) (redacted) 2017-02-11 22:27:42.938852 +0800 info main: #76 C VID tx (Z 0) 2017-02-11 22:27:53.634604 +0800 info main: #76 C VID rx msg D 40,0,0,9,7,9,457,1061084,0,453159,6,0,119,117,11.3,33,11.4,0,0 2017-02-11 22:27:53.636440 +0800 info main: #76 C VID msg handle D 40,0,0,9,7,9,457,1061084,0,453159,6,0,119,117,11.3,33,11.4,0,0 2017-02-11 22:29:34.076615 +0800 info main: #76 C VID got error Broken pipe Anybody else seeing anything like this? Regards, Mark.

3 2

V3 Hardware / Roll Your own
by Chris Perez 27 Feb '17

27 Feb '17

Just wondering if you are still on track to hit your 1Q17 target for the new hardware release. Interested in beta testing the new HW!

4 8

Re: [Ovmsdev] V3 Hardware / Roll Your own
by Chris Perez 27 Feb '17

27 Feb '17

Thanks Mark. A few more questions. 1. When will the schematics/component selections be published on GitHub? 2. What programming language are you planning on moving to seeing as how the PIC code will not translate directly to the ESP32? 3. Will the modem be moving to LTE Cat M1.NB1 for a little future proofing? I am toying with the idea of ordering a https://www.pycom.io/product/gpy-preorder-shipping-may-2017/ board and converting the OVMS code base+vehicle specifics to Python leveraging private MQTT. But I don’t want to fork too far away :/ Chris, Julien, I hear you. Just waiting for the latest processor stepping from Espressif, then should be ok for a run of developer boards. Still no modular certification, so stuck as a DIY until that is resolved. I appreciate that the delays are frustrating - for me too. Just a huge steep learning curve with this new platform. Regards, Mark.

2 1

SIM808 GPS float bug
by Edward Cheeseman 13 Feb '17

13 Feb '17

Hello, I am new to OVMS. I have a Gen2 Leaf on Dexters server. Tom has helped me set it up. I found my GPS data was off up to two degrees. I’ve traced it to myatof() in utils.c. It adds the fractional part with both positive and negative numbers, where it should subtract for negative numbers. myatof() is used in SIM808 lat and long conversions, and somewhere in Twizy which I didn’t look into. I suppose there isn’t that many SIM808 based OVMSs in the Southern or Western hemispheres? It is easy to fix, but maybe going through float in the first place isn’t necessary? Looks like there is 31bits of information coming out of the GPS where float will drop this to 23bits. I’ve started rewriting gps2latlon() to use a long long (64bit) integer multiply and divide. I see reference to SIM808 and 908 on an arduino shield, so I might have a look to see what they have done. Edward

5 25

ODB CAN message decoder?
by Greg D. 09 Feb '17

09 Feb '17

3 7