<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div>I think Sunday end-of-day (US time) cut-off is fine. I’ll build the first production firmware first thing monday morning, my time.<div class=""><br class=""></div><div class="">Most likely, the first thing users will have to do will be to update firmware anyway :-)</div><div class=""><br class=""></div><div class="">Regards, Mark.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 16 Mar 2018, at 5:24 AM, Michael Balzer <<a href="mailto:dexter@expeedo.de" class="">dexter@expeedo.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
Mark,<br class="">
<br class="">
I'll take care of the password & OTA web UI. HTTP upload will
not be ready until sunday, but the first version of the standard OTA
form including help info will.<br class="">
<br class="">
I haven't finished the streaming mode yet, it seems there is some
sort of LWIP issue. It's usable though with a higher timeout, so
I'll do that as a workaround for the OTA UI. Streaming is necessary
to see the OTA command progress. The issue is the socket doesn't
begin to stream until the first 1024 buffer has been filled, despite
setting TCP_NODELAY. Reducing the send buffer size doesn't work at
all, LWIP gets stuck on the send if I do.<br class="">
<br class="">
I'll concentrate on implementing the workaround first, can try to
solve this later on.<br class="">
<br class="">
I'll also add your latest feature extensions (i.e. APCLIENT mode
& DNS server) to the config forms.<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Am 15.03.2018 um 09:06 schrieb Mark
Webb-Johnson:<br class="">
</div>
<blockquote type="cite" cite="mid:2A5D3637-9E02-47D4-9BB4-2591C9B9D946@webb-johnson.net" class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div class=""><br class="">
</div>
<div class="">All components have arrived, and final assembly is
happening now. Next week will be firmware flashing, QC, and then
packaging.</div>
<div class=""><br class="">
</div>
<div class="">Label looks like this:</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding:
0px;" class="">
<div class=""><span id="cid:part1.2E8E270F.24A4F167@expeedo.de"><SerialNumberLabel.png></span></div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">Last things to do, with the goal of making this as
easy as possible for the first guinea pig end users…</div>
<div class=""><br class="">
</div>
<div class="">
<ol class="MailOutline">
<li class="">Modem Stability. I’ve been working on this. Seems
ok now; I drive in and out of zero coverage areas often, and
it seems to recover. I’ll address any new issues as and when
I find them. It would be helpful if others could put these
in their cars, and feedback good/bad news.<br class="">
<br class="">
</li>
<li class="">Module Password (via web interface). I’ve asked
Michael to handle this, if he has time.<br class="">
<br class="">
</li>
<li class="">Tidy up of ‘secure’ mode. I’ve asked Steve to
handle this.<br class="">
<br class="">
</li>
<li class="">OTA. It is workable at the moment. Not automatic,
but pretty usable. I’ve committed my last change today so
that ‘ota status’ shows the version available on the server
(if wifi is up). It would be nice if the web interface could
help with this; and particularly nice if we could upload
firmware via the web interface directly to flash. I think
Michael is working on this (at least the help, if not the
upload).<br class="">
<br class="">
</li>
<li class="">Deadline for the above is this Sunday (18th
March).<br class="">
<br class="">
</li>
<li class="">End-User Documentation. This is priority now, and
deadline is the end of this month to have something good
enough for someone to follow to setup the module from
scratch.</li>
</ol>
</div>
<div class=""><br class="">
</div>
<div class="">The other production and Fasttech side of things is
being handled. We’re gonna have the Fasttech US$20 coupon codes
ready to go at launch. Hologram have also offered a US$5 coupon
code as a starter for OVMS users (both new and existing), which
will be ready at launch as well. Developers can benefit from
both.</div>
<div class=""><br class="">
</div>
<div class="">Fasttech will have 100 kits (50 US, 50 EU) and I’ll
have 20 (10 US, 10 EU). Normal orders can go through Fasttech -
if people need something special (just modems, just main boards,
etc) let me know and I’ll handle it directly.</div>
<div class=""><br class="">
</div>
<div class="">So, for me it is now on to end-user documentation.
As a reminder, that is in google docs and everyone is welcome to
join in and help. The link to view/comment on the document is
here:</div>
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding:
0px;" class="">
<div class=""><a href="https://docs.google.com/document/d/16JrXR7rybp-18DrEoeh1rg6GqQT_jVBvhaXh2oEWRHw/edit?usp=sharing" class="" moz-do-not-send="true">https://docs.google.com/document/d/16JrXR7rybp-18DrEoeh1rg6GqQT_jVBvhaXh2oEWRHw/edit?usp=sharing</a></div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">If anyone wants to help directly edit/author some of
it, let me know your eMail address and I’ll send an invite with
editing privileges.</div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark.</div>
<div class=""><br class="">
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre wrap="" class="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br class="">
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</div>
_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br class=""></div></blockquote></div><br class=""></div></body></html>