Hi John,

I think, if the fuse may be replaced by the end user (according to the 
equipment's instruction), then it may be UL listed like other components that 
may be replaced or connected to the equipment by the end user (e.g. cord sets).

Kind regards,

Bernd

Von: John Allen <jral...@productsafetyinc.com>
Gesendet: Montag, 11. Mai 2020 20:19
An: EMC-PSTC@LISTSERV.IEEE.ORG
Betreff: [PSES] UL Listed Fuse vs Recognized

Hi,

I hope everyone is good, healthy and being safe.

Does anyone have an accurate explanation of how a fuse can be UL Listed vs UR?  
 A fuse cannot stand alone as with other UL Listed products.

UL categories are JDYX, JDYX2

Thank you and Be Safe,

John

-
----------------------------------------------------------------

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

________________________________


WILO SE
Nortkirchenstrasse 100, 44263 Dortmund
Amtsgericht Dortmund, HRB 21356
www.wilo.com

Vorstand/Executive Board:
Oliver Hermes (President & CEO), Dr. Patrick Niehr, Georg Weber, Mathias Weyers
Aufsichtsratsvorsitzender/Chairman of the Supervisory Board:
Prof. Dr. Norbert Wieselhuber

Dieses Dokument ist vertraulich zu behandeln. Die Weitergabe sowie 
Vervielfaeltigung, Verwertung und Mitteilung seines Inhalts ist nur mit unserer 
ausdruecklichen Genehmigung gestattet. Alle Rechte vorbehalten, insbesondere 
fuer den Fall der Schutzrechtsanmeldung.
This document has to be treated confidentially. Its contents are not to be 
passed on, duplicated, exploited or disclosed without our expressed permission. 
All rights reserved, especially the right to apply for protective rights.

Datenschutz ist uns wichtig! Daher gehen wir sorgsam mit Ihren Daten um. 
Näheres finden Sie in unseren 
Datenschutzhinweisen<https://wilo.com/de/de/Wilo-Deutschland/Datenschutzhinweise.html>.
 Sollten Sie keinen Kontakt mehr mit uns wünschen, wenden Sie sich bitte an 
datensch...@wilo.com<mailto:datensch...@wilo.com>.
Data Protection is important to us! Therefore we handle your data carefully. 
Please find the details in our Note on Data 
Protection<https://wilo.com/de/de/Note-on-data-protection.html>. If you do not 
wish to stay in touch with us anymore, please write to 
data-priv...@wilo.com<mailto:data-priv...@wilo.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