<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="">I think this is turning out to be a rather confusing conversation, and I'm not clear who knows what about CE marking or what the exact planned products are. I have a little bit of experience in this area, but I am far from an expert.<div class=""><br class=""></div><div class="">It is important to understand the difference between a CE marking and CE testing.<br class=""><div class=""><br class=""></div><div class="">If you have a radio module that is part of a product supplied to an end user, the radio module itself does NOT need to be CE marked. However, as has already been said, the full product including the radio board should be CE tested and if compliant CE marked.</div><div class=""><br class=""></div><div class="">It may not even be possible to CE mark a radio module unless it meets the criteria for being a subassembly - i.e. the only assembly required is to "plug it in". This is often a slightly grey area, eg. whether a module has a 0.1" header fitted or just space for one to be fitted could make the difference! (I would imagine a large number of radio modules have been CE tested in some way, you just can't legally apply the CE mark to something that is not an end-user product.)</div><div class=""><br class=""></div><div class="">There is an obvious advantage in having a module that has passed some CE testing, either by it's manufacturer or as part of someone else's product, as you then know that the radio board is well designed and not likely to cause a problem in your product's CE testing.</div><div class=""><br class=""></div><div class="">[The CE mark is self-certified. There are unfortunately a huge number of products that have the CE mark but would not pass a certification test - some by accident, some through acts of omission, some due to deliberate fraud. Enforcement of CE marking in the UK is "highly variable" at best.]</div><div class=""><br class=""></div><div class=""><div class="">Joseph</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 8 Jun 2016, at 11:55, Bo Herrmannsen <<a href="mailto:bo.herrmannsen@gmail.com" class="">bo.herrmannsen@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">If it has a CE stamp it's CE certified<div class=""><br class=""></div><div class="">it cant have half CE stamp :-P</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">2016-06-08 12:52 GMT+02:00 Damon Hart-Davis <span dir="ltr" class=""><<a href="mailto:dhd@exnet.com" target="_blank" class="">dhd@exnet.com</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="">
> On 8 Jun 2016, at 11:45, Stuart Poulton <<a href="mailto:stuart@poulton.org.uk" class="">stuart@poulton.org.uk</a>> wrote:<br class="">
><br class="">
> Damon,<br class="">
><br class="">
> Don't see why RFM23B/69 won't cut it, it is after all what CurrentCost used in their hardware.<br class="">
<br class="">
My understanding is that that they are not properly/fully CE-certified for a start.<br class="">
<br class="">
It may be that we simply cannot find a CE-certified module that will work for us and that we have time to program, so it’s not a view I am holding lightly.<br class="">
<br class="">
Rgds<br class="">
<br class="">
Damon<br class="">
_______________________________________________<br class="">
OpenTRV-dev mailing list<br class="">
<a href="mailto:OpenTRV-dev@lists.opentrv.org.uk" class="">OpenTRV-dev@lists.opentrv.org.uk</a><br class="">
<a href="http://lists.opentrv.org.uk/listinfo/opentrv-dev" rel="noreferrer" target="_blank" class="">http://lists.opentrv.org.uk/listinfo/opentrv-dev</a><br class="">
</blockquote></div><br class=""></div>
_______________________________________________<br class="">OpenTRV-dev mailing list<br class=""><a href="mailto:OpenTRV-dev@lists.opentrv.org.uk" class="">OpenTRV-dev@lists.opentrv.org.uk</a><br class="">http://lists.opentrv.org.uk/listinfo/opentrv-dev<br class=""></div></blockquote></div><br class=""></div></div></div></body></html>