In addition to 5000m and 2000m we have also approved products up to 2500m, 3048m and 4000m.
Best regards, Bostjan Glavic SIQ On 6. sep. 2013, at 03:12, "IBM Ken" <ibm...@gmail.com<mailto:ibm...@gmail.com>> wrote: I've used a number of different altitudes beyond the 2000m default (scaling based on IEC 60664 as mentioned in annex G of '950). You may know this, but I just want to point out- your product does not have to *function* at 5000m, it can shut down for OT or whatever, they just seem to want the spacings set for 5000m. You also have the option of labelling with the "no mountains" graphic if you can't get 5000m spacings. On Thu, Sep 5, 2013 at 4:49 PM, Mark Gandler <markgand...@hotmail.com<mailto:markgand...@hotmail.com>> wrote: Hi there, Wanted to get some simple data point based on your experiences across different companies and industries: what are an altitude levels been used while evaluating 60950-1 isolation requirements? By default you get 2000m, how many of you used different levels? This is driven by 5000m CCC requirement and some critical power supply component limitations. If there will be enough responses, I’ll send back statistical breakdown. Thank you for reading, Mark - ---------------------------------------------------------------- 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://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 <emcp...@radiusnorth.net<mailto:emcp...@radiusnorth.net>> 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 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://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 <emcp...@radiusnorth.net<mailto:emcp...@radiusnorth.net>> 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 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://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 <emcp...@radiusnorth.net> Mike Cantwell <mcantw...@ieee.org> For policy questions, send mail to: Jim Bacher: <j.bac...@ieee.org> David Heald: <dhe...@gmail.com>