I couldn't agree more. Automated EMC emissions test software gets you running, but a test engineer must be involved in the testing process. There is too much manual intervention during a test to allow automated software to "run with it". Cable or peripheral manipulation, EUT modes of operation, and other test altering factors, all require test engineer intervention. We also wrote our own testing scripts, since the software available does not generally allow that much flexibility. There is no such thing as fully automated emissions testing!
Bill From: [email protected] [mailto:[email protected]] On Behalf Of Mark Briggs Sent: Wednesday, December 12, 2007 12:35 PM To: Grace Lin Cc: [email protected] Subject: Re: Software for EMC Automation Grace - There are benefits and disadvantages to all of the packages you are looking at. The lab I work for decided to write our own software because of the diverse test equipment types from different manufacturers. This allowed us a lot of flexibility but it also incurred a longer development and implementation time. One comment on your goal: >My goal is to have a software fully control emission measurement (for >unintentional radiators) including generating a test report without an >engineer's additional intervention (except changing an antenna from >BiLog to Horn). You can avoid the engineers intervention during the preliminary scans (except, as stated, for switching antennas). However, part of the measurement process during the final stages includes manipulation of cables to maximize emissions - so during the maximization process for the signals you select during the preliminary scans an engineer needs to go in and move the cables around. Whichever software package you select, make sure it allows you to do this ! Good luck - Mark > > > >- ---------------------------------------------------------------- >This message is from the IEEE Product Safety Engineering Society >emc-pstc discussion list. Website: http://www.ieee-pses.org/ > >To post a message to the list, send your e-mail to [email protected] > >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] > >All emc-pstc postings are archived and searchable on the web at: > >http://www.ieeecommunities.org/emc-pstc - This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. Website: http://www.ieee-pses.org/ To post a message to the list, send your e-mail to [email protected] 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] All emc-pstc postings are archived and searchable on the web at: http://www.ieeecommunities.org/emc-pstc - This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. Website: http://www.ieee-pses.org/ To post a message to the list, send your e-mail to [email protected] 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] All emc-pstc postings are archived and searchable on the web at: http://www.ieeecommunities.org/emc-pstc
