January 2019 - OvmsDev - Open Vehicles

Anyone else get an ESP-EYE from espressif?
by Stephen Casner 08 Jan '19

08 Jan '19

Because I contributed some code back to espressif for esp-idf they sent to me a gift of their new ESP-EYE development board plus a T-shirt. Did anyone else get this gift? The ESP-EYE board includes a camera and the notes indicate that it is supposed to do facial recognition but there is very little information available at this point. See https://www.cnx-software.com/2019/01/02/esp-eye-esp32-ai-development-board/ -- Steve

2 1

Javascript - Documentation
by Robert Sharpe (Electric Vehicle Consultant) 07 Jan '19

07 Jan '19

Hi, In order to help new users access the power of the OVMS I have pulled together some of the scripting documentation. It is mainly from http://bit.ly/2FcqnyS and is in a draft section in a http://bit.ly/2sdkgmh that will later be integrated into User Manual once reviewed. I don't have an OVMS unit at the moment so cant test myself. So it would be great if those with experience of using the scripting feature could review/add to the above document as necessary. You will need to request access, mainly so that I can come back to specific people if I need to clarify anything (rather than pinging the entire group). Also happy to take known issues not in the http://bit.ly/2CUS8KX and capture in github. Thanks, Rob

1 1

Javascript
by Robert Sharpe (Electric Vehicle Consultant) 07 Jan '19

07 Jan '19

Hi Mark, Great news about scripting. Which of your comments below are still to be addressed? Note that this is very hacky and experimental at the moment. A better approach seems to be to have a javascript task running, initialised at boot with a user’s javascript program. That can have timers, and whatever else it needs, to do it’s stuff. Then, scripts executed are run in the context of that task. The current implementation is really just a proof of concept. The OvmsPrint is particularly kludgy (a better implementation would be to hook to the duktape I/O > system). Duktape is also currently running in internal RAM, although changing it to use SPI RAM should not be hard. Thanks, Rob Am 09.07.2018 um 07:40 schrieb Mark Webb-Johnson: > > I’ve enabled the javascript support in the ovms_scripts module. You can now write script files using the javascript language, and they will be run by the > duktape engine. Any script file ending with “.js” extension will be treated as javascript. > > I’ve also added OvmsCommand and OvmsPrint extension commands. > > Two examples: > > OVMS# vfs cat /store/scripts/helloworld.js > OvmsPrint("Hello world!\n”); > > OVMS# . helloworld.js > Hello world! > > > OVMS# vfs cat /store/scripts/ota.js > OvmsPrint(OvmsCommand("ota status")); > > OVMS# . ota.js > Running partition: factory > Boot partition: factory > Firmware: 3.1.008-40-g9254170-dirty/factory/edge (build idf v3.1-dev-1583-g0fb2019f Jul 9 2018 08:49:48) > Server Available: 3.1.008-37-g939416c (no update required) > > Sat Jul 7 16:00:45 UTC 2018 Automated build (markhk8) > ... > > > A useful example would be to have a script that runs on location.leave, and checks the v.e.gear metric for vehicle in Drive, before firing off the homelink to > close the garage door. > > Like all good things, the opportunity for evil is forever prevalent (and truly scary): > > OVMS# vfs cat /store/scripts/bruteforce.js > for (var pin = 1000; pin < 10000; pin++) > { > OvmsCommand("unlock " + pin); > } > > OVMS# . bruteforce.js > V (1421374) canlog: TX can1 id 102 len 8: 0b 03 00 00 e8 03 00 40 | .......@ > V (1421374) canlog: TX can1 id 102 len 8: 0b 03 00 00 e9 03 00 40 | .......@ > V (1421374) canlog: TX can1 id 102 len 8: 0b 03 00 00 ea 03 00 40 | .......@ > V (1421384) canlog: TX can1 id 102 len 8: 0b 03 00 00 eb 03 00 40 | .......@ > V (1421384) canlog: TX can1 id 102 len 8: 0b 03 00 00 ec 03 00 40 | .......@ > V (1421384) canlog: TX can1 id 102 len 8: 0b 03 00 00 ed 03 00 40 | .......@ > V (1421384) canlog: TX can1 id 102 len 8: 0b 03 00 00 ee 03 00 40 | .......@ > V (1421384) canlog: TX can1 id 102 len 8: 0b 03 00 00 ef 03 00 40 | .......@ > V (1421384) canlog: TX can1 id 102 len 8: 0b 03 00 00 f0 03 00 40 | .......@ > V (1421394) canlog: TX can1 id 102 len 8: 0b 03 00 00 f1 03 00 40 | .......@ > ... > > > I’ll leave it up to an exercise to the reader to change that script to use DukOvmsMetricValue() to monitor the v.e.locked metric to record success. > > Note that this is very hacky and experimental at the moment. A better approach seems to be to have a javascript task running, initialised at boot with a > user’s javascript program. That can have timers, and whatever else it needs, to do it’s stuff. Then, scripts executed are run in the context of that task. The > current implementation is really just a proof of concept. The OvmsPrint is particularly kludgy (a better implementation would be to hook to the duktape I/O > system). Duktape is also currently running in internal RAM, although changing it to use SPI RAM should not be hard. > > Regards, Mark. > >> Begin forwarded message: >> >> *From: *GitHub >> >> Branch: refs/heads/master >> Home: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3 >> Commit: f1736f927df582c5ff374ef5d8c3a565e8f67295 >> https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/f17… >> Author: Mark Webb-Johnson <http://lists.openvehicles.com/mailman/listinfo/ovmsdev <mailto:http://lists.openvehicles.com/mailman/listinfo/ovmsdev>> >> Date: 2018-07-09 (Mon, 09 Jul 2018) >> >> Changed paths: >> M vehicle/OVMS.V3/main/ovms_command.cpp >> >> Log Message: >> ----------- >> Javascript: Add a OvmsCommand function to execute an OVMS command >> >> >> Commit: 69427f4ac0cf68dc462b05752936befe4be22256 >> https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/694… >> Author: Mark Webb-Johnson <http://lists.openvehicles.com/mailman/listinfo/ovmsdev <mailto:http://lists.openvehicles.com/mailman/listinfo/ovmsdev>> >> Date: 2018-07-09 (Mon, 09 Jul 2018) >> >> Changed paths: >> M vehicle/OVMS.V3/main/ovms_script.cpp >> >> Log Message: >> ----------- >> Javascript: Add a OvmsPrint function to be able to print a string >> JavaScript: Support .js script files (executed with javascript engine) >> >> >> Compare: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/compare/92… >> **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ >> >> Functionality will be removed from GitHub.com <http://github.com/> on January 31st, 2019. > > > > _______________________________________________ > OvmsDev mailing list > 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

1 0

github usability work
by Robert Sharpe (Electric Vehicle Consultant) 06 Jan '19

06 Jan '19

Hi Mark, I wanted to tidy up new issues created related to the usability work I am doing. But cant seem to create or apply labels. Could you apply the labels "enhanced" and "help wanted" to the following https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/181 #181 opened 7 days ago by https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues?q=i… https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/180 #180 opened 7 days ago by https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues?q=i… Also it would be good to categorise issues associated with this work. How do you suggest we do that eg using a "Label" or "Project" Rob

2 3

Android app vs. iOS app
by Geir Øyvind Vælidalo 06 Jan '19

06 Jan '19

Hi guys, I’ve done some assumptions when it comes to how the apps works and I need to know if the Android app disconnects when it is put in the background or if it keeps up the connection to the OVMS unit in the car. The iOS app disconnects for certain when it is put in the background, and I’ve taken for granted that the Android app also do that. Best regards, Geir

2 2