Does LabWindows/CVI: IVI Instrument Driver Development Course contain subject like Communicating with Instruments(SCPI commands)

HI, I am having query regarding; Does LabWindows/CVI: IVI Instrument Driver Development Course contain subject like Communicating with Instruments(SCPI commands)
LabVIEW: LabVIEW Instrument Control Course Day 1 coves subject like Communicating with Instruments This lesson describes how you can use LabVIEW tocommunicate with instruments. You will learn how touse NI-VISA, NI Spy, SCPI commands, and theInstrument I/O Assistant to perform instrument I/O. My question is to you,Does LabWindows/CVI: IVI Instrument Driver Development Course covers similar kind of training like Communication with Instruments? I am more interested in learning How to use SCPI commands to perform instrument I/O. Will you please guide me? So I can choose correct training course. Thanks & Regards,Jay +91 90110 62790EXFO Electro Optical Engineering India Pvt. Ltd.701, 7th floor The Ceribrum IT Park,Kalyani nagar. Wadgaown Sheri India, Maharashtra, Pune 411014

stick to the original thread.

Similar Messages

I just purchased a camera packaged with Adobe photoshop Elements 11. I have a mac book air- which does not have a cd drive. The package did not come with a code or anything that would provide me with another way to install photoshop that came with my came

I just purchased a camera packaged with Adobe photoshop Elements 11. I have a mac book air- which does not have a cd drive. The package did not come with a code or anything that would provide me with another way to install photoshop that came with my camera. Is there any other way i can install this on my camera without using the provided cd or buying the software again?

That doesn't help the user with the serial code though.
There has to be some kind of code somewhere within the package. The disk itself does not contain one. You can look here for help with finding your serial number:
Find your serial number quickly

Does LabWindows/CVI support C++?

Hi there,
I have been using labview for long time and we are looking for another way to improve the performance and labwindows/CVI seems to be a good choice. But here I got few questions
1) Does it support C++ also?
2) Could I compile the LabWindows/CVI applicaiton as a standalone program using in other computer without labview installed?

Hi dragondriver,
are you using CVI or LabVIEW??!? 'Cause here we are on the CVI board
Anyway, whichever is the system you are developing on the Run-time Engine must match the requirements for the executable. As per CVI, the runtime must be of the same level or higher that this. That is why you cannot run a CVI2012 executable with a CVI7 IDE or runtime installed, while it is safe to so the opposite. I do not know the state of the art with LV: in the past the release of the development system and that of the runtime needed to match exactly (infact you could have several LV runtime installed on the same system).
You cannot expect of course that a CVI executable can run on a system with the LV runtime installed (and vice versa)!
With reference to your last question, Traditional DAQ and DAQmx are completely different products, so installing one of them does not affect the other. Additionalle, you cannot mix commands from both environments in the same application: either you develop using old Traditional DAQ functions or you move entirely to the new DAQmx. You can have both of them installed on the target system.
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?

How does Labwindows/CVI label the device?

hi there,
I have two DAQ devices installed in machine. I am using labview 7.1 & traditional DAQ in that machine too. In that machine, the system label the card dev1 and dev2. Recently, I am trying to port my code to CVI with DAQmx9.7 applied, I am trying to write to dev2, it works. But when I write to dev1, it said no such device and suggest me to use dev2 or dev4. I don't know what's going on. When I open MAX, it only shows the old configuration (dev1 and dev2). I didn't see anything about dev4. So how can I tell the label of devices in CVI? Thanks.

Travis-E wrote:
Hello dragondriver,
What DAQ devices are you using? You can try testing the devices in MAX by running a "Self Test" on both the device names you found in MAX. After running the "Self Test" on both devices you can try removing one of the devices and seeing what device name in MAX goes from green to white with a red "X". You can then do the same to the second device to make sure you know which is which. After doing this, hook both devices back up to the computer and give them both custom names by right clicking and selecting "Rename". CVI responds in the same way LabVIEW responds to devices in MAX, the device name is how CVI represents any devices connected. Once both devices are hooked up to the computer and renamed then they should show up as their names in both CVI and LabVIEW.
Regards,
Travis E.
Hi Travis, I have 6711 and 6713. In the MAX, it really shows that those devices are assigned to dev1 and dev2, it has been using for long time. But after I install CVI and developed a program, it seems that dev1 is not accessible in the CVI (though it is all right in labview), the error message suggest to use dev4 instead, it is so confusing. I don't know why.

Is LabWindows/CVI 4.0 for WIndows NT/95/3.1 compatible with Windows XP

Hi,
I have a LabWindows currently running on Windows 95. I want to upgrade my system to XP.
My question is
Is LabWindows 4.0 compatible with windows XP?
Regards,
Adeel Butt
Brookhaven National Lab.

Doing a brief forum search reveals (here) that not even LabWindows 5 is compatible with Windows XP, so the earlier LabWindows 4 is also not compatible with XP.

Conversion of an Instrument Driver from LabWindows/CVI to LabVIEW

Hello All,
Conversion of an Instrument Driver from LabWindows/CVI to LabVIEW
http://zone.ni.com/devzone/conceptd.nsf/webmain/9A93316BEBEDB17786256FA300675A0A
But I can not find any hyperlinkt to download
"LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers"
Is there any evaluation version for downloading?
Thanks,
nonomiya

So strange,
I go through three pages but does not find any entry for download,
hmm...,
1. After press the hyperlink,
See Also:
LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
2. and for a resuest info. form.
3. press download..
====
LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
System Requirements
NI LabVIEW 7.1 or later
Windows 2000/NT/XP
Use the LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers to create LabVIEW VIs for VXIplug&play and IVI-C instrument drivers from function panel (.fp) files.
Instrument Driver Network
Before using the conversion utility to create a new instrument driver wrapper, please visit ni.com/idnet to see if a LabVIEW Plug and Play instrument driver is available for your device. The Instrument Driver Network (IDNET) provides support for more than 3,000 different instrument models from over 170 different instrument vendors.
Recommendations
This utility was created for developers of C-based instrument drivers who wish to provide a LabVIEW interface, but do not develop a LabVIEW Plug and Play driver. By developing the C and LabVIEW interfaces together, it keeps the components synchronized, and eliminates the need for customers to create their own LabVIEW interfaces. Vendors should distribute the LabVIEW wrapper files with the associated VXIplug&play or IVI instrument driver, so that end users do not have to visit multiple web sites to download the complete driver.
If you are not an instrument vendor, we recommend that you use this utility only if you have instrument driver expertise. Access to the instrument driver source code is preferred, in case you need to edit the C instrument driver in LabWindows/CVI.
After generation, the wrapper VIs should be tested with the instrument.
Instructions
Once you install the software, simply access the utility from the Tools>>Instrumentation>>Import CVI Instrument Driver...menu in LabVIEW. This software replaces the built-in tool and provides feature enhancements.
For additional information on this utility, view the resources below.
Readme for the LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
Submit your Driver
Visit the Instrument Driver Network
nonomiya

IVI driver development

Is there any place where there are open projects for delveloping
drivers using IVI? I know one is ivifoundation.org but that does not
list if any comapny wants the driver to be developed for his/her
instrument.
u'r help will be appreciated as I am interested in developing IVI
drivers.
Thanks,
RK

I'm not aware of any listing of companies needing drivers written. I'm assuming that you would like to get paid for driver development so you could try contacting instrument manufacturers and see if they have any need. The biggest (i.e. Tektronix, Agilent) include driver developement in the planning of any new product and usually have an in-house staff doing this type of work but occasionally do go outside. You might also approach instrument manuafacturers that aren't part of the IVI Foundation and try to convince them that a driver will improve sales and that you're just the person that can help. You can also browse the other NI forums such as LabWindows/CVI and Instrument Connectivity to search for driver requests. NI also has a Certified Instrument Driver
Developer program that you might want to investigate as it would probably help you get jobs. Also, you might not want to limit yourself to IVI developement (which requires LabWindows/CVI) but also include the creation of LabVIEW drivers.

Sequence hangs after LabWindows/CVI DLL execution

Hi there, I've written a DLL in LabWindows/CVI that I loaded and executed it successfully in TestStand, with the LabWindows/CVI adapter.
The weird thing is that, when the adapter is configured to debug DLL code with an external instance of LabWindows/CVI, the sequence just hangs after the DLL finishs executing its code.
If I turn off external LabWindows/CVI debugging, in the adapter configuration, it doesn't hang but other strange errors occur, even crashing TestStand!
I reviewed my DLL source code and I didn't find anything problematic. Is it possible that the DLL is overwriting a reserved memory region, thus breaking TestStand functionality? Have you ever seen that?
Thank you very much.

Yes it's possible that the call is corrupting memory. The most likely way for that to happen is if the prototype specified in TestStand does not match what actually exists in the dll, or if you write more bytes to an array passed in from teststand than the step is specified to be passing from TestStand. Double-check that your prototypes match and that you aren't writing past the end of any buffers or accessing any pointers incorrectly.
Hope this helps,
-Doug

Is there a way to do multithreading in LabWindows CVI 5.0(Windows95)?

Because I would like to do several functions in the same .c file, in the same time. This morning, I asked this question:
Is there a way to do multithreading in LabWindows CVI 5.0(Windows95)?
Because I would like to do several functions in the same .c file, in the same time.
You answer me, and you give me some files, some documents. In this documents, there are these routes:
cvi\samples\utility\threading
cvi\apps\dagmthread
but I have not these files with the 5.0 version.
How can I do?
A French guy.

Hey my French friend. I'd say something cute in French but I don't know any so I'll kindly refrain.
I just wanted to echo what Chris said. There are some sweet functions in 5.5 that really make it easy. I tried running my thread app that I made under 5.5 on 5.0 and got all kinds of problems. Mostly because none of the helper functions I wanted to use are in 5.0. Makes sense right? Anyway, 5.5 is a worthy upgrade. I wanted to make sure you didn't think Mr. Matthews was just making a sales pitch.
Let me know if you want some example code for threading under 5.5. ([email protected])
Grant
Grant M. Johnson
Project Engineer
LECO Corporation

Accessing IVI-COM Driver through TestStand ActiveX Steps

Hello
I need to control a Agilent 6691 PowerSupply with TestStand. For this PowerSupply only an IVI-COM Driver exists, no IVI-C Driver. I tried to access it with the ActiveX Adapter Step. But when I try to create a IAgilent66xx object it produces an error without an meaningfull error message.
Is there any way to get this working ?
Thanks
Olli

Hi !,
- I am working on similar need (using Tek scope IVI-COM driver) and currently facing some problems, I was looking for help and saw this thread of discussion almost two year old. Is there any solution to this problem that is now found within two years ?
- I am trying to use IVI-COM driver for scope using ActiveX/COM adapter in TestStand (Ver. 3.5) and when I try to execute sequence I get message as ""Attach to Active Object" in automation call failed. Operation unavailable". Attached is sequence file I am working on.
Attachments:
Tek_scopeIVI.seq ‏21 KB

What is the version of Labwindows CVI that includes IVI AC Power instrument

Hello,
I am looking for the version of Labwindows CVI which i should use to develop custom IVI-C driver for IVI ACPwr instrument. Please share the version of Labwindows where i can find the option to select IVI AC power instrument and create IVI-C Complaint driver.
Regards,
Usha
Solved!
Go to Solution.

Hi Usha,
That version hasn't released yet. It will release sometime this summer.
Luis

NI MAX entry for a Non-NI/VISA Instrument LabWindows/CVI Driver

Hi All,
Sorry in advance if this is not the right forum.
I have created a IVI class and specific instrument driver in LabWindows/CVI for a Video Generator. The generator is a networked, SCPI based instrument. It does not automatically appear in MAX like other NI based instruments.
How or what do I need to do to MAX to use the instrument? Is it as simple as adding the logical name, driver session and advanced driver entries to MAX? Do I need to create a new instrument in the HW section such that the driver session has a device to point to? I have been playing aroud with the networked instrument section in MAX and nothing seemed to make sense to me.
Any help would be greatly appreciated!
Thanks
Minesh
Solved!
Go to Solution.

Minesh,
Maybe this Knowledge Base article will help get you started. I think you will need to add a new VISA TCP/IP Resource in Measurement and Automation Explorer.
How Do I Configure an Instrument to Communicate via TCP/IP in Measurement & Automation Explorer:
http://digital.ni.com/public.nsf/allkb/D7D8E3E1B682022286256D4A00771A52
Robert B
Applications Engineer
National Instruments

Is there a USB Instrument driver developer tool for CVI

Is there a USB instrument driver developer tool/guide for CVI?
Thanks
Chip B.
Solved!
Go to Solution.

Hi! ASIC LabRat,
I agree with your comment. IVI drivers take too much overhead and the executing speed can be very slow compared to the drivers developed using VISA platform. The previous link sent by the NI engineer was very old (2001) and doesn't really help you at all.
Please take a look at this one instead: http://zone.ni.com/devzone/cda/tut/p/id/4713.

SCPI Instrument driver for LabWindows/CVI ?

Is there somthing like a plain SCPI instrument driver for LabWindows/CVI
that works with all SCPI-DMMs ?
Thanks,
Manfred

Manfred Schininger wrote:
> "Kevin B. Kent" schrieb im Newsbeitrag
> news:[email protected]..
> > Manfred Schininger wrote:
> >
> > > Is there somthing like a plain SCPI instrument driver for LabWindows/CVI
> > > that works with all SCPI-DMMs ?
> > >
> > > Thanks,
> > > Manfred
> >
> > SCPI like any other standard is typically non-standard.
> > You can try to get a DMM driver and it will probably work
> > for the most part with any DMM. There may be some
> > slight differences and some features may not work on all DMMs.
> >
> > I might suggest you look into IVI drivers. These follow SCPI for the most
> > part. You get the drivers for each DMM you want and then you have a
> > configuration
file that tells the program which DMM you are using.
> > It then loads the appropriate driver.
> >
> > Kevin Kent
>
> Hello Kevin,
>
> thank you for your answer.
> Unfortunately there is no specific instrument-driver for the DMM I'd like to
> use (Keithley 2700). As I understand this would be the precondition for the
> IVI base classes to work. My hope was to find a simple SCPI instrument
> driver to get into the advantage of instrument independence. But you are
> right, I also once made the experiance that the "SCPI standard" isn't
> completely perfect.
>
> Manfred
Manfred,
You could look for a driver for another Keithly model or try one for a
different brand. They may be similar enough to modify easily. I realize this
goes against the idea of SCPI and standards but it is the best we have now.
Good Luck
Kevin

Importing Instruments Driver from LabWindows/CVI

Does anybody have got wintools_32.dll library ?
I need it to convert LabWindowc/CVI Wintools Instrument Driver to Labview.
Could you send it to me?
Romek.
[email protected]

Hi!
Thanks for your answer.
Exactly, I've tried to import LabWindows/CVI instrument driver to Labview.
This Instrument driver I've found here:
http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B45EACE3F04956A4E034080020E74861&p_node=DZ52176&p_submitted=N&p_rank=&p_answer=&p_source=External
During import procedure i was asked about wintools_32.dll library.
Personally I am interested in System Tray icons functionality of this driver.
I'm not sure that wintools_32.dll is Labwindows/CVI library, but i've searched Microsoft Windows pages with no results.
Regards.
Romek.

Does LabWindows/CVI: IVI Instrument Driver Development Course contain subject like Communicating with Instruments(SCPI commands)

Similar Messages

Maybe you are looking for