September 2014 - OvmsDev

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

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 17 Nov '15

17 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

Re: [Ovmsdev] Open Charge Map
by Christopher Cook 17 Oct '14

17 Oct '14

Actually, on that topic (almost) - we should discuss how OVMS users might checkin (or even auto-checkin) to OCM. That would help us track which locations people are using and the quality of their experience there. Are there any recent thoughts on this from the OVMS side? Currently there are no third party apps writing to the OCM API. Doing so currently requires at least authentication (via the web UI) - this is also the method used by the OCM mobile apps. There is the possibility of a quicker/simple login to OCM via third party apps by way of a security code emailed to the user (who would either be new to OCM or an existing user). Not massively secure (there are holes in the approach) but it would make it easy for third party apps to quickly authenticate. Alternatively we can provide URLs which OVMS users would open in a browser/webview which go on to use the standard mobile app or site. This is the easiest for OVMS apps to implement. Depends on what integration people would like to see? Chris J-C Saint-Pô <jcsaintpo(a)gmail.com> wrote: >_______________________________________________ >OvmsDev mailing list >OvmsDev(a)lists.teslaclub.hk >http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

9 47

Twizy release 3.5.0
by Michael Balzer 30 Sep '14

30 Sep '14

Hi everyone, just checked in Twizy release 3.5.0: https://github.com/openvehicles/Open-Vehicle-Monitoring-System/commit/b6d21… This release adds a kickdown function to the Twizy to make eco profiles more usable. If using a profile with reduced drive level, a kickdown will temporarily raise the level to 100%. See manual for details. Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

3 4

CFG commands on RT_Production
by Julien NOZAIS 26 Sep '14

26 Sep '14

Hello everybody, my name is Julien, I am a soon-to-be CS engineer from France. I am working on an internship project that requires to modify the Renault Twizy's internal parameters via the CAN bus. I am very interested in the work done by the OVMS developers on that topic. In the past few weeks I have learned quite a lot about Twizy's SEVCON through the documentation and also by browsing through the OVMS car module's source code. Thanks a lot for all the documentation and advice you provide! I have some questions that I hope you guys can answer to (TL;DR below). MSG commands My current situation is that I have upgraded my OVMS module to 2.6.5 firmware with the .hex file provided on GitHub. I have also successfully connected to the module via SMS commands and Android App. Most of the basic commands that I tried worked. I say 'most', because I have set the #15 'write' bit to '1' and cleared the #14 bit as well. However, I don't seem to be able to send CFG commands via SMS (such as CFG SPEED <speed> for example) in the way that the twizy manual describes it. All I get are push notifications forwarding my SMS to the app. Is there something I'm missing? :( Compilation issues On an other topic, I have installed MPLABX and acquired the C18 compiler thanks to someone hosting it on a personal website (note: it's nowhere to be found in the microchip archive and static links sourcing it on the website are all dead at the moment). I have tried to compile the V2_RT_Production from the last source available on GitHub. However I ran into compilation errors in vehicle_twicy.c, caused by what I assumed were missing '#define' directives (i.e 'OVMS_TWIZY_BATTMON' & 'OVMS_TWIZY_CFG'). I didn't see them referenced anywhere but in the version comments at the start of the file: > - Twizy battery monitor compiler switch: OVMS_TWIZY_BATTMON So I added these two, but I don't know if they were supposed to be left out. Incidentally, I ran into a new compilation error: > Error - section '.romdata_net_msg.o' can not fit the section. Section '.romdata_net_msg.o' length=0x000000a8 Which as I understand is an issue relative to the length of the file being too large to pass compilation. I'm fairly new to PIC programming, so I may have misinterpreted some of these compilation errors. I imagine there is a lot of work in progress on the code so maybe the version I pulled was not a stable one ? Any remark or advice is most welcome! DIAG communication Probably noob error: I tried connecting through the DIAG port with minicom. I set minicom to 9600 Bds / 8N1, as specified in the developers documentation, but had no success. I think that I'm closed since since I received data, but it was just gibberish encoding errors. Since these errors are often caused by a wrong baud setting, I tried different baud values without success. I hope somebody can point out something that I could have missed. I have read the manual, but, well... you never know. TL;DR - Can I send SMS CFG commands to Twizy 2.6.5 firmware? - Is there any specific advice on how to get started on OVMS source and compile it for the Twizy? - Communication with DIAG port on minicom only speaks gibberish although I have (supposedly) correct settings. Could I have missed something? Anyway, I hope I'm not bothering you with all my questions. Sorry for the long e-mail. I look forward to reading from you ! Julien Nozais

2 5

Re: [Ovmsdev] OvmsDev Digest, Vol 32, Issue 5
by Aatheus 25 Sep '14

25 Sep '14

On 09/24/2014 09:00 PM, ovmsdev-request(a)lists.teslaclub.hk wrote: > Message: 4 > Date: Thu, 25 Sep 2014 09:51:47 +0800 > From: Mark Webb-Johnson <mark(a)webb-johnson.net> > Subject: Re: [Ovmsdev] CFG commands on RT_Production > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > Message-ID: <DB4A9580-13F5-4343-A098-CB5463C2A3D9(a)webb-johnson.net> > Content-Type: text/plain; charset=us-ascii > > Jeff, > > It should be sufficient, for the Nissan Leaf, to use the V2_EXPERIMENTAL build and select NL and the vehicle type. > > You also need to make sure you've got the new style Nissan Leaf OBDII cable (with the EV bus CAN pins, not the CAR CAN bus). > > Regards, Mark. Mark, I tried recompiling because I see that the V2_EXPERIMENTAL firmware is from 7 months ago, but the vehice_nissanleaf.c was last modified in July. I had to exclude all of the other vehicles from the build, or I got the "cannot fit" linker error. I did not know about the custom LEAF ODBII cable. Was it recently added to the Fasttech site? I could have sworn that it wasn't there a month ago. Thanks, -Jeff

2 1

Re: [Ovmsdev] CFG commands on RT_Production
by Aatheus 25 Sep '14

25 Sep '14

Thank you for posting this info! I was able to get the experimental Nissan Leaf code to compile and (sort of) do useful things now. The configuration that I had to use was V2_EXPERIMENTAL. I cloned it to be V2_EXPERIMENTAL_LEAF. I set these flags: OVMS_CAR_NONE OVMS_HW_V2 OVMS_DIAGMODULE OVMS_INTERNALGPS OVMS_NISSANLEAF OVMS_LOGGINGMODULE OVMS_POLLER OVMS_ODBII OVMS_TRACK I also excluded acc.c and all of the other vehicle source files except for these: vehicle_nissanleaf.c vehicle_none.c vehicle_odbii.c vehicle_track.c vehicle.c Now the hex file builds and the OVMS v2 module is able to give me a different inaccurate battery percentage (0% instead of 80%). Progress? :) -Jeff Orr Message: 2 Date: Mon, 22 Sep 2014 20:02:47 +0200 From: Michael Balzer <dexter(a)expeedo.de> Subject: Re: [Ovmsdev] CFG commands on RT_Production To: ovmsdev(a)lists.teslaclub.hk Message-ID: <54206447.5010806(a)expeedo.de> Content-Type: text/plain; charset="windows-1252"; Format="flowed" (snip) To compile yourself you need to define these (and only these) compiler flags: OVMS_CAR_NONE OVMS_CAR_RENAULTTWIZY OVMS_HW_V2 OVMS_DIAGMODULE OVMS_INTERNALGPS OVMS_TWIZY_BATTMON OVMS_TWIZY_CFG ...and you need to manually exclude source files "acc.c", "logging.c" and all other "vehicle*.c" from the build, because otherwise... (snip)

2 1

OVMS not connecting
by Jack West 08 Sep '14

08 Sep '14

My module has been on the fritz for about two weeks after working for a long time. Red led flashes 8 times. "GPRS Network initialization failed". I have tried unplugging the module to reboot. My phone plan still has a balance. The blue led is slowly flashing. I replaced the cable a few months ago when I thought the unit was acting flakey and that seemed to help for a while, ie the module stayed connected more reliably. What should my next step be in troubleshooting? Thanks, Jack

1 0