<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
@All: please note there was an error in both sdkconfig default
files, LWIP SO_REUSE was not enabled. That is necessary for the wifi
reconfiguration to work.<br>
<br>
If you patch your existing sdkconfig, you also need to add the
second line:<br>
<br>
<tt>CONFIG_LWIP_SO_REUSE=y</tt><tt><br>
</tt><tt>CONFIG_LWIP_SO_REUSE_RXTOALL=y</tt><br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 05.05.2018 um 20:57 schrieb Michael
Balzer:<br>
</div>
<blockquote type="cite"
cite="mid:eb3382ec-f1b3-2907-3e75-8ccdf8b57ebd@expeedo.de">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
I have just pushed the first version of a setup wizard.<br>
<br>
It currently consists of five steps:<br>
<ol>
<li>Secure module access (configure wifi AP and module password)<br>
</li>
<li>Connect module to internet (switch to Wifi APCLIENT mode)</li>
<li>Update to latest firmware version</li>
<li>Configure vehicle type and server</li>
<li>Configure modem (if equipped)</li>
</ol>
I tried hard to avoid any dead ends and simplify the process as
much as possible, but need your help to test if I really handled
all potential screw-ups.<br>
<br>
I developed and tested the whole process on my 3.0 hardware
module, so if you've got an unused 3.0 module you can use that for
the test without destroying your car configuration.<br>
<br>
The wizard state is kept in config module / init, with states "1"
… "5" = steps above + sub steps suffixed, and "done" being the
final state. There is currently no "back" option, but you can
simply set the config variable.<br>
<br>
You can start at any point, regardless of the configuration
already existing. The wizard will also not change configuration
options it doesn't need to touch, so you can run it also on an
already configured module. But it's really meant to be a first
init wizard, and thus won't be a standard menu option.<br>
<br>
It only shows if module/init is not "done". If you try the new
version on an existing module, you won't see the wizard until you
do:<br>
<ul>
<li><tt>config set module init ""</tt><br>
</li>
</ul>
…that's because the previous "password/changed" variable is
migrated to "module/init=done".<br>
<br>
The wizard is offered on the home screen if init is empty. It
automatically loads after login and from the home screen when
started, but it does not block the UI. You can use all UI pages
normally, to return to the wizard, simply click the home icon.<br>
<br>
Logging is currently maybe a bit excessive, especially as it's on
the info level. That is to be able to get some debug info also
from modules in default configuration.<br>
<br>
Regards,<br>
Michael<br>
<br>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>