<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div>Instantaneous power should be available in most cars. It is certainly there in the roadster (because we spoof it to show speed as a digital speedo).<div><br></div><div>It would not be hard to add it to the model and to the location streaming feature when an App is connected.</div><div><br></div><div>Regards, Mark.</div><div><br><div><div>On 6 Apr, 2013, at 10:39 PM, Michael Balzer <<a href="mailto:dexter@expeedo.de">dexter@expeedo.de</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
...btw, it would be quite easy to send power usage updates within
the streaming update mode, just adds some traffic. So you would get
5 second sections in GPS and power usage, easier to correlate. But
still the power usages would be far easier to process when being
included in the GPS messages.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 06.04.2013 16:29, schrieb Michael
Balzer:<br>
</div>
<blockquote cite="mid:5160314A.4080004@expeedo.de" type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
Nikki, Mark,<br>
<br>
I decided against adding the current power to the GPS log because
that's something not defined in the general virtual car model, all
other cars lack this feature, and I wanted to make the GPS log
function fit for inclusion in the framework first.<br>
<br>
I currently send the power usage log (RT-PWR-UsageStats) once per
minute. You can correlate that to the GPS log to get the power
usage of minute long sections, but that's a lot of manual work and
not very detailed (e.g. for hills).<br>
<br>
Btw: using the power collection feature, you can also measure
certain route parts: easiest way is to turn the Twizy on just
before driving the section, then turn the Twizy off and check the
power stats message. But a combined GPS track would of course be
far better and more accurate.<br>
<br>
Mark, you mentioned a "kWh used" value with the driving log
function, so I guess we can think about adding the power usage to
the standard car model?<br>
<br>
But I'm not sure yet if the way I currently collect power usages
is suitable and sufficient as a standard. As I wrote in the docs,
that's work in progress... any thoughts on this?<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 06.04.2013 15:39, schrieb Nikki
Gordon-Bloomfield:<br>
</div>
<blockquote cite="mid:B3F4A5F2-5369-4E65-B978-71DC42C5B9B8@littlecollie.com" type="cite">Hi folks,
<div><br>
</div>
<div>Just got the server.pl running and the client_app.pl
running on my Ubuntu box at home. And I've pulled down the GPS
Logs for the Twizy. </div>
<div><br>
</div>
<div>One thing that's missing, which I'd love to see in the
future, is an instantaneous power reading. This would enable
us to not only plot the course, but figure out where the most
demanding part of a trip is based on power drainage. </div>
<div><br>
</div>
<div>Anyone else think it's a good idea? </div>
<div><br>
</div>
<div apple-content-edited="true"> <span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Nikki Gordon-Bloomfield<br>
<br>
<a moz-do-not-send="true" href="http://about.me/aminorjourney/bio">http://about.me/aminorjourney/bio</a><br>
email: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:nikki@littleCollie.com">nikki@littleCollie.com</a><br>
tel: +44 7901 553308<br>
</span> </div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
</pre>
</div>
<span><dexter.vcf></span>_______________________________________________<br>OvmsDev mailing list<br><a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a><br>http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br></blockquote></div><br></div></body></html>