Nikki, that's no new error, it's due to the Twizy measuring metric vs. the OVMS car model needing miles. The kilometer to miles conversion is optimized to avoid floating point math (the OVMS has no FPU), and the conversion is already fine tuned to produce the least mean error in the range 0..100 km. Conversion errors get bigger the bigger the numbers get, and there's not much we can do about this (except enabling metric values in the car model, which is on our list). Here's your current error explained: MP-0 c200,0,0040,0000,0000,4,0,0,169252,8430,8430,8774,65,65,41,37,0 169252 is the Twizy internal odometer value meaning 1692.52 km. See utils.h for the conversion: // 1 mile = 1.609344 kilometers // smalles error approximation: mi = (km * 10 - 5) / 16 + 1 So the integer conversion for 1692 results in 1058 while the real value is 1051. That's your 7 mile offset. Regards, Michael Am 12.05.2013 21:49, schrieb Nikki Gordon-Bloomfield:
I forgot to mention...
My Twizy is about 7 miles less on the odometer than the creek OVMS build says.
Sent from my iPhone
On 12 May 2013, at 17:40, Michael Balzer <dexter@expeedo.de <mailto:dexter@expeedo.de>> wrote:
Nikki,
I haven't had that special case, but it sounds like the RAM corruption effect. I think you need to do a hard reboot, i.e. switch the module off.
Please read out the debug info (cmd 200) and send me all history data if possible, maybe I can find something in there.
Thanks, Michael
Am 12.05.2013 13:26, schrieb Nikki Gordon-Bloomfield:
HI folks,
Just to let you know that my Twizy is still reporting 0 percent and 0 miles, even though it is now fully charged! (At least, OVMS is!) I've rebooted it a few times, and geolocation works fine.
Nikki.
On 12 May 2013, at 12:09, Michael Jochum <mikeljo@mac.com <mailto:mikeljo@mac.com>> wrote:
Hi,
i think yes. We have the Voltage(s) and Amper(s) per Motor and Battery. But currently not used in OVMS. So we can calc the Power like DashDaq.
I think these are the IDs:
7EC 432D High Voltage Battery Voltage 7EC 4356 High Voltage Battery Current
7E9432D High Voltage Battery Voltage 7E94356 High Voltage Battery Current
7E92883 Motor A DC Current 7E92884 Motor B DC Current 7E92885 Motor A DC Voltage 7E92886 Motor B DC Voltage
7E8000D Vehicle Speed Km/Hr
You can see the Data for the Battery are here twice. For Filter reasons i think it is better to use 7E9 instead 7EC.
Bye Michael J.
Am 11.05.2013 um 21:05 schrieb Denis KRAUTH <denis.krauth@wanadoo.fr <mailto:denis.krauth@wanadoo.fr>>:
Michael (J), Is this feasible for our Amperas ? Denis (aka Kratus). *De :*ovmsdev-bounces@lists.teslaclub.hk <mailto:ovmsdev-bounces@lists.teslaclub.hk>[mailto:ovmsdev-bounces@lists.teslaclub.hk <mailto:bounces@lists.teslaclub.hk>]*De la part de*Michael Balzer *Envoyé :*samedi 11 mai 2013 16:52 *À :*ovmsdev@lists.teslaclub.hk <mailto:ovmsdev@lists.teslaclub.hk> *Objet :*Re: [Ovmsdev] Twizy firmware image V2.3.6 / 2.6.5
Denis,
thanks :-)
The GPS logging feature and energy usage stats are currently Twizy specific.
To move these into the framework, we need to make the energy usage variables part of the common car model. And of course we need to know how to get these values from other cars like Ampera...?
Regards, Michael
Am 11.05.2013 10:17, schrieb Denis KRAUTH:
Wow, great ! Can this be done on my Ampera too, or is it Twizy-specific ? Can FEATURE 8 2 also be applied on my 2.3.2 Ampera firmware? There is a Volt/Ampera ecodrive contest in a few days (June 1^st ) and this would be really great to track the data. I just read your german guide, and it seems really not difficult. Hut ab! Denis. *De :*ovmsdev-bounces@lists.teslaclub.hk <mailto:ovmsdev-bounces@lists.teslaclub.hk>[mailto:ovmsdev-bounces@lists.teslaclub.hk]*De la part de*Michael Balzer *Envoyé :*vendredi 10 mai 2013 20:26 *À :*'OVMS Developers' *Objet :*[Ovmsdev] Twizy firmware image V2.3.6 / 2.6.5 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 <http://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:
<image001.png>
Regards, Michael
--
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk <mailto: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 <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ 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 <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