LabWindows/CVI 5.5 for GPIB communication

Hello!
I'm a GPIB rookie and can't get my GPIB devices to talk with LabWindos/CVI:
For the GPIB devices I am using (FWBell 7030 Gaussmeter, Keithley 6514 Electrometer) are no instrument modules available (at least I can't find any).
How can I talk with these devices, using the IEEE488(.2) functions in LabWindows 5.5?
If I use these functions (i.e. Send / Receive), I allway get error messages and the devices don't redspond and sometimes they show error messages.
How do I address a device on the GPIB Bus?
Every idea is welcome, I need all the help I can get.
Thank you!"

Unfortunately I was unable to find a driver for this instrument either. This leaves you with one of a couple options. First, I would like you to submit a request for this driver at:
http://zone.ni.com/idnet/other.htm
We develop drivers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one.
If you would like to try developing your own instrument driver (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at :
http://zone.ni.com/idnet/development.htm
There may be a similar driver on ni.com/idnet that can be used as a model.
We also have a syndicate of third party vendors that specialize in National Instruments'
products and services. Some of the vendors specialize in driver development. I would suggest contacting one of the Alliance members at:
http://www.ni.com/alliance

Similar Messages

  • LabWindows​/CVI 5.5 for GPIB communicat​ion?

    Hello!
    I'm a GPIB rookie and can't get my GPIB devices to talk with LabWindos/CVI:
    For the GPIB devices I am using (FWBell 7030 Gaussmeter, Keithley 6514 Electrometer) are no instrument modules available (at least I can't find any).
    How can I talk with these devices, using the IEEE488(.2) functions in LabWindows 5.5?
    If I use these functions (i.e. Send / Receive), I allway get error messages and the devices don't redspond and sometimes they show error messages.
    How do I address a device on the GPIB Bus?
    Every idea is welcome, I need all the help I can get.
    Thank you!"

    Unfortunately I was unable to find a driver for this instrument either. This leaves you with one of a couple options. First, I would like you to submit a request for this driver at:
    http://zone.ni.com/idnet/other.htm
    We develop drivers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one.
    If you would like to try developing your own instrument driver (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at :
    http://zone.ni.com/idnet/development.htm
    There may be a similar driver on ni.com/idnet that can be used as a model.
    We also have a syndicate of third party vendors that specialize in National Instruments'
    products and services. Some of the vendors specialize in driver development. I would suggest contacting one of the Alliance members at:
    http://www.ni.com/alliance

  • How to develope LabVIEW for GPIB Communication check?

    I would like to check for GPIB communication using Labview.How to check it?

    Hi,
       You can use the GPIB vis located at Functions>>Instrument I/O>>GPIB palette.
    See attachment.
    Attachments:
    GPIB-vis.Jpg ‏411 KB

  • Develop a LabWindows/Cvi Driver(fp) for custom pci card(dll).

    How to do it?

    You can go to following web page and get some help from there. You might be interested in Driver Development Kit (DDK) Software Reference Manual. Here is the link:
    http://www.ni.com/support/gpib/reg_prog.htm

  • 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.

  • 82351a with labwindows cvi

    Hello,
    I am trying to use Labwindows CVI 2013 with a GPIB card, Agilent 82351a and it can't talk with a GPIB instrument connected to the GPIB card.
    NI-MAX can see the 82351a card but I can't use this card to talk with an instrument.
    I installed Labwindows CVI with NI-VISA 5.4, AGILENT IO suite 16.3 with Agilent Visa a secondary VISA.
    With NI-MAX, in the options VISA, I enable "Passport for Tulip" and with Agilent Connexion Expert, I tried to enable '"programs Agilent GPIB cards for 488" but it reboots the PC and the option remains not validated.
    I wan't to know if this Agilent 82351a card can work with Labwindows CVI 2013.
    thanks

    http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/82351a-with-labwindows-cvi/m-p/2818356/highli...
    Paolo_P
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    Travaux Pratiques d'initiation à LabVIEW et à la mesure
    Du 2 au 23 octobre, partout en France

  • How do I send e-mail to a distribution list using LabWindows/CVI?

    I need to be able to send e-mail to a user-defined distribution list using LabWindows/CVI? Has anyone done this? Any ideas where I could look?

    I commented on something similar to this awhile back.  My issue was that I had the base version and didn't have the Internet classes.  So this external app worked like a charm
    It has a lot of command-line inputer options to use as well.
    http://forums.ni.com/t5/LabWindows-CVI/Need-Help-for-Sending-Email-with-LabWindows-8-5-or-9/m-p/1095...

  • Where can I get Labwindows/CVI v4.0?

    Hi,
    I have been programming with Labwindows CVI at work for the past 4 years
    and I would like to buy a legit copy for my home. I can get buy with 4.0
    asopposed to 5.0 mainly because of price. Does anyone have a copy that
    they don't need after upgrading to 5.0 ?
    email me at [email protected]
    Thanks,
    Russ
    Sent via Deja.com http://www.deja.com/
    Before you buy.

    Hi Russ,
    What is the price you're looking to pay for CVI 4.0?
    Because once you have CVI 4.0, you can upgrade to the Measurement Studio
    Full
    Development System (which has CVI 5.5 and other tools for Visual C++ and
    Visual Basic)
    for $295.
    And this is a really good deal because if you want to buy the base package
    of Measurement
    Studio (which has CVI 5.5 as well) it's $995 and the Full System is $1995 !!
    So you save big time by buying a cheap (hopefully) CVI 4.0 and then later on
    you can upgrade
    to CVI 5.5.
    Just adding my two cents.
    Azucena
    wrote in message news:8dodr2$vvn$[email protected]..
    > Hi,
    >
    > I have been programming with Labwindows CVI at work for the past 4 years
    > and I would like to buy a legit copy for my home. I can get buy with 4.0
    >
    asopposed to 5.0 mainly because of price. Does anyone have a copy that
    > they don't need after upgrading to 5.0 ?
    >
    > email me at [email protected]
    >
    > Thanks,
    >
    > Russ
    >
    >
    > Sent via Deja.com http://www.deja.com/
    > Before you buy.

  • LabWindows/CVI Idea Exchange

    National Instruments introduced the LabWindows/CVI Idea Exchange for submitting and voting on feature requests to be included in future versions of LabWindows/CVI.
    The LabWindows/CVI R&D team is committed to reviewing every idea submitted via the LabWindows/CVI Idea Exchange, so start posting your ideas today!
    Adri Kruger
    National Instruments
    LabVIEW Product Marketing

    One of the more valuable tools within LabWindows is the ability of the editor to fill in struct elements given the struct name. I also work with Eclipse-based tools for embedded systems work, and it has a similar ability. Unfortunately, whereas Eclipse dynamically analyzes the code as it is written, and can provide stuct elements (and other variable information) as soon as the programmer types it in, LabWindows cannot provide this information until after the code has been successfully compiled. As this may or may not happen for some time after the file has been started, or major changes begun, it is almost useless.
    Another useful tool that Eclipse offers that LabWindows does not is the ability to refactor variables and other symbols. Again, Eclipse dynamically tracks the code as it is written, not requiring compilation; refactoring is similar to global replace, except that it tracks the 'C' usage of the symbol and only changes the proper usage. So, for instance, if I use a local variable named "X1" in three different subroutines, and refactor "X1" to "X2" in one of them, only the variable in the particular routine gets changed.It works with any C symbol, including routine names, global and static variables, and structures.
    As a matter of fact, I would encourage NI to look into the possiblity of basing LabWindows on the Eclipse platform, as Atmel did in replacing its proprietary Studio software with an Eclipsed-based version. This would enable users to take advantage of a large number of available Eclipse tools, such as source-code management.

  • Any LabWindows/CVI examples for SPI communication using DAQmx?

    I have a PXIe-6363 module in a PXI running as a real time target, and I'm trying to talk to an accelerometer that communicates with SPI.  I know the 6363 isn't one of the special modules built for SPI, but my understanding is it should be capable; the issue is just the programming.  I've seen examples of this for LabVIEW using DAQmx.  Are there any examples out there for doing it in LabWindows/CVI?
    I'm looking to save time and avoid reinventing the wheel here.  SPI is easy on an Arduino, so it should be doable in LabWindows/CVI, right?  
    Thanks,
    Matt

    Hey Matt,
    I was unable to find any full examples of SPI communication with DAQmx in C. My best suggestion would be to use the LabVIEW examples and implement the same series of function calls to implement the LabVIEW code in C. The DAQmx C API is good about keeping a standard with naming conventions to map with the function names in LabVIEW.

  • Announcement: Security Update 5Q5FJ4QW for multiple versions of LabWindows/CVI and LabVIEW

    An update for LabWindows/CVI and LabVIEW users is now available for download. This update resolves security vulnerabilities in components installed with LabWindows/CVI 2010 SP1 and earlier and LabVIEW 2011 and earlier. Further details can be found at KnowledgeBase Article 5Q5FJ4QW: How Does National Instruments Security Update 5Q5FJ4QW Affect Me?
    The update can be downloaded with NI Update Service 2.0 (which installs with LabWindows/CVI 2010 SP1 and LabVIEW 2011) or from the Drivers and Updates page. Information about the update is also available in other languages through links in the Drivers and Updates page.
    This is free update for all LabWindows/CVI and LabVIEW users.
    National Instruments
    Product Support Engineer

    The correct link should be this one
    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's NI's support for LabWindows/CVI? How's it likely to be in the future?

    Hello Fellow LabWindows/CVI Users,
    Have you found that National Instruments provides good support for LabWindows/CVI?  If so, do you expect good support to continue in the future?
    Thanks,
    Gayle Roth

    Duplicated post
    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?

  • Book: LabWindows/CVI Programming for Beginners

    Has anyone read the followong book LabWindows/CVI Programming for Beginners LabWby Shahid F. Khalid ?
    This book in not in print anymore and  inpossible to find.
    Does anyone know of any similar source material?
    I have both LabWindows/CVI Basics I&II but the content is extremely limited and not enogh details.
    Does NI offer anything better than the embedded Help?
    A Programmers Reference would be nice.
    Thanks.

    Hello NI Nubie,
    I have that book, and also its "advanced" sequel by the same author.  They both went out of print a long time ago.  The books are OK, but they are only available on the secondary market for ridiculous prices now, and that is assuming that you can even find them.
    If I could pass on some advice that might be more helpful to you in learning CVI: pretend those books do not exist for now.  Instead, I think that for learning CVI, there is nothing better than looking at other people's CVI project-level code and really understanding it, inside and out, and then making your own modifications to it to enforce what you just learned from it.  There are several places to start looking for project-level CVI code, which I will list in (what I think) are the highest-to-lowest priority of your training.
    The first place I recommend is the examples that ship with CVI (located in the "samples" directory under the CVI installation directory).  I say this because these are supported by the NI developers and support crew.  In fact, back in 1995 when I was learning CVI 3.1, I dove into the "Icon Editor" application, for several reasons: it was a *complete* application (as opposed to the other, mostly point-solution "academic" examples under the samples directory), it showed how to segment your code into multiple source and header files, and it showed many advanced user interface features (menus, cut-and-paste).  There is now an "example finder" to help locate examples that "fit" to what you are currently trying to accomplish.  I also use the freeware "grep-like" tool called "Agent Ransack" (URL is below) to hunt down specific CVI functions and identifiers (such as certain EVENTS and how these examples use them).
    Agent Ransack on MythicSoft.com
    The second place I recommend is the other "support" locations on the NI web site.  There are knowledgebase articles, tutorials, submitted examples, community examples, and also extra "academic" examples from NI engineers that aren't the same as the ones that ship with CVI.  There are also whitepapers scattered in there as well, and a few that have hidden sample code that is embedded at the bottom of the article.  You really have to hunt for this stuff, and it would be great if the NI folks could try to index this a bit better somehow.  I sometimes even resort to using Google's search engine to find them on the NI web site, because the NI search engine may not find them.
    The third place I recommend are user-based web sites created by power-users of CVI who like to share their code.  Two that I found long ago that remain at the top of the list (in my opinion).  One is Guillaume Dargaud's site, where he has lots of CVI examples and freeware.  The other is Philippe Baucour's "Rebel" CVI site (but you will need to use an online translator if you don't speak French, though).
    Guillaume Dargaud's web site (drill down for CVI examples and freeware)
    Philippe Baucour's "Rebel" CVI web site
    Finally, you might find it interesting to know that there is a tremendous repository of C source code scattered all around the Internet, mostly as part of free and open-source software projects, many of which are supported on sites such as SourceForge.net, and many other locations.  Many of these places are filled with people (in forums or mailing list servers) who live in the C programming world on a full-time basis, and can help you through some of the advanced techniques.  Some of these projects might be targeted to Windows, some use cross-platform techniques, so they have a chance of being applied to your CVI efforts.  There is also an entire universe of programming "libraries" and capabilities that you can use to augment your CVI projects as well.  All of this because of the open-source revolution, riding on the back of GNU/Linux and the community and corporate entities that are backing it all.  Examples that come to mind are Cygwin and MinGW.  If you only have the time to just look up these two items on Wikipedia, you will see that this is just the tip of the iceberg of the possibilities that are available to you as a C and CVI programmer on Windows.
    I hope this was helpful to you.
    JB
    To whom it may concern: My alias is also my nickname, I've had it since I was a (very) skinny basketball-playing teen. OK, so I've got a 38 inch waist now, but my hometown friends haven't shaken that appellation for me. I trust that you will someday be OK with that alias, as I have been with that nickname.

  • How to set a DMA transfer type for PXIe-6536 in LabWindows/CVI?

    I have a PXI chassis PXIe-1078 with a controller PXIe-8115 running under Windows 7. The digital output board is PXIe-6536.
    I use a function DAQmxSetChanAttribute to set a property DAQmx_DO_DataXferMech to a value DAQmx_Val_DMA, since I want to use a direct memory access data transfer. This wokred well with a PCI-6534 board using the same LabWindows/CVI code before migrating it to the PXIe system.
    Unfortunately, running this code on the PXIe system reports a DAQmx error -200452: "Specified property is not supported by the device or is not applicable to the task".
    The task is created in the following simple way (the board name in MAX is 'Dev1'):
       DAQmxCreateTask ("digTask", &digitalTask);
       DAQmxCreateDOChan (digitalTask, "Dev1/port0:3", "DIG_CHANNELS", DAQmx_Val_ChanForAllLines);
       DAQmxSetChanAttribute (digitalTask, "", DAQmx_DO_DataXferMech, DAQmx_Val_DMA, 15);
    How can I solve this problem? How is it possible to choose between different transfer types?
    Thank you in advance for any hint!

    Hi CavityQED,
    The PCI-6534 is a "Digital I/O" board while the PXIe-6536 is a "High Speed Digital I/O" board, that's why they don't have the same properties.
    By the way you can use DMA transfer with this method :
    http://zone.ni.com/reference/en-XX/help/370520J-01/hsdio/direct_dma/
    Let me know if it helps you.
    Regards.
    Mathieu_T
    Certified LabVIEW Developer
    Certified TestStand Developer
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    LabVIEW Tour
    Journées Techniques dans 10 villes en France, du 4 au 20 novembre 2014

  • Yokogawa UT driver for LabWindows/CVI 6.0 won't translate to LabVIEW 8.6?

    The device driver for the Yokogawa UT series furnace controllers is in LabWindows/CVI 6.0 and I would like to use it in LabVIEW. I tried to use the utility to convert from LabWindows/CVI to LabVIEW, but it said it couldn't and that the device driver is from before LabWindows/CVI 5.01.
    In any case, here is the series of events.
    I downloaded the LabWindows/CVI to LabVIEW Converter, from
    the page on LabVIEW's developer's connection that had the driver for the
    Yokogawa UT controller.
    From an empty LabVIEW Block Diagram, I click
    Tools>>Instrumentation>>Create LabVIEW Interface to LabWindows/CVI
    Instrument Driver...
    This takes a little while to load. During loading an
    FC_Interface_Main.vi runs, apparently trying to find a file.
    Once that is done, the two options are Basic and Advanced. I leave
    basic selected. I click next. browse to find the ykut.fp file from the
    driver I downloaded.
    I then click next. The error window that is seen in the screen shot is
    then shown.
    I called a tech support guy at NI about this, and I e-mailed him with all the above, but there was no reply, though the conversion utility is no longer available on the same web page as this specific device driver.
    In any case, if anybody could give a little guidance, it would be appreciated.

    Hello Screamingzebras,
    I converted the .fp file to be version 5.5 and ran the utility that was mentioned.  I have attached two files to this post.  "ykut.zip" is the converted .fp file (version 5.5).  "yut.zip" is the converted instrument driver.
    Regards,
    Jon S.
    National Instruments
    LabVIEW R&D
    Attachments:
    yut.zip ‏174 KB
    ykut.zip ‏25 KB

Maybe you are looking for