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

Similar Messages

  • Error -1073807253 occurred at VISA Read in transient SR830.vi VISA: (Hex 0xBFFF006B) A framing error occurred during transfer.

    Hi,
    I am have written a program with labview to make transient c-v measurement using a stanford research SR830 lockin amplifier. The program seems to be runing fine, but sometimes it is givvibg an error:
    Error -1073807253 occurred at VISA Read in transient SR830.vi
    Possible reason(s):
    VISA:  (Hex 0xBFFF006B) A framing error occurred during transfer.
    Error -1073807253 occurred at VISA Read in transient SR830.vi
    Possible reason(s):
    VISA:  (Hex 0xBFFF006B) A framing error occurred during transfer.
    but if I press ok, the program again starts running. What might be the poblem? BTW I googled a bit and I see that in the labview topic "RS-232 Framing Error with HP 34401A Mulitmeter" by pkennedy32 this is what is said about framing error:
    ""Framing Error" in an RS-232 context means a very specific thing - when the receiver was expecting a stop bit, the line was not in SPACE condition. This can be the result of:
    1... Baud rate mismatch (although other problems would likely crop up first).
    2... Data Length problem, If I send 8 data bits and you expect 7, the stop bit is in the wrong place.
    3... Parity setting mismatch - If I send 7 data bits + parity and you expect 7 data bits and no parity, the stop bit is in the wrong place.
    4... Mismatch in # Stop bits - If I send you 7 Data bits + parity + one stop bit, and you expect 7 data bits + parity + TWO stop bits, the second one might not be correct, although most devices do not complain about this.
    But, I must say that this is the same com port setting that I use to measure c-v hysterysis, but I never gt this error there.
    I attach the program herewith for your kind perusal. Please help me resolve this issue.
    Thanks in advance.
    Solved!
    Go to Solution.
    Attachments:
    transient SR830.vi ‏94 KB
    csac.vi ‏8 KB
    sr830 initialize1.vi ‏15 KB

    @Dennis Knutson  you are right I checked the read indicator in backslash mode, and instead of a \n it is sending \r. So I changed the \n in my write strings to \r. But, if I keep the CLOSE VISA outside my loop instead of inside as you suggested, the termination character appears to come in the middle of the read string instead at the end. And since the read terminates at the \r so it is displaying some junk value before the \r, but if I put the CLOSE VISA outside the loop and play along with the bytes at the read buffer, I see the whole read string with the \r  at the end of the string. But, whenever the values are in exponential form (when close to zero) like 6.938839 e-5, I always get a time out error whatever be the timeout that I put at the VISA initialize. And subsequently, if I stop the program and run it again the machine program hangs and I donot get any reading. Then after I close it again and start, sometimes it hangs for some more or starts working. If I put an arbitrarily large byte count at the READ VISA, then I always get the time out before the operation completed error.
    @ Ravens Fan I have removed the CSAC VI altogether and taking the CH! And CH” reading separately, instead as one string. So, no more issues with that.
    I use the control at the delay so that I can choose how much delay I want to set, and I use the math operation because I am using adding up the delay time to keep track of the time elapsed. Because in the end I have t plot a time vs. CH! And CH” readings.
    I am not sure but probably I am making some silly errors. Please help me out. 
    Attachments:
    transient SR830-2.vi ‏103 KB
    sr830 initialize1.vi ‏15 KB

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

  • Error 33172 occurred at Read & Write data transfer between two or more PF2010 controller

    Hi,i need to do data transfer between two or more FP2010 controller.e.g. FP2010(A) & FP2010(B).
    FP2010(A) need to transfer the measurement (from its I/O module) to FP2010(B) to do the data analysis.These data transfer should be synchronous btw two controller to prevent data lost.
    From the vi used in the attachment,i encountered some problems at:
    (1) Error 33172 occurred while publishing the data.Can i create and publish data under different item name?
    (2) How to synchronies the read & write btw contorller?
    All controller are communicating with each other directly without the need of a host computer to link them together
    Is there any other method to do fast data transfer betwe
    en controller?

    Hi YongNei,
    You were succesful in omiting enough information to make it very difficult to answer!
    Please post your example.
    Please tell us what version of LV-RT you are using.
    Please define what you concider "fast data transfer".
    Have you concidered mapping the FP tags of FP2010(A) to FP2010(B) and vise versa?
    WHat exactly has to be syncronized?
    If you have something that is close to working, share that.
    Well, that as far as I can go with the info you have provided. Depending on the details, what you are asking could be anything from trivial to impossible with the currently available technology. I just can't say.
    It would probably be a good idea to start over with a fresh question (sorry) because not many people are going to know what a a "
    PF2010" is and I can not guarentee that I will be able to get back to you personally until next week-end.
    Trying to help you get an answer,
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Error-1073807322 occurred at VISA Enable Event

    Hi,
    I am getting this error in the HP54825A Oscilloscope instrument VI i downloaded. This occurs when I try to run the "Getting Started" VI that came with the driver. This VI was working fine and now all of a sudden it will not work. I have tried redownloading the driver but it stills gives me the same error.
    It says:
    Possible reasons- VISA (Hex 0xBFFF0026) Specified event type is not supported by the resource.
    Any help would be appreciated.
    Thanks

    Hi gravy,
    It is very odd that the VI was working earlier, and now all of a sudden does not. There is probably something that has changed about the application that has created this error.
    The first place I would have gone would have been to check and make sure that the VI's code had not been altered in any way, but if that were the case it would have been fixed when you downloaded the driver again. There are a few other possible places that could be the cause of this problem, however. Some things to check are to ensure that all of the inputs are the same and wired into the same terminals on the Getting Started VI, and that all of the settings on the instrument are the same.
    If you are sure that the setup is exactly the same, then I recommend running it in highlight execution mode (the lightbulb on the toolbar at the top of the block diagram) to see exactly where this error is occurring. From there we can dig in deeper and see what is going on.
    John M
    Applications Engineer

  • Error -1074388984 occurred at CAN Write (Multi-Chan Single-Samp 1D Dbl).vi

    I keep running into an error with CAN Write.  The error keeps telling me that I have to many messages in the CAN Write que and need to clear then or that the messages might be to short or that I may have to wait until there is a successful read.  I believe the memory is full....Any suggestions

    1.  nctInitialize ("Fuel Value,Pump duration angle,Pump a...", 0, 3, 0, 1)
    Process ID: 0x00000578         Thread ID: 0x000001BC
    Start Time: 15:38:26.656       Call Duration 00:00:00.015
    Status: 0 (VI_SUCCESS)
    2.  nctStart (1)
    Process ID: 0x00000578         Thread ID: 0x000001BC
    Start Time: 15:38:26.671       Call Duration 00:00:00.000
    Status: 0 (VI_SUCCESS)
    > 3.  nctWrite (1, 1, NULL)
    > Process ID: 0x00000578         Thread ID: 0x000001BC
    > Start Time: 15:38:26.671       Call Duration 00:00:00.000
    > Status: 0xBFF62207
    4.  nctClear (1)
    Process ID: 0x00000578         Thread ID: 0x000001BC
    Start Time: 15:38:26.671       Call Duration 00:00:00.063
    Status: 0 (VI_SUCCESS)

  • Error -200428 Occurred at DAQmx Write (Digital Bool 1Line 1Point).vi

    The working program started giving this program after we have had a hard_disk crash. We are just using the program that was backed up. Will appreciate any suggestions on this one. 
    Naresh

    Have you read the explanation for the error and did you verify the task or virtual channels exist?

  • Error -107380734​6 occurred at VISA

    My progarm has a very simple Visa write to a E4432 Signal Generator, which worked very good. After sometime Suddenly an error occurs which I cannot understand :" Error -1073807346 occurred at VISA Write in Setting Generator.vi;Possible reason(s):VISA: (Hex 0xBFFF000E) The given session or object reference is invalid."
    But when I am using the NI-488.2 Communicator with the same SCPI syntax, it works right away. I chose the right Instrument handler address from the pull up menu of the controller.
    What is wrong?
    Regards
    Yariv

    Hi Yariv,
    I didn't dig through every part of your code, but for the most part, it looks good. You've got it set up to run the "Quit" case last, which closes out your two VISA sessions before exiting. However, I did notice that on the "Sensitivity check" case, there is a possibility that the Front subVI will pass out a True, which would then stop the while loop immediately without going through the Quit case. If this happens, and something has happened in the SensitivityBlock 1.vi to interrupt the VISA Resource Name wires (and I did notice that these wires were not passed through in all of the cases in this subVI), then the state machine will exit immediately without passing the proper VISA Resource Name values out to the VISA Close VIs.
    I also see in your post that you said that this error came back after some changes. When this happens, I would always look very closely at the parts of the program that I modified in order to see what I have changed in order to cause the error. You could also go back to a previously saved version of the program and add the changes one by one, making sure that the program still works at each step.
    I won't be able to go through your code extensively, but I recommend tracing through the VISA Resource Name wires and making sure that in every possible scenario, these values get passed through to the close VIs. Good luck with your application!
    john

  • Visa error 1073807346

    I?m new on LabView and create an application that uses a power meter, everything works fine during 127 tests but after this I get the following error message :
    - Error ? 1073807346 Occurred at VISA Write in ?
    - Error Query VI -> ???.
    Posible reasons:
    VISA: ( Hex 0xBFFF000E ) the given session object reference is invalid.
    Why is that the system works fine during 127 iterations ?
    Is there any buffer or something that maybe is getting overload ?
    I hope somebody can help me.

    Hello,
    The open VISA is not exactly in a loop, because it?s in a VI that opens twice on each test but when is open then the VISA session open only is called once and the loop is for the measure, because the meter is accessed X number of times but the VISA session is closed only after all the measures have been made I think this works as you mentioned, then is not really inside the loop, I couldn't send you the Spy capture file the system indicates an error, the file is about 1.2 Mb for one run, I only capture one because the systems run very slowly when the NI Spy is running then it will take a lot of time and a very large file to reach the 127 tests, I think the file is big because the meter it?s not the only instrument
    that I?m accessing, I?m using a generator and a power supply during the same test.
    Let me know if there is another way to send you the file.
    BCU

  • Error -1073807346 will get away when i run VI for second time

    This is the weird thing
    i open the vi for the first time and run it and it will put out the error :
    Error -1073807346 occurred at VISA Open in Prompt for com port.vi
    Possible reason(s):
    VISA:  (Hex 0xBFFF000E) The given session or object reference is invalid.
    i run the vi for the second time and the error goes away.. and everything works...
    i dont know whats wrong, have you had this problem also?
    Attachments:
    serial.png ‏31 KB
    serial.png ‏31 KB

    You know that almost threw me untill I re-read the vi name!
    Dude, that's not how you write a "Prompt User" routine!  What is happening is that you read the VISA In Terminal run that value through the for loop (At warp speed burning a cpu core) while the user fiddles with the VISA in terminal.  BUT, nothing changes the value on the wire!  so you pass the "Old" value to the VISA Open.
    I've been meaning to add Prompt(VISA).vi to my reuse for a while anyhow.  Thanks for the excuse.
    Jeff

  • GPIB locks up after about 15 minutes with a VISA Write Timeout Error

    I am using GPIB to control two electronic loads.  After about 15 minutes of runtime on the program, the GPIB communication locks up.  A probe reveals an error message about a Visa Write Timeout.  When this occurs, I have to stop the program, cycle the power on the two loads, and then restart the LabView program. When addressing the loads, I use the same routine every time.  1) Initialize communication, 2) Send command/request, 3) Close communication.  I thought I might have been overloading the GPIB bus, so that's when I added the close command after each sequence. However, it didn't seem to make a difference.  Could there be a compatability issue with the GPIB of the loads and the NI GPIB or Windows version? (I'm using XP and LV 10)  The electronic loads are older models, so I'm not sure how that impacts this scenario.

    Hi kcarbon80, 
    As this thread is over 2 years old, I do not know what solution was found for the previous problem being addressed, if any. However, if the device is locking up in the middle of your program, you may want to try clearing the device programmatically using the DevClear.vi that comes with the NI 488.2 driver. 
    I hope this helps. 
    Best Regards,
    Thomas B.
    National Instruments
    Applications Engineer

  • Why do I receive error -1073807339 VISA Write

    I have a LV app built using LV2010 SP1 on a WinXP 32-bit machine.  The app uses VISA to communicate serially through a RS232 to USB adpater to a pump.  I can run the compiled app (exe) on another Win XP 32-bit machine without error.  But the app generates "error -1073807339" with a VISA Write VI (timeout before completion) when run on Win7 64-bit machine.  I have verified that both WinXP machines and the Win7 machine all have the NI device drivers installed (NI VISA 5.0.3), the LV2010 Run-Time engine, and the RS232-USB device drivers.
    I have investigated sources of the timeout error and tried increasing the timeout with no success.  I have also verified port settings, although the app is
    identical between all machines.
    I have verified that the installation on the Win7 64-bit machine was done using admin rights and files were installed correctly.
    I feel like I must be missing something, so I'd appreciate some suggesitons.
    Thanks
    Dan 

    Can you communicate to the device on the Win 7 machine using hyperterminal or some some other communication program? Make sure that you have basic communication and it isn't some strange Win 7 thing. Are you runnign Win 7 64-bit? If so make sure you use the correct drivers.
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot

  • Error -200587 occurred at DAQmx Start Task.vi:7

    I am running the attached code Merrit_Coil_calibration, and I get the following error:
    Error -200587 occurred at DAQmx Start Task.vi:7
    Possible reason(s):
    Requested operation could not be performed, because the specified digital lines are either reserved or the device is not present in NI-DAQmx.
    It is possible that these lines are reserved by another task, the device is being used through the Traditional NI-DAQ interface, or the device is being reset. You might also get the error if the specified resource is currently in use by LabVIEW network variables bound to the DAQ Channel, or if the DAQ Channel is being used in any OPC Client software.
    If you are using these lines with another task, wait for the task to complete.  If you are using the device through the Traditional NI-DAQ interface, and you want to use it with NI-DAQmx, reset (initialize) the device using the Traditional NI-DAQ interface. If you are resetting the device, wait for the reset to finish.
    Device:  Dev2
    Task Name: _unnamedTask<F>
    I am calling the same DAQ, many different places in my code and I think that is the problem, but I can not figure out why or hw to fix it.  Anyone have any suggestions?
    Attachments:
    Final.zip ‏2434 KB

    Thank you both for your input.  I slightly changed my code to Merritt_Coil_calibration (updated code attached) and the first error went away, but now I have a different one which is:
    Error -200429 occurred at DAQmx Write (Digital U32 1Chan 1Samp).vi:1
    Possible reason(s):
    Value passed to the Task/Channels In control is an empty string (or I/O control).
    The value must refer to a valid task or valid channels.
    As far as what DAQ device I am using, it is the NI USB 6009.  I am only using digital port 0.  During different pieces of my code I send different values to port 0.  I am using this to drive some stepper motors.  I thus send square waves on the different pins on port 0.  I do not know if this is exactly what you were asking. 
    Whatever the case, I was wondering if anyone knows why this error occurs and how I could fix it. 
    thanks.
    Attachments:
    honorsproject.zip ‏256 KB

Maybe you are looking for