Display Property Node Error 1077

I have created a vi with multiple analog inputs (up to 20), and I want to be able to turn plots on and off on the front panel. I currently have this case structure set up to go through each input (i through N), and the front pannel array (LED buttons) can be turned on and off to choose which plot to display:
Turning the plots on and off work, but I am getting this error message:
Error 1077 occurred at Property Node (arg 1) in NetworkAnalyzer_UpdatedDAQmx.vi
Possible reason(s):
LabVIEW: Invalid property value.
Property Name: Active Plot
Any solutions? Thank you.
Solved!
Go to Solution.

Are you sure the number of elements in the Boolean array matches the number of plots you actually have? That error implies that you have more elements in your Boolean array than you have plots.

Similar Messages

Can I access probe image display property node?

Hello
Working with labview 2010.
I would like to use a user defined palette in the probe image display.
I know how to do it for standard image display, but not for the probe viewer. Is it possible to access the property node of that display?
Working with labview 2013
Can i use a custom probe to apply a user defined LUT?
Thanks,

It sounds like you want to enable Snapshot mode on the image display controls. Note that you will then need to wire the image to the display reference each time that you want the display to be updated.

Error 1077 in Sub VI chart node property code

Hi all,
I've finally worked out how to be able to change the data that is plotted in a strip chart, the code I have below works fine if it is added into my global loop, however it takes a lot of room and I'm trying to place it in a sub VI. However, when I do this I get the 1077 error on one of the property nodes, if I click ignore it moves onto the next node etc. I read in other posts that the problem had resulted from the order in which the code was executed, but I can't see where I could have gone wrong. If someone could point it out to me that would be great.
As for what this sub vi does, the max and min arrays store the max and min values of the y axes to be configured on the front panel, there is 6 strip charts and 20 data strands which can be plotted. When the user selects the data they want plotted in the strip chart, the property node of that strip chart is used to hide all the plots except the one selected and adjust the axes to the required scale. If someone could point out where I have gone wrong here that would be greatly appreciated!!
Stirling
Attachments:
Chart Config.png ‏47 KB

I looked at simplifying your code as a challenge. Attached is a VI (LV 8.2.1) and a screenshot of the block diagram. Since I was creating from scratch, I didn't have your actual rings or waveform charts. I just created 2 rings and 2 waveform chart references. These can be scaled to as many as you need.
If this is going in a subVI, you may want to make the rings and references as arrays, so you won't need numerous connector terminals for each ring and reference control. If you do that, you can eliminate the build array functions for those before the loops. It would also make the subVI more scaleable.
I also broke the property nodes into 2 loops. As it was, you were setting the property nodes 20 times for each of 6 charts. Only the active plot and visible? needed to be looped through 20 times. The actYscale, Max, and Min were the same for each of the 20 iterations, so they only needed to be done once.
One other possibility would be to do a defer panel updates before, then allow them after the code, so there aren't as many screen refreshes while the loops iterate.
Message Edited by Ravens Fan on 08-18-2007 09:17 PM
Attachments:
Multi chart mod.vi ‏28 KB
Multi chart mod.png ‏11 KB

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.

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

Error cluster in XControls Property node

Hello!
Property Nodes of XControls do have Error Clusters, but how can I change those out of the Facade? I'm setting an object through a property node for tree data. It is possible that some of the object methods generate an error while executing in the facade and I would like to catch this error in the VI containing my XControl.

You can't change the error output from a property node from within the facade since the facade only gets called after the property VI has run and modified the contents of the display state information. If possible try to catch invalid values in the property VI itsefl. If there are errors that the xcontrol will need to report you will need to provide a separate mechanism.
Something that I have used in the past to good effect is the idea of an error stack. The error stack itself is an array of error clusters that resides in the display state data and is maintained as a circular buffer by the xcontrol code. To access this value from the calling program create a read-only property that reads the contents of the buffer and then clears 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

I get error 1055 "Object Reference Is Invalid" when I try to write to a property node

Hi, I'm trying to get these results to be displayed in two tables now, where I originally had them being displayed in just one. Outside of the attached vi, I can just copy the value property from one table to the other after this vi has run, and the table values appear properly. The problem with that is, that any table property I assign (changing background colours to be exact), is not considered part of the value property, and thus isn't copied when I copy the value from one to the other.
The thing I can't understand is that the second set of property nodes (at the bottom), give me the "Object Reference Is Invalid" when I added them. I've tried everything I can think of, but can see no logical reason why I get that error for those two, while I don't get the error for the top two (not wired to constants).
Any help on this would be much appreciated. Thanks
Geoff
Attachments:
Table Display Testing.vi ‏396 KB

The logical reason that you're getting that error is that you are not passing in a reference to Table In Two. The control is not wired to the connector pane so you are not getting a reference from the calling VI.

Cursor List Property - error 1077

Hello
I'm trying to programatically create cursors in the Waveform Graph. I want to have as many cursors as plots in the graph. See the attached VI. And now the weird thing: when I decrement number of plots, everything is OK - plots are shown, cursors are created. But when I increment them - I get "Error 1077 - Invalid property value." from the Cursor List Property Node.
So the typical question: is it me or LabVIEW doing it wrong?
Attachments:
CursorList.vi ‏29 KB

Thanks to your reply, TiTou, I've came with another workaround - if you put wait (for example 10 ms) into the sequence struct on my VI's front panel, it works. And this lead me tothe best solution yet - update graph using Value property:
This leads to interesting conclusion regarding updating controls using terminal or property node. It seems that update through terminal is the quickest method, but it doesnt work immediately - the graph didn't know about the data update right after the cable reached the terminal! When you use Value property node, you can be sure that everything is updated when the flow leave the node.
Any comments from NI about this?
Attachments:
cursors.png ‏39 KB

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.

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

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

Setting DAQ channel by property node does not display the value

I am writing a configuration VI to set channel selection and calibration parameters for an SCXI chassis. I store a default setup in a configuration (ini) file and read that file automatically when the VI is called. The value from the file are set by property nodes using the "Value" property. The values from the file do not display in the DAQ channel selection rings, but the numerical calibration values do display correctly. When I click the down arrow in the channel rings, the correct value displays.
This behavior exists both in LabView and app-builder EXEs. Also, if I change the property nodes for the DAQ channels to local variables, it works. The Value (signaling) property doesn't cause them to display
properly either. Why can't I use the property node?

I don't understand exactly what you are trying to do.
Please upload a simple VI to demonstrate the behavior you are describing. Remember also to attach the .ini file.
Best regards,
Philip C.
Applications Engineer
National Instruments
www.ni.com/ask
- Philip Courtois, Thinkbot Solutions

Display Property Node Error 1077

Similar Messages

Maybe you are looking for