Error 14 ocurred at GPIB write, labview cant add resource

I am using LabView 2009 to control a research system contains Lakeshore 331S and Keithely 2425, it was work probably , but recently I am receivng an error message:
Error 14 ocurred at GBIB write, LabView cant add resource

Hello baalbiss,
Which version of the 488.2 driver do you have installed?  Just to confirm, you are able to communicate with the instrument through MAX, but not through LabVIEW?  Did you recently upgrade to LabVIEW 2009?
Thanks
Ryan T
National Instruments
Applications Engineer

Similar Messages

  • Keithley 6517B GPIB Write Error 7

    Hello,
    I have a Keithley 6517B running and communicating with PC through GPIB. The program was initially running fine, and giving the current-noise signal against applied voltage (as programmed). But now when I run the program , it is giving an error that arises at the 6517 Reset/Preset.vi -
    Error 7 occurred at GPIB Write in Keithley 6517A Reset / Preset.vi
    How do I get rid of this error. I don't understand how suddenly an error arised when I changed nothing in the program or settings of the keithley. The keithley is configured at GPIB address 27.
    I am attaching the main program and the sub.VI llb file .
    Now when I run the main program, the graph does not show any current or noise signal, but it shows a straight line plotted along '0' along the x-axis (that is, against time or voltage)
    Please help.
    Best Regards,
    Poulomi Das.
    Institute for Microsystems Engineering.
    University of Freiburg.
    Freiburg, Germany.
    Attachments:
    VI Measurements_v4.vi ‏45 KB
    kei6517v6.llb ‏1213 KB

    Hello Mike,
    I was on leave hence the late reply. I have attached the entire LV main vi with the sub VIs llb file to the very first message on this post. I have attached them again to this message.Do you mean something else?
    Best Regards,
    Poulomi Das.
    Institute for Microsystems Engineering.
    University of Freiburg.
    Freiburg, Germany.
    Attachments:
    VI Measurements_v4.vi ‏45 KB
    kei6517v6.llb ‏1213 KB

  • 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

  • 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

  • Error 6 in GPIB Write

    Hi
    I have a LabVIEW code acting as a driver for an EG&G 5210 lock-in amplifier. Essentially I am using the GPIB write vi to send a string to the amplifier.
    I have been trying to de-bug my code for a while.
    The problem is, I have split the code into each constituent control and each separate part (e.g. changing phase or filter type etc.) works absolutely fine on its own. Also, when I combine several of these into one string it also works fine, apart from the addition of the very last part. 
    At this point I get error 6 "LabVIEW:  Generic file I/O error. NI-488:  I/O operation aborted."
    I cannot then check any of the others parts work after this point since I only get the same error, even just testing one constiuent part (which had been working well beforehand)
    I am using Labview 2011 with an NI GPIB-USB-HS with the previously mentioned EG&G 5210 amplifier.
    Any help is greatly appreciated.
    Please find attached my LabVIEW if required.
    Jordan B
    Attachments:
    test 3.2.vi ‏28 KB

    My guess is that when you are stringing the commands together, you aren't waiting long enough for at least one command to complete.  I can't see the VI because of the ancient version of LV that I have at work, but if the instrument is SCPI compliant, consider appending ;*OPC? to each command that isn't already a query.  This will turn that command into a query, so you execute a read (of a couple of bytes) and it will wait until the instrument has completed the command.
    Read the instrument manual to make sure that the commands you are going to modify in this fashion are compatible with the *OPC? command.
    Bill
    (Mid-Level minion.)
    My support system ensures that I don't look totally incompetent.
    Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

  • FieldPoint Write LabVIEW Error -33499

    Hi all,
    I'm going to try to explain this as coherently as possible:  
    I've got an application running on a cFP-2200 that uses LabVIEW 8.6.1 and FieldPoint 6.0.4.  This application is communicating with some IO modules on a FP-1601 over Ethernet.  I've set up my devices in Project Explorer, and they match the hardware configuration exactly.  (I double checked all of the IPs and everything.)  I compile the RT executable and place it on the controller when it's connected to my development machine.  Then I disconnect the controller (physically) pick it up off of my desk, and connect it outside in our equipment.  (This equipment is on an isolated network - I can't connect to it from my development PC)
    Oddly, I'm getting error -33499 on my FieldPoint writes to the FP-1601 bank of modules.  The description for -33499 is "Cannot communicate with the specified remote module."  I've troubleshot lots of FP errors before, but I've never seen this one.
    There's a PC on this isolated network that runs my client application that communicates with the controller. On that PC, I can see the modules in MAX and on the distributed system manager.  I even checked the aliases file on the RT controller, too,and those IPs match up.  I know the modules are communicating -- just not with my RT application, and I can't find any instance of this error code anywhere on the NI site. .
    Can someone shed some light on why this would be occurring?  Has anyone ever gotten this error code?  Hopefully I've provided enough information.
    Thanks,
    Jim
    P.S.  Due to the proprietary nature of the code, I can't post it.  I could probably take screenshots of portions of it, though.

    Hi Will,
    Thanks for your response - you've brought up
    some great suggestions.   Actually, on Friday before you posted your
    message I brought the controller back to my desk (the development
    machine) and completely reformatted it.  I also built the Fieldpoint
    hierarchy over again in Project Explorer, and placed all new tags in my
    FieldPoint IO VIs.  Lastly, I checked fpremote.ini on the cFP-2200 to
    verify that the IPs match the textual aliases that appear in the FP
    tags.
    After all of that I thought for sure that
    everything would connect properly, but as of this morning I'm still
    getting some instances of error -33499.
    Another detail that may be useful is the following:
    We've
    got sort of an unusual setup.  The cFP-2200 controller resides outside
    of a hazardous area, while two FP-1601s reside inside the hazardous
    area.  The cFP-2200 checks to ensure that it's safe to power up the
    1601s and their associated equipment, and then turns them on after the
    check completes.  I would expect a few errors to be thrown when
    initially trying to connect to the 1601s right after they power up, but
    the -33499 errors persist indefinitely and they seem atypical among
    the errors I've seen in the past.
    I'm sure by now that
    this is as clear as mud.  If you have any insight, though, I'd be very
    appreciative.  Do you know, specifically, in which instances -33499
    shows up?  There are several errors that result from bad connections
    and it can seem a little ambiguous at times.
    Thanks very much,
     Jim

  • HT201210 my iphone was being updated when it was ready to restore it stops sayin an error ocured, the phone wont oparate cant get it to restore

    my iphone was being updated when it was ready to restore it stops sayin an error ocured, the phone wont oparate cant get it to restore

    any specific error messages? If so, check out http://support.apple.com/kb/ts3694 for solutions
    if not, force restore: http://support.apple.com/kb/ht1808
    NB: make sure you have a backup, because following the last article will remove all data/content on the device.
    Good luck

  • Error -1073807346 occurred at VISA Write in rsspecan_core_write.vi

    Possible reason(s):
    VISA:  (Hex 0xBFFF000E) The given session or object reference is invalid.
    I'm using a USB to GPIB connection to a Rohde Schwarz FSV30 Spectrum Analizer from Windows 7.
    My program works 100% in LabView but the problem comes in when I've compiled the program into an executable.
    I have already installed the NI VISA Run Time Engine 5.0.1 and it still does not work.
    I've also installed the NI-488.2 2.73 drivers for the GPIB unit.
    Any ideas?
    Solved!
    Go to Solution.
    Attachments:
    Error -1073807346 occurred at VISA Write.png ‏30 KB

    Hey,
    the problem when building executables with LabVIEW is, that the driver core of the attribute based instrument drivers (esp.. the VIs which are creating this error) is linked while runtime dynamically to the VIs. The application builder which follows all dependencies and include them into the package fails in this case.
    To get a running executable please add manually all VIs for the folder <inst lib>\rzspecan\_utility\rsspecan_core\callbacks\ to the LabVIEW project and everything should work fine.
    For more details of this driver refer to http://www.rohde-schwarz.com/appnote/1ma170
    So long, juergen

  • Error 63 occurred at DataSocket Write in getWavelength_v80 EDITED.vi, help? please!

    Hey guys, I am new to LabView and I have thought myself everything that I know.  I am an undergraduate student at NC A&T.
    Okay so I took a peice of code that I acquired from Bristol, and it's for a Bristol Wavemeter V1.22.  I first edited it to get a graph in there to show the data, and get a slope and Y intercept.  Now I am trying to connect it to a computer that controls a COntinuum ND6000.  We have existing code for the ND6000 that lets the two computers connect.  I took the code out of there that was the part that connects them and now when I wired everything up, I get the "Error 63 occurred at DataSocket Write in getWavelength_v80 EDITED.vi" error message.  it states; Possible reason(s):
    LabVIEW:  Serial port receive buffer overflow.
    =========================
    LabVIEW:  The network connection was refused by the server. For TCP/IP, make sure the server is running and listening on the port you are trying to use. Firewalls can also cause a server to refuse a connection. For VI Server, make sure you have enabled VI Server from Tools>>Options>>VI Server:Configuration."
    I tried making sure everything in the configuration was correct and it all is.  Can you guys please help me?
    Thank you. 
    I have attached the folder that it is located in because you do have to have the library function.  The file is located in the Bristol Wavelength Meter V1.22\Programming Interface\LabVIEW example I.
    Thank you again!
    Solved!
    Go to Solution.
    Attachments:
    6.jpg ‏153 KB
    7.jpg ‏112 KB

    So I went through and realized that I had the wrong port typed in by 1 number, I changed that and put in the correct port for the TCP address.  Now when I run it I get this error message 66....
    "LabVIEW:  The network connection was closed by the peer. If you are using the Open VI Reference function on a remote VI Server connection, verify that the machine is allowed access by selecting Tools>>Options>>VI Server:Machine Access on the server side."
    Any help?? I checked the Server Machine access and all of them are set to allow.

  • Error -200609 occurred at DAQmx Write: Selected Buffer Size Too Small

    Hello, I'm writing some simple test VI's that I will eventually build upon to make an externally clocked analog output VI. I started with a very simple program to output finite samples using the onboard clock with the DAQmx Timing.VI. When I run the program, I almost immediately get an error. The error message is below.
    Error -200609 occurred at DAQmx Write (Analog DBL 1Chan 1Samp).vi:1
    Possible reason(s):
    Generation cannot be started, because the selected buffer size is too small.
    Increase the buffer size.
    Conflicting Property
    Property: Output.BufSize
    Corresponding Value: 1
    Minimum Supported Value: 2
    Task Name: _unnamedTask<1C>
    I have used DAQmx VI's before in similar applications and never encountered this error. Additionally, I read at the link below that DAQmx Timing.VI should be generating the buffer automatically. Any ideas as what could be causing this?
    Specs:
    Windows 7
    Labview 2012
    PCIe-6353 as DAQ board
    Below is a picture of my block diagram and the VI is attached.
    Solved!
    Go to Solution.
    Attachments:
    FiniteSamplesTest.vi ‏18 KB

    Oops. Just realized my very silly mistake: I forgot to add the Start Task VI. I did so and it works as designed.

  • Error-10608 ocurred at AI singlescan

    hi,
    i'm using windows 3.11 with labview 4 on a lab-pc+ card. i've been using the example ContAcq&Chart vi, but modded to log the data to a text file to acquire data from 2 channels. it had been working fine, but this morning i had to change the card configuration from unipolar to bipolar. it all checks out in the configuration utility, passing the tests etc.
    but when i run the actual vi it come back with the following error:
    Error-10608 ocurred at AI singlescan
    NI-DAQ: LV no transfer is in progress for specified resources.
    i'm sure it's a competing acquisition problem, as running the vi for either channel 1 or 2, is o.k, but together i get the error.
    nothing else is running or attempting to access the channels (config test/utility etc)
    baffled why it's suddenly stopped working?
    thanks for replies in advance.

    Hi Jaykay,
    Please can you tell me what version of NI-DAQ you are using so I can try to replicate you system as closely as possible.
    I have a copy of LabVIEW 4.1 that I can use, this is the earliest version I can get a hold of, so when I have your DAQ version I can install that try your code.
    Regards
    JamesC
    NIUK and Ireland

  • GPIB Write to multiple address

    How do you write commands to multiple instruments?  I get Error 6-GPIB
    Controller not in charge when I use GPIB Write consecutively in block
    diagram.  Is there an easy way?
    Attachments:
    Multiple IO.llb ‏25 KB

    Hi Rig
    see attached llb
    Its quick and 'dirty' it assumes you already know instrument addresess's!
    Note use of sequence -this can be improved by either state machine or
    simply by connecting vi in series using error connection as link.
    No error detection coding has been added. This could cause problem with regard to time out etc.
    Basically it should give you inspiration.
    xseadog
    Attachments:
    Basicinstr.llb ‏204 KB

  • Error-50150 occured at DAQmx Write

    Hello,
        I am experiencing a seemingly random error in a large program. The error occurs in a part of the program that simulates tach signals to a CPLD. I have not been able to find out what conditions cause this error, it seems to be random in nature.
    The full error reads this:
    Error - 50150 occurred at DAQmx Write(Digital 1D U16 1Chan Nsamp).vi
    Possible Reasons:
    The software has entered an unknown state-usually as a result of a cascade failure induced by an unexpected series of state inputs. The operation could not be completed as specified and you should immediately terminate all further transactions if you are able to do so.
    Task Name:TackABC_Write Port0 U16
    The device we are using is a PCI-DIO-32HS, with Labview 7.1, NI-MAX 4.1, and DAQmx drivers 8.3.1. The task writes 3 signals to the CPLD, and it works most of the time, but every so often this error will occur. I was wondering what could be the cause of an error like this?
    Thanks, Steve

    Hello Brian, thanks for the response.
    I made a mistake in my last post, it is actually a DAQmx clear task in place of the stop task vi i mentioned. When we first received this error it had no clear task at the end, but I added one. Even with this the error has still shown up from time to time. Would it help at all to add a reset device vi afte the clear task vi?
    I took some screenshots for you as well. The first shot is of the function in question, the second is the same shot with the case turned to false, and the third is the inside of the main subvi. When the error occurs it focuses on the write vi that is inside the subvi. Let me know if there is more info I could grab that would make things mroe clear.
    Thanks,
    Steve
    Attachments:
    SS3.JPG ‏160 KB
    SS1.JPG ‏189 KB
    SS2.JPG ‏181 KB

  • Créer un "client" GPIB avec labView

    Bonjour,
    Bien qu'il existe passablement de docs sur le bus gpib et son utilisation, je n'ai rien trouvé qui efface mes doutes à propos de ma question.
    Voilà ma problématique:
    Une application d'un client veut contrôler ma machine (qui execute un VI donc) à travers le bus GPIB. C'est un peu stupide, au jour d'aujourd'hui, d'utiliser un tel bus mais on ne choisit pas ...
    Pour moi, ce qui est flou, est de savoir comment aborder la programmation d'un client "esclave" gpib. D'abord, est-ce vraiment un esclave à part entière? Est-ce que un clent doit réagir aux commandes du master ou il peut avoir une initiative? et surtout, comment acquérir un ordre? par un read?
    Merci pour vos réponses à ces questions générales.¨
    Gaëtan

    Bonjour,
    Quelque soit le bus de communication lors d'une conversation maître/esclave, le client (l'esclave) ne pourra pas agir sans commande, c'est à dire il ne pourra pas prendre d'initiative. Sauf si le Master lui donne l'ordre d'avoir des initiatives, et lui définit les initiatives.
    On pourra utiliser les fonctions "GPIB read" et "GPIB write" pour établir la communication.
    Cordialement,
    Christophe S.
    FSE East of France І Certified LabVIEW Associate Developer І National Instruments France

  • Cant add account manager from myverizon  keeps throwing error message

    did everything but go into the store. Im 9 months pregnant on bed rest and my verizon gives me an error when i try to add account manager. Called  922 0204  and customer service says its now verizon policy that you cant add anyone to your account until after 30 days   ive added and removed people before on the same day Talked to supervisor he said its a my verizon problem and that the ppl that are supposed to work on it arent in right now So shouldnt they have a way to bypass this??  what is up with this new rule?? Anyone else getting this same error??

       I originally had wireless service with Alltell and I was very concerned when Verizon purchased Alltell ( I had numerous bad experiences with Verizon customer service when I had their FIOS cable service).  For years now that Verizon took over for Alltell I have not had any issues and I believe it was because I did not have to contact customer service.   Now in December I purchased three new phones and my daugther wanted to change her work number to one of the numbers I had on my service.  You would have thought we were trying to pattern a new cure for cancer.  We had to spend hours on the phone with customer service trying to accoumplish a very easy task and each time my daugther tried to deal with these people they all complained because she was not an account manager. 
    For the last wo weeks I have tried to add my daughter thru the website.  Each time I got an error message stating that I needed to call 611 to get this corrected.   Tonight we called 611  and I got the same run around with customer service for the last 45 minutes, but they told me that I had to wait 60 days since we had purchased  new phones.   They also told me that we could go to a Verizon store location and this could be accomplished at the store.  I have already spent more time with customer service than any live person should and I certainly do not want to have to make another trip to a Verizon store.  It is utterly amazing how Verizon can take such simple tasks and turn them into a Federal case.  This waste hours of your time and also the time spent by their employees,  and you don't get anything accomplished.  They must be getting so many complaints that now there is no place on their website where you can write a complaint.         

Maybe you are looking for