PCI-GPIB compatible with Genrad 1687-B Megahertz LC Digibridge?

I am trying to use a Genrad 1687-B Megahertz LC Digibridge with a recently purchased NI PCI-GPIB card.
The Digibridge works normally from the front panel. The GPIB card and the cable work normally with another GPIB instrument.
However, the "Measurement and Automation Explorer" does not detect the instrument. When I "Scan for Instruments", the pretty animation displays for a while and then the scan fails because it did not find any instruments.
Is there possibly an incompatability between this instrument and the newer GPIB specification? The instrument documentation mentions IEEE 488-1978 (not 488.1 or 488.2).

I doubt that your instrument is incompatible with the newer GPIB specification. Do you get any indication of an error on the instrument following a Scan for Instruments? Do you know what the instrument's GPIB address is? It must be a different address than the GPIB controller. The address of the GPIB controller is probably 0.

Similar Messages

  • Is the Linksys WMP54G PCI adapter compatible with the Airport Extreme?

    I have set up my network using the Airport Extreme and am able to connect my iMac, my Macbook Pro, and two Windows laptops without difficulty. However, the two Windows desktops that I have are using the Linksys PCI wireless adapters (WMP54G) and they both do not even see my network. They are able to see the neighbors' networks just fine, though.
    I called Linksys and they assure me that the cards are compatible with the Airport Extreme. Linksys advised me to adjust my settings or call Apple for support. I have tried configuring the Airport, but I don't really know what settings to change. Has anyone else successfully connected using this adapter? If so, could you help me connect? Thank you very much!

    Ok, thanks! Try the following setting on the WMP54G PCI adapter:
    o Look at page 12 of the adapter's User Guide for reference ...
    o For Security, select WPA Personal
    o For Encryption, select AES
    If this doesn't work, try reconfiguring the AEBSn for WPA Personal (not WPA2 Personal), and then make the following change on the adapter:
    o For Encryption, select TKIP

  • Is PCI-6723 compatible with BNC-2090A?

    Hi everyone, I'm currently working in a project where I'm required to use both a PCI-6723 connected to a BNC-2090A....In the 6723's datasheet only the BNC's 2110 and 2115 versions are suggested. Does anyone know if I can still use the one I have without any problems? What I mean is, is the 2090 still compatible, do I have to make some adjustments to the hardware/software, or it's just a hopeless mission?
    Any tips are good, thanks for the help.
    Solved!
    Go to Solution.

    Hi Jason
    BNC-2090A is specifically for X-Series, E-Series, M-Series, and S-Series.
    The PCI-6723 is part of the Analog Output Series and for this reason BNC-2090A not support this board.
    The best BNC connector block for it is the 2110. This connector block lists the Analog Output Series as a supported series.
    Regards
    André Bassoli Napoleão
    Application Engineering
    National Instruments Brazil

  • Is the IMAQ PCI-1409 compatible with the JAI CV-M30 camera?

    Does the IMAQ PCI-1409 support the double speed and partial scan modes of the JAI CV-M30 camera?

    In theory the PCI-1409 should work with the JAI CV-M30; however, National Instruments has not tested that particular camera with our PCI-1409. Since the camera can output the pixel clock, if necessary you could put the PCI-1409 in External Lock mode to lock to the camera signals. You may also need to adjust some of the settings in MAX.
    If you need more direct assistance on this matter, please contact National Instruments technical support directly.
    Best regards,
    Dawna P.
    Applications Engineer
    National Instruments

  • PCI-GPIB Card with Visual Basic gives blue screen and re-boots PC

    The application makes the "ibsic" call then "ibln" to find devices on the bus. Running the VB program the first time is fine, but if you end the program and re-run a second time, you get a blue screen and the PC reboots when the program reaches the lines that make the first call to the NI-488 functions. If you close out of VB and then restart VB, everything is OK again.
    What is wrong?

    Hi,
    Here's an article that describes the most common blue screen when using VB:
    Why Does My Windows 2000 or XP System Crash When I Use Visual Basic to Program GPIB?
    Hope this helps
    DiegoF

  • GPIB-USB-HS vs PCI-GPIB

    Hi,
    I have LabVIEW code that is using VISA to communicate with a PCI-GPIB interface card/instruments. I replaced the PCI-GPIB card with a  GPIB-USB-HS interface for ease of use.
    Now the code does not work...I thought the code(VISA session) should work for both interfaces? Do I need VISA for GPIB-USB-HS too?
    What is wrong?
    Thanks for your help...
    NY

    Look in MAX (Measurement & Automation Explorer) to see if the USB-GPIB shows up in the list of devices.  If it does, try to communicate with an instrument from there.  If it doesn't, your drivers were not installed properly.  If you can talk to instruments from MAX,  you should be able to do so from Labview also.
    - tbob
    Inventor of the WORM Global

  • Is this video graphic card compatible with the motherboard?

    Hello,
    I only have one question, is  nVidia GeForce GT430, 1024MB, GDDR3, 128bit, DVI-I, HDMI, PCI-E compatible with MSI K9N neo v2 ?
    The slot for the graphic card : PCI Express 2.0 x16
    For the motherdoard: • 1 PCI Express x16 slot
                                 • 2 PCI Express x1 slots
                                 • 3 PCI slots, support 3.3V/ 5V PCI bus Interface
    Will it work? Does it lose performance?
    Thank you very much

    Yes, should works
    Quote
    Does it lose performance?
    no

  • I have problems with pci-gpib card under windows me, What I need to know what to do in order to fix this problems?

    Hi, I have installed a pci-gpib card in my computer, I have a problem with
    installation, the message of troubleshooting wizard is as follow:
    "One or more missing GPIB interfaces.
    There are several reasons why you might encounter this problem:
    Reason: Your GPIB interface is incorrectly installed.
    Solution: Please verify that your GPIB interface is correctly installed
    and rerun the NI-488.2 Troubleshooting Wizard.
    Reason: You are using a non-Plug-and-Play interface (e.g., AT-GPIB/TNT,
    GPIB-PCII/IIA, GPIB-ENET) and you did not use the Add New Hardware Wizard
    to add the interface to your system properly.
    Solution: Click th
    e Add Hardware button and the Add GPIB Hardware wizard
    will guide you through the process of adding GPIB hardware.
    Reason: For the GPIB-USB and GPIB-1394, the host controller (USB or 1394)
    must be working properly in order to use the GPIB interface.
    Solution: Click on the System Details button for details about the USB and
    1394 host controllers.
    Reason: For the PCMCIA-GPIB and PCMCIA-GPIB+, the PCMCIA host controller
    must be working properly in order to use the GPIB interface.
    Solution: Use the Windows Device Manager to verify that your PCMCIA host
    controller is functioning correctly. Start the control panel by selecting
    "Start>>Settings>>Control Panel", open the System icon and select the
    Device Manager page. If you select "View devices by type", you can look at
    the PCMCIA socket properties to ensure it is correctly enabled."
    And on system details the message is the next:
    "USB Driver type: USB universal host controller"
    "This version of windows does not su
    pport IEEE 1394."
    I am using Windows Me, so i want to know what i need to do to fix this
    problems.
    Best regards.

    If you have a PCI-GPIB card, you needn't worry about the USB port or whether or not Windows ME supports 1394. All you need in NI-488.2 version 1.70 from National Instruments. Install this driver and then insert your card. Windows should detect the card and find the proper driver.
    If this did not happen in the proper sequence, look in the device manager and see if the card was installed as an "other device". If this happens, remove the card in the device manager and have windows redetect it. If this is not a solution, you may consider the ask an engineer page at www.ni.com/ask. Provide as many details as possible.

  • Is the PCI-232/8 compatible with XP?

    Is the PCI-232/8 compatible with XP? The datasheet doesn't indicate XP compatibility.
    Thanks, Alan
    Alan Blankman, Technical Product Marketing Manager and LabVIEW Developer
    LeCroy Corporation
    800-553-2769 x 4412
    http://www.lecroy.com
    [email protected]

    Yes (despite any XP messages you may get).

  • W2K crashes with PCI-GPIB

    I am using a PCI-GPIB card under W2K, with driver version 1.60. All diagnostics
    indicate that the card is functioning correctly, and there are no hardware
    conflicts. I am able to use WaveStar to communicate with the Tektronix 694C
    scope. When using Excel/VBA macros to control an oscope, W2K crashes to
    a blue screen, with the message:
    Hardware Failure
    Please Contact Hardware Vendor
    A hard reset is required to re-start the system. There is no error logged
    by W2K, and using NI Spy reveals no consistent macro command that is causing
    the failure. I have followed all the suggestions in the Troubleshooter,
    Knowledge Base, etc. I have tried a different PCI-GPIB card from an known-good
    system. I have tried this card in a
    different, identical system. Any other
    suggestions would be greatly appreciated.
    Thanks,
    Cory Allen

    I am using a Pentium III 733/Intel VC820 motherboard/256M RAM/Matrox Millenium
    G400 that was built by our IT dept. In addition to the GPIB card, there
    is an Intel PRO/100+ network card, an In-Target Probe (ITP) card, and a SoundBlaster
    Live (which has since been removed, reducing the frequency of the crashes,
    but not eliminating them.). I have tried a variety of PCI slot configurations.
    Thanks,
    Cory
    "Eric Singer" wrote:
    >What type of computer are you running? Please indicate the make and model.>>Thanks,>Eric
    Singer>"Cory Allen" wrote in message>news:[email protected]..>>>>
    I am using a PCI-GPIB card under W2K, with driver version 1.60. All>diagnostics>>
    indicate that the card is functioning correctl
    y, and there are no hardware>>
    conflicts. I am able to use WaveStar to communicate with the Tektronix>694C>>
    scope. When using Excel/VBA macros to control an oscope, W2K crashes to>>
    a blue screen, with the message>>> Hardware Failure>>>> Please
    Contact Hardware Vendor>>>> A hard reset is required to re-start the system.
    There is no error logged>> by W2K, and using NI Spy reveals no consistent
    macro command that is>causing>> the failure. I have followed all the suggestions
    in the Troubleshooter,>> Knowledge Base, etc. I have tried a different PCI-GPIB
    card from an>known-good>> system. I have tried this card in a different,
    identical system. Any>other>> suggestions would be greatly appreciated.>>>>
    Thanks,>> Cory Allen>>>>

  • Problems with Tru64 UNIX 5.1b PCI-GPIB driver developmen​t

    I am using your NI488.DDK product to develop a PCI-GPIB device driver for Tru64 UNIX 5.1b3. I have experience porting other device driver from 4.x to 5.1b and thought that this would not be too hard.  The driver that I have developed loads and configures ok.  It allows for the IBFIND of /dev/gpib0 minor #255 to work fine because a bus table is built for it during the probe/attach. When I try an IBFIND on /dev/gpib_dev/dev1 I get an error from ni_Cp2BusPtr for minor #51 because no table is created for the devx devices during driver initialization. I don't see where this was done in the example ib.c code provided for Tru64 Unix 4.x,  am I missing something?

    This is really an update to my original posting for those of you who may have similar concerns.
    The source code provided as part of the NI488DDK kit is not really a fully functional driver with the same capabilities as they provided in the device driver that they devloped for Tru64 UNIX 3.x and 4.x.  The the "ib" commands supported by the DDK driver is a subset of the entire ni488 suite.  None of the device specific "ib" command are supported, neither is ibask.  Device commands are written to the bus as character strings that contain device addresses and command.

  • Is a PCI-488.2-1M card backwards compatible with the 488-1975 standard?

    Is a PCI-488.2-1M card backwards compatible with the 488-1975 standard?

    IEEE 488-1975 is one of the early revisions of the IEEE 488.1 stardard, other revisions include 488-1978 and 488.1-1987.
    Because the original IEEE 488 document contained no guidelines for preferred syntax and format conventions, work continued on the specification to enhance system compatibility and configurability among test systems. This work resulted in a supplement standard, IEEE 488.2.
    So, both 488.1 and 488.2 support 488-1975
    I checked the link and it is fine, make sure you have the right web browser settings.
    http://sine.ni.com/apps/we/nioc.vp?cid=1233〈=US

  • HP 3478A DMM not seen with PCI/GPIB 488.2

    Hi All,
    I'm really new at this so watch out...  I have an old 3478A which is compliant with the old HP-IB (GPIB) connector and I'm trying to communicate with it using a PCI/GPIB 488.2 card.  I found some drivers for Labview and that's wonderful but it simply doesn't work.  The automation explorer also doesn't see the device.  What am I doing wrong?  I read somewhere that you have to enable some old drivers but I the message was somewhat unclear now I'm just desperate.  Please help someone.
    OS : win XP
    Labview: 7.1
    thanks

    It is possible the cable is faulty. The cables I am using are National Instruments 763061-02 RevC; Type-X2. These cables work on all of the instruments I am using. Check the configuration of your GPIB Card, I have provided screen captures of my current settings that are working for me.
    1. As before use the Measurement and Automation Explorer to get to the GPIB Bus under devices.
    2.Right click on the GPIB Bus and select properties, you should see the following screen.
    3. Click the Configure and on the next screen click Software>> button to see all of the options.
    Try these settings(I have not made any changes these should be Default).
    Message Edited by AndrewAlford on 11-25-2005 02:23 PM
    Andrew Alford
    Production Test Engineering Technologist
    Sustainable Energy Technologies
    www.sustainableenergy.com
    Attachments:
    ConfigGPIB.JPG ‏39 KB
    GPIBconfig.JPG ‏14 KB

  • Problems with pci--gpib-300k from computerboards

    hallo,
    i have problems with my gpib-card, win95 and 2000 identify this card
    corectly but labview not, the max 2.0 find not cards.......have everyone the
    self card and can help????
    (sorry for my bad english..)
    bye & thanks...
    Thomas

    Thomas,
    The short answer is the MAX will not recognize non-NI devices. NI-MAX was designed to recognize and interface with National Instruments' boards such as our PCI-GPIB, AT-GPIB/TNT, etc. With the introduction of MAX2.0 and NI-VISA2.5, there was an added capability to recognize some Hewlett-Packard boards but even then, configuration of them must be done from an HP interface.
    LabVIEW will interface with the board fine but MAX is designed specifically to interface with our drivers for our boards.
    Ryan Mosley
    National Instruments, Applications Engineer
    http://www.ni.com/exchange

  • GPIB Enet/100 with PCI-GPIB

    Is the a timeframe with the release of a GPIB Driver
    capable of supporting both the Enet device and an installed GPIB-PCI card within the same computer?

    The next version of the 488.2 driver will support the ENET and PCI GPIB cards together for Win 2000/NT/XP. We canot give a release date at this time but it will be on the web when we do.

Maybe you are looking for