Pilotage agilent 34401a

j'ai besoin de votre aide à propos le pilotage d'un multimétre agilent 34401a. je veux avoir le diagramme sous LabView sachant que je veux le piloter à travers le Rs232. merci

voila ce que l'on trouve dans le VI tree:
C'est un example de l'organistion des VI présents dans le driver. Pour un exemple concret voir la phrase en haut de l'image
Cordialement,
Simon D.
CLA | Certified LabVIEW Architect
CTA | Certified TestStand Architect

Similar Messages

Communication problem with agilent 34401a

Hi all,
I' m using Labview 8.2 and visa 4.2.
I 've connected my agilent 34401a and it is recognized, I see it in agilent connection expert and manage to communicate with it. (query *IDN?)
But I get a problem when I want to use the control_mode vi. (remote or local).
the error is displayed just after the Visa Read function (Vi below)
I don't understand why. I use the RS 232 connection and it is correctly configured in the devices manager.
Anyone can help me ?
Thanks,
Romain

Sorry,
I've forgotten the Vi.
Now it's OK
Thanks
Attachments:
control mode Vi.JPG ‏44 KB

When trying to work with Agilent 34401A multimeter (serial RS-232 connection), HP34401A Getting Started.vi gives always the message: "Error 1073807369 occurred at Old VISA Open ".

Baud rate and parity are set correctly, RS-232 cable is also connected correctly. My QuickBasic program has no problems to read and write to the Multimeter. It is obviously a software problem: the same error is persistent if I disconnect RS-232 cable.
I downloaded NI-VISA 2.6 for Windows 95/98/NT/ME/2000/XP frorm digital.ni.com and installed it. But it did not help.
Thank you in advance
Best regards
Alexei Soloviev

Hi Steve
I have problems with the 34401A and serial communication. Do you remember
where the error was in the code ?
Thanks
Klaus
wrote in message
news:[email protected]..
> Alexei,
> This may or may not help, I was tasked to do something similar
> recently and found an error in their driver. The GPIB VISA worked
> fine, but when I tried it on serial it played up. There was an errant
> carriage return (or CR/LF I can't remember). GPIB liked one and Serial
> liked the other. It always amuses me that we never have problems with
> Quickbasic!.
> If you want me to dig deeper give me a shout.
>
> Steve Watts
>
> On Thu, 24 Jan 2002 06:16:55 -0800 (PST), "Alexei V. Soloviev"
> wrote:
>
> >When trying
to work with Agilent 34401A multimeter (serial RS-232
> >connection), HP34401A Getting Started.vi gives always the message:
> >"Error 1073807369 occurred at Old VISA Open ".
> >
> >Baud rate and parity are set correctly, RS-232 cable is also connected
> >correctly. My QuickBasic program has no problems to read and write to
> >the Multimeter. It is obviously a software problem: the same error is
> >persistent if I disconnect RS-232 cable.
> > I downloaded NI-VISA 2.6 for Windows 95/98/NT/ME/2000/XP frorm
> > digital.ni.com and installed it. But it did not help.
> >Thank you in advance
> >Best regards
> >Alexei Soloviev
>

Agilent 34401A multimeter to PC with Labview driver via RS232

Hello!
I am trying to measure a voltage with Agilent 34401A multimeter connected to PC via RS232 cable. I installed the driver. When I am starting Read Single Measurement.vi. It gives me an error:
Error-1073807346 occured at Visa Open in Agilent 34401.lvlib: Initialize.vi->Agilent 34401 Read Single Measurement.vi
Possible reason(s):
Visa: (Hex 0xbFFF000E) The given session or object reference is invalid.
I would like to ask, how can I adjust my system to use RS23 with Agilent 34401A, if it is possible? If not, should I get GPIB card and cable?
Thank you!
Yulia.

LabVIEW already comes with a driver for the 34401 pre-installed, so I'm not sure I understand what you installed. The pre-installed driver is in the Instrument I/O >> Instrument Drivers >> Agilent 34401 functions palette.
As for the control that Dennis is referring to, it's the VISA control.
As for the VISA version, you should have received a set of driver CDs along with LabVIEW. That will have the minimum VISA version required. Don't remember off the top of my head which version it is. Probably something like 4.1.
Attachments:
visa.png ‏42 KB

Reading Max/Min/Avg with labview from agilent 34401a

Hi,
I'm using Labview drivers I've downloaded from the ni.com
website to control an agilent 34401A digital multimeter. All I'm trying to do right now is read
min/max/avg measurements after putting the device into a DC current mode,
configuring it for min/max measurements, and then pausing for a couple
seconds. The program successfully puts
the multimeter into the correct modes, but always returns 0 for each
measurement. Could you take a look at
the program to see if you find a simple mistake on my part? It should be
attached to this message. Thanks very
much.
Attachments:
AVGMAXMIN.vi ‏421 KB

I don't have the instrument or manual handy but is it possible that the instrument is waiting for a series of trigger to actually take a series of measurements. do you see the display changing? You can try setting a breakpoint at the min/max function and manually trigger the instrument to see if that makes a difference. Also, you don't need the sequence structure at all. Most of the time, sequence structures just serve to make your programs harder to read and debug. Use dataflow for controlling execution order like in the picture I've attached.
Message Edited by Dennis Knutson on 07-07-2006 02:51 PM
Attachments:
No Sequence Structure.JPG ‏31 KB

I need instraction manual of . Agilent 34401A

I have a used Agilent 34401A but I haven't any catalogue or instraction manual for work with this equipment .

Am sorry,
Its not 163 as i mentioned
even more than that. 242

Agilent 34401A TriggerMultiPoint

Agilent 34401Aから外部トリガを使って計測した値をLabview(ver8.6)に取り込もうとしています。
マルチメータとの通信は問題なくおこなわれており、単純な値の取得は行えています（http://zone.ni.com/devzone/cda/tut/p/id/9512）。
しかし、複数の計測値（外部トリガ、５１２カウント）の取り込み方が分かりません。
Measurement.FetchMultiPointのReadingArrayを使って取り込もうとしても、エラー(番号１)が出てきて読み取りができません。
正しい方法を教えていただけないでしょうか？
よろしくお願い申し上げます。
Solved!
Go to Solution.
Attachments:
agilent test 01.vi ‏15 KB

sorry, here is the question in English.
I am trying to get data from Agilent34401A to labview (8.6).
There is no problem with communication between a PC and the multimeter via RS-232.
Also, a simple voltage reading program is running without any error. (http://zone.ni.com/devzone/cda/tut/p/id/4505)
sending trigger setting command seems fine.
However, I don't know how to read (fetch) values which triggered by using multiple external triggers.
"Measurement.FetchMultiPoint" outputs "Err 1".
Could you please teach me how to trigger and get multiple data from Agilent 34401A?
Many thanks for using your time.

How to increase measuring speed of Agilent 34401A

The process of my program (written in Labview) is:
1) A control code is automatically generated by the program, and the code is sent to multiplexing circuit (the chips I used are ADG706) through digital port (USB6501 from NI) then a coresponding channel is selected. (for example code hex0000 selects 1st channle,0001 selects 2nd channel, and so on......)
2) Multimeter Agilent 34401A measures the current value of this channel, and send this value back to the computer for storage. After this, the program goes back to step 1) for next channel, and this program executes like this.
The functions mentioed above are all realized, and the program works well, but the problem is the speed is slow. It takes a little more than 1 second to measure one channel, totally I have 2048 channels (32 groups and 64 channels in each group, I used two layers of "for" cycles), and it takes about 32 minutes to finish measure all these 2048 channels, too slow, I'd like to reduce them to 10 minutes.
I tried to reduce the resolution to 4.5, turn off the autozero function of multimeter, but nothing happens, no change of the speed. Now every time the multimeter measures a channel, it makes a "click" sound, does it mean that every trigger the multimeter only takes one measurement? Is there anyway I can increase the measuring speed? Can I send the multimeter 64 control condes a time, and then let the multimeter takes 64 measurments in one trigger? Is it right? If so, how can I realized it? If I'm wrong about it, can you give me some solutions?
Thank you very much!

I don't have the manuals with me, but I do have a couple of these in my lab. There is an internal buffer where you can store (I think) 512 readings. You can use a digital output to trigger the DMM, and only transfer after every 512 readings (4 times) or perhaps one read per group as you mentioned. I suggest one read per trigger (you can do many more) since it is easier to synchronize with your channel changes. I believe the commands are INIT and FETCH?, check your manual. The two times I know the instrument "clicks" are changing functions and certain range changes. I suspect in your attempts to speed things up you are sending some config. commands each time. Configure it once initially and make certain you are only sending measurement related commands during the scan, any config. changes (even if you resend the current value) will likely cost you time.

Agilent 34401a error -410

Hi everyone,
I am having some problems adding communicating via GPIB with three instruments at the same time. The three instruments are an Oxford superconducting magnet power supply, an SRS lock-in amplifier, and an HP 34401A multimeter (used to read the voltage output of an analog lock-in). The problem is my code runs for a minute or two, and then the Agilent evidently gets bogged down before timing out and spitting out an error on the front panel (error -410 "query interrupted"). I'm running this on a pretty old system (Win 2K, Labview 6.1, Visa 2.6.0) which doesn't help with the speed issue.
I have been running my code for a couple years now without any major problems (occasionally the DMM will give an error if I abort the program at the wrong point) - all the problems I have had have been fixed by shutting down all the electronics and computer and restarting everything. The problem is now when I try to add the SRS lock-in to the code. I can run the code witht just the SRS lock-in and magnet supply, and I can run the code with as many as three DMM's being read over the GPIB with the magnet supply. The problem only happens when I have the SRS lock-in and the DMM being read at the same time. My suspicion (based on the error message) is that one of the instruments is leaving some data on the communication bus somewhere, and it is overloading the DMM, though I have unfortunately not yet found what exactly is causing the overload. Does anyone have any guesses of what to try? The help documentation in Labview is unfortunately even older than the VI I'm using (some of the inputs in the "Initialize instrument" VI are different from what is shown in the help menu). Does anyone know if it is easy/safe to communicate more directly with the DMM than using the VI's included in Labview? I ask because the SRS lock-in, for instance, is really easy to read - you just write one VISA command and the lock-in returns whatever the front-panel of the instrument is reading. You can of course create more complicated codes to read or set other instrument parameters, but all I need to do is read a simple DC voltage -10 to 10V with the DMM, so anything I can do to make the communication faster/simpler would be good since right now my data resolution is pretty limited due to the lag in all the communication steps. Also, does anyone know if there is anywhere online I can access newer help files on the Agilent/HP sub-VI's since the help files on my computer are inconsistent with the VI's? Thanks!

I would assume that you know that you cannot communicate to the instruments 'at the same time'. It would help to see some code to ensure you really are doing sequential reads and writes.
It would also seem your problems started when you added the SRS. There have been numerous posts about GPIB problems with that instrument. You can, of course skip the 34401 driver and use the SCPI commands but I'm not sure that would make any difference.
p.s. You complain about the speed of your old system but the limiting factor is almost always the instruments and the GPIB communication itself. A faster pc/newer PS/current LabVIEW would not change much if you kept the existing program.

Triggering and reading on two HP/Agilent 34401A DMMs at same time

Hi folks,
I'm VERY new to LabVIEW and need some help with a measurement. I'm using LV 8.2 with all equipment on GPIB. I have two 34401A multimeters, triggered externally using an HP 33120A function generator. I've downloaded the example vi's and drivers and everything works fine. My problem is with the speed of the triggering and the synchronization between the two multimeters on the same trigger. I've read the manual and for this multimeter, it claims it can be triggered and read over GPIB at 1kHz (display off, auto range off, delay= 0, 4.5 digits). I'm finding it is nowhere near this speed. The fastest I have successfully triggered and recorded the data was at 100 Hz, anything higher and it no longer stays in sync with the trigger (i.e. for 200 measurements at 100 Hz, I'm getting all 200 measurements, but over 3-5 seconds). The trigger speed is the first problem. The second problem is getting the two meters to take a reading at the same time. One meter always lags the other (or vice versa) by 1 to 3 readings. My goal is to continuously (for about 60 seconds) read both multimeters as fast as possible and at the same time (250-500 Hz would be fantastic) and write it to a file. Can anyone give me some advice on this? Is a software trigger the way to go? Is there some limitation with GPIB that it cannot read/write to two devices this fast?
Thanks!
P.S. I've been experimenting mostly with the example code provided by NI and a .vi posted in this forum thread (http://sine.ni.com/niforum/niforumforumDU=http://forums.ni.com/ni/board/messageboard.id=170&message....) hp34401a_-_testing.vi from Kunal. If anyone could share some other example vi's it would be very helpful!

Hi plasma420,
I should have read your post more carefully - was thinking it was a 1 sec acquisition, not 1 minute!
Getting your LabVIEW app to reliably respond to a measurement (detect/read) every 2 to 4 ms is going to be tough - especially if in a multi-tasking OS environment. On a 2GHz box running a normal Windows XP or 2K install, I suspect you could see an occasional "hiccup" even at 100Hz. A bit of searching the forum turned up this old-but-still-valuable (even entertaining) post related to improving determinism of DAQ applications on a PC.
Observation: The listed max measurement-rate of the 34401 (1000Hz) may assume the GPIB-bus is dedicated to one instrument - the requirement to read from two instruments sequentially, may necessarily increase time spent servicing each trigger - decreasing maximum theoretical throughput.
The first rule for "high-speed" multi-sample DAQ - especially under Windows - is to make it a hardware task instead of a software loop; the 34401 doesn't seem well suited here. I hate to suggest this, but... have you considered purchasing one of NIs multi-channel DAQ devices? With a $360 PCI 6010 + cable and break-out box, you could have one of the LabVIEW DAQ examples running in ~ 30 min. The 6010 was the cheapest 16-bit board I could find, ask your sales-rep for other alternatives if you go this route...
Cheers!
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)

HP 34401A and IVI help please

I am new to IVI so I am attempting to use the Teststand Example "IviStepTypes.seq" with a live 34401A with partial success. See NI I/O Trace messages below. The only change made to the sequence is a file global variable for the DMM name and the DMM Init step which I changed from Simulate=1 to Simulate=0. The DMM is set for RS232, 9600, 8 bit (no parity), SCPI. I am using the current ag34401 IVI driver from Agilent. Also, when I use the Soft Panel built into TestStand all messages starting with IVI_ work but ones starting with IVIDMM_ do not(error: function not supported). I am soooo confused. Could someone explain the errors? I get the feeling that there is a driver or newbie issue. Thanks!
Pat
1. IviDmm_InitWithOptions ("HPDMM", VI_FALSE, VI_FALSE, "Simulate=0,", 0x136960E4)
Process ID: 0x00001D4C         Thread ID: 0x00002668
Start Time: 09:20:58.778       Call Duration 00:00:01.121
Status: 0 (VI_SUCCESS)
2. IviDmm_GetAttributeViInt32 (HPDMM, NULL, SPECIFIC_DRIVER_CLASS_SPEC_MAJOR_VERSION, 3)
Process ID: 0x00001D4C         Thread ID: 0x000020E8
Start Time: 09:20:59.922       Call Duration 00:00:00.008
Status: 0 (VI_SUCCESS)
3. IviDmm_GetAttributeViString (HPDMM, NULL, GROUP_CAPABILITIES, 1000, "IviDmmBase,IviD...,IviDmmAutoZero")
Process ID: 0x00001D4C         Thread ID: 0x000020E8
Start Time: 09:20:59.930       Call Duration 00:00:00.007
Status: 0 (VI_SUCCESS)
> 4. IviDmm_ConfigureMeasurement (HPDMM, 1, 10, 0.0001)
> Process ID: 0x00001D4C         Thread ID: 0x000020E8
> Start Time: 09:20:59.937       Call Duration 00:00:02.019
> Status: 0x80000000
5. viWrite (hp34401a (0x11D08A10), "SENS:FUNC "VOLT".", 17, 17)
Process ID: 0x00001D4C         Thread ID: 0x0000227C
Start Time: 09:20:59.941       Call Duration 00:00:00.002
Status: 0 (VI_SUCCESS)
6. viWrite (hp34401a (0x11D08A10), "SENS:FUNC?.", 11, 11)
Process ID: 0x00001D4C         Thread ID: 0x0000227C
Start Time: 09:20:59.943       Call Duration 00:00:00.001
Status: 0 (VI_SUCCESS)
> 7. viRead (hp34401a (0x11D08A10), 0x1B9758C8, 4096, 0)
> Process ID: 0x00001D4C         Thread ID: 0x0000227C
> Start Time: 09:20:59.944       Call Duration 00:00:02.008
> Status: 0xBFFF0015 (VI_ERROR_TMO)
8. viStatusDesc (hp34401a (0x11D08A10), 0xBFFF0015, "Timeout expired...tion completed.")
Process ID: 0x00001D4C         Thread ID: 0x0000227C
Start Time: 09:21:01.952       Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)
> 9. IviDmm_CheckAttributeViInt32 (HPDMM, NULL, FUNCTION, 1)
> Process ID: 0x00001D4C         Thread ID: 0x000020E8
> Start Time: 09:21:01.956       Call Duration 00:00:00.003
> Status: 0xBFFA0011 (IVI_ERROR_FUNCTION_NOT_SUPPORTED)
> 10. IviDmm_CheckAttributeViReal64 (HPDMM, NULL, RANGE, 10)
> Process ID: 0x00001D4C         Thread ID: 0x000020E8
> Start Time: 09:21:01.959       Call Duration 00:00:00.003
> Status: 0xBFFA0011 (IVI_ERROR_FUNCTION_NOT_SUPPORTED)
> 11. IviDmm_CheckAttributeViReal64 (HPDMM, NULL, RESOLUTION_ABSOLUTE, 0.0001)
> Process ID: 0x00001D4C         Thread ID: 0x000020E8
> Start Time: 09:21:01.962       Call Duration 00:00:00.005
> Status: 0xBFFA0011 (IVI_ERROR_FUNCTION_NOT_SUPPORTED)

Another update. I could not get the demo to work with my DMM (tried 2 34401A's just to make sure) so after learning a bit more about IVI I decided to reinstall and start from scratch. NI IVI Compliance Package 4.5 and Agilent 34401A IVI driver were reinstalled.
Using the demo (IviStepTypes.seq) with no changes (running is simulate mode) the sequence gets part way then show this runtime error:
An error occurred calling 'RunStep' in 'ISubstep' of 'zNI TestStand Ivi Step Types'
An error occurred while executing the step.
Component Works IVI Control Error: The IVI Read operation failed for logical name 'SampleDmm'.
Details: [IVI Error Code: BFFA1190]
Source: TSIviStepTypes[Error Code: -31100]
I next skipped the soft panel step and the simulated sequence completes with no errors. So I tried real hardware. Note that it is on RS232 and communicates fine with the VISA test panel.
So I changed to live mode by makeing 2 changes. The initiate step Simulate option was changed from 1 to 0. The session in Ni-Max was changed to "Don't simulate". I then get the following error.
An error occurred calling 'RunStep' in 'ISubstep' of 'zNI TestStand Ivi Step Types'
An error occurred while executing the step.
Component Works IVI Control Error: The IVI Configure operation failed for logical name 'SampleDmm'.
Details: Invalid procedure call or argument
Source: TSIviStepTypes[Error Code: -30000]
Here's the NI I/O Trace.
I haven't been able to figure it out. I am assuming that the demo was tested with simulated and real hardware so I am expecting there is something wrong with Ni-Max settings or ...? Thanks for any help.
Pat

Agilent 34970A Switch/DMM

Hello!
I have a problem with Agilent's 34970A.
We have a testsystem consisting of Agilent 34401A DMM, Agilent 53131A
Counter and the troublesome Agilent 34970A.
I'm using VISA most of the time to control the 34970A, I say most of the
time because I have been forced to do the most strange programming to
make the program work. I have never noticed any problem with the other
instruments mentioned. But the 34970A can suddenly perform a reset,
switch itself off or just "freeze". Most of the time it is not possible
to turn it back on again without pulling the plug. I thought I had the
solution when I closed the VISA session in the middle of the program and
performed a reset on the instrument. I know it sounds strange but
somehow it wo
rked much better then. But now it seems like it needs more
to function properly. Have any of you guys ever heard of this kind of
problem or maybe you've got an idea on how to solve it?
Best regards
/Fredrik
Posted from ms-101.aerotechtelub.se [194.23.231.242]
via Mailgate.ORG Server - http://www.Mailgate.ORG

Hi,
Do you get the same problems with more than one 34970A. Because this sounds like a hardware problem with your 34970A. Have you tried using NI-Spy to monitor the bus traffic.
I've had no problems driving the 34970A just using the basic NI driver. The unit was part of a system for a life test application and therefore was required to take a series of reading over a period of time.
Regard
Ray.
Regards
Ray Farmer

SRQ Line no longer works on a PCI-GPIB

I have just upgraded a test pc, (tranfering hardware, reinstalling software etc) and now I have a fault with the PCI-GPIB card.
One of the instruments connected to the PC (HP34401 multimeter) uses the SRQ line to indicate when its ready to download its readings. The LV 5.0 code uses the standard legacy drivers from NI and these drivers use the 'wait for SRQ' function which are now timing out in the new setup.
The rest of the card functionality seems ok, and it tests ok. The LV code and cables are fine, because I can run the system with a USB-GPIB-B device.
Has anybody had the same problem?
Could it be a hardware specific driver problem?
The current config is:
1.7GHz PC with 512Mb Ram
PCI-GPIB
PCI-1200
LV 5.0.1
NI-
488.2 Version 2.0
VISA 2.6.1
NIDAQ 6.7
Thanks for your help
Tim

Hi Tim,
I found this knowledge base article which seems to address the same problem:
Why is the Agilent 34401A Driver's Getting Started VI Timing Out?
Hope this helps out.
DiegoF
National Instruments.

Visual C++ 6.0 usage with TestStand

Greetings! I would like to have a jump start in using Visual C++
6.0 with Test Stand. Any example of Visual C++ DLL and sequency
file which demonstrates the most basic function as below :
Example 1:
a. Test stand sequence calls a Visual C++ 6.0 DLL and pass in 2
parameters, say a variable type of float - "fInput" and another
variable type of integer - "nPower"
b. The Visual C++ 6.0 DLL calculates "fInput" to the power of "nPower" and pass back the results to Test Stand
c. Test Stand evaluate the result by comparing to the upper and lower limit
Example 2:
a. Test stand sequence calls a Visual C++ 6.0 DLL and pass in 1
parameter, says a variable type of string - "strMeasType" (value of
"AC" or "DC")
b. The Visual C++ 6.0 DLL reads the parameter and configure an
instrument, says Agilent 34401A, to measure either ACVolt or DCVolt
depending on "strMeasType" (using VISA)
c. Test Stand evaluate the result by comparing to the upper and lower limit
Thanks a lot!

Hi,
What you are trying to do is pretty basic TestStand functionality. There are several resources you can use to get information on howTestStand and C++ DLL's can interact.
For instance, you can check out http://ni.com/manuals (or more specifically, http://sine.ni.com/manuals/main?q=Teststand) to look at the TestStand documentation that is shared online. For more TestStand documentation, you could also open TestStand and follow the Help menu to Help>>Search the TestStand Bookshelf. This will open a PDF with a link to several helpful documents. You could also check out the NI Developer Zone and search for help there.
If you are looking for specific coding examples, there are several examples of how to access a C/C++ DLL in <TestStand>\Examples. Specifically, you could look at the <TestStand>\Examples\MultiUUT example. While this example does not perform your exact requirements, it does demonstrate how a TestStand sequence file can use a DLL and how to evaluate limits. If this example is not what you are looking for, you can always search on the previously mentioned NI Developer Zone and look for example code to find something that better fits your needs.Message Edited by Matt Mueller on 08-14-2006 03:20 PM

Unexpected loop behaviour with asynchronous call

I am having trouble with loop behaviour when using an asynchronous call.
I am building an application to record simultaneously temperature (NI USB-TC01 thermocouple), displacement (DC voltage, read from an Agilent 34401a) and resistivity (using a Keithley 2400 sourcemeter).
I am using a voltage sweep function on the Keithley 2400 to alternate current direction in a sample and measure the voltage drop - this is a common technique for eliminating thermal emf from resistance measurements. But what you need to know is that I set the number of current cycles I want and then wait for the instrument to measure and return the meausurements - up to 50 samples, which takes nearly 30 seconds. With the other two measurements, I have to programmatically call a measurement vi for each sample I want.
I have set up my application to asynchronously program the resistivity measurement and then wait for the response, and I want to in parallel measure temperature and position until the resistivity is done. I then want to record the mean and standard deviation for each signal. I used an event structure to interrupt the temperature and position measurements when done.
The problem I am running into is that after the first resistivity measurement is completed and I go to do the second one, the loop that measures temperature and displacement only runs twice, so I only get two samples, regardless of how many resistivity samples I want to collect. For example, if I want 50 resistivity samples at a time, the first iteration will measure rougly 40 samples of temperature and displacement, but any subsequent iterations will only measure twice.
I know this is probably overwhelming to understand the operation, but can anyone help? I have attached my code ('Delatometer') as well as a test vi I built that uses the same structure but has no interactions with instruments ('asynchronousCall').
The
Attachments:
Delatometer.zip ‏221 KB
asynchronousCall.zip ‏29 KB

I forgot to mention...the test vi that I uploaded executes as expected, so I am thinking that maybe its an issue with the instrument calls? I also found that if I run the Delatometer program in 'highligh execution mode' it runs properly, and it is my understanding that in 'highlight execution mode' there is no multi-threading.

Pilotage agilent 34401a

Similar Messages

Maybe you are looking for