(Q) Labview and HP-IB card

Hi,
I have a problem in using LabView with HP-IB card (HP82341D).
The GPIB-search proram of national instrument can not find the interface
card. I also heard that HP-IB cards are not compatible wit LabView. Is it
true? If not, how I can use Labview 5.1 with the HP-IB card? Thank you in
advance.

On Sat, 6 Nov 1999 02:58:30 -0500, Eun Sang Choi
wrote:
>Hi,
>
> I have a problem in using LabView with HP-IB card (HP82341D).
>The GPIB-search proram of national instrument can not find the interface
>card. I also heard that HP-IB cards are not compatible wit LabView. Is it
>true? If not, how I can use Labview 5.1 with the HP-IB card? Thank you in
>advance.
Did you try out installing the HP-VISA drivers and using the LabView
VISA functions? By using VISA I managed to use a HP-GPIB card with
LabView, but I am not sure if it was the HP82341D.
As far as I remember, you must do the following to use HP-VISA:
After installing LabView install HP-VISA on your computer.
After this you must start the Solution wizards/instrument wizard to
prepare HP-VI
SA to run with LabView, as far as I remeber you will be
asked if you want to use HP-VISA with LabView. After this you should
be able to communicate with the HP card by using the VISA-functions.
I hope this will help you.
>
>
>

Similar Messages

  • Analogic acquisition with Labview and National Instruments card

    I need to acquire 2 analogic signals simultaneously. I use version 4
    (maybe 5) of Labview, with a National Instruments data acquisition
    card (BNC-208x). I want to save the 2 signals in a text file. Does
    anyone could send to me a diagram (vi) for doing that.
    Thank you very much.
    (my email: [email protected])

    True simultaneous sampling is possible with only a few types of DAQ cards. I believe BNC-208x is like the current BNC-2xxx series and is nothing more than a adaptor to the actual DAQ card inside the PC. If you can live with the small delay between channels that the majority of DAQ boards has, then there are a number of shipping examples that can help you. Look for the Cont Acq&Graph examples and Data Logger to Spreadsheet File.

  • LabView and Keithley PC488-Card

    Hi,
    I hope somebody can solve my problem: I have a Keithley PC<>488
    GPIB-Interface installed and want to get it work with LabView. There are
    compatibility-drivers shipped with the interface, but they don't work.
    The driver is installed, but I can't communicate (through LabView) with
    the PC488.
    My System runs under Windows NT. I can exclude hardware conflicts,
    because under DOS (test programs that come with pc488) communication
    works.
    Thanks,
    Michael

    Michael.Buettner wrote in message
    news:[email protected]..
    > Hi,
    >
    > I hope somebody can solve my problem: I have a Keithley PC<>488
    > GPIB-Interface installed and want to get it work with LabView. There are
    > compatibility-drivers shipped with the interface, but they don't work.
    > The driver is installed, but I can't communicate (through LabView) with
    > the PC488.
    > My System runs under Windows NT. I can exclude hardware conflicts,
    > because under DOS (test programs that come with pc488) communication
    > works.
    >
    > Thanks,
    > Michael
    Hi Michael
    I have had the same problem.
    My keithley card is an old XT slot card
    This card is a CEC card .
    On http://www.cec488.com/gpibupgd.htm you
    can download the driver to
    simulate an NI-Gpib card.
    Than you must install the driver with ADD new Hardware , Find Capital
    Equipment Corp. etc.
    THe LAbview GPIB.vi works fine.
    C.J.Wisman
    Holland.

  • SPI communicat​ion protocol with LabVIEW and 6062E PCMCIA Card. Is it possible?

    Hey people. I'd like to know if it's possible to get SPI communication with 6062E card, and if there is any example of that use.
    Thank you!

    Good afternoon,
    With this hardware NI DAQCard-6062E (for PCMCIA) has inputs / outputs digital and analog, but has hardware that makes USB-8451 communication with SPI. Below is the link to the Hardware. Any questions please contact us.
    NI USB-8451
    http://sine.ni.com/nips/cds/view/p/lang/en/nid/202​368
    graciously
    Mauro Vera
    Applications Engineer
    National Instruments

  • I have installed successfuly Nidaq692.exe and LV5Fra.exe drivers for LabVIEW AND PCI-6110 card

    Unfortunately, I didn't find the data acquisition functions to acquire data from PCI-6110 through LabVIEW.
    How can I do to find VI data acquisition in Labview.

    Is the Data Acquisition palette completely missing? It may be that if you initially installed LabVIEW without NI-DAQ, that none of the VI's got installed. You may have to reinstall at least part of LabVIEW.

  • "How to use an Appplicom card with Labview and a Seimens PLC"

    Hi, I am using an applicom card type PCI1500-PFB to communicate with a Seimens S7-300 CPU315-2DP plc. I am using this simply to display in a labview front panel the outputs of the plc and may in the future use switches on the front panel to control the inputs of the plc. How do I do the communication? I have setup the applicam card and have comms with the plc I think. I am trying to use data socket to communicate to the plc via the applicom card. Any suggestions?
    Thanks
    Tom

    There�s a fair bit of documentation on NI�s site regarding the Applicom card.
    The following doc does a pretty good job summarizing Applicom's PCCONF and PCINIT, and the use of ReadWait and WriteWait to ensure you�ve got communication with the between the PLC and the Applicom card:
    http://zone.ni.com/devzone/conceptd.nsf/2d17d611efb58b22862567a9006ffe76/5913e03f551de3f786256a32005b4586?OpenDocument
    Since it doesn�t sound like you�re using the LV DSC module, you can stop reading once it gets into connecting to Lookout Objects.
    Once you�re sure you�ve got comm, you can do some quick tests in LabVIEW using front panel datasocket connections as shown on page 11-12 of the following:
    http://www.ni.com/pdf/manuals/323241a.pdf
    From there, it all depends on
    the complexity of your system. If simple, you could just stay with front panel connections, or you could move to programming with the Datasocket Read and Write functions.
    ... and if you get to the point that Datasocket is too slow and cumbersome, you might want to look at the LV DSC module:
    http://ni.com/labview/labviewdsc/what_is.htm?node=10418
    =====================================================
    Fading out. " ... J. Arthur Rank on gong."

  • Using the In port.vi and Out port.vi in LabVIEW access my the Cards(Home made)

    Hi Everyone,
    I have got the Cards (home made 8 bit and 16 bit ) plug in at slot ISA my PC (I am using the commands inport and outport (addressed with 318-31A Hex) in C language to access very good).This now,I want to use LabVIEW language to access data directly to Port at my the Cards. In LabVIEW, Can I access data to port using the In port.vi and Out port.vi located in the Advance?
    My English is poor, you don't laugh when you read it.
    Thank you a lot.

    SachaE wrote:
    > LabVIEW 7.0 cannot use the built-in In/Out Port VIs with a 32-bit
    > address. Instead, you will have to use the versions of these VIs found
    > in previous versions of LabVIEW.
    Are you talking about physical memory access here? If so that is
    something entirely different. The Intel x86 architecture uses a separate
    IO address range which is entirely separate from memory space.
    And at least up to the first Pentium models it was definitely never
    possible to address more than 16 bits for IO address space.
    This of course has gotten a little more complicated nowadays with many
    PCI boards being actually mapped into memory address space instead of IO
    address space. So eventhough a PCI board is more like an IO device it
    often is accessed in the memory space.
    > Actually, the In Port and Out Port VIs are intended for 16-bit port
    > I/O and not for writing to arbitrary addresses in memory. For this
    > reason, writing to 32-bit addresses never should have been allowed.
    I think the VIs to access physical memory addresses were different than
    the ones to access IO addresses. And yes it is definitely not a good
    idea to have an application poke into physical memory as it could
    completely screw the system to the point where you couldn't start it
    anymore. Also IO devices mapped into memory address space are almost
    always typically plug and play devices, so their address is not really
    fixed and you need to do quite some more work on OS level to enumerate
    your hardware and find the resources used before trying to access it.
    This is something not really suited to try to do in LabVIEW and
    therefore should be at least implemented as DLL but in fact anything but
    a device driver is a very bad kludge.
    > One possible work-around would be to use NI-VISA to perform
    > register-level programming. NI-VISA gives you access to any PXI/PCI
    > board, not only NI boards, and can be used to access the board's
    > registers.
    >
    > http://zone.ni.com/devzone/conceptd.nsf/webmain/ADF3152837E2B4A486256B5600642AC7?opendocument
    Thanks for this. Didn't now this existed in NI-VISA. Will check it out.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Controling heating/cooling element with labview and usb 6008 DAQ card

    Greetings All
    I'm looking for a heating/cooling type of element that I can control with labview and my usb-6008 card. Heating/Cooling will just be for clean water and the temperture range will be from 0 C to 100 degree C.
    Thanks
    The heating and cooling elements can be seperate products. Any recommendations

    A simple kettle element will of course be sufficient for upto 100°C
    To get the temperature down you need a cooling system, what springs readily to mind of course is a refrigerator.
    Just a note of warning, water and electricity are dangerous bed fellows.
    On that note perhaps one of those vortex air units would be safer - they blow hot in one direction and cold in the other, nominally to 100°C
    see: -
    http://www.airtxinternational.com/how_vortex_tubes_work.php

  • Labview and engine dyno (newbie)

    I am totally new to labview. I recently purchased various parts from a
    "Mustang" automotive engine dyno. I got the eddy current unit, the
    load cells, and shaft encoders. I was unable to get the control unit
    and a/d cards for the computer so I am researching options, and
    looking for some help on the computer end. My current plans are to
    hook it all up manually with a hydraulic load cell and manual current
    control but down the road I'd like to ad computer control when I can
    afford it.
    A few questions: Will labview let me program an interface to read all
    my sensors? Will an older copy of labview work? (maybe someone has an
    older copy to sell?) What do I need to make the load cells work with
    the computer? Do I need an amp of so
    me kind? (there is an amp card in
    the junction box) I'd like to be able to control the eddy current
    unit with the computer also. Any feedback would be helpful. I'd like
    to startout simple and maybe ad more sensors later for airflow, fuel
    flow, thermocouples. I'm also doing this on a budget since I don't
    have some high $$$ corporate sponsor. Thanks in advance.
    Bruce
    Please feel free to email me off the newsgroup.
    "advanced dealer in the great material continuum"

    In article , smcfarl1
    @rochester.rr.com says...
    > I have used the microsoft activex xml components to do what you are
    > describing. The LabVIEW activex interface does not
    > keep track of the open references so you have to be very carefull about
    > closing all references.
    > Stu
    >
    > > --
    > > After three days in the desert fun
    > > I was looking at a river bed
    > > And the story it told of a river that flowed
    > > Made me sad to think it was dead
    >
    >
    >
    I've looked on the microsoft site but I didn't find anything. Could you
    be a little more specific? The only XML related activex I've found (via
    google) is Redix, nothing by microsoft.
    Thank you for your patience
    eXistenZ
    After three days in the desert fun
    I w
    as looking at a river bed
    And the story it told of a river that flowed
    Made me sad to think it was dead

  • Troubles with LabVIEW and the SR830 Lock-in Amp.

    i'm quite new to LabVIEW and am trying to use the sr830 instrument drivers
    to control the Lock-in from a computer, but the instrument drivers don't
    seem to want to send or recieve any data. if anyone who is more proficient
    in VI programming couild help me out with this, i would greatly appreciate
    a response. thanks.

    Lackey wrote:
    > i'm quite new to LabVIEW and am trying to use the sr830 instrument drivers
    > to control the Lock-in from a computer, but the instrument drivers don't
    > seem to want to send or recieve any data. if anyone who is more proficient
    > in VI programming couild help me out with this, i would greatly appreciate
    > a response. thanks.
    Are you using the instrument driver downloaded from Nat Inst ??
    If you are this thing looks terrible, but should work.
    You could try building a simple VI to see if all the communication is working
    properly.
    Check to make sure you have the correct GPIB address and that all the cables
    cards etc are properly connected and working.
    Kevin KEnt
    Attachments:
    Kevin.Kent.vcf ‏1 KB

  • MAX does not detect my PXI-5122 and PXI-6551 cards in a PXI-1045 chassis.

    I have been using a PC with MXI-3 to PXI-1045 chassis to develop LabView TestStand code.  Things are fine on my development PC.  [Software configuration report attached nireport_rich.txt].
    I have a 2nd PC set aside to test my deployment packages.  I installed a GPIB card and MXI-3 card in my deployment test PC, and loaded a bunch of hardware drivers.  [Report attached nireport_depPC_0006.txt]
    All the PXI cards are found just fine when my development PC is connected, but when I power up my deployment PC (with MXI-3 connected to the 1045 chassis) -- I can't import the development configuration [exported from development PC] because the deployment PC does not see the PXI-6551 DIO card in slot 6 [PXI6::10::INSTR] and the PXI-5122 card in slot 13 [PXI8::15::INSTR].
    I keep reviewing the hardware driver versions installed, and the only small difference that I see at this point is that the deployment PC has a slightly older version of NI-Switch.
    Anybody have any ideas of what I can try next?  I'm out of ideas.
    . . . . hmmm, can't seem to attach more than one file, so here's the software info on the deployment PC
    NI Software Information:
    CVI Run-Time 7.0.0.395
    NI-DAQ 7.3.0f1
    NI-DAQmx 7.3.1f0
    NI Script Editor 1.1
    NI-DMM 2.3.1
         Soft Front Panel 2.3.0
    NI-FGEN 2.2.1
         FGEN Soft Front Panel 2.2
    NI-488.2 Software 2.30
    IVI Compliance Package 2.2 2.2
    LabVIEW Run-Time 7.0
    Measurement & Automation Explorer 3.1.1.3003
    Measurement Studio 6.0
         For Visual Basic 
              ActiveX User Interface 7.0.0.344
              ActiveX 3D Graph 7.0.0.344
              ActiveX DataSocket 4.2.2.1
    NI-USI 1.0.2
    NI-HSDIO 1.2.1.3
    NI-HWS 1.2.2.0
    NI-PAL Software 1.8.2.0
    NI-SCOPE 2.7.0f5
         SCOPE Soft Front Panel 2.1.0
    NI Spy 2.2.0.12
    NI-SWITCH 2.30.49153
    NI-TClk 1.2
    TestStand 3.1
    NI-VISA 3.2
         visa32.dll 3.2.0.19
         NiVisaServer.exe 3.2.0.19
         NIvisaic.exe 3.2.0.19
    LabVIEW Run-Time 7.1

    Hello Maggie,
    Appreciate your assistance and reply.
    The pxisys.ini and pxiesys.ini files are modified by me with referring to
    1)PXI System Alliance PXI-2 SW spec,
    2)PXI-6 SW spec,
    and 3)pxisys.ini pxiesys.ini generated by MAX v5.3.0f0 with NI PXIe-1075 + NI PXIe-8133.
    The content in pxisys.ini/pxiesys.ini generated by MAX looks like simple. Consequently, I modified and checked it line by line according to actual hardware of PXES-2590+PXIe-3975. Then, MAX just list devices as described in the first post. I tried to find the root cause but in vain.
    Is this minor issue can be related any incorrect tag lines in pxisys.ini or pxiesys.ini I posted?
    Is any suggestion tests I can do to troubleshoot root cause?
    Looking forward your reply.
    Cheers,
    KL Tseng

  • Anyone got experience with LabView and JTAG ?

    Anyone got experience with LabView and JTAG ?
    Especially in system programming of Altera and FLASH

    Yes, I've actually driven JTAG using DIO, but this was a project in itself.
    I guess you're just wanting to get the job done! I'm currently evaluating
    gear to do the same job myself, in addition to interconnect testing. I've
    been looking at JTAG Technologies equipment. They do PCI/PXI cards and the
    SW, with a LabVIEW interface.
    They're at:
    www.jtag.com
    You'll need to be sitting down when you get their quote though - their development
    system costs about the same as a decent car!
    Cheers
    -Sean.
    [email protected] wrote:
    >Anyone got experience with LabView and JTAG ? >Especially in system programming
    of Altera and FLASH

  • LabView and Micro-Pump

    hello guys
    i am trying to automate a micro-pump by using labView. can you please tell of a hardware card that i must use in the computer?? and are there any examples regarding a LV program that can program and automate any device.
    Thanx in advance
    Nikhil
    Many more Kudos to give

    You need to look for DAQ cards over here. You won't be able to find a card that outputs a 12V analog signal; all of them output a maximum of 10V. But, the digital cards have the capability to go higher. If you want to output an analog signal, then you will need to use an external amplifier. After you choose and install your card, you install the DAQmx driver which installs loads of LabVIEW examples that you can use. If you want, install the DAQmx driver right now and have a look at the examples in LabVIEW. (Help -> Find Examples). That should give you an idea of how to get started. Remember, after you install the DAQmx driver, you also have the capability to simulate a device and test it's functionality in LabVIEW.
    Adnan Zafar
    Certified LabVIEW Architect
    Coleman Technologies

  • Labview and profibus

    Is it possible to use labview with a profibus card in the computer?
    I have a Hilscher card that I would like to use with labview, but I have no
    idea how to make it work.
    /david

    The easiest is to use NI cards, then you get LabVIEW drivers...however we have used Hilscher too - but then we had to write a wrapper around their Cif32dll.dll.
    Attached is a file containing VIs to open, close, read and write to the Hilscher profibus cards using that dll. I have not included the dll, you will need to put that dll together with the VIs.
    The VIs are not a general library, it's something made by a collegue of mine for internal use to solve a specific task, however unless someone has made a general solution at least this will give you an idea of how to move forward...
    Mads
    MTO
    Attachments:
    Hilscher_Profibus.zip ‏85 KB

  • Synchronized sampling from PCI-mounted card and PXI-mounted card

    Hi, everyone
    My latest problem concerns sampling. I need to acquire samples from around 20 different (differential) channels and my PCI-card (NI-6224) has only 16 differential inputs. I do, however, have another card (NI-6229) mounted in our PXI-system. This PXI-system seems to be connected to the computer with a network cable. When i try to perform synchronized sampling from these cards with the PCI-card as master I get an error message saying that these cards cannot cooperate. There must be a way to do this...?
    I'm using DAQmx and labview 8
    Einar

    Hello!
    It is just a matter of taste I guess but I think PXI chassis and synchronization is more convenient since you don’t have to care about physical wires or a RTSI cable.
    Data will be stored at your host since it is the Windows application and LabVIEW with its DAQmx Read functions that actually transfer the data from the buffer created by DAQmx to LabVIEWs memory space in RAM.
    Regards,
    Jimmie Adolph
    Systems Engineer Manager, National Instruments Northern Region
    Bring Me The Horizon - Sempiternal

Maybe you are looking for