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

Similar Messages

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

  • When trying to work with Agilent 34401A multimeter (serial RS-232 connection), HP34401A Getting Started.vi gives always the message: "Error 1073807369 occurred at Old VISA Open ".

    Baud rate and parity are set correctly, RS-232 cable is also connected correctly. My QuickBasic program has no problems to read and write to the Multimeter. It is obviously a software problem: the same error is persistent if I disconnect RS-232 cable.
    I downloaded NI-VISA 2.6 for Windows 95/98/NT/ME/2000/XP frorm digital.ni.com and installed it. But it did not help.
    Thank you in advance
    Best regards
    Alexei Soloviev

    Hi Steve
    I have problems with the 34401A and serial communication. Do you remember
    where the error was in the code ?
    Thanks
    Klaus
    wrote in message
    news:[email protected]..
    > Alexei,
    > This may or may not help, I was tasked to do something similar
    > recently and found an error in their driver. The GPIB VISA worked
    > fine, but when I tried it on serial it played up. There was an errant
    > carriage return (or CR/LF I can't remember). GPIB liked one and Serial
    > liked the other. It always amuses me that we never have problems with
    > Quickbasic!.
    > If you want me to dig deeper give me a shout.
    >
    > Steve Watts
    >
    > On Thu, 24 Jan 2002 06:16:55 -0800 (PST), "Alexei V. Soloviev"
    > wrote:
    >
    > >When trying
    to work with Agilent 34401A multimeter (serial RS-232
    > >connection), HP34401A Getting Started.vi gives always the message:
    > >"Error 1073807369 occurred at Old VISA Open ".
    > >
    > >Baud rate and parity are set correctly, RS-232 cable is also connected
    > >correctly. My QuickBasic program has no problems to read and write to
    > >the Multimeter. It is obviously a software problem: the same error is
    > >persistent if I disconnect RS-232 cable.
    > > I downloaded NI-VISA 2.6 for Windows 95/98/NT/ME/2000/XP frorm
    > > digital.ni.com and installed it. But it did not help.
    > >Thank you in advance
    > >Best regards
    > >Alexei Soloviev
    >

  • Error 1003 occurred at ABAPI Dist Chg and Save VIs.vi

    I used to be able to build executable file for my application. However when I upgrade to LV8 and try to build executable file, I got the following message.
    Error 1003 occurred at ABAPI Dist Chg and Save VIs.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  The VI is not executable.
    The vi is perfectly executable in LV enviroment.
    Anyone know what's going on?
    Thanks in advance!

    DGU,
    Unfortunately this is a known bug in LabVIEW 8.0.1. Our R&D department is well aware of the issue and is currently working on the problem. In the mean time there are some possible work arounds
    Check the "Enable debugging"option in the "Advanced Category" of the application executable properties.
    Disable the "Remove Panel" option for all SubVIs containing Shared Variables in the build
    Try Unchecking the "Disconnect type definitions and remove unused polymorphic VI instances" options also in the Advanced category of the executable properties as shown in the attached figure.
    Move shared variables to the top level VIs and pass the data through the SubVI connector
    Downgrade to LabVIEW 8.0.
    I apologize for the problem. Please let us know if these suggestions help out. Thanks!
    Best Regards,
    Chris C
    Applications Engineering
    National Instruments
    Chris Cilino
    National Instruments
    LabVIEW Product Marketing Manager
    Certified LabVIEW Architect
    Attachments:
    1.gif ‏1 KB

  • Error 1073807202 occurred at Property Node (arg 1) in VISA Configure

    I am working with the 30-day evaluation version of LabVIEW
    (Version 9.0 32-bit).  I am attempting to perform the serial loopback test
    described in NI's Developer Zone Tutorial, executing Basic Serial Read and
    Write.vi.  When I click the Run arrow a dialog box appears with the
    following legend:
    "Error 1073807202 occurred at Property Node (arg 1) in VISA Configure
    Serial Port (Instr).vi>Basic Serial Read and Write.vi.  LabVIEW: VISA or
    code library could not be located.  ...required drive not installed..."
    I can find the "smplserl.vi" driver in the /examples folder on my PC.
    What's wrong?

    Did you do a search for that error? Install NI-VISA.

  • Error -107380734​3 occurred at niDCPower Initialize With Channels.v​i

    Hi all,
    While initializing NI PXI-4130 power source I got the error "Error -1073807343 occurred at niDCPower Initialize With Channels.vi".
    The routine is in a sub VI already working since two years.
    No problem accessing the supply with NI-DCPower Soft Front Panel.
    I have the problem since Thursday after installing some LabVIEW updates (don't remember which ones, just all the available).
    Is this problem known?
    Can anybody help me?
    BR
    ViP

    Dear vigna,
    I would please you to check the advices in this KB:
    http://digital.ni.com/public.nsf/allkb/8130049893D​6461E86256F3B00461E1B?OpenDocument
    When the Error still occurs please let me know.
    Kind Regards,
    Oleg Scherling, M.Eng | Applications Engineering | National Instruments | NIG |

  • Error 7 occurred at open vi reference in New Report.VI

    Hello!
    I use the report generation toolkit on LabView 7.0 to create a report in Excel. The program works fine until I make an executable version. I the get the error:
    Error 7 occurred at open vi reference in New Report.VI
    I use the New Report.VI, Bring Excel to front.VI and Save Report To File.vi
    Can you pleace help me!!!

    Most likely, you did not include the required libraries in your build script. When building an executable in which you use the Report Generation Toolkit, you must include the _Word Dynamic VIs.vi from _wordsub.llb and _Excel Dynamic VIs.vi from _exclsub.llb as dynamic VIs on the Source Files tab.
    Check this article for more info.
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/86256a47004e16d186256a84004cb883?OpenDocument
    Daniel L. Press
    PrimeTest Corp.
    www.primetest.com

  • Open DeviceNet interface error when TestStand call VIs of NI PCI-8532

    Hello,
    We use NI PCI-8532 was used as DeviceNet master to do functionality test with a slave (AC Drive).
    But when open DeviceNet interface, it happen the error.
    We can't find the solution and hope to find help from you.
    The basic sequence in TestStand is:
    1). Call "Open DeviceNet Interface.vi" to open interface and creat interface object.
         Interface(master) setting: interface name=dnet0, MAC ID=0, baudrate=125000bps
    2). Call "Open DeviceNet IO.vi" to creat DeviceNet IO object.
         Device(slave) setting: MAC ID=63
    3). Call "Operate DeviceNet Interface.vi" and operation code=start
    4). Call "Wait For State.vi"
    5). Call "Read DeviceNet IO.vi" to read data from IO object
    6). Call "Close Object.vi" to close IO object handle
    7). Call "Close Object.vi" to close interface object handle
    Remark, these DeviceNet VIs locates at "C:\Program Files\National Instruments\LabVIEW 2012\vi.lib\DeviceNet\VIAPI".
    First time to run sequece in TestStand, it can pass to run step 1) to open DeviceNet interface.
    But once there is some error with these steps, and it will happen "Open DeviceNet Interface" error (error code=0xBFF62006) when run these steps again.
    Then even use LabVIEW DeviceNet example to test, and it happen the same error except restart computer.
    The DeviceNet example locates at "C:\Program Files\National Instruments\LabVIEW 2012\examples\NI-Industrial Communications for DeviceNet\Basic Examples\PXI & PCI\MixedCommunication.vi".
    Some information more:
    PC operate system: Windows XP SP3
    LabVIEW version: 2012 SP1
    TestStand version: 2012 SP1
    PCI 8532 driver version: 2.3.0
    Other installed PCI board: PCI 8531 CANOpen

    The following errors may be resolved by resetting the CAN, DeviceNET or LIN device:
    Error -1074388986 occurred at ...
    NI-CAN:  (Hex 0xBFF62006) The object is already open in another application.  Solutions: Ensure that only one application at a time uses an object , and that you close all objects prior to exiting your application (don't use LabVIEW toolbar's Abort button).
    Error -1074388969 occurred at ...
    NI-CAN: (Hex 0xBFF62017) This attribute's value must be provided prior to the Open. Solutions: Set the attribute using the Config function before the Open, and do not set the attribute at any later time; Do not configure multiple CAN Objects for the same ID.
    SO,you should reset the DeviceNet.
    And another similar issue can explain some points of your problem  http://digital.ni.com/public.nsf/allkb/7D9383E9BEAD0B21862571640002F687?OpenDocument

  • Error 7 occurred at ABAPI Dist Report Read Link Info Error.vi - [.....] - RTBUIP_Build_Invoke.vi.ProxyCaller

    Hi all,
    I am on a field campaign with my Labview-controlled instrument. I wanted to make a small change to the code and build it again for uploading to a cFP-2020 Fieldpoint but the application builder stopped with the following error message:
    Error 7 occurred at ABAPI Dist Report Read Link Info Error.vi -> ABAPI Dist Cmp Settings to Disk Hier.vi -> ABAPI Get Settings From File2.vi -> ABAPI Get Settings From File.vi -> RTBEP_Invoke_Build_Engine.vi -> RTBUIP_Build_Invoke.vi -> RTBUIP_Build_Invoke.vi.ProxyCaller
    This is another computer than the one I used in the lab previously so might have forgotten to install something. I just copied the whole application folder with project file and subfolders
    to the Laptop I am using now. Labview version should be the same though (8.20).
    Any suggestions?
    Olaf

    Hello Olaf,
    This error is usually found when a subVI or a support file (DLL, custom control, etc)
    isn't able to be found by the application builder.  Possible reasons
    for this could include subVIs no longer located in their original
    paths and in need to be relinked, a DLL that isn't included in the build,
    and many other possibilities.
    You wrote that you copied the project from another PC, so it is very possible that some file went missing. Are all VIs in your project executable?
    You could try to mass compile all the VIs in your project and see if that helps.
    Regards,
    Johannes
    AE, NI Germany

  • Error 7 occurred at Open VI Reference with Application Builder

    Using Labview 5.1, I am building an application where all the vi's are placed in a single .LLB file. I have one top level vi (with sub-vi's), and one vi that is opened by the Open VI command. The program runs fine with labview installed. I want to make an executable file. I select the top level vi and select the vi that is opened by the Open VI command as a dynamically loaded file. I get an error when I attempt to build the file.
    "Error 7 occured at Open VI Reference in Dist Build LLB Image.vi -> Dist Build App Image.vi -> Build application.vi"

    Dear Sir;
    There are two things that are good to try:
    First, create the application in a folder that is closer to the root directory (e.g., c:\myApp). There is a limit to the length (or depth) of the path name to your application's target directory, so, if you are choosing a too long path you might get an error.
    Second: The Application Builder reads certain information from the VI in order to determine how to build the executable. To avoid possible errors, either in the build process or in the built executable, make sure the VIs are LabVIEW 5.1 VIs. You can convert your VIs to LabVIEW 5.1 VIs by using the Mass Compile feature (File >> Mass Compile) in LabVIEW before you build your executable. The Mass Compile feature will allow you to select either a directory or a LabVIEW
    .llb file to compile.
    Regards

  • Error -32810 occurred at The FieldPoint server initialization failed. Possible causes: 1. Missing or corrupt configuration file; 2. Failed to create callbacks. : FP Open.vi

    I have two cFP-2120 RT controller. They both have NI-Serial RT2.5.6, DataSocket for LV RT4.2, NI-VISA 3.6, FP Drivers 5.1.0, FP VI Manager 3.1.0 LV RT 7.1.1 installed. But one same vi can run on one controller but not another.
    the error message got when it runs on another controller is "Error -32810 occurred at  The FieldPoint server initialization failed. Possible causes: 1. Missing or corrupt configuration file; 2. Failed to create callbacks. : FP Open.vi"
    I wonder by what it is caused?
    Thanks

    Hi Matthew,
    As mentioned previously, this KnowledgeBase article may be of some help. Also, if your code is being run on an embedded controller and then a network controller (not embedded), you will need to run the program differently. On the embedded controller, you should deploy your VI in a Project Explorer or programmatically (as described here.) However, you do not need to deploy the program to a network controller, but simply run the VI.
    I would also suggest creating a new .IAK file. Do you still see the same error? Also, double-check that the software installed on the controller matches the software installed on the host PC. If you have any file paths associated with one FieldPoint controller, ensure that you are changing them to match the second controller.
    Please keep us posted on your troubleshooting steps. Have a great day!
    Amanda Howard
    Americas Services and Support Recruiting Manager
    National Instruments

  • Error 7 occurred at Get LV Class Default Value.vi only in my executable for Print Report - LV 2010 SP1

    I have a program written which uses the print report function. Everything works fine in the uncompiled code, my report prints just fine. I can compile my project all the way to a full installer. When I run the executable I get the error:
    Error 7 occurred at Get LV Class Default Value.vi
    With the following text:
    Possible reason(s):
    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 X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
    =========================
    NI-488:  Non-existent board.
    Complete call chain:
         Get LV Class Default Value.vi
         NI_report.lvclass:New Report.vi
         print report.vi
         EMS V3.0 streamline.vi
    LabVIEW attempted to load the class at this path:
    H:\InMotion\EMS\builds\EMS_01\Emissions Analyzer\EMS.exe\1abvi3w\vi.lib\Utility\NIReport.llb\Standard Report\NI_Standard Report.lvclass
    "EMS V3.0 streamline.vi" is my main vi, "print report.vi" is the subvi that creates and prints the report based on all the information sent to it. I get no warning when I compile this to an executable. I already tried repairing both LV SP1 and the report generator toolkit. No change after I compile to an exe.
    Any help would be appreciated. Thanks.
    Garrett Herning

    Ok, I tried that... and now I get an error when I try to compile to an executable... This is right at the end of the build and will not let me build an executable.
    Error:
    An error has occurred. Expand the Details section for more information.
    Details:
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    Error 7 occurred at Invoke Node in AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    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 X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
    =========================
    NI-488:  Non-existent board.
    Method Name: Linker:Write Info To File

  • Build error after upgrading from 8.2.1 to 8.5 "Error 1055 occurred at Invoke Node..."

    After upgrading to 8.5, I'm getting the following error when trying to build an EXE:
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    Error 1055 occurred at Invoke Node in AB_Source_Library.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  Object reference is invalid.
    I have been building this application for both Windows and Mac OS, and I even get the same error when building the .app on an Intel Mac.
    Things that I've already tried:
    * Mass-compiling all my code
    * Created the project from scratch
    * Enabled each panel of the "diagram disable structure" one at a time and compiled again
    Any ideas?

    Hi Travis,
    Ben’s advice if definitely the best place to start. Error 1055 is a very general LabVIEW error for “Object reference is invalid.” The cause is usually a bad install where important LabVIEW function aren’t placed in the right directory or aren’t installed at all.
    Charlie M. CLD

Maybe you are looking for