[Ovmsdev] Production batch 2 and onwards

[Michael Balzer]

FYI: I'm getting more reports of modules being stopped / sent back by german customs offices now. None crushed up to now AFAIK.

Problem is, with the current module looking like a commercial product, customs officers no longer accept the hobbyist / development board declaration, they now
require a CE label when checking the package contents.

Regards,
Michael


Am 02.05.2018 um 13:40 schrieb Mark Webb-Johnson:
> Michael,
>
>> 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?
>
> 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).
>
> 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.
>
> Financially, once the money for the first batch comes in fully, we can afford it out of project funds.
>
>> 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.
>
> 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.
>
>> We should replace the serial number process by the factory defaults (wifi AP "OVMS / OVMSinit", no shell password).
>
> 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.
>
> Regards, Mark.
>
>> On 2 May 2018, at 5:00 PM, Michael Balzer <dexter at expeedo.de <mailto:dexter at expeedo.de>> wrote:
>>
>> Mark,
>>
>> thanks for the update and your monetary support.
>>
>> 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?
>>
>> 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.
>>
>> We should replace the serial number process by the factory defaults (wifi AP "OVMS / OVMSinit", no shell password).
>>
>> Regards,
>> Michael
>>
>>
>> Am 02.05.2018 um 08:24 schrieb Mark Webb-Johnson:
>>>
>>> FYI
>>>
>>> The order for production batch #2 has just been placed:
>>>
>>>   * 50x US kits (module + US 3G modem + Hologram sim)
>>>   * 150x EU kits (module + EU 3G modem + Hologram sim)
>>>   * 20x modules only (board + case, but no modem)
>>>   * 5x EU 3G modems (incl. Hologram sim)
>>>   * 5x US 3G modems (incl. Hologram sim)
>>>
>>>
>>> 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.
>>>
>>> Availability at Fasttech perhaps in about 3 weeks time. Our deadline for firmware is about 10 days.
>>>
>>> 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.
>>>
>>> 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.
>>>
>>> So long as this certification process doesn’t drag on, we should be able to keep OVMS v3 in stock and available from now.
>>>
>>> Regards, Mark.
>>>
>>>
>>>
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.openvehicles.com
>>> http://lists.openvehicles.com/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.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/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/20180829/df53a4d6/attachment-0001.html>