Property node standard error in functionality - odd behavior

I am getting what I would consider unusual behavior from a property node when there is an error on the error cluster input. The Help for the VI indicates this node has Standard Error In functionality, which I interpret as if there is an error on the input then the node does not run and the error is simply passed through to the output.
The behavior I'm getting is that the error gets passed through, but the properties of the node also get passed out with the data that was present the last time the node was called (including when it wasn't this specific node, but a different property node within the same VI that has the same property outputs).
In Psuedo code, this is what I'm doing:
Use Invoke node to call a method from a DLL (which sends a command to a device and gets its response).
Pass the method reference to a property node, which then outputs the properties of the method (the response from the device).
This works fine when everything is as it's supposed to be (device I'm communication to is connected, etc.).
If I disconnect the device completely and then run the VI again, I get the property outputs from the previous communication out of the property node, which are obviously not valid as the device isn't even connected. This happens even if the command I sent to the device is not the same; Command1 is sent and gets valid response, disconnect device, command2 is sent and I get response for command1 from the property node of command2. Command1 and command2 are in different cases of a case structure.
At first I thought there might be an issue with the DLL functionality (and there might be) reporting stale data, but before that is even an option it seems the property node shouldn't even be possible to have data output when the node is supposed to be bypassed entirely when an error is passed in.
Is this supposed to happen? Am I missing something?

Coincidentally, this week I ran into what appears to be the same behavior with the Scan from String function, and I thought of this thread. It doesn't help solve your problem, but maybe it's useful to know that this behavior happens in other built-in functions, not just Property Nodes. I started a new thread to look at this more generally.

Similar Messages

Tab Control Property Node unknown error on TPC

I am using Lab View 8.6. I am programming an HMI onto a TPC 2106. I am using a Tab Control and it workls fine. The problem is when I add a property node for the tab control to the block diagram. I get an unknown error no matter which property I choose or if it is read or write. I tried it on a vi destined for the computer and it works fine. It seems to be an issue with the TPC 2106 as the destination.

Hi vrundquist,
When compiling a VI for a TPC, there are many properties of controls and indicators that will not be supported. Which properties specifically have you tried? I want to be sure you are choosing a property that should be OK. For example, try the Visible property. Also, is there anything else going on in your code, or can you reproduce this with a VI that has nothing but a tab control?
Regards,
Brian A.
National Instruments
Applications Engineer

Property node invalid error

hi all,
i am transfering my application(for HP 4284a) from my old computer(windows 98 and labview 6.1) to a new one (windows xp and labview 8.0). A repeated error occured.
Property Node: invalid property.
Someone told me i have to change the property from Range to Range2 for the Excel Worksheet Node in my program. But as can be seen from the diagram, the list only has Range and no Range2.
Attached are print screens of the error.
Any further information required can tell me. Please help. Thanks.
wjsd
Attachments:
error.zip ‏205 KB

Hi wjsd
It's not the Range property that is wrong, but the Value property. Use the Value2 property to read/write values from/to Excel.
Hope this helps
Daniel

Capturing various standard errors using openscript

Hi , we have automized a scenario using openscript where in the steps are like starting from creating requistion --> Req approval --> PO creation and approval --> Receipt Creation --> Invoice Creation and then quick payment.
when we playback the script it works fine with valid data inputs from databank. But we want to capture all the standard errors if any occurs in between when script playback. For eg : if Invoice batch name entered already exists in system it throws a warning like name already exists. At this step scripts fails but it capturing some error which end user wont understand. By anyway we can capture all the standard errors that can occur during functional testing. I mean we cannot write custom exception for each situation and may not what kind of errors we may face. So is there any way we can capture all the standard errors during functional testing using openscript/OTM. The platform we are using is Oracle Applicaitions ERP R12, open script 12.2

Enter your codes in try and mention code like following in catch
try{ }
catch(Exception e ) {
String pageindex = web.getFocusedWindow().getAttribute("index");
            if(web.element("/web:window[@index='"+pageindex+"']/web:document[@index='"+pageindex+"']/web:div[@text='Error']").exists()){
            fail(web.element("/web:window[@index='"+pageindex+"']/web:document[@index='"+pageindex+"']/web:div[@text='Error' ]").getParent().getAttribute("text"));
            else if(web.element("/web:window[@title='Oracle Applications R12']").exists()){
                forms.captureScreenshot();
                    think(2.169);
            String statusBarMessage = "";
            if(! forms.getStatusBarMessage().equalsIgnoreCase("")){
                statusBarMessage =""+forms.getStatusBarMessage().toString();
            if (forms.choiceBox("//forms:choiceBox").exists()) {
                fail(" Unexpected choicebox found:- "+forms.choiceBox("//forms:choiceBox").getAlertMessage()+ (!statusBarMessage.trim().equals("") ? (".... \t Statusbar message: "+statusBarMessage) : ""));
            } else if (forms.alertDialog("//forms:alertDialog").exists()) {
                fail(" Unexpected alertbox found:- "+forms.alertDialog("//forms:alertDialog").getAlertMessage()+ (!statusBarMessage.trim().equals("") ? (".... \t Statusbar message: "+statusBarMessage) : ""));
            } else {
                fail(" Failed during script playback : " + e.getMessage()+(!statusBarMessage.trim().equals("") ? (".... \t Statusbar message: "+statusBarMessage) : ""));
        else {
            fail("   Failed during script playback : " + e.getMessage());
Cheers,
Deepu M
[email protected]

Error -70038 occurred at Property Node in nimc.fb.power.power.coordinate.vi

HI,
I created a Real Time application with debugging enabled that only makes a straight line move and then finds center (using SoftMotion function blocks). When I run the VI from the project everything works fine. When I create the executable and run the application as a start up some times it moves beyond the limit switches and I have to abort the application, it never really works as smooth as it does when ran directly from the project.
I simplified the application. When connecting to the executable ( Operate>>Debug Application or Shared Library...)
I saw that sometimes I was getting an error that said the find center function could not be executed because the driver was not enabled. This was never needed when running from the project. I added the Power SoftMotion block and I enabled the driver before getting into the while loop that finds center. Again the VI ran without errors when ran directly from the project, but when I connected to the executable I found the following error coming out of the Power SoftMotion block (the name of my VI is: "Testing SEND to ZERO by itself.vi"):
"Error -70038 occurred at Property Node in nimc.fb.power.power.coordinate.vi --> Testing SEND to ZERO by itself.vi
Possible reason(s):
Motion: An unexpected error has occurred internal to the driver. Please contact National Instruments with the name of the function or VI that returned this error"
I am using cRIO 9022 as a controller and two 9512s.
LabVIEW 2009
NI-RIO 3.2.1
SoftMotion
Any idea why the VI works fine when ran directly from the project but does not work as expected when ran as a stand alone application directly on the cRIO?
Thanks,
Fab
Certified LabVIEW Architect * Certified Professional Instructor * LabVIEW Champion

Marc,
When I simplified my program, I forgot to put the Power Function block inside a loop and make sure I was sending a pulse for the execute input. I am guessing that could have caused the weird error.
If I see it again, I will let you know.
Thanks,
Fab
Certified LabVIEW Architect * Certified Professional Instructor * LabVIEW Champion

Tab Control Property Node gives a build error when used in a VI for LabVIEW PDA

Hello,
    Iam new to LabVIEW development & need help regarding this:
    We are trying to port a LabVIEW application from desktop to a Windows Mobile PDA. Please note that the LabVIEW application works fine on the desktop. In one of the VIs, a Tab control property node is used which gives a build error with LabVIEW PDA project. A sample VI which shows the problem & the error list snapshot is attached with this post. Can anyone please suggest an alternate approach to achieve the same functionality with LabVIEW PDA? Waiting for an early response from anyone...
Thanks & Regards,
Subhashini
Attachments:
VI_Error.zip ‏31 KB

Hello Ton,
    Am glad that i got a response, thanks. The following links indicate that Tab control is supported on PDA target:
http://digital.ni.com/public.nsf/allkb/CBA335641E27B858862571490015EA88?OpenDocument
http://forums.ni.com/ni/board/message?board.id=170&message.id=221507&requireLogin=False
    I feel that the Tab control property node that has been used in the VI (which is attached earlier) may not be supported on the PDA target. Can u (or any LabVIEW expert) suggest an alternate approach to achieve the same goal with LabVIEW PDA (changing colour of Tab control pages programatically)??
    I had missed out some details earlier: We are using LabVIEW 8.5 PDA module on a Windows Mobile PDA.
Thanks & Regards,
Subhashini

Just checking on another odd feature: Typedef enum Property Node "Value" not reflecting changes in the Typedef?

Just encountered this odd behavior in LV 2011 which I reduced to the following example:
- create a new VI and drop an enum control on te FP.
- make this control a typedef and open the corresponding typedef
- create a "case 1" item and a "case 2" item
- save the typedef (I used the name Typedef Control 1) and CLOSE it (this is to allow updating of the original control).
- drop a case structure on the diagram and connect the enum to it:
So far so good. Now create a "Value" Property node for the enum and use it instead of the terminal:
If I now go back to the typedef and add a "case 3" item, save the typedef and close it, the control is updated, but the Property node is not.
How do I know that? For one, the Case Structure contextual menu does not offer to create a case for every value. Also, if I add a "case 3" case manually, it turns red.
Luckily, the magic Ctrl-R key stroke actually does solve this problem.
Tested in LV 2011.

By Ctrl-R trick do you simply mean running the VI? That is one way to force a recompile, but if you hold down Ctrl while pressing the run button you can recompile without running. This should not be "dangerous" in any situation.
As you have drawn your example, I see no reason not to use a local in that situation (ok, maybe for vanity). Still, I view the behavior you describe as a bug, and it should certainly be fixed for the benefit of local haters out there. You have to be a little careful where you draw the line between what gets handled in real time and what gets handled only at compile time.

NI 845x USB: Error -301713 occurred at Property Node (arg 2) in General I2C Read.vi

Hello,
I am currently working with digital accelerometer LIS35DE from ST Microelectronics. I want to start with tests of this device. For that purpose I used NI 845x USB to connect with accelerometer via I2C. Unfortunately, when I made electrical connections and set up parameters of communication and run the program (I found it in examples) the following error occured:
Error -301713 occurred at Property Node (arg 2) in General I2C Read.vi
Possible reason(s):
NI-845x: An input parameter, or combination of parameters, is invalid. An example of this error may be setting an invalid baud rate or enabling I2C ACK polling while using 10-bit addressing.
The code can be found in attachements. I couldn't find any extended description of this problem. What could be a problem: incorrect device address, register address, configuration parameters?
Any help is appreciated!
Best regards,
Michael
Attachments:
General I2C Read.vi ‏24 KB

Hi MicMac89!
First of all could you please post which version of LabView are you using?
Could you please tell me which version of 845X hw are you using? (8451 or 8452)
I opened the example you attached. As you wrote the error occurs at the second argument of the property node. (I guess this is the first property node where the error occurs.)
This argument of the property node enables the onboard pull-up resistors. But not all NI-845x hardware support pull-up resistors. (Because of this is important to know which hw version are you using.)
Did you try the example with disabling the pull-up resistors?
I suggest you to go through the Manual of this product, (if you did this not yet) This could make it clear where and when to use what kind of pull-up resistors.
For example: If you are using 8452, you must enable pull-up resistors, for Vref ≤ 1.8 V for the FPGA to properly detect a low-to-high transition
Manual: http://www.ni.com/pdf/manuals/371746d.pdf
HW specification: http://www.ni.com/pdf/manuals/290598a.pdf
Please post if my suggestions helped. Of course if you have any questions, don't hesitate to post them.
Best regards,
Balazs Nagy

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 1055 occurred at Property node

Generating the error:
"Error 1055 occurred at Property Node in ... Possible reason(s): LabVIEW object reference is invalid."
when I try to wire the IMAGE OUT output from the IMAQdx Snap vi to the value property of an externally referenced image display control.
To describe in more detail, I have a parent vi with an image display control and a child vi which has a control refnum linked to the parent vi display. In the child vi I create a value property for the refnum and try to write images to it, essentially to drive the parent display from the child vi.
The technique works elsewhere, though I can't think of what I could have done differently to generate this error?

Hi Mike - looks like I may not need to. I've been working away at this and have found the original cause and something else a bit weird...
I deleted the objects from the sub-VI that was giving me errors, then cut and pasted the objects (image display refnum and value property) from a VI that was working and this solved the problem. So you might think that the issue was just some obscure configuration item, or I'd used the wrong type in my reference or something.
I found the display reference in the parent VI was not even wired to the sub VI - duh! Error between keyboard and chair. So at least the original error message made sense, but I have no idea why it actually worked after pasting in the new objects. Are these references using some sort of auto-magic? Who knows. Safer to wire up my sub-VI's properly methinks.
Sorry for wasting forum time on this one.

Property Node in VI throws Error 7 in LV 7.1 but runs OK in LV80 and LV86

Hi everybody
I build a custom IVI instrument driver and using the LV tool <Generate VI Interface from Instrumnet CVI Driver> I was able to get a LV wrapper for each driver method. From LV86 I saved first in LV80 and from LV80 I saved as LV71. I have all these LV versions on installed on my PC.
I have no trouble in using these LV wrappers in any of these LV versions as they work OK.
Now my IVI driver has also Properties that the Import Driver Tool does not convert as a wrapper and for that reason I had to create a Property Node Warpper myself and saved in the same LLB under LV/instr.lib folder.
Once I have all these method wrappers and the property node wrappers I made a small VI
1. Initialize IVI With Options on a TCPIP instrument
2. Set-Get an IVI Timeout property
3 Close IVI driver on TCPIP instrument.
Good part is that in LV 86 and in LV 80 the VI is running fine when I use these LV version wrappers from their coresponding instr.lib folder.
As soon as I am going to use the LV 71 wrappers in LV 71 I could create the same small VI to Set/Get Timeout and the VI look OK nothing is broken but when I run it the Initialization is OK but as soon as is reaching the Timeout Set Property Node gets out an Error Code 7.
To run this VI the user need to install the jdCMR IVI driver then add the LV71 jdCMR wrappers inside LV71/instr.lib and then he may build any VI using these LV warppers.
The only problem is that the Property Node get out an Error Code 7 and the same error code get out from Property Node if I am picking the Property Node from VISA Advanced Pallette, connect this node to jdCMR driver, set Timeout property inside the node and after connecting the input and output references plus the input and output error to Initialize and Close LV wrappers I still get this error at running time.
The same LV 71 VI if I open in LV80 or in LV 86 runs without any problem?
Does anybody knows why LV 71 is not working the same way as LV80 and LV86 with respect to Property Node?
Btw When I save my VI from LV 80 to LV 71 I get this warning...
IVI Error Message Builder.vi
    Cannot save VI from VI.LIB to previous version.
Merge Errors.vi
    Cannot save VI from VI.LIB to previous version.
Thanks
Sorin

Hi
For further testing of the IVI driver Property Node bug with LabVIEW 7.1 IVI drivers I download and installed two different IVI drivers from two very known instrument companies, Rodhe-Schwarz and Agilent Technologies.
I have to mention that both these companies releasead their IVI NI LabVIEW 7.1 drivers under NI Instrument Driver Network and ready to be installed and used by any customer of these two instruments.
The bug is present only in LabVIEW 7.1 version as if I take the same VI that breaks in LabVIEW 7.1 I could run it without any problem in LabVIEW 8.0 or LabVIEW 8.6 versions.
Anybody could test this bug for these two NI released IVI drivers in simulation in LabVIEW 7.1 by following these links below.
Agilent ag81150ni IVI Driver for LabVIEW 7.1 install from here. Run in simulation only by setting Simulate=1
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=55798957B1A633BDE0440003BA7CCD...
   Rodhe Schwarz rsngpt IVI Driver for LabVIEW 7.1 install from here. Run in simulation only by setting Simulate=1
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E91D6659CE034080020E748...
After installation complete close LabVIEW 7.1 if was open, then restart LabVIEW 7.1 and now you may see under the LabVIEW Instrument Driver Palette two new IVI drivers ready to be used as LabVIEW 7.1 wrappers.
Open a new blank VI and from Instrument Driver Palette use two well known Vis that are Initialize With Options.vi and Close.vi add them on your blank VI block diagram and connect thm together. Accept all default parameters except Simulate that must be Simulate=1.
Both Vis run OK in simulation mode without errors. Now pick a Property Node from VISA Advanced Panel and squeeze this between the Initialize With Options VI and Close VI and make the instrument reference in-out and error in-out connections.
Now run these two simple Vis in simulation
I run Rodhe Schwarz IVI driver and Property Node passes OK until the end
I run Agilent IVI driver but Property Node is getting out Error Code 7 that is the same as my own driver error.
Both these IVI drivers are under NI Instrument Driver Networks and have been built and integrated as native NI IVI instrument drivers.
Question is why they behave so different with respect to Property Node from the VISA Advanced Panel?
I attached the screen shots as PNG files that show clearly the difference of VISA Property Node behaviour when used under the same circumstances.
Thanks  Sorin
Attachments:
ScreenTestShots.zip ‏152 KB

Error with property nodes and svx_DAQmx Popup for DSA.vi

Some example vi of the sound and vibration toolset 3.1 use property nodes with an undefined class (e.g. svx_DAQmx Popup for DSA.vi). I use Labview 7.1 and NI-DAQmx. Could it be that the vi uses classes from traditional NI-DAQ?

The error occurs in:
C:\Programme\National Instruments\LabVIEW 7.1\examples\Sound and Vibration\Utility\Daq\DAQmx\svx_Get DAQmx Info.vi
C:\Programme\National Instruments\LabVIEW 7.1\examples\Sound and Vibration\Utility\Daq\DAQmx\svx_DAQmx Popup for DSA.vi
see also attached screen shot.
It is a new installation on a PXI-system, WinXP, LabView 7.1, SVT 3.1, NI-DAQ 7.4 (only DAQmx driver installed). The examples had not been tested before.
Attachments:
screenshot.jpg ‏144 KB

The VI closed the connection : error 1074360302 at property node(arg 1)

hi!
I'm trying to running a code which apply the control of my myRIO through a VI on my host computer. A video stream of data is also going to be send from myRIO to the Host Computer VI. However, I am getting the "Host Computer VI" closed the connection. I have no idea why.
And at the Host Computer keep giving out error 1074360302 occured at Property Node (arg 1) in myRIO vi.
I would be glad if someone could help me.
Thank you.
Attachments:
Picture1.png ‏81 KB

Hi e_pah,
Thanks for your response, what sort of camera are you using? This error has been previously seen with a Stingray camera when the IMAQ drivers aren't quite up to date.
So firstly, we need to make sure the IMAQ drivers are updated.
Further questions regarding your application:
Did this VI ever run?
Does this error occur everytime the VI is run?
What is the the property node doing?
Many thanks
Ingram

Multiplot XY graph : error when wiring 24 to active plot property node

I'm using LabVIEW 2009
When I wire 24 or higher to the active plot property node of a multiplot XY graph , I receive error message :
error 1077
Property Node (arg 1) in Untitled 1
<APPEND>
Property Name: <b>Active Plot</b>
Anyone a suggestion ?
Solved!
Go to Solution.
Attachments:
Error1077.png ‏20 KB

Hi,
how many plots do you have currently plotted? ActPlot can only be as big as the current number of plots...
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Error 1055 occurred at Property Node : Object reference is invalid. This Error occurs only in built application

I am using a WaveformChart to display multiple traces of data, the number of traces is variable, I use property nodes to set the number of traces and whether the digital display is visible or not, as more data is available the number of traces is increased and the digital displays are made visible. Within the Labview design environment everything works well. However when running the built application if two or more traces are to be charted I see error 1055. I suspect it is related to making the digital display visible on two or more waveform traces. See VI attached.
Why is this error happening ?
Thanks.
Single trace
Two traces
Solved!
Go to Solution.
Attachments:
Setup Plot Style.vi ‏29 KB

WF Charts only create their plots at development time.
If you attempt to access a plot that was never there you get that error.
To work-around this detail, simply size the legend for more plots than you ever expect to use at development time so that the plots are created and availabe when you do the build.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Property node standard error in functional​ity - odd behavior

Similar Messages

Maybe you are looking for

Property node standard error in functionality - odd behavior