[Ovmsdev] Things left to do, before production

[Michael Balzer]

First version of the OTA web UI is in the hub.

Everybody please test & give me feedback, this is one of the more important functions for our first users.

Don't forget to force a browser cache reload, assets have changed.

I don't know yet if we can get the "power down modem" function to work, if not I'll replace it by a warning and info to reboot without modem enabled.

Regards,
Michael


Am 16.03.2018 um 02:22 schrieb Mark Webb-Johnson:
>
> 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.
>
> Most likely, the first thing users will have to do will be to update firmware anyway :-)
>
> Regards, Mark.
>
>> On 16 Mar 2018, at 5:24 AM, Michael Balzer <dexter at expeedo.de <mailto:dexter at expeedo.de>> wrote:
>>
>> Mark,
>>
>> 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.
>>
>> 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.
>>
>> I'll concentrate on implementing the workaround first, can try to solve this later on.
>>
>> I'll also add your latest feature extensions (i.e. APCLIENT mode & DNS server) to the config forms.
>>
>> Regards,
>> Michael
>>
>>
>> Am 15.03.2018 um 09:06 schrieb Mark Webb-Johnson:
>>>
>>> All components have arrived, and final assembly is happening now. Next week will be firmware flashing, QC, and then packaging.
>>>
>>> Label looks like this:
>>>
>>>     <SerialNumberLabel.png>
>>>
>>>
>>> Last things to do, with the goal of making this as easy as possible for the first guinea pig end users…
>>>
>>>  1. 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.
>>>
>>>  2. Module Password (via web interface). I’ve asked Michael to handle this, if he has time.
>>>
>>>  3. Tidy up of ‘secure’ mode. I’ve asked Steve to handle this.
>>>
>>>  4. 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).
>>>
>>>  5. Deadline for the above is this Sunday (18th March).
>>>
>>>  6. 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.
>>>
>>>
>>> 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.
>>>
>>> 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.
>>>
>>> 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:
>>>
>>>     https://docs.google.com/document/d/16JrXR7rybp-18DrEoeh1rg6GqQT_jVBvhaXh2oEWRHw/edit?usp=sharing
>>>
>>>
>>> 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.
>>>
>>> Regards, Mark.
>>>
>>>
>>>
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>
>> -- 
>> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
>> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk>
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180317/33f19e85/attachment.htm>