<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Michael,<div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div text="#000000" bgcolor="#FFFFFF" class="">Regarding the CE/FCC certification, maybe we can raise some funds from the users interested in this, i.e. nearly all EU users. How much is it?<br class=""></div></blockquote><br class=""></div><div class="">Certification lab is suggesting to do CE-RED and FCC-ID. The direct certificate test and consultancy charge is about US$2,000 for CE-RED, and US$4,000 for FCC-ID. Modifications to our circuit and test modules will probably cost not much at all (few hundred US$). Not sure about the actual certification filing fees (but I am told not excessive, and maybe able to negotiate with test lab). Also not sure about the other parts of CE, like WEEE (and still waiting for confirmation on that).</div><div class=""><br class=""></div><div class="">Those prices are for a China lab doing it, and seem about the going rate. The testing process itself is 1 to 2 weeks (plus whatever time we need to make revisions in order to pass). Doing it in china speeds up those revision times to a matter of days.</div><div class=""><br class=""></div><div class="">Financially, once the money for the first batch comes in fully, we can afford it out of project funds.</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div text="#000000" bgcolor="#FFFFFF" class="">Regarding the firmware deadline, 10 days may be a bit short for the wifi rework and new setup wizard to get done and mature enough for rollout. The web UI now checks for all common mistakes users made in their initial setup (I hope I got all of them…). I'll see if I can add a "quick setup" page of the main configuration options.</div></blockquote></div><div class=""><br class=""></div><div class="">I think so too. For me, it depends on how well the wifi re-work I am doing goes. I should know that this week. I am trying to get it so that the module can be configured as AP + STA mode, and then either AP or STA brought up and down as necessary (including taking down the STA, doing a scan, then bringing it back up). But the ESP32 IDF library is not co-operating.</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div text="#000000" bgcolor="#FFFFFF" class="">We should replace the serial number process by the factory defaults (wifi AP "OVMS / OVMSinit", no shell password).</div></blockquote></div><div class=""><br class=""></div><div class="">Yes. I will update the production notes and deal with factory for that. Should be fine, and much simpler for the user. But, need to get the prompt for password configuration during initial setup very clear to the user, to avoid this becoming a major vulnerability.</div><div class=""><br class=""></div><div class="">Regards, Mark.</div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On 2 May 2018, at 5:00 PM, 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="">
thanks for the update and your monetary support.<br class="">
<br class="">
Regarding the CE/FCC certification, maybe we can raise some funds
from the users interested in this, i.e. nearly all EU users. How
much is it?<br class="">
<br class="">
Regarding the firmware deadline, 10 days may be a bit short for the
wifi rework and new setup wizard to get done and mature enough for
rollout. The web UI now checks for all common mistakes users made in
their initial setup (I hope I got all of them…). I'll see if I can
add a "quick setup" page of the main configuration options.<br class="">
<br class="">
We should replace the serial number process by the factory defaults
(wifi AP "OVMS / OVMSinit", no shell password).<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Am 02.05.2018 um 08:24 schrieb Mark
Webb-Johnson:<br class="">
</div>
<blockquote type="cite" cite="mid:F0948BC9-E56F-43F7-A68F-69FA7688CC35@webb-johnson.net" class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div class=""><br class="">
</div>
<div class="">FYI</div>
<div class=""><br class="">
</div>
<div class="">The order for production batch #2 has just been
placed:</div>
<div class=""><br class="">
</div>
<div class="">
<ul class="MailOutline">
<li class="">50x US kits (module + US 3G modem + Hologram sim)</li>
<li class="">150x EU kits (module + EU 3G modem + Hologram
sim)</li>
<li class="">20x modules only (board + case, but no modem)</li>
<li class="">5x EU 3G modems (incl. Hologram sim)</li>
<li class="">5x US 3G modems (incl. Hologram sim)</li>
</ul>
<div class=""><br class="">
</div>
</div>
<div class="">No change to specification and board layout from the
first production batch, except to re-iterate the points that
came in from feedback. We are arranging a foam box to ship the
modules in, with our logo on it, to avoid the issues with sticky
glue on those padded bags.</div>
<div class=""><br class="">
</div>
<div class="">Availability at Fasttech perhaps in about 3 weeks
time. Our deadline for firmware is about 10 days.</div>
<div class=""><br class="">
</div>
<div class="">This is a lot of $$$ upfront payment, and the
project is pretty tapped financially (I’ve had to pay for most
of this myself). Once the money from sales starts to come in,
we’ll be better off.</div>
<div class=""><br class="">
</div>
<div class="">I have quotes from certification labs for CE and FCC
certs, and it seems possible. They say we may have some small
changes to make (ESD primarily), but overall our design seems
fine and they are confident we can achieve the certification.
The process is expensive, but is just a one off upfront payment.
Current plan is to start with that process once we have this
production batch built and at Fasttech. We did consider doing
this before this production batch #2, but that would have just
delayed things several months.</div>
<div class=""><br class="">
</div>
<div class="">So long as this certification process doesn’t drag
on, we should be able to keep OVMS v3 in stock and available
from now.</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.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 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.openvehicles.com" class="">OvmsDev@lists.openvehicles.com</a><br class="">http://lists.openvehicles.com/mailman/listinfo/ovmsdev<br class=""></div></blockquote></div><br class=""></div></body></html>