Thanks Peter. I looked at this standard, but ignored because no EN and noted
that the WG had it marked 'on hold'. Recent status known?

I want single grand unified product safety and EMC standards for everything.
Both less than 20 pages. Using very large font. And mostly pictures.

Brian

-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of Peter
Tarver
Sent: Friday, April 20, 2012 3:59 PM
To: [email protected]
Subject: RE: [PSES] safety standard for PV-related stuff

Combiner boxes are in the scope of 62109-4, but this is a potential new
work item on TC82's docket.

For now, the guts would be subjected to whatever the guts normally would
if the guts were components used elsewhere.

Regards,

Peter L. Tarver

> From: Brian Oconnell> Sent: Friday, April 20, 2012 14:30
>
> IEC site says that TC22 has voted yes on IEC62477-1 Nov
> 2011, but still
> waiting. EN62103 has scope that I need, but not
> published in LVD. And the
> usual suspects of 61730, 61646, 61215, 50521, and 50548
> not correct for my
> stuff.
>
> EU equivalilant of UL1741/UL1012 for stuff in combiner
> box that is connected
> to a PV string?
>
> thanks,
> Brian

-
----------------------------------------------------------------
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]>

Reply via email to