Error 6 occurred at RcvRespMsg - NI-488: I/O operation aborted.

Hi,
I am getting an error while trying to Read data bytes from a previously addressed device (RcvRespMsg) with Labview 7.1. In MAX I can write data to control my Test Receiver by GPIB USB-B. I tried to run the same software I usually work with and it was working totally fine until today. Since I didn’t change anything to the software, I wanted to know to solve that error:
Error 6 occurred at RcvRespMsg in ESVBv2.vi
Possible reason(s):
LabVIEW: Generic file I/O error.
NI-488: I/O operation aborted.
Thanks a lot for your help,
Phil

Someone in the instrument control board will be more likely to know the answer to your question, so I would recommend posting your question there.

Similar Messages

Error 200380 occurred at DAQmx perform bridge offset nulling operation

I had a working VI that could balance a wheatstone half bridge and read and record measurements. My sensors are attached to a SCXI-1314 modle in a 1520 box in channel 0 (positioned as in the manual for half bridge) with the completion resistors in the appt places in ch7. It used 'custom voltage with excitation'.
Wanted to improve this VI so that it would also do a shunt calibration. I therefore connected the shunt resistor in the board over my active sensor as in the manual. I tried then to create a virtual channel for it - but it wouldn't work. So I gave up on that idea and tried to put things back how they were - deleted the virtual channel, and removed the connections to the shunt resistor. Except now none of my previously working VIs will work. I have built a new VI, and that can find a signal but not balance the bridge. I get:
error 200380 occurred at DAQmx perform bridge offset nulling operation.
I have checked the hardware again, and it's all wired correctly - it seems like the VI can see the channel but doesn't know what to do with it. Have running the VIs with and without a custom voltage with excitation channel created but nothing works.
Help!

Hi LucyWH
Have you tried re identifying the chassis in Measurement and
automation explorer?
Have you changed the jumpers at all as when rewiring this is easily
overlooked?
I have found some links that you may find useful:
Error -200380 When
Calibrating SCXI-1520 in NI-DAQmx
http://digital.ni.com/public.nsf/allkb/6E94108C9611910186256D43007C2584?OpenDocument
Common NI-DAQmx Error
Codes and Solutions: Codes -200300 to -200999
http://digital.ni.com/public.nsf/allkb/8A0E097385A4269586256DBA0054E668?OpenDocument
Regards
Robert
National Instruments UK & Ireland

Error 6 occurred at Open/Create/Replace File in NI_Excel.lvclass:Save Report to

I have an application that works on LV60 and when run in LV86 I get the following error:
Error 6 occurred at Open/Create/Replace File in NI_Excel.lvclassave Report to File.vi->SWF001 Test.vi
Possible reason(s):
LabVIEW: Generic file I/O error.
=========================
NI-488: I/O operation aborted.
C:\SWF001 IO Files\1_Single.xls
The application does:
New Report.vi
Excel Get Worksheet.vi
Excel Easy Table.vi
Excel Easy Text.vi (4 of them)
Save Report to File.vi
Dispose Report.vi
all in a nice chain (errors and report-in/outs) as is typical
For some reason I'm getting this error. I'm using it with Excel 2003 SP3 and the spreadsheet contains macros (and I get a prompt "should I enable macros:" (I answer yes), that I didn't get with LV60 and the older version of Excel). This is probably not the problem? but deserves mention.
The file does exist on the system (and it appears the application is writing to it successfully - though perhaps truncated as the error indicates- i can't tell for sure).
I can open and save the Excel file independently of LV just fine.
Any clues?
Many thanks! -David
Solved!
Go to Solution.

Unfortunately, an Error 6 is a catch all category for all sorts of file IO errors that LV doesn't know how to handle. For example, while it doesn't sound like your problem, trying to access a file that resides on a network drive that isn't currently mounted can generate an Error 6.
Have you tried saving the file to a different location?
If you restart your computer and run the VI does it generate the error the very first time you run it?
Can you post your code - or at least a subset of it that demonstrates the problem?
Is Excel open when you are running the code?
Also, as a test try modifying your code so it has a unique name every time you save it.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Error 6 occurred at TDMS Open in TDMS

Hi,
I have a application that is using the TDMS VI's to generate a Logfile.
The application ran correctly for 12 days. (Each errors, and some parameters - every hours - was correctly written to my TDMS file).
Then, the following error occured :
Error 6 occurred at TDMS Open in TDMS - Write data SubVI V1.2.vi->D2XX MultiTester V1.5.vi
Possible reason(s):
LabVIEW: Generic file I/O error.
=========================
NI-488: I/O operation aborted.
I join my VI that manage the TDMS file.
The error seems to come from the VI "TDMS OPEN". The corresponding TDMS file is effectively at the specified path, and its content is OK (all expected infos are present). The file is called LogFile_0_1.TDMS.
Depending on the TDMS file size, the application automatically creates a new file. I tried to force that to get a new TDMS file (assuming that the active file was corrupted or blocked). A new TDMS file was created (LogFile_0_2.TDMS.) but only the first tab (root) was created. Then the same "Error 6 " was still present, exactly like before.
Do you think this problem can come from Windows?
Or does it come from my application? What is not optimal, is that this "TDMS - Write data SubVI V1.2.vi" is called about every second, and the "TDMS OPEN" function is called unconditionally (even if no modification on the TDMS file are needed).
How can we explain that this bug appears after about 12 days only?
I also join you the LogFile_0_1.TDMS that I converted to an Excel file, and the LogFile_0_2.TDMS that was not correctly created.
Thank you in advance for your support.
Michael
Solved!
Go to Solution.
Attachments:
LogFile_0_1.xlsx ‏560 KB

MarcoMauri wrote:
My guess is that you forgot to close the TDMS file and each time your VI is called a reference is created.
It could be that after a week the maximum possible number of references was reached, and you got the error.
Regards,
Marco
Marco,
That's not just a guess, that is a very real possibility. And lets not forget the memory leaks from not closing references.
ALWAYS close ANY references you create. If you open a reference to a file, make sure you close it.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Error 6 occurred at invoke node in dist build app

Error 6 occurred at Invoke Node in Dist Build App from LLB.vi->Dist Build App Image.vi->Build Application.vi
Possible reasons:
LabView: Generic file I/O error
or
NI-488: I/O operation aborted
Version 6.0.2

I noticed that you updated your system to 6.0.2. A couple things to check on that may remedy the problem.
1)Did you install the application builder after upgrading your system to 6.0.2? You will want to install the application builder 6.0 first, and then add the 6.0.2 update to the whole system.
2)Have you mass compiled all of your VIs since the upgrade? You will want to make sure that all of your VIs are in 6.0.2 format before trying to build them into an executable.
Matt Kisler
Applications Engineer
National Instruments

Error 6 occurred at AB_Source_VI.lvclass:Close_Reference.vi -

So I got this error code when trying to create an exe. file....any help
Error 6 occurred at AB_Source_VI.lvclass:Close_Reference.vi -> 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_Build.lvclass:Build_from_Wizard.vi -> AB_UI_Frmwk_Build.lvclass:Build.vi -> AB_UI_FRAMEWORK.vi -> AB_Create_Build_Application.vi -> EBUIP_Global_OnCommand.vi -> EBUIP_Global_OnCommand.vi.ProxyCaller
Possible reason(s):
LabVIEW: Generic file I/O error.
=========================
NI-488: I/O operation aborted.

Did you try a search?

Error 6 occurred during build of compact FieldPoint executable

I am building my executable for the compact FieldPoint and I received the following build error:
[ERROR]
Code:6
An error occurred while saving the following file:
C:\Program Files\National Instruments\LabVIEW 2009\vi.lib\Utility\SMTP\smtpeml.llb\SMTP Email Get Case Insensitive Search Pattern.vi
Invoke Node in AB_Source_VI.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_RTEXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_RTEXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
<APPEND>
Method Name: <b>Save:Target Instrument</b>
<Call Chain>Error 6 occurred at AB_Source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_RTEXE.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Application.lvclass:Build.vi -> AB_RTEXE.lvclass:Build.vi -> AB_Build.lvclass:Build_from_Wizard.vi -> AB_UI_Frmwk_Build.lvclass:Build.vi -> AB_UI_FRAMEWORK.vi -> AB_Item_OnDoProperties.vi -> AB_Item_OnDoProperties.vi.ProxyCaller
Possible reason(s):
LabVIEW: Generic file I/O error.
=========================
NI-488: I/O operation aborted.
Any ideas what caused this or how to fix it?

Hi Carol
I encountered an error similar to this when i was working with CD and SIM, I solved the problem by building the executable from the C: drive concluding that the file reference was too long.
http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx
Be sure to also disconnect all type definitions in Application Builder.
Message Edited by Eric_R on 10-12-2009 03:22 PM
Thank You
Eric Reid
National Instruments
Motion R&D

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

Opening Build Specification - Error 7 occurred at Get LV Class Default Value.vi

I recently ported my project to a new PC. Everything seems to run fine uncompiled, and I am able to build an executable without issue. However, my build specification shows up in the project explorer with question mark next to it. When I try to build again or edit the properties I get a popup with the information below:
Error 7 occurred at Get LV Class Default Value.vi
Possible reason(s):
LabVIEW: File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.
=========================
NI-488: Nonexistent GPIB interface.
Complete call chain:
Get LV Class Default Value.vi
AB_UI_Initialize_Framework.vi
AB_UI_FRAMEWORK.vi
AB_Item_OnDoProperties.vi
AB_Item_OnDoProperties.vi.ProxyCaller
LabVIEW attempted to load the class at this path:
<Empty Path>
I've seen messages from people getting the same error when trying to run a compiled executable, but mine actually runs fine. I am just unable to open the build specification to rebuild or edit its properties.

This application is for a Windows machine, and I am not using the Report Generation Toolkit. However, I shut down my computer last night and when I booted it up this morning my Build Specification now opens fine and I am able to edit it. My only thought as to why it occured in the first place is that I had added several files to user.lib and instr.lib and restarted LabVIEW, but it appears that it required my computer to be restarted as well.

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

Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi- AB_Engine_Build.vi- AB_Build_Invoke.vi- AB_Build_Invoke.vi.ProxyCaller

Hi there,
Hope someone can help me. I recently upgraded to LV 8.5 and am having a problem building a .exe which has a subvi in it that opens in a new dialog window. When I try to build this I get the following error:
Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: File permission error. You do not have the correct permissions for the file.
=========================
NI-488: DMA hardware error detected.
Method Name: Build:Application
I have built the .exe with the same subVi but without opening it in a dialog window and it works fine., so the problem seems to be linked to the inclusion of the dialog window.
Any advice greatly appreciated
Regards
Tadhg

UPDATe: I can get the .exe to build but now I get an error when I run teh .exe which is shown in the picture attached.
Attachments:
error screen1.JPG ‏122 KB

Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi- AB_Build.lvclass:Bui

During software build to make exe file, I got the following error message:
Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
Possible reason(s):
LabVIEW: File permission error. You do not have the correct permissions for the file.
=========================
NI-488: DMA hardware error detected.
Method Name: Build:Application
The vi was working fine before the build. It just access some text files and creates some excel files. No hardware is involved. See if anybody know how to solve this problem. Thanks.

I am using LabVIEW 2014 and have been getting this error randomly, but fairly consistently on a recent build. I searched all over and could not find a solution that worked. However, just through trial and error I discovered that the problem is related to SSE2 Optimization in the Advanced properties window. I can consistently cause this error by enabling this feature and consistently compile successfully when it is disabled. Try turning this feature off and see if it solves the problem.
...UPDATE: After closing and re-opening LabVIEW this error came back, and did not seem to be affected by the SSE2 option. Not that it isn't related, but perhaps not the silver bullet I thought it was.
I also got the error to go away sometimes when I compiled the EXE while the main program VI was open, whereas it gave the error most of the time when no VIs were open...again, nothing seems to consistently solve the problem...there is definitely some kind of bug in the appllication builder, and it seems like there are a lot of people that have been struggling with this for a long time (as far back as LV 8)...hopefully NI eventually finds this bug and squashes it!..although, I doubt that anybody at NI is even looking for it...

Error 7 occurred at Invoke Node in AB_EXE.lvclass

I get the "Error 7 occurred at Invoke Node in AB_EXE.lvclass" error when trying to build an executable in Labview 8.5.1. I can run the application without any errors but when I try to build the executable, I get the error. I have tried a mass compile of the project, tried ctrl + shift + run on the top level vi, and tried to mass compile the folder where the project is located and nothing seems to help. I have also looked at the project dependencies for conflicts and found none. I have made a new project and tried to build an executable from this same code without any luck. How can I get this to build an executable?
The exact error is:
Error 7 occurred at Invoke Node in 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, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Nonexistent GPIB interface.
Method Name: Build:Application

Are you using the Report Generation Toolkit? A lot of error 7's during builds seem to be related to this toolkit. Any dynamically called VI's?
Take a look here and here.
Also search the forums for "error 7" and you'll find some other threads related to error 7 and the application builder.

Labview 9.0: Error 1 occurred at Write To Measurement File

Hi
Our University recently got the latest version of Labview (9.0 32-bit) which I installed today.The labview file I am using (my6008v6.vi) used to work fine with the older version (8.5 i think). My write-to-file VI is enabled at certain time intervals in order to log data. As soon as it is enabled for the second time I get the following error:
Error 1 occurred at Write To Measurement File->Copy of murray6008v6.vi
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
I made a simple file (simplew2f.vi) to test this, with a button which I can press to enable/disable the writing of data. I am able to start writing data and then stop writing data but as soon as I try resume the writing the same error occurs.
This confuses me greatly since this wasn't a problem using the old version and my Labview knowledge is minimal. Any help would be appreciated.
Attachments:
my6008v6.vi ‏214 KB
simplew2f.vi ‏64 KB

So, which VI are you having problems with? Sounds like both...
Okay... - sigh - where to start....
Well.. Let's start with a few comments.
1. Try to stay away from the Express VI. I know the Marketing guys at NI will not like me for saying so, but I am saying so. They are a nice marketing feature that Grumpy Old Men like myself do not like. They make it easy to write quick code.. And I will limit my comments to that. (It's not your fault.. )
2. The wiring on your diagram is not clear or easy to read. Yes, with additional time and double-clicking each wire I can tell where they are going. However, a rule of thumb, alway wire from Left to Right. Never right to left. And do not run the wires under objects, even the ones you are wiring to.
3. simplew2f.vi: You should put a small delay in the While Loop. I ran it three times and it wrote to the files without error. And yes, I used LV2009.
4. my6008v6.vi: Avoid wiring from the top of the While Loop. At frist, it looked like the data was coming out of the While Loop because the wires went to the left side of all the index node of the Index Array function.
You should set your Browse Option for the file path to "Files or Folders" and "New or existing". I did that and I was not getting the error message you described.
R
Message Edited by Ray.R on 03-03-2010 08:33 AM
Attachments:
pathProperty.PNG ‏13 KB

Error 6 occurred at RcvRespMsg - NI-488: I/O operation aborted.

Similar Messages

Maybe you are looking for