LabVIEW 6.0.2 Compund Arithmetic function in XOR mode Inverted generates Compiler error when file saved

I am posting this as a problem for NI to look at.
I am using the Compund Arithmetic function in XOR mode Inverted with 5 inputs. File is also set up in reentrant mode. When I attempt to save the file I get the following error:
Compiler error. Report this problem to National Instruments Tech Support.
int inv mode=0x40000
Advertising Section:
Alliance Member
William Simmons
Simmons Software Engineering, Inc.
714 Germantown Pkwy Ste 5-341
Cordova, TN 38018
(901) 679-3513
[email protected]
LabVIEW, TestStand, Automated Test
environments, On-Site, Off-Site
Attachments:
NXOR_error.vi ‏73 KB

XOR is a new addition to compound arithmetic node. LabVIEW developpers just overlooked the fact that the outpout could be inverted. The compiler fails to generate the proper code because the inversion is not expected.
Just do what the message says. Report the problem to NI Tech Support (and use a separate inverter node).
LabVIEW, C'est LabVIEW

Similar Messages

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

Error when calling a DLL function

Hi,
I am using external C++ code with labView. One of the DLL functions I use serves to call files. The directory and the name of the file is is passed as a parameter for this function. When the VI is running and arrives at this function (I use the Calling Library Function Node tool), the following message is displayed:
ERREUR de type class boost::filesystem::filesystem_error.
boost::filesystem:ath: invalid name "D:\Documents Johan\Johan\Stitching\Fichiers de mesure\front parfait\13z2" in path: "D:\Documents Johan\Johan\Stitching\Fichiers de mesure\front parfait\13z2"
I do not know why this message is sent to me.
Thanks for your answer
JF

Hello,
How are you passing the file path to the DLL -- are you passing it as a
string? If you are passing at as a string, I would do some basic
console output to make sure that your DLL is receiving the file path
corectly as a string and perform your appropriate C++ function in your
DLL. If the error is occuring with passing the file path you
might want to check out the links below for a little more information
on this.
http://zone.ni.com/devzone/conceptd.nsf/webmain/7d6a20fe02edbf318625690700704cf3#4
http://digital.ni.com/public.nsf/websearch/4E9234BA4C7C4ABE86256E3C0074760F?OpenDocument
http://digital.ni.com/public.nsf/websearch/3B994675B17C654A86256FDD00754DD2?OpenDocument
Hope this helps,
Travis M
NI
Travis M
LabVIEW R&D
National Instruments

I get an labview.exe application error when i use the driver of 4395A spectrum analyzer

i have the message:unhandled exception in labview.exe(HP4395A_32.dll):0xc00000005:access violation.
could you help me?

This error can be caused by many things. The first step in getting an instrument driver to function is the "Getting Started.VI"
Be sure the GPIB controller can establish communication to the device. Also, capturing with NI-Spy will help isolate any VISA errors.
Randy Solomonson
Application Engineer
National Instruments

Why I get an error when running a sequence using the LabVIEW operator interface ?

I have a simple TestStand sequence calling LabVIEW vis that is giving me an error when I run it with the .exe version of the LabVIEW operator interface and I set TestStand to run the vis using the 8.2.1 runtime engine instead of the development adapter. I made a change in the operator interface to open a vi programatically and get the value of a control, this vi is also used in the TestStand sequence I am trying to run. Could this be causing my problem ?
Thanks

Hello Verdulken,
I have a few additional questions:
Does your application function correctly when running the LabVIEW operator interface you have created as a VI in the LabVIEW development environment (i.e. does this problem only occur when the LabVIEW operator interface is run as an executable)?
What is the error that you are receiving?
Regarding the VI that you open programmatically, do you open it in a visible manner (i.e. use the Show front panel when called option from VI Properties)?If so, do you also close this VI after it finishes (i.e. use the Close if originally closed option from VI Properties)?
Does the error occur on the step that calls this very same VI again later in the sequence?
Does your application function correctly if you use the development adapter for all of your calls?
Thank you in advance for this information,
Matt G.
National Instruments
Applications Engineering

"Not Enough Memory" Error when programming Keithley 2400 using LabView 6i

I'm trying to use LabView 6i drivers to control a keithley 2400 via GPIB interface. Most of the drivers work fine but the high level operations such as a the sweep functions or even functions that perform a single measurement gives a "Not enough memory" driver error. What doesn't have enough memory? A single measurement can't overload the PC's or Keithley's memory buffer so why am I getting the error?
Thanks for any help you can offer...
Evan

Evan,
That's not a LabVIEW, GPIB, or NI-VISA error code - that error is generated by the instrument driver. I went ahead and downloaded this driver from keithley.com to take a look at this Perform DC VI.vi function's source. But unfortunately, the heart of the Perform DC VI function is a "Call Library Node" call to a keithley DLL, so that is a black box. Also, no c-source included that I could find, so I could not look at that either. And since I don't have a Keithley 2400 to play with, that brings me to the end of the rope on my system.
A couple of more things you could try, however, since you actually have the instrument.
(1) Definately build a simple VI to eliminate other aspects of your program. In this case, the most simple
VI would be an Init, Perform DC VI.vi, and then a close. Make sure this simple program reproduces the error. If it doesn't, then the problem is likely introduced in your code, not the driver.
(2) If #1 reproduces the problem, then check that you have all the driver pre-requisites correct (ie, that NI-VISA is installed, that the GPIB board is working properly, etc).
(3) If #1 and #2 do not result in any discoveries, then you will have to enter the black box of that DLL. Primary method to do that, to be honest, is to contact Keithley and ask for help, since they developed the driver. Second method is to use our NI-SPY utility, which can capture all calls to VISA drivers, (since this is a VXIpnp driver, it should be fundamentally using VISA within the DLL). Within NI-SPY, you will be able to see the individual function calls, and which ones are returning errors. That may help point in the right direction.
Regards,
Greg Caesar
National Instruments
Applications Engineer

What does LabVIEW mean by "Error 71: File Datalog Type Conflict"

What does LabVIEW mean by "Error 71: File Datalog Type Conflict" (Hex code:47)
Thank you.

Please provide us further information on when you are getting the error and what the functionality of the VI is. That would help us to troubleshoot your issue.
Is the error caused by a similar situation as the one descibed in this KnowledgeBase?
Best regards,
Philip C.
National Instruments
- Philip Courtois, Thinkbot Solutions

Why Labview.exe error when exit simple-state machine?

Can someone please help me figure out why, unless I ABORT the VI, I get a "Labview.exe is closing" error when I press Stop. I am using a simple-state machine like what comes with Labview's examples. What could be some causes of this? I have read that not closing all files first can cause an error but it seems to me like I have them all closed.
I am running LabVIEW 6.1 on Windows 2000. In my Initialize state I use Global and Local variables. Could these cause problems?
Any ideas?
Thanks,
Lauren

I do an AI Clear after data is acquired. I don't open up any AI functions in the "INITIALIZE" state, so I think the only AI Clear I need is where it is. WHat do you mean print the front panel without errors. I see its set to "print at completion" (the computer I use does not have a printer connection) but do you mean save the front panel to file without errors?
Could there be an error in these subVIs that causes the program to shut down?
Attachments:
ReadConfigSettingsSUBVI.vi ‏72 KB
Lines_From_File_SUBVI.vi ‏27 KB

Please help suggestions for solving built-only compiler error: 'The VI is not executable. The full development version of LabView is required tofix this error.'

We have develoepd a software tool and build it on regular basis. It currently runs error free when compiled in the editor, but when we built it and run the executable stand alone we get the error.
'The VI is not executable. The full development version of LabView is required tofix this error.' plus a broeken error.
This menas an compiler error that is not present in the editor but in the stand alone version. We tried to identify errors as suggested in several posts in this forum, but so far unsuccesfull.
As the editor and its compiler do not see the error and are running fine and the stand alone version just syas 'find the error in the editor' in this case LabView is of no help.
Can anyone suggest a sensible or 'good practice ' way of searching for the source of this error?
Our project comprises hundreds of Vis over several libraries.
Thanks,
Chris

Thanks Craig for all your suggestions.
We seem to have located the problem in a new vi just added to the package causing conflicts by using the same vi names as other vis already present in the package. Excluding this vi removed the error.
It seems related to a conflict by having two vis with the same name, which was mentioned by LabView and interactively resolved when running the main vi from the editor. When successfully building the main vi the builder did not mention this conflict and reported a successful build, but when trying to run the executable it gave the cryptic error. The error caused us problems because there was no hint for the cause, just the suggestion to solve this in the editor, while at the same time in the editor the VI was running fine.
We will post about this in detail after we have positively proven that this actually was the case.
The .net version issue was already checked.
Performance was the same on all machines we tested on including the dev machine.
Debugging was tried nut did not help as the vi could not run (broken arrow). We assumed that debugging only helps in running faulty functioning vi''s. We did not check for broken arrows in sub-vis (after connecting), that could have helped, although our application has hundreds of our own vis.
In relation to your remark:
'Are you using many classes? Have you verified that the proper access scopes are set for functions calling those vis?'
Could you elaborate on setting access scopes. We were not aware of this option in LabView, although we realize this is a basic element of the underlying c code.
Ragrds,
Chris

I recieve the following error when running an executable ("This VI is not Executable. The full development version of Labview is required to fix the errors"

I recieve the following error when trying to build and run a labview executable. I am able to build the executable but when trying to run the executable, a pop up window comes up asking the user to select a dll. (please see screen shot attached). Once the DLL is selected, I get the error that This VI is not Executable. The full development version of Labview is required to fix the errors. (please see screen shot attached). I have also attached a snapshot of the project window.
I have the professional development system
I can run the main VI
all the required DLL's are in the dependencies section of the project window.
I am trying to find the root cause of this error but to no avail. can anyone give me a clue to what i am missing here. Any suggestions on where i should look to find the problem ?
Thanks in advance to all labview users for your help
Attachments:
project window.PNG ‏36 KB

other PNG
Attachments:
Broken Arrow on EXE.PNG ‏179 KB

Problem with Vision Builder and LabView: Error -1074395995, File not found

I have created an inspection with Vision Builder AI 2009 SP1. In it I load some pictures from the HDD and run some checks over it. It works fine. Then I have migrated it to LabView 2010, I get a message that the migration is successfull, but when I run the VI on LabView I get a fail status. I have been checking my program and I have found and error when I try to load the picture from file: Error -1074395995 occurred at IMAQ ReadImageAndVisionInfo
Possible reason(s): IMAQ Vision: File not found.
But I am not sure which file it refers to. At first I thought it was the picture I wanted to load, but I have checked the path and it is correct, so maybe it refers to another thing. What puzzles me most is that it works perfectly on Vision Builder and I have changed nothing in LabView, maybe it is a problem with the migration. Any clues?

Here's a screenshot of what I'm talking about. Put a break point here and see what the path is and compare that with what Vision Builder AI is using (described where to find this in the previous post). You could find where this global is used to make debugging easier.
Hope this helps,
Brad
Attachments:
Generated Code.png ‏43 KB

Error when call RFC Function module in R/3

Dear All,
We are trying to call RFC function module CBIF_GLM1_PROCESS_ORDER_READ (This is not a BAPI and also not released ) in R/3 from XI system.
we are facing the error "Error while lookup Exception during processing the payload. Error when calling an adapter by using the communication channel CC_PPPI_MES_RFC_Rcvr (Party: , Service: WCD_320, Object ID: 16563889b449328eac76caa6a3bc592e) XI AF API call failed. Module exception: 'error while processing the request to rfc-client: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.adapter.rfc.util.bapi.BapiException: Parameter with name RETURN not found.'. Cause Exception: 'com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.adapter.rfc.util.bapi.BapiException: Parameter with name RETURN not found.'."
This is the first time we are doing this configuration.
Could you please let me know what woulbe the reason.

read the original message
We are trying to call RFC function module CBIF_GLM1_PROCESS_ORDER_READ (This is not a BAPI and also not released ) in R/3 from XI system.
I am talking about the above Receiver RFC channel which you guys are using to call R/3 from XI. That where you need to change the commit parameter

Error when using record group type as param in a function in where clause

Hi folks.
I have a record type defined in a packages specification. I have to use this record as parameter to call a function. I am able to call the function if as return its value to a string variable. However, the function should be called into a query to compare the returned value and this code is not compiled.
The code is below:
DECLARE
l_line_group_rec INL_CUSTOM_PUB.inl_ship_headers_rec;
l_name VARCHAR2(100);
l_count NUMBER;
BEGIN
l_name := INL_GET_PARTY_SITE_NAME(l_line_group_rec); -- Compiling successfully
SELECT COUNT(1)
INTO l_count
FROM dual
WHERE INL_GET_PARTY_SITE_NAME(l_line_group_rec) = 'Allied Manufacturing'; --- Error when compiling
END;
I got the error: PLS-00306: wrong number or types of arguments in call to 'INL_GET_PARTY_SITE_NAME'
I would like to know if there is any restriction in using record type as parameter in where clauses or if there is another way to do it.
Thanks in advance

Hi.
The definition of INL_GET_PARTY_SITE_NAME:
FUNCTION INL_GET_PARTY_SITE_NAME(p_line_group_rec INL_CUSTOM_PUB.inl_ship_headers_rec) RETURN VARCHAR2 IS
l_party_site_name VARCHAR2(100);
BEGIN
l_party_site_name := 'Allied Manufacturing';
URN l_party_site_name;
END INL_GET_PARTY_SITE_NAME;
Thanks.

Error when running the LabVIEW program

hello...........
I'm newbie in LabVIEW....I have a problem when i'm running the LabVIEW program...i want to analyse data using the LabVIEW through the real experiment....
My problem is, there is an Error when i try to start the program...This Error forced me to restart the program several times until it can run.......By the way, i'm using Picoscopes 3206 to connect the LabVIEW program in PC with the real experiment.....
Here, I'm attached the picture that I snap when the Error occur....
Attachments:
error.JPG ‏222 KB

You have to try to isolate the problem...
Use 'Diagram disable' or 'Case' structure to run special part of code or try write a specific code to access and manage your equipment.
Several questions could help:
- Are you up to date with your hardware driver?
- Do you call external ressources (ex: dll)? perhaps with instability
- Do you properly close connection with your equipment after using?
- With your offline mode, do you load all the code, including hardware driver or do you use a special method without no loading the specific code?
- When you are able to run after many tries, is the program stable? Can you re-start it without exiting LabVIEW?

NO Authorization error when accessing Functional module RH_CUT_OBJECT

Hi,
I am getting NO AUTHORIZATIOn error when I am executing SE37-->FUNCTIONAL OBJECT-RH_CUT_OBJECT.
I also checked SU53 screenshot which says AUTHORIZATION CHECK SUCCESSFUL and there are no errors or missing authorizations highlighted in SU53.
I switched on the TRACE-ST01 then also the error is not captured.
I would like to know WHY am I getting NO AUTHORIZATION error.
I am already having access to T-CODE SE37, SE11, SE80, SMARTFORMS and authorization object S_DEVELOP.
I need to know this ASAP on why I am getting NO AUTHORIZATION error when I am trying to access the FUNCTIONAL MODULE RH_CUT_OBJECT whereas I am having all the required authorization required for ABAP Developer including SE37.
Is it something I need change at ABAP code level.
Please advise ASAP.

The reason is ..You do not have acess to see/acess the data this FM is trying to acess ...Debug the function module keep a breakpoint at The Raise statement see which authorization you do not have ....BTW this is my guess you are trying to demilit certain objects /infotypes using this FM and delimit basically makes that object non-usable in that system .So it is quite evident that every one will not have authorization for that .Please post in detail that what is it that you are trying to achieve using this function module .....
Also you can check with debugging which authority object is being checked before raising the message and can ask security team to get that added to your profile ....
Thanks,
Anjaneya

LabVIEW 6.0.2 Compund Arithmetic function in XOR mode Inverted generates Compiler error when file saved

Similar Messages

Maybe you are looking for