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

Similar Messages

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?

LabVIEW PDA reports COREDLL.DLL error when using Call Library Function Node

I'm trying to build a LV PDA app that calls an external DLL file built using embedded visual C. When configuring the Call Library Function node I select the stub DLL, configure the I/O parameters and select OK. When the configuration dialog closes I get the following error:
LabVIEW: LabVIEW.exe - Unable to Locate Component
This application has failed to start because COREDLL.DLL was not found. Re-installing the application may fix this problem.
I do not get this error when using the configuration dialog in the example VIs.
Any suggestions as to the cause and/or the solution?
Thanks,
Ryan

Hello -
When you create a PDA VI that calls a DLL, you must include the .c or .lib file that corresponds to the DLL. Take a look at these documents:
LabVIEW PDA Module Build Errors with VIs that Call DLLs
Why Do I Receive Errors When Calling a C++ DLL from a Call Library Node Using the LabVIEW PDA Module...
How To Call External Code in LabVIEW PDA for Palm OS
H
ow To Call External Code in LabVIEW PDA for Pocket PC
Hope this helps!
S Vences
Applications Engineer
National Instruments

Getting an error when closing a VISA session

I have a VI that uses VISA to talk to an instrument through aLAN/GPIB gateway. It works fine when talking to my laser. When I try to communicate with my OSA, all of the commands work, and I get the data, but I get an error message from the VISA Close. The OSA is an older unit, but I thought that the VISA stuff was all internal to the PC and OS. Any help or insight would be appreciated.
Jim
Jim
LV 2013
Solved!
Go to Solution.

Sorry for the missing info.
Error code: –1073807338
Which in NI help is indicated as: VI_ERROR_CLOSING_FAILED - The VISA driver failed to properly close the session or object reference. This might be due to an error freeing internal or OS resources, a failed network connection, or a lower level driver or OS error.
Watching the VI execute in highlighted mode, there are no errors out of any of the VISA writes or reads before the Close.
Jim
Jim
LV 2013

Error when posting - Call up of feature PPMOD was not successful

Good Afternoon,
We recently completed an upgrade to ECC6.0 and this week we have seen two cases of receiving an error when trying to post payroll to FI using RPCIPE00.
The error we are receiving is: Call up of feature PPMOD was not successful, Message no. 3G100
The diagnosis on the error message is: Feature PPMOD has been called to set the employee grouping for account determination. This call was unsuccessful and suggests that we check the decision tree for PPMOD.
While there have been some somewhat recent changes to PPMOD, I have stepped through the feature for both individuals who had this error and can find no problem with the logic in the decision tree. I've also regenerated the feature successfully. After searching OSS I found note 1243065, which is the exact error that we are receiving. The problem is that this note was included in HR support pack 44, and we're already on HR support pack 48. We also found a post that suggested we use RPCIPE00_OLD, but gave us the same error.
My next step was to post a customer message, but thought it would be worthwile to post something here and see if anyone has any suggestions first.
Thanks in advance,
-Nick
Edited by: Nicholas Petters on Apr 15, 2010 5:32 PM

The issue may not be related to the note you indicated as this note should already be included in your system with SP 48. Please check what personnnel areas the errors ees are in, and see if they're in the decision tree of 'PPMOD' .
If this looks OK, run payroll simulation for the error ee, put break-point in form 'CALL_549B' of program '/1PAPA/FEAT310PPMOD' and see what value STRUC-WERKS (pers. area) is when it fails.

Why I get an error when I call Snipping Tool with System Exec?

Hi to everyone, I want to call Snipping Tool from LabVIEW using the System Exec VI, but I always get an error 2; this not happen when I call another executables like calculator or paint; I hope someone can help me or tell me why this error occurs.
Thanks in advance, I have attached a couple of images of the VI that I have done so far.
Solved!
Go to Solution.
Attachments:
block diagram.PNG ‏11 KB

Hey there ;
I am guessing you are using the command: SnippingTool or SnippingTool.exe, just as you would use mspaint; but it is giving you Error 2; this is a Windows Issue more than a LabVIEW one, ,you can try using command:
C:\Windows\Sysnative\snippingtool.exe;
it worked for me; i found this info in the KB below.
Command Not Recognized When Using System Exec VI
Good luck

OAF pages open up with error when FND_VALIDATION_LEVEL profile set to ERROR

Hi,
We get error “You have insufficient privileges for the current operation. Please contact your System Administrator.” when we access the OAF page on a click of a link .
On a click of a link in a OAF page a new OAF page should open up. This is achieved by following piece of code
String javaS = (new StringBuilder()).append("javascript:openWindow(top, 'OA.jsp?page=/XXX/oracle/apps/cs/XXX/XXX/webui/ViewRulesPG&paramRoot=RULES&reportname=").append(strViewRepName).append("&retainAM=N&addBreadCrumb=N','modal'").append(",{width:screen.width,height:screen.height-30,top:0,left:0").append(",resizable:false},true, 'document', null);void(0);").toString();
bodyBean.setOnLoad(javaS);
This works fine when the FND_VALIDATION_LEVEL is set as 'None' but gives the error when the profile is set as 'Error'. We can't go with this work around.
Please suggest
Regards,
Mrugesh

FND_VALIDATION_LEVEL is a profile option that should always be set to ERROR. It is not advisable to set it to NONE, just to enable your javascript. The profile ensures that the page is well secured when accessed through Oracle Applications, applies the necessary security similar to seeded OAF pages. OA Framework does not support javascript functionality such pop-ups (you can do it but ) but does not guarantee that the page is secure from outside world (web traffic or cross-browser attacks) when the FND_VALIDATION_LEVEL=None. Work with Dialog pages instead of pop-ups or otherwise limit the page functionality, as javascripting is not recommended in OAF pages.
-Vikram

I get an error when installing Call To Call

I always get this error when installing the Skype Call To Call toolbar:
"The installer has encountered an unexpected error installing this package,this may indicate a problem with this package.The Error code is 2738"
Help anyone?

Just in case, even though it's for a different error message, try the procedure from the following user tip:
"The administrator has set policies to prevent this installation" error messages when installing iTunes for Windows on Windows Vista and Windows 7 systems

Maximum Open cursor Exceeded error when deleting records from a table

I have a strange problem.
I have a table EMP_MASTER . Whenever I am trying to delete a record from this table, I am getting Maximum no. of open cursor exceeded error. But this error doesnot come when i delete from any other tables. And no. of open cursor is much lesser than OPEN_CURSOR parameter.
All other tables (around 700) has foreign key constraint to this EMP_MASTER table for created_user paramater.
Is it some thing like, when I am trying to delete a record from EMP_master, implicit cursor opens up and checks all referenced tables. and that limit gets exceeded ?
Please help.
Thanks,
Raj

Raji03 wrote:
There is no trigger defined for this table.
Is there a limit on which no.of references made to a column ? Because one column in this field, Emp no is being referenced in almost every other table. around 700 tables. Will it have any adverse effect ?That should have nothing to do with your problem directly. Again, those tables could have triggers defined on them and you are leaking cursors in one of those triggers (wild guess).
An example of a table with many many others foreign key'd to it.
create table parent_of_everything
   column1 number primary key
insert into parent_of_everything select level from dual connect by level <= 1000;
commit;
--create 1000 tables all with foreign keys to the parent_of_everything
begin
   for i in 1 .. 1000
   loop
      execute immediate 'create table child_' || i || ' (column1 number, column2 number, constraint child_' || i || '_fk foreign key (column1) references parent_of_everything (column1) on delete cascade)';
      execute immediate 'insert into child_' || i || ' select level, mod(level, ' || i || ') from dual connect by level <= 1000';
      commit;
   end loop;
end;
TUBBY_TUBBZ?delete parent_of_everything;
1000 rows deleted.
Elapsed: 00:02:53.03No problems were had (none were expected).
Cleanup script.
--remove the 1000 child tables
begin
   for i in 1 .. 1000
   loop
      begin
         execute immediate 'drop table child_' || i || ' purge';
      exception when others
         then
            null;
      end;
   end loop;
end;
/

Nvidia Open GL driver error when Photoshop CC is open

New PC, bought predominantly for Photoshop use. Downloaded trial of Photoshop CC and it keeps closing with this message -
"Nvidia Open GL Driver detected a problem with the display driver and is unable to continue. Tha application must close. Error Code 3"
This has happened with Photoshop just being open, as well as when in use.
If I untick "use graphics processor", I have no problems. My use of Photoshop is fairly basic (processing and editing photographs from a Nikon D7100), so I don't know what I will miss if I don't use the graphics processor.
Intel i7-3770 Quad Core (3.4ghz 8mb cache)
16gb DDR3 1866 mhz
2GB Nvidia GeForce GTX660 graphics card
Windows 7 professional 64 bit
I have updated the graphics card driver, which made no difference. Can anyone help with suggestions of why I'm getting the error, and what I can do about it please?
Thank you
Chris

Had to re-install windows and all drivers for other reasons, and having downloaded Photoshop CC again, I no longer have the problem.
Chris

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

"Unable to open config file" Error when starting tomcat

hi all,
Here is the output from two of the log files when I start tomcat4 on my linux box. I have configured the mod_jk on the tomcat side.
From the output of the second log file, it seems that the ajp13 worker I defined was started successfully. What I don't understand is the following:
1) In catalina.out, where des the line 'Unable to open config file' come from? Which config file?
2) Tomcat4 is supposed to generate a mod_jk.conf automatically, but I don't see any file generated in 'conf/auto/'.
Content of 'catalina.out'
Unable to open config file
Starting service Tomcat-Standalone
Apache Tomcat/4.0.4
Unable to open config file
Starting service Tomcat-Apache
Apache Tomcat/4.0.4content of 'catalina_log.2002-08-16.txt'
2002-08-16 01:05:22 HttpConnector Opening server socket on all host IP addresses
2002-08-16 01:05:28 Ajp13Connector[8009] Opening server socket on all host IP addresses
2002-08-16 01:05:28 Ajp13Connector[8009] Starting background thread
2002-08-16 01:05:29 Ajp13Processor[8009][0] Starting background thread
2002-08-16 01:05:29 Ajp13Processor[8009][1] Starting background thread
2002-08-16 01:05:29 Ajp13Processor[8009][2] Starting background thread
2002-08-16 01:05:29 Ajp13Processor[8009][3] Starting background thread
2002-08-16 01:05:29 Ajp13Processor[8009][4] Starting background thread

I have all those files too.
I think the 'config file' mentioned in the error log is the mod_jk.conf.
On Jason Hunter's tomcat4 guide, it says don't use the tomcat4 RPM to installed. What is the difference bettween the RPM version and the tar.gz version? The only difference I can think of is that in the RPM version, the conf directory is in the 'etc/tomcat4/conf'. Could it be the reason that tomcat4 cannot read the config file? But it has no problem reading the server.xml though.

Open wallet failed error when running DBCA

Hi,
running 9i on AIX 5.3
By starting dbca, get the Error Message 'Open wallet failed'
The dbca GUI comes up and runs fine.
Anyway in case anyone has the problem please let me know...
The wallet entry is in the sqlnet.ora
WALLET_LOCATION =
(SOURCE =
(METHOD = FILE)
(METHOD_DATA =
(DIRECTORY =/ora01/admin/DB_01/wallet)
Thanks in advance

See Note:369562.1 ERROR: Open Wallet Failed when starting NETMANAGER/NET CONFIGURATION, it states that the message can be ignored (the Note mentions DBCA too).
HTH
Enrique

Open VI Reference Error when Using a LV Created EXE as ActiveX Server

Making a long story short, I'm trying to create an executable in Labview that I can call from another Labview program via active x. I've been using the following article as my guide:
https://decibel.ni.com/content/docs/DOC-9647
It seems simple but I keep getting error 6945 saying that the VI name is no longer suffiencient. I've checked and rechecked the VI name that feeds VI path and I know it is correct. All I'm really trying to do is grab the VI reference so I can hide the front panel. Attached is a screenshot of the code and the error. Any thoughts?
Solved!
Go to Solution.
Attachments:
Screen Shot 2012-07-03 at 4.18.05 PM.png ‏44 KB
Screen Shot 2012-07-03 at 4.18.35 PM.png ‏22 KB

Thanks, dbell
This is such an awaited improvement and I am shocked that I did not know about it until now. I want to move to LV 2009 or later so that I do not have to expose bunch of VIs outside of executables. In LV8.6 if you use inheritance of LV Classes then conflicting name was inevitable as overriden VIs always have the same name as the parent method VIs (prefix does not fix it).
And I guess we need to add some comments on this page from PO >> https://decibel.ni.com/content/docs/DOC-9647
TailOfGon
Certified LabVIEW Architect 2013

ORA-00922 error when user calls sys.verify_function from forms

Hi there,
I have a form to change the user's current password.
After user provides new password and clicks on OK button, it calls a database procedure called "change_pwd" which calls the Alter command.
I modified the SYS.verify_function, which has the code
-- rule Passwords can only contain A-Z, 0-9, _
   violate_rule_five := FALSE;
   FOR v_char IN 1 .. lv_pwd_len
   LOOP
      v_this_char := UPPER (SUBSTR (PASSWORD, v_char, 1));
      IF (   ((v_this_char >= 'A') AND (v_this_char <= 'Z'))
          OR ((v_this_char >= '0') AND (v_this_char <= '9'))
          OR (v_this_char = '_')
      THEN
         violate_rule_five := FALSE;
      ELSE
         violate_rule_five := TRUE;
         GOTO violrule5;
      END IF;
   END LOOP;
   <<violrule5>>
   IF violate_rule_five = TRUE
   THEN
            raise_application_error (-20600, lv_error_msg);
   END IF;When i try to change the password to 'blah-blah1' i expect it to show be error 20600. But instead shows ORA-00922.
Why is this happening?
All other rules in the verify_function are working correctly.
Please help.
I added the [ code ] tags to make the code easier to read.
Message was edited by:
Jan Carlin

I have noticed just now that a dump file having a name like ifrun60_dump_299, is generated by FORMS every time I issue the aborted call to the foreign function.
Inside the form dump file, apart from useless info like Registers and so on, the message:
"Could not find Module32First"
By a FILE/FIND/CONTAINING TEXT I searched all the DLLs, and I noticed that Module32First is a routine that can be found within each of the following DLLs:
Cl32
d2kwut32
d2kwut60
I tried to load those DLLs along with SECURSIGN.DLL by modifying the PROCEDURE LoadLibrary into the FFI-generated PLL code, and I have apparently no problem in loading all the DLLs that I wish, but the error persists, and that dump file is constantly generated, always looking for the "Module32First" routine.
How can I avoid all that mess and the FRM-40734 error??

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

Similar Messages

Maybe you are looking for