Understand that you want to avoid "full blown", but Tektronix (nee Voltech) 
makes power analyzers that will probably out-last your lab. Otherwise, as you 
have the code-monkey on your back, not that difficult to do using a CT or shunt 
and 6.5 digit logger such as the Agilent 34970 and about 100 lines of Python. 
The big problem here is channel-to-channel latency, which would affect accuracy 
of power measurements, unless you are willing to integrate the rms over many 
cycles. Then there are the DIY solutions - recommend at least a decent Cortex 
M4 class micro (my preference is the NXP MK20 series); and there are many 
canned design solutions for this stuff, where you would 'just' add your analog 
front-end.

If you have some of the later Tektronix or Agilent DSOs or MSOs, get a power or 
math module, then all you do is suck the data out of the scope (you will still 
need a CT or shunt).

If not Ethernet, then use GPIB. RS-232 is ok if differential pair.

Labview is a poor solution where long-term stability and maintenance is 
important.

If resultant data part of your formal TRF, be mindful that your solution can 
support the ISO17025 traceability stuff.

Brian


From: Kunde, Brian [mailto:brian_ku...@lecotc.com] 
Sent: Wednesday, September 12, 2018 8:25 AM
To: EMC-PSTC@LISTSERV.IEEE.ORG
Subject: [PSES] Recommondations for Test Equipment

Please send replies directly to me if this is a group violation.

In our Safety lab, we do input current tests. We currently use two handheld 
meters; one showing Voltage and the other Current via a current clamp.

We want to replace these two meters with a single piece of test equipment that 
will provide live data measurements via a PC Interface.   It would also be nice 
if it could provide power, power factor, and other such measurements.

We would like it to have a hardy interface, such as Ethernet or old fashion 
serial port (no USB).  We take these measurements in our EMC Lab where USB has 
a hard time surviving.  

Labview compatible would be nice. Since we write our own code, we will have to 
have access to the command set.  

Any recommendations?  We don’t really need the features and expense of a full 
blown power analyzer. Does anyone make something like this?

Thanks,
The Other Brian

-
----------------------------------------------------------------
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://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 <sdoug...@ieee.org>
Mike Cantwell <mcantw...@ieee.org>

For policy questions, send mail to:
Jim Bacher:  <j.bac...@ieee.org>
David Heald: <dhe...@gmail.com>

Reply via email to