Class LV instrument drivers

Similar Questions

• How to load a device driver into the range of instrument Drivers

  I want to be able to download a driver on the area nor to the developers and do appear in the Instrument of e/s, range of instrument Drivers.  Can someone guide me through this?

  Thanks in advance.

  To be a little more specific, you must unzip the file in the instr.lib folder. LabVIEW to restart and it should appear. Read the instructions for more details.

• global variable in the instrument Drivers

  Hello

  We design an instrument Driver for our devices. We have VI that does the same thing, but with different inputs and this entry is a collection of references.

  I would like to know if this VI can be contributed by these groups as global variables. Through this way, I hope that we will significantly optimizie our code.

  We are also looking for drivers to achieve certification by the OR so looking for any sort of solution if global will not be a good solution to achieve the optimization.

  Thanks in advance,

  VIvek

  I don't understand what you mean by "chipped". Using global variables magically will not make your code more efficient. It is used for the global variable, and there are places where they should not be used. Reasonable use must contain the data used by several processes, even if a queue is usually a better way to go.

  The best way to see how to write an instrument driver is to download recent instrument of the NI Instrument Driver Networkdrivers. Look for ones that are based on projects like these are made in 8.x and are fairly recent. You don't have to bother with the old drivers - they are a mess. You should be able to find something that looks like your instrument and use it as a model. There is also a Driver of Instrument wizard that comes with LabVIEW. Another source of information is the basis of knowledge of NOR. Do a search and you will find a lot of information. Like this: developing LabVIEW Plug - and - Play instrument Drivers.

  You should also read on the nugget of Ben on the engines of the Action.

• Confused and IVI compared with plug-and-play instrument drivers

  I'm just going up to LabVIEW and see that when I go to download instrument drivers, there are several lists.  One is a Plug-and-Play and the other is typically IVI.  What is the difference?  So far, I've been through the course of the lesson no. 1 and lesson #2 Basic Developer, but we have not touched on the use of the downloaded drivers.

  IVI: Interchangeable Virtual Instrument. With the help of this software layer allows the developer to work with an independent 'generic instrument' of the manufacturer (e.g. Agilent DMM VX OR DMM).

  Plug 'n' Play driver: the driver for the same instance of an instrument, necessary for the operating system to identify and drive the instrument. The driver is device-specific.

  hope this helps,

  Norbert

• Different versions of instrument drivers

  Hello

  Version of labVIEW drivers are specific?

  If I have an instrument not - NOR and the only driver available for the version of labVIEW 8.2 for interpreter, this driver may work with newer versions of labVIEW 8.6, 2009and 2010.

  Yes, it will work. He just needs to be recompiled and re-recorded for the new version. Just open the screw in the new version and save it back. Make sure that you have a backup of the original.

• using LVOOP with several instrument drivers

  I created 3 classes SigGen.lvclass, HP8657B.lvclass and HP8648B.lvclass. The second 2 classes inherit from SigGen is simply the address of the instrument and virtual functions. I created a VI that initializes a class according to the configuration in a file. This VI emits a SigGen.lvclass. This seems to work fairly well with dynamic distribution. So, I created another set of classes for power meters. However, in the VI which initializes one of objects and the fate as a base class, I get a constraint point while on the SigGen I get none. I am new to LVOOP so I don't know that I'm doing this correctly. Can someone take a look?

  LabVIEW 8.5 Professional

  Nothing to worry about. This is because the cast can't until it hits the indicator so you don't have to only one type of power to the output meter. With the SigGens casting goes to the Terminal output of the case structure (which does not show a point constraint).

  LabVIEW should probably be more dynamically in the question about if it shows a constraint when dot LVOOP ascending cast objects.

• Where to download instrument drivers?

  I need the driver of instruments described in this link:

  http://sine.NI.com/apps/UTF8/niid_web_display.download_page?p_id_guid=E3B19B3E950B659CE034080020E748...

  but I can't find the download button. Any help?

  
  

• instrument drivers

  Hey

  I have a Chroma AC power source model 61600 series. I am looking for a driver to labview, should I install the chr61xx series, what are the options

  chr61xx

  chr6310

  chr640x

  chr6430

  chr6490

  chr65xx

  Vascular, I do not have access to the saturation because it is used by another application. However, none of these pilots say that they take over windows 7. Any idea is welcome thanks.

  Damien

  There are the driver of 616xx so I don't know why you wouldn't download it. It says windows only. I don't see anything on windows 7. Do you really mean 64 bit?

  p.s., A power supply driver writing is actually quite insignificant if you do not want to use IVI.

• Why are sometimes has data from WriteMeas Read zero instrument drivers?

  I have a labview program to control the motorized turntable to rotate and measure the light intensity using photometer Konica Minolta CS - 100a.

  Photometer is connected to the PC via RS - 232.

  Program works great again, data are zero in the decusse format (see table below), the ok status shows error all the time, for line with zero data error code is nothing, and for lines with data, there is a "107367629" error code

  I also enclose the program and a few photos, could someone help?

  Angle	Intensity	x	There		error code
  0	340.1	0,443	0,405		107367629
  10	0	0	0		0
  20	345.99	0,443	0,405		107367629
  30	0	0	0		0
  40	343.33	0,443	0,406		107367629
  50	0	0	0		0
  60	335.73	0,443	0,406		107367629
  70	0	0	0		0
  80	323	0,443	0,406		107367629
  90	0	0	0		0

  YBU wrote:

  Hi all

  Could someone suggest a solution for this problem?

  Thank you very much

  Sorry man, you know most of us here have jobs and help people on this forum for our time free nothing expected in return.

  The first question is how the serial data is formatted? Have a stop character? IE is the data sent by the device always ends with a return character or new transmission line? Device series more for this.

  

• Best way to distribute the Drivers of Instruments LabVIEW.

  Hello

  I'm trying to stick to the standards described just that:

  • Development of instrument LabVIEW Plug-and-Play Drivers
  • Instrument driver development tools and resources
  • Instrument Driver Guidelines

  However, I see clearly what is the best way to distribute LabVIEW instrument Drivers, except that I need to be compliant with these standards are on the IDNET (Instrument network drivers).

  Here are a couple of questions, I'm not really sure of their responses:

  • Is it safe to use a .NET dll and make calls?
  • Is this really hide the block diagram? With the passwords in the drivers
  • Can we prevent the change
  • In my situation several devices (or let's say modules can be controlled by means of a communication), so basically I could be an instrument for many things drivers.,.
  • Can I use some OOD? In order to control the equipment with methods and set properties and encapsulate the tricks of communication in the classes, some equipment could be considered are inherited from other (most recent example), or it is totally prohibited by the above guidelines?
  • What is the type of specification build more appropriate: library packages or other? If packed library, how to handle the first version created problem at the opening of the lib with the new version of LabVIEW then?
  • How to deal with the copyright thing, I have to copy and paste the copyright on both before and on the block diagram Panel?
  • Is this copyright enough: "Copyright (c) . All rights reserved"?

  Ehouarn wrote:

  Hello

  I'm trying to stick to the standards described just that:

  • Development of instrument LabVIEW Plug-and-Play Drivers
  • Instrument driver development tools and resources
  • Instrument Driver Guidelines

  However, I see clearly what is the best way to distribute LabVIEW instrument Drivers, except that I need to be compliant with these standards are on the IDNET (Instrument network drivers).

  Here are a couple of questions, I'm not really sure of their responses:

  • Is it safe to use a .NET dll and make calls?
  • Is this really hide the block diagram? With the passwords in the drivers
  • Can we prevent the change
  • In my situation several devices (or let's say modules can be controlled by means of a communication), so basically I could be an instrument for many things drivers.,.
  • Can I use some OOD? In order to control the equipment with methods and set properties and encapsulate the tricks of communication in the classes, some equipment could be considered are inherited from other (most recent example), or it is totally prohibited by the above guidelines?
  • What is the type of specification build more appropriate: library packages or other? If packed library, how to handle the first version created problem at the opening of the lib with the new version of LabVIEW then?
  • How to deal with the copyright thing, I have to copy and paste the copyright on both before and on the block diagram Panel?
  • Is this copyright enough: "Copyright (c) . All rights reserved"?

  But unsure about 1) (2) and 3) definitely are a no go if you want your library to be distributable through the network ID. The standard only allows dll in which are really developed in C, but you also need to distribute the C code as far as I understand.

  OOP isn't necessarily a problem.

  Packed library is certainly not something you want to do. They work only in the version of LabVIEW in which they were created. You hate when you decide to go with the packaged libraries requests arrive for other versions of LabVIEW and your drivers are high on all the forums of discussion as being a pain in the ass to use.

• Instrument of i/o Drivers added

  I'm sure I knew how to do this at some point, but I completely forgot...

  I just downloaded a new driver from the network driver OR (Agilent 34420 A) and I do not remember how to get the icon appears under the 'Instrument Drivers' tab, under 'Instrument i/o' in the range of functions.

  LabVIEW comes with a driver installed already, so I tried to match.

  I went into c:/program files / etc to the National Instruments installation folder and I put the driver in the instr.lib folder, and then restarted LabVIEW but who do not appear to do.

  If I open 'Find of instrument Drivers' options tab 'Tools', it lists the 34420 A as a driver installed, but it is not always appear in the palette.

  I don't know that I'm missing something simple here.

  OK, here's a (answering my own question).

  Tools > advanced > Edit Palette game

  Then the functions palette appears on the screen.  Find the Instrument of e/s palette.  Right-click.

  Insert > subpallet

  Then use the Browse dialog box to find the file dir.mnu for the specific driver you want to add.

  I am always interested to find an easier (more obvious) way to do...

• Plug and Play drivers: Instrument of Identification error (pumps Ultra PHD at Harvard)

  Hi all! I use the LabView drivers to control a unit of Harvard pump 70-3007 and fall on some issues. (I'm controlling through the USB port).

  Driver:

  http://sine.NI.com/apps/UTF8/niid_web_display.model_page?p_model_id=16026

  Plug-and-Play site:

  http://www.NI.com/white-paper/3271/en/

  So I downloaded and installed the drivers and made sure that I have ALL the necessary software (USB virtual COM and VISA) installed. I then used teraterm (serial port communication software) to make sure my computer can communicate with the pump. He could.

  I then moved in labview, to make sure that my computer can control the pump. He couldn't. As soon as I try to screw attached with the drivers, I get an error. The first step in each VI is to call an Initialize.VI that makes a 'Identification of Instrumentation' stage, which always generates an error. He tells me that either I have wrong COM port (I assure you, I did not) or that the instrument drivers are not updated. HM.

  Any ideas? Of course, I know probably no one here has used this series of pumps before, so if there is no additional information / screws I can join, please let me know.

  
  

• To the installation of custom (my) Labview drivers created using system driver instruments LabView 8.2

  I spent the day writing a driver for my new general i/o board for LabView using the creator of project pilot such Instrument indicated on the latest LabView tutorials. It works fine on my computer, even incorporated in the Panel 'Instrument i/o' on the toolbar. Really great.

  But! This must obviously be something that I can publish on a Web site or email to people for them to install on * their * computers! I tried to use the configuration settings as described in another tutorial in order to produce a zip file, a source folder and a Setup program. However, none of these export options seems to produce a labview library that can be opened without nasty error message on the files being found. Of course, the files are present in the directory, but it is looking for them in the * original * folder instead of either the file installation or a folder in a directory from the file to the library. It's really quite absurd, so I guess I'm doing something wrong... but I can't find information on how to do this right. When I followed the instructions I can find, it does not at all.

  What I * should * was that, if I created an installer, when an end user with LabView installed ran the installer it would integrate the new Instrument of e/s vi in their panel of LabView. But this does not happen. In addition, when you look in the installation directory (by default not the LabView directory), but a directory in Program Files/driver-name all the files are there. But if you open the library in the directory of the Volume, he complains about the vi being in the wrong place, then load them in the wrong place.

  It seems clear that the behavior of the installer must be to put the appropriate files in the location where LabView research instrument drivers. That is not that this disturbs the bajeezus out of me. Can someone explain me or give me a link to the instructions how to accomplish this feat apparently obviously necessary? I can possibly download my driver to the network NOR, but I want to at least test it out first!

  I've attached a zip file of the installation directory, which I do not understand in the runtime environment for reasons of size. I've also attached a zip file of the original directory. It won't work unless that place in the correct location in the folder of LabView. He probably has an older version of I've been using the build options.

  I think I got this figured out, maybe, others may use the solution.

  On the "Source Files" category in the specifications of construction for an installer, [LVDIR] represents the LabView installation directory. So, if you create the directory instr.lib under [LVDIR], you are installing in the root directory of the instr.lib. Then, create another folder named identically in your project source directory (so that it can find the files) and mark in the installation directory. On the side of the project view, open 'My computer', choose your lvlib on the left and your installation on the right directory and click on the right arrow between the two panes. This will create an installation directory structure in the correct location on the target.

• Automing instruments LabVIEW without using specific and coding drivers for each instrument?

  Hello

  I'm new to programming in labVIEW, but I had a few questions about its use in automation and remote controlling several instruments.

  It is an ideal software for automation of various instruments remote control/test. Assuming that I have several different companies spectrum analyzers, I understand that labVIEW drivers of instruments or special VI who would control these instruments. But if I wanted that all these spectrum analyzers to say, to display on another computer using the remote control, but I wanted to use the same program for effeciency, is it possible to do so universally for all instruments using labVIEW? Or do I have to adapt this program for each instrument to instrument drivers cause?

  If labVIEW can do that, is - anyone had good success for such scenarios in other programming languages?

  Thanks in advance for your help.

  Look for the Abstraction Layer material (that you can implement with LabVIEW, even if it's a slightly advanced topic).

  The idea of having a specific Test and be able to enforce it against different Instruments, decided at run time, is the kind of situation that LabVIEW and use of HALs was designed to facilitate.

  The concept is to 'Levels of Abstraction'.  When you create a test, you can design it for an abstract Framistan, since all the Framistans are supposed to be able to measure Vorbels in the range of 0 to 100, so you just plug a generator of Vorbel to generate Vorbels in a certain sequence of Test (linear, random, quickly, slowly, pulsatile, continuous, you decide), measure your Abstract Framistan records readings and compare with the results you expect write the results in a nice report.

  Of course, Framistat of OR uses Ethernet as the means of communication, while HP uses a serial port (depending on the model, series settings can change) and uses of the Intel one. DLL to communicate with the low-level API.  So you also need to develop, for each specific instrument, an "interface" between its API and the Framistan abstract (not everyone uses Vorbels as the input unit, for example).

  So the good news is that it can be done, the bad news is that one of the best ways of handling this type of question on the programming is to use OOP (OOP).  A number of languages (LabVIEW, C++, JAVA) support OOP, but LabVIEW might have the advantage when it comes to interact with the material.

  I you are looking for Hardware Abstraction Layer?  Add LabVIEW to the search query and you should find some nice presentations by Elijah Kerry...

  Bob Schor

• How to use the class IIA for LabVIEW driver wrappers?

  Hi all

  I've read some texts on IVI compliance, but I have not quite how I wrap an IVI - COM to an IVI - C. Where is this done?

  In MAX, I see:

  -Configuration-> software-> IVI Compliance Package 3.3

  But no properties in there...

  I have an analizer spectrum available drivers are only IVI - COM, but I want to wrap them up in IVI - C...

  can someone tell me step by step how can I do this?

  or maybe tell me some beginner tutorial?

  Kind regards

  JPLO

  Hello JPLO,

  Before trying to communicate with your instrument using any sort of instrument drivers, you must confirm that you can connect at a lower level.  In most cases, this means through VISA, using MAX.  IVI - COM driver installation program should add a software module to the IVI Configuration, which is the MAX.  Most installers IVI - C also adds a pilot session, but you'll need to create a.

  We include adaptors IVI - COM for class IVI - C with PKI pilots.  Here's a knockout who talk about them: IVI-C class for specific drivers IVI-COM driver Support

  You can also simply treat the IVI - COM driver like any other ActiveX object.

  What type of instrument you are using?

  See you soon,.

  NathanT