I think we are ready for a 3.2.000 OTA release to EAP. I’ve built this, and it is in the nightly build system ready to go. I’ve completed all the JavaScript tasks, including migrating all the existing extensions to modular object format. That is a breaking change (existing scripts will break), but easy to do now than later when more are using it. I really haven’t heard of anyone using javascript with the system at the moment. With 200 commits, the changelog is massive. The scripting system warrants a 3.2 release. Please have a try with this in your cars, and let me know of any issues. If nothing comes up in the next day, I’ll move it to EAP at the weekend. Thanks to everyone who contributed to this. The system functionality is really very impressive now, and only getting better as time goes by. Regards, Mark
Yep, definitely worth a major revision bump, and a huge thanks from me to everyone here as well. The scripting system before wasn't suited for much more than simple calculations, and editing scripts on the console wasn't likely to attract users as well. I think we'll see some cool applications evolve from this now. Maybe we should add a top level directory for scripting extensions? A number of users also jumped into web plugin development, that could also be worth a top level directory. If only as an incentive to publish their results. Btw, a user currently works on an ESP8266 based wifi console to display metrics and some simple battery powered wifi buttons to trigger commands: The community is growing. I've also got a feedback from an automotive engineer who was absolutely astonished discovering all the features and tools included. I think we need better communication on what the OVMS can already do now, not only for users but especially also for technical applications and fleet management. Regards, Michael Am 18.01.19 um 14:18 schrieb Mark Webb-Johnson:
I think we are ready for a 3.2.000 OTA release to EAP. I’ve built this, and it is in the nightly build system ready to go.
I’ve completed all the JavaScript tasks, including migrating all the existing extensions to modular object format. That is a breaking change (existing scripts will break), but easy to do now than later when more are using it. I really haven’t heard of anyone using javascript with the system at the moment.
With 200 commits, the changelog is massive. The scripting system warrants a 3.2 release.
Please have a try with this in your cars, and let me know of any issues. If nothing comes up in the next day, I’ll move it to EAP at the weekend.
Thanks to everyone who contributed to this. The system functionality is really very impressive now, and only getting better as time goes by.
Regards, Mark _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Hi Mark, How long before the release, I was hoping to push in the initial support for the smart ED into this if possible? Thanks Fran On Fri, 18 Jan 2019 at 15:36, Michael Balzer <dexter@expeedo.de> wrote:
Yep, definitely worth a major revision bump, and a huge thanks from me to everyone here as well.
The scripting system before wasn't suited for much more than simple calculations, and editing scripts on the console wasn't likely to attract users as well. I think we'll see some cool applications evolve from this now. Maybe we should add a top level directory for scripting extensions?
A number of users also jumped into web plugin development, that could also be worth a top level directory. If only as an incentive to publish their results.
Btw, a user currently works on an ESP8266 based wifi console to display metrics and some simple battery powered wifi buttons to trigger commands:
The community is growing. I've also got a feedback from an automotive engineer who was absolutely astonished discovering all the features and tools included.
I think we need better communication on what the OVMS can already do now, not only for users but especially also for technical applications and fleet management.
Regards, Michael
Am 18.01.19 um 14:18 schrieb Mark Webb-Johnson:
I think we are ready for a 3.2.000 OTA release to EAP. I’ve built this, and it is in the nightly build system ready to go.
I’ve completed all the JavaScript tasks, including migrating all the existing extensions to modular object format. That is a breaking change (existing scripts will break), but easy to do now than later when more are using it. I really haven’t heard of anyone using javascript with the system at the moment.
With 200 commits, the changelog is massive. The scripting system warrants a 3.2 release.
Please have a try with this in your cars, and let me know of any issues. If nothing comes up in the next day, I’ll move it to EAP at the weekend.
Thanks to everyone who contributed to this. The system functionality is really very impressive now, and only getting better as time goes by.
Regards, Mark _______________________________________________ OvmsDev mailing listOvmsDev@lists.openvehicles.comhttp://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
That is a new car module, so can go in whenever ready. When do you think you will be ready to commit code? Mark
On 18 Jan 2019, at 11:46 PM, Fran Terry <fajterry@gmail.com> wrote:
Hi Mark,
How long before the release, I was hoping to push in the initial support for the smart ED into this if possible?
Thanks
Fran
On Fri, 18 Jan 2019 at 15:36, Michael Balzer <dexter@expeedo.de> wrote: Yep, definitely worth a major revision bump, and a huge thanks from me to everyone here as well.
The scripting system before wasn't suited for much more than simple calculations, and editing scripts on the console wasn't likely to attract users as well. I think we'll see some cool applications evolve from this now. Maybe we should add a top level directory for scripting extensions?
A number of users also jumped into web plugin development, that could also be worth a top level directory. If only as an incentive to publish their results.
Btw, a user currently works on an ESP8266 based wifi console to display metrics and some simple battery powered wifi buttons to trigger commands:
<fikgienoeoefpmjb.jpeg>
The community is growing. I've also got a feedback from an automotive engineer who was absolutely astonished discovering all the features and tools included.
I think we need better communication on what the OVMS can already do now, not only for users but especially also for technical applications and fleet management.
Regards, Michael
Am 18.01.19 um 14:18 schrieb Mark Webb-Johnson: I think we are ready for a 3.2.000 OTA release to EAP. I’ve built this, and it is in the nightly build system ready to go.
I’ve completed all the JavaScript tasks, including migrating all the existing extensions to modular object format. That is a breaking change (existing scripts will break), but easy to do now than later when more are using it. I really haven’t heard of anyone using javascript with the system at the moment.
With 200 commits, the changelog is massive. The scripting system warrants a 3.2 release.
Please have a try with this in your cars, and let me know of any issues. If nothing comes up in the next day, I’ll move it to EAP at the weekend.
Thanks to everyone who contributed to this. The system functionality is really very impressive now, and only getting better as time goes by.
Regards, Mark _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Fran, are you aware Martin Graml has already added initial Smart ED support? https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/193 Regards, Michael Am 18.01.19 um 16:46 schrieb Fran Terry:
Hi Mark,
How long before the release, I was hoping to push in the initial support for the smart ED into this if possible?
Thanks
Fran
On Fri, 18 Jan 2019 at 15:36, Michael Balzer <dexter@expeedo.de <mailto:dexter@expeedo.de>> wrote:
Yep, definitely worth a major revision bump, and a huge thanks from me to everyone here as well.
The scripting system before wasn't suited for much more than simple calculations, and editing scripts on the console wasn't likely to attract users as well. I think we'll see some cool applications evolve from this now. Maybe we should add a top level directory for scripting extensions?
A number of users also jumped into web plugin development, that could also be worth a top level directory. If only as an incentive to publish their results.
Btw, a user currently works on an ESP8266 based wifi console to display metrics and some simple battery powered wifi buttons to trigger commands:
The community is growing. I've also got a feedback from an automotive engineer who was absolutely astonished discovering all the features and tools included.
I think we need better communication on what the OVMS can already do now, not only for users but especially also for technical applications and fleet management.
Regards, Michael
Am 18.01.19 um 14:18 schrieb Mark Webb-Johnson:
I think we are ready for a 3.2.000 OTA release to EAP. I’ve built this, and it is in the nightly build system ready to go.
I’ve completed all the JavaScript tasks, including migrating all the existing extensions to modular object format. That is a breaking change (existing scripts will break), but easy to do now than later when more are using it. I really haven’t heard of anyone using javascript with the system at the moment.
With 200 commits, the changelog is massive. The scripting system warrants a 3.2 release.
Please have a try with this in your cars, and let me know of any issues. If nothing comes up in the next day, I’ll move it to EAP at the weekend.
Thanks to everyone who contributed to this. The system functionality is really very impressive now, and only getting better as time goes by.
Regards, Mark _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
How about ‘extras’ as a top level directory? Then sub-directories below that for the various types of extras. Please go ahead and create the structure you are happy with. Regards, Mark.
On 18 Jan 2019, at 11:36 PM, Michael Balzer <dexter@expeedo.de> wrote:
Yep, definitely worth a major revision bump, and a huge thanks from me to everyone here as well.
The scripting system before wasn't suited for much more than simple calculations, and editing scripts on the console wasn't likely to attract users as well. I think we'll see some cool applications evolve from this now. Maybe we should add a top level directory for scripting extensions?
A number of users also jumped into web plugin development, that could also be worth a top level directory. If only as an incentive to publish their results.
Btw, a user currently works on an ESP8266 based wifi console to display metrics and some simple battery powered wifi buttons to trigger commands:
<fikgienoeoefpmjb.jpeg>
The community is growing. I've also got a feedback from an automotive engineer who was absolutely astonished discovering all the features and tools included.
I think we need better communication on what the OVMS can already do now, not only for users but especially also for technical applications and fleet management.
Regards, Michael
Am 18.01.19 um 14:18 schrieb Mark Webb-Johnson:
I think we are ready for a 3.2.000 OTA release to EAP. I’ve built this, and it is in the nightly build system ready to go.
I’ve completed all the JavaScript tasks, including migrating all the existing extensions to modular object format. That is a breaking change (existing scripts will break), but easy to do now than later when more are using it. I really haven’t heard of anyone using javascript with the system at the moment.
With 200 commits, the changelog is massive. The scripting system warrants a 3.2 release.
Please have a try with this in your cars, and let me know of any issues. If nothing comes up in the next day, I’ll move it to EAP at the weekend.
Thanks to everyone who contributed to this. The system functionality is really very impressive now, and only getting better as time goes by.
Regards, Mark _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Hi Michael,
I think we need better communication on what the OVMS can already do now, not only for users but especially also for technical applications and fleet management.
I would be happy to help with this. What are you thinking? Rob --- On Wed, 23 Jan 2019 11:49:08 +0000 Mark Webb-Johnson <mailto:mark@webb-johnson.net> wrote ---- How about ‘extras’ as a top level directory? Then sub-directories below that for the various types of extras. Please go ahead and create the structure you are happy with. Regards, Mark. On 18 Jan 2019, at 11:36 PM, Michael Balzer <mailto:dexter@expeedo.de> wrote: Yep, definitely worth a major revision bump, and a huge thanks from me to everyone here as well. The scripting system before wasn't suited for much more than simple calculations, and editing scripts on the console wasn't likely to attract users as well. I think we'll see some cool applications evolve from this now. Maybe we should add a top level directory for scripting extensions? A number of users also jumped into web plugin development, that could also be worth a top level directory. If only as an incentive to publish their results. Btw, a user currently works on an ESP8266 based wifi console to display metrics and some simple battery powered wifi buttons to trigger commands: <fikgienoeoefpmjb.jpeg> The community is growing. I've also got a feedback from an automotive engineer who was absolutely astonished discovering all the features and tools included. I think we need better communication on what the OVMS can already do now, not only for users but especially also for technical applications and fleet management. Regards, Michael Am 18.01.19 um 14:18 schrieb Mark Webb-Johnson: I think we are ready for a 3.2.000 OTA release to EAP. I’ve built this, and it is in the nightly build system ready to go. I’ve completed all the JavaScript tasks, including migrating all the existing extensions to modular object format. That is a breaking change (existing scripts will break), but easy to do now than later when more are using it. I really haven’t heard of anyone using javascript with the system at the moment. With 200 commits, the changelog is massive. The scripting system warrants a 3.2 release. Please have a try with this in your cars, and let me know of any issues. If nothing comes up in the next day, I’ll move it to EAP at the weekend. Thanks to everyone who contributed to this. The system functionality is really very impressive now, and only getting better as time goes by. Regards, Mark _______________________________________________ OvmsDev mailing list mailto:OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list mailto:OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list mailto:OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Rob, for example, technicians could be appealed by… - three CAN buses - SD logging - wifi streaming - scriptable frame injections and replays - reverse engineering toolkit - CANopen toolkit - DBC framework - scriptable GPIO - GPS tracking Fleet operators possibly don't know about the OVMS… - being able to not only monitor car positions and tracks but also internal status metrics like SOC, energy consumption, battery health etc. - being able to remotely control charging - being able to remotely control the car climate (→ a car sharing fleet that preheats the car you're about to use?) - being able to remotely disable or restrict car usage - enabling simple integration into existing fleet management systems as well as operating your own fleet management server There's possibly more. Regards, Michael Am 25.01.19 um 23:10 schrieb Robert Sharpe (Electric Vehicle Consultant):
Hi Michael,
I think we need better communication on what the OVMS can already do now, not only for users but especially also for technical applications and fleet management.
I would be happy to help with this. What are you thinking?
Rob
--- On Wed, 23 Jan 2019 11:49:08 +0000 *Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>>* wrote ----
How about ‘extras’ as a top level directory? Then sub-directories below that for the various types of extras.
Please go ahead and create the structure you are happy with.
Regards, Mark.
On 18 Jan 2019, at 11:36 PM, Michael Balzer <dexter@expeedo.de <mailto:dexter@expeedo.de>> wrote:
Yep, definitely worth a major revision bump, and a huge thanks from me to everyone here as well.
The scripting system before wasn't suited for much more than simple calculations, and editing scripts on the console wasn't likely to attract users as well. I think we'll see some cool applications evolve from this now. Maybe we should add a top level directory for scripting extensions?
A number of users also jumped into web plugin development, that could also be worth a top level directory. If only as an incentive to publish their results.
Btw, a user currently works on an ESP8266 based wifi console to display metrics and some simple battery powered wifi buttons to trigger commands:
<fikgienoeoefpmjb.jpeg>
The community is growing. I've also got a feedback from an automotive engineer who was absolutely astonished discovering all the features and tools included.
I think we need better communication on what the OVMS can already do now, not only for users but especially also for technical applications and fleet management.
Regards, Michael
Am 18.01.19 um 14:18 schrieb Mark Webb-Johnson:
I think we are ready for a 3.2.000 OTA release to EAP. I’ve built this, and it is in the nightly build system ready to go.
I’ve completed all the JavaScript tasks, including migrating all the existing extensions to modular object format. That is a breaking change (existing scripts will break), but easy to do now than later when more are using it. I really haven’t heard of anyone using javascript with the system at the moment.
With 200 commits, the changelog is massive. The scripting system warrants a 3.2 release.
Please have a try with this in your cars, and let me know of any issues. If nothing comes up in the next day, I’ll move it to EAP at the weekend.
Thanks to everyone who contributed to this. The system functionality is really very impressive now, and only getting better as time goes by.
Regards, Mark _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
I just got a heap corruption on my more or less idling bench module: I (19500734) housekeeping: 2019-01-18 20:54:13 CET (RAM: 8b=102516-103792 32b=10196) OVMS# CORRUPT HEAP: Bad head at 0x3f8269b4. Expected 0xabba1234 got 0x3f826b84 assertion "head != NULL" failed: file "/home/balzer/esp/esp-idf/components/heap/multi_heap_poisoning.c", line 205, function: multi_heap_free abort() was called at PC 0x4010f35b on core 1 Backtrace: 0x40091184:0x3ffe1e90 0x4009137f:0x3ffe1eb0 0x4010f35b:0x3ffe1ed0 0x40098041:0x3ffe1f00 0x40085362:0x3ffe1f20 0x400857a1:0x3ffe1f40 0x4000bec7:0x3ffe1f60 0x4015e931:0x3ffe1f80 0x4015e961:0x3ffe1 fa0 0x4015ff61:0x3ffe1fc0 0x401605eb:0x3ffe20b0 0x40160687:0x3ffe20d0 0x40163a2f:0x3ffe2120 0x4010ba3a:0x3ffe21f0 0x4010d4a6:0x3ffe2220 0x4010ba3a:0x3ffe2240 0x4010bf77:0x3ffe2270 0x4010c027:0x3ffe22a0 0x4 010dc33:0x3ffe22d0 0x4010debd:0x3ffe2310 0x4010a005:0x3ffe2370 0x400f3900:0x3ffe2390 0x400f396d:0x3ffe23e0 The corruption was detected on a free() call from the websocket tx handler, that does only reads on the object in question. Everything else in the backtrace is mongoose. Any ideas? Some task writing out of bounds could explain issue #189 as well… Regards, Michael Am 18.01.19 um 14:18 schrieb Mark Webb-Johnson:
I think we are ready for a 3.2.000 OTA release to EAP. I’ve built this, and it is in the nightly build system ready to go.
I’ve completed all the JavaScript tasks, including migrating all the existing extensions to modular object format. That is a breaking change (existing scripts will break), but easy to do now than later when more are using it. I really haven’t heard of anyone using javascript with the system at the moment.
With 200 commits, the changelog is massive. The scripting system warrants a 3.2 release.
Please have a try with this in your cars, and let me know of any issues. If nothing comes up in the next day, I’ll move it to EAP at the weekend.
Thanks to everyone who contributed to this. The system functionality is really very impressive now, and only getting better as time goes by.
Regards, Mark _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
participants (4)
-
Fran Terry -
Mark Webb-Johnson -
Michael Balzer -
Robert Sharpe (Electric Vehicle Consultant)