Everyone,
please find attached the improved version of the UI:
- Optimized wording & user guidance
- Suppress irritating request errors
- Include run time estimation & progress bar
- Include "unplug now ok" info on process timeout
- Include setup mode reconnect details with factory reset
invocation
This needs to be tested in combination with a firmware including the
latest commits to master.
Be aware that due to the build partition table now being updated,
doing "make flash" on "master" is no longer sufficient to reset a
module to the previous partitioning. To revert to the old
partitioning including the latest changes, switch to the new test
branch "partitioning-v3-30", and do the "make flash" from there.
The runtime estimations should normally exceed the actual time
needed. I've also changed the initial time info to "up to 10
minutes", the process will normally take 5-6 minutes when starting
from an ota boot (standard for normal users). With the estimation on
the safe side, users shouldn't normally run into the "you may need
to unplug now" state.
Feedback is welcome.
Btw, the culprit for the slow intermediate reboots is the modem off
detection when no modem type has been configured (auto detect). That
process may be optimizable, but that's a task for another day.
Regards,
Michael
Am 02.05.26 um 20:08 schrieb Craig
Leres:
On 5/2/26
00:33, Michael Balzer via OvmsDev wrote:
After it copied the image to factory
(and wanted to reboot), I clicked "Download" and got "Request
error, please retry" (see attached). I clicked "Download"
again and I watched from the serial while it rebooted. I could
click download again but just get a log identical to the one
that ends with "Request error, please retry".
Yes, the request error is irritating, I'll suppress that. It's
the normal output of a command channel getting lost, here due to
the reboot.
My only concern is that when I saw the error message I thought
something had gone wrong.
The download button was meant to be able
to also download the initial command output, but it obviously
can get misinterpreted, so I'll remove it. We won't need it
anyway if we don't do the partition copy directly on command
invocation.
I actually like the download button; if something goes wrong you
have more information that you might if things go really wrong.
But I would prefer a unique name for each log.
Eventually I logged into module via ssh
and could see that it had completed successfully. I logged
back into the web gui and was able to download the entire log
(Partition-upgrade(3).txt)
(It reminded me of the windows xp "task failed successfully"
meme!)
With a little more patience, the web UI would have reloaded
automatically and shown the final success page (after login).
I get from this that it's not sufficient to place the info on
the update process…
Maybe a "don't navigate away from this page, the upgrade can take
up to 5 minutes" message?
The upgrade procedure runs*fully
automatic*, you just need to start it. Depending on your
configuration, the upgrade can take*up to 5 minutes*to finish,
so please be patient.
In case something goes wrong, the module will reboot into
standard mode, and you can use this page to display and
download the upgrade log for further analysis.
I saw/liked that feature.
Could we print progress messages on the serial console? (I might
have been more patient if I had thought to watch the console
earlier in the process.)
Craig
--
Michael Balzer * Am Rahmen 5 * D-58313 Herdecke
Fon 02330 9104094 * Handy 0176 20698926