June 2014 - 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

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

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

Re: [Ovmsdev] Twizy ideas
by Gianluca Magalotti 30 Jun '14

30 Jun '14

Hi After the release of the 3.3.0 version is now possible to lock unlock the car by reducing max speed. Would be nice if (by feature enabling) ovms could handle automatic lock each time car is parked, forcing an unlock by the app. Maybe Can be an app feature. Il 07/giu/2014 00:42 <ovmsdev-request(a)lists.teslaclub.hk> ha scritto: > Send OvmsDev mailing list submissions to > ovmsdev(a)lists.teslaclub.hk > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > or, via email, send a message with subject or body 'help' to > ovmsdev-request(a)lists.teslaclub.hk > > You can reach the person managing the list at > ovmsdev-owner(a)lists.teslaclub.hk > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OvmsDev digest..." > > > Today's Topics: > > 1. Re: Twizy feature ideas (Mark Webb-Johnson) > 2. Re: Twizy feature ideas (Nikolay Shishkov) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 6 Jun 2014 20:31:29 +0800 > From: Mark Webb-Johnson <mark(a)webb-johnson.net> > Subject: Re: [Ovmsdev] Twizy feature ideas > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > Message-ID: <49247C68-2B86-467C-A9E8-72E7B1D10629(a)webb-johnson.net> > Content-Type: text/plain; charset="windows-1252" > > Bug squished. Live on tmc now (and pushed to github). > > Neat web page. Shows promise. > > Regarding the CORS, I?m very willing to make the changes - just not really > sure what headers exactly need to be added. Anyone here know what I would > need to add? > > Regards, Mark. > > On 6 Jun, 2014, at 3:03 pm, Michael Balzer <dexter(a)expeedo.de> wrote: > > > Nikolay, > > > > you found an API server bug :-) > > > > Solution: delete all domain cookies for "openvehicles.com" from your > browser before using the API. > > > > The API server gets confused by multiple cookies. If you visit > www.openvehicles.com before using the API, you get a persistent PHP > session cookie like this: > > > > Name SESS619b2b3f204291df32506531f8b446dd > > Host .openvehicles.com > > Pfad / > > > > As the host defines ".openvehicles.com" and path "/", this cookie also > gets sent to the API host, which then confuses this one with the > "ovmsapisession" cookie, i.e. > > > > Name ovmsapisession > > Host tmc.openvehicles.com > > Pfad /api/ > > > > Regards, > > Michael > > > > > > Am 05.06.2014 23:46, schrieb Nikolay Shishkov: > >> Thanks Michael, > >> I am getting "login ok" when pressing on the login button, but then all > the other buttons are giving "authentication error" message. > >> I could check that the cookie is sent with the request, but the server > seems to respond with the 400 code. > >> I tried in Chrome. Where, how do you use the page? > >> Nikolay > >> > >> > >> On Thursday, June 5, 2014 10:59 PM, Michael Balzer <dexter(a)expeedo.de> > wrote: > >> > >> > >> Nikolay, > >> > >> that's right, I intend to get this running without an otherwise > necessary proxy, i.e. for local HTML pages on mobile devices or the like. > I've been in contact with Mark about CORS on the perl server. > >> > >> A server could of course be used, most simply the HTTP API itself could > deliver the client page, but CORS should now enable to cope without and > open possible cross origin data/control integrations. Not sure about static > pages for this though, not yet tested. I think it would be cool to just > load some HTML file in your browser and have a graphical OVMS client. > >> > >> The "code" is currently just a first test bed HTML page to interact > with the HTTP API. No graphics, just a simple table view. Works, but is > clumsy as hell. > >> > >> Try yourself, I've attached it. > >> > >> Regards, > >> Michael > >> > >> > >> Am 05.06.2014 11:26, schrieb Nikolay Shishkov: > >>> Hi Michael, > >>> > >>> I am very interested in the "Browser client using HTTP API and > jQuery/Flot for visualization". From the comment that CORS is needed I > suspect you want to have the html5 page locally and then fetch data from > the server while using other sources for context data. > >>> Have you considered running this on a separate server that serves as a > gateway to the TMC server? > >>> > >>> Have you uploaded the code somewhere? > >>> > >>> I have been playing around with C# client and was thinking of using it > on an asp.net server... > >>> > >>> Nikolay > >>> > >>> > >>> On Wednesday, June 4, 2014 11:22 PM, Michael Balzer <dexter(a)expeedo.de> > wrote: > >>> > >>> > >>> Am 04.06.2014 07:38, schrieb Gianluca Magalotti: > >>> > For nice2have features I'll wait for your list (I have my personal > >>> > list too but maybe we'll have a later focus on that) > >>> > >>> So here it is. > >>> > >>> If other Twizy drivers would like to add their ideas, you're welcome. > >>> > >>> I'll do my best to check new ideas against my collected knowledge of > >>> what's possible up to now and give you some feedback. > >>> > >>> > >>> Regards, > >>> Michael > >>> > >>> > >>> -- > >>> Michael Balzer * Paradestr. 8 * D-42107 Wuppertal > >>> Fon 0202 / 272 2201 * Handy 0176 / 206 989 26 > >>> > >>> > >>> > >>> _______________________________________________ > >>> OvmsDev mailing list > >>> OvmsDev(a)lists.teslaclub.hk > >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> OvmsDev mailing list > >>> OvmsDev(a)lists.teslaclub.hk > >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > >> > >> -- > >> Michael Balzer * Paradestr. 8 * D-42107 Wuppertal > >> Fon 0202 / 272 2201 * Handy 0176 / 206 989 26 > >> > >> _______________________________________________ > >> OvmsDev mailing list > >> OvmsDev(a)lists.teslaclub.hk > >> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > >> > >> > >> > >> > >> _______________________________________________ > >> OvmsDev mailing list > >> OvmsDev(a)lists.teslaclub.hk > >> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > > > > > -- > > Michael Balzer * Paradestr. 8 * D-42107 Wuppertal > > Fon 0202 / 272 2201 * Handy 0176 / 206 989 26 > > _______________________________________________ > > OvmsDev mailing list > > OvmsDev(a)lists.teslaclub.hk > > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > >

2 1

Re: [Ovmsdev] SEVCON ALERT
by Gianluca Magalotti 30 Jun '14

30 Jun '14

Thankyou both I'll check with Renault asap Il 30/giu/2014 00:40 <ovmsdev-request(a)lists.teslaclub.hk> ha scritto: > Send OvmsDev mailing list submissions to > ovmsdev(a)lists.teslaclub.hk > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > or, via email, send a message with subject or body 'help' to > ovmsdev-request(a)lists.teslaclub.hk > > You can reach the person managing the list at > ovmsdev-owner(a)lists.teslaclub.hk > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OvmsDev digest..." > > > Today's Topics: > > 1. Re: SEVCON ALERT (Michael Balzer) > 2. Re: SEVCON ALERT (Julien (JaXX) Banchet) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 29 Jun 2014 23:08:43 +0200 > From: Michael Balzer <dexter(a)expeedo.de> > Subject: Re: [Ovmsdev] SEVCON ALERT > To: ovmsdev(a)lists.teslaclub.hk > Message-ID: <53B0805B.8000607(a)expeedo.de> > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" > > Gianluca, > > there's a fault code list in the SEVCON DVT package, you can find it on > the web. > > Info from that list: > Description: "Throttle appears to be stuck. This fault will clear if > throttle starts to work again." > Recommended action: "Check throttle wiring and installation." > > There once was a throttle service callback concerning mechanically stuck > pedals, maybe that's the cause? > > But first check if the fault persists. > > Regards, > Michael > > > Am 29.06.2014 22:42, schrieb Gianluca Magalotti: > > Tonight I've received on my app the following message: > > SEVCON ALERT 0x4582 Safety Case 1 > > > > What does it mean? > > > > *Gianluca* > > * > > * > > Il giorno 29/giu/2014, alle ore 06:00, > > ovmsdev-request(a)lists.teslaclub.hk > > <mailto:ovmsdev-request@lists.teslaclub.hk> ha scritto: > > > >> Send OvmsDev mailing list submissions to > >> ovmsdev(a)lists.teslaclub.hk <mailto:ovmsdev@lists.teslaclub.hk> > >> > >> To subscribe or unsubscribe via the World Wide Web, visit > >> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > >> or, via email, send a message with subject or body 'help' to > >> ovmsdev-request(a)lists.teslaclub.hk > >> > >> You can reach the person managing the list at > >> ovmsdev-owner(a)lists.teslaclub.hk > >> > >> When replying, please edit your Subject line so it is more specific > >> than "Re: Contents of OvmsDev digest..." > >> > >> > >> Today's Topics: > >> > >> 1. Re: changing android app server IP (Tom Saxton) > >> 2. Re: changing android app server IP (Lee Howard) > >> > >> > >> ---------------------------------------------------------------------- > >> > >> Message: 1 > >> Date: Sat, 28 Jun 2014 09:28:52 -0700 > >> From: Tom Saxton <tom(a)idleloop.com> > >> Subject: Re: [Ovmsdev] changing android app server IP > >> To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > >> Message-ID: <CFD43A7E.6BBAD%tom(a)idleloop.com> > >> Content-Type: text/plain;charset="US-ASCII" > >> > >> I just downloaded the Android Open Vehicle app and configured it for our > >> Roadster. It gives me an error message that it can't connect and > >> recommends checking my passwords. I've double-checked the passwords and > I > >> think they are right. > >> > >> I don't see anywhere to enter my OVMS server user name, which the iOS > app > >> requires. Is that the problem? > >> > >> Tom > >> > >> -----Original Message----- > >> From: Mark Webb-Johnson <mark(a)webb-johnson.net> > >> Reply-To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > >> Date: Saturday, June 28, 2014 at 6:06 AM > >> To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > >> Subject: Re: [Ovmsdev] changing android app server IP > >> > >>> Lee, > >>> > >>> Looks good. I merged it, and submitted v3.2.2 to google play. > >>> > >>> Regards, Mark. > >>> > >>> On 28 Jun, 2014, at 3:44 am, Lee Howard <lee.howard(a)mainpine.com> > wrote: > >>> > >>>> On 06/27/2014 10:38 AM, Lee Howard wrote: > >>>>> On 06/26/2014 08:38 PM, Tom Saxton wrote: > >>>>> > >>>>>> Arguably the server account should be per-vehicle but I'm > >>>>>> guessing the > >>>>>> thought was that anyone who has multiple OVMS vehicles will have > them > >>>>>> all > >>>>>> on the same server and making that app-wide means you only have to > >>>>>> enter > >>>>>> username, password and server IP once. > >>>>>> > >>>>>> Of course none of this is any help for figuring out how to do it on > >>>>>> Android... > >>>>> > >>>>> As I dug-into the Android code better to hard-code the address change > >>>>> I discovered - to my delight - that the app server address is > >>>>> stored in > >>>>> a per-car data object. Yay! So this is nice. I'm going to give > this > >>>>> another shot. > >>>> > >>>> Here is the patch. Someone with privs can apply it and commit these > >>>> changes to the repository if it meets with their approval. > >>>> > >>>> It's a very small enhancement - basically permitting an interface to > >>>> sel_server in the CarData object. The interface is right where it > >>>> should be, IMO: right where you enter the vehicle info and passwords. > >>>> The default is left to "tmc.openvehicles.com", but the user now has > the > >>>> capability to modify it (on a per-car basis, even). > >>>> > >>>> I did not change the sel_server initialization value of > >>>> "tmc.openvehicles.com". I could have changed this to "" as with the > >>>> other CarData strings, but it probably makes little difference. > Leaving > >>>> it to initialize with "tmc.openvehicles.com" possibly it could be > >>>> confusing to someone later who doesn't recognize that the initialized > >>>> value is always overwritten by the configured value (as with the other > >>>> CarData strings which are initialized to ""). If someone cares > >>>> they can > >>>> modify that at the top of CarData.java. > >>>> > >>>> This patch also makes one obvious grammatical correction in a string > >>>> appearing on the same page layout. > >>>> > >>>> If there is any concern just look at the patch - it's a very, very > >>>> benign set of changes. This e-mail is longer than the patch is. > >>>> > >>>> 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 > >>>> > >>>> > <ovms-android-editserver.patch>__________________________________________ > >>>> _____ > >>>> OvmsDev mailing list > >>>> OvmsDev(a)lists.teslaclub.hk > >>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > >>> > >>> _______________________________________________ > >>> OvmsDev mailing list > >>> OvmsDev(a)lists.teslaclub.hk > >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > >>> > >> > >> > >> > >> > >> ------------------------------ > >> > >> Message: 2 > >> Date: Sat, 28 Jun 2014 10:05:43 -0700 > >> From: Lee Howard <lee.howard(a)mainpine.com> > >> Subject: Re: [Ovmsdev] changing android app server IP > >> To: ovmsdev(a)lists.teslaclub.hk > >> Message-ID: <53AEF5E7.1060806(a)mainpine.com> > >> Content-Type: text/plain; charset=ISO-8859-1; format=flowed > >> > >> I'm using my built .apk instead of the one from Google Play, but my > >> source code is now identical to the one in the git repository. > >> > >> Mine is working fine for me. > >> > >> Admittedly, I do get confused about which one is the server password and > >> which one is the module password, and so I just swap them around if I > >> get the password error. Maybe the Android app has the two mixed-up? > >> > >> As for the app not needing the your account username... I've never > >> needed it on the Android app before. I think that it just uses the car > >> info. > >> > >> Thanks, > >> > >> Lee. > >> > >> > >> On 06/28/2014 09:28 AM, Tom Saxton wrote: > >>> I just downloaded the Android Open Vehicle app and configured it for > our > >>> Roadster. It gives me an error message that it can't connect and > >>> recommends checking my passwords. I've double-checked the passwords > >>> and I > >>> think they are right. > >>> > >>> I don't see anywhere to enter my OVMS server user name, which the > >>> iOS app > >>> requires. Is that the problem? > >>> > >>> Tom > >>> > >> > >> -- > >> *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 > >> > >> > >> ------------------------------ > >> > >> _______________________________________________ > >> OvmsDev mailing list > >> OvmsDev(a)lists.teslaclub.hk > >> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > >> > >> > >> End of OvmsDev Digest, Vol 29, Issue 73 > >> *************************************** > > > > > > > > _______________________________________________ > > OvmsDev mailing list > > OvmsDev(a)lists.teslaclub.hk > > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > -- > Michael Balzer * Paradestr. 8 * D-42107 Wuppertal > Fon 0202 / 272 2201 * Handy 0176 / 206 989 26 > >

1 0

SEVCON ALERT
by Gianluca Magalotti 30 Jun '14

30 Jun '14

Tonight I've received on my app the following message: SEVCON ALERT 0x4582 Safety Case 1 What does it mean? Gianluca Il giorno 29/giu/2014, alle ore 06:00, ovmsdev-request(a)lists.teslaclub.hk ha scritto: > Send OvmsDev mailing list submissions to > ovmsdev(a)lists.teslaclub.hk > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > or, via email, send a message with subject or body 'help' to > ovmsdev-request(a)lists.teslaclub.hk > > You can reach the person managing the list at > ovmsdev-owner(a)lists.teslaclub.hk > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OvmsDev digest..." > > > Today's Topics: > > 1. Re: changing android app server IP (Tom Saxton) > 2. Re: changing android app server IP (Lee Howard) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 28 Jun 2014 09:28:52 -0700 > From: Tom Saxton <tom(a)idleloop.com> > Subject: Re: [Ovmsdev] changing android app server IP > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > Message-ID: <CFD43A7E.6BBAD%tom(a)idleloop.com> > Content-Type: text/plain; charset="US-ASCII" > > I just downloaded the Android Open Vehicle app and configured it for our > Roadster. It gives me an error message that it can't connect and > recommends checking my passwords. I've double-checked the passwords and I > think they are right. > > I don't see anywhere to enter my OVMS server user name, which the iOS app > requires. Is that the problem? > > Tom > > -----Original Message----- > From: Mark Webb-Johnson <mark(a)webb-johnson.net> > Reply-To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > Date: Saturday, June 28, 2014 at 6:06 AM > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > Subject: Re: [Ovmsdev] changing android app server IP > >> Lee, >> >> Looks good. I merged it, and submitted v3.2.2 to google play. >> >> Regards, Mark. >> >> On 28 Jun, 2014, at 3:44 am, Lee Howard <lee.howard(a)mainpine.com> wrote: >> >>> On 06/27/2014 10:38 AM, Lee Howard wrote: >>>> On 06/26/2014 08:38 PM, Tom Saxton wrote: >>>> >>>>> Arguably the server account should be per-vehicle but I'm guessing the >>>>> thought was that anyone who has multiple OVMS vehicles will have them >>>>> all >>>>> on the same server and making that app-wide means you only have to >>>>> enter >>>>> username, password and server IP once. >>>>> >>>>> Of course none of this is any help for figuring out how to do it on >>>>> Android... >>>> >>>> As I dug-into the Android code better to hard-code the address change >>>> I discovered - to my delight - that the app server address is stored in >>>> a per-car data object. Yay! So this is nice. I'm going to give this >>>> another shot. >>> >>> Here is the patch. Someone with privs can apply it and commit these >>> changes to the repository if it meets with their approval. >>> >>> It's a very small enhancement - basically permitting an interface to >>> sel_server in the CarData object. The interface is right where it >>> should be, IMO: right where you enter the vehicle info and passwords. >>> The default is left to "tmc.openvehicles.com", but the user now has the >>> capability to modify it (on a per-car basis, even). >>> >>> I did not change the sel_server initialization value of >>> "tmc.openvehicles.com". I could have changed this to "" as with the >>> other CarData strings, but it probably makes little difference. Leaving >>> it to initialize with "tmc.openvehicles.com" possibly it could be >>> confusing to someone later who doesn't recognize that the initialized >>> value is always overwritten by the configured value (as with the other >>> CarData strings which are initialized to ""). If someone cares they can >>> modify that at the top of CarData.java. >>> >>> This patch also makes one obvious grammatical correction in a string >>> appearing on the same page layout. >>> >>> If there is any concern just look at the patch - it's a very, very >>> benign set of changes. This e-mail is longer than the patch is. >>> >>> 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 >>> >>> <ovms-android-editserver.patch>__________________________________________ >>> _____ >>> OvmsDev mailing list >>> OvmsDev(a)lists.teslaclub.hk >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >> >> _______________________________________________ >> OvmsDev mailing list >> OvmsDev(a)lists.teslaclub.hk >> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >> > > > > > ------------------------------ > > Message: 2 > Date: Sat, 28 Jun 2014 10:05:43 -0700 > From: Lee Howard <lee.howard(a)mainpine.com> > Subject: Re: [Ovmsdev] changing android app server IP > To: ovmsdev(a)lists.teslaclub.hk > Message-ID: <53AEF5E7.1060806(a)mainpine.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I'm using my built .apk instead of the one from Google Play, but my > source code is now identical to the one in the git repository. > > Mine is working fine for me. > > Admittedly, I do get confused about which one is the server password and > which one is the module password, and so I just swap them around if I > get the password error. Maybe the Android app has the two mixed-up? > > As for the app not needing the your account username... I've never > needed it on the Android app before. I think that it just uses the car > info. > > Thanks, > > Lee. > > > On 06/28/2014 09:28 AM, Tom Saxton wrote: >> I just downloaded the Android Open Vehicle app and configured it for our >> Roadster. It gives me an error message that it can't connect and >> recommends checking my passwords. I've double-checked the passwords and I >> think they are right. >> >> I don't see anywhere to enter my OVMS server user name, which the iOS app >> requires. Is that the problem? >> >> Tom >> > > -- > *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 > > > ------------------------------ > > _______________________________________________ > OvmsDev mailing list > OvmsDev(a)lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > > End of OvmsDev Digest, Vol 29, Issue 73 > ***************************************

3 2

Re: [Ovmsdev] Twizy 45
by Gianluca Magalotti 29 Jun '14

29 Jun '14

Yes Michael, I was referring to the intro stating it was for the 80 kph only (i said it was ambiguous because of that...). BTW I also solved the modem issue.. was my fault.. I didn't check the switch on the board and it was in "disable" position. Now everything works well and I've also downloaded last Android App. Gianluca Il giorno 28/giu/2014, alle ore 16:33, ovmsdev-request(a)lists.teslaclub.hk ha scritto: > Send OvmsDev mailing list submissions to > ovmsdev(a)lists.teslaclub.hk > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > or, via email, send a message with subject or body 'help' to > ovmsdev-request(a)lists.teslaclub.hk > > You can reach the person managing the list at > ovmsdev-owner(a)lists.teslaclub.hk > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OvmsDev digest..." > > > Today's Topics: > > 1. Re: Twizy 45 (Michael Balzer) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 28 Jun 2014 16:33:36 +0200 > From: Michael Balzer <dexter(a)expeedo.de> > Subject: Re: [Ovmsdev] Twizy 45 > To: ovmsdev(a)lists.teslaclub.hk > Message-ID: <53AED240.903(a)expeedo.de> > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" > > Gianluca, > > the CFG macro commands work identically on both models, automatically > respecting the lower T45 limits. > > So there is no usage difference between the models, and no need for > separate instructions. > > I just saw I forgot to remove one "only 80 kph" passage from the manual > on page 27, I suppose that's what you mean... fixed, will check that in > later. > > Section intro now is: > > "All macro commands work identically for the 80 kph and the 45 kph > versions of the Twizy, automatically using the respective limits (see > previous section on limit differences). The limits will be applied on > setting the registers, so you can even load a T80 macro profile into a > T45 (but don't expect similar driving results)." > > Regards, > Michael > > > Am 28.06.2014 14:28, schrieb Gianluca Magalotti: >> First of all please confirm that CFG commands (SPEED, POWER, RECUP, >> etc.) will work properly with Twizy 45. I've tried them on it and >> everything >> In any case I think we have to update twizy documentation at page 26 >> to be less ambiguous. >> More in general I think guide should be upgraded to provide >> instructions for both 45 and 80 model. I can try to do it with support. >> >> >> *G.* >> * >> * >> Il giorno 28/giu/2014, alle ore 06:00, >> ovmsdev-request(a)lists.teslaclub.hk >> <mailto:ovmsdev-request@lists.teslaclub.hk> ha scritto: >> >>> Send OvmsDev mailing list submissions to >>> ovmsdev(a)lists.teslaclub.hk <mailto:ovmsdev@lists.teslaclub.hk> >>> >>> To subscribe or unsubscribe via the World Wide Web, visit >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>> or, via email, send a message with subject or body 'help' to >>> ovmsdev-request(a)lists.teslaclub.hk >>> >>> You can reach the person managing the list at >>> ovmsdev-owner(a)lists.teslaclub.hk >>> >>> When replying, please edit your Subject line so it is more specific >>> than "Re: Contents of OvmsDev digest..." >>> >>> >>> Today's Topics: >>> >>> 1. Re: changing android app server IP (Christopher Cook) >>> 2. Re: changing android app server IP (Lee Howard) >>> 3. Re: changing android app server IP (Lee Howard) >>> >>> >>> ---------------------------------------------------------------------- >>> >>> Message: 1 >>> Date: Fri, 27 Jun 2014 12:44:52 +0800 >>> From: Christopher Cook <christopher.cook(a)webprofusion.com> >>> Subject: Re: [Ovmsdev] changing android app server IP >>> To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> >>> Message-ID: <r7evp31xp6nup2wd3sya83eu.1403844292014(a)email.android.com> >>> Content-Type: text/plain; charset=utf-8 >>> >>> Off topic but long term it would be prudent to investigate the cross >>> platform options for the app, otherwise there's a lot of duplicate work. >>> >>> I'd consider HTML/Cordova, Xamarin (and perhaps Xamarin Forms), >>> Titanium Sdk, etc. >>> >>> Not saying cross platform doesn't have its challenges but otherwise >>> there's probably not enough dev resources to expect to develop a >>> complete app for all platforms. >>> >>> Chris >>> >>> Tom Saxton <tom(a)idleloop.com> wrote: >>> >>>> On iOS, the App settings is buried in the System Settings app, a >>>> terrible >>>> UI design. Finally, with iOS 8, there will be a way for apps to send you >>>> straight to the app settings. But for now... >>>> >>>> Open the Setting app, then scroll down to the bottom to find a list of >>>> apps that use the built-in settings mechanism. You'll find an item for >>>> "Open Vehicle". In there you'll find the configuration for your OVMS >>>> account, including the server IP address. >>>> >>>> That's also where you can turn the Open Charge Map stuff on/off and >>>> where >>>> you can override the module's choice for distance and temperature units. >>>> >>>> Arguably the server account should be per-vehicle but I'm guessing the >>>> thought was that anyone who has multiple OVMS vehicles will have >>>> them all >>>> on the same server and making that app-wide means you only have to enter >>>> username, password and server IP once. >>>> >>>> Of course none of this is any help for figuring out how to do it on >>>> Android... >>>> >>>> Tom >>>> >>>> -----Original Message----- >>>> From: Lee Howard <lee.howard(a)mainpine.com> >>>> Reply-To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> >>>> Date: Thursday, June 26, 2014 at 4:22 PM >>>> To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> >>>> Subject: Re: [Ovmsdev] changing android app server IP >>>> >>>>> On 06/11/2014 05:23 PM, Mark Webb-Johnson wrote: >>>>>> I think the 'tmc' server is hard-coded in the Android App. >>>>>> >>>>>> The code on github is up-to-date, if anyone wants to take a stab at >>>>>> making it configurable. >>>>> >>>>> I spent a few days getting acquainted with Android development and >>>>> toying with the OVMS Android app code, loading it onto the Android >>>>> emulator, etc. >>>>> >>>>> I couldn't decide where was the best place was to put an "app settings" >>>>> menu item, and so I caved and downloaded OVMS from the App Store >>>>> onto my >>>>> iPad... >>>>> >>>>>> The iOS App has it in the system settings tab. >>>>> >>>>> I don't see it. Is this in unreleased/unpublished code? >>>>> >>>>> There is the "OVMS Server IP" in the "Parameters" section of the >>>>> "Control" menu for each configured car. However, I believe that refers >>>>> to the server IP configured in the car module and not for the app. AND >>>>> this same section and menu exist on the Android app (after waiting >>>>> long-enough for it to populate... or getting lucky... I can't >>>>> figure out >>>>> which since it often doesn't populate at all). >>>>> >>>>> Since for each car the app needs to talk to the same server as the car >>>>> module it would be ideal for changes made to this "OVMS Server IP" in >>>>> the "Parameters" section to apply to both the IP where the module >>>>> communicates *AND* to where the app communicates for that car, but >>>>> since >>>>> this "Parameters" section doesn't even come up at all until the app can >>>>> talk to the server and module, I don't think that's how it works, >>>>> presently, and it would appear to need a lot of effort to get it >>>>> working >>>>> in that fashion. >>>>> >>>>> It would be nice if I could have different car modules talking to >>>>> different servers and for me to be able to use one app to rule them >>>>> all. The app would merely talk to different servers for each car. >>>>> >>>>> Anyway... since my initial interest is in doing server-side and >>>>> car-module-side developments (and not so much the app-side of things) >>>>> I'm inclined to just make a hard-coded change to the server IP address >>>>> in my Android app and move on for the sake of being productive. >>>>> >>>>> 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 >>>>> _______________________________________________ >>>>> OvmsDev mailing list >>>>> OvmsDev(a)lists.teslaclub.hk >>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> OvmsDev mailing list >>>> OvmsDev(a)lists.teslaclub.hk >>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>> >>> ------------------------------ >>> >>> Message: 2 >>> Date: Fri, 27 Jun 2014 10:38:05 -0700 >>> From: Lee Howard <lee.howard(a)mainpine.com> >>> Subject: Re: [Ovmsdev] changing android app server IP >>> To: ovmsdev(a)lists.teslaclub.hk >>> Message-ID: <53ADABFD.4010407(a)mainpine.com> >>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed >>> >>> On 06/26/2014 08:38 PM, Tom Saxton wrote: >>>> On iOS, the App settings is buried in the System Settings app, a >>>> terrible >>>> UI design. >>> >>> Oh, I see. Thank you. That was very helpful. >>> >>> Yes, it is a terrible UI design by Apple on iOS. >>> >>> I was going to try to do on Android similar to what had been done on >>> iOS, but since this is so terrible, I'd rather not do it like that. >>> >>>> Arguably the server account should be per-vehicle but I'm guessing the >>>> thought was that anyone who has multiple OVMS vehicles will have >>>> them all >>>> on the same server and making that app-wide means you only have to enter >>>> username, password and server IP once. >>>> >>>> Of course none of this is any help for figuring out how to do it on >>>> Android... >>> >>> As I dug-into the Android code better to hard-code the address change I >>> discovered - to my delight - that the app server address is stored in a >>> per-car data object. Yay! So this is nice. I'm going to give this >>> another shot. >>> >>> 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 >>> >>> >>> ------------------------------ >>> >>> Message: 3 >>> Date: Fri, 27 Jun 2014 12:44:16 -0700 >>> From: Lee Howard <lee.howard(a)mainpine.com> >>> Subject: Re: [Ovmsdev] changing android app server IP >>> To: ovmsdev(a)lists.teslaclub.hk >>> Message-ID: <53ADC990.5010708(a)mainpine.com> >>> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" >>> >>> On 06/27/2014 10:38 AM, Lee Howard wrote: >>>> On 06/26/2014 08:38 PM, Tom Saxton wrote: >>>> >>>>> Arguably the server account should be per-vehicle but I'm guessing the >>>>> thought was that anyone who has multiple OVMS vehicles will have them >>>>> all >>>>> on the same server and making that app-wide means you only have to >>>>> enter >>>>> username, password and server IP once. >>>>> >>>>> Of course none of this is any help for figuring out how to do it on >>>>> Android... >>>> >>>> As I dug-into the Android code better to hard-code the address change >>>> I discovered - to my delight - that the app server address is stored >>>> in a per-car data object. Yay! So this is nice. I'm going to give >>>> this another shot. >>> >>> Here is the patch. Someone with privs can apply it and commit these >>> changes to the repository if it meets with their approval. >>> >>> It's a very small enhancement - basically permitting an interface to >>> sel_server in the CarData object. The interface is right where it >>> should be, IMO: right where you enter the vehicle info and passwords. >>> The default is left to "tmc.openvehicles.com", but the user now has the >>> capability to modify it (on a per-car basis, even). >>> >>> I did not change the sel_server initialization value of >>> "tmc.openvehicles.com". I could have changed this to "" as with the >>> other CarData strings, but it probably makes little difference. Leaving >>> it to initialize with "tmc.openvehicles.com" possibly it could be >>> confusing to someone later who doesn't recognize that the initialized >>> value is always overwritten by the configured value (as with the other >>> CarData strings which are initialized to ""). If someone cares they can >>> modify that at the top of CarData.java. >>> >>> This patch also makes one obvious grammatical correction in a string >>> appearing on the same page layout. >>> >>> If there is any concern just look at the patch - it's a very, very >>> benign set of changes. This e-mail is longer than the patch is. >>> >>> 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 >>>

1 0

changing android app server IP
by Lee Howard 29 Jun '14

29 Jun '14

I need to set up my own OVMS server for development use. I don't see any way in the Android app to modify the server IP that the app uses. In examining the Android code I do see it tucked into the app preferences, but since my Android device is not rooted, I can't get at that without recompiling the app and reinstalling my customized version. Do I really need to rebuild the Android app from scratch in order to modify the server IP? Am I missing something obvious? 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

3 8

Re: [Ovmsdev] Twizy 45
by Gianluca Magalotti 28 Jun '14

28 Jun '14

First of all please confirm that CFG commands (SPEED, POWER, RECUP, etc.) will work properly with Twizy 45. I've tried them on it and everything In any case I think we have to update twizy documentation at page 26 to be less ambiguous. More in general I think guide should be upgraded to provide instructions for both 45 and 80 model. I can try to do it with support. G. Il giorno 28/giu/2014, alle ore 06:00, ovmsdev-request(a)lists.teslaclub.hk ha scritto: > Send OvmsDev mailing list submissions to > ovmsdev(a)lists.teslaclub.hk > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > or, via email, send a message with subject or body 'help' to > ovmsdev-request(a)lists.teslaclub.hk > > You can reach the person managing the list at > ovmsdev-owner(a)lists.teslaclub.hk > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OvmsDev digest..." > > > Today's Topics: > > 1. Re: changing android app server IP (Christopher Cook) > 2. Re: changing android app server IP (Lee Howard) > 3. Re: changing android app server IP (Lee Howard) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 27 Jun 2014 12:44:52 +0800 > From: Christopher Cook <christopher.cook(a)webprofusion.com> > Subject: Re: [Ovmsdev] changing android app server IP > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > Message-ID: <r7evp31xp6nup2wd3sya83eu.1403844292014(a)email.android.com> > Content-Type: text/plain; charset=utf-8 > > Off topic but long term it would be prudent to investigate the cross platform options for the app, otherwise there's a lot of duplicate work. > > I'd consider HTML/Cordova, Xamarin (and perhaps Xamarin Forms), Titanium Sdk, etc. > > Not saying cross platform doesn't have its challenges but otherwise there's probably not enough dev resources to expect to develop a complete app for all platforms. > > Chris > > Tom Saxton <tom(a)idleloop.com> wrote: > >> On iOS, the App settings is buried in the System Settings app, a terrible >> UI design. Finally, with iOS 8, there will be a way for apps to send you >> straight to the app settings. But for now... >> >> Open the Setting app, then scroll down to the bottom to find a list of >> apps that use the built-in settings mechanism. You'll find an item for >> "Open Vehicle". In there you'll find the configuration for your OVMS >> account, including the server IP address. >> >> That's also where you can turn the Open Charge Map stuff on/off and where >> you can override the module's choice for distance and temperature units. >> >> Arguably the server account should be per-vehicle but I'm guessing the >> thought was that anyone who has multiple OVMS vehicles will have them all >> on the same server and making that app-wide means you only have to enter >> username, password and server IP once. >> >> Of course none of this is any help for figuring out how to do it on >> Android... >> >> Tom >> >> -----Original Message----- >> From: Lee Howard <lee.howard(a)mainpine.com> >> Reply-To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> >> Date: Thursday, June 26, 2014 at 4:22 PM >> To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> >> Subject: Re: [Ovmsdev] changing android app server IP >> >>> On 06/11/2014 05:23 PM, Mark Webb-Johnson wrote: >>>> I think the 'tmc' server is hard-coded in the Android App. >>>> >>>> The code on github is up-to-date, if anyone wants to take a stab at >>>> making it configurable. >>> >>> I spent a few days getting acquainted with Android development and >>> toying with the OVMS Android app code, loading it onto the Android >>> emulator, etc. >>> >>> I couldn't decide where was the best place was to put an "app settings" >>> menu item, and so I caved and downloaded OVMS from the App Store onto my >>> iPad... >>> >>>> The iOS App has it in the system settings tab. >>> >>> I don't see it. Is this in unreleased/unpublished code? >>> >>> There is the "OVMS Server IP" in the "Parameters" section of the >>> "Control" menu for each configured car. However, I believe that refers >>> to the server IP configured in the car module and not for the app. AND >>> this same section and menu exist on the Android app (after waiting >>> long-enough for it to populate... or getting lucky... I can't figure out >>> which since it often doesn't populate at all). >>> >>> Since for each car the app needs to talk to the same server as the car >>> module it would be ideal for changes made to this "OVMS Server IP" in >>> the "Parameters" section to apply to both the IP where the module >>> communicates *AND* to where the app communicates for that car, but since >>> this "Parameters" section doesn't even come up at all until the app can >>> talk to the server and module, I don't think that's how it works, >>> presently, and it would appear to need a lot of effort to get it working >>> in that fashion. >>> >>> It would be nice if I could have different car modules talking to >>> different servers and for me to be able to use one app to rule them >>> all. The app would merely talk to different servers for each car. >>> >>> Anyway... since my initial interest is in doing server-side and >>> car-module-side developments (and not so much the app-side of things) >>> I'm inclined to just make a hard-coded change to the server IP address >>> in my Android app and move on for the sake of being productive. >>> >>> 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 >>> _______________________________________________ >>> OvmsDev mailing list >>> OvmsDev(a)lists.teslaclub.hk >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>> >> >> >> _______________________________________________ >> OvmsDev mailing list >> OvmsDev(a)lists.teslaclub.hk >> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > ------------------------------ > > Message: 2 > Date: Fri, 27 Jun 2014 10:38:05 -0700 > From: Lee Howard <lee.howard(a)mainpine.com> > Subject: Re: [Ovmsdev] changing android app server IP > To: ovmsdev(a)lists.teslaclub.hk > Message-ID: <53ADABFD.4010407(a)mainpine.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 06/26/2014 08:38 PM, Tom Saxton wrote: >> On iOS, the App settings is buried in the System Settings app, a terrible >> UI design. > > Oh, I see. Thank you. That was very helpful. > > Yes, it is a terrible UI design by Apple on iOS. > > I was going to try to do on Android similar to what had been done on > iOS, but since this is so terrible, I'd rather not do it like that. > >> Arguably the server account should be per-vehicle but I'm guessing the >> thought was that anyone who has multiple OVMS vehicles will have them all >> on the same server and making that app-wide means you only have to enter >> username, password and server IP once. >> >> Of course none of this is any help for figuring out how to do it on >> Android... > > As I dug-into the Android code better to hard-code the address change I > discovered - to my delight - that the app server address is stored in a > per-car data object. Yay! So this is nice. I'm going to give this > another shot. > > 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 > > > ------------------------------ > > Message: 3 > Date: Fri, 27 Jun 2014 12:44:16 -0700 > From: Lee Howard <lee.howard(a)mainpine.com> > Subject: Re: [Ovmsdev] changing android app server IP > To: ovmsdev(a)lists.teslaclub.hk > Message-ID: <53ADC990.5010708(a)mainpine.com> > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" > > On 06/27/2014 10:38 AM, Lee Howard wrote: >> On 06/26/2014 08:38 PM, Tom Saxton wrote: >> >>> Arguably the server account should be per-vehicle but I'm guessing the >>> thought was that anyone who has multiple OVMS vehicles will have them >>> all >>> on the same server and making that app-wide means you only have to enter >>> username, password and server IP once. >>> >>> Of course none of this is any help for figuring out how to do it on >>> Android... >> >> As I dug-into the Android code better to hard-code the address change >> I discovered - to my delight - that the app server address is stored >> in a per-car data object. Yay! So this is nice. I'm going to give >> this another shot. > > Here is the patch. Someone with privs can apply it and commit these > changes to the repository if it meets with their approval. > > It's a very small enhancement - basically permitting an interface to > sel_server in the CarData object. The interface is right where it > should be, IMO: right where you enter the vehicle info and passwords. > The default is left to "tmc.openvehicles.com", but the user now has the > capability to modify it (on a per-car basis, even). > > I did not change the sel_server initialization value of > "tmc.openvehicles.com". I could have changed this to "" as with the > other CarData strings, but it probably makes little difference. Leaving > it to initialize with "tmc.openvehicles.com" possibly it could be > confusing to someone later who doesn't recognize that the initialized > value is always overwritten by the configured value (as with the other > CarData strings which are initialized to ""). If someone cares they can > modify that at the top of CarData.java. > > This patch also makes one obvious grammatical correction in a string > appearing on the same page layout. > > If there is any concern just look at the patch - it's a very, very > benign set of changes. This e-mail is longer than the patch is. > > 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 >

2 1