https://www.openvehicles.com/node/2123 <https://www.openvehicles.com/node/2123> Today, we are pleased to release v3.2.0-1 to Early Access Program (EAP) participants. This is the first public v3.2 version, and introduces an entirely new scripting framework based on an embedded javascript engine. Now, custom javascript modules and functions can be written to respond to system events. In addition, a host of other UI changes enhancements have been made. A summary of the major changes is here: 2019-01-19 MWJ 3.2.001 OTA release - v3.2 first public release - New JavaScript modular framework allowing for dynamic scripting and object model - New vehicle: Smart ED (adaption by Martin Graml ) - Mitsubishi i-MiEV re-write for OVMS v3 - Web UI: text / script editor - Web UI: user plugin support (pages & hooks) - Web UI: night mode by URI parameter, e.g. "…/#/dashboard?nm=1" - Web UI: dashboard accessible w/o login - Web UI: added config backup & restore tool - Web UI: file selector added for firmware flashing from SD - Web UI: text notifications (info/error/alert) displayed as dialogs - Twizy web UI: drivemode buttons secured & added to dashboard - Twizy web UI: added file dialog for virtual dyno recording - Twizy: SEVCON monitoring & recording New commands: xrt mon start [] xrt mon stop xrt mon reset New metrics: xrt.i.* = operational inverter data xrt.s.* = power & torque by speed (virtual dyno) - Twizy: experimental powermap calculation including region 3 / breakdown torque New config: xrt [motor_trq_breakdown] = 0 Breakdown torque in Nm, e.g. 210.375 xrt [motor_rpm_rated] = 0 Rated speed in rpm, e.g. 2100 See docs/Renault-Twizy/Twizy-Powermap-Calculator-Tbrk.ods for details. - Add inactivity watchdog timers to CAN buses - NissanLeaf: Fix for 0% SOH on 30KWh models with Nissan BMS update - Introduction of support for DBC CAN bus configuration files For full detail on all changes, check the GitHub revision history. The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all without requiring special hardware programmers like the PICKIT used for v2. The simplest way to update the module firmware is to connect it as a client to your wifi network (or phone hotspot), and then use the web interface Config / Firmware / Flash-from-Web; that will show you the version you are running, as well as the latest version available for update. One click on 'Flash now' and the update will be downloaded and installed. Alternatively, you can download the firmware update to a file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the card into the module's slot - the new firmware will be updated automatically and the file renamed ovms3.done to signify completion. This firmware also includes the feature to check for and automatically update to newly available firmware, every night (so long as the vehicle is connected to WiFi). After updating to 3.1.005 or later, you can enable this for future firmware releases with 'config ota auto yes'. You can choose the release level by setting 'config ota tag edge|eap|main', as one of: edge: Bleeding edge developer nightly-builds eap: Early Access Program (full releases, but with little public testing) main: Publicly tested full releases (the most stable) We expect to release the 3.2.001 firmware to 'main' (all users) after EAP testing (most likely within a week or so). Thank you to all the open source developers who have contributed to this, and previous, releases, and thank you for your support of the project. Open Vehicles
I’ve just moved this 3.2.001 to ‘main’ release level. If anybody wants to include something, please commit. Hoping to build 3.2.002 for EAP later this week. Regards, Mark.
On 19 Jan 2019, at 5:00 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
https://www.openvehicles.com/node/2123 <https://www.openvehicles.com/node/2123>
Today, we are pleased to release v3.2.0-1 to Early Access Program (EAP) participants. This is the first public v3.2 version, and introduces an entirely new scripting framework based on an embedded javascript engine. Now, custom javascript modules and functions can be written to respond to system events. In addition, a host of other UI changes enhancements have been made. A summary of the major changes is here: 2019-01-19 MWJ 3.2.001 OTA release - v3.2 first public release - New JavaScript modular framework allowing for dynamic scripting and object model - New vehicle: Smart ED (adaption by Martin Graml ) - Mitsubishi i-MiEV re-write for OVMS v3 - Web UI: text / script editor - Web UI: user plugin support (pages & hooks) - Web UI: night mode by URI parameter, e.g. "…/#/dashboard?nm=1" - Web UI: dashboard accessible w/o login - Web UI: added config backup & restore tool - Web UI: file selector added for firmware flashing from SD - Web UI: text notifications (info/error/alert) displayed as dialogs - Twizy web UI: drivemode buttons secured & added to dashboard - Twizy web UI: added file dialog for virtual dyno recording - Twizy: SEVCON monitoring & recording New commands: xrt mon start [] xrt mon stop xrt mon reset New metrics: xrt.i.* = operational inverter data xrt.s.* = power & torque by speed (virtual dyno) - Twizy: experimental powermap calculation including region 3 / breakdown torque New config: xrt [motor_trq_breakdown] = 0 Breakdown torque in Nm, e.g. 210.375 xrt [motor_rpm_rated] = 0 Rated speed in rpm, e.g. 2100 See docs/Renault-Twizy/Twizy-Powermap-Calculator-Tbrk.ods for details. - Add inactivity watchdog timers to CAN buses - NissanLeaf: Fix for 0% SOH on 30KWh models with Nissan BMS update - Introduction of support for DBC CAN bus configuration files For full detail on all changes, check the GitHub revision history. The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all without requiring special hardware programmers like the PICKIT used for v2. The simplest way to update the module firmware is to connect it as a client to your wifi network (or phone hotspot), and then use the web interface Config / Firmware / Flash-from-Web; that will show you the version you are running, as well as the latest version available for update. One click on 'Flash now' and the update will be downloaded and installed. Alternatively, you can download the firmware update to a file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the card into the module's slot - the new firmware will be updated automatically and the file renamed ovms3.done to signify completion. This firmware also includes the feature to check for and automatically update to newly available firmware, every night (so long as the vehicle is connected to WiFi). After updating to 3.1.005 or later, you can enable this for future firmware releases with 'config ota auto yes'. You can choose the release level by setting 'config ota tag edge|eap|main', as one of: edge: Bleeding edge developer nightly-builds eap: Early Access Program (full releases, but with little public testing) main: Publicly tested full releases (the most stable) We expect to release the 3.2.001 firmware to 'main' (all users) after EAP testing (most likely within a week or so). Thank you to all the open source developers who have contributed to this, and previous, releases, and thank you for your support of the project. Open Vehicles _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Any chance someone can include door lock/unlock for Leaf? Then I don´t have to compile the code every time to get the function, and can use the auto-update function. I have no idea how to commit anything to git. Kind regards, Stein Arne Sordal On 2019-02-04 06:11, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
I’ve just moved this 3.2.001 to ‘main’ release level.
If anybody wants to include something, please commit. Hoping to build 3.2.002 for EAP later this week.
Regards, Mark.
On 19 Jan 2019, at 5:00 PM, Mark Webb-Johnson <mark@webb-johnson.net(mailto:mark@webb-johnson.net)> wrote: https://www.openvehicles.com/node/2123
Today, we are pleased to release v3.2.0-1 to Early Access Program (EAP) participants. This is the first public v3.2 version, and introduces an entirely new scripting framework based on an embedded javascript engine. Now, custom javascript modules and functions can be written to respond to system events. In addition, a host of other UI changes enhancements have been made. A summary of the major changes is here: 2019-01-19 MWJ 3.2.001 OTA release - v3.2 first public release - New JavaScript modular framework allowing for dynamic scripting and object model - New vehicle: Smart ED (adaption by Martin Graml ) - Mitsubishi i-MiEV re-write for OVMS v3 - Web UI: text / script editor - Web UI: user plugin support (pages & hooks) - Web UI: night mode by URI parameter, e.g. "…/#/dashboard?nm=1" - Web UI: dashboard accessible w/o login - Web UI: added config backup & restore tool - Web UI: file selector added for firmware flashing from SD - Web UI: text notifications (info/error/alert) displayed as dialogs - Twizy web UI: drivemode buttons secured & added to dashboard - Twizy web UI: added file dialog for virtual dyno recording - Twizy: SEVCON monitoring & recording New commands: xrt mon start [] xrt mon stop xrt mon reset New metrics: xrt.i.* = operational inverter data xrt.s.* = power & torque by speed (virtual dyno) - Twizy: experimental powermap calculation including region 3 / breakdown torque New config: xrt [motor_trq_breakdown] = 0 Breakdown torque in Nm, e.g. 210.375 xrt [motor_rpm_rated] = 0 Rated speed in rpm, e.g. 2100 See docs/Renault-Twizy/Twizy-Powermap-Calculator-Tbrk.ods for details. - Add inactivity watchdog timers to CAN buses - NissanLeaf: Fix for 0% SOH on 30KWh models with Nissan BMS update - Introduction of support for DBC CAN bus configuration files For full detail on all changes, check the GitHub revision history. The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all without requiring special hardware programmers like the PICKIT used for v2. The simplest way to update the module firmware is to connect it as a client to your wifi network (or phone hotspot), and then use the web interface Config / Firmware / Flash-from-Web; that will show you the version you are running, as well as the latest version available for update. One click on 'Flash now' and the update will be downloaded and installed. Alternatively, you can download the firmware update to a file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the card into the module's slot - the new firmware will be updated automatically and the file renamed ovms3.done to signify completion. This firmware also includes the feature to check for and automatically update to newly available firmware, every night (so long as the vehicle is connected to WiFi). After updating to 3.1.005 or later, you can enable this for future firmware releases with 'config ota auto yes'. You can choose the release level by setting 'config ota tag edge|eap|main', as one of:
edge: Bleeding edge developer nightly-builds eap: Early Access Program (full releases, but with little public testing) main: Publicly tested full releases (the most stable)
We expect to release the 3.2.001 firmware to 'main' (all users) after EAP testing (most likely within a week or so). Thank you to all the open source developers who have contributed to this, and previous, releases, and thank you for your support of the project. Open Vehicles _______________________________________________ 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
Can you give details on what you are compiling custom, and where you are getting the code from? I checked the current driver and there doesn’t seem to be any door lock code. Also checked github pull requests, but nothing related to that. Of it this is your extension, can you email it in? Regards, Mark
On 4 Feb 2019, at 4:39 PM, ovms <ovms@topphemmelig.no> wrote:
Any chance someone can include door lock/unlock for Leaf? Then I don´t have to compile the code every time to get the function, and can use the auto-update function. I have no idea how to commit anything to git.
Kind regards, Stein Arne Sordal
On 2019-02-04 06:11, Mark Webb-Johnson <mark@webb-johnson.net> wrote: I’ve just moved this 3.2.001 to ‘main’ release level.
If anybody wants to include something, please commit. Hoping to build 3.2.002 for EAP later this week.
Regards, Mark.
On 19 Jan 2019, at 5:00 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
https://www.openvehicles.com/node/2123
Today, we are pleased to release v3.2.0-1 to Early Access Program (EAP) participants. This is the first public v3.2 version, and introduces an entirely new scripting framework based on an embedded javascript engine. Now, custom javascript modules and functions can be written to respond to system events. In addition, a host of other UI changes enhancements have been made. A summary of the major changes is here: 2019-01-19 MWJ 3.2.001 OTA release - v3.2 first public release - New JavaScript modular framework allowing for dynamic scripting and object model - New vehicle: Smart ED (adaption by Martin Graml ) - Mitsubishi i-MiEV re-write for OVMS v3 - Web UI: text / script editor - Web UI: user plugin support (pages & hooks) - Web UI: night mode by URI parameter, e.g. "…/#/dashboard?nm=1" - Web UI: dashboard accessible w/o login - Web UI: added config backup & restore tool - Web UI: file selector added for firmware flashing from SD - Web UI: text notifications (info/error/alert) displayed as dialogs - Twizy web UI: drivemode buttons secured & added to dashboard - Twizy web UI: added file dialog for virtual dyno recording - Twizy: SEVCON monitoring & recording New commands: xrt mon start [] xrt mon stop xrt mon reset New metrics: xrt.i.* = operational inverter data xrt.s.* = power & torque by speed (virtual dyno) - Twizy: experimental powermap calculation including region 3 / breakdown torque New config: xrt [motor_trq_breakdown] = 0 Breakdown torque in Nm, e.g. 210.375 xrt [motor_rpm_rated] = 0 Rated speed in rpm, e.g. 2100 See docs/Renault-Twizy/Twizy-Powermap-Calculator-Tbrk.ods for details. - Add inactivity watchdog timers to CAN buses - NissanLeaf: Fix for 0% SOH on 30KWh models with Nissan BMS update - Introduction of support for DBC CAN bus configuration files For full detail on all changes, check the GitHub revision history. The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all without requiring special hardware programmers like the PICKIT used for v2. The simplest way to update the module firmware is to connect it as a client to your wifi network (or phone hotspot), and then use the web interface Config / Firmware / Flash-from-Web; that will show you the version you are running, as well as the latest version available for update. One click on 'Flash now' and the update will be downloaded and installed. Alternatively, you can download the firmware update to a file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the card into the module's slot - the new firmware will be updated automatically and the file renamed ovms3.done to signify completion. This firmware also includes the feature to check for and automatically update to newly available firmware, every night (so long as the vehicle is connected to WiFi). After updating to 3.1.005 or later, you can enable this for future firmware releases with 'config ota auto yes'. You can choose the release level by setting 'config ota tag edge|eap|main', as one of:
edge: Bleeding edge developer nightly-builds eap: Early Access Program (full releases, but with little public testing) main: Publicly tested full releases (the most stable)
We expect to release the 3.2.001 firmware to 'main' (all users) after EAP testing (most likely within a week or so). Thank you to all the open source developers who have contributed to this, and previous, releases, and thank you for your support of the project. Open Vehicles _______________________________________________ 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 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Hi Mark, Attached is the two files I have changed before compiling. Can you use these two files and do a diff between yours and mine? Kind regards, Stein Arne Sordal On 2019-02-04 11:17, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Can you give details on what you are compiling custom, and where you are getting the code from? I checked the current driver and there doesn’t seem to be any door lock code. Also checked github pull requests, but nothing related to that.
Of it this is your extension, can you email it in?
Regards, Mark
On 4 Feb 2019, at 4:39 PM, ovms <ovms@topphemmelig.no(mailto:ovms@topphemmelig.no)> wrote:
Any chance someone can include door lock/unlock for Leaf? Then I don´t have to compile the code every time to get the function, and can use the auto-update function. I have no idea how to commit anything to git.
Kind regards, Stein Arne Sordal
On 2019-02-04 06:11, Mark Webb-Johnson <mark@webb-johnson.net(mailto:mark@webb-johnson.net)> wrote:
I’ve just moved this 3.2.001 to ‘main’ release level.
If anybody wants to include something, please commit. Hoping to build 3.2.002 for EAP later this week.
Regards, Mark.
On 19 Jan 2019, at 5:00 PM, Mark Webb-Johnson <mark@webb-johnson.net(mailto:mark@webb-johnson.net)> wrote: https://www.openvehicles.com/node/2123
Today, we are pleased to release v3.2.0-1 to Early Access Program (EAP) participants. This is the first public v3.2 version, and introduces an entirely new scripting framework based on an embedded javascript engine. Now, custom javascript modules and functions can be written to respond to system events. In addition, a host of other UI changes enhancements have been made. A summary of the major changes is here: 2019-01-19 MWJ 3.2.001 OTA release - v3.2 first public release - New JavaScript modular framework allowing for dynamic scripting and object model - New vehicle: Smart ED (adaption by Martin Graml ) - Mitsubishi i-MiEV re-write for OVMS v3 - Web UI: text / script editor - Web UI: user plugin support (pages & hooks) - Web UI: night mode by URI parameter, e.g. "…/#/dashboard?nm=1" - Web UI: dashboard accessible w/o login - Web UI: added config backup & restore tool - Web UI: file selector added for firmware flashing from SD - Web UI: text notifications (info/error/alert) displayed as dialogs - Twizy web UI: drivemode buttons secured & added to dashboard - Twizy web UI: added file dialog for virtual dyno recording - Twizy: SEVCON monitoring & recording New commands: xrt mon start [] xrt mon stop xrt mon reset New metrics: xrt.i.* = operational inverter data xrt.s.* = power & torque by speed (virtual dyno) - Twizy: experimental powermap calculation including region 3 / breakdown torque New config: xrt [motor_trq_breakdown] = 0 Breakdown torque in Nm, e.g. 210.375 xrt [motor_rpm_rated] = 0 Rated speed in rpm, e.g. 2100 See docs/Renault-Twizy/Twizy-Powermap-Calculator-Tbrk.ods for details. - Add inactivity watchdog timers to CAN buses - NissanLeaf: Fix for 0% SOH on 30KWh models with Nissan BMS update - Introduction of support for DBC CAN bus configuration files For full detail on all changes, check the GitHub revision history. The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all without requiring special hardware programmers like the PICKIT used for v2. The simplest way to update the module firmware is to connect it as a client to your wifi network (or phone hotspot), and then use the web interface Config / Firmware / Flash-from-Web; that will show you the version you are running, as well as the latest version available for update. One click on 'Flash now' and the update will be downloaded and installed. Alternatively, you can download the firmware update to a file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the card into the module's slot - the new firmware will be updated automatically and the file renamed ovms3.done to signify completion. This firmware also includes the feature to check for and automatically update to newly available firmware, every night (so long as the vehicle is connected to WiFi). After updating to 3.1.005 or later, you can enable this for future firmware releases with 'config ota auto yes'. You can choose the release level by setting 'config ota tag edge|eap|main', as one of:
edge: Bleeding edge developer nightly-builds eap: Early Access Program (full releases, but with little public testing) main: Publicly tested full releases (the most stable)
We expect to release the 3.2.001 firmware to 'main' (all users) after EAP testing (most likely within a week or so). Thank you to all the open source developers who have contributed to this, and previous, releases, and thank you for your support of the project. Open Vehicles _______________________________________________ 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(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
There seemed to be a few difference in what you sent vs what we have: No issues with the changes to typedef enum RemoteCommand and the CommandLock and CommandUnlock virtual implementations. No idea why CommandActivateValet was set to lock the doors? I didn’t copy that over. No idea why homelink button 2 was set to unlock the doors? I didn’t copy that over. There were a bunch of changes to the PollReply_Battery that didn’t seem current. I didn’t copy these over. Please have a review of #2 and #4, and let me know if anything further needs to go in related to these. The lock/unlock functionality should be in now. Can you try, and let us know if ok? Regards, Mark.
On 4 Feb 2019, at 6:28 PM, ovms <ovms@topphemmelig.no> wrote:
Hi Mark,
Attached is the two files I have changed before compiling. Can you use these two files and do a diff between yours and mine?
Kind regards, Stein Arne Sordal
On 2019-02-04 11:17, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Can you give details on what you are compiling custom, and where you are getting the code from? I checked the current driver and there doesn’t seem to be any door lock code. Also checked github pull requests, but nothing related to that.
Of it this is your extension, can you email it in?
Regards, Mark
On 4 Feb 2019, at 4:39 PM, ovms <ovms@topphemmelig.no <mailto:ovms@topphemmelig.no>> wrote: Any chance someone can include door lock/unlock for Leaf? Then I don´t have to compile the code every time to get the function, and can use the auto-update function. I have no idea how to commit anything to git.
Kind regards, Stein Arne Sordal
On 2019-02-04 06:11, Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>> wrote: I’ve just moved this 3.2.001 to ‘main’ release level.
If anybody wants to include something, please commit. Hoping to build 3.2.002 for EAP later this week.
Regards, Mark.
On 19 Jan 2019, at 5:00 PM, Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>> wrote:
https://www.openvehicles.com/node/2123 <https://www.openvehicles.com/node/2123>
Today, we are pleased to release v3.2.0-1 to Early Access Program (EAP) participants. This is the first public v3.2 version, and introduces an entirely new scripting framework based on an embedded javascript engine. Now, custom javascript modules and functions can be written to respond to system events. In addition, a host of other UI changes enhancements have been made. A summary of the major changes is here: 2019-01-19 MWJ 3.2.001 OTA release - v3.2 first public release - New JavaScript modular framework allowing for dynamic scripting and object model - New vehicle: Smart ED (adaption by Martin Graml ) - Mitsubishi i-MiEV re-write for OVMS v3 - Web UI: text / script editor - Web UI: user plugin support (pages & hooks) - Web UI: night mode by URI parameter, e.g. "…/#/dashboard?nm=1" - Web UI: dashboard accessible w/o login - Web UI: added config backup & restore tool - Web UI: file selector added for firmware flashing from SD - Web UI: text notifications (info/error/alert) displayed as dialogs - Twizy web UI: drivemode buttons secured & added to dashboard - Twizy web UI: added file dialog for virtual dyno recording - Twizy: SEVCON monitoring & recording New commands: xrt mon start [] xrt mon stop xrt mon reset New metrics: xrt.i.* = operational inverter data xrt.s.* = power & torque by speed (virtual dyno) - Twizy: experimental powermap calculation including region 3 / breakdown torque New config: xrt [motor_trq_breakdown] = 0 Breakdown torque in Nm, e.g. 210.375 xrt [motor_rpm_rated] = 0 Rated speed in rpm, e.g. 2100 See docs/Renault-Twizy/Twizy-Powermap-Calculator-Tbrk.ods for details. - Add inactivity watchdog timers to CAN buses - NissanLeaf: Fix for 0% SOH on 30KWh models with Nissan BMS update - Introduction of support for DBC CAN bus configuration files For full detail on all changes, check the GitHub revision history. The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all without requiring special hardware programmers like the PICKIT used for v2. The simplest way to update the module firmware is to connect it as a client to your wifi network (or phone hotspot), and then use the web interface Config / Firmware / Flash-from-Web; that will show you the version you are running, as well as the latest version available for update. One click on 'Flash now' and the update will be downloaded and installed. Alternatively, you can download the firmware update to a file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the card into the module's slot - the new firmware will be updated automatically and the file renamed ovms3.done to signify completion. This firmware also includes the feature to check for and automatically update to newly available firmware, every night (so long as the vehicle is connected to WiFi). After updating to 3.1.005 or later, you can enable this for future firmware releases with 'config ota auto yes'. You can choose the release level by setting 'config ota tag edge|eap|main', as one of:
edge: Bleeding edge developer nightly-builds eap: Early Access Program (full releases, but with little public testing) main: Publicly tested full releases (the most stable)
We expect to release the 3.2.001 firmware to 'main' (all users) after EAP testing (most likely within a week or so). Thank you to all the open source developers who have contributed to this, and previous, releases, and thank you for your support of the project. Open Vehicles _______________________________________________ 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>_______________________________________________ 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> _______________________________________________ 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>_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev <vehicle_nissanleaf.cpp><vehicle_nissanleaf.h>_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
On Mon, Feb 04, 2019 at 11:28:20AM +0100, ovms wrote:
Attached is the two files I have changed before compiling. Can you use these two files and do a diff between yours and mine?
There was an earlier thread about this: http://lists.openvehicles.com/pipermail/ovmsdev/2018-May/005167.html I did a branch for it back then, which I just updated: https://github.com/caederus-ovms/Open-Vehicle-Monitoring-System-3/tree/leaf-... However, I don't think the code is quite right, either on the branch or in Stein Arne Sordal's version; the latter also adds Homelink button 2 which duplicates the unlock function and CommandActivateValet which duplicates the lock function. Both versions should probably also address the issue Tom mentioned, (sending the lock/unklock command multiple times, if it isn't necessary): http://lists.openvehicles.com/pipermail/ovmsdev/2018-May/005182.html
Yes, I also used the valet/homelink function to lock the doors since the can-bus stops receiving after some time and the lock/unlock button is only one button that does not change status. -Stein Arne- On 2019-02-04 13:05, Robin O'Leary <ovmsdev@caederus.org> wrote:
On Mon, Feb 04, 2019 at 11:28:20AM +0100, ovms wrote: > Attached is the two files I have changed before compiling. Can you use these two files and do a diff between yours and mine? There was an earlier thread about this: http://lists.openvehicles.com/pipermail/ovmsdev/2018-May/005167.html I did a branch for it back then, which I just updated: https://github.com/caederus-ovms/Open-Vehicle-Monitoring-System-3/tree/leaf-... However, I don't think the code is quite right, either on the branch or in Stein Arne Sordal's version; the latter also adds Homelink button 2 which duplicates the unlock function and CommandActivateValet which duplicates the lock function. Both versions should probably also address the issue Tom mentioned, (sending the lock/unklock command multiple times, if it isn't necessary): http://lists.openvehicles.com/pipermail/ovmsdev/2018-May/005182.html _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http:! //lists.o
penvehicles.com/mailman/listinfo/ovmsdev
participants (3)
-
Mark Webb-Johnson -
ovms -
Robin O'Leary