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.

Similar Messages

ERROR 1073676294 ????? VISA READ...!!

Dear All
I am Writing and Reading the data from one EEPROM,interfacing with a PIC16F690,like this i am swiotching 240 EEPROM with MUX,through LabVIEW serial communication pallets,I am controlling the Reading/Writing, but some times ERROR 1073676294 ????? VISA READ...!!,once this error occurs next all EEPROM chip are not able to READ /WRITE,if unplug the powersupply and plug it back,then LabVIEW can Read/Write,i am not able to fix this error,please advise me whether problem is from LabVIEW or MICROCONTROLLER,I used delay function but also same problem.
Raikar A G

1073676294 is not an error but a warning saying that you got exactly the number of bytes you requested in the Visa read, and that there might be more bytes still remaining in a serial buffer. (Which I've always considered this a stupid warning, because as a programmer, I'm going to assume that there might be more data in the buffer than I have just pulled out.)
The warning should not cause any problems in your LabVIEW code, nor should it cause a problem with your serial communication. So if you lose communications with your microcontroller, it must be something else going wrong.

Error 1073676294

Hi,
The following codes i posted below is not written by me.
Now i got a problem with the setting.
Basically, i have a NI camera with Gige and Rs232 connection to the computer.
I can snap picture using MAX or VBAI.
but i cant get my picture in the LABview executable program.
It shows 1073676294 error message.
i know its just a warning message, but seems like my camera doesn't work well with my program.
I suspect is connection/setting problem.
Can anyone help me with the setting problem, if possible, no source code change attempts.
(As this program is proved to be working fine for 1 year already)
here are the codes.
Attachments:
serial write read.JPG ‏172 KB
error msg.JPG ‏7 KB
no error.JPG ‏140 KB

more attachments.
Attachments:
error.JPG ‏136 KB
MAX setting.JPG ‏61 KB
network ip.JPG ‏37 KB

Old visa open, error code 1073807343, using VISA with a GPIB device, and VISA resource names

Hi everyone,
I'm trying to get a SRS model SR720 LCR meter (manual on this page) working with LabView, connecting it to my PC with an Agilent 82357A GPIB/USB interface (manual on this page). I'm running MAX version 14.0, and NI-VISA version 14.0. I'm running LabView version 13.0f2, 32 bit.
I followed the directions on this page, and I'm pretty confident I can communicate with my LCR meter, because I can go to NI MAX->GPIB0::17::INSTR under "devices and interfaces", then go to the VISA test panel, go to the I/O tab, and I can enter a few commands from the SR720 manual, like changing the frequency, and I see the light on the LCR meter change to what I just told it to do. Here is a picture, just to illustrate it:
Also, if I do the *IDN? command, it returns "
9: Write Operation (*IDN?)
Return Count: 5 bytes
10: Read Operation
Return Count: 41 bytes
StanfordResearchSystems,SR720,08087,1.03\n
So, that's good too. I also made the alias of this device "MyLCRmeter", but that shouldn't matter for now.
Now I'm trying to get it to work in a more usable way. The SR7xx drivers that LabView found for me came with a couple sample programs, one called "Getting Started.vi". I tried to just simply see if it worked, changing the "instrument descriptor" field to "GPIB0::17::INSTR", since that's the one that seemed to be the right device in MAX. Here is a picture of the front panel of "Getting Started.vi":
Trying to run it like this gave me this error (code -1073807343):
Old VISA Open in SR715/720 Initialize.vi->SR715/720 Getting Started.vi
Doing a bit of searching on these forums, I found these few threads (1 2 3), which seem to tell me that, since this program was written, the way you open VISA has changed. In the 2nd of those links, one guy said:
You just have to replace the Old VISA Open function with the VISA Open that is on the Instrument I/O>VISA>VISA Advanced palette. When you do that, the wire to the string that was used for the resource name will be broken. Delete the string and make the actual VISA Resource Name visible on the front panel. Wire the VISA Resource Name control to the connector pane where the string control was (upper left connection).
So, I went into the sub-VI Initialize.vi, and did that. Here is a picture of what the front panel and block diagram of the sub-VI Initialize2.vi (I changed the name in case I screwed things up, but I'm pretty sure the new one is the one being called by Getting Started.vi) looked like before I changed anything (you can see the Old VISA Open):
and here it is after replacing that with the regular VISA Open, deleting the instrument descriptor string and replacing it with a VISA resource, and connecting that to the VISA Open:
However, as you can see in the image above, and it seems like someone else had this problem in the 2nd thread linked above, I don't see my device listed in the drop-down menu (even if I refresh), only "LPT1" (I don't even know what that is):
No, I wasnt able to select the visa resource from the pull down menu. somehow it seems disabled or something.
If I just enter the VISA resource name from MAX manually, GPIB0::17::INSTR, and save and try running that, I get the error(code -1073807346):
VISA Open in SR715/720 Initialize2.vi->SR715/720 Getting Started.vi
So I'm not sure where to go from there, or why it's not in the drop down menu to begin with. I'm sorry if I've missed something but I've searched about as far as I can go. If I had to guess, maybe one thing could be that in MAX, under Tools->NI-VISA->VISA Options->My System->Conflict manager, I have both Agilent VISA and NI VISA enabled; I know sometimes problems arise from conflicts between different software fighting over the same hardware. Is this okay, or do I need to change it?
Thank you and please let me know if there is any other code/screenshots I could provide that could help!

Hi, I did indeed enable NiVisaTulip.dll under MAX->Tools->NI-VISA->VISA Options->My system->Passports->List of passports. Sorry, I should have mentioned that explicitly.
By install as primary, do you just mean as it is here, where it is selected as the "Preferred VISA"?
Or somewhere else? I installed NI-VISA first I believe, and then the Agilent one, and during the installation of the Agilent one, I'm pretty sure I made it not the primary. Here's what I have in the Agilent (it's called Keysight now) Connection Expert software:
I also have this under the "Keysight 488 options" tab:
Should that be checked? I don't actually know the role of VISA vs 488 here...
What could I try?
Thank you!

Error when running software on computers w/o GPIB interface card

I'm writing some simple GPIB I/O software using the VISA libraries and I'm getting an error when I run the program on a computer that doesn't have a GPIB card. The error is "The application failed to initialize properly (0xc0000142). Click on OK..." The program runs and works fine on the machine that is hooked up to GPIB devices, but I would like to be able to use my laptop for development. I've installed version 2.3 of NI-488.2, so all the required dll libraries are there.
Thanks in advance,
Jeff

Unless you're using all IVI drivers, there is no built in simulation mode. As long as you make calls to VISA that expect a GPIB board, you'll get errors. Even if you had a gpib board, if you write your code correctly, you would also get errors when the board doesn't find an instrument to write to or read from. The only solution is for you to write your own simulation code. Encapsultate your write/read functions with case statements that skip the driver calls and return simulated data.

Error 7 occurred at Open File+.vi:Open File,NI-488: Nonexistent GPIB interface

I did some clean-up of my computer and have been having issues ever since.
I'm not the one that did the programming; the person who did is long gone.
The VI loads fine but when I hit run I get:
Error 7 occurred at Open File+.vipen File
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Nonexistent GPIB interface.
All the necessary VIs are available and I've tried changing all the file calls in the VIs to the new locations but the error is the same.
Any suggestions?
Thanks.

Error 7 is a generic file not found. If it is happening after cleaning up files, more than likely you moved some subVIs called in a main VI to a new location on your computer. If all the VIs are in a project, a possible solution would be to remove the vis in the project directory and add them back to the project as they may be pointing to a previous location where the files were once stored. Perhaps this is what Anon123123123 meant by "linking". Hope this helps.
Regards,
Isaac S.
Regards,
Isaac S.
Applications Engineer
National Instruments

How to resolve the error -1073807339 when using Agilent LAN/GPIB Gateway (E5810A)?

Dear Sir/Madam,
Appreciate that you could advise me on the following error occur when connect power meter E4419B to computer via E5810A LAN/GPIB Gateway(remote interface) & run with Labview:
-1073807339
VISA Write in E4419_read_power.vi
I have added 5s timeout to Labview program but the result as previous.
There no error occurs when the power meter to computer via USB/GPIB interface(82357B).
Is it related to E5810A driver or the program I wrote?
How to resolve it?
Attachments:
E4419_read_power.vi ‏16 KB

Hi.
I'm experiencing the same problem when connecting a laser controller (New Focus Vortex TLB-6000) via the Agilent E5810A to a PC.
There are no problems when connected through a regular serial port, but timeouts arise every few seconds through the E5810A. I have another controller (SRS LDC501) which works very well with a second Agilent console.
Have you managed to find a solution to this problem?
Thanks,
Orel.

Error Code 10 with GPIB PCI Card

PC used: Dell optiplex GX110, lastest Bios release, Windows 2000 SP4, GPIB Drivers version 2.2, Local Admin session.
After having install the driver (without the GPIB)and plug the card, this one is automaticaly recognised by the Os.
But, after the reboot (asked by the OS to validate the installation), the GPIB card appears, in the device manager, with an error code 10 (not started)....
I tried with two (new) differents GPIB PCI Card, two OS (First time with NT4.0 SP6 Drivers 1.7 and now, Win2000 SP4 Drivers 2.2) and with two PCs Dell Optiplex GX110 !
I even tried with a "Ghost" from an other PC (also an Optiplex GX110, with the same model of GPIB Card)
-> I obtain the same error each time !
Help me please..........

Hello,
Could you give me the exact reference of the board (PCI-GPIB, PCI-GPIB+, AT-GPIB, AT/GPIB-TNT...)?
Is the error code displayed on the Windows device manager (in the properties dialog box of the device)?
What is the exact description of the error code?
A PCI-GPIB installation do not need to reboot the OS if the NI-488.2 driver is correctly installed. The board should be recognized in MAX and you must be able to scan for instruments and start I/O communication with the device from test panels in MAX.
Update me as soon as you receive another feedback.
Regards.

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

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

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

PNA Guided Calibration: GPIB write error in for loop

Hi,
I have a LabVIEW program that creates a Guided Power Calibration on a PNA.
After initializing everything properly, I have a for loop that loops through all the manual steps that the user must go through (ex: Connect Channel A of Power meter to Port 1" "Connect male Short to port 1" etc).
The problem is, the program displays an error at the first command: sens:corr:coll:guid:acq STAN1
I says there is an error with the GPIB Write function.
Here are the commands I send:
SYSTRES
DISPlay:WINDow2TATE ON
CALCulate2ARameterEFine:EXT 'MyMeas',S21
DISPlay:WINDow2:TRACe1:FEED 'MyMeas'
CALC1AREL 'CH1_S11_1'
SENS:FREQTAR 2e9
SENS:FREQTOP 4e9
SENSWEOINTS 3
SENS:CORR:COLL:GUID:CONNORT1 'APC 2.4 male'
SENS:CORR:COLL:GUID:CONNORT2 'APC 2.4 male'
SENS:CORR:COLL:GUID:CKITORT1 '85056D'
SENS:CORR:COLL:GUID:CKITORT2 '85056D'
SENSe:CORRection:COLLect:GUIDedSENsor1 ON
SYSTem:COMMunicateSENsor gpib, "13"
SENSe:CORRection:COLLect:GUIDedSENsor1OWer:LEVel -20
sens:corr:coll:guid:init
sens:corr:coll:guid:steps?
//for loop from 1 to total_number_of_steps
sens:corr:coll:guid:desc? <step#>
sens:corr:coll:guid:acq STAN<step#>
The program quits right at the first step, when I send "sens:corr:coll:guid:acq STAN1", although the command is executed.
Also, the VBScript with the same commands works fine.
Can anybody help me? I've been stuck for a while now.
I attached the block diagram of the for loop.
Thanks in advance,
Nicolas
Attachments:
Guided cal for loop.vi ‏27 KB

Sending SENS:corr:coll:guid:acq STAN1 \n gives me a different error: -101 "Invalid Character".
From my different attempts at figuring this out, I thought the problem would come from LabVIEW, since the vbscript with the same commands works on the PNA.
I also modified the for loop because I thought each iteration should be linked to the previous one with the error wire (see attached).
I still have the same issue, only the first iteration is executed, then the program quits.
Attachments:
Guided cal for loop.vi ‏28 KB

When I try an install the GPIB drivers from the CD for NT I get an error. It says the GPIB software is not properly instal

led. Please run the GPIB setup software from your disk. Once it is installed use ibconf to modify your settings. Under error information is says file: reginfo.c Line: 3601 and Item knownDLLs. Am I missing a file, what is reginfo.c, what is error 3601?

led. Please run the GPIB setup software from your disk. Once it is installed use ibconf to modify your settings. Under error information is says file: reginfo.c Line: 3601 and Item knownDLLs. Am I missing a file, what is reginfo.c, what is error 3601?I might recommend either copying the contents onto your harddrive and install from the fixed disk or download the NT driver from http://www.ni.com/support/gpib/versions.htm

Why do error comes when trying to use NI ISA GPIb and NI DAQ card (both PnP)together while they work well when one at a time?

we configured gpib pnp and at-mio-64e3 cards (isa) in the same pc.gpib function was invoked to take the device to remote and listen mode.now when daq function getDeviceInfo is called the remote mode of the device is removed and after this it always shows no gpib board until pc is rebooted

Hi,
I have some questions:
What OS are you using?
What driver versions?. You can find the driver versions in the Windows Add/Remove programs utility. DAQ driver is NI-DAQ anmd GPIB driver is NI-488.2.
Is there any error code?
I haven't found any known issues between these two drivers. How are the board's resources configured? Base address, IRQ, DMA.
Let see if with this information we can clear out what is going on.
DiegoF.

Error on NI-488.2 GettingStarted Wizard (PCMCIA-GPIB) "TROUBLESHOOTER.EXE" fails.

Can't verify my PCMCIA-GPIB card because:
Error message on NI488.2 Getting Started Wizard...
TROUBLESHOOTER.EXE is linked to missing export MFC42.DLL:6907

Kindly goto http://www.ni.com/support/install/ and follow the steps to dowload the latest driver.

BERTAN ERROR on GPIB error 1073676294

Similar Messages

Maybe you are looking for