Instrument driver hp34970A advanced scan example timeout error

if i scan more than two channels using the hp34970A andvanced scan example.vi instrument driver, i get"timeout expired before operation completed occured at visa read in standard event status.vi of advanced scan example.vi. this occurs before the instrument finishes the scan. i am using mac osx. any suggestions? thanks

I do not have experience with this instrument or driver but have you tried increasing the timeout value? On the front panel of the VI that you mentioned there is a place for the timeout value.
Please repost if you still have problems with it. Thanks!
JenK

Similar Messages

Agilent 53131A LabWindows/CVI device driver showing timeout error

Hi All,
I have developed TestStand sequences for Measurements using Agilent 53131A frequency counter instrument. I have developed 2 sequences one using CVI drivers and the other using LabVIEW drivers. The functionality of the sequence is as follows
1. Initialize the instrument
2. Measure the frequency for N number of times
3. Close the instrument
What I could find is the LabVIEW driver based sequence is working fine (for any number of measurements) but the CVI driver based sequence is showing Timeout errors after 1or 2 measurements.
Thsi is the driver page http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=1003
Can anyone help me to find the root cause of this issue?
Thanks in advance...
Into the pursuit...
Maverick

Were you using the VXI Plug and Play or IVI driver?

How to save changes to downloaded instrument driver

I am using downloaded Tk278x drivers. The default address is different from my what I want. I tried to change the address in the VIs. But I am not lucky. How can I do it? Many thanks.

It looks like this is a driver that Tektronix wrote and donated to the Instrument Driver library. The VIs on the palette are a mix of examples and instrument driver VIs, and the examples hard-code the GPIB address. (The instrument driver VIs have the white background on the icon, and the examples have a gray background.)
So, if you are interested in using one of the examples in your application, I would make a copy of just that example VI. Be sure to rename the VI when you make a copy. (E.g., "My TEK 278X.vi". Otherwise, since LabVIEW only allows one VI of the same name in memory at a time, your application might link to the original VI in instr.lib.) Ensure that all of your VIs reference the new copy, and not the VI with the original name in instr.lib.
In these examples, it appears that there's a string constant on the diagram that you just need to change from "1" to whatever your GPIB address is.
I hope this helps.
Brian

I get an error when I use the instrument driver KE230x.

Good day. I am using the ke230x instrument driver connected to a Keithley 2306-PJ. I am using the USB to GPIB to communicate with the instrument
I load the Getting Started VI and when I hit run I get the following error message
====================================================================
Error - 1074003951 occured at ke230x Initialize With Options.vi
Possible reason(s):
Driver Status: (Hex 0xBFFC0011) Primary Error: (Hex 0xBFFC0011) Identification query failed.
Elaboration: Failed to Recognize Model
=====================================================================
When I place the "id query" switch into the false position, everything appears to be working. I have left the "reset device" in the true position and I see the instrument resetting.
I do not understand what is happening?
Thank you for your time and help.

Good day. Dennis - thank you for your response. My next question is if I leave the ID Query off (false) position, I still cannot get the program to work.
My guess is that I am doing something wrong (I am relatively new to LabView). I use the Getting Started vi and everything looks to be working okay. I then start the Application Example (I run the Getting Started vi before I run the Application Example to make sure that the Application Example has the correct instrument handle). When I run the Application Example I get the following error message
Error -1074130544 occurred at ke230x Configure Current Limit.vi
Possible reason(s):
Driver Status: (Hex 0xBFFA1190) The session handle is not valid.
Any help or advice would be greatly appreciated.
Michael

I have an error with the hpe363xa instrument driver. Where do I go from here?

I have the latest versions of labview, max, gpib, ivi engine,... I downloaded the hpe363xa driver (for Agilent E3633A power supply). MAX configured the gpib ok (can communicate with instrument and gpib tests run ok). When I run the hpe363xa Getting Started.vi (only changed the Resource Name to match instruments gpib address) I get the following error message:
Error -1074135024 occurred at hpe363xa Configure Current Limit.vi
Possible reasons:
Driver Status: (Hex 0xBFFA0010) Invalid value.
Secondary Error (Hex 0xBFFC0004) Parameter 4 out of range, or error occurred while setting Parameter 4.
Elaboration: Current Limit
---end of error message
This error o
ccurs in the call to hpe363xa_ConfigureCurrentLimit(); in the DLL. The current limit value is ok right up to the function call vi (calls the c function in the DLL), so presumably the "error occurred while setting Paramter 4", whatever that means.
A possibly related issue is that even though I have IVI installed and it shows up under My System\Software in the configuration tree, there is no My System\IVI in the configuration tree (like MAX and other documentation implies there should be). I tried re-installing IVI, but did not try re-installing MAX.
Thanks for any help.

Hi,
Just back from holiday and spotted your question.
I had a similar problem a while back and resolved it with some modifications to the IVI example with IDT 1.1. ( IviDCPwr [MSR] - Output DC Volts.vi ).
Attached is my vi. This vi is intended to run with a sperate Initialise.vi and close vi but as you will see the initialise and close are encased in case statements.
The VI is labVIEW 5.1.1, IVI IDT 1.1 library.
Hope this helps.
Regards
Ray Farmer
Regards
Ray Farmer
Attachments:
setpowersuply_ividcpwr.vi ‏112 KB

Timeout error (code 6101) for acquisition from MODBUS instrument

I am experiencing a problem which other users have reported, but for which little useful information has been posted:
I am trying to acquire data from an instrument using MODBUS RTU protocol. The code works as desired for a while, but will intermittently stop executing and give a timeout error, code 6101. This code seems to be associated with the MB Serial Master Query sub VI. In the past, I was getting this error as a result of RF noise corrupting the signal in the USB connection to the instrument. Removing the USB cable from the noisy environment eliminated the problem. I am now having the problem with an RS 485 line in the noisy environment, which should be very stable in noisy environemnts.
My question: is there a coding trick i can use to reconnect in the event that a corrupt signal occurrs (or some other problem which results in the intermittent appearence of the error 6101)?   I've increased the timeout value on the MB Serial Master Query sub vi, but this hasn't helped. Any input is appreciated. In case it's useful, I've posted a simple version of code which generates the problem.
Thanks,
Paul
Attachments:
Floating point 1.12.vi ‏24 KB
timeout error1.JPG ‏31 KB

Thanks for your input, Ravens Fan. I am indeed getting a popup error message with the timeout. I agree that putting the MODBUS read in its own loop would solve the problem. However, I'm struggling with trying to figure out how to actually do this.  Should I put the read in a case structure or a while loop? How do I go about looping back to re-execute the read statement? I think so called "state machine architecture" seems to be where I should be going. Some example code would be greatly appreciated.
paul

Error-85 on instrument driver VI

Hi,
I'm trying to modify an instrument driver in from an instrument control course tutorial. I followed the tutorial and I can't see any mistakes on my but when I run the instrument driver vi, I get an error 85 message saying that labview scan failed. Possible reasons, the input string does not contain data in the expected format. Please see attached VI. I will appreciate any help.
Thanks.
Attachments:
Fetch Waveform.vi ‏22 KB

Hi Dennis,
Sorry, I thought explaining what was happening the way I did would be enough. Anyways, the data at the input is pretty long but here is the starting section below. The only thing I noticed here is that the first data point has a different format than the rest.
8.8531e-17,
0.31395,0.62667,0.93691,1.2434,1.5451,1.8406,2.1289,2.4088,2.6791,2.9389,3.1871,3.4227,3.6448,3.8526,4.0451,4.2216,4.3815,4.5241,4.6489,4.7553,4.8429,4.9114,4.9606,4.9901,5,4.9901,4.9606,4.9114,4.8429,4.7553,4.6489,4.5241,4.3815,4.2216,4.0451,3.8526,3.6448,3.4227,3.1871,2.9389,2.6791,2.4088,2.1289,1.8406,1.5451,1.2434,0.93691,0.62667,0.31395,-1.4742e-14,-0.31395,-0.62667,-0.93691,-1.2434,-1.5451,-1.8406,-2.1289,-2.4088,-2.6791,-2.9389,-3.1871,-3.4227,-3.6448,-3.8526,-4.0451,-4.2216,-4.3815,-4.5241,-4.6489,-4.7553,-4.8429,-4.9114,-4.9606,-4.9901,-5,-4.9901,-4.9606,-4.9114,-4.8429,-4.7553,-4.6489,-4.5241,-4.3815,-4.2216,-4.0451,-3.8526,-3.6448,-3.4227,-3.1871,-2.9389,-2.6791,-2.4088,-2.1289,-1.8406,-1.5451,-1.2434,-0.93691,-0.62667,-0.31395,8.8531e-17,0.31395,0.62667,0.93691,1.2434,1.5451,1.8406,2.1289,2.4088,2.6791,2.9389,3.1871,3.4227,3.6448,3.8526,4.0451,4.2216,4.3815,4.5241,4.6489,4.7553,4.8429,4.9114,4.9606,4.9901,5,4.9901,4.9606,4.9114,4.8429,4.7553,4.6489,4.5241,4.3815,4.2216,4.0451,3.8526,3.6448,3.4227,3.1871,2.9389,2.6791,2.4088,2.1289,1.8406,1.5451,1.2434,0.93691,0.62667,0.31395,-1.4742e-14,-0.31395,-0.62667,-0.93691,-1.2434,-1.5451,-1.8406,-2.1289,-2.4088,-2.6791,-2.9389,-3.1871,-3.4227,-3.6448,-3.8526,-4.0451,-4.2216,-4.3815,-4.5241,-4.6489,-4.7553,-4.8429,-4.9114,-4.9606,-4.9901,-5,-4.9901,-4.9606,-4.9114,-4.8429,-4.7553,-4.6489,-4.5241,-4.3815,-4.2216,-4.0451,-3.8526,-3.6448,-3.4227,-3.1871,-2.9389,-2.6791,-2.4088,-2.1289,-1.8406,-1.5451,-1.2434,-0.93691,-0.62667,-0.31395,8.8531e-17,0.31395,0.62667,0.93691,1.2434,1.5451,1.8406,2.1289,2.4088,2.6791,2.9389,3.1871,3.4227,3.6448,3.8526,4.0451,4.2216,4.3815,4.5241,4.6489,4.7553,4.8429,4.9114,4.9606,4.9901,5,4.9901,4.9606,4.9114,4.8429,4.7553,4.6489,4.5241,4.3815,4.2216,4.0451,

"undefined symbol" error while using a custom instrument driver

Hello all, I'm facing a problem related to instrument driver creation.
I want to pack a part of my code to a .FP to be able to reuse it in other applications of mine. This part of code includes calls to Windows API and a third party dll. I have included both windows.h and the include for the dll in the header file for the instrument. I developed the source code and next a little application that simply calls one function to test the result of my work, but I get some 'undefined symbol' errores while linking the test application with the instrument. The instrument header file is included in program source file.
Situation is as follows:
I can run the test application if I include the source file for the instrument directly in the project (without loading the instrument)
I created a static library and can have the test program up and running if directly including the library in the project (again without the .fp file)
I get linker errors when trying to use the instrument I created based on the same code, both when including the instrument at source code level and when including at library level. Adding the .fp to the project makes no difference
Linker errors are all related to WinSDK and third-party dll functions.
Question is: where and how I have to declare the symbols apart including the appropriate .h files in the instrument header file?
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Being waited on to log on... how flattering
I wish I had a simple and obvious solution, but I don't.
The problem in this case is that, whereas DLLs (via their import libraries) carry no additional build-time dependencies to their clients, that is not the case with object files and static libraries: any project that uses those .obj and .lib files must satisfy all of their dependencies when that project builds.
There is a mechanism, with .fp files, to advertise such dependencies to the clients of the .fp, and that is the auto-load list (Edit>>FP Auto-Load List, in the function tree editor). The caveat, however, is that these indirect dependencies must have a companion .fp that you can add to this list. And in your case, you don't have one. So the only solution I can think of is for you to create a very thin wrapper module where you would wrap all of the SDK functions that you need, then create a basic .fp for this wrapper -- you can do this semi-automatically, from the header file (Options>>Generate Function Tree) -- and then add this .fp to the auto-load list of your primary .fp. And then you'll probably have to create a second .fp wrapper for your other dependency (a non-SDK third-party DLL?).
Once you have declared the dependency chain for this .fp, you should then be able to use it on any test application and CVI should know to link in these additional static libraries whenever it builds the test application.
If you choose to go this route, you'll probably have to deal with a bunch of non-standard data types in the parameters of the SDK functions. I don't remember if these are automatically added to the .fp when you create it from the header file. If not, all you need to do is add them to the .fp later (Options>>Data Types, from the function panel editor). Don't worry about providing the definitions for these data types. They're not necessary. You just need to make sure that their names are in the list.
Luis
Message Edited by LuisG on 05-19-2010 10:43 AM

Timeout error in Wait for Operation Complete VI for TEKDPO4054 scope driver

Hi,
I keep getting a timeout error (-1073807339) when I run the "wait for operation complete" sub-VI that comes with the tektronix DPO4000 series oscilloscope driver. I'm using a DPO4054 scope. The error out source is the VISA Read STB command, but I can't figure out what's wrong. Has anyone else encountered this error? Please help!
Thanks for your time!
I've attached the sub-VI where I'm having this problem.
Attachments:
tkdpo4k Wait for Operation Complete.vi ‏27 KB

duplicate post
Please try to keep your questions to a single board.

Advanced LabVIEW Instrument Driver Development Techniques

Hi, reading AN006-Developing a LabVIEW™
Instrument Driver and in page 2 I find:
"refer to the Advanced LabVIEW Instrument Driver Development Techniques application note."
I can not find this AN. Is the name correct ?
Bye
Luca

Hi Luca,
the link you're looking for should be this:
http://zone.ni.com/devzone/conceptd.nsf/2d17d611efb58b22862567a9006ffe76/e7a1635c2166e0728625680a005b0b9a?OpenDocument
Happy new year,
Alberto

INI instrument driver and fatal run time errors

Hey everyone, I'm experimenting with the INI instrument driver and running into a fatal run time error. Here's what I know so far:
The runtime error only happens during the very first Ini_Putxxx
It only happens if the target INI file does not yet exist. After the file is created with a Ini_WriteToFile, then the program will proceed with all my Put functions without any errors.
Ideas?
Solved!
Go to Solution.

Are you sure about that? I just tried calling these functions in the Interactive Execution window without errors (the destination file wasn't there before the call and has been created without errors):
#include "inifile.h"
static int error = 0;
static IniText T = 0;
T = Ini_New (0);
Ini_PutString (T, "General", "Item 1", "Test string");
Ini_PutInt (T, "General", "Item 2", 123);
Ini_PutDouble (T, "General", "Item 3", Pi ());
error = Ini_WriteToFile (T, "C:\\test.ini");
Ini_Dispose (T);
Ini_PutXX functions do not make any disk access, they work entirely in memory; the only functions where the instrument accesses the disk are Ini_WriteToFile and Ini_ReadFromFile. Which error are you receiving? Can you post a sample code that exhibits the error?
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

In the NI-5640R Instrument Driver API Examples for the Modulation Toolkit what is the mode of operation of the DAC/DUC(AD9857)

In the NI-5640R Instrument Driver API Examples for the Modulation Toolkit what is the mode of operation of the DAC/DUC(AD9857)

In the single tone mode AD9857 would not take any digital data. It ganerates the sinusoidal wave using DDS present inside.
Message Edited by Vinny ICS on 05-25-2009 05:04 AM

Frame timeout error using Configure Trigger3.vi

Hi all,
I'm triggering the frame capture of an .avi with an RTSI connection. However, I keep getting a frame timeout error when I use the IMAQ Configure Trigger3.vi. I don't get any timeout errors when I just use the IMAQ Generate Pulse3.vi but I am trying to sync the frame capture to an optical switch. If I just use IMAQ Generate Pulse3.vi, I get a .avi but the frames are completely out of sync with the switch, but if I use both IMAQ Generate Pulse3.vi and Configure Trigger3.vi I get nicely separated images but it takes an age and ends up in a timeout error.
I want to capture e.g. 500 frames, over the course of 2 s - so I've set my frame timeout to be 2000. At my current acquisition rate (31680 Hz per line (1024 pixels)) 500 frames corresponds to a total of 1.578 s (images are 100 pxls in height). This is much less than the total scanning time. Where am I going wrong?
Thanks in advance for your help.
Miika
Attachments:
screen.png ‏32 KB

Hey Miika
What are the hardware you are using. These vi's only work with specific hardware and this may be why they are not functioning correctly. For example the Configure trigger3 vi only works with the following PCIe-1427, PCIe-1429, PCe-1430, PCIe-1433.
Matthew Trott
Applications Engineer
National Instruments UK
www.ni.com/ask

"agesani Initialize With Options" timeout error on HP E4401B spectrum analyzer

System: Windows XP Pro, LabVIEW 7.1, IVI Compliance Package 3.0, NI-VISA 4.1
I have an HP E4401B Spectrum Analyzer. I'm trying to write some LabVIEW code for it, using the agesani.llb library.
When I try using the agesani Initialize With Options VI, I get the following error:
Error code: BFFF0015
Source: agesani Initialize WIth Options.vi<ERR>Driver Status: (Hex 0xBFFF0015) Primary Error: (Hex 0xBFFF0015) Timeout expired before operation completed.
I've searched the NI Knowlege Base, and haven't found anything that seems useful. What I _have_ found are the following items.
Knowlege Base article "Time-Out Error with the Agesa Instrument Driver Example". This refers to the agesa drivers, not the agesani drivers. It also references an E4440A spectrum analyzer, not an E4401B. The article says one cause could be that a compatibility mode other that SCPI is in use. While the articles says how to fix this on an E4440A, the fix does not appear to apply to the E4401B. In fact, if it is even _possible_ to have a mode other than SCPI on an E4401B, I can't figure out how to do it. A second possibility the article suggests is that the spectrum analyzer is in Phase Noise mode rather than Spectrum Analyzer mode. My E4401B is in SA (spectrum analyzer) mode. I don't even see a way to put it in any other mode - I don't think the required options are installed. Finally, my VI is configured as the article states - ID Query YES, Reset Device YES, etc. I should note that the instrument's GPIB address is 18, and that this matches the resource name GPIO0::18::INSTR.
Some additional information: The spectrum analyzer's screen is indicating the instrument is in Remote (R) mode as a Talker (T). A "Query UNTERMINATED" error message appears at the bottom of the instrument screen.
I've attached the results of a NI Spy capture to this message. (At least, I think I have. I've never tried doing this before, so if it doesn't show up, would some kind soul tell me how to include an attachment to my post?)
Oh, yes. The agesani version is driver version 1.1, updated 17 Aug 2007. (The version that's currently on the NI download site.)
Attachments:
Capture4.spy ‏9 KB

Hi MXI Master,
If there's an instrument timeout, I haven't been able to find it yet. Seems like there should be, so maybe I just haven't looked in the right place yet. As for the timeout value on the computer, I'm not sure what you mean by this - could you elaborate, and maybe tell me where to find it?
As far as SCPI mode, if it's possible to put the E4401B in something _other_ than SCPI mode, I haven't figured out how. I can't find any support in the programming manual for anything other than SCPI.
That kind of seques into my next couple points. The NI Spy output indicates that one of the commands that is being sent is "*SRE 32".
The "User's & Programmer's Reference" for the E4401B says (on page 206) "Send the *SRE <number> command (where <number> is the sum of the decimal values of the bits you want to enable plus the decimal value of bit 6). [Bit 6 is the Request Service (RQS) Summary Bit. BP] For example, assume that you want to enable bit 7 so that whenever the operation status summary bit is set to 1, it will trigger a service request. Send the *SRE 192 (128 + 64) command."
This statement would seem to imply that the "*SRE 32" command that is being sent by the agesani "Initialize With Options" command is an illegal command, or at best an ineffective command. In light of that, it is interesting to me that the NI Spy output indicates that the next line , viQuery(GPIB::18::INSTR (0x246E9C8), "%s?","%ld"), is generating an 0xBFFF0015 error. In addition, I can find neither the "%s?" nor the "%ld" commands listed in the Programmer's Reference. I wonder if these could be for a firmware revision later than mine (A.01.03), or for instrument options I don't have (A4H, A4J). Alternatively, I wonder if these are simply mistakes.
The next line in the NI Spy output, Formatted viWrite(CPIB0::18::INSTR (0x0246E9C89),"INST:NSEL?",11,11), also puzzles me. The Programmer's Reference indicates that this is a supported command, to see what instrument application is currently selected. (e.g. spectrum analyzer, GSM, Bluetooth, EDGE, noise figure, etc.) However, when I try to issue this command to my instrument, by using the Instrument I/O Assistant Express VI, I get an "Undefined header" error on the instrument's front panel. The instrument's error history shows the same "Undefined header" error. Since my instrument only has the basic spectrum analyzer option installed, I wonder if this command is not valid? (Personally, I wouldn't write instrument firmware code this way, but who knows?) Alternatively, I wonder if this command requires a firmware revision more recent than mine. (The Programmer's Reference is silent about this possibility.)
The next line in the NI Spy output, Formatted viRead(GPIB::18::INSTR (0x0246E9C8),"",4000,0), has another 0XBFFF0015 error associated with it.
Does this information shed any more light on the situation?

CD/DVD drive issue on Satellite L notebook - error code Code 39

Hi,
Could anyone tell me if there is an updated driver for the TSSTcorp CDDVDW TS-L632H ATA Device? The device is not available as a selectable drive and in device manager it reports the following error:
Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
I have removed the device and the driver, however on scanning for hardware; vista re-installs the default driver and the same error returns.
Because of this error, I am unable to update the firmware for the drive and the firmware update is unable to see the drive.
Any ideas??
Thanks in advance.

Hi buddy
What to saythis issue is known and caused by wrong Windows registry entries.
Microsoft has released and published some knowledge articles.
Check this:
http://support.microsoft.com/kb/270008/en-us
First of all I recommend removing the CD/DVD drive from the device list in device manager. Then remove the Upperfilters and Lowerfilters values completely from the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}
Finally reboot the notebook.
Thats all.
PS: you would find this solution also without my help. You should use the forum search function! Its helpful!

Instrument driver hp34970A advanced scan example timeout error

Similar Messages

Maybe you are looking for