Randy, I will continue to look for my adapter. I haven't used it for quite a while.
I have seen similar issues and swapped cables, moved the adapter to the other meter, etc... One of my cables was bad from one side of the connector to the other (on the same end of the cable) and caused me lots of wasted time. Weird reading errors were happening. Would you email me Martin's code so I can test it here and I will see if anything can be done to replicate your issue. Todd On Sat, Dec 30, 2017 at 6:42 PM, Randy Evans <randyevans2...@gmail.com> wrote: > Todd, > > I tried adding the line but it made no difference. > > Randy > > On Sat, Dec 30, 2017 at 12:19 PM, Randy Evans <randyevans2...@gmail.com> > wrote: > > > Todd, > > > > Does it matter where I put the line in the Init_Device procedure? > > > > > > procedure Init_Device; > > begin; > > EZGPIB_BusWriteData(gpib_address,GET_ID); // Get ID of > meter > > if EZGPIB_BusWaitForData(gpib_address,meter_id,Timeout) then > > EZGPIB_ScreenWriteLn(meter_id); > > > > EZGPIB_BusWriteData(gpib_address,TRIGGER_SOURCE); // Hold trigger > > until meter can be setup > > EZGPIB_BusWriteData(gpib_address,'INBUF ON'); > > EZGPIB_BusWriteData(gpib_address,AUTO_ZERO); > > EZGPIB_BusWriteData(gpib_address,OUTPUT_FORMAT); > > end; > > > > > > Randy > > > > On Sat, Dec 30, 2017 at 11:20 AM, Todd Micallef <tmical...@gmail.com> > > wrote: > > > >> Randy, > >> > >> I am the person that wrote that EzGPIB script. It was my first before I > >> moved on to Python and I have only written a couple for the different > >> meters I have on hand. Version 1.01 is the most current version I have > for > >> the 3458A. > >> I see that I should have added at least one more command to the meter > >> initialization. The additional init command is used in the scripts on > >> xDevs. > >> > >> Add the following line in the Init_Device procedure > >> EZGPIB_BusWriteData(gpib_address,'END ALWAYS'); > >> > >> This tells the meter to send an EOI on every read. > >> > >> I am looking for one of my Prologix adapters or I would test this. When > I > >> find it, I will also test it. I want to make sure there are no further > >> issues. > >> Also, do both meters run the same firmware versions? I wonder if the HP > >> meter is using a much older version. > >> > >> Todd > >> > >> On Sat, Dec 30, 2017 at 10:42 AM, Randy Evans <randyevans2...@gmail.com > > > >> wrote: > >> > >> > Todd, > >> > > >> > I have version 1.01. Yes, please e-mail me your modified version. > >> Maybe it > >> > will help. > >> > > >> > Thanks, > >> > > >> > Randy > >> > > >> > On Sat, Dec 30, 2017 at 4:24 AM, Todd Micallef <tmical...@gmail.com> > >> > wrote: > >> > > >> > > Randy, > >> > > > >> > > Is there a version number at the top of the file? I had two versions > >> > (1.00 > >> > > and 1.01). I can't remember all that changed between the two since > it > >> has > >> > > been a while but I did find an additional timeout code that limited > >> the > >> > > wait time for reading data to 1 minute. I am guessing I had a > problem > >> > with > >> > > mine and added it. > >> > > > >> > > I can email it to you if you want to try it. If it works for you, I > >> will > >> > > have Illya update it on xDevs. > >> > > > >> > > Todd > >> > > > >> > > On Sat, Dec 30, 2017 at 12:39 AM, Randy Evans < > >> randyevans2...@gmail.com> > >> > > wrote: > >> > > > >> > > > I am still unable to get my HP-3458A to work with the xdevs > program > >> > > > "HP3458A_Measure_DMM_Noise.488" (https://xdevs.com/article/dmm > >> _noise/ > >> > ). > >> > > > It > >> > > > works fine with my Agilent 3458A and with a friend's HP-3458A and > >> his > >> > > > Agilent 3458A using the EZGPIB program. The SW versions are > >> identical > >> > > with > >> > > > my friend's DMMs, the HP units are (8.2) and with the Agilent > units > >> are > >> > > > (9.2). However, both of my units work fine with the KE5FX GPIB > >> Toolkit > >> > > > HP3458.EXE program to download the NVRAM CAL data. This would > seem > >> to > >> > > > indicate that my HP-3458 GPIB works at least partially. > >> > > > > >> > > > Does anyone have a EZGPIB program that I could try to run (that is > >> > > > different from the Xdev program)? It would be nice to see if I > >> could > >> > get > >> > > > something to work other than the HP3458.EXE program. Or if any > one > >> has > >> > > > some ideas on what to look for. > >> > > > > >> > > > Thanks, > >> > > > > >> > > > Randy Evans > >> > > > > >> > > > On Tue, Dec 26, 2017 at 7:24 PM, Randy Evans < > >> randyevans2...@gmail.com > >> > > > >> > > > wrote: > >> > > > > >> > > > > I am hoping some of you experts might be able to assist with a > >> > strange > >> > > > > problem i am having trying to make automated measurements using > >> > EZGPIB > >> > > > with > >> > > > > an Agilent and an HP 3458A. I have a program given to me by > >> Martin > >> > > > > Reynolds, which is a variant on the Xdevs noise measurement > >> program. > >> > > > > Martin's program continuously reads the voltage measurements > >> > > sequentially > >> > > > > from the two meters and then stores then in a measurements file, > >> > along > >> > > > with > >> > > > > the temperature measurements from both meters. The program > works > >> > fine > >> > > on > >> > > > > his Agilent and HP 3458As. > >> > > > > > >> > > > > On my two 3458As, it takes the temperature measurements just > fine > >> but > >> > > > only > >> > > > > takes a voltage measurement from the Agilent unit. The HP unit > >> will > >> > > not > >> > > > > make any voltage measurements although I can see both the 3458As > >> in > >> > > talk > >> > > > > states and, of course, it does sent the temperature > measurements. > >> > > > However, > >> > > > > if I turn the HP unit off and then on again, the HP will start > to > >> > take > >> > > > > voltage and temperature measurements and send them to the PC. > >> > > > > > >> > > > > Any ideas on what might be causing the strange behavior? > >> > > > > > >> > > > > Thanks, > >> > > > > > >> > > > > Randy Evans > >> > > > > > >> > > > _______________________________________________ > >> > > > volt-nuts mailing list -- volt-nuts@febo.com > >> > > > To unsubscribe, go to https://www.febo.com/cgi-bin/ > >> > > > mailman/listinfo/volt-nuts > >> > > > and follow the instructions there. > >> > > > > >> > > _______________________________________________ > >> > > volt-nuts mailing list -- volt-nuts@febo.com > >> > > To unsubscribe, go to https://www.febo.com/cgi-bin/ > >> > > mailman/listinfo/volt-nuts > >> > > and follow the instructions there. > >> > > > >> > _______________________________________________ > >> > volt-nuts mailing list -- volt-nuts@febo.com > >> > To unsubscribe, go to https://www.febo.com/cgi-bin/ > >> > mailman/listinfo/volt-nuts > >> > and follow the instructions there. > >> > > >> _______________________________________________ > >> volt-nuts mailing list -- volt-nuts@febo.com > >> To unsubscribe, go to https://www.febo.com/cgi-bin/m > >> ailman/listinfo/volt-nuts > >> and follow the instructions there. > >> > > > > > _______________________________________________ > volt-nuts mailing list -- volt-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/ > mailman/listinfo/volt-nuts > and follow the instructions there. > _______________________________________________ volt-nuts mailing list -- volt-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/volt-nuts and follow the instructions there.
