Gpib error 0

Hi!
So i've converted an old daq-program to daqmx and have it running on a test station.
On the 2nd station, quite similar to the 1st one, i get a gpib error 0, and i cant figure out what/why/how to do anything about it.
I'm using older NI cards (same on both stations), listed as Traditional in MAX and using daqmx 9.3.5. and daq 7.4. The cards work in max, although i sometimes need to reset the driver on the problematic one.
Any ideas as to why it'd work on one computer and not the other?
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV
Solved!
Go to Solution.

Hello
I am building a digital down converter in LabVIEW. I am not able to figure out if my output is correct ( Inphase and Quadrature components). Am I on the right path? Please find attached the VI I have been working on.
Thank you.
Attachments:
ddcnew5.vi ‏516 KB

Similar Messages

Strange error: gpib error when using DAQmx

Hello
I try to out put a single puls using a counter on a PCI-6602 Board with the attached LabVIEW code.
Strangely I get the following error message:
"Error 3 occurred at an unidentified location
Possible reason(s):
LabVIEW: Internal error. Wrong memory zone accessed.
=========================
NI-488: GPIB Controller not addressed correctly."
Why do I get an GPIB-Error, although I don't even use a GPIB-Card?
Attachments:
ShortTrigger3.vi ‏23 KB
ErrorMessage.GIF ‏9 KB

Hello!
The problem is coming from the simple error handler.
The Simple Error Handler cannot decide if plots error + warnings, or only errors.
You cannot put your enumerator to the simple error handler, it works only with the general error handler.
In your program you are giving to the simple error handler a number 3 as error code. The VI convert this error number 3 with the error GPIB you received.
You should so replace the Simple Error Handler.vi with the General Error Handler.vi
Best regards
Ken

GPIB error in the instrument while no communication error

I am developing a test system by connecting several measurement instruments through GPIB with LabVIEW 6.i. The driver is written by using VISA command. GPIB control card is NI PCMCIA. When using laptop everything runs fine. When using an old PC with something like EISA to PCI converting card for slotting in the NI PCMCIA card. One instrument always displays an GPIB error. The error is instrument specific, no further detail is given by the manual. When the error comes out, no GPIB or VISA error exists. If only the driver for this instrument is installed so that the software only communicates with this particular instrument, no error. With other driver installed, there is no error in the first or two commnunication
. Later on the error is surely out and display in the instrument screen only. Once again, no any other GPIB or VISA communication error. Anybody can help on this ? Thanks a lot.

Hi JLS,
First of all, thank you very much for your prompt response. I am not sure some of your questions because our hardware engineer is away for a week. I am trying to explain what I know and see whether you could help to figure out the reason.
0. The operation system in the old PC is Win98. The CPU is PII 350MHz, 32G Hard disk and 320M RAM. The reason why we are using the old PC is that we have a 3rd party motion controller. Its control card is a ISA card.
1. The conversion device is a kind of card, put in the ISA slot in the PC extention I/O bus. We can slot in 2 PCMCIA cards in the conversion device. The driver for the NI PCMCIA card is supposed to be the same with that in laptop.
2. The driver that works with the instrument is developed by me by using NI-VISA. The instrument is a signal generator (SG) from Marconi instruments. Basically what the driver does is to turn on or turn off SG and read back its on-off status. When turning on SG, send setting frequency and signal level data as well. The calling of the driver is in a loop where frequency is stepping up.
3. There are other measuring instruments. e.g. electric field monitor probe to get the electric field strength etc. All these instruments' driver are developed by me by using NI-VISA. I also develop a set of dummy driver for all the instrument for demo purpose. Dummy drive did not communicate with instrument, inside, control is directly wired to status. When all other instruments except SG uses dummy driver, The running is OK. No error is displayed in the SG screen. If I use any of the other instrument's driver with that of SG, there is no problem at the first run (that means at the beginning of the loop), problem surely comes out later on. But it is OK when running in the laptop of which the OS is Win2000. The funny thing is if I takes out the status readback in SG driver, there will be no error at all even running with other instruments' driver in the old PC. I have compare through the GPIB card setting in the old PC and laptop, make sure that the EOI setting, primary address, EOS etc. to be the same in the two computer. It does not work.
4 & 5. The error displayed in the instrument screen is Error#403 "Data Expected". The manual said it is caused by the GPIB programming wrongly. No further explaination on how it may happen. Even there is such error display, no any GPIB or VISA error happens in my driver, the error cluster is clear. I debug the problem and find that the SG error appears when executing VISA resource open. I have also checked through all the NI GPIB help. It seems I could not find the answer.
6. I am not sure how to check the version of NI-488.2 and NI-VISA. NI-VISA is installed with the LabVIEW 6.i together.
Best Regards
Jason

"GPIB error Query Interrupted" flashes on HP54542A

I've written a display and control program in Delphi 7 for the HP54542A. The program uses NI commands and the GPIB-32.dll library, per NI's recommendation. The program appears to work properly, but I frequently get the message "GPIB error-Query Interrupted" flashing on the scope screen. I've tried putting delays in the software after read and write commands, but that seems to have no effect. Any suggestions? The version of the GPIB-32.dll that I have is dated 1999. I'm using a fairly new NI PCMCIA card in a new Dell laptop.

tfowler,
Perhaps someone in the community has some experience with the HP54542A. We do have a newer GPIB driver which has a newer GPIB-32.dll that you could try:
NI-488.2 Download
We also have CVI and LabVIEW instrument drivers for this instrument that you could try out (since you are using Delphi you could at least check out what the drivers are doing and get some ideas):
54542A Driver Downloads
Craig H.

Quick question GPIB error report vi

where is this vi located in labVIEW v6.1?
i tried searching for it in the functions pallette but couldnt find it,
thanks in advance,
Staunton

staunton wrote in news:506500000005000000F5110100-
[email protected]:
> i found this subVI also in an example VI shipped with V6.1, find
> examples>hardware input and output>GPIB>LabVIEW<->gpib.vi
Yup, I see it, and here's the revision history:
-rev. 1 28 Jun 1994 00:57:15 Apostolos K
-SubVIs of this VI were modified.
-VI was converted from LabVIEW version 3.0.1 to LabVIEW version 3.1a16.
1994!!!
If you need it, just copy it from its current location to somewhere in your
VI folder:
LabVIEW 6.1\examples\instr\smplgpib.llb\GPIB Error Report.vi
Andrew

Intermittant GPIB Errors "type mismatch"

The VB6 application I'm writing to control an Anritsu MP1570A Sonet Analyzer is now working moderately well, but I intermittently get the GPIB error,
"Unable to talk to GPIB device.||Type mismatch."
I find that this error does not occur if the program is single stepped. I have tried adding delays after each GPIB command and have played around with the duration. Delays seem to improve the situation but not entirely and not consistently. I'm not certain, but it seems like the problem may be less pronounced when the application is running standalone, i.e., not in the development environment. NI Spy reports no errors, by the way.
Has anyone seen anything similar or have an idea what the fix might be?
Thanks to all
in advance,
JG"

Hi Jerry,
I don't know of a specific reason why this may happen..but the first step would be to try and narrow this down...
Do you have any casts in your code ?
Especially from string to double? (from data you are getting back perhaps ?)
Its possible that if there is a timing issue, then sometimes you may get invalid , or unexpected data back, so if you have a cast such as dblValue = Cdbl(strText) * 2 it may work most of the times, but fail, if strText is not a number in the unexpected case...
The other case could be that, it is a Gpib Write or a Gpib Command thats failing with the type mismatch error(The command itself will not take place if there is a type mismatch error - so NI-Spy will look fine...). This could be true in the case, where data you send out is
not a string literal, and something that you calculate in your code..
The Read should always work, since it returns a variant..
So those are two places you could look at for potential problems...i.e. (1) the GPIB Writes,especially those where the command is not a literal string and (2) any casts, or a combination of the two...
Hope this helps some...
Nandan Dharwadker
Staff Software Engineer
Measurement Studio Hardware Team

Intermittent GPIB error 6 (EABO)

my system: Mac OS 8.6, Labview 5.1, NI-488.2 for Mac OS version 7.6.3, PCI-GPIB card, Keithley 2182 Nanovoltmeter and Keithley 24xx Sourcemeters.
I have a Labview application (modeled on Keithley's application note "Automatic Resistance Measurements on High Temperature Superconductors") which runs well with >99% reliability. The other times it hangs on a GPIB read with a EABO error. The Keithley instruments will complain "Query interrupted" or "Query unterminated". These problems seem to be more prevalent if the computer is distracted with mouse action or other applications, but it'll fail even without such challenges.
Since the application runs, I know my syntax is good. I've tried increasing the timeouts, but this does not pr
ovide immunity. Software delays help somewhat, but with an unacceptable duty cycle penalty. I suspected that I was getting spurious SRQ's for a while, but the GPIB reads that fail most frequently are not those preceded by Wait RQS.
All my GPIB functions are the old style (not 488.2). I'm not using VISA anywhere, since I've found the VISA functions to be even less reliable on my system.
Any suggestions?

Hello,
I realize I getting into this stream after some correspondence, and that you are asking another poster a question. But, if you are simply trying to get your LabVIEW program not to stop and indicate an error, rather continue and discard it, all you have to do is monitor the error cluster, for example, by wiring it to an error cluster selector input, and then in the error case, simply pass out a fresh, new error cluster constant with status = false (no error), code = 0, and an empty source string. The easiest way to do this is to first wire through the no error case to create a tunnel at the output, and then right click to create a constant in the error case. Attached is a screenshot showing both the the error case and no error cases in a quick example.
I hope this helps! Repost if you are having any further or continued problems!
Best Regards,
Jassem
Best,
JLS
Sixclear
Attachments:
Ignore Errors.PNG ‏5 KB

BERTAN ERROR on GPIB error 1073676294

I am using code from this vi package to communicate to 8 High Voltage Power Supplies:
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E9635659CE034080020E748...
Three of the eight power supplies tell me the right voltage. All eight appear to work fine, but five of them will not send back their voltage to the front panel, but they all send back their correct current.
When I run the Bertan 225 simple I get the following error code:1073676294 and the voltage displays 0.0.
Thanks for any help,
Kevin

First of all, that's a warning and not an error. The fact that you are getting it indicates that not enough bytes are being requested during a read. A read would normally terminate on an EOI and not just a specific byte count. The byte count requested can be some large number.
I am not at all familiar with this instrument. My only suggestion would be to use the interactive GPIB/VISA programs in MAX to test the commands. You can use NI-Spy to capture thecommands and compare to what is in the programming manual.

Occasional GPIB Error -1073807342/-1073807300

Hi
I am running a test with a CSA7404B (Tektronix Communication Sigal Analyzer). The system is expected to run for about 7-8 days without interrruption while communicating to this instrument. Occasionally (after 48 hours of running without problems), I get the one of the two errors mentioned above. I dont have multiple open visa sessions. Any ideas?
Thanks

Error -1073807342 mostly is caused when the resource name passed to VISA Open is incorrect. Try to adress your device directly such as: GPIB0::5::INSTR. Make sure not changing GPIB adress on your target device ((Tektronix) while communicating with it.
As a precaution for error -1073807300 prove following. Is there really only one session opened ?
If one of both errors occur, try to open a VISA session and communicate with your instrument via MAX (Measurement & Automation Explorer). Further try to reset your remote GPIB device.
How do you procedure when this error occurs ? Do you restart your VI which is responsible for communication ( or LabVIEW completly) ? Do you reset your GPIB device ? Do you restart your PC ?
Is this error dependent on your GPIB device (does this error also occur if you communicate with an other
instrument) ?
What GPIB Card you are using ?
Maybe you can attach your GPIB communication vi realized with VISA VI´s ?

GPIB errors

Hi
I have posted a message regarding this in the past,however I have still not found a solution. So hopefully someone can help me this time! I am using a PCI-GPIB card with Windows 2000 and Labview 7.0.
I have an Elliot Scientific instrument that I am trying to write to and read from. Everything is working fine from the IBIC control. However, in labview (using the example GPIB.vi given) I am gettting intermittant errors..that is my program works a number of times and then reports an error. I have tried extending the timeouts but the problem persists. I think what is happening is that the GPIB board is taking on the address of my device, as when I use ibpad 0 in IBIC I get a previous value of 4, which is the address of my device (see attached Spy file).
I have attached the Labview program I am using, the Spy file of the program working a number of times and then reporting an error and the spy file of the gpib controller with the address of my device.

You should NOT be using the GPIB Initialization with the same address as the instrument you're trying to communicate with. You are telling the instrument to be the system controller. I can't believe that it works at all. Delete the init function altogether and try it. I don't think you really need the ReceiveSetup either. The example you copied didn't use either of them.
Also, the original example is really old and I'm not sure it's the best one. Unless you have automatic error handling on, you should wire the error in/error out connections and have an error indicator on your front panel.

GPIB error

Hi all,
I just got the labVIEW 5.1 for our lab together with a PIC-GPIB board. I
tried to install the GPIB board into my computer. It seems that everything
is OK during the installation process. But when I started the so-called "NI
488-2(GPIB) Getting Started Wizard", it was said that software presence
verified,hardware presence verified, while GPIB interfaces Sequentially
Verification can not be completed. After I reinstalled the hardware and the
software, the problem still existed. Would you please shed a light on my
problem if you happen to know the answer? Thanks.
Best,
Douglas

thats pretty odd, you may have an irq conflict. Try placing the GPIB card
into a different PCI slot.
Regards,
Rob
douglas_dou wrote in message
news:8mc5j5$pjg$[email protected]..
> Hi all,
>
> I just got the labVIEW 5.1 for our lab together with a PIC-GPIB board. I
> tried to install the GPIB board into my computer. It seems that everything
> is OK during the installation process. But when I started the so-called
"NI
> 488-2(GPIB) Getting Started Wizard", it was said that software presence
> verified,hardware presence verified, while GPIB interfaces Sequentially
> Verification can not be completed. After I reinstalled the hardware and
the
> software, the problem still existed. Would you please shed a light on my
> problem if you happen t
o know the answer? Thanks.
>
> Best,
> Douglas
>
>

GPIB write error code 6, how to do proper wait in GPIB comm

Hi!
I use a Keithley MUX and a DVM to measure different values in my system, including 4 wire resistance. My project runs for several hours without any problem, but last night I have got an error after approx. 8 hours runtime. My error out in the main vi shows the following error:
GPIB Write in A_4Wire_resMUX_2!1,2!3,2!5_new.vi Error code 6.
I have attached this subvi, as you can see, I have put a while loop in the subvi, to give enough time for the 4Wire measurement to be done. But of course maybe another GPIB write function crashes in the subvi, not the one after the while loop.
I have 2 questions:
1. what is the best way to do error handling in GPIB comm., so I could see on my final error out what element caused the problem in this certain subvi?
2. Can someone show me what I could do better in this subvi, to avoid possible GPIB errors?
Its just guessing, but I think the error comes from that I may not give enough time to the GPIB device to perform an action, so the next GPIB write crashes?
plus info: WindowsXP, LabView 2010 Full version
Thanks very much for advice and help!
Solved!
Go to Solution.
Attachments:
A_4Wire_resMUX_2!1,2!3,2!5_new.vi ‏35 KB

2001 driver
7001 driver
Now that you have a modern version of LabVIEW why are you not taking advantage of the instrument driver network? VISA is wonderful and the raw 488.2 primitives should be considered "obsolete".
Since you did not use the specific instrument driver vi's we can't tell which write to what device generates the error you are seeing.
So to specifically answer Q1. Use the Driver's found on the instrument driver network- they are tested and structured in ways that assist in debugging your application and take advantage of powerful features in VISA..
And 2) (see #1) and change the stacked sequence into a state machine
Jeff

GPIB User account error

GPIB ERROR:
I created a prgm in LV to control a 3561A signal Analyzer via GPIB. I was able to run the program in my account.
I copied the main VI along with all the subVIs to another user account (Administator Account) in the same computer. There i could not run the program. The error msg in the attachment always comes.
I have installed the GPIB drivers in this Administator Account.
What could be the problem?
Nghtcwrlr
********************Kudos are alwayzz Welcome !! ******************
Attachments:
GPIB User change error.JPG ‏8 KB

Hi davidek,
Sorry for the late reply. Yes its possible to run the MAX from the other account. It has been installed to use for all users.
Administators have full control and other users have the permission to read and execute.
Message Edited by Nghtcrwlr on 08-24-2009 02:40 AM
Nghtcwrlr
********************Kudos are alwayzz Welcome !! ******************

How do I suppress error messages from displaying in GPIB calls?

I use GPIB Read and GPIB Write to access instruments on the bus. Both vi's supply status on error out.
I sometimes call these routines in situations where I do NOT want to reap error status, so I leave the error out terminal unconnected.
Here's the problem: I get error popups that display the GPIB errors (when there are some) even though I don't connect the error out terminals to simple error or general error.
How can I suppress the error messages??? I do NOT want them to display...
As always, thanks in advance for the assist!!!

PROBLEM SOLVED.
Thanks gentlemen. But... now I have to defend myself!
1. I have both old non-488.2 and newer 488.2 instruments on the same bus. When I send *IDN? to the old instruments, they generate errors. When I send model-specific (non 488.2) commands to the newer stuff, they sometimes error. I have to 'search' the bus and identify specific instruments (by mfg/model) that I'm looking for; I don't know what address they're at. So I go thru a loop (the index is the GPIB address) and for each address I try the old-style probe; if it fails, the new style; if neither succeeds, no one is home at that address. The problem is that in cases where I try the wrong probe for the device first, it frequent gets 'trapped' in the input buffer of that device causing it to incorrectly respond to its correct probe when I finally get to it. So I have to clear the device before sending it the probe to make sure its listening. Can't use *CLR since many devices don't recognize it; and since I can't send a command (yet) because the device is screwed up. So.... I figured out what I have to do to get the devices listening. The NEAT-3xx controllers are happy *after* they receive a null command with a LF (EOS) character - but they generate errors while processing the digital enema just described. The HP spectrum analyzers I use work fine when they get *IDN?, but generate an error on the bus when they receive the probe designed to get the NEAT controller to respond. So what I do is always send an EOS character first to each address before each probe - and then issue a GPIB read. I ignore the errors generated, and the data returned. Then when I probe, I always get a good response (if the probe type matches the device!) instead of an artifact from the garbage the instrument had to listen to. It's like drinking a beer after your wife calls you and nags - it clears your head and makes you ready to move forward. So now you know why sometimes I wanna ignore errors, but thanks for asking.
2. Why don't I use VISA? Well, find me a VISA driver for the NEAT-3xx family of controllers, and I will... I use raw GPIB reads/writes (and nothing else) in my 'scan the bus and probe each address' loop described above. I use raw GPIB commands for the NEAT controllers, and VISA for the HP. You guys designed this stuff, not me... What I don't know (and what you might help me with) is whether there's a 'raw' interface that allows you to talk to instruments using VISA calls when there is NOT a VISA driver for the device... kinda like "I wanna use the GPIB read/write, but use the VISA interface so all my code looks the same" deal...
Thanks again!

My PCMCIA-GPIB cannot start in win2000 system, tne error code is code 10

I installed the Driver V1.60 on my PC,and the PC can identify the card as PCMCIA-GPIB.But It cannot tested pass,as I open the Device manager,I can see the card is errored as "cannoe start,the error code is code 10",
and the resouce all are "?".

Hello,
This type of problem is difficult to diagnose without getting more information. Does it pass Diagnostics? If it fails, what part fails. Error 10 is not a common GPIB error. First I recommend going to http://www.ni.com/support/gpib/pnp2000/default.htm to troubleshoot.
If you cannot resolve the issue in this way, please go to:
http://sine.ni.com/apps/we/niae_asc.main
and request either phone or email support.
Kim L.
Applications Engineer
National Instruments

Gpib error 0

Similar Messages

Maybe you are looking for