Intuilink with NI 488.2

I am using HP IntuiLink for oscilloscope screen capture and I switched from an HP I-O card to NI488.2
Now I do not see the NI488.2 in InuiLinks configure options.
What can I do to get good screen capture again from the HP54645D Oscilloscope?
Thanks in advance,
Bertho

Hi Bertho,
NI 488.2 is a driver package. The following document walks through setting up and configuring your system with the NI 488.2 drivers and communicating with your instrument through the NI Measurement and Automation Explorer.
http://www.ni.com/pdf/manuals/370428l.pdf
If that is not able to solve your problem, we will need more information about your hardware setup. Are you now using a National Instruments GPIB card?
If you are not using LabVIEW or other National Instruments hardware/software, you may need to contact Agilent for help with IntuiLink.
Regards,
Kelsey Johnson
Applications Engineer
National Instruments
http://www.ni.com/support
(866) 275-6964

Similar Messages

Agilent board doesn't work with NI-488

I have an Agilent GPIB interface board, but it seems that it doesn't work with NI-488 software. I would like to know if there's a way to use these board with LabView because if it's not recognize by NI-488 software I can not use it in an application with Labview

As far as I know, NI-488 only works with NI's GPIB boards and other GPIB Interfaces.
I suggest getting an GPIB interface from NI. If you are looking for a cheap way to do this, try getting a USB-GPIB Interface. They are only $495. Also, ISA GPIB cards are only $395.
Alternatively, try installing the GPIB interface software for the Agilent board, and communicating with it through LabVIEW. Agilent may have a driver for this.

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

Problems with NI-488 cPCI adapter under QNX.

Hi Michael,
The problems that I am having with the NI 488 cPCI adapter are random, so
it is
very difficult to nail down where the problem lies. Sometimes the adapter
fails
the initialization sequence in the nitn_presence_check routine at various
points in the 4 tests that the driver performs. Other times, if the adapter
initialization passes, the driver will loop in the nitn_wrtPIO with the
message
"waiting, isr3=0x4c" or "waiting, isr3=0x00". I have added a loop count to
the
routine so that it exits after 100 loops, but it still affects the driver
performance. I have had a similar problem with the nitn_wrt1byte routine.
I have been told that the driver works under Windows and Linux, but it
doesn't
work under QNX, and I have no idea why not, as I don't have any chip-level
documentation on the adapter. I will appreciate any help that you can give.
Thanks, Hugh.

Hi bearhug,
This post was a little confusing. Was it started in another thread and moved over to a new one accidentally? Since it appears that you have had some previous correspondence, I looked into the type of issue you are experiencing and it looks like Michael, one of our Applications Engineers, has an in-work service request related to it. If that is your service request, I would encourage you to contact him directly by calling 1-866-275-6964 and entering the service request number there. Please let me know if there has been some miscommunication.
Best regards,
Matt J
Matt J.

Can a 488.2 controller be used with 488.1 device?

I was wondering if a 488.2 controller can be used with a 488.1 device? I have used the same controller with 488.2 devices with no problems but not with a 488.1 device.

srm,
A 488.2 controller (such as any of NI's GPIB boards) is backwards compatible with a 488.1 device. Both use the same digital communication protocol to address the bus. The main differences in 488.1 and 488.2 are the status model (which is also backwards compatible, 488.2 just added additional functionality on top) and that the 488.2 specification added additional software specifications, such as a common command set and syntax & data structure guidelines, that a 488.1 device would not necessarily understand. So if you were trying to address a 488.1 device using commands or programming calls specific to 488.2, this could be the cause of the problem. I know these abilities are separated into two different palettes in LabVIEW, I'm not sure exactly how they are separated in the text-based languages.
Regardless, a 488.1 device should show up when you "Scan for Instruments" with your GPIB card in MAX. Some things to check are that the GPIB card is installed with the proper drivers (the latest verison of NI-488.2 compatible with your OS) and is detected by Windows and MAX, the cable connections are made properly and the instrument is powered on and has its GPIB interface configured with an address that does not conflict with another instrument. Hope this helps clear up the confusion, have a good day!
Sincerely,
Ross C

Mapping 488.2 errors to NI iberr

Is there a mapping between iberr and 488.2 standard ESR bits (Command Error, Exec Error, Query Error and Device Err)?
How does one relate to another?
Does the NI driver set iberr based on the values in ESR? If so, what is done with a 488.1 device which does not have an ESR at all.
Thanks
Raj

The ESR is an added function of the 488.2 standard. Its use is primarily from an application standpoint. That is, how the ESR is handled depends on your application and not the driver. The Ni-488.2 is a backward compatible driver that will support both standards. As such, its error codes are generated by a marriage of driver level and hardware level queries. The ESR is not involved with the IBERR generation.

AT-GPIB NI-488.1 Jumper settings

I have an old ISA AT-GPIB board (180210-V1 Rev A3) with NI-488.1 DOS-driver that works fine with an old DOS computer. Now I want to move the board to a new computer with ISA-bus but it is not possible to change the application software that is using the card. The old I/O-address of the board conflicts with something else on the new motherboard, so I have to try another I/O-address, but I haven't been able to find documentation of the jumper and dip-switch settings.
Where can I get the infrmation how to set the jumpers and DIP-swithes to use different settings?

Thanks for the answers. I have already found these documents, but the jumpers are different. Attached is a picture of the card.
The working settings corresponding the jumpers and switches in the picture are:
DMA channel: 1
Base I/O address: 02E1H
Interrupt jumper setting: none
Attachments:
NI-AT-GPIB.jpg ‏526 KB

Ways to configure VISA properties associated with the EOS character in LabVIEW

I am having a great deal of trouble reading consistently from an instrument (HP5328A Universal Counter) and am investigating the EOS character. In ibic, there are 6 properties of interest accessed through the ibconfig command. The following are the properties and their default settings:
Board level
- IbcEOSchar EOS character is 0 (zero)
- IbcEOSrd EOS is ignored during read operations
- IbcEOSwrt EOI not asserted when EOS sent
Device level
- IbcEOSchar EOS character is 0x0A (set in ibdev)
- IbcEOSrd EOS ignored during read operations
- IbcEOSwrt EOS not asserted when EOS sent
I would like to be able to programmatically set these at the beginning of my LabVIEW
program. The only relevant VISA properties in the INSTR or GPIB BoardInterface classes I can find are:
- Send End Enable
- Suppress End Enable
- Termination Character
- Termination Character Enable
The defaults in my LabVIEW program for both VISA classes mentioned are: Send End Enable is true; Suppress End Enable is false; Termination Character is \10 (Line Feed); and Termination Character Enable is false.
The only property I change is setting the Termination Character Enable to true for both classes. Is there anything else I can do with properties associated with the EOS char? Is there a property like the IbcEOSwrt that may have a part in generating a service request?
Just to confirm, the last two bytes of the instrument's ouput are \CR and \LF. I am using \LF as the EOS. Is this correct or should I be incorporating the \CR in the EOS somehow?
ANY input is appreciated,
Chris

Chris:
VISA "Termination Character" = NI-488 "IbcEOSchar"
VISA "Termination Character Enable" = NI-488 "IbcEOSrd"
VISA "Instr" or "GPIB Instr" = NI-488 "Device level"
VISA "GPIB BoardInterface" = NI-488 "Board level"
VISA cannot automatically add the termchar to the end of the written data (like IbcEOSwrt).
Unless you specifically need to do board-level communication, which is considered advanced, I suggest ignoring that, and sticking to the device-level calls.
If the instrument's ASCII data responses always end in \LF, then yes, just using \LF as the termchar is the correct thing. In fact, with most 488.2 devices you don't need to worry about the termchar, because the final byte of a response also contains EOI. EOI causes the driver to s
top reading from the instrument because it knows that is the end of the response.
You say you're having trouble, but you don't say what the symptom is. Is the read timing out? You might also want to use NI Spy to get a snapshot of what is going wrong.
I hope this helps some.
Dan Mondrik
Senior Software Engineer, NI-VISA
National Instruments

NI-488.2 no instruments found

Using PCI-GPIB card with NI-488.2 version 1.6 (or 1.7) and Windows NT 4.0:
- If a GPIB instrument is at GPIB address 1 on PCI-GPIB configured as GPIB1, this instrument is not found using N.I. "Scan for instruments" utility. If I change this GPIB instrument address to 0 or anyone from 2 to 31, the utility can find the instrument.
- Same observation if I connect a GPIB instrument at address 0 on GPIB0, or at address 2 on GPIB2, etc.
Is the PCI-GPIB card number used to configure it is then no more available for the address number of any instrument connected to this bus?
Thanks.

The problem is an address conflict. To answer your question at the end, yes, if the GPIB board has a particular address, it is not available for any instrument connected to the controller. All controllers/devices must have a unique address.
I don't remember how the NT configuration utility worked. It is possible that the GPIB configuration utility automatically configures GPIB1 for PAD1 and GPIB2 for PAD2, etc. In general, you should always configure your GPIB controller to be at primary address 0 and have your instrument(s) be configured for an address in the range 1-30.
The GPIB configuration utility lets you choose the GPIB number AND the GPIB primary address separately. Therefore, if you GPIB controller is GPIB1, go into the configuration utili
ty and configure it be at PAD0. Then everything should work.

How to program VC++ with AT-GPIB-TNT

I am a student in Taiwan and a beginner user in GPIB.
I am writing a control program in Visual C++(console) on Win98 (by N.I. GPIB-TNT
board).
I need to control two devices one is Laser interferometer for measurement,
another is PZT(piezo actuator).
When I execute a simple read and write program,
it always shows " can not read ".
I am so confused.
Can you help me to overcome this problem
and show me a new simple program?!
Thank you very much.....
I am so appreciate for your help.
best regards
Andrew

Andrew,
From the bottom of http://www.ni.com/support/trouble/gpib/max/ibic.htm, there is
a link to "Solutions to Common Errors." If you follow that link, the next page will
have an entry for the EABO error code (and several other error codes). These tips
are the suggestions that our support staff would make to you if you were to speak
with them. I suggest checking that link out. I have posted this message to the
newsgroup for the benefit of all readers.
Regards,
Rich
NI
Thanks for your help.
After receiving your mail, I try to follow the step.
But when I use "ibrd", it has the error code as follow
iberr = EABO
EABO indicates that an I/O operation has been canceled, usually due to a
timeout condition after a GPIB read.
Before reading from the instrument, verify that the GPIB command you are
sending is understood by your device
and instructs it to place data in its output buffer.
device data as follow
Board: GPIB0 AT-GPIB/TNT
Device: Name Type
Value Description
instrument0 Instrument is not 488.2 compatible pad=2 GPIB
instrument
instrument1 Zygo, VMEbus control board pad=3 GPIB
instrument
My goal just want to read the measuring data from laser device by
AT-GBIP/TNT board.
Need your help again thanks.
Andrew
> Andrew,
>
> What you may want to do, instead of starting off with straight
coding, is
> to see if you can establish communication with the instrument using
"IBIC," our
> interactive diagnostic tool for instrument control. This program comes
> installed with your 488.2 driver.
>
> To find out more about this, visit
> http://www.ni.com/support/trouble/gpib/max/ibic.htm . If you can achieve
> communication with your instruments with this program, you're well on your
way.
> If you cannot, the website has solutions to common errors that one can see
while
> using this tool.
> ps. "threads" refer to the number of processes running at once. For
example,
> if you can do two separate math operations simultaneously in your program,
> that's a multithreaded application.
> "andrew" on 04/24/2000 03:51:13 AM
> I am a student in Taiwan and a beginner user in GPIB.
> I got your e-mail address from your post on N.I. user newsgroups.
> I am writing a control program in Visual C++(console) on Win98 (by N.I.
GPIB-TNT
> board).
> I need to control two devices one is Laser interferometer for measurement,
> another is PZT(piezo actuator).
> When I execute a simple read and write program,
> it always shows " can not read ".
> I am so confused.
> Can you help me to overcome this problem?
> And show me a new simple program!
> Thank you very much.....
>
> I am so appreciate for your help.
>
> best regards
> Andrew
>
> Ps.what is singlethreaded and multithreaded?

Can an image of Windows 2000 using NI-VXI 3.5 with a PXI-MXI controller be fielded for multiple computers using sysprep?

I am trying to field an image of Windows 2000 using NI-VXI 3.5 with a PXI-MXI controller. Can I set the system up to retain to original settings for VXI? Some of my computers use a PCI-MXI controller. Although Windows always finds the MXI controller, the original VXI System 0 is not used. I have several VME instruments set up and the target is about 85 different computers. Also the NI-GPIB interface does not show in MAX. Is this supposed to work?

Hello,
Here's an update regarding the gpib error. There has been a Corrective Action Request (CAR) ID:3BI8A578, filed due to a similar issue of error gpibpnp.exe with NI-488.2 v2.2 on Windows 2000 and Sysprep. This issue's workaround involved going back to install NI-488.2 v2.1 or installing the v2.3 release in order to eliminate the problem. Currently, NI-488.2 v2.3 is no longer available for download, however, all operating systems and hardware supported by NI-488.2 v2.3 are also supported by NI-488.2 v2.4 (see link 1).
1. NI-488.2 2.4 - Windows XP/2000: http://joule.ni.com/nidu/cds/view/p/lang/en/id/3402. GPIB Driver Versions for Microsoft Windows and DOS: http://zone.ni.com/devzone/cda/tut/p/id/5326
Best regards,
Ali M
Applications Engineer
National Instruments
Message Edited by Ali M on 05-25-2010 02:07 PM

Unresolved external symbols when linking C++ with ni.4882.obj

Moving from 32-bit XP to Windows 7 using Microsoft Visual Studio 2008 C++. When linking with NI-488.2 version 3.0.2 I (ni4882.obj) get the following warning and errors:
1>Linking...
1>ni4882.obj : warning LNK4217: locally defined symbol _time64 imported in function time
1>ni4882.obj : error LNK2019: unresolved external symbol __imp_rand referenced in function LoadFunction
1>ni4882.obj : error LNK2019: unresolved external symbol __imp_srand referenced in function LoadFunction
1>ATP.exe : fatal error LNK1120: 2 unresolved externals
1>Creating browse information file...
1>Microsoft Browse Information Maintenance Utility Version 9.00.21022
1>Copyright (C) Microsoft Corporation. All rights reserved.
Any ideas.
Solved!
Go to Solution.

Hi Guys,
I got this error too recently. Was troubling me a lot. I was using Windows 7 OS, Visual Studio 2010 compiler.
The fix for this is pretty much straight forward and solution lies in the Project settings only.
To my knowledge, with /MDd switch, it causes the compiler to place the library name MSVCRTD.lib into the .obj file.
But with /MTd switch, This option just causes the compiler to place the library name LIBCMTD.lib into the .obj file so that the linker will use LIBCMTD.lib to resolve external symbols. For details, please refer to this MSDN article:
https://msdn.microsoft.com/en-us/library/2kzt1wy3(VS.71).aspx
Its very useful.
Also
MDd stands for Multi-threaded Debug DLL
MTd stands for Multi-threaded Debug
Thanks,
Kiran

Can IEEE 488.2 Labview software/drivers used on a IEEE 488.1 instrument

I have a IEEE 488.1 device but am using a IEEE 488.2 Labview software/driver package. Measurement and Automatiion
tells me that the IEEE 488.2 board is working properly but there is no communication between the board and the device.
Is IEEE 488.2 downward compatible? If not, is there any remedy rather than getting a new board or getting a new instrument
with IEEE 488.2 software?
Thanks.
Mark

Hello,
In my application I am conducting a pressure test, Here am using DMA Make Air Data Test Set witch I am interfacing to the PXI system through GPIB.
In MAX the particular GPIB address is detected but if i write a query "*IDN?" it did nt respond.
To debug this issue I used NI 488.2 Interactive control when i started communicating with the instrument it throws error such as EAB0 and status as TIME0 and CMPL
Here the Instrument DMA make MPS31C is 1EEE 488.1 Compliant.and NI 488.2 Ver 2.52
Please find the attached operation manual and Device communication manual of the Air data test set
Please suggest be a solution for this issue.
Waiting for a quick reply
Regards
Lingaraj
Attachments:
EM MPS31C Operating0108.pdf ‏2452 KB
EMPS31CExtDrivComm.1010.pdf ‏104 KB

How to make "visa find resource" working with Agilent device

I am trying to use Agilent 82357B GPIB device with LabVIEW for instrument control.
I have checked:
1.       NI-VISA (ver 5.1.1) is the primary visa by checking visa.dll properties under windows\system32 folder
2.       Enable NIVISATulip.dll in NI Max Explorer
3.       Enable the Agilent libraries to work with NI 488.2 in Agilent IO library (ver 16).
I am able to communicate with the instrument in Max Explorer and talk to the instrument in LabVIEW with VISA write for almost all commands.
But I can NOT make one particular visa function (Visa find resource) working with Agilent 82357B GPIB.
With NI USB GPIB device, the same code above can find attached instruments as below, where GPIB1 is the Agilent device and GPIB0 is the NI device.
I have no clue on how to make “visa find resource” working with Agilent device.
Please help.
Solved!
Go to Solution.

Quick question. Did you also enable 488 support in Agilent?
If that does'not work try this. and well see if you found a bug
Jeff

Compatibility of Agilent GPIB/USB adapter with NI

Hi,
I have an Agilent GPIB / USB adapter 82357B, and I'm experiencing some problems for detecting my instruments in the laboratory when I try to use the labview software for capturing the data from the measurement instruments.
I installed the CD with the libraries the adapter has and through this software I can detect the instruments, however once that I open the Labview software from National instruments(NI) for capturing my data, I miss comunication with the devices in both programs, the Agilent one and in the MAX of NI.
I run across a document regarding tip on using Agilent GPIB solutions in National instruments's Labview environment. I have done all the document indicates, but It is not workingt, I experience the problem I outlined above for detecting the instruments.
I hope someone can help me with that.
Regards

DCU STUDENT wrote:
Yes I am. According to documents it is possible. But I don't know want else to do, since I have done what document indicated. I as mentioned in previous message, now I can see the measurement instrument with Labview and using the Agilent cable adapter, and I can stablish communication with device since that when I select the device in the labview program, a led in the instrument is ON, indicating communication. However when I try to capture the data on screen, there is not data at all.
Hello DCU STUDENT,
It sounds like there may be some conflict between the NI VISA and Agilent drivers, which can occur between certain models; considering when you use the NI cable data can be collected when when you're using the Agilent you cannot. Please tell me what versions of both drivers you are using so I can determine whether or not there are any known incompatibilities between the two if you're still receiving the same error after following these instructions.
Can you also please go through this instrument troubleshooting guide to see if your installation matches the expected configuration of a functional device so we can confirm that your driver has been installed correctly from the previous guides.
For a IEEE488 Agilent Device Card, as you mentioned that you have the NIVISATulip.dll enabled, for this GPIB configuration to work you must ensure that the 488 Programs must be activated with NI 488.2 (At the Enable Agilent GPIB cards option) through the Agilent Connection Expert.
You've mentioned that you've been able to establish a connection with the device and see communication transfer, yet you are getting no returned communication. Do you see a similar response when you view the device through the Measurement and Automation Explorer?
If it is possible, could you test your configuration with any other Agilent devices with your current configuration and see if the error persists?
Alex Thomas, University of Manchester School of EEE LabVIEW Ambassador (CLAD)

Intuilink with NI 488.2

Similar Messages

Maybe you are looking for