GPIB support on LabVIEW-RT

I would understand why the GPIB interface on the PXI-8175-RT is not supported with LabVIEW-RT.
The same interface is supported on the PXI-8146-RT.
As I have some performance problem to communicate with the Ethernet link, I would use the GPIB link to transfert data between 2 systems.

Hello,
That is correct. At this time, GPIB is only supported on the 8146 RT and 8156B RT controllers. LabVIEW RT does not support the GPIB controllers on the 8175 and 8176; also, PXI GPIB cards are not supported.
There are a few easy alternatives to using the ethernet link. One easy solution is to use your serial ports. Another solution is to use your I/O modules, like Analog or Digital lines on a Data Acquisition board to share information between systems.
I hope this information helps.
Regards,
Dafna

Similar Messages

  • NI-DAQmx support for labview could not be found

    Hi, I am pretty new to LabView. I was using VC++ to programming for my USB-6215. Just curious how LabView works, so I try to follow the "Introduction to Taking an NI-DAQmx measurement in LabView" and configure my USB-6215 in LabView. However, when I try to gererate codes for the DAQmx task name control, an error message pop up as "Error:NI-DAQmx support for labview could not be found. Please reinstall NI-DAQmx".  I did reinstall NI-DAQmx, but it doesn't help. This error occurs anyway. Any idea how it happens and the solution is highly appreciated. Thank you.
    Jingyu 

    See attached
    Paul Falkenstein
    Coleman Technologies Inc.
    CLA, CPI, AIA-Vision
    Labview 4.0- 2013, RT, Vision, FPGA
    Attachments:
    MX picture.PNG ‏35 KB

  • Is the Aardvark OEM I2C Host Adapter supported with Labview?

    Hi All,
    I am now looking forward to use Aardvark OEM I2C Host Adapter (http://www.totalphase.com/products/aardvark-oem-i2c/)
    in LabView2013.
    Question:
    Is this device supported with LabView?
    How can I use this device?
    Best Thanks,
    Jessie

    Yes
    We have plan to buy and use Aardvark OEM I2C Host Adapter and use it with LabView2013.
    I am searching if this device already has LabView VI's for I2C communication.
    I am not sure If we can use the VI's for Aardvark I2C/SPI Host Adapter to Aardvark OEM I2C Host Adapter.
    Before we decide  to buy Aardvark OEM I2C Host Adapter we just want to make sure that we can use it.
    Best Thanks.
    Jessie

  • Upnp service support in labview

    I'm looking for info on uPnP support in LabVIEW. Anyone know of any existing support for this out there? Any help is appreciated. Thanks, JH

    Hi Jason, I have attached a .llb (V7.1) which should discover UPNP devices on the network. The ini file will need modified on the NI folder with the following line:
    SocketSetReuseAddr=TRUE
    Also, during development I would disable the Win XP firewall.
    The vi is taken from NI's examples under networking with a couple of mods - nothing spectacular I'm afraid. After discovery you can use the NI web browser (specified IP and Port number for the device) and XML parser to extract the info from the xml files that each UPNP device holds. This should give you all the actions and variables required to control the device. I used TCP vi's for this action - the only pain was formatting the SOAP messages to the correct format.
    Hope this may be of some help!
    PC.
    Attachments:
    UPNP DISCOVER Root Devices.llb ‏1051 KB

  • Usrp driver 1.3 do not support for Labview 2013 64 bit ??

    Hello, dear all
    Is anyone install the latest USRP driver 1.3 for LV 2013 64 bit ?  I found there is no version for 64 bit LV 2013. 

    Currently the 1.3 driver supports only LabVIEW 2013 32 bit (even on 64 bit computers.)
    The LabVIEW 2014 version will support 64 bit and will be available to download very soon.
    Please check here within the next week or so:  http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/ssnav:drv/q/usrp/

  • Install datasocket support for labview 8.6

    Hi,
    Can I get a link to download a Datasocket Support for Labview 8.6 or higher?
    Thanks
    Ken

    Installing the Latest Version of DataSocket and DataSocket Server
    Problem: 
    I would like to download and install the current version of National Instruments DataSocket and/or DataSocket Server on my computer. Where can I find the latest version of this to download it from National Instruments' website?
    Solution: 
    The latest release of the DataSocket libraries and the DataSocket Server is installed with the LabVIEW Run-Time Engine. Go to the Drivers and Updates web page at ni.com and search for "LabVIEW Run-Time Engine" and sort by Version to find the most recent version of the LabVIEW Run-Time Engine.
    http://digital.ni.com/public.nsf/websearch/40295802535E31B686256E91001859AB?OpenDocument
    Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
    If you don't hate time zones, you're not a real programmer.
    "You are what you don't automate"
    Inplaceness is synonymous with insidiousness

  • Gpib.dll and labview

    I copy a VI program to my automation system(window95 16-bit and labview5.1).This VI program is writed by labview4 in window3.11.When I open it,there shows "GPIBW.DLL is not a 32.bit.dll" .How can I use those old VI programs in my new operating system?

    I appears that you're going to have to update the old program to use the gpib functions in LabVIEW 5. I've seen this problem happen when an entire hierarchy was saved - including vi.lib files. If you do have an llb with older NI gpib functions in it, delete them from the llb and the next time you open the top level VI it should open the newer LabVIEW 5 gpib functions assuming that they're the same name.

  • NI-DNET support for LabVIEW 2013

    We are using currently NI-DNET 1.6.6 with LabVIEW 2011. I installed now also LabVIEW 2013 on my computer and tried to sync the set of drivers with my LabVIEW 2011 installation.
    Well, it seems that NI-DNET doesn't support LabVIEW 2013, at least officially. The NI-DNET and LabVIEW Version Compatibility shows that NI-DNET 1.6.6 supports LabVIEW 2011 and NI-DNET 1.6.7 supports LabVIEW 2012.
    The NI System Driver Set November 2013 list NI-DNET 1.6.7 as part of the driver set. When I try to install it, there is no LabVIEW 2013 support.
    My question is actually, if there is a plan to include NI-DNET support for LabVIEW 2013 or later in the driver set?
    I copied the vi.lib\DeviceNet and vi.lib\nidnet directories from LabVIEW 2011 to 2013 and I can load my programs without any problems. I still didn't build an executable and didn't run them on the test fixture, but the projects can be loaded in LabVIEW 2013 without any brocken VIs. Should I expect any problems running LabVIEW 2013 with the NI-DNET 1.6.6 or 1.6.7 driver?
    Nick
    Solved!
    Go to Solution.

    I would update our drivers right away, but unfortunately the NI-Industrial Communications for DeviceNet doesn't support the PCI-DNET cards. We have probably close to 30 of those in the test fixtures. So, we need to use the NI-DNET 1.6.x driver anyway.
    It will be nice if the NI-DNET installer can copy the NI-DNET VIs and supporting files to any LabVIEW version, well maybe any 201x. I hope until 2020 we can replace the old cards :-)
    Nick

  • How do I interface a computer to the HP8753D Network Analyzer (NA) via a GPIB cable using Labview?

    Hi,
    I am a new beginner to LabVIEW. Right now, I am trying to acquire data from the HP8753D Vector Network Analyzer (VNA). However, I don't think I even managed to get past the first step.
    I tried to create a simple VI with only a single READ GPIB and a WRITE GPIB both to the address 16 (default for HP8753D) with the command IDN?;. I output the result from the READ GPIB to the a string indicator but the front panel displayed boxes and unrecgonized characters.
    The NA didn't even showed that it was communicating to the computer at all (No LED lit up).
    I have also varied the byte size from 200 to 2000 but I still did not get the res
    ult.
    I really need help on how to interface the VNA and my computer together. I have a strong feeling that the VI I constructed is too simplified (attachment below). If you know the solution, please help. I really would like to get past this first stage of first getting the computer and the device to communicate first.
    Thank you.
    Attachments:
    LabVIEW_VI.gif ‏4 KB

    Hello,
    There are several things to check. First make sure that you are using the correct GPIB or VISA resource name. If you are using GPIB the name that you use should be something similar to:
    GPIB0::2::INSTR where 2 is the primary address and 0 is the device number.
    Then you need also to check which commands are accepted by your device. It is a good idea to start in MAX (Measurement and Automation Explorer) by right clicking in the device.
    Another thing you might want to try is to download the driver the instrument driver for this HP8753D that you have.
    You can find it in the following address:
    hp8753D Instrument Driver
    H
    ope this helps
    Ricardo S.
    National Instruments
    Message Edited by Support on 12-08-2006 01:36 PM

  • Traditional DAQ support in LabVIEW 2010?

    Hello,
    Been researching this a while and I must admit, I am quite confused. I am trying to run a program written in LV 7.1 using traditional DAQ vi's in LV 2010. I think what I need are traditional DAQ drivers, but I cannot find the correct drivers. Plus I'm unsure if I will run into compatability issues. If someone could point me in the right direction I would very much appreciate it!
    Old machine:
    PCI 6040E
    LV 7.1
    Win XP
    New Machine:
    PXI 6251
    LV 2010
    Win 7
    Thanks
    Solved!
    Go to Solution.

    Dirk H. wrote:
    ...  Finally, due to errors, I was forced to LabVIEW 2010.
    What errors?
    Finally, due to errors, I was forced to LabVIEW 2010.  Now I'm looking for the traditional DAQ(to minimize my work) for the old software.
    LabVIEW 2010 would require Traditional DAQ 7.4.4. http://digital.ni.com/public.nsf/allkb/F4E76EC05118F72D8625773000672298
    Dirk H. wrote:
    I have a PCI-6503 and a PCI-MIO-16E-4(along with a PCI-GPIB board).  ...  Am I forced to upgrade any or both of the DAQ cards?  All of the cards appear to be installed successfully by viewing them in Measurement and Automation.
    This page lists the required DAQ software for each device: http://zone.ni.com/devzone/cda/tut/p/id/6910. That page indicates both of your devices are supported by Traditional DAQ 7.4.4.

  • IOTECH GPIB card and Labview

    I wish to use IOTECH's Personal488 GPIB card for measurement on HP8510C Network Analyser.  This works fine with QBASIC or C programming.   Can I use Labview for this application using this card ?

    Maybe. From doing a search of the forum, I got the impression that at one time, the IOtech driver replaced the NI GPIB driver and used the same low level GPIB commands. I have not found any reference to a VISA driver for the IOtech board and if there isn't one, you will not be able to use the 8510C driver. I think NI purchased IOtech a few years ago but the place for technical support is IOtech itself. You should really contact them about using their card with LabVIEW. I did a quick search of their website though, and cannot find this card listed as a current product and their GPIB driver has not been updated in 8 years.

  • How to use a GPIB card's LabView drivers to communicate with the card?

    I have an axiomtek AX4810P PCI-GPIB card and i have aquired LabView drivers from the manufacturer.
    This has put VI's for the GPIB functions on the 'user palette' but i can't work out how to use them to communicate with the card. can anyone help? please.

    LS,
    Thank you for contacting National Instruments.
    Unfortunately, since you are not using a National Instruments GPIB card, I do not have access to the drivers that were provided to you by your card's manufacturer. I would suggest contacting Axiomtek directly to obtain support using their drivers.
    However, I did write a small VI that demonstrates how to use similar National Instruments drivers with a National Instruments GPIB card. Keep in mind, this example VI is not intended to work with your particular card. The drivers you obtained from Axiomtek may have similar functions, however, and you can use my VI as a guide. My VI allows you to send a command to an instrument at address 2 on the GPIB card.
    Hope this helps!
    Matthew C
    Applications
    Engineer
    National Instruments
    Attachments:
    GPIB_Communication.vi ‏23 KB

  • How to configure the GPIB controller in LABVIEW or MAX to send UNLISTEN and UNTALK when each message ends?

    In a PC to PC GPIB configuration, one PC is used as a non-controller and it reads either LACS or TACS status bits continuously. It apears that the controller PC does not send UNTALK and UNLISTEN at the end of each message. The non-controller reads and writes therefor times-out.
    What is the correct message synchronisation for a non-controller?
    I use Labview 6, PCIIA, WIN98SE.
    Thanks.

    Are you using LabVIEW as the controller, non-controller, or both?
    NI-488.2 does have a configuration option to enable unaddressing. I am not sure of where it is in LabVIEW, but if you search for unaddressing, you should find some information on it. With unaddressing, NI-488. will unaddress the device after communicating with it.
    If you are not using LabVIEW as the non-controller, National Instruments does have a software package called NI-Device that may help. This is an API designed for non-controllers. It does not currently have a LabVIEW interface. It works under C++ with a PCI-GPIB board.
    A third option is to rewrite your device application. Your device should really not care about TACS or LACS as you read them from the status register Your device
    should only look for LACS, DCAS, and perhaps DTAS (if you desire triggering). When it is LACS, it should read data. After a read has completed, it should interpret the data and get ready for a response. It is only at that moment that the device should look for TACS (and DCAS). It is hard to put a flowchart here, but if you design the flow of a standard instrument, you will see some patterns about when to look for certain status bits.

  • "Import string" method not supported in LabVIEW 7.1

    We have made an application that support multi-language (English, French, etc.). In LabVIEW 6.1, we used the "import string" VI method to support this option. The method was executed just before to open front panel. The code was based on this example found in NI Developer Zone:
    Translation/Localization Tools in LabVIEW
    (http://sine.ni.com/apps/we/niepd_web_display.disp​lay_epd4?...
    But surprise in version 7.1, this method can't be loaded without the diagram block. So the built application doesn't support it! It works only in the development interface. Why this change?
    If someone has an idea to solve this, let me know.

    If you build that example into an EXE under LabVIEW 7.1, it should work fine as long as you add the non top-level VIs as Dynamic VIs and add the language files as Support Files when you create the executable, making sure to specify in "Custom Destinations" that you want the string files to end up in the same directory as the EXE.
    Your point about the method requiring the block diagram is correct, according to the help for the method. However, I think the diagrams will be available to the run-time engine as long as you haven't purposefully removed them prior to creating the EXE in the manner described above. Maybe someone else can chime in on this point, because I know the App Builder changes a lot with every new major LabVIEW version (and sometimes, with minor versions too!).
    In any case, I just did a test where I downloaded the example you referenced, created a .BLD file as I indicated above, and got a successful executable that was able to use the Import VI Strings method to load the desired language at run-time.
    Regards,
    John

  • I have some B/W video cameras(analog) are they supported by Labview

    i have some B/W video cameras that I wanted to use with LabView but they are not in the list of supported cameras under LabView, but they are still very new and they work great and they are small and light weight which are two important things that I need. Can I still use these? Or should I look into buying some new ones? The website for these cameras is www.x10.com, model number SC21A, thanks.

    Hi magnusrules,
    The National Instruments Framegrabbers can adquire video formats like RS-170 or CCIR, it depends on the model of the framegrabber. Here is information about the analog video signals:
    http://zone.ni.com/devzone/conceptd.nsf/webmain/0c19487aa97d229c8625685e00803830
    I saw the datasheet, but I did not find the type of signal. It says RCA, so maybe this can be of some help:
    http://digital.ni.com/public.nsf/websearch/A247A92A91FDEFAE86256BA50051F28B?OpenDocument
    http://sine.ni.com/nips/cds/view/p/lang/es/nid/11356
    Since the camera has a RCA connector, and it's BW, it could be RS-170, but we need to confirm it with the manufacturer.
    Tania Lozoya

Maybe you are looking for