Hp 4145B instrument driver problem

I am having a problem with the graphics plot.vi program of the hp 4145B instrument driver library I downloaded from NI network. This Vi calls a sub vi which is data output.vi and this particular subvi is unable to send its data to the computer. Only in case of short integration time (i.e. the instrument takes measurement very fast and it is not worth always), the dataoutput.vi is able to write if the time out (in ms) is large enough. However I would like to get the data out for a larger integration time, so that the data is good enough. And although this subvi works, this is unable to send its data array to the graphics plot.vi and I get an error message from graphics plot.vi saying error with receive message problem. Could anypne help
me with this?

It sounds like you just need to adjust your timeout. Open the initialize VI and increase the timeout in the block diagram, the original values is set to 10000ms.

Similar Messages

Download instrument driver problem & doubts

Hey friend, i encounter sme problems in displaying my waveform in my labview exercise..currently i am a student n wrking on proj. My present/ongoing task is to try out n understand a prev ex done by a student frm the last batch. The ex is a AM modulation ex. the driver installed by her is 54602B 4-channel Digitizing Oscilloscope however i check my oscilloscope is HP 54600B instead, my signal generator was changed but i am not sure isit the same brand model but current generator is HP 8648B 100-2000 MHz. My teacher say it is a completed n no error ex solution. but no matter how i try and change e setting on the oscilloscope i cant manage to display two match waveform. 1 is internal result another is external which came frm the scope and send the information into the com LabView ex. I even redo and follow e instruction n connection diag she have printed out but it still doesn't wrk.The only fault i thik n suspect that might lead to failure is the prob which i jus mention..so i need to clarify n confirm it..any1 who can help pls reply mi asap..Thanx alot!

My present/ongoing task is to try out n understand a prev exercise done by a student from the last batch. The exercise is a AM modulation exercise. the driver installed by her is 54602B 4-channel Digitizing Oscilloscope however i check my oscilloscope is HP 54600B instead, my signal generator was changed but i am not sure isit the same brand model as before and current generator is HP 8648B 100-2000 MHz. My teacher said it is a completed n no error exercise solution. but no matter how i try and change the setting on the oscilloscope i cant manage to display two matched waveform. 1 is internal result another is external which came from the scope and send the information into the com LabView exercise. I even redo and follow e instruction n connection diagram she have printed out but it still doesn't work.The only fault i think and suspect that might lead to failure is the prob which i jus mention..so i need to clarify n confirm it..anyone who can help pls reply mi asap..Thanx alot! I only have copy of unsuccessful diag. because the work-out exercise i only have is hardcopy.
(The Signal Generator Information graph should display a waveform almost similar to Modulating Signal)
Message Edited by Serina on 03-23-2008 08:16 PM
Attachments:
AM modulation diag.JPG ‏137 KB
AM modulation connection diag.PNG ‏64 KB

"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

Import CVI Instrument Driver failure

Using the "LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers" utility, I successfully converted (wrapped) an IVI-COM instrument driver for use with LabVIEW 8.2.1. However, I have a customer who insists on using LabVIEW 6.0. When I attempt to use the "Import CVI Instrument Driver" tool of version LabVIEW 6.0, I get a crash: Failure: "funcmenu.cpp", line 1873. (Specifically, the error occurs after pressing "OK" to the "CVI Function Panel Converter" dialog and selecting the DLL.) The pop-up suggests to navigate to www.ni.com/failure for assistance in resolving the problem, but when the proper data is entered in that web page, it errors also.
1. Is it possible to do what I'm attempting to do?
2. Any ideas on what is causing my problem?
Thanks

The import tool for CVI drivers only supported IVI-C with LabVIEW 6. If there is no IVI-C driver available, you might be able to write C wrappers around the IVI-COM functions or manually write all of the ActiveX calls to the IVI-COM driver.

Instrument driver import for 2010

The instrument driver import plug-in is not available for 2010 yet. The work-around is obvious (import in 2009> copy>mass-compile) but a bit frustrating.
Jeff

Hi Brian
You're right. The 55292a usb expansion Module is from Agilent Technologies. It can house the Agilent 10887A calibrator board (ISA Slot) for the interferometer hp 5519A. Because we want to use this interferometer with a pc that has no ISA slot, we bougth that expansion module (3 years ago). Unfortunately the cd from agilent has no driver for this device. There's only a program on it. The other point is, that Agilent sold this device to another company and this company sold me this drivers (I think there are no others).
The problem is now, that Agilent don't support the device at all. The other company won't support the drivers running in LabView and national Instruments (Germany) also told me that they won't support me in this case.
But you were right about the COM library I think. I now can see the methods from the drivers, but they are grayed out (except two of them, see attachement).
Thanks for your offer to have a look at the dll. The problem is, that I had to buy this drivers and think the company wouldn't be happy to see me share them here... Can I send them by email to you? My adress is: [email protected]
Thank you very much for your help!
Attachments:
55292a.jpg ‏41 KB

Teststand call cvi instrument driver

I'm new to working with instrument drivers in TestStand. I'm trying to use TestStand to call a CVI instrument driver dll (for Agilent N5767 power supply), and then perform a specific function (init, set voltage, set current, etc.) All of the instruments in my test bench are connected via LAN, and they are configured in NI MAX too. I thought it was pretty straight forward, but I'm obviously missing something. Attached is the simple TS 3.1 seq file with the steps I'm trying perform.
Attachments:
N5700_on_off.seq ‏20 KB

Hi Bkoch1,
Please elaborate on the problem you are experiencing. I am able to open the sequence file you have attached and view your steps and on the surface, this seems like it should work just fine. What indications are you experiencing that it does not work fine? Have you tried setting breakpoints and using the Watch Window to monitor variables to ensure that they are being passed into the DLL? Please explain what the problem is and try to narrow down where the problem occurs and we would be happy to help you.
Regards,
Jackie
DAQ Product Marketing Engineer
National Instruments

Is it possible to convert a LabView .ldd Instrument Driver into a dll that can be used with MAX and visual basic?

I got the following problem. I'm using a Stanford DS360 UltraLow Destortion Function Generator, and would like to access it with the CwIVIFgen ActiveX Controll. In the driver database i found a instrument driver for LabView (ds360fg.llb). But its a llb file and i am not sure what to do.
Is it possible to convert it?
Is it possible to use it anyways?
Maybe i overread the answer, but i search the forums for quite a while now and i am not a bit wiser.
Thanks in advance
Felix

If you have LabVIEW and the application builder, a dll can be created from it but it cannot be used as an IVI driver. The only way to create an IVI instrument driver is with LabWindows/CVI. I personally don't have the time right now to create the dll but maybe if you post to the LabVIEW forum and get someone there to do it. Another other option is to hire an Alliance member to create either a dll from the LabVIEW code or to create an IVI driver from scratch.

Measurement Studio Evaluation Software - Instrument Driver Factory

Greetings,
I have a copy of the Measurement Studio Evaluaiton Software CD. I've
installed the Labwindows/CVI Demo and Component Works Demo. Wanted to
check out the Instrument Driver Factory (located in VB\Instrument
Driver Factory). When I launch IDF.exe I get an error which states
that I have to install Labwindows/CVI. I tried the installation a
couple of times with the same results.
Has anyone else had this problem?
Thanks,
Rick

Mika,
I have tried the installation on two machines.
The first system has Windows XP Pro along with Labview 6.0.2 / MAX /
PCMCIA-GPIB / Visual Basic 6.0 / Visual Basic.Net
The second system has Windows 2000 and Visual Basic 6.0
The Instrument Driver Factory error reads:
The ComponentWorks Instrument Driver Factory cannot locate
Labwindows/CVI. In order to use the factory, please install
Labwindows/CVI version 5.0 or greater.
The Measurement Studio Evaluation Sofware CD installed Labwindows/CVI
5.5 The CD picks a path of "C:\MeasurementStudioDemo\CVI\"
The Instrument Driver Factory is installed in
"C:\MeasurementStudioDemo\VB\Instrument Driver Factory\"
The Instrument Driver Factory is installed when the Component Works
for Visual basic is
installed.
The part number on the installation CD is 350654B-00
Thanks for your help.
Rick
On Mon, 25 Nov 2002 14:00:06 -0600 (CST), mfukuchi wrote:
>Hi!
>I would like to reproduce the problem on a test machine. Could you
>please tell me what OS you are using, and if you have any other NI
>softwares installed on your machine. Also, am I correct that you have
>Measurement Studio Evaluaiton Software for version 6?
>
>Mika Fukuchi
>Application Engineer
>National Instruments

Instrument driver not saving in workspace

I'm very new to LabWindows, so sorry for a newbie question. I've added an instrument driver to my project to have secure obfuscated text entry on a text string control for password purposes. See here.
However, when I close LabWindows and reopen, the IDE seems to forget about the password instrument. I have to re-add it each time. Why doesn’t my workspace remember the instruments?
I tried looking in the ASCII of the workspace or the project file to see if there was a hard reference to the password fb file. Couldn’t find one.
Solved!
Go to Solution.

You may solve this problem in two ways.
If the password control is to be used in that project only, add pwctrl.fp to the project itself.
If you plan to use this instrument for several projects of yours, you can add it to the library menu (Library >> Customise... menu netry, then browse to the instrument file to add it to the list and then restart CVI).
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?

Issue running user created instrument driver VI

I configured an instrument driver measurement VI to fetch test results from a testing device. There is an constant to enter the type of test result to fetch either cres, swave, or twave.
My problem with the VI is that when I run it to fetch "cres" for example, the output string array would display the result from the previous run. I would need to run the VI again to correctly display the result of "cres". Similarly, if I include the measurement VI more than once within one VI to fetch in sequential order of "cres", "swave" and "twave" for example, even with a time delay and in a sequence structure to separate the requests, the output box for "cres" would display data from previous execution and the output box for "swave" would display the data from "cres", and "twave" output box "swave". Please see attached file for detail.
Attachments:
Error with instrument driver VI.docx ‏36 KB
Error in Fetch VI.vi ‏12 KB
Fetch.vi ‏15 KB

I would see how many bytes are in the buffer before you do any fetch. Though, just doing a flush before the first fetch would make sure there is nothing there. All it takes is 1 message to get out of sync. Is this the only VI you are using? Your problem might be in one of your other VIs if not.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions

Instrument Driver Tool has blank Source driver list.

I am trying to create an Instrument Driver form a template using the Instrument Driver Project Tool. When I launch the tool there are no drivers listed in the Source Driver pull down list. Does anyone know why this list would be blank and how to correct the problem?

If the Templates that are installed with LabVIEW are deleted they drop down menu will be blank. You can try restoring the templates (if they were recently deleted) or try to do repair for LabVIEW so the templates are re-installed.

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

Instrument Driver VI's for Linux

Does anyone know if there are already written VI's which use the comedi
suite for data acquisition? Preferrably ones very similiar to the windows
based NIDAQ (like the Configure, Read Data, Write Data, etc) but I imagine
there will be some differences? If not, I'm ready to start making the suite
of these.
Thanks,
Caleb

Caleb Tennis wrote:
> Does anyone know if there are already written VI's which use the comedi
> suite for data acquisition? Preferrably ones very similiar to the windows
> based NIDAQ (like the Configure, Read Data, Write Data, etc) but I imagine
> there will be some differences? If not, I'm ready to start making the suite
> of these.
>
> Thanks,
> Caleb
>>>>>>>>>>>>>>>>> Mensaje original <<<<<<<<<<<<<<<<<<
El 12/14/00, 6:44:20 PM, "Caleb Tennis" escribió
sobre el tema Instrument Driver VI's for Linux:
> Does anyone know if there are already written VI's which use the comedi
> suite for data acquisition? Preferrably ones very similiar to the windows
> based NIDAQ (like the Configure, Read Data, Write Data, etc) but I imagine
>
there will be some differences? If not, I'm ready to start making the suite
> of these.
> Thanks,
> Caleb
Caleb:
I am working in the same that you and I saw your questions in the comedi list
and I am trying the same. I work with the PCI-6025 and I saw that you are
working with the PCI-6023 but the installation is the same. Furthemore I have
installed the driver edaq-0.9.5 of National Instrument but the analog output is
not supported.
Now I have some problems with the installation of Comedi in Debian 2.2 but I
will resolve this problem and then I will begin to make the vi's with comedi
inside, I think that we can help us.
Please mantain the contact.
Ricardo Leal Pacheco.
e-mail: [email protected]/[email protected]
FONO: (09)7111100, 654622.
Ingenieria Civil Electrónica.
Universidad Técnica Federico Santa María.
Valparaíso-CHILE.

Hp8648c instrument driver

Hi,
I am trying to create instrument driver for hp8648c using hp8648a (found in NI website). Could you please help how I can do this?
The only difference is the operating frequency range between two signal gens.
Does this take alot of effort?
Thanks in advance!

Hi Dennis
while I can appreciate your point of view. I am not in full agreement with you,
let me explain.
The Original driver attempts to capture the return code which ends with 8648A
thus using a different model will in present state generate an error.
Which is what should occur. Lets remember that signal generators supply HF
energy which in HF applications can be extremely hazardous ( power amplifier driven
into saturation on open circuit !!!) Resulting in component damage and possible
exposure to HF radiation (higher levels than mobile phones!!)
A dam good reason why the author used 8648A and not 8648.
Back to the point if the library is being modified then surely a compenent engineer would
ensure that all safeguards were implimented, if necessary improved !! YOU cannot not say
well it was some one else software code.
By modifying the library you are taking resonibility for it.
So renaming it 8648C would be most appropiate.
Dedicating the library to a specific model ensures that it could not be accidentally used
in other model applications without re engineering. Thus the onus is now on someone else.
By coercion the VI will only operate in the predefined frequency range.
Let not forget a whether it is a virtual instrument of a physical instrument one should
read the instrument guidlines before attempting to utilise it. Usually though i find that
people refer to the manual when they have a problem.
With regard to your point about the driver sending a valid number, you are assuming that
the labview programmer is using error messaging throughout his code.
chow
xseadog

Anritsu S113B Instrument Driver

Hi,
I'm looking for an Antritsu S113B instrument driver for Labview 6.
I was unable to get the "awsm2" from the NI download area to work., I think
this is an old driver which may not support the newer model S113B.
One of the problem is that the driver expects 604 bytes from the device, but receives 608 bytes, I am not sure where these extra bytes come from.
Some of the VI's work, others (most) don't work at all.
Any help would be appreciated.
Thanks
Heinz

You best resource for troubleshooting instrument drivers in LabVIEW are NI-SPY, Highlight Execution, and the Instrument's manual. I would suggest making sure the flow and command structure are valid for the S113B using these utilities.

Hp 4145B instrument driver problem

Similar Messages

Maybe you are looking for