August 2015 - 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

OVMS v2 stock / OVMS v3
by Mark Webb-Johnson 22 Feb '16

22 Feb '16

At the current rate, the batch we have of OVMS v2 modules will run out sometime in the next two months. Given the imminent shutdown of AT&T’s 2G network in USA, global re-allocation of 2G frequency bands, and the difficulties we are having obtaining the discontinued SIM908, it is decision time. Option #1: Re-order a large batch now, enough to last us into the new year, but with the risk that I’ll be personally stuck with them. Option #2: Just let the v2 modules run out, and move on with the plans for v3. Development on v2 is stagnating. Partly because the platform already does what we need it to do, and partly because we’re hitting the limits (no external connectivity other than GPRS, single CAN bus, no storage, limited RAM, flash, etc). The v3 plans have been on hold for some time, pending MBED OS release (first beta due this month) and the imminent release of hybrid processors such as that used in the UDOO Neo (due in September). We know what we want, but it is just too hard to pick a long-term platform when everything is on the cusp of changing. I really want a v3 module. Something with lots of RAM and Flash, wifi, bluetooth and cellular connectivity, multiple CAN bus support, and a rich development platform. Something we can all use as a platform for reverse engineering as well as end-user connectivity. I’ll do everything I can to make this a reality. Just not today. Too much is changing and we need to wait for things to stabilise. So, my gut feeling is to choose option #2. 2G GPRS is slowing dying, and building more on that platform just seems to be the wrong decision. This may leave us with several months of no platform stock, but I would rather people waited than spend $100 on something that is going to be obsolete/outdated. Kind of like buying an iPhone in August ;-) I don’t want to be stuck with the stock, and I don’t want people to buy a v2, only to have v3 come out a week later. Even if we started now, which we can’t, an optimistic schedule for the first end-user v3 units would be early 2016. So, tough decisions, but I really think option #2 is best. Bottom line is if you need v2 modules, order them now. If you are likely to need a large quantity for any upcoming projects, let me know. The SIM908 modules will be unavailable within the next month or so, and changing to another module is a PITA I don’t want to deal with (especially given the tight RAM and FLASH we have now). Regards, Mark.

14 37

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

iOS 8.4
by Mark Webb-Johnson 29 Aug '15

29 Aug '15

A lot has changed in iOS 8, and it seems to have broken push notifications (APNS) for new users. Existing users are fine. So, I find the few lines that need to be changed, and fixed that. Cool. Now, submit to App Store, and Apple requires 64bit. OK, change the building settings for a 32bit + 64bit dual package, and rebuild. (old) Testflight sdk not compatible (32bit only). Remove testflight sdk, and all its tendrils throughout the code base. Rebuild. 190+ warnings about int vs long. Crap de crap de crap. Rebuild. OK. All clean, built and ready to go. Only issue is that all my working devices are IOS 9 beta (for work), and Apple’s not accepting iOS 9 built stuff yet, so I can’t properly test. Each of the above steps needs about 15-to-45 minutes of googling. So, I have a build (v1.6.6). It is 32bit and 64bit. It seems to work. But, I need help testing. Seems Apple have a new test flight integrated to iTunes connect. Never tried it, but you are all about to get an invite ;-) Regards, Mark.

4 11

Fwd: The status for your app, Open Vehicles (490098531), is now Ready for Sale.
by Mark Webb-Johnson 29 Aug '15

29 Aug '15

Approval was fine. I just gave it the green-light for release, as no negative feedback on the beta. Regards, Mark > Begin forwarded message: > > From: iTunes Store <no_reply(a)email.apple.com> > Subject: The status for your app, Open Vehicles (490098531), is now Ready for Sale. > Date: 29 August, 2015 9:10:50 pm HKT > > > > > Dear Mark Webb-Johnson, > The following app has been approved and the app status has changed to Ready for Sale: > > App Name: Open Vehicles <https://itunes.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=49009853…> > App Version Number: 1.6.6 > App Type: iOS App > App SKU: OVMS-IOS > App Apple ID:490098531 > If your contracts are not in effect at this time, your app status will be Pending Contract. You may track the progress of your contracts in the Agreements, Tax, and Banking <http://www.apple.com/itunes/go/itunesconnect/contracts> module in iTunes Connect. > > To make changes to this app, sign in to iTunes Connect and open the Manage Your Applications <http://www.apple.com/itunes/go/itunesconnect/manageApps>module. > > It can take up to 24 hours before your app is available on the App Store. This delay is dependent on any app availability issues. > > Before you market your app, read the App Store Marketing and Advertising Guidelines <https://developer.apple.com/appstore/AppStoreMarketingGuidelines.pdf> for Developers. The guidelines include information on using the App Store badge, best practices to market apps on the App Store, and details on the use of Apple product images. > > If you have any questions regarding your app, use the Contact Us <http://www.apple.com/itunes/go/itunesconnect/contactus> module on iTunes Connect. > > Regards, > The App Store team > > > > Contact Us <http://www.apple.com/itunes/go/itunesconnect/contactus> | iTunes Connect <http://itunesconnect.apple.com/> | 1 Infinite Loop, Cupertino, CA 95014 > > Privacy Policy <http://www.apple.com/legal/privacy/> | Terms of Service <http://www.apple.com/support/itunes/legal/terms.html> | Terms of Sale <http://www.apple.com/support/itunes/legal/policies.html>

1 0

Broken pipes
by Michael Balzer 23 Aug '15

23 Aug '15

Mark, I've had lots of broken pipes on the car side yesterday and I've got the same for the app side today. Do you know of any change on the server side that could cause this? Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

2 4

Twizy beta release 3.6.0
by Michael Balzer 22 Aug '15

22 Aug '15

This is a beta rest / release candidate, documentation has not yet been updated. Firmware: http://dexters-web.de/f/tw/OVMS-Twizy-3.6.0-beta1.zip Source: https://github.com/dexterbg/Open-Vehicle-Monitoring-System/ 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 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 Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

1 0