Author Topic: Agilent U1272A - Data logging - Software installation.  (Read 27875 times)

0 Members and 1 Guest are viewing this topic.

Offline Kiriakos-GR

  • Super Contributor
  • ***
  • Banned!
  • Posts: 3525
  • Country: gr
  • Country: gr
  • User is banned.
    • Honda AX-1 rebuild
Re: Agilent U1272A - Data logging - Software installation.
« Reply #25 on: June 28, 2011, 03:56:06 am »
The data logger GUI is the half part of the story,
The other half is the unit it self.

And so I decided to benchmark:
1) The U1272A internal timer accuracy
2) The U1272A when the memory of it gets full.  (Took a picture)
2) The USB-IR cable speed
3) The battery consumption (by using rechargeable Ansmann AAA 1100mA).


I did mains voltage Auto - log 10.000 entries (Full memory use)
Interval every 5Sec = 14:28min.
The internal timer does a true clock work !!


And here goes my own example and how to.

1) I prepared the DMM for an Auto – log Interval every 5Sec.
2) I took a paper wrote on it the starting time    02:02 am  (hh/mm) 
3) And started immediately the DMM log function (The DMM was plugged to mains with home made cables with bananas at both ends)

The first value at the log was A00001

30 Minutes later the counter was at A00360 
60 Minutes later the counter was at A00720
120 Minutes later the counter was at A01440

At the end I got the A10000 ,  the DMM showed A-FULL on the screen ,  was still in the logging mode, and was measuring the voltage with out logging,
And it was waiting for me so to stop the logging mode.

At the GUI software I got as Min/Max voltage events the entries :
A05281 = 219.03V AC
A08609 = 228.13V AC

To calculate that and find the time, I follow this root.
Example:   A05281  = 5281 (log entry)  x 5 Sec (time interval)  =  26405 seconds  Now divide by 60 so to get the minutes = 440.08
and again divide by  60 so to get the hours  = 7:33 (Hours measured by the DMM)  +  my staring hour ( 02:02 am).
And the result is that on Sunday 26 June 2011 at 09:35 am I had the highest under voltage in my shop.

For the overvoltage entry, the same method.

A08609  =  8609 (log entry)  x 5 Sec (time interval)  =  43045 seconds =  717.4 minutes = 11.95 hh/mm =  12:35:06  hh/mm/ss  +  my staring hour ( 02:02 am).
And this does on Sunday 26 June 2011 at 14:37:06 pm I got the highest overvoltage. 

It is not that hard to deal with these calculations if you do start doing logs frequently.
But you will need to do it methodically by keeping notes, plus a pocket calculator.
I bet that the older in age electricians will found it as slightly complicate this task.
The younger’s will find it easy as a new toy.


About the USB-IR cable:
It needs 07:05 mm:ss to transfer the 10.000 entries at 19200 Baud rate.
And 13:06 mm:ss   to do the same at 9200 Baud rate.     
   



Software related observations: 
a) b) The data logger GUI at the “Memory tab” , will load the Auto – generated log at the lowest table, it is a predefined place for it.
b) At the Memory tab you can move the tables separator bar (tool bar), at a higher location by dragging it with your mouse,
and you can gain some extra space for the lowest table .
c) By loading the auto-log file, at the top bar of the active window, is the button named as “Shows”
With it you can hide unwanted columns of the log before you export it or print it.
I found a bug at the setting “Range” I got an pop-up warning and the software does not run the specific command,
all the other selections works nicely, I have all ready inform Agilent about it.
d)  Bellow the Auto data logging tools bar, there is some arrows that helps to see the values with accenting or descending order.
Just click on the arrow above the voltages, as many times you like.
Tip :  the order “ numbering of the entries”  gets messed up if you give priority to the voltages sorting,
And before you print or export the log, you should adjust the sorting by the entry numbering.
You can do that on the MS Excel too, but it’s a bit complex in there.

e) Interesting enough the software exports the Auto-Log files at the folder   C:\Program Files\Agilent\Agilent GUI Data Logger
It does not look to offer a choice for changing the folder. (Or I did not find it yet)


The battery consumption ( by using rechargeable Ansmann  AAA 1100mA ) :
I am still exploring this option, because it would be nice to use rechargeable batteries,
for long lasting data logging tasks. (As I did all ready)
I have all ready some results, but I will have to double check my findings,
before saying anything more about it.
My digital Ansmann battery tester with load, looks like a priceless tool for such research.
I can measure the battery condition, after its one task.  (Data logging – uploading – idle – back light usage)
   
My current impression is that Agilent did some good work, about the data logging,
but this is not my final word yet.
When I will complete my tests I would know how the “Auto data-logging” weights as function among the others.
In simple words, it was added on the U1272A for occasional use or as primary?     

Agilent will release an new version of the GUI Data logger in August..
 

Offline Kiriakos-GR

  • Super Contributor
  • ***
  • Banned!
  • Posts: 3525
  • Country: gr
  • Country: gr
  • User is banned.
    • Honda AX-1 rebuild
Re: Agilent U1272A - Data logging - Software installation.
« Reply #26 on: July 01, 2011, 01:09:01 am »
Oups ... A new version of the data logger GUI is out all ready ...  :)
I still run  1.2.0.1 ..

They just added support for the new small DMM U1230 series.

Just get it here ...  http://www.home.agilent.com/sec/editorial.jspx?cc=GR&lc=eng&ckey=878442&nid=-34618.956189&id=878442

I am going to test it too.  :)

Agilent GUI Data Logger 1.3.0.0 Release Notes
--------------------------------------------------------------------
1. Added support for U1230 series.
2. No Secondary display for U1230 series.
3. Fix decimal points error for certain ranges.
4. Disable the "Write Permission" for the properties tab.


Agilent GUI Data Logger 1.2.0.1 (Windows 7 - 32 bit support) Release Notes
-----------------------------------------------------------------------------
1. Update PL-2303 Driver Installer which support all OS (XP, Vista, Windows 7 - 32 bit)
2. Update Help File


 

Offline Kiriakos-GR

  • Super Contributor
  • ***
  • Banned!
  • Posts: 3525
  • Country: gr
  • Country: gr
  • User is banned.
    • Honda AX-1 rebuild
Re: Agilent U1272A - Data logging - Software installation.
« Reply #27 on: August 12, 2011, 04:02:24 pm »
A new version of the GUI is scheduled at September  15 ..

I got the info last night.

 
 

Offline Kiriakos-GR

  • Super Contributor
  • ***
  • Banned!
  • Posts: 3525
  • Country: gr
  • Country: gr
  • User is banned.
    • Honda AX-1 rebuild
Re: Agilent U1272A - Data logging - Software installation.
« Reply #28 on: September 09, 2011, 10:27:23 pm »
Hey Agilent, if I do not get the new version at 15 of September I will start screaming !! :P   
 

Offline Kiriakos-GR

  • Super Contributor
  • ***
  • Banned!
  • Posts: 3525
  • Country: gr
  • Country: gr
  • User is banned.
    • Honda AX-1 rebuild
Re: Agilent U1272A - Data logging - Software installation.
« Reply #29 on: October 17, 2011, 08:41:35 pm »
Finally a new version looks to be out ..

Agilent GUI Data Logger 1.5.0.0 Release Notes
----------------------------------------------
1. Added support for U1273 series.
2. Added Trigger Data Logging memory mode for U1270 series.
3. Added saving last window workspace when the software close.


Agilent GUI Data Logger 1.4.0.0 Release Notes
----------------------------------------------
1. Added support for U1240 series.


Agilent GUI Data Logger 1.3.0.0 Release Notes
----------------------------------------------
1. Added support for U1230 series.
2. No Secondary display for U1230 series.
3. Fix decimal points error for certain ranges.
4. Disable the "Write Permission" for the properties tab.

http://download.home.agilent.com/WC/Installer1.zip?authparam=1318880343_260e86d5fee6fc527ab682abc3b10838


 

Offline amahon

  • Contributor
  • Posts: 12
  • Country: nz
  • Country: nz
Re: Agilent U1272A - Data logging - Software installation.
« Reply #30 on: April 20, 2012, 08:14:05 am »
Just wondering if anyone has further info/links on the communications spec for the U1272?

I would like to write my own scripts to controlling and transferring data from the meter so wanted to round up any command lists, code examples etc.

Was also wondering if it is possible to query the meter at a rate faster than its minimum interval (1 sec, interval logging mode). The specs say the LCD is updating at 7 samples/sec.... so one might be able to get data more often if the interface can keep up.

Thanks
Andrew
 

Offline drjoe047

  • Newbie
  • Posts: 1
Re: Agilent U1272A - Data logging - Software installation.
« Reply #31 on: January 04, 2013, 04:26:32 pm »
I looked for a python version. didn't find one. wrote one. sharing it below. (note: it is brutal but anyone that can read python can at least have something to start)

Joe J.

import time
import serial

 ##If Agilent provides you with documentation, please let us know. I haven't asked for anything from them under the assumption that they wouldn't. I could be wrong and I'd be please if that were the case.
 ##
 ##You'll find that the meter supports a very small subset (understandable) of the SCPI (Standard Commands for Programmable Instruments) protocol. You can make a request to the Google Gods to find documentation on SCPI and amazingly it doesn't appear that you have to pay $10,000USD to have the privilege of reading them.
 ##
 ##Here's a minimal list of commands that the U1253A (Hey  Kiriakos, I got the model number correct this time!  ) meter supports:
 ##     *Query commands are post-fixed with a "?"
 ##     *For queries regarding the secondary display, append @2 to the command (e.g. CONF? @2)
 ##*IDN?                 - Identification
 ##SYST:BATT?        - Request batter status. Not sure what units are returned.
 ##CONF?                - Request confirguration (e.g. "VOLT:AC +5.00000000E+00,+1.00000000E-04")
 ##STAT?                - Request unit status. I have not decoded the meaning of the return value for this. (e.g. "000000I00302L00004001")
 ##FETC?                - Request current reading (and FETC? @2 returns current reading on secondary display)
 ##*RST                 - Meter reset
 ##SYST:VERS?        - Unknown, my meter returns 1990.0
 ##SYST:ERR?          - Unknown, probably returns the last error
 ##READ?                 - Request current reading. I don't believe that the @2 option works for this command.
 ##If your meter supports logging (manual or auto) then the following commands can be used:
 ##LOG:AUTO xx        - Request value of auto-log position xx
 ##LOG:HAND xx        - Request value of manual log position xx
 ##
 ##There are other configuration commands as well. Let me know if you want them.
 ##I haven't been able to spend a lot of time playing with the commands so I certainly can't provide comprehensive documentation especially w.r.t. the system and configuration commands.


def init_meter(com_port):
    global meter
    print('meter, starting open:')
    meter = serial.Serial(com_port-1, 9600, timeout=.1)
    time.sleep(1)
    print('meter,  done open')
    print(meter)
    print('meter,  reseting meter:')
    meter.write("RST\n")
    time.sleep(0.25)
    response = meter.read(100)
    print(response)
    print('meter,  identifying meter:')
    meter.write("*IDN?\n")
    time.sleep(0.25)
    response = meter.read(100)
    print(response)
    print('meter,  Battery:')
    meter.write("SYST:BATT?\n")
    time.sleep(0.25)
    response = meter.read(100)
    print(response)
    print('meter,  Config:')
    meter.write("CONF?\n")
    time.sleep(0.25)
    response = meter.read(100)
    print(response)
   
    return meter

def read_meter(second='no'):
    global meter
    if second != 'yes' :
 ##        print ('not in second')
        meter.write("FETC?\n")
    else :
 ##        print ('yes in second')
        meter.write("FETC? @2\n")

 ##    time.sleep(0.05)
    responsestr = meter.read(17) 
 ##    print ('>' + responsestr + '<', len(responsestr))
    response = float(responsestr)
    return response

def close_meter():
    global meter
    print('meter, starting close')
    print(meter)
    meter.close()
    print('meter, closed')
    return

if __name__=='__main__':
    init_meter(11)
    for i in range(100):
        primaryValue = read_meter()
        secondaryValue = read_meter(second='yes')
 ##        time.sleep(0.1)
        print('count:' , i, "{:10.4f}".format(primaryValue), "{:10.4f}".format(secondaryValue))
    close_meter()
   
 

Offline pdnyberg

  • Newbie
  • Posts: 3
  • Country: se
  • Country: se
Re: Agilent U1272A - Data logging - Software installation.
« Reply #32 on: January 14, 2013, 10:37:40 am »
Hi,
I've written a small utility for Agilent DMM. It works both with Windows and Linux.

http://sourceforge.net/projects/dmmutils/

The protocol is reverse engineered from the "Agilent GUI"-program. Drop me an email I you find it useful or need some help.

Regards
Daniel
« Last Edit: January 14, 2013, 11:14:03 am by pdnyberg »
 

Offline pdnyberg

  • Newbie
  • Posts: 3
  • Country: se
  • Country: se
Re: Agilent U1272A - Data logging - Software installation.
« Reply #33 on: January 14, 2013, 03:28:42 pm »
I just made a document describing what I know about the protocol. This is the result of the extensive reverse engineering I did when I wrote dmmutils. Look under "files" at the project page. It will be included in the dmmutils archive in the next release.

I hope you will find it useful.

/Daniel
 

Offline jnd

  • Contributor
  • Posts: 49
  • Country: cz
  • Country: cz
    • Personal stuff
Re: Agilent U1272A - Data logging - Software installation.
« Reply #34 on: January 15, 2013, 11:21:46 pm »
I just made a document describing what I know about the protocol. This is the result of the extensive reverse engineering I did when I wrote dmmutils. Look under "files" at the project page. It will be included in the dmmutils archive in the next release.

I hope you will find it useful.

/Daniel
I just started playing with our new U1232A at work, nice timing :D

Once I found out there is free Bluetooth module included I went to search how could I actually connect it to PC and found that the USB Bluetooth modules are very cheap on eBay at $1 with shipping included, so I grabbed three. This is actually the first time I get to work with any Bluetooth devices, I managed to set it up at home where I have Linux, then at work PC with Windows and the actual multimeter with the Agilent software. It's not that great, you can't even adjust the font size for the virtual display but I guess it work enough for logging.

However my problem is when I tried to get it working on Raspberry Pi with your project. The USB module works without problems after simple setup, then you get /dev/rfcomm0 serial port. I managed to talk to the meter successfully with manual input but I can't get your app working. It compiles fine, one problem was that you have fixed array of port names so it doesn't accept something like /dev/rfcomm0. I managed to fix that myself by replacing one name in the array. But then I got "unable to open comport" error. And I have no idea why it doesn't work, further browsing of your source didn't enlighten me, I'm not familiar with your way of serial port handling in C. Is there any way I can test more and see where exactly is the problem? Or if you can do something about it, perhaps try with the Bluetooth module if you have one?

This Raspberry board is basically just controlling one large LED matrix, currently showing clock and I'd like to add showing values from the multimeter and possibly also reading the value or having alert with text to speech software. I could go simply with some Python script but when you have this already done I thought I could use your app to try the communication and various parameters first.

I also have question for the logging, I assume there is no option to set the meter for automatically sending the values, each must be requested separately? If so, how often can you ask, is it the same as the LCD update rate?
Wannabe volt-nut, slowly hunting solid meters with low budget.
 

Offline pdnyberg

  • Newbie
  • Posts: 3
  • Country: se
  • Country: se
Re: Agilent U1272A - Data logging - Software installation.
« Reply #35 on: January 17, 2013, 04:03:07 pm »
I do not have the bluetooth module myself, but I will try my best to help you.

Can you change line 116 in rs232.c from:
Cport[comport_number] = open(comports[comport_number], O_RDWR | O_NOCTTY | O_NDELAY);
to (eg. rfcomm0 hard coded into the code)
 Cport[comport_number] = open("/dev/rfcomm0", O_RDWR | O_NOCTTY | O_NDELAY);
and compile it again.

You used the same user when you did the communication manually as when you tried with dmmutils, didn't you?

If it still doesn't work I will modify the code a bit to print more debugging info. In that case my suggestion is that we continue either by mail or as a ticket at the sourceforge page to avoid getting to much of topic of this thread.

Another thing to try out is to make symlink to the port as described on:
http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=107183

I cannot give you a good answer to the last question about logging. I know that for my DMM U1252A, there is an option in the setup menu which does what you want. Its "Print mode". Check page 93, section 4 in Agilent document U1251-90003. I can't find it in the documentation for U1232, so I suppose its not there. The best thing you can do is probably to use dmmutils with the -q option and put it into a script and see how long time it takes do do, say 100 measurements. Try to use the highest baud rate as possible.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf