[Ovmsdev] GPS Logs (TWIZY) -- Future Feature?

Michael Balzer dexter at expeedo.de
Mon Apr 8 14:06:25 HKT 2013


Nikki,

I think I found the bug, please use the attached new version instead.

I'll also test that one myself later on today.

Regards,
Michael

PS: your posts are great to read! I also like your idea for a permanent 
installation place of the OVMS, I still have mine in the glove box.


Am 07.04.2013 19:48, schrieb Michael Balzer:
> Nikki,
>
> I have added these fields to the RT-GPS-Log message:
>
> // current power (W)
> // power usage sum (Wh)
> // recuperation sum (Wh)
> // distance driven (m)
>
> Be aware that the "current power" is really the power use of the exact 
> moment the message is sent, no average. This reacts to any bump in the 
> road or wind gust. So the sums will normally be more useful, but will 
> need deriving the section differences in a post processing step.
>
> New firmware image attached. So if you activate GPS streaming you'll 
> get updates every 5 seconds, which should already give a very detailed 
> view of the power usage (if GPS position can be acquired fast and 
> precise enough).
>
> I had a strange effect (read: possible bug) on the first test run: 
> distance would start at 6546 meters (should be 0). That could have 
> been because I was very fast with flashing so maybe the SRAM init was 
> skipped... but maybe it's a real bug. If it's a bug it will also 
> affect the power usage statistics, resulting in too low Wh/km figures.
>
> Please tell me if you still see a similar fault if you wait 2-3 
> minutes from flashing to reinstalling.
>
> Thanks,
> Michael
>
>
> Am 07.04.2013 16:36, schrieb Mark Webb-Johnson:
>>
>> 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).
>>
>> It would not be hard to add it to the model and to the location 
>> streaming feature when an App is connected.
>>
>> Regards, Mark.
>>
>> On 6 Apr, 2013, at 10:39 PM, Michael Balzer <dexter at expeedo.de 
>> <mailto:dexter at expeedo.de>> wrote:
>>
>>> ...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.
>>>
>>> Regards,
>>> Michael
>>>
>>>
>>> Am 06.04.2013 16:29, schrieb Michael Balzer:
>>>> Nikki, Mark,
>>>>
>>>> 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.
>>>>
>>>> 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).
>>>>
>>>> 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.
>>>>
>>>> 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?
>>>>
>>>> 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?
>>>>
>>>> Regards,
>>>> Michael
>>>>
>>>>
>>>> Am 06.04.2013 15:39, schrieb Nikki Gordon-Bloomfield:
>>>>> Hi folks,
>>>>>
>>>>> 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.
>>>>>
>>>>> 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.
>>>>>
>>>>> Anyone else think it's a good idea?
>>>>>
>>>>> Nikki Gordon-Bloomfield
>>>>>
>>>>> http://about.me/aminorjourney/bio
>>>>> email: nikki at littleCollie.com
>>>>> tel: +44 7901 553308
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at 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 at 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
>>> <dexter.vcf>_______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk>
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>
>>
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at 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 at 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20130408/e85d4ef4/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OVMS.X.production.hex
Type: text/x-hex
Size: 243374 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20130408/e85d4ef4/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dexter.vcf
Type: text/x-vcard
Size: 206 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20130408/e85d4ef4/attachment-0002.vcf>


More information about the OvmsDev mailing list