34970a

Similar Questions

• continue reading agilent 34970a error 113

  I tried to use labview to make records of continuous temperature of a K type thermocouple and an agilent 34970 a daq and then graphically representing changes in temperature.  I think this should be a fairly easy application, but I've been using the intsrument 34970a driver.  in any case, after a minute or two to run correctly my 34970a agilent gives me an error - 113 error.  Here's my simple coding.

  

  And have you looked at the error message?

• Initialization with 34970A on GPIB problems

  I have a built in LabVIEW 7.1 that takes data from a pair of 34970A executable and 34401, using comms NOR-488.  I have no problem at all to get data. My problem - an intermittent one - occurs during the initialization of the 34970A.  The problem has persisted for a few years.  I use 3.1 NI-VISA.

  The problem is that the 34970A puts in error during initialization, with an error-113 (undefined header).  When single-browsing the Initialize.vi HP34970A I can see that the error occurs as soon as the * IDN? request is sent to the 34970A via the function Write VISA.

  I tried many things: 1. concatenated in a line of constant power to the * IDN? query.  2 tried a 34970 driver later.  3 replace the 34970 A.  4. replace the cable release between 34970 and 34401 (although, as far as I can see, it is unimportant).  The only solution I found is to reset the 34970A.  Sometimes, it works.  In the attached picture you can see where the * IDN? request is sent to the instrument.

  Johnboy:

  I think the problem is with the command sent before this one.  Maybe something flying in the transmission of the buffer that the * IDN? query command gets added, causing the equipment to get confused.  Time out NI SPY max to check what is happening.

  Bill

• Initialization of 34970A reproduction

  I'm trying to reproduce the Figure. http://zone.ni.com/devzone/cda/tut/p/id/4644 3

  My problem:

  After you create the Cluster of Serial Port (Timeout, baud rate, flow control) and try to connect it to the connection on the HP34970 initialize block I get a message that says: 'you have two or more types of enumeration data.
  wired together, but the enumerations are different. The list of questions
  enumerations must be exactly the same. »

  I think my problem is with the enumeration of the input stream control, a last of the Configuration of the Port cluster series in Fig. 3.  I double checked all the entries in the cluster properties and has compared to the example, they match.  But did not work.  However when I dragged the stream of the example input control and it fell in my cluster, the connection has been made without errors.  I don't understand what the difference between the input stream control example and my control of input stream is.

  What I am doing wrong?

  or maybe an easier question, step by step, what is the correct method to create the control Cluster series?

  As you did not post your code, it is impossible to say exactly what could be the difference. Of course, you have created a different enum.

  To create the cluster, the easiest method is to simply right click on the entry of the VI and select 'create a control '. You would have automatically created a cluster of correct type.

• Pilot Data Acquisition Unit 34970A for LabView 6.0

  Is there an instrument driver LabView Data Acquisition Unit Agilent 34970 A 6.0?

  Thank you!

  Paul

  You can go there.

  It is actually LV5.11 that we still use LV 5.11 in production.

• manage requests between acquisition and control program using agilent 34970 A

  Hello
  I realized an acquisition program of data with labview and agilent 34970, real-time acquisition works very well with a time you sample of a second... There is no problem
  to complete the program and control the taps installed in a photovoltaic system, pumping system
  I realized that a second program for the controlit is functional
  but the problem is when I merge the two programs in real-time
  This error is present at the execution of two programs at the same time, that is to say that they launch two request at the same time the instrument 34970 A
  (the poster of agilent 34970A labview crashes)

  -------------------------------------------------- --------------------------------------
  what I want is to find a little thing programming to manage two outgoing REQUESTS at the same time in LabVIEW instrument and create a kind of delay between two REQUESTS

  Sorry for the bad English

  Thank you

  If you are in the same executable, semaphores works well.  You lock the semaphore before making your order and demand.  Release after you get your data.  If the lock is already taken, then the semaphore just will wait until the lock is available.  Only one process can act both in this way.

• Open ERRO agilent 34970 has

  Hello, I am brand new to Labview, I use a 34970A agilent. (I'm french, sorry for my English).
  I made a small program with agilent drivers for temperatures and it works.

  I would now like to measure a voltage. I can read it directly on the Panel prior to the agilent, BUT when I try to read it with the labview with the function of monitor program, the front indicates that the channel is open, it is not that I could read 1 minute before the façade.

  I don't understand the problem because my program is very simple and excutable, there is no problem of communication between the computer and the agilent, so I wonder with the agilent says that the canal is open...?

  I'm sorry for the bad explanation, I hope your understand my pain, I you give some pictures to illustrate my purposes.

  Thank you very much in advance

  
  

• LabVIEW application will run on reboot fees unless MAX is started.

  I'm a NOOB of Labview. I'm the only one here IT and started a year ago and essentially got thrown into the "labview" with 0 experience of labview. I have an xp machine and transform it into a machine to win 7.

  Some highlights: labview 8.2 32 bit running on windows 7 32 bit with libraries of e/s 16. Drive a QPIP to 34970A usb data acquisition unit and an oven temperature compensation. Here's the situation. When I restart the PC my "temp_comp.exe"(application que consultant labview a écrit) will not work. "" I have some errors one as soon as I start the application: 'four due to lack of Communication' and when I try to operate the oven with shortcut both tests and temp:

  error 107387202 has occurred to close visa in HP34970A close.vi.

  34970A_read.VI > Measure oven temp.vi-> wait oven reach temp vi -.

  a model loop.vi - a loop test sequence.vi > hand temp comp.vi

  The possible reasons VISA: 0xbfff009e a library of code required by VISA impossible located or loaded hex.

  I reformatted a machine with xp and was able to get what works well.

  So here's the kicker. If I open MAX and develop devices and interfaces tree program works fine and dandy. no errors. I ran 3 batches in the oven all night with no problems. I thought that I would just an easy work around and the program max to run at startup but I must manually unpack the tree of devices and interfaces before that it will work.

  All ideas will be useful great Cheers!

  Well, VISA 4.0 don't is not supported on Windows 7 either.

  From my point of view, the upgrade to Windows 7 is the problem since your program and your driver are obsolete and unsupported. I don't know what to offer in addition to roll back to xp or upgrade the app and drivers.

• Error 511 & 103 to Agilent 34970

  IM using labview 2011 to measure pressure of a 34970A instrument readings. IM able to measure blood pressure, write to a file, and the trace of the waveforms.

  IM also able to let the user to change the resolution. When I try to control the NPLC (number of Cycles of power line), the VI works perfectly, but im getting errors in the instrument. The error codes are 521 & 103. 521 is a communication error: Input Buffer Overflow and 103 is "invalid separator '.

  I have attached the sub - VI, which sets up the tension and gets the values of the instrument. I noticed that if I run my Initialize.vi in normal mode, it displays error, but if I highlight the lay, it works normally. Is this something to do with the timeout values? The other auxiliary screw works perfectly.

  Thank you

  Eureka

  Since you reset the instrument, try to give some delay after the initialize function.

• Build suspicious in Labview 8.6f1

  Hello

  I'm doing a build of my project containing a couple of instrument drivers. But Labview reacts in a weird way when it deploys construction preview, I got this message:

  "LabVIEW has prevented a file name collision during the build. Names of duplicate files can be copied to the same destination. You can rename the files as part of the build process to avoid name conflicts.

  The following files have been moved to a single location:

  C:\Program NIUninstaller Instruments\LabVIEW 8.6\instr.lib\Array 3711ALV80\Public\Initialize.vi
  C:\Program NIUninstaller Instruments\LabVIEW 8.6\instr.lib\Tektronix TDS 200 1000 2000 Series\Public\Initialize.vi
  C:\Program NIUninstaller Instruments\LabVIEW 8.6\instr.lib\Agilent 34970A\Public\Initialize.vi
  C:\Program NIUninstaller Instruments\LabVIEW 8.6\instr.lib\TTI TSX3510P QL355\Public\Initialize.vi
  C:\Program NIUninstaller Instruments\LabVIEW 8.6\instr.lib\TENMA 72-685X\Public\Initialize.vi
  C:\Program NIUninstaller Instruments\LabVIEW 8.6\instr.lib\Tektronix TDS 200 1000 2000 Series\Public\Utility\Error Query.vi
  C:\Program NIUninstaller Instruments\LabVIEW 8.6\instr.lib\TENMA 72-685X\Public\Utility\Error Query.vi
  C:\Program NIUninstaller Instruments\LabVIEW 8.6\instr.lib\Tektronix TDS 200 1000 2000 Series\Public\Utility\Reset.vi
  C:\Program NIUninstaller Instruments\LabVIEW 8.6\instr.lib\TENMA 72-685X\Public\Utility\Reset.vi
  C:\Program NIUninstaller Instruments\LabVIEW 8.6\instr.lib\Tektronix TDS 200 1000 2000 Series\Public\Close.vi
  C:\Program NIUninstaller Instruments\LabVIEW 8.6\instr.lib\TENMA 72-685X\Public\Close.vi
  C:\Program NIUninstaller Instruments\LabVIEW 8.6\instr.lib\TTI TSX3510P QL355\Public\Close.vi
  C:\Program NIUninstaller Instruments\LabVIEW 8.6\instr.lib\Agilent 34970A\Public\Close.vi.

  I thought that Labview has been able to differentiate between the functions of the different instrument drivers, but apparently it does not.

  LabVIEW is creating in the final construction of a few directories of the instrument with the VI inside.

  Inside of my sweet, I am loading a few screws in memory (with reference) before launching the main façade, this is why I put this VI as always included in the source files for the build.

  If I'm deleting the VI with all instruments used inside drivers, Labview makes no more directories, but I can't start my sweet too...

  We had this problem before with Labview (8.2, 8.2.1, 8.5). Are there clues?

  Thank you

  Hi BugVW!

  Visit this link and tell me if the problem persists:

  http://digital.NI.com/public.nsf/allkb/FB9A11C924883B0C8625742D0059D55B?OpenDocument

  Kind regards