Today, we are pleased to release v3.2.002 to general availability. This is the first public v3.2 version, with approximately 200 bug fixes and enhancements (mostly to individual vehicle support modules). A summary of the major changes is here: 2019-05-12 MWJ 3.2.002 OTA release - Locations: Introduce support for location actions - Twizy: Release 1.0.0 -- all V2 features planned are now included in V3 - Vehicle framework: Regenerative braking signal generation - Vehicle framework: DBC and RETOOLS integrations - Vehicles: Extensions to Kia Niro, Kia Soul, Mitsubishi, Nissan Leaf, Renault Twizy, SmartID, Tesla Model S, and Think City 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) 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
This evening I have received 6 notifications (so far) from the iOS app telling me that this new release is available. I have properly dismissed each of the notifications, so it is not just a repeat for lack of acknowledgement. Is something broken? -- Steve On Mon, 27 May 2019, Mark Webb-Johnson wrote:
Today, we are pleased to release v3.2.002 to general availability. This is the first public v3.2 version, with approximately 200 bug fixes and enhancements (mostly to individual vehicle support modules). A summary of the major changes is here:
2019-05-12 MWJ 3.2.002 OTA release - Locations: Introduce support for location actions - Twizy: Release 1.0.0 -- all V2 features planned are now included in V3 - Vehicle framework: Regenerative braking signal generation - Vehicle framework: DBC and RETOOLS integrations - Vehicles: Extensions to Kia Niro, Kia Soul, Mitsubishi, Nissan Leaf, Renault Twizy, SmartID, Tesla Model S, and Think City 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)
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
Steve, I’ve seen that in the past where the module had trouble downloading the firmware. Every ten minutes, in the hour you set it to download at, it will check what is available and if I new version is available, it will notify: New OTA firmware XXX is available for download It will then try to prepare the flash partition, download, and reboot into that. If everything was successful, just before reboot it will notify: OTA firmware XXX has been updated (OVMS will restart) So, if you are getting a notification every ten minutes (six in the hour), saying new firmware is available, the most likely cause is that it can’t download and install the new firmware. Regards, Mark.
On 28 May 2019, at 11:45 AM, Stephen Casner <casner@acm.org> wrote:
This evening I have received 6 notifications (so far) from the iOS app telling me that this new release is available. I have properly dismissed each of the notifications, so it is not just a repeat for lack of acknowledgement. Is something broken?
-- Steve
On Mon, 27 May 2019, Mark Webb-Johnson wrote:
Today, we are pleased to release v3.2.002 to general availability. This is the first public v3.2 version, with approximately 200 bug fixes and enhancements (mostly to individual vehicle support modules). A summary of the major changes is here:
2019-05-12 MWJ 3.2.002 OTA release - Locations: Introduce support for location actions - Twizy: Release 1.0.0 -- all V2 features planned are now included in V3 - Vehicle framework: Regenerative braking signal generation - Vehicle framework: DBC and RETOOLS integrations - Vehicles: Extensions to Kia Niro, Kia Soul, Mitsubishi, Nissan Leaf, Renault Twizy, SmartID, Tesla Model S, and Think City 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)
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
Mark, Thanks, that explains it. I had forgotten that I had enabled auto-update at 0300; since the timezone setting appears to be GMT, that matches the hour when I received the notifications. I should not have auto-update enabled since I am running a current build of my own: Version: 3.2.001-18-gac0ae29b-dirty/ota_1/main (build idf v3.1-dev-2835-g151269458-dirty May 23 2019 17:16:23) I'm not sure why the download would have failed, though. I installed a separate access point in my garage so that OVMS now has good wifi connectivity. -- Steve On Tue, 28 May 2019, Mark Webb-Johnson wrote:
Steve,
I’ve seen that in the past where the module had trouble downloading the firmware. Every ten minutes, in the hour you set it to download at, it will check what is available and if I new version is available, it will notify:
New OTA firmware XXX is available for download
It will then try to prepare the flash partition, download, and reboot into that. If everything was successful, just before reboot it will notify:
OTA firmware XXX has been updated (OVMS will restart)
So, if you are getting a notification every ten minutes (six in the hour), saying new firmware is available, the most likely cause is that it can’t download and install the new firmware.
Regards, Mark.
On 28 May 2019, at 11:45 AM, Stephen Casner <casner@acm.org> wrote:
This evening I have received 6 notifications (so far) from the iOS app telling me that this new release is available. I have properly dismissed each of the notifications, so it is not just a repeat for lack of acknowledgement. Is something broken?
-- Steve
participants (2)
-
Mark Webb-Johnson -
Stephen Casner