PCI-GPIB y Perkin Elmer AAnalyst 300

Buenas,
Estoy en una escuela que suele recibir material antiguo de empresas para sus clases de química (con lo cual el tema de soporte, licencias, etc.. está un poco imposible).
El tema es que adquirieron una máquina con una tarjeta PCI-GPIB y, en teoría, dicha máquina llevaba un espectrómetro Perkin Elmer Aanalyst 300.
El tema es que el programa del espectrómetro (AA WinLab 2.61) dice que no vé el dispositivo pero utilizando el NI MAX (actualizado a la última versión) parece que hay comunicación.
Si utilizo el NI Trace puedo ver como se envían y reciben datos a través del cable IEEE pero cuando arranco el programa, el NI Trace no detecta nada de nada, como si ni se intentara la comunicación.
¿A alguien se le ocurre alguna idea? Estaré (tanto yo como los profesores) eternamente agradecido

Similar Messages

  • SRQ Line no longer works on a PCI-GPIB

    I have just upgraded a test pc, (tranfering hardware, reinstalling software etc) and now I have a fault with the PCI-GPIB card.
    One of the instruments connected to the PC (HP34401 multimeter) uses the SRQ line to indicate when its ready to download its readings. The LV 5.0 code uses the standard legacy drivers from NI and these drivers use the 'wait for SRQ' function which are now timing out in the new setup.
    The rest of the card functionality seems ok, and it tests ok. The LV code and cables are fine, because I can run the system with a USB-GPIB-B device.
    Has anybody had the same problem?
    Could it be a hardware specific driver problem?
    The current config is:
    1.7GHz PC with 512Mb Ram
    PCI-GPIB
    PCI-1200
    LV 5.0.1
    NI-
    488.2 Version 2.0
    VISA 2.6.1
    NIDAQ 6.7
    Thanks for your help
    Tim

    Hi Tim,
    I found this knowledge base article which seems to address the same problem:
    Why is the Agilent 34401A Driver's Getting Started VI Timing Out?
    Hope this helps out.
    DiegoF
    National Instruments.

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

  • How do I determine the interrupt detection sequences for an HP 82350A PCI GPIB card?

    I am trying to install an HP 82350A PCI GPIB card in CentOS 6.4. I have installed NI-VISA 5.4.
    I tinkered around and found driverwizard in /usr/local/bin. It creates an ini file to control the PCI GPIB card.
    I had somehow succeeded in detecting the card (PXI3::0::INSTR). My driverwizard output looks like this
    [Module]
    ModuleName = "PLX PCI <-> IOBus Bridge"
    ModuleVendor = "PLX Technology, Inc."
    ModelCode = 0x9050
    ManufCode = 0x10B5
    SubsystemModelCode = 0x10B0
    SubsystemManufCode = 0x103C
    VISARegistration = Simple
    As you can see, it does not have interrupt handling built into it, so I cannot access it properly.
    How do I set up interrupt handling for this card? What are the specifications for the following fields?
    Interrupt Detection:
    Access Type
    Access Width
    Address Space
    Space Offset
    Compare Mask
    Write/Compare Value
    Interrupt Removal:
    Access Type
    Access Width
    Address Space
    Space Offset
    Compare Mask
    Write/Compare Value
    Interrupt Disarm:
    Access Type
    Access Width
    Address Space
    Space Offset
    Compare Mask
    Write/Compare Value
    This is the first time I have tried hacking at the PCI interrupt level. At the very least, how do I find out the values for the above parameters? Or at best, straight away what are the values for those parameters?

    Their IO Libraries Suite supports only Windows. Our lab probably used Windows before. This 82350A card is quite ancient. I need to use this because we also have ancient instruments that do not have Ethernet.

  • How can I use the instrument toolbox in MATLAB 6.1 to contol the PCI-GPIB card under Linux?

    I'm trying to use the PCI-GPIB controller to control lab equipment through MATLAB 6.1 (R12.1) under Linux. MATLAB's instrument toolbox seems to integrate with NI's board, but the MATLAB documentation says it requires the installation of a driver. I've downloaded the linux gpib driver, and I'm able to run the associated utilities (ibconf, ibic, ibsta), but MATLAB cannot interface to it. For example,
    >> g=gpib('ni',0,1)
    ??? Error using ==> gpib/gpib
    The specified VENDOR adaptor could not be found.
    Where can I find a MATLAB driver and how can I install it?
    Thanks,
    Richard

    Hello-
    The knowledge base: "Can Matlab for Windows Call the National Instruments GPIB Driver?" Also applies to this question as well. This article is very extensive. Try searching on ni.com for "+matlab +gpib" for more details.
    Randy Solomonson
    Application Engineer
    National Instruments

  • How can I read the trace data from Agilent(HP​)8510C in C++ using NI488.2 and PCI-GPIB ?

    Hello! I am trying to develop an application in C++ for measurements with Agilent(HP) 8510C network analyser using NI488.2 and National Instrument's PCI-GPIB card. In HPBASIC the trace data is read using OUTPDATA command which contains PREAMBLE, SIZE and then the data string in real and imaginary pair for the required points. The ibrd function gives data only for one point. Kindly guide me how I can read the whole trace and and separate out the real and imaginary data values. Regards, kapil

    Hey Kapil,
    It seems that in HPBASIC you were using an instrument driver for the 8510C. OUTPDATA is not a native HPBASIC function. National Instrument has similar instrument drivers for LabVIEW and CVI.
    http://zone.ni.com/idnet97.nsf/9b2b33e1993d8777862​56436006ec498/7b235254f3881ddb862568ab005fbd2e?Ope​nDocument
    http://zone.ni.com/idnet97.nsf/9b2b33e1993d8777862​56436006ec498/24ca7db880ab78ae862568ab005fbc0f?Ope​nDocument
    For example in the CVI instrument driver you will find a source file called hp8510.c. In the source code you will find a function called hp8510c_dataInRaw that sounds similar to the function that you described.
    Note that this example is designed for CVI, but it is possible that you could extract the information you need for C++. If
    you had a copy of CVI you could just add the files downloaded from the instrument driver to a project and then compile and run the project. It already contains a ready to run example that allows you to capture data and use your instrument.
    If you want try CVI you can download an evaluation copy on-line at http://ni.com/lwcvi/launch.htm.
    I hope this helps out,
    JoshuaP
    National Instruments

  • Is there example code for using Ni488 and PCI-GPIB card in non controller mode?

    Is there example code for using Ni488 and PCI-GPIB card in non controller mode?

    cymrieg,
    Your code looks good to me. What is the problem? What happens when it fails? What is the IBSTA value on the controller, and at what point in the code does it stop? What is the IBSTA value on the slave, and at what point does it stop?
    One thing is that you might not want to call IBCLR() in a loop on the device. At the beginning of the program is fine...This will send a clear command to the device and will clear out any LACS and TACS bits that might be set. Also your IBDEV call shouldn't be in a loop.
    Hope this helps, but let me know if you need more information.
    Scott B.
    GPIB Software
    National Instruments

  • Symbolic name for PCI-GPIB card

    I am using Agilent's ADS2002 to interact with an HP 8722D VNA via a PCI-GPIB card. I need a symbolic name for the card in order to write or read from the instrument; I've tried the suggested GPIB0 and GPIB1, as well as a few other guesses. Nothing on the card looks like a card number or symbolic name. How can I determine what the symbolic name should be? Thanks.

    Hello-
    Be sure that the GPIB board passes diagnostics. Also, try doing a Scan for Instruments in MAX. It may be that the board is not yet recognized.
    Also, consider using a programming language other than ADS. It may be easier for future upgrades to use a language like C or LabVIEW.
    Randy Solomonson
    Application Engineer
    National Instruments

  • Can't add PCI-GPIB board in Windows 2000.

    Installed software:
    NI-DAQ v6.9.2
    NI-488.2 v1.7
    MAX v2.2.0.3010
    After physically installing the PCI-GPIB board and booting, Windows 2000 recognized the card and configured it such that it shows up in Device Manager. Device Manager shows "This device is working properly."
    However, when I double-click on GPIB in Control Panel I get the message, "No GPIB interfaces present in the system."
    If I open MAX and do a refresh the card does not show up. If I right click on "Devices and Interfaces" and click "Create New", select "GPIB Interface", click Finish, select PCI-GPIB, I get "The PCI-GPIB is a plug and play interface and requires no manual hardware configuration for installation. You should now install the interface i
    nto your system."
    What's wrong?

    I phoned NI tech support and they said although NI-488.2 v2.0 recommends version 2.6.1 of NI-VISA, it is not required and still should work OK. Also, as of this date, version 2.6.1 has not been released.
    The good news: I installed NI-488.2 v2.0 and the card is recognized by NI-MAX now. Installation note for anyone else trying it: I installed the software on a fairly fast 1.3 GHz PC. So after installing the board and booting the PC, the NI Add Hardware Wizard started running before Windows 2000 had completed its installation of the board. The wizard's first attempt failed to find the board. When I clicked "Retry," the wizard found the board and it tested OK.

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

  • PCI-GPIB Mac OSX.4 G5

    Running Labview 8.2 on MacOS X.4 with the latest PCI/X-GPIB card to a Spex / Jobin-Yvon monocromator. The interface handshake fails on first character sent to the device (TIMO). Using an older PCI-GPIB card (physically larger, I don't see how to differentiate between cards) with G4 MacOS X.4, this handshake is no problem. I admit the Spex interface probably hasn't been changed in 15 years!! Other devices (newer) on the same bus communicate reliably with this latest PCI-GPIB/ OSX.4
    Robin

    Dear raman_epfl
    You could try troubleshooting the communication problem following the
    hints on
    http://digital.ni.com/public.nsf/allkb/9C9DBA7A3A56B6B686256F4A006FC8DA.
    Best regards
    Philipp R.

  • How do I configure my PCI-GPIB cards so that one is a controller and the other is a device being controlled by the first card

    I have 2 PC's, both fitted with PCI-GPIB cards. One will be the system controller and the other will be a device on the GPIB bus. How do I configure both cards using LabWindows/CVI v7.0 to achieve this ? What commands are used to send and receive the data ?

    Hi Pete,
    For the controller board you don't really need to do anything. By default the GPIB interface is configured as controller.
    The non-controller can be configured in MAX. Right-click on the interface, uncheck the ono-controller box and change the primary address. It is usually a good idea to set these parameters programatically. Use ibpad to set the primary address and ibrsc to release system control.
    For the controller you can use a device descriptor (using ibdev) or a board descriptor (ibfind).
    You can only open a reference to the non-controller board using ibfind (ibfind("gpib0"), for example). This will open a board reference. You cannot use a device reference because that implies that the board is capable of addressing the bus. On
    ly the system controller can.
    Here are some links I found on the web on this subject:
    Passing GPIB Control -- System Controller vs. Controller In Charge
    Tutorial: Programmatic File Transfers over the GPIB
    Example: Using a C Program as a GPIB Non-Controller with LabVIEW as the GPIB Controller
    Example: Serial Polling Between Two Computers (Controller and Non-controller)
    Hope this helps.
    DiegoF
    National Instruments.

  • For Sale: PCI GPIB cards.

    i have a couple of GPIB cards for sale from National Intruments
    give me an offer if you are interested.

    Thanks for the answer. Rev K and later for the older boards, and all new boards.
    But then your documentation
    is incorrect if you look at the "overview" section below the prices which seems to imply that OS 9 will work with this board. The description for the older TNT4882 based board is different and discusses only OS 9.
    The description of the board is:
    Name: NATI,pci-gpib
    Type: ndrv
    Bus: PCI
    Slot: SLOT-4
    Vendor ID: 0x1093
    Device ID: 0xc801
    Revision ID: 0x0001
    And the only thing that changees is the last part that is the revision ID? Is the name field the same since that is what my driver uses to identify the board. I suppose I should change that to use the Dev
    ice ID field. I am hoping that the NI DDK which my driver is based uses the "one chip mode" and will work equally well with both the TNT4882 and TNT5004 if you know anything about the NI GPIB DDK and the TNT5004 it would be most helpful.
    Are their major differences internally for the PCI-GPIB/LP board so that the GPIB DDK based driver would not work with that? If so, does that have a PCI Name or Device ID that I can tell my driver to service.
    Thanks again for the prompt answer.
    >

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

  • How can i change the voltage of my power supply using my pci gpib 488.2 driver?

    I need to be able to control the voltage outputed by the power supply. I have a pci gpib 488.2 and I downloaded the correct driver. I also don't no exactly how to use the communicator included in the measurement and automation explorer. When ever I type in the commands I get an error. If anyone can help me I would appreciate it.
    thank you

    First see if you can establish communications with the power suppy using Meas and Automation explorer (MAX for short). If you can find your GPIB card in the directory tree choose it and then use the scan for instruments tool. If it can see your power supply it will give you it's address. Choose it and try the Communicate with my instrument tool. It will send a IDN? command to that address and it might return a string if the instrument understands the command. If not you will need to dig through the power supply manual to find the correct commands.
    Using LabVIEW 2010SP1 and TestStand 4.5

Maybe you are looking for