Error -1074388957 occurred at Open DeviceNet Interface.vi

I keep getting the following error message
Error -1074388957 occurred at Open DeviceNet Interface.vi
Possible reason(s):
NI-CAN: (Hex 0xBFF62023) The Interface is invalid or unknown. Solution: Verify that the interface is assigned to a specific port within the Devices and Interfaces branch of the Measurement and Automation Explorer (MAX).
=========================
NI-Industrial Communications for DeviceNet: (Hex 0xBFF62023) The Interface is invalid or unknown. Solution: Verify that the interface is assigned to a specific port within the Devices and Interfaces branch of the Measurement and Automation Explorer (MAX).
Here is my system Info:
Windows 7 Pro 64
LabVIEW 2010 32 bit
PCI-CAN card
Drivers Installed: NI Device Net 1.6.7, NI-IndCom for Devicenet 2.2, NI-CAN 2.7.5
Thanks for any help!

I noticed that there are two sets of devicenet VI libraries in my LabVIEW 2010 vi.lib directory that have the same name. The supposedly correct one that LabVIEW automatically places on the block diagram from the palette is from the "DeviceNet" folder. This one gives the error described earlier when I run it. There is another one in the "Nidnet" folder with the same name and this one works and does not give an error. TheNidnet one appears older since it has the older looking front panel objects.
Does not work (error hex BFF62023):
C:\Program Files (x86)\National Instruments\LabVIEW 2010\vi.lib\DeviceNet\VIAPI\Open DeviceNet Interface.vi
Works:
C:\Program Files (x86)\National Instruments\LabVIEW 2010\vi.lib\Nidnet\Nidnet.llb\Open DeviceNet Interface.vi
It is correct to use the nidnet folder with LabVIEW 2010 and newer or should I be using the DeviceNet folder version. If the nidnet version is the correct one, is there a way to make it so these appear on the palette when I go to add them to the block diagram?
Any thoughts?

Similar Messages

Error -1074388957 occurred at Open DeviceNet Interface.vi

NI-CAN: (Hex 0xBFF62023) The Interface is invalid or unknown.
The interface is assigned to a specific port within the device and detected in MAX

The 8532 board needs a different driver. The Ni-DNET 1.6.6 driver is for our legacy hardware line. You need the NI-IndCom for Devoicenet 2.0.2 driver from here. However it currently doesn't have a API as you know it from 1.6.6.
So it would be better if you try the 2.1 Beta from here. We will release soon so the Beta driver should be in good shape.
DirkW

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

Error 42 occurred at Open Application Reference in DynamicDownload.vi

Hi！
I want to create an executable from a VI wich calls a dll created by Simulink and Simulation Interface Toolkit.
After I compile the simulink module with MSVC++ 6.0 in MATLAB,and then use this dll in LabVIEW,
the following message appears:
Error 42 occurred at Open Application Reference in DynamicDownload.vi->SIT_InitEstablishTCPConnection.vi->SIT Initialize.vi->Untitled.vi
Returning to Select Host dialog.
Possible reason(s):
LabVIEW: Generic error.
What should I do to have an executable which works correctly?

I have the same Problem here with the Error 42 on open application reference.
Can someone pleas explain what this error means, and what the reasons are for this error?
I have two exe files, and i am trying to open the application reference of the other exe when i get this error.
First i thought it has something to do with the .ini file settings, which by the way is nowhere explained...
here my entries:
server.tcp.acl="290000000A000000010000001D00000003000000010000002A10000000030000000000010000000000"
server.tcp.enabled=TRUE
server.tcp.port=3360
server.tcp.serviceName=Image Monitoring
server.tcp.access=+*,"+*","127.0.0.1","Localhost"
server.vi.access=+*
server.vi.callsEnabled=TRUE
server.vi.propertiesEnabled=TRUE
server.ole.enabled=TRUE
server.tcp.paranoid=TRUE
server.tcp.servic=My Computer/VI Server
tcpServer.log=TRUE
tcpServer.logPath=c:\TestStand\Tools\Image Monitoring PC\serverlog.txt
server.app.propertiesEnabled=TRUE
if i build a simple exe with call on open applicationr eference it works. but not with my main application,
so this is why i need to know what causes the Generic Error???
Is there a possibility that there have to be certain entries in the ini file of the calling exe? and what would those entries be?????????

Stand alone application(.exe) : Error 7 occurred at Open File+.vi: Open File (error: L'erreur 7 s'est produite à : Open File+.vi:Open File)

Dear group members - as i am trying to build a stand alone application , i ran into this problem : "Error 7 occurred at Open File+.vi: Open File" (L'erreur 7 s'est produite à : Open File+.vipen File)
when i select continue i get this error message: "Error 7 occurred at open/create/replace file in Write spreadsheet string.vi->Write To Spreadsheet File (I64).vi->Mono Com Write ini.vi->mainVI2.vi"" ( "L'erreur 7 s'est produite à : Ouvrir/Créer/Remplacer un fichier dans Write Spreadsheet String.vi->Write To Spreadsheet File (I64).vi->Mono Com Write ini.vi->mainVI2.vi" )
i didn't get what's the problem with this vi, i have no problem running my VIs
Can any one here help me out ?
here is the project :

Neither can I. When I opened your Project, there were no VIs present on the top level. The Build Spec refers to a Mainv12, which I finally found buried in the folder Interface 2, but when I tried to open it, there were multiple missing VIs. I notice you have an Interface 2.llb -- is this the same as the VIs in the Interface 2 folder? If so, try getting rid of the .llb (at least for the purpose of sharing your code in the Forum) and re-post your code. As it stands, when I open your Project, virtually every entry is marked "Warning: has been deleted, etc." The fact that so much is "missing" means that I can't easily see/understand MainV12, hence can't guess where the File Not Found error is arising. Sorry.
Bob Schor

Suppressing error 8 occurred at open file dialog box

Hello,
I am getting randomly occurring "error 8 occurred at open file" dialog
boxes every couple of days. This is stopping all of the data collection
on all of the vi's on the pc. In order to continue all that is needed
to hit continue. Is there a way to suppress this dialog box?

There's a vi called Clear Error, in the Dialog and User Interface section of the palette. If you wire the error out of the offending vi to the error in of the clear error, your problem should be solved.
Technically I think you can wire the error out to just about anything that ends (as in, to the side of a case structure or loop or something, so long as nothing is connected to it further). I think as long as LV thinks that you've handled the error (i.e. wired anything out of the error out), the dialog box does not come up.
Message Edited by Novatron on 07-07-2006 11:02 AM
Attachments:
No Error.jpg ‏5 KB

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

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 7 occurred at open/create/replace file

Hello,
I have searched the forum and could not find any useful information regarding my problem, so hope you may shed some light. MyVI can create a new csv (text) file by using the time to name the file, so every time the new file will be created with a different name and file path is not a relative path. I can run the VI in both development environment and stand along executable without any problem. But,
One of my colleagues cannot run the executable exe on her machine because Error 7 occurred at Open/Create/Replace File in xxxx.vi Possible reason: 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.
My question is why only she cannot run this exe on her machine. I have checked a few different PC in my office and all of them can run this exe without problem, so I am pretty sure the code is fine.
I have already ask her to do,
Run the executable as administrator
Save the new file to other drives (not C: drive)
but she still cannot run the executable. I dont think this is a premission issue, otherwise, LabVIEW would give a different error, Error 8 I believe.
Both her PC and my PC is running Windows 7 professional 64-bit. The only difference I can see is that she is based in US and I am based Australia. Does anyone have any idea? Please help.
Thanks,
Sherman

I’m not sure but expecting like below,
As you said, your creating file name with Time. Make sure file name is correct and there is no special characters (like, / or : ). If your formatting time to string with “Format Date/Time String.vi” (while creating file name), based on UTC format, string will change.
UTC format specifies if the output string is in Universal Time or in the configured time zone for the computer. If TRUE, date/time string is in Universal Time. The default is FALSE.
Make sure you have access rights to create files into mentioned folder. Try to create new file manually.
Munna

Error 1003 occurred at Open VI Reference in Dist Copy Non-VI Files.vi- Dist Build LLB Image.vi- Dist Build App Image.vi- Build Application.vi

When trying to build an application using labview 7.1 and windows XP, I get the error
Error 1003 occurred at Open VI Reference in Dist Copy Non-VI Files.vi->Dist Build LLB Image.vi->Dist Build App Image.vi->Build Application.vi
I've tried the crtl-shift-run as well as a mass compile and I still get the error.
Any ideas?
Thanks,
Mike

Hopefully this thread, or this KB article might help.
It seems like this could come from a lot of things, but there's suggestions in those which might lead you in the right direction
Message Edited by Day on 09-22-2006 02:07 PM

高手快帮忙谢谢labview7打包后用到7中新的new report.vi的地方(选择的是word)都提示error 7 occurred at open vi reference in new report.vi

高手快帮忙谢谢
labview7打包后用到7中新的new report.vi的地方（选择的是word）都提示error 7 occurred at open vi reference in new report.vi。
下面提示的可能原因是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 UNIX.
我愿自己是个胡萝卜，可以自己自足啦!

我明白您的意思，也可以按您所说的作，
但是open vi peference这个vi是labview提供的标准new report.vi的子vi中使用到的，如果我手动修改open vi peference中的提供的word路径，也就是说labview提供的模块也要自己修改了??
我愿自己是个胡萝卜，可以自己自足啦!

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 occured at open file+.vi:open file

Hi
Iam using lab view 7.1 licensed version.But when i create a stand alone application and install it in a 4gb touchpanel(ADVANTECH TPC 660G B1-E).iTS WORKING PERFECTLY FOR SOME TIME.But after some time i get an error (error 6 occured at open file+.vipen file).Iam attaching the snapshot
plz help me out
ekanth
Attachments:
untitled.JPG ‏55 KB

This indicates a problem with your code. Since you haven't shown us any code we can' tell you what the problem is. Are you trying to open a file that's open by another application? Are you trying to open a file that's on a network, and the network is temporarily unavailable? You should know what file it's trying to open - after all, you wrote the app, right?

Error 1430 occurred at Open/Create/Replace File in NI_Fuzzy_Logic_API.lvlib:FL Load Fuzzy System.vi- Untitled 3 Possible reason(s): LabVIEW: The path is empty or relative. You must use an absolute path. Not A Path how can i copy it in new vi plz help

when i am copy the vi that is in find example>fuzzy>fuzzyEx with pi control the follwing error occuring
'error 1430 occured at open/create/replacefile in NI Fuzzy logic API.LVLIB FL LOAD FUZZY SYTEM.vi
untitel 3 possible reason the pat is empty or relative you must se use an absolute patth <not apath>
plz help me i only want that i can copy this vi in new vi but when i do so the above error occur and fuzzy logic cotroller is highlited

Hello Nofil,
This is probably happening because you have made a copy of the VI without changing the name/ location on the disc. I have saved a copy of the VI for you, it is in LabVIEW 2010 SP1, please ask if you want this in a previous version.
Regards
Andrew George @ NI UK
Attachments:
Fuzzy Tanks with PI.vi ‏31 KB

Error -107438895​7 occurred at Open DeviceNet Interface.​vi

Similar Messages

Maybe you are looking for

Error -1074388957 occurred at Open DeviceNet Interface.vi