PCI-GPIB under WIN98 DOS

I have installed a PCI-GPIB board in a Dell computer. I can communcite withmy CDS rack from the DOS version of the "Interactive Control", IBIC. In my qb4.5 DOS program, I can find GPIB0 without any errors. However, the data returned in the second parameter for ibfind does not appear to be correct. When I try to clear the RQS, I get a 10 second timeout. It appears that I can not communicate with my devices. NI-488.2 for DOS is enabled. Thanks for any help you can give me.
Gaylon Patton

By saying that you are using the DOS version of "Interactive Control", do you mean that you are working in the DOS operating system? The PCI-GPIB board cannot be used in the DOS operating system. Enabling DOS Support allows you to run DOS programs in the Windows MSDOS prompt. If you need to work in the DOS operating system, you can use the AT-GPIB/TNT board with driver version 2.7.2.
Kim L

Similar Messages

PCI-GPIB under Win2k AS TE

Hi All,
Does anyone try to run PCI-GPIB under Windows 2000 Advanced Server Terminal
Edition?
Everything works perfectly in case I have a console session, but I cannot
communicate with GPIB and instruments during a terminal session (logged as
a terminal client as Administrator). Any suggestions?
Thanks.
Michael.

That param is the Board or device descriptor. If a device or an interface is taken offline, the board or device descriptor (ud) is no longer valid. You must execute an ibdev or ibfind to access the board or device again.
Is there an error message associated with the crash? Also this discussion sounds similar to "VB6, W2K, always crashes 2nd time run in VB design mode" http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000EF150000&ECategory=Instrument+Connectivity.GPIB

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

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.

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

Where can I find the driver for PCI-GPIB drivers for Windows XP

We have PCI-GPIB cards work well under Win2k Pro and WinME, but when we try to mount the card to a WinXP machine and install the same driver as used under Win2k, and whenever I try scan instruments in Measurement & Automation, the system crashes and dumps the memory.
Is there a specific driver for PCI-GPIB working under Windows XP? Thanks

Hello,
I don't know what GPIB driver version you have but you can go to the following webpage in order to get the latest GPIB driver (version 2.0) available.
http://www.ni.com/support/gpib/versions.htm

PCI-GPIB/Win2000 blue screen-resolved yet?

Hi,
I have been kind of out of the loop lately, so can anybody enlighten me
on the subject?
Has the blue-screening (BAD POOL CALLER) error with PCI-GPIB board under
win2000 resolved yet and everything is hunky-dory, or it's still there?
Sincerely
Yuri

Hello-
This error is caused by a faulty process that does not close GPIB sessions. With these orphan sessions, a call to open another GPIB session will cause Windows to assert this screen.
The solution to the problem is to call ibonl(ud,0) for each session that is open. This typically needs to occur just before terminating the process using GPIB.
If this solution is not working, please write back.
Randy Solomonson
Application Engineer
National Instruments

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

PCI-GPIB card not found in linux 2.4.22-1.2115.nptl Fedora Core 1

I am trying to install the nigpib driver on a Fedora Core 1 installation of linux (kernel 2.4.22-1.2115.nptl.) The installation script reports the following errors:
Your kernel appears to be configured properly to build NI-GPIB for Linux.
Do you want to proceed? [yn] y
make: `nigpib.o' is up to date.
Copied nigpib.o driver to modules directory /lib/modules/2.4.22-1.2115.nptl/kernel/drivers/char
Devices created.
Probing for PCI-GPIB.
No PCI-GPIB boards detected.
Do you have an AT-GPIB/TNT board installed? [ny] n
/etc/modules.conf is up to date.
Warning: loading /lib/modules/2.4.22-1.2115.nptl/kernel/drivers/char/nigpib.o will taint the kernel: no license
See http://www.tux.org/lkm
l/#export-tainted for information about tainted modules
/lib/modules/2.4.22-1.2115.nptl/kernel/drivers/char/nigpib.o: init_module: Device or resource busy
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.22-1.2115.nptl/kernel/drivers/char/nigpib.o: insmod /lib/modules/2.4.22-1.2115.nptl/kernel/drivers/char/nigpib.o failed
I have moved the PCI-GPIB card to the first PCI slot with no differences in the error messages I recieve. When I run dmesg I recieve the following information:
unable to get major 31 for gpib
unable to get major 31 for gpib
unable to get major 31 for gpib
unable to get major 31 for gpib
unable to get major 31 for gpib
Any help would be appreciated.

I have this same exact problem. I'd rather not disable USB 2.0, because I use it to transfer files to my MP3 player when in Windows.
I find it hard to "blame the BIOS" when it was working fine under kernel 2.6.7. Anyone know of another solution?
EDIT: Well it isn't the same "exact" problem. When I first boot into Arch, the usb mouse and keyboard don't work. I press and hold the power button on the machine to restart. The second time I boot into Arch, the usb devices do work. If I do a standard soft reboot and go back into Arch, the usb devices again don't work. I guess this is a hotplugging issue, but enabling it in rc.conf does nothing. The only permanent solution I can find is disabling USB 2.0 in the BIOS.

PCI-GPIB on Win NT 4 - No serial number to configure card

Unable to install PCI-GPIB on Win NT 4.
Cannot detect any serial number.

Eddie,
Thanks for contacting National Instruments.
I am sorry to hear you are having trouble installing your PCI-GPIB card. I found a document on our website which details troubleshooting steps for the situation you described:
Grayed Out Serial Numbers for PCI-GPIB Boards under Windows NT
I hope this helps you resolve your installation issue. If not, feel free to post here and we can discuss it further. If you do have further questions, please be as detailed as you can in your response. This will let us give you the most relevant answer to your situation.
Sincerely,
Ross C
National Instruments
Applications Engineer

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.

Analog Triggering and Interrupt generation on the PCIe-6320 under Linux

We would like to use the analog triggering functions of the PCIe-6320 under Linux to time tag external events.
I have no experience with the MH DDK but have been told this is what we would need to implement the functions we want. We plan on using Fedora Linux and we are targetting kernel 2.6.31 with the PREEMPT_RT patch applied. We may consider slightly more recent kernel versions. The PREEMPT_RT patch is used to greatly improve determinism in the system and get real-time responses to some external events.
Here is what we wish to do in more details:
We wish to route at least two analog inputs to the comparator, then route the output of the comparator to a digital input which in turn would create a PCIe interrupt. The interrupt software handler would than time tag that event for our application purposes. We need the comparator threshold to be software programmable in level and slope. We are also interested in using the Watchdog Timer feature of the board.
Our application is written in C/C++.
Would the above be feasible? Please provide comments and instructions how we should address our requirement.
Thanks!

Patof wrote:
I am not familiar with the MHDDK. I would like to have an idea of the effort required to implement the functions I have described using MHDDK on Linux. Like I mentionned, we plan on using Linux kernel 2.6.31 with the PREEMPT_RT patch. Could you provide comments on that matter? I need to evaluate the amount of time I will need to spend to deploy and use MHDDK for the PCIe-6320.
There are two factors to consider when writing a driver for your specific application:
Using the deterministic kernel API calls
Writing to the device registers to
Control the watchdog timer
Configure the analog comparator
Manage the analog subsystem state as trigger events occur
Handle device interrupts
The MHDDK for X Series offers the following behavior out-of-the-tarball:
A Linux kernel module using the standanrd kernel and PCI subsystem calls
Mapping device registers to user-mode for access
Demonstrating/documenting how to
Control the watchdog timer (dioex6.cpp)
Manage the analog subsystem state as trigger events occur (aiex2.cpp, aiex4.cpp)
Handle device interrupts (reference manual only)
There are two notably missing pieces and one item to consider:
Missing: deterministic kernel API calls. If you decide to use the nirlpk module, you would need to change it from the standard interfaces to the deterministic variants.
Missing: configuring the analog comparator. You will need to implement this with additional insight from this discussion board.
Consider: if your application requires device access from kernel-mode only, you would not be able to use the MHDDK's C++ classes that perform device programming but would need to implement register programming in C.
To estimate the time for these three, here are my recommendations:
Review the nirlpk.c source file to understand how device access and DMA buffers are implemented and mapped to the user-mode application.
Beware that operation-specific programming help (as you would need for analog triggering) typically requires two weeks for a complete response.
Review the ChipObjects in the MHDDK distribution to understand how register addresses, widths, and bit fields affect device programming.
Joe Friedchicken
NI VirtualBench Application Software
Get with your fellow hardware users :: [ NI's VirtualBench User Group ]
Get with your fellow OS users :: [ NI's Linux User Group ] [ NI's OS X User Group ]
Get with your fellow developers :: [ NI's DAQmx Base User Group ] [ NI's DDK User Group ]
Senior Software Engineer :: Multifunction Instruments Applications Group
Software Engineer :: Measurements RLP Group (until Mar 2014)
Applications Engineer :: High Speed Product Group (until Sep 2008)

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.

Cannot make bios flash with nvflash under the DOS for MSI N660 TF 2GD5/OC?

I download latest bios file on MSi product page. I installed CWSDPMI.EXE, NV287MS222.ROM, NVIDIA.BAT, nvflash.exe files in bootable USB. I started nvflash under the DOS.
First try to update with .bat files command like this;
nvidia
NVIDIA firmware update utility v1.527 Cannot open files: NV287MS222.ROM
I tried this time manually command like this;
nvflash NV287MS222.ROM -4 -5 -6 click
I got same error
NVIDIA firmware update utility v1.527 Cannot open files: NV287MS222.ROM
I tried that one;
nvflash --index=1 -5 -6 NV287MS222.ROM
Same error again;
firmware update utility v1.527 Cannot open files: NV287MS222.ROM
Can anybody tell me where am I doing wrong? How can I update my bios under the DOS?
PS: inside .bat files command
nvflash %1.ROM -4 -5 -6

Quote from: Svet on 29-November-12, 18:03:35
Use attached archive, extract all files to bootable USB stick,
then boot from it to pure DOS, when you see A:\ or C:\, type:
flash [ENTER]
Thank you its worked.

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/9b2b33e1993d877786256436006ec498/7b235254f3881ddb862568ab005fbd2e?OpenDocument
http://zone.ni.com/idnet97.nsf/9b2b33e1993d877786256436006ec498/24ca7db880ab78ae862568ab005fbc0f?OpenDocument
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

PCI-GPIB under WIN98 DOS

Similar Messages

Maybe you are looking for