- OvmsDev - Open Vehicles

Re: [Ovmsdev] OvmsDev Digest, Vol 17, Issue 7
by Bennett Leeds 02 Jun '13

02 Jun '13

I would say to keep things simpler that if you're doing a standard charge, always optimize for cost (since a full standard charge isn't bad for the battery at all), but if the car is set for Range Charge, then do the "finish by" thing. My (Nor Cal PGE) TOU periods are: Summer M-F Summer Weekends Summer Rates Peak: 2pm-9pm None $0.30-$0.54/kWh Part-Peak: 7am-2pm & 9pm-mid 5pm-9pm $0.09-$0.34/kWh Off-Peak: mid-7am 9pm-mid & mid-5pm $0.04-$0.28/kWh Winter M-F Winter Weekends Winter Rates Peak: None None None Part-Peak: 7am-mid 5pm-9pm $0.09-$0.34/kWh Off-Peak: mid-7am 9pm-mid & mid-5pm $0.04-$0.30/kWh The new Nor Cal PGE TOU periods get rid of summer/winter time differences and will be: M-F Weekends Rates Peak: 2pm-9pm 3pm-7pm summer:$0.36 winter:$0.27 Part-Peak: 7am-2pm & 9pm-11pm None summer:$0.20 winter:$0.16 Off-Peak: 11pm-mid & mid-7am 7pm-mid & mid-3pm summer:$0.10 winter:$0.10 I'm attaching PGE's letter on TOU periods. Note that we could just leave the off-peak entries off, since even PGE says "Off-peak is all other times." Just enter peak and part-peak and whatever's left is off-peak. Probably the cases I'm worried about are edge cases, where the charging amperage is so low that it won't get to full at the next upcoming off-peak period, and so don't really matter. Since the Off-Peaks are always followed by a Part-Peak, there would be no reason not to wait until the Off-Peak to start any charging, since any time overflow would be in the next lowest tier anyway. For Range charging on trips, I would suggest that if charging time permits, it would be better to do a cost-optimized Standard charge, followed by a time-optimized Range charge. That's what I do manually today - charge Standard overnight and then when I wake up the next morning, switch to Range and charge again. By the time I'm showered, fed, and packed, the car is Range charge full. As long as you can calculate the time from Standard Full to Range Full you can work out when to start the Range to be Range full in time. I also suggest this saves energy, as there's less aggressive battery cooling in standard charge. Of course, some people might be battery coolness freaks and want to range charge all the time but with stopping the charge early (eg, at the same SOC as a standard full). That would keep the battery from getting too full while keeping the battery very cool. However, I think there are issues with performance and even battery life trying to pull a lot of power out of a too-cool battery. Range Mode charge leaves you in Range mode driving, which reduces power. I think that's not only to help your charge go faster, but to reduce the strain on a too-cool battery. - Bennett On Sun, Jun 2, 2013 at 6:05 AM, <ovmsdev-request(a)lists.teslaclub.hk> wrote: > 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: Advanced Charge Control (ACC) (Mark Webb-Johnson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 2 Jun 2013 21:05:12 +0800 > From: Mark Webb-Johnson <mark(a)webb-johnson.net> > Subject: Re: [Ovmsdev] Advanced Charge Control (ACC) > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > Message-ID: <943A7C26-8D84-4086-9FEF-37DB7B42233B(a)webb-johnson.net> > Content-Type: text/plain; charset="iso-8859-1" > > Bennett, > > I'm a little confused on why we need this. > > Say you have three TOU rates: > (a) 6am->6pm the most expensive > (b) 6pm->2am the middle rate > (c) 2am-6am the cheapest > > Now, you leave for work at 8am. > > Assume a charge requires 5 hours to complete. > > You could put in 8am as the departure time, in which case you would get 3 > hours in rate (c) and 2 hours in rate (a). > > Or you could just put in the end of the most cheap rate, in which case the > charge would be 1 hour in rate (b) and 4 hours in rate (c). > > Surely when you are doing a complete-charge-by-time style of charge, you > could either put in the time you leave (to optimise for battery lifetime) > or the end of the cheap rate band (to reduce charge cost)? > > My concern is because of (a) complicating the setup and configuration (in > particular where user has to choose been optimising his battery lifetime or > electricity bill), and (b) complicating the code (eeprom, ram and flash > storage are very very tight). > > Could you provide some examples for your electricity provider? What are > the current rate bands, and what time are they for weekdays and weekends? > > Regards, Mark. > > On 2 Jun, 2013, at 12:22 PM, Bennett Leeds <bennettleeds(a)gmail.com> wrote: > > > This is really exciting. I would request that the Charge Timer should be > based on Time Of Use periods, in order to automatically have the lowest > charging costs while still having a full vehicle when you need it. > > > > Here in the states, many EV owners are on time of use meters. The > cheapest period times very not only by day of the week, but also by season. > I'd like to be able "teach" the car what the TOU periods are, tell it what > time I leave each morning, and then have the car figure out the cheapest > way to get me a full charge by the time I need it given the upcoming TOU > periods between plug-in and when I need to leave. > > > > The TOU periods could be specified in 3 levels per weekday and 3 levels > per weekend. With 2 seasons, that would be 12 fields to be entered. Time > Needed could be specified per weekday and per weekend - so 14 time fields > total for this to work. > > > > The logic is pretty straightforward. When the car is off and plugged in, > look to see when the full charge is needed by. Either know the amperage > available, or use the cooldown to get a pilot signal. Obey any lower > current limits set by owners (which might be done due to old breakers, > etc.). Then figure out if the cheapest time period is long enough to fully > charge the car. If not, then do just enough charging in the second cheapest > time period to result is a full charge, and if that won't be enough, then > do just enough charging in the most expensive time period to result in a > full charge after the upcoming second cheapest and most cheapest periods. > > > > I'd be happy to be a tester for whatever you come up with. > > > > thanks > > - Bennett > > > > > > > > > > > > On Sat, Jun 1, 2013 at 9:00 PM, <ovmsdev-request(a)lists.teslaclub.hk> > wrote: > > 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: Advanced Charge Control (ACC) (Tom Saxton) > > 2. Re: Advanced Charge Control (ACC) (Mark Webb-Johnson) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Sat, 01 Jun 2013 12:02:41 -0700 > > From: Tom Saxton <tom(a)idleloop.com> > > Subject: Re: [Ovmsdev] Advanced Charge Control (ACC) > > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > > Message-ID: <CDCF9361.804A3%tom(a)idleloop.com> > > Content-Type: text/plain; charset="US-ASCII" > > > > Mark, > > > > This all sounds great. It covers everything I want, and more. > Personally, I > > think three zones is plenty if you want to save some parameter space. > > > > Tom > > > > on 5/31/13 6:56 AM, Mark Webb-Johnson wrote: > > > > > I've spent some time planning this, and now have the time to try to > get it > > > done. The observant will have noticed a new branch ACC just appeared > in the > > > github repository. > > > > > > This is primarily for Tesla Roadster owners, but once we work out how > to do > > > charge control in other cars, it will have use for them. > > > > > > The premise of what I'm thinking is a replacement for the limited > charge > > > control in the car, to make an Advanced Charge Control: > > > > > > We have the concept of a 'charge location'. This is an area (square, > because > > > it is easiest) around a GPS location. An area of 200m x 200m, centred > on the > > > charge location, should be sufficient for gps inaccuracies. Up to 5 > such > > > charge locations can be defined (I'm thinking home, work, and one > other). > > > Once the car enters a charge location, an action can be triggered. At > the > > > moment, I'm only thinking of automatic home link activation, but > others are > > > possible. > > > When a car is turned off, while in a charge location, acc is enabled > and > > > current charge settings are saved. > > > When a car is turned on, while in a charge location, acc is disabled > and > > > previous charge settings are restored. > > > Features that acc should support include: > > > Homelink activation. > > > Cooldown (cool the car using a sequence of low amperage range mode > charges) - > > > this would need a minimum temperature (don't cool down unless ESS > temperature > > > is above this), a desired temperature (cool down until the ESS reaches > this > > > temperature),and a time limit (stop cooling down if we've been trying > for too > > > long). > > > Charge mode (standard, storage, range, performance). > > > Charge current limit. > > > Various charge types, including: > > > Charge on plug-in > > > Start charge at specific time > > > Complete charge by specific time > > > Desired charge limit (SOC%, ideal miles/kilometers, or full) > > > In addition to the charge locations, acc should be able to be turned > on, > > > one-off, for the current location. This should be done after the car > is turned > > > off, before plugging in. It will be effective until the car is turned > on > > > again. > > > It should also be possible to use this one-off acc to override the > charge > > > control for the current location. This will be effective until the car > is > > > turned on again. > > > Control, and status, is possible by SMS commands. > > > Control is also possible by a new tab added to the apps. I'm going to > do > > > iPhone first, with the existing charge control moved to a new "Charge" > tab. > > > > > > I'm not sure how to do the 'specific time'. This could be > > > simple-to-ludicrously-complex. My inclination is to just put a > day-of-week > > > filter on each charge location - with acc only being enabled if the day > > > matches. More than one location could be created for each physical gps > > > location, with different day matches, to control how that would behave. > > > > > > Changes to be made include: > > > > > > Move the roadster digital speedo experimental feature to a fully > supported > > > features, and give it a permanent feature storage number. > > > Assign five new permanent parameters, one each for five charge > locations > > > (home, work, other, or whatever they want to be known as - we just > call them > > > #1, #2, #3, #4 and #5). > > > The parameter storage for these new locations includes the charging > > > preferences for each location. > > > We would also need a parameter for time zone. > > > Add a new module called "acc". > > > If "acc" detects we are at a known charge location, it will take over > the > > > charge control from the car. > > > The "acc" will also support commands for the current location, and > will be > > > able to take over charge control from now until the car is next driven. > > > > > > Please let me have your comments / suggestions. I'll handle the > coding, but > > > I'll need lots of help testing. > > > > > > Regards, Mark. > > > > > > _______________________________________________ > > > OvmsDev mailing list > > > OvmsDev(a)lists.teslaclub.hk > > > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > > > > > > > > > ------------------------------ > > > > Message: 2 > > Date: Sun, 2 Jun 2013 09:29:37 +0800 > > From: Mark Webb-Johnson <mark(a)webb-johnson.net> > > Subject: Re: [Ovmsdev] Advanced Charge Control (ACC) > > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > > Message-ID: <AF3A64D7-E806-4CF3-94A8-360D170626C4(a)webb-johnson.net> > > Content-Type: text/plain; charset=us-ascii > > > > Tom, > > > > My original design was 3 (home, work, other). I increased to 5 to allow > for different schedules weekday / weekend, etc. > > > > Lets see how it works out. More would be good. > > > > Regards, Mark > > > > On 2 Jun, 2013, at 3:02 AM, Tom Saxton <tom(a)idleloop.com> wrote: > > > > > Mark, > > > > > > This all sounds great. It covers everything I want, and more. > Personally, I > > > think three zones is plenty if you want to save some parameter space. > > > > > > Tom > > > > > > on 5/31/13 6:56 AM, Mark Webb-Johnson wrote: > > > > > >> I've spent some time planning this, and now have the time to try to > get it > > >> done. The observant will have noticed a new branch ACC just appeared > in the > > >> github repository. > > >> > > >> This is primarily for Tesla Roadster owners, but once we work out how > to do > > >> charge control in other cars, it will have use for them. > > >> > > >> The premise of what I'm thinking is a replacement for the limited > charge > > >> control in the car, to make an Advanced Charge Control: > > >> > > >> We have the concept of a 'charge location'. This is an area (square, > because > > >> it is easiest) around a GPS location. An area of 200m x 200m, centred > on the > > >> charge location, should be sufficient for gps inaccuracies. Up to 5 > such > > >> charge locations can be defined (I'm thinking home, work, and one > other). > > >> Once the car enters a charge location, an action can be triggered. At > the > > >> moment, I'm only thinking of automatic home link activation, but > others are > > >> possible. > > >> When a car is turned off, while in a charge location, acc is enabled > and > > >> current charge settings are saved. > > >> When a car is turned on, while in a charge location, acc is disabled > and > > >> previous charge settings are restored. > > >> Features that acc should support include: > > >> Homelink activation. > > >> Cooldown (cool the car using a sequence of low amperage range mode > charges) - > > >> this would need a minimum temperature (don't cool down unless ESS > temperature > > >> is above this), a desired temperature (cool down until the ESS > reaches this > > >> temperature),and a time limit (stop cooling down if we've been trying > for too > > >> long). > > >> Charge mode (standard, storage, range, performance). > > >> Charge current limit. > > >> Various charge types, including: > > >> Charge on plug-in > > >> Start charge at specific time > > >> Complete charge by specific time > > >> Desired charge limit (SOC%, ideal miles/kilometers, or full) > > >> In addition to the charge locations, acc should be able to be turned > on, > > >> one-off, for the current location. This should be done after the car > is turned > > >> off, before plugging in. It will be effective until the car is turned > on > > >> again. > > >> It should also be possible to use this one-off acc to override the > charge > > >> control for the current location. This will be effective until the > car is > > >> turned on again. > > >> Control, and status, is possible by SMS commands. > > >> Control is also possible by a new tab added to the apps. I'm going to > do > > >> iPhone first, with the existing charge control moved to a new > "Charge" tab. > > >> > > >> I'm not sure how to do the 'specific time'. This could be > > >> simple-to-ludicrously-complex. My inclination is to just put a > day-of-week > > >> filter on each charge location - with acc only being enabled if the > day > > >> matches. More than one location could be created for each physical gps > > >> location, with different day matches, to control how that would > behave. > > >> > > >> Changes to be made include: > > >> > > >> Move the roadster digital speedo experimental feature to a fully > supported > > >> features, and give it a permanent feature storage number. > > >> Assign five new permanent parameters, one each for five charge > locations > > >> (home, work, other, or whatever they want to be known as - we just > call them > > >> #1, #2, #3, #4 and #5). > > >> The parameter storage for these new locations includes the charging > > >> preferences for each location. > > >> We would also need a parameter for time zone. > > >> Add a new module called "acc". > > >> If "acc" detects we are at a known charge location, it will take over > the > > >> charge control from the car. > > >> The "acc" will also support commands for the current location, and > will be > > >> able to take over charge control from now until the car is next > driven. > > >> > > >> Please let me have your comments / suggestions. I'll handle the > coding, but > > >> I'll need lots of help testing. > > >> > > >> Regards, Mark. > > >> > > >> _______________________________________________ > > >> 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 > > > > > > ------------------------------ > > > > _______________________________________________ > > OvmsDev mailing list > > OvmsDev(a)lists.teslaclub.hk > > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > > > > > End of OvmsDev Digest, Vol 17, Issue 5 > > ************************************** > > > > _______________________________________________ > > OvmsDev mailing list > > OvmsDev(a)lists.teslaclub.hk > > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > >

1 0

Re: [Ovmsdev] Tesla Roadster - COOLDOWN (not working for me)
by Bennett Leeds 02 Jun '13

02 Jun '13

I haven't done it when the temps have been that hot, but up to 36C a 240volt, 13 amp cooldown has always worked for me. V2.5 model. - Bennett On Sun, Jun 2, 2013 at 6:39 AM, <ovmsdev-request(a)lists.teslaclub.hk> wrote: > 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. Tesla Roadster - COOLDOWN (not working for me) (Mark Webb-Johnson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 2 Jun 2013 21:39:21 +0800 > From: Mark Webb-Johnson <mark(a)webb-johnson.net> > Subject: [Ovmsdev] Tesla Roadster - COOLDOWN (not working for me) > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > Message-ID: <845C3D7E-4BD9-434C-AD19-790B260CCE7E(a)webb-johnson.net> > Content-Type: text/plain; charset="us-ascii" > > > It was blistering hot today in Hong Kong, so when I got home from a drive > I thought I'd try to get cool down working again. I set the car to 220V 10A > and 13A range mode charges, and here is what I got: > > 2013-06-02 02:26:24.653242 -0400 info main: #102 C EV915 rx msg S > 72,K,3,0,prepare,range,282,240,10,0,100,0,10,13,3,0,0,-1,155.40,-1 > 2013-06-02 02:26:26.433171 -0400 info main: #102 C EV915 rx msg S > 72,K,223,0,charging,range,282,240,10,0,100,0,5,1,3,0,0,-1,155.40,-1 > 2013-06-02 02:26:31.811202 -0400 info main: #102 C EV915 rx msg D > 124,8,4,44,74,39,130,143065,0,163,38,2,120,120,13.1,33,13.1,0 > 2013-06-02 02:26:31.812661 -0400 info main: #102 C EV915 rx msg S > 72,K,221,0,charging,range,282,240,10,0,100,0,5,1,3,0,0,-1,155.40,-1 > 2013-06-02 02:27:18.411345 -0400 info main: #102 C EV915 rx msg S > 72,K,222,10,charging,range,282,240,10,0,100,0,5,1,3,0,0,-1,155.40,483 > 2013-06-02 02:27:31.869285 -0400 info main: #102 C EV915 rx msg S > 72,K,223,10,charging,range,282,240,10,1,100,0,5,1,3,0,0,-1,155.40,483 > 2013-06-02 02:27:31.871196 -0400 info main: #102 C EV915 rx msg D > 124,8,4,46,71,40,130,143065,0,223,38,2,120,120,13.0,33,13.1,0 > 2013-06-02 02:28:33.931349 -0400 info main: #102 C EV915 rx msg S > 72,K,223,10,charging,range,282,240,10,2,100,0,5,1,3,0,0,-1,155.40,482 > 2013-06-02 02:28:33.933551 -0400 info main: #102 C EV915 rx msg D > 124,8,4,47,69,40,130,143065,0,283,39,2,120,119,13.0,33,13.1,0 > 2013-06-02 02:29:34.969362 -0400 info main: #102 C EV915 rx msg S > 72,K,220,10,charging,range,282,240,10,3,100,0,5,1,3,0,0,-1,155.40,487 > 2013-06-02 02:29:34.971570 -0400 info main: #102 C EV915 rx msg D > 124,8,4,48,67,40,130,143065,0,344,39,2,120,118,13.0,33,13.1,0 > 2013-06-02 02:30:35.208051 -0400 info main: #102 C EV915 rx msg S > 72,K,221,10,charging,range,282,240,10,4,100,0,5,1,3,0,0,-1,155.40,482 > 2013-06-02 02:30:35.210313 -0400 info main: #102 C EV915 rx msg D > 124,8,4,48,65,40,130,143065,0,404,39,2,120,117,13.0,33,13.1,0 > 2013-06-02 02:31:36.708542 -0400 info main: #102 C EV915 rx msg S > 72,K,221,10,charging,range,283,240,10,5,100,0,5,1,3,0,0,-1,155.40,474 > 2013-06-02 02:31:36.710902 -0400 info main: #102 C EV915 rx msg D > 124,8,4,48,64,40,130,143065,0,464,39,2,120,115,13.1,33,13.1,0 > 2013-06-02 02:32:30.467402 -0400 info main: #102 C EV915 rx msg D > 124,8,4,48,63,40,130,143065,0,524,39,2,120,120,13.1,33,13.1,0 > 2013-06-02 02:32:48.448194 -0400 info main: #102 C EV915 rx msg S > 72,K,221,13,charging,range,283,240,13,6,100,0,5,1,3,0,0,-1,155.40,485 > 2013-06-02 02:32:48.450414 -0400 info main: #102 C EV915 rx msg D > 124,8,4,48,63,40,130,143065,0,534,39,2,120,120,13.0,33,13.1,0 > 2013-06-02 02:33:42.125427 -0400 info main: #102 C EV915 rx msg S > 72,K,223,13,charging,range,283,240,13,7,100,0,5,1,3,0,0,-1,155.40,344 > 2013-06-02 02:33:42.127944 -0400 info main: #102 C EV915 rx msg D > 124,8,4,48,61,40,130,143065,0,594,39,2,120,120,13.0,33,13.1,0 > 2013-06-02 02:34:43.083457 -0400 info main: #102 C EV915 rx msg S > 72,K,220,13,charging,range,283,240,13,8,100,0,5,1,3,0,0,-1,155.40,343 > 2013-06-02 02:34:43.085865 -0400 info main: #102 C EV915 rx msg D > 124,8,4,48,60,40,130,143065,0,655,39,2,120,120,13.0,33,13.1,0 > 2013-06-02 02:35:57.476830 -0400 info main: #102 C EV915 rx msg S > 72,K,220,13,charging,range,283,242,13,9,100,0,5,1,3,0,0,-1,155.40,343 > 2013-06-02 02:35:57.479805 -0400 info main: #102 C EV915 rx msg D > 124,8,4,48,59,40,130,143065,0,716,39,2,120,120,13.1,33,13.1,0 > 2013-06-02 02:36:19.381948 -0400 info main: #102 C EV915 rx msg S > 72,K,221,13,charging,range,283,242,13,9,100,0,5,1,3,0,0,-1,155.40,343 > 2013-06-02 02:36:19.387764 -0400 info main: #102 C EV915 rx msg D > 124,8,4,48,59,40,130,143065,0,746,39,2,120,117,13.1,33,13.1,0 > 2013-06-02 02:36:20.064292 -0400 info main: #102 C EV915 rx msg D > 124,8,4,48,59,40,130,143065,0,746,39,2,120,116,13.1,33,13.1,0 > 2013-06-02 02:38:08.322698 -0400 info main: #102 C EV915 rx msg S > 72,K,222,13,charging,range,283,242,13,11,100,0,5,1,3,0,0,-1,155.40,340 > 2013-06-02 02:38:08.324403 -0400 info main: #102 C EV915 rx msg D > 124,8,4,48,57,40,130,143065,0,837,39,2,120,119,13.1,33,13.1,0 > 2013-06-02 02:47:48.833122 -0400 info main: #102 C EV915 rx msg S > 72,K,223,13,charging,range,285,242,13,21,100,1,5,1,3,0,0,-1,155.40,353 > 2013-06-02 02:47:48.834882 -0400 info main: #102 C EV915 rx msg D > 124,8,4,48,52,37,130,143065,0,1435,45,2,120,117,13.0,33,13.1,0 > 2013-06-02 02:53:03.289711 -0400 info main: #102 C EV915 rx msg S > 73,K,221,13,charging,range,286,243,13,26,100,1,5,1,3,0,0,-1,155.40,362 > 2013-06-02 02:53:03.293934 -0400 info main: #102 C EV915 rx msg D > 124,8,4,48,51,37,130,143065,0,1748,47,2,120,111,13.0,33,13.1,0 > 2013-06-02 02:53:18.948786 -0400 info main: #102 C EV915 rx msg D > 124,8,4,48,51,37,130,143065,0,1769,47,2,120,116,13.0,33,13.1,0 > 2013-06-02 02:53:54.371628 -0400 info main: #102 C EV915 rx msg S > 73,K,3,0,stopped,range,286,243,13,26,100,1,3,21,3,0,0,-1,155.40,362 > 2013-06-02 02:53:55.111864 -0400 info main: #102 C EV915 rx msg D > 108,8,4,47,51,37,130,143065,0,1779,47,2,120,119,13.0,33,13.1,0 > 2013-06-02 02:53:55.113231 -0400 info main: #102 C EV915 rx msg S > 73,K,1,0,stopped,range,286,243,13,26,100,1,3,21,3,0,0,-1,155.40,362 > 2013-06-02 02:53:55.114938 -0400 info main: #102 C EV915 rx msg D > 108,8,4,45,50,37,130,143065,0,1809,47,2,120,120,13.1,33,13.1,0 > 2013-06-02 02:54:05.867679 -0400 info main: #102 C EV915 rx msg D > 108,8,4,45,50,37,130,143065,0,1809,47,2,120,118,13.1,33,13.1,0 > 2013-06-02 02:54:08.290338 -0400 info main: #102 C EV915 rx msg D > 108,8,4,45,50,37,130,143065,0,1819,47,2,120,118,13.1,33,13.1,0 > 2013-06-02 02:54:18.749731 -0400 info main: #102 C EV915 rx msg D > 108,8,4,44,50,37,130,143065,0,1830,47,2,120,117,13.1,33,13.1,0 > 2013-06-02 02:54:27.467551 -0400 info main: #102 C EV915 rx msg S > 73,K,86,0,charging,range,286,243,10,26,100,1,5,1,3,0,0,-1,155.40,362 > 2013-06-02 02:54:27.947474 -0400 info main: #102 C EV915 rx msg S > 73,K,221,0,charging,range,286,243,10,27,100,1,5,1,3,0,0,-1,155.40,-1 > 2013-06-02 02:54:32.591240 -0400 info main: #102 C EV915 rx msg D > 124,8,4,44,50,37,130,143065,0,1840,47,2,120,119,13.1,33,13.1,0 > 2013-06-02 02:54:32.592638 -0400 info main: #102 C EV915 rx msg S > 73,K,222,0,charging,range,286,243,10,27,100,1,5,1,3,0,0,-1,155.40,-1 > 2013-06-02 02:56:35.248727 -0400 info main: #102 C EV915 rx msg S > 73,K,220,10,charging,range,286,243,10,29,100,1,5,1,3,0,0,-1,155.40,498 > 2013-06-02 02:56:35.252732 -0400 info main: #102 C EV915 rx msg D > 124,8,4,47,50,37,130,143065,0,1970,48,2,120,120,13.0,33,13.1,0 > 2013-06-02 02:57:36.643939 -0400 info main: #102 C EV915 rx msg S > 73,K,222,10,charging,range,286,243,10,29,100,1,5,1,3,0,0,-1,155.40,504 > 2013-06-02 02:57:36.646202 -0400 info main: #102 C EV915 rx msg D > 124,8,4,47,50,37,130,143065,0,2000,48,2,120,117,13.1,33,13.1,0 > 2013-06-02 02:58:41.228929 -0400 info main: #102 C EV915 rx msg S > 73,K,222,10,charging,range,286,243,10,30,100,1,5,1,3,0,0,-1,155.40,508 > 2013-06-02 02:58:41.231097 -0400 info main: #102 C EV915 rx msg D > 124,8,4,47,49,37,130,143065,0,2060,49,2,120,116,13.0,33,13.1,0 > 2013-06-02 02:59:14.084569 -0400 info main: #102 C EV915 rx msg S > 73,K,222,10,charging,range,286,243,10,31,100,1,5,1,3,0,0,-1,155.40,513 > 2013-06-02 02:59:14.087038 -0400 info main: #102 C EV915 rx msg D > 124,8,4,47,49,37,130,143065,0,2120,49,2,120,114,13.0,33,13.1,0 > 2013-06-02 03:00:53.585786 -0400 info main: #102 C EV915 rx msg S > 73,K,220,10,charging,range,286,243,10,32,100,1,5,1,3,0,0,-1,155.40,508 > 2013-06-02 03:00:53.588020 -0400 info main: #102 C EV915 rx msg D > 124,8,4,47,49,37,130,143065,0,2180,49,2,120,113,13.0,33,13.1,0 > 2013-06-02 03:01:17.004554 -0400 info main: #102 C EV915 rx msg S > 73,K,221,10,charging,range,286,243,10,33,100,1,5,1,3,0,0,-1,155.40,513 > 2013-06-02 03:01:17.006333 -0400 info main: #102 C EV915 rx msg D > 124,8,4,47,49,38,130,143065,0,2251,50,2,120,120,13.1,33,13.1,0 > 2013-06-02 03:02:20.183015 -0400 info main: #102 C EV915 rx msg S > 73,K,219,10,charging,range,286,243,10,34,100,1,5,1,3,0,0,-1,155.40,518 > 2013-06-02 03:02:20.186090 -0400 info main: #102 C EV915 rx msg D > 124,8,4,47,48,38,130,143065,0,2311,50,2,120,120,13.0,33,13.1,0 > 2013-06-02 03:03:20.463407 -0400 info main: #102 C EV915 rx msg S > 73,K,220,10,charging,range,286,243,10,35,100,2,5,1,3,0,0,-1,155.40,512 > 2013-06-02 03:03:20.465812 -0400 info main: #102 C EV915 rx msg D > 124,8,4,47,48,38,130,143065,0,2371,51,2,120,119,13.0,33,13.1,0 > 2013-06-02 03:04:22.479305 -0400 info main: #102 C EV915 rx msg S > 73,K,221,10,charging,range,286,243,10,36,100,2,5,1,3,0,0,-1,155.40,512 > 2013-06-02 03:04:22.480838 -0400 info main: #102 C EV915 rx msg D > 124,8,4,47,48,38,130,143065,0,2431,51,2,120,118,13.0,33,13.1,0 > 2013-06-02 03:05:22.922594 -0400 info main: #102 C EV915 rx msg S > 73,K,222,10,charging,range,288,243,10,37,100,2,5,1,3,0,0,-1,155.40,513 > 2013-06-02 03:05:22.924902 -0400 info main: #102 C EV915 rx msg D > 124,8,4,47,48,38,130,143065,0,2491,52,2,120,117,13.0,33,13.1,0 > 2013-06-02 03:08:22.920905 -0400 info main: #102 C EV915 rx msg S > 73,K,221,10,charging,range,288,245,10,40,100,2,5,1,3,0,0,-1,155.40,518 > 2013-06-02 03:08:22.922656 -0400 info main: #102 C EV915 rx msg D > 124,8,4,47,47,38,130,143065,0,2672,53,2,120,116,13.0,33,13.1,0 > 2013-06-02 03:18:50.728261 -0400 info main: #102 C EV915 rx msg S > 74,K,221,10,charging,range,290,245,10,50,100,2,5,1,3,0,0,-1,155.40,417 > 2013-06-02 03:18:50.730062 -0400 info main: #102 C EV915 rx msg D > 124,8,4,47,46,38,130,143065,0,3267,55,2,120,112,13.1,33,13.1,0 > 2013-06-02 03:28:19.623012 -0400 info main: #102 C EV915 rx msg S > 74,K,221,10,charging,range,291,246,10,60,100,2,5,1,3,0,0,-1,155.40,423 > 2013-06-02 03:28:19.628428 -0400 info main: #102 C EV915 rx msg D > 124,8,4,47,45,38,130,143065,0,3874,57,2,120,120,13.0,33,13.1,0 > 2013-06-02 03:38:19.014530 -0400 info main: #102 C EV915 rx msg S > 74,K,219,10,charging,range,291,248,10,70,100,3,5,1,3,0,0,-1,155.40,418 > 2013-06-02 03:38:19.016185 -0400 info main: #102 C EV915 rx msg D > 124,8,4,47,44,38,130,143065,0,4467,57,2,120,116,13.0,33,13.1,0 > 2013-06-02 03:48:16.329201 -0400 info main: #102 C EV915 rx msg S > 75,K,220,10,charging,range,294,250,10,80,100,3,5,1,3,0,0,-1,155.40,429 > 2013-06-02 03:48:16.330915 -0400 info main: #102 C EV915 rx msg D > 124,8,4,46,43,38,130,143065,0,5069,58,2,120,120,13.0,33,13.1,0 > 2013-06-02 03:58:16.439588 -0400 info main: #102 C EV915 rx msg S > 75,K,221,10,charging,range,294,250,10,90,100,4,5,1,3,0,0,-1,155.40,421 > 2013-06-02 03:58:16.441272 -0400 info main: #102 C EV915 rx msg D > 124,8,4,46,42,39,130,143065,0,5666,59,2,120,118,13.1,33,13.1,0 > 2013-06-02 04:08:13.068713 -0400 info main: #102 C EV915 rx msg S > 75,K,219,10,charging,range,296,251,10,100,100,4,5,1,3,0,0,-1,155.40,400 > 2013-06-02 04:08:13.070848 -0400 info main: #102 C EV915 rx msg D > 124,8,4,46,42,39,130,143065,0,6262,58,2,120,116,13.1,33,13.1,0 > 2013-06-02 04:18:11.402837 -0400 info main: #102 C EV915 rx msg S > 76,K,221,10,charging,range,298,253,10,110,100,4,5,1,3,0,0,-1,155.40,397 > 2013-06-02 04:18:11.404683 -0400 info main: #102 C EV915 rx msg D > 124,8,4,46,42,39,130,143065,0,6859,56,2,120,115,13.1,33,13.1,0 > > Decoding it, at 02:26 the PEM was at 44C, motor at 74C, and ESS at 39C. > Ambient (garage open on 1 side) was 38C. > > I left it for 8 minutes, after which time the PEM was at 48C, motor at 63C > and ESS at 40C. Ambient was 39C. > > I tried increasing current to 13A (again 220V, range mode), and left it > for a while. > > After 21 minutes, PEM was 48C, motor was 51C, ESS was 37C and ambient was > 47C. That is a total of 29 minutes so far, and I've managed to cool the ESS > 39C->37C, but heat up my garage 38C->47C. > > I restarted the range mode charge at 10A and this time left it for about > an hour. After that, PEM was 46C, motor 42C, ESS 39C, and my garage a > blistering 59C. > > This pretty much recreates my experiments from last summer. After more > than an hour, the ESS temperature was unchanged, but I had managed to heat > up my garage from 38C to 59C. Not sure if the term 'cool down' is > appropriate for this :-( > > Does any of you do cool down regularly (manually, or with Tattler)? If you > do, what settings do you use (voltage, current, duration) and what sort of > temperature drop on the ESS do you see? Last year, it was suggested I try > at a higher current, but that seems to defeat the purpose. Any suggestions? > > Regards, Mark. >

1 0

Re: [Ovmsdev] Advanced Charge Control (ACC)
by Bennett Leeds 02 Jun '13

02 Jun '13

This is really exciting. I would request that the Charge Timer should be based on Time Of Use periods, in order to automatically have the lowest charging costs while still having a full vehicle when you need it. Here in the states, many EV owners are on time of use meters. The cheapest period times very not only by day of the week, but also by season. I'd like to be able "teach" the car what the TOU periods are, tell it what time I leave each morning, and then have the car figure out the cheapest way to get me a full charge by the time I need it given the upcoming TOU periods between plug-in and when I need to leave. The TOU periods could be specified in 3 levels per weekday and 3 levels per weekend. With 2 seasons, that would be 12 fields to be entered. Time Needed could be specified per weekday and per weekend - so 14 time fields total for this to work. The logic is pretty straightforward. When the car is off and plugged in, look to see when the full charge is needed by. Either know the amperage available, or use the cooldown to get a pilot signal. Obey any lower current limits set by owners (which might be done due to old breakers, etc.). Then figure out if the cheapest time period is long enough to fully charge the car. If not, then do just enough charging in the second cheapest time period to result is a full charge, and if that won't be enough, then do just enough charging in the most expensive time period to result in a full charge after the upcoming second cheapest and most cheapest periods. I'd be happy to be a tester for whatever you come up with. thanks - Bennett On Sat, Jun 1, 2013 at 9:00 PM, <ovmsdev-request(a)lists.teslaclub.hk> wrote: > 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: Advanced Charge Control (ACC) (Tom Saxton) > 2. Re: Advanced Charge Control (ACC) (Mark Webb-Johnson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 01 Jun 2013 12:02:41 -0700 > From: Tom Saxton <tom(a)idleloop.com> > Subject: Re: [Ovmsdev] Advanced Charge Control (ACC) > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > Message-ID: <CDCF9361.804A3%tom(a)idleloop.com> > Content-Type: text/plain; charset="US-ASCII" > > Mark, > > This all sounds great. It covers everything I want, and more. Personally, I > think three zones is plenty if you want to save some parameter space. > > Tom > > on 5/31/13 6:56 AM, Mark Webb-Johnson wrote: > > > I've spent some time planning this, and now have the time to try to get > it > > done. The observant will have noticed a new branch ACC just appeared in > the > > github repository. > > > > This is primarily for Tesla Roadster owners, but once we work out how to > do > > charge control in other cars, it will have use for them. > > > > The premise of what I'm thinking is a replacement for the limited charge > > control in the car, to make an Advanced Charge Control: > > > > We have the concept of a 'charge location'. This is an area (square, > because > > it is easiest) around a GPS location. An area of 200m x 200m, centred on > the > > charge location, should be sufficient for gps inaccuracies. Up to 5 such > > charge locations can be defined (I'm thinking home, work, and one other). > > Once the car enters a charge location, an action can be triggered. At the > > moment, I'm only thinking of automatic home link activation, but others > are > > possible. > > When a car is turned off, while in a charge location, acc is enabled and > > current charge settings are saved. > > When a car is turned on, while in a charge location, acc is disabled and > > previous charge settings are restored. > > Features that acc should support include: > > Homelink activation. > > Cooldown (cool the car using a sequence of low amperage range mode > charges) - > > this would need a minimum temperature (don't cool down unless ESS > temperature > > is above this), a desired temperature (cool down until the ESS reaches > this > > temperature),and a time limit (stop cooling down if we've been trying > for too > > long). > > Charge mode (standard, storage, range, performance). > > Charge current limit. > > Various charge types, including: > > Charge on plug-in > > Start charge at specific time > > Complete charge by specific time > > Desired charge limit (SOC%, ideal miles/kilometers, or full) > > In addition to the charge locations, acc should be able to be turned on, > > one-off, for the current location. This should be done after the car is > turned > > off, before plugging in. It will be effective until the car is turned on > > again. > > It should also be possible to use this one-off acc to override the charge > > control for the current location. This will be effective until the car is > > turned on again. > > Control, and status, is possible by SMS commands. > > Control is also possible by a new tab added to the apps. I'm going to do > > iPhone first, with the existing charge control moved to a new "Charge" > tab. > > > > I'm not sure how to do the 'specific time'. This could be > > simple-to-ludicrously-complex. My inclination is to just put a > day-of-week > > filter on each charge location - with acc only being enabled if the day > > matches. More than one location could be created for each physical gps > > location, with different day matches, to control how that would behave. > > > > Changes to be made include: > > > > Move the roadster digital speedo experimental feature to a fully > supported > > features, and give it a permanent feature storage number. > > Assign five new permanent parameters, one each for five charge locations > > (home, work, other, or whatever they want to be known as - we just call > them > > #1, #2, #3, #4 and #5). > > The parameter storage for these new locations includes the charging > > preferences for each location. > > We would also need a parameter for time zone. > > Add a new module called "acc". > > If "acc" detects we are at a known charge location, it will take over the > > charge control from the car. > > The "acc" will also support commands for the current location, and will > be > > able to take over charge control from now until the car is next driven. > > > > Please let me have your comments / suggestions. I'll handle the coding, > but > > I'll need lots of help testing. > > > > Regards, Mark. > > > > _______________________________________________ > > OvmsDev mailing list > > OvmsDev(a)lists.teslaclub.hk > > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > > > > ------------------------------ > > Message: 2 > Date: Sun, 2 Jun 2013 09:29:37 +0800 > From: Mark Webb-Johnson <mark(a)webb-johnson.net> > Subject: Re: [Ovmsdev] Advanced Charge Control (ACC) > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > Message-ID: <AF3A64D7-E806-4CF3-94A8-360D170626C4(a)webb-johnson.net> > Content-Type: text/plain; charset=us-ascii > > Tom, > > My original design was 3 (home, work, other). I increased to 5 to allow > for different schedules weekday / weekend, etc. > > Lets see how it works out. More would be good. > > Regards, Mark > > On 2 Jun, 2013, at 3:02 AM, Tom Saxton <tom(a)idleloop.com> wrote: > > > Mark, > > > > This all sounds great. It covers everything I want, and more. > Personally, I > > think three zones is plenty if you want to save some parameter space. > > > > Tom > > > > on 5/31/13 6:56 AM, Mark Webb-Johnson wrote: > > > >> I've spent some time planning this, and now have the time to try to get > it > >> done. The observant will have noticed a new branch ACC just appeared in > the > >> github repository. > >> > >> This is primarily for Tesla Roadster owners, but once we work out how > to do > >> charge control in other cars, it will have use for them. > >> > >> The premise of what I'm thinking is a replacement for the limited charge > >> control in the car, to make an Advanced Charge Control: > >> > >> We have the concept of a 'charge location'. This is an area (square, > because > >> it is easiest) around a GPS location. An area of 200m x 200m, centred > on the > >> charge location, should be sufficient for gps inaccuracies. Up to 5 such > >> charge locations can be defined (I'm thinking home, work, and one > other). > >> Once the car enters a charge location, an action can be triggered. At > the > >> moment, I'm only thinking of automatic home link activation, but others > are > >> possible. > >> When a car is turned off, while in a charge location, acc is enabled and > >> current charge settings are saved. > >> When a car is turned on, while in a charge location, acc is disabled and > >> previous charge settings are restored. > >> Features that acc should support include: > >> Homelink activation. > >> Cooldown (cool the car using a sequence of low amperage range mode > charges) - > >> this would need a minimum temperature (don't cool down unless ESS > temperature > >> is above this), a desired temperature (cool down until the ESS reaches > this > >> temperature),and a time limit (stop cooling down if we've been trying > for too > >> long). > >> Charge mode (standard, storage, range, performance). > >> Charge current limit. > >> Various charge types, including: > >> Charge on plug-in > >> Start charge at specific time > >> Complete charge by specific time > >> Desired charge limit (SOC%, ideal miles/kilometers, or full) > >> In addition to the charge locations, acc should be able to be turned on, > >> one-off, for the current location. This should be done after the car is > turned > >> off, before plugging in. It will be effective until the car is turned on > >> again. > >> It should also be possible to use this one-off acc to override the > charge > >> control for the current location. This will be effective until the car > is > >> turned on again. > >> Control, and status, is possible by SMS commands. > >> Control is also possible by a new tab added to the apps. I'm going to do > >> iPhone first, with the existing charge control moved to a new "Charge" > tab. > >> > >> I'm not sure how to do the 'specific time'. This could be > >> simple-to-ludicrously-complex. My inclination is to just put a > day-of-week > >> filter on each charge location - with acc only being enabled if the day > >> matches. More than one location could be created for each physical gps > >> location, with different day matches, to control how that would behave. > >> > >> Changes to be made include: > >> > >> Move the roadster digital speedo experimental feature to a fully > supported > >> features, and give it a permanent feature storage number. > >> Assign five new permanent parameters, one each for five charge locations > >> (home, work, other, or whatever they want to be known as - we just call > them > >> #1, #2, #3, #4 and #5). > >> The parameter storage for these new locations includes the charging > >> preferences for each location. > >> We would also need a parameter for time zone. > >> Add a new module called "acc". > >> If "acc" detects we are at a known charge location, it will take over > the > >> charge control from the car. > >> The "acc" will also support commands for the current location, and will > be > >> able to take over charge control from now until the car is next driven. > >> > >> Please let me have your comments / suggestions. I'll handle the coding, > but > >> I'll need lots of help testing. > >> > >> Regards, Mark. > >> > >> _______________________________________________ > >> 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 > > > ------------------------------ > > _______________________________________________ > OvmsDev mailing list > OvmsDev(a)lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > > End of OvmsDev Digest, Vol 17, Issue 5 > ************************************** >

2 1

Advanced Charge Control (ACC)
by Mark Webb-Johnson 02 Jun '13

02 Jun '13

I've spent some time planning this, and now have the time to try to get it done. The observant will have noticed a new branch ACC just appeared in the github repository. This is primarily for Tesla Roadster owners, but once we work out how to do charge control in other cars, it will have use for them. The premise of what I'm thinking is a replacement for the limited charge control in the car, to make an Advanced Charge Control: We have the concept of a 'charge location'. This is an area (square, because it is easiest) around a GPS location. An area of 200m x 200m, centred on the charge location, should be sufficient for gps inaccuracies. Up to 5 such charge locations can be defined (I'm thinking home, work, and one other). Once the car enters a charge location, an action can be triggered. At the moment, I'm only thinking of automatic home link activation, but others are possible. When a car is turned off, while in a charge location, acc is enabled and current charge settings are saved. When a car is turned on, while in a charge location, acc is disabled and previous charge settings are restored. Features that acc should support include: Homelink activation. Cooldown (cool the car using a sequence of low amperage range mode charges) - this would need a minimum temperature (don't cool down unless ESS temperature is above this), a desired temperature (cool down until the ESS reaches this temperature),and a time limit (stop cooling down if we've been trying for too long). Charge mode (standard, storage, range, performance). Charge current limit. Various charge types, including: Charge on plug-in Start charge at specific time Complete charge by specific time Desired charge limit (SOC%, ideal miles/kilometers, or full) In addition to the charge locations, acc should be able to be turned on, one-off, for the current location. This should be done after the car is turned off, before plugging in. It will be effective until the car is turned on again. It should also be possible to use this one-off acc to override the charge control for the current location. This will be effective until the car is turned on again. Control, and status, is possible by SMS commands. Control is also possible by a new tab added to the apps. I'm going to do iPhone first, with the existing charge control moved to a new "Charge" tab. I'm not sure how to do the 'specific time'. This could be simple-to-ludicrously-complex. My inclination is to just put a day-of-week filter on each charge location - with acc only being enabled if the day matches. More than one location could be created for each physical gps location, with different day matches, to control how that would behave. Changes to be made include: Move the roadster digital speedo experimental feature to a fully supported features, and give it a permanent feature storage number. Assign five new permanent parameters, one each for five charge locations (home, work, other, or whatever they want to be known as - we just call them #1, #2, #3, #4 and #5). The parameter storage for these new locations includes the charging preferences for each location. We would also need a parameter for time zone. Add a new module called "acc". If "acc" detects we are at a known charge location, it will take over the charge control from the car. The "acc" will also support commands for the current location, and will be able to take over charge control from now until the car is next driven. Please let me have your comments / suggestions. I'll handle the coding, but I'll need lots of help testing. Regards, Mark.

6 12

Desktop Apps?
by Nikki Gordon-Bloomfield 24 May '13

24 May '13

Hi Folks, Just out of curiosity, has anyone built an Apple or Windows client for OVMS yet? I'm at my desk most of the day, and having something sitting in the background would be truly awesome. Nikki Gordon-Bloomfield http://about.me/aminorjourney/bio email: nikki(a)littleCollie.com tel: +44 7901 553308

2 1

Twizy firmware image V2.3.6 / 2.6.5
by Michael Balzer 15 May '13

15 May '13

For those avoiding self-compiling (Nikki et al), here's the current firmware image with Twizy extensions. It makes GPS logging (RT-GPS-Log) at 5 second intervals stable. To get max GPS precision be sure to activate only the GPS logging (w/o location streaming) by setting feature #8 to 2. The ZIP also contains a guide and spreadsheet template for creating energy use heatmap-style GPS tracks using gpsvisualizer.com -- the guide text is in german now, I can make an english version and add it to the repository if there is demand. Here's an example result: Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

5 20

Spewing Vehicle Alerts
by Tom Saxton 15 May '13

15 May '13

I took our Roadster in for service yesterday, and this morning I noticed that it's sending the same vehicle alert repeatedly at an alarming rate, like once a second. Vehicle Alert Code: TR1N/29 (00000000) I tried calling the store to ask them to unplug the OVMS, but they weren't answering the phone (it was before they were officially open). I then tried to turn off GPRS to get it to stop spewing. I sent a PARAMS command to only allow SMS, but that didn't work. Thinking that it might need to reboot to get the command to stick, I sent a RESET command, which did the trick. I see there's code to call vehicle_initialise() after handling a PARAMS command, so I'm a little surprised the RESET was needed. Then I remembered that version 2.3.2 mentioned a way to turn off vehicle alerts. From the release notes: ## Add facility to suppress vehicle alerts via carbits feature +16 But Mark's email from April 16th says: > Yes, car bits feature 14, add 8 to the value (bit #3) to > suppress vehicle alerts via push notification. >From looking at the code, it looks like adding 8 (setting the 8 bit in binary) to the value for Feature 14 will turn off sending the vehicles alerts to the server. I have Feature 14 set to 1 to indicate that ours is a 2008 Roadster, so I added 1+8=9 and sent "FEATURE 14 9", then re-enabled SMS,IP, and RESET. That restored network comms so the OVMS app is working again, and I'm not seeing the alerts any more. Finally, I notice there's code to prevent OVMS from sending the same alert more than once per minute, but if another code comes in, or the alert gets cancelled, the 60-second timer gets cleared. I wonder if that code should be more aggressive about limiting alert frequency. I suspect what's happening with the Roadster is that it's repeatedly firing and then dismissing an alert message (presumably related to the service they are doing), which completely circumvents the timer, resulting in a ridiculous number of alert messages. I suspect this was happening all night, so my next phone bill may be interesting at $2/MB. Tom

2 1

Look what they found...
by Mark Webb-Johnson 14 May '13

14 May '13

Look what they found behind the cubby under the touchscreen of the Tesla Model S... Reminds me of the Tesla Roadster: Is it wrong of me to want to find a MS, pull down the cubby and plug in (my CAN analyser)? Regards, Mark.

3 7

Current TWiZY Firmware.
by Nikki Gordon-Bloomfield 14 May '13

14 May '13

Hey Guys, Noticed a few strange bits of behaviour lately with the latest Twizy firmware. Michael, I'm getting really long waits between the module contacting the server -- and sometimes it's reporting it can't see the server, despite being able to connect to the GPRS modem. Also, I'm finding I have to reboot the OVMS module every now and then because it becomes unresponsive. Haven't looked at the logs yet though as I'm off to Sweden today. Any thoughts? Nikki.

1 0

OVMS Android localization
by Denis KRAUTH 13 May '13

13 May '13

Hi, I offered my help a few months ago to translate the app into French. Has the app now reached a state where localization into other languages can be considered? Denis. Envoyé depuis mon mobile. -------- Message d'origine -------- De : Mark Webb-Johnson <mark(a)webb-johnson.net> Date : A : OVMS Developers <OvmsDev(a)lists.teslaclub.hk> Objet : [Ovmsdev] OVMS Android goes live @OpenVehicles: OVMS Android App back in Google Play - out of beta and supporting hi-res modern phones and latest EVs. https://t.co/7K8m0IeB27 _______________________________________________ OvmsDev mailing list OvmsDev(a)lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

8 27