In message <[email protected]>, dated Mon, 26
Nov 2012, Mark Gandler <[email protected]> writes:
Bill,being struggling with the same question. 1.8.1 goes in effect only
on 1.1.2015, but current 1.7.1 should be used with an adaptivity
requirement from 1.8.1.It is very unusual circumstances where the
requirement is pretty much "dropped" out of nowhere and looks like goes
in effect immediately.Our test lab posted this question to an alleged
author of the below note and his answer was "yes, it applies and must
be tested". not sure how it all makes sense to etsi authors and RTTE
committee. what about currently shipping equipment which been evaluated
to 1.7.1 version, but before adaptivity note been posted?
It is indeed very unusual for a provision to come into effect without a
transition period, and is normally not allowed. If it is allowed, there
must be a safety or other over-riding issue to justify it and it must be
explained publicly (at least according to many Directives).
Were manufacturer experts on the relevant ETSI standards committee
unaware of this unusual development?
--
OOO - Own Opinions Only. See www.jmwa.demon.co.uk
The longer it takes to make a point, the more obtuse it proves to be.
John Woodgate, J M Woodgate and Associates, Rayleigh, Essex UK
-
----------------------------------------------------------------
This message is from the IEEE Product Safety Engineering Society emc-pstc discussion
list. To post a message to the list, send your e-mail to <[email protected]>
All emc-pstc postings are archived and searchable on the web at:
http://www.ieee-pses.org/emc-pstc.html
Attachments are not permitted but the IEEE PSES Online Communities site at
http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used
formats), large files, etc.
Website: http://www.ieee-pses.org/
Instructions: http://listserv.ieee.org/request/user-guide.html
List rules: http://www.ieee-pses.org/listrules.html
For help, send mail to the list administrators:
Scott Douglas <[email protected]>
Mike Cantwell <[email protected]>
For policy questions, send mail to:
Jim Bacher: <[email protected]>
David Heald: <[email protected]>
