Hi John,

So EN 55035 (CISPR 35) may not filter through to the OJ Harmonised list until 
end of 2019?

Up until that point, it will be a combination of EN 55032 and either EN 55024, 
55020 or 55103-2?

Thanks,

Regards
Rob.


From: John Woodgate [mailto:jmw1...@btinternet.com]
Sent: 19 May 2016 13:16
To: Robert Dunkerley; EMC-PSTC@LISTSERV.IEEE.ORG
Subject: RE: [PSES] EN 55035 / CISPR 35

It is most unlikely that 55035 will be brought into mandatory effect without at 
least 3 years transition. It appears that the CISPR FDIS is forecast for 
October 2016, and CENELEC will for sure need time to process it into an EN.

With best wishes DESIGN IT IN! OOO – Own Opinions Only
www.jmwa.demon.co.uk<http://www.jmwa.demon.co.uk/> J M Woodgate and Associates 
Rayleigh England

From: Robert Dunkerley [mailto:robert.dunker...@s-a-m.com]
Sent: Thursday, May 19, 2016 12:45 PM
To: EMC-PSTC@LISTSERV.IEEE.ORG<mailto:EMC-PSTC@LISTSERV.IEEE.ORG>
Subject: [PSES] EN 55035 / CISPR 35

Hi,

I’m trying to plan ahead for the new EMC Standards coming in next year, in 
particular EN 55032 and EN 55035.

With EN 55035 still in draft form, are we likely to see that become compulsory 
the same time EN 55032 does? (ie 5th March 2017?)

In addition, do we know what the Radiated Immunity test changes are likely to 
be on the final version of the draft? I’ve seen that there is a new requirement 
for spot frequencies at 1.8GHz, 2.6GHz, 3.5GHz and 5GHz @ 3V/m. However, I have 
also seen talk of a ‘Protection Distance’ which could increase this 3V/m up to 
30V/m.

Best regards,

Rob.


________________________________
This email has been scanned for email related threats and delivered safely by 
Mimecast.
For more information please visit http://www.mimecast.com
________________________________
-
----------------------------------------------------------------

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 
<emc-p...@ieee.org<mailto:emc-p...@ieee.org>>

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://www.ieee-pses.org/list.html (including how to 
unsubscribe)<http://www.ieee-pses.org/list.html>
List rules: http://www.ieee-pses.org/listrules.html

For help, send mail to the list administrators:
Scott Douglas <sdoug...@ieee.org<mailto:sdoug...@ieee.org>>
Mike Cantwell <mcantw...@ieee.org<mailto:mcantw...@ieee.org>>

For policy questions, send mail to:
Jim Bacher <j.bac...@ieee.org<mailto:j.bac...@ieee.org>>
David Heald <dhe...@gmail.com<mailto:dhe...@gmail.com>>
---------------------------------------------------------------------------------------
This email has been scanned for email related threats and delivered safely by 
Mimecast.
For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------


-
----------------------------------------------------------------
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 
<emc-p...@ieee.org>

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://www.ieee-pses.org/list.html (including how to unsubscribe)
List rules: http://www.ieee-pses.org/listrules.html

For help, send mail to the list administrators:
Scott Douglas <sdoug...@ieee.org>
Mike Cantwell <mcantw...@ieee.org>

For policy questions, send mail to:
Jim Bacher:  <j.bac...@ieee.org>
David Heald: <dhe...@gmail.com>

Reply via email to