I agree with Stephen, except that I would exert a great deal of my energy to
have this corrected by the power supply manufacturer, -- and fast!   The
manufacturer  is in danger of loosing your business unless this gets
resolved.  
 
Try to resolve this in parallel, assuming it is the same NRTL:  address this
issue with your NRTL certifying engineer and at the same time have the
manufacturer work the issue with their cert engineer.   Request that both
NRTL engineers talk to each other.   When the issue is resolved, your cert
engineer should be able to give you a completed report a day or so later
after the manufacturer gets his report corrected.   The assumption is that
both NRTL engineers proceed with their work per the agreement, and the first
formal approval immediately toggles your formal approval.   This approach
worked for me several times.
 
If it is not the same NRTL,  having both cert engineers talking to each
other will not work.   You are now working serially, and this will take
time.   However, I still think that this will be faster rather than going to
another NRTL entirely and starting from scratch, or using another power
supply in your product (probably will take even longer!).   Another
option,-- you might want to consider taking your product to the same NRTL as
the power supply manufacturer and forcing them to correct this issue.  

Tania Grant,  [email protected] 
Lucent Technologies, Switching Solutions Group 
Intelligent Network and Messaging Solutions 

 
-----Original Message-----
From: Stephen Phillips [mailto:[email protected]]
Sent: Thursday, October 19, 2000 10:07 AM
To: Doug; EMC-PSTC Discussion Group
Subject: Re: Got a beef with an NRTL ... 


  Doug,  

  You don't say for certain, but can we assume 
that the fact that the NTRL even knew of the 
internal fuse's limitations - that you and the ps 
company used the very same NRTL, including 
the same office?  

  Or is this a case of one NRTL not accepting 
the 'interpretation' of another?  

  Also, are you sure there are no CofA's on this 
supply?  I require a copy of the UL and CB 
reports for every power supply, in an effort to 
avoid issues approaching this.  

  It sounds very scary.  I'd be pretty darn mad 
too!  I'd direct some of that energy at the ps 
manufacturer as well as the NRTL.  

  Best regards, 
  Stephen  

At 12:42 PM 10/19/00 Thursday , Doug wrote:
>
>I'm just about ready to escalate this issue. 
>
>Issue:  Major NRTL has recognized a DC-DC power supply. 
>        Said ps is being used within the confines of 
>        it's stated purpose, input power, output power, 
>        temps, etc ... 
>
>        Said product is submitted to NRTL for what appeared 
>        to be a walk through.  Oh no, Mr. McKean.  You can't 
>        use THAT power supply as intended.  Input fuse of 
>        power supply (that is the fuse INSIDE the power that 
>        is out of our hands) is an AC fuse.  It should be a 
>        DC fuse.  (From the documentation from the ps mfr, 
>        the approval was done with the aC rated fuse.) 
>
>        You have to either: 
>
>        1. have the ps mfr change the input fuse. 
>
>        or 
>
>        2. drop an in-line fuse between the power inlet 
>           of the product and the input of the ps. 
>
>EXCUSE ME!?!  
>
>How the heck can a power supply mfr get NRTL approval on one 
>hand and, yet, when that power supply is used within it's 
>intended and stated purpose, get rejected? 
>
>Even bringing this to the attention of the test engineer 
>(who has approx over 10 years experience as a test eng) 
>it defaults to - "well, that's just because the OTHER 
>test engineer interpreted it that way ... " 
>
>I can understand and have been in those areas of 
>"interpretation" with NRTLs, but this one really ... 
>er ... surprises me. 
>    
>Yours truly and totally confused, Doug
>
>-------------------------------------------
>This message is from the IEEE EMC Society Product Safety
>Technical Committee emc-pstc discussion list.
>
>To cancel your subscription, send mail to:
>     [email protected]
>with the single line:
>     unsubscribe emc-pstc
>
>For help, send mail to the list administrators:
>     Jim Bacher:              [email protected]
>     Michael Garretson:        [email protected]
>
>For policy questions, send mail to:
>     Richard Nute:           [email protected]
>
>



-------------------------------------------
This message is from the IEEE EMC Society Product Safety
Technical Committee emc-pstc discussion list.

To cancel your subscription, send mail to:
     [email protected]
with the single line:
     unsubscribe emc-pstc

For help, send mail to the list administrators:
     Jim Bacher:              [email protected]
     Michael Garretson:        [email protected]

For policy questions, send mail to:
     Richard Nute:           [email protected]

Reply via email to