Think that CISPR32 is supposed to address very short-term stuff, but since is not recurring and periodic, would a few hundred mSec affect test limits?
So what is the SAR for 2.5GHz stuff? Is it an integral effect for exposure time? Is safety issue per new LVD (2014/35/EU), and would need a good rationale per required risk analysis. Bet that most of you EMC engineers would have this figured out in a few hours. PhD astronomers and rocket scientists, 17 years - meh. Brian From: Doug Powell [mailto:[email protected]] Sent: Thursday, May 14, 2015 3:18 PM To: [email protected] Subject: [PSES] Interference Caused by Microwave Oven All, Today Interference Technology published on their website, "Astronomers Discover 17-Year Interference Caused by Microwave Oven" Link: http://www.interferencetechnology.com/astronomers-discover-17-year-interference-caused-by-microwave-oven/?utm_source=itnewsletter&utm_medium=email&utm_campaign=20150514 My question is this. If the RF generated inside the oven does not stop prior to the opening of the RF seal on the door, which testing is responsible to identify this problem, EMC or the Safety testing? Thanks, Doug Douglas E Powell http://www.linkedin.com/in/dougp01 - ---------------------------------------------------------------- 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://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 <[email protected]> Mike Cantwell <[email protected]> For policy questions, send mail to: Jim Bacher: <[email protected]> David Heald: <[email protected]>
