Hi Guys, attached you find a picture which could be used to integrate the Tazzari Zero into the range of cars in the App. It isn't anywhere near high-res but a decent size which is usable for now. Regards, Patrick
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@littleCollie.com tel: +44 7901 553308
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@littleCollie.com tel: +44 7901 553308
_______________________________________________ OvmsDev mailing list OvmsDev@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
...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@littleCollie.com tel: +44 7901 553308
_______________________________________________ OvmsDev mailing list OvmsDev@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@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
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@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@littleCollie.com tel: +44 7901 553308
_______________________________________________ OvmsDev mailing list OvmsDev@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@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@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
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@expeedo.de <mailto:dexter@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@littleCollie.com tel: +44 7901 553308
_______________________________________________ OvmsDev mailing list OvmsDev@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@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@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@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
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@expeedo.de <mailto:dexter@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@littleCollie.com tel: +44 7901 553308
_______________________________________________ OvmsDev mailing list OvmsDev@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@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@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@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@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
Michael. That's great! Thanks. I have to drive the Twizy about 50 km today, so I'll try and get this new software installed ASAP :) Nikki. On 8 Apr 2013, at 07:06, Michael Balzer <dexter@expeedo.de> wrote:
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@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@littleCollie.com tel: +44 7901 553308
_______________________________________________ OvmsDev mailing list OvmsDev@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@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@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@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@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 <OVMS.X.production.hex><dexter.vcf>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Michael, Just confirmed that the OVMS system died earlier on: It stopped reporting from 9:35 through until 13:52, when I rebooted it. I think it's died again, so will try and get crash logs :) Nikki. On 8 Apr 2013, at 07:18, Nikki Gordon-Bloomfield <nikki@littlecollie.com> wrote:
Michael. That's great! Thanks.
I have to drive the Twizy about 50 km today, so I'll try and get this new software installed ASAP :)
Nikki.
On 8 Apr 2013, at 07:06, Michael Balzer <dexter@expeedo.de> wrote:
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@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@littleCollie.com > tel: +44 7901 553308 > > > > _______________________________________________ > OvmsDev mailing list > OvmsDev@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@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@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@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@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 <OVMS.X.production.hex><dexter.vcf>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
I think I just found another bug... Look at the mileage estimate! Also not sure I didn't have a system crash. Need to ping the server to make sure... Nikki Sent from my iPhone On 8 Apr 2013, at 07:06, Michael Balzer <dexter@expeedo.de> wrote:
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@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@littleCollie.com tel: +44 7901 553308
_______________________________________________ OvmsDev mailing list OvmsDev@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@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@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@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@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 <OVMS.X.production.hex> <dexter.vcf> _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Michael, Here's my debug log. Any use? Nikki.
Nikki, that rather looks like some problem with your OBD2 connector (12V power supply), as the logs show only first boots instead of resets/crashes. Can you check that? I have no problem running the last version I sent. Thanks, Michael Am 08.04.2013 16:32, schrieb Nikki Gordon-Bloomfield:
Michael,
Here's my debug log. Any use?
Nikki.
_______________________________________________ OvmsDev mailing list OvmsDev@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
...or an antenna / GSM problem, logs are sent on GSM connect also. Am 08.04.2013 17:02, schrieb Michael Balzer:
Nikki,
that rather looks like some problem with your OBD2 connector (12V power supply), as the logs show only first boots instead of resets/crashes.
Can you check that?
I have no problem running the last version I sent.
Thanks, Michael
Am 08.04.2013 16:32, schrieb Nikki Gordon-Bloomfield:
Michael,
Here's my debug log. Any use?
Nikki.
_______________________________________________ OvmsDev mailing list OvmsDev@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@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
Ok! I'll check when I get home! Sent from my iPhone On 8 Apr 2013, at 16:09, Michael Balzer <dexter@expeedo.de> wrote:
...or an antenna / GSM problem, logs are sent on GSM connect also.
Am 08.04.2013 17:02, schrieb Michael Balzer:
Nikki,
that rather looks like some problem with your OBD2 connector (12V power supply), as the logs show only first boots instead of resets/crashes.
Can you check that?
I have no problem running the last version I sent.
Thanks, Michael
Am 08.04.2013 16:32, schrieb Nikki Gordon-Bloomfield:
Michael,
Here's my debug log. Any use?
Nikki.
_______________________________________________ OvmsDev mailing list OvmsDev@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@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@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Hi Michael, Confirmed CAN bus happily connected (ODB2), and that modules are firmly affixed with good signal. Attached is the BattPack.CSV file, along with the other four logs. . Notice that there's a big gap where it stopped reporting and then I reconnected it (That's what the reboots are in the logs: when I reconnected the system after firmware installation and when I reconnected to reboot it) Given that it completely died for the best part of my trip, I'm tempted to suggest that it was a firmware bug. In addition, my Twizy now reports a range in the hundreds of miles! Congratulations, you broke the laws of physics (Or we've shifted to the right one too many!) Nikki. On 8 Apr 2013, at 16:14, Nikki Gordon-Bloomfield <nikki@littlecollie.com> wrote:
Ok! I'll check when I get home!
Sent from my iPhone
On 8 Apr 2013, at 16:09, Michael Balzer <dexter@expeedo.de> wrote:
...or an antenna / GSM problem, logs are sent on GSM connect also.
Am 08.04.2013 17:02, schrieb Michael Balzer:
Nikki,
that rather looks like some problem with your OBD2 connector (12V power supply), as the logs show only first boots instead of resets/crashes.
Can you check that?
I have no problem running the last version I sent.
Thanks, Michael
Am 08.04.2013 16:32, schrieb Nikki Gordon-Bloomfield:
Michael,
Here's my debug log. Any use?
Nikki.
_______________________________________________ OvmsDev mailing list OvmsDev@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@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@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Nikki, that's really strange as I haven't touched the range calculation at all. Can you please check your feature and parameter settings, especially max ideal range? I sometimes (seldom) lose some of the configuration on flashing. Also please try to force an SRAM reinit by switching the vehicle type to some other and then back to "RT". Do the problems occur only in GPS streaming mode or also with normal update frequency? Thanks, Michael Am 08.04.2013 18:06, schrieb Nikki Gordon-Bloomfield:
Hi Michael,
Confirmed CAN bus happily connected (ODB2), and that modules are firmly affixed with good signal.
Attached is the BattPack.CSV file, along with the other four logs. . Notice that there's a big gap where it stopped reporting and then I reconnected it (That's what the reboots are in the logs: when I reconnected the system after firmware installation and when I reconnected to reboot it)
Given that it completely died for the best part of my trip, I'm tempted to suggest that it was a firmware bug.
In addition, my Twizy now reports a range in the hundreds of miles! Congratulations, you broke the laws of physics (Or we've shifted to the right one too many!)
Nikki.
On 8 Apr 2013, at 16:14, Nikki Gordon-Bloomfield <nikki@littlecollie.com <mailto:nikki@littlecollie.com>> wrote:
Ok! I'll check when I get home!
Sent from my iPhone
On 8 Apr 2013, at 16:09, Michael Balzer <dexter@expeedo.de <mailto:dexter@expeedo.de>> wrote:
...or an antenna / GSM problem, logs are sent on GSM connect also.
Am 08.04.2013 17:02, schrieb Michael Balzer:
Nikki,
that rather looks like some problem with your OBD2 connector (12V power supply), as the logs show only first boots instead of resets/crashes.
Can you check that?
I have no problem running the last version I sent.
Thanks, Michael
Am 08.04.2013 16:32, schrieb Nikki Gordon-Bloomfield:
Michael,
Here's my debug log. Any use?
Nikki.
_______________________________________________ OvmsDev mailing list OvmsDev@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@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@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@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
Nikki, I did some more stress tests and could trigger two errors with streaming enabled. I checked the code again and maybe found a bug that could result in connection drops in case of an exact time synchronisation between framework and Twizy notifications (the framework could send notifications without checking for pending sends). I also raised the watchdog timeout to 16 seconds because there are so many delays in the net code that we might pass the 8 seconds under normal conditions now. Regards, Michael Am 08.04.2013 19:27, schrieb Michael Balzer:
Nikki,
that's really strange as I haven't touched the range calculation at all.
Can you please check your feature and parameter settings, especially max ideal range? I sometimes (seldom) lose some of the configuration on flashing.
Also please try to force an SRAM reinit by switching the vehicle type to some other and then back to "RT".
Do the problems occur only in GPS streaming mode or also with normal update frequency?
Thanks, Michael
Am 08.04.2013 18:06, schrieb Nikki Gordon-Bloomfield:
Hi Michael,
Confirmed CAN bus happily connected (ODB2), and that modules are firmly affixed with good signal.
Attached is the BattPack.CSV file, along with the other four logs. . Notice that there's a big gap where it stopped reporting and then I reconnected it (That's what the reboots are in the logs: when I reconnected the system after firmware installation and when I reconnected to reboot it)
Given that it completely died for the best part of my trip, I'm tempted to suggest that it was a firmware bug.
In addition, my Twizy now reports a range in the hundreds of miles! Congratulations, you broke the laws of physics (Or we've shifted to the right one too many!)
Nikki.
On 8 Apr 2013, at 16:14, Nikki Gordon-Bloomfield <nikki@littlecollie.com <mailto:nikki@littlecollie.com>> wrote:
Ok! I'll check when I get home!
Sent from my iPhone
On 8 Apr 2013, at 16:09, Michael Balzer <dexter@expeedo.de <mailto:dexter@expeedo.de>> wrote:
...or an antenna / GSM problem, logs are sent on GSM connect also.
Am 08.04.2013 17:02, schrieb Michael Balzer:
Nikki,
that rather looks like some problem with your OBD2 connector (12V power supply), as the logs show only first boots instead of resets/crashes.
Can you check that?
I have no problem running the last version I sent.
Thanks, Michael
Am 08.04.2013 16:32, schrieb Nikki Gordon-Bloomfield:
Michael,
Here's my debug log. Any use?
Nikki.
_______________________________________________ OvmsDev mailing list OvmsDev@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@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@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@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@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
Patrick, Here are some notes from before:
For new vehicles, to get the images into the apps, we need images in a similar size, orientation and layout.
The images are:
1] The car front-angle view. 654x302 pixels, high quality PNG format. One for each colour to be supported. The background must be transparent.
If you have problems with aspect ratio, try to keep the width the same, and leave space on the top/bottom.
2] The car xray view, 304x606 pixels, high quality PNG format. One for each colour to be supported. The background must be transparent.
You should try to keep the wheels in approximately the same position as the attached picture (in particular if your vehicle supports TPMS). If you have problems with aspect ratio, try to keep the height the same, and leave space on the sides.
3] Car map images. 96x96 pixels, medium quality PNG format. One for each colour to be supported. Car must be pointing upwards (north). The background must be transparent.
If you have problems with aspect ratio, try to keep the height the same, and leave space on the sides.
4] Name of vehicle type
We also need the official name and model of the vehicle type (eg. Tesla Roadster, Nissan Leaf, Volt Ampera, etc).
5] File naming
The files should be named as follows:
car_<type>_<colour>.png (for the car front-angle view) ol_car_<type>_<colour>.png (for the car X-ray view) map_car_<type>_<colour>.png (for the car map image)
The <type> is the vehicle type (e.g.; roadster, ampere, twizy, etc). The <colour> is the official colour name (e.g.; thundergray, crystalred, lithiumwhite, electricblue, etc).
Once we have artwork in the correct format, putting it in the apps is trivial. The primary problem is finding artwork of appropriate quality and style, with a transparent background.
I'll have a look to see what is available for Tazzari. Regards, Mark. On 6 Apr, 2013, at 3:00 AM, Patrick Kapsch wrote:
Hi Guys, attached you find a picture which could be used to integrate the Tazzari Zero into the range of cars in the App. It isn't anywhere near high-res but a decent size which is usable for now.
Regards, Patrick
<IMG_2286.PNG><tazzari-zero001_enl.jpg>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
participants (4)
-
Mark Webb-Johnson -
Michael Balzer -
Nikki Gordon-Bloomfield -
Patrick Kapsch