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> 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> 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 mailing list



_______________________________________________
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