RE: NI LabVIEW for EMC

2006-11-20 Thread emc-p...@ieee.org
Horz, 12 Vert) in a little over an hour. If a lot of manual testing is required it of course would take longer. The Other Brian _ From: emc-p...@ieee.org [mailto:emc-p...@ieee.org] On Behalf Of Pearson, John Sent: Monday, November 20, 2006 4:47 AM To: ieee Subject: RE: NI LabVIEW for

RE: NI LabVIEW for EMC

2006-11-20 Thread emc-p...@ieee.org
.@ieee.org] On Behalf Of Kunde, Brian Sent: 17 November 2006 20:05 To: Bob Richards; Brian O'Connell; ieee Subject: RE: NI LabVIEW for EMC Bob, I totally agree with your insight especially source code control. And I would agree that writing software is not for every EE. But, as it has becom

RE: NI LabVIEW for EMC

2006-11-17 Thread emc-p...@ieee.org
more than one way of getting the job done with software. The other Brian _ From: emc-p...@ieee.org [mailto:emc-p...@ieee.org] On Behalf Of Bob Richards Sent: Friday, November 17, 2006 1:45 PM To: Brian O'Connell; ieee Subject: RE: NI LabVIEW for EMC Brian, See my response

RE: NI LabVIEW for EMC

2006-11-17 Thread emc-p...@ieee.org
+ C# (http://www.codeplex.com/IronPython). luck, Brian From: emc-p...@ieee.org [mailto:emc-p...@ieee.org]On Behalf Of Kunde, Brian Sent: Friday, November 17, 2006 9:31 AM To: lfresea...@aol.com; Grace Lin Cc: emc-p...@ieee.org Subject: RE: NI LabVIEW for EMC Grace, In my opinion, every lab can b

RE: NI LabVIEW for EMC

2006-11-17 Thread emc-p...@ieee.org
_ From: Bob Richards [mailto:b...@toprudder.com] Sent: Friday, November 17, 2006 10:45 AM To: Brian O'Connell; ieee Subject: RE: NI LabVIEW for EMC SNIP For anyone thinking of writing their own EMC application, you probably don't have any idea what you are about to

RE: NI LabVIEW for EMC

2006-11-17 Thread emc-p...@ieee.org
Brian, See my response below: Brian O'Connell wrote: Closing thoughts - my advice should be read with a caveat - I have a C.S. education, and was a test engineer in previous lives (so why the heck is this guy a product safety engineer ?), so developing s/w, using whatever environment or lan

RE: NI LabVIEW for EMC

2006-11-17 Thread emc-p...@ieee.org
Mertinooke [mailto:mertino...@skyskan.com] Sent: Friday, November 17, 2006 1:53 PM To: Kunde, Brian Cc: lfresea...@aol.com; Grace Lin; emc-p...@ieee.org Subject: Re: NI LabVIEW for EMC >When we have slow times in the lab our guys are working on software. In >the last 10 years, our lab is able

Re: NI LabVIEW for EMC

2006-11-17 Thread emc-p...@ieee.org
gt; correctly. Software is not replacing a qualified tech or engineer, it is > just speeding up the process and making it more repeatable (and less > boring). > > The other Brian > > > From: emc-p...@ieee.org [mailto:emc-p...@ieee.org] On Behalf Of Derek > Walton > Se

RE: NI LabVIEW for EMC

2006-11-17 Thread emc-p...@ieee.org
e process and making it more repeatable (and less boring). The other Brian From: emc-p...@ieee.org [mailto:emc-p...@ieee.org] On Behalf Of Derek Walton Sent: Friday, November 17, 2006 9:44 AM To: Grace Lin Cc: emc-p...@ieee.org Subject: Re: NI LabVIEW for EMC Hi Grace, to answer your q

RE: NI LabVIEW for EMC

2006-11-17 Thread emc-p...@ieee.org
Ms Lin and August List Members, (The approaching holidays seem to require a more formal appellation...) NI's LV is an very productive development environment for test engineering. It has good support from both the community of users and from NI. And where the instrument and bus I/O are directly s

Re: NI LabVIEW for EMC

2006-11-17 Thread emc-p...@ieee.org
Hi Grace, to answer your question, any control package can be used for EMC, I must have used a 1/2 dozen in the last 30 years. It all comes down to how much time you want to invest. The big crevasse that almost everyone falls into when they embark on their own software, is that they do not see how