Error 1055 using XY graph's node property

Hello I'm using the node property block to specify the plot name of a XY graph (and other things). But is so strange because it makes an error 1055 , incorrect object. I'd run this application before and I'd no
problems, what is the reason?
Thank you
Larson

Error 1055 occurred at Property Node (arg 6) in 29-08.vi
Possible reason(s):
LabVIEW: Object reference is invalid.
This is the node property I'm using (case false and true). It runs correct but if I introduce the plot name attribute it makes this error. But this plot name is a constant.
Attachments:
case_false.bmp ‏1031 KB

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

FRM-47026 Cannot get parameter error when using bi graph

Hi,
I have recently tried to use the BI Graph bean provided as a demo from Oracle.
I have amended the cursors and put into our system but get an error on the master graph.
When i mouse click on a column i recieve the error from forms :
FRM-47026 Cannot get parameter GRAPH_INFO attributes from parameter List CUSTOM_ITEM_LST19: no such names parameter exists.
Any ideas. i have not changed the code in this trigger only the procedure cursors to work within our system
code in trigger:
               eventValues := get_parameter_list(:system.custom_item_event_parameters);
               get_parameter_attr(eventValues,'GRAPH_INFO',eventValueType, tempString);
               set_custom_property('PJC.WAREHOUSEGRAPH',1,'HIDE_GRAPH','');
               FORMSGRAPHSAMPLE.clearData('PJC.DETAILGRAPH');
               FORMSGRAPHSAMPLE.populateDetailGraphData('PJC.DETAILGRAPH',tempString,',');
thanks

Hi,
Did you ever get this issue resolved?
I am facing the same problem.
Thanks
Ian

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.

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 1055 on Graph cursors.

I am using LabView 2010, expanding on one of the example vis for data acquisition. I want to use graph cursors to allow someone to zoom in on a particular part of a graph. To do so, I have been trying to use property nodes. When a graph has more than one cursor, the property nodes seem to access only the highest indexed cursor. So, I tried to apply a property node to a graph with just one cursor. In particular, I tried to access the x-value of the cursor. When I then run the vi, I get error 1055 "Object reference is invalid". I had hoped to construct the property nodes for one cursor, then add another cursor, and attach property nodes to it. There does not seem to be a way to use property nodes to specify which cursor I am accessing. I have tried a property node with two properties: select cursor as an input, and x-value as an output. The "select cursor" property input seem to have no effect at all.
Is there an example vi for programmatically extracting information from graph cursors?
Joe Rudmin
Solved!
Go to Solution.

Joe,
Please take a look at my screen shot as a reference for getting the x position for a cursor on a graph object. I hope this helps.
Right clicking on the graph and hover over create then property node, cursor, cursor position then cursor x. This should create a property node that gives the position of the cursor on the graph. I understand you are trying to use multiple cursors but this will get you started.
Kyle Hartley
RIO Product Support Engineer
National Instruments
Attachments:
cursor position.JPG ‏42 KB

Build error after upgrading from 8.2.1 to 8.5 "Error 1055 occurred at Invoke Node..."

After upgrading to 8.5, I'm getting the following error when trying to build an EXE:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1055 occurred at Invoke Node in AB_Source_Library.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: Object reference is invalid.
I have been building this application for both Windows and Mac OS, and I even get the same error when building the .app on an Intel Mac.
Things that I've already tried:
* Mass-compiling all my code
* Created the project from scratch
* Enabled each panel of the "diagram disable structure" one at a time and compiled again
Any ideas?

Hi Travis,
Ben’s advice if definitely the best place to start. Error 1055 is a very general LabVIEW error for “Object reference is invalid.” The cause is usually a bad install where important LabVIEW function aren’t placed in the right directory or aren’t installed at all.
Charlie M. CLD

Error reading node property?

I'm using Premiere Pro CS6, editing a 10 minute sequence using H.264 clips in .MOV containers. This morning I have been applying the Fast colour corrector, warp stabiliser and highlight/shadow adjustment to the clips. A small red box with a white X has appeared in the lower right corner with the message "error reading node property". What does this mean and how do I rectify it?
Thanks for your help
This error doesn't appear to refer to any specific clip, and there is no more information given. Premiere seems to be running fine, except for occasional crashes, which I think are caused by adding the warp stabiliser to too many clips at once.

Wish I had the answer, but I do not. I am getting the same message, yet all seems well , no crashes (Win 8)

REL 12 GETTING ERROR WHEN PRINTING A BARCODE USING THE GRAPH TOOL

Hi,
We are getting the following error:
REP-34551: Oracle Graphics Graph: is deprecated. See help for more information.
Environment variable ORACLE_GRAPHICS6I_HOME not set
REP-1811: Error while generating a graph.
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP-1811: Error while generating a graph.
So please advice.
Details of the DEV instance.
RDBMS : 11.2.0.3.0
Oracle Applications : 12.1.3
Thanks in advance.

Thanks for replying but I m no longer under the warranty and the CDs don't have any scratch at all. I guess it's problem with the hard drive. But it's there way to diagnostic and repair the hard drive without sending back to the manufacture??Should I just replace the hard drive?Is it ok to replace the hard drive with different band and then use the recovery disc?I also want to know what cause the hard drive to fail??

"XSL Error: Cannot use a DTMLiaison for a input DOM node"

This code:
Writer writer = new StringWriter();
XSLTProcessor processor = XSLTProcessorFactory.getProcessor();
// Note: event.getDocument() returns a
// org.apache.xerces.dom.DocumentImpl
// sourced from xlms.jar
processor.process(new XSLTInputSource(event.getDocument()),
new XSLTInputSource(new FileReader(GDS_XSLT_STYLESHEET)),
new XSLTResultTarget(writer));
Gives this stacktrace:
XSL Error: Cannot use a DTMLiaison for a input DOM node... pass a weblogic.apache.xalan.xpath.xdom.XercesLiaison
instead!
XSL Error: SAX Exception
weblogic.apache.xalan.xslt.XSLProcessorException:
     at weblogic.apache.xalan.xslt.XSLTEngineImpl.error(XSLTEngineImpl.java:1756)
     at weblogic.apache.xalan.xslt.XSLTEngineImpl.error(XSLTEngineImpl.java:1648)
     at weblogic.apache.xalan.xslt.XSLTEngineImpl.getSourceTreeFromInput(XSLTEngineImpl.java:876)
     at weblogic.apache.xalan.xslt.XSLTEngineImpl.process(XSLTEngineImpl.java:600)
1. All XML/XSLT classes are being sourced from weblogic.jar or xmlx.jar
2. Both jar files come from the WLS installation (WLS6.0 + SP2)
3. There are no other XML class providers on my class path
4. This is a standalone application, not running within WLS; I'm using weblogic
jarfiles here purely so I use the same XML implementation both inside and outside
WLS. Is this a sensible approach?
Any help, anyone?

All works fine in WLS6.1, with this extra code:
System.setProperty("javax.xml.transform.TransformerFactory",
"weblogic.apache.xalan.processor.TransformerFactoryImpl");
(or you could use -D)
No longer concerned; we've moved off WLS6.0
"Simon Spruzen" <[email protected]> wrote:
>
Interestingly, expanding the code to (the very verbose):
Document sourceDocument = event.getDocument();
XSLTProcessor processor = XSLTProcessorFactory.getProcessor();
StringWriter source = new StringWriter();
XMLSerializer sourceSerializer = new XMLSerializer(source, new OutputFormat(sourceDocument));
sourceSerializer.asDOMSerializer();
sourceSerializer.serialize(sourceDocument.getDocumentElement());
StringWriter output = new StringWriter();
processor.process(new XSLTInputSource(source.toString()),
new XSLTInputSource(new FileReader(GDS_XSLT_STYLESHEET)),
new XSLTResultTarget(output));
(i.e. document -> string -> transform -> string)
works just fine, but this code is far too long-winded for me to be happy
with.
(Note that one of XSLTInputSource's ctors does take a Node, so I'm assuming
that
it should be perfectly safe to pass a Document here)
(Note also, that for various reasons at the moment, using JAXP's transformer
factory
is difficult for us)
"Simon Spruzen" <[email protected]> wrote:
This code:
Writer writer = new StringWriter();
XSLTProcessor processor = XSLTProcessorFactory.getProcessor();
// Note: event.getDocument() returns a
// org.apache.xerces.dom.DocumentImpl
// sourced from xlms.jar
processor.process(new XSLTInputSource(event.getDocument()),
new XSLTInputSource(new FileReader(GDS_XSLT_STYLESHEET)),
new XSLTResultTarget(writer));
Gives this stacktrace:
XSL Error: Cannot use a DTMLiaison for a input DOM node... pass a weblogic.apache.xalan.xpath.xdom.XercesLiaison
instead!
XSL Error: SAX Exception
weblogic.apache.xalan.xslt.XSLProcessorException:
     at weblogic.apache.xalan.xslt.XSLTEngineImpl.error(XSLTEngineImpl.java:1756)
     at weblogic.apache.xalan.xslt.XSLTEngineImpl.error(XSLTEngineImpl.java:1648)
     at weblogic.apache.xalan.xslt.XSLTEngineImpl.getSourceTreeFromInput(XSLTEngineImpl.java:876)
     at weblogic.apache.xalan.xslt.XSLTEngineImpl.process(XSLTEngineImpl.java:600)
1. All XML/XSLT classes are being sourced from weblogic.jar or xmlx.jar
2. Both jar files come from the WLS installation (WLS6.0 + SP2)
3. There are no other XML class providers on my class path
4. This is a standalone application, not running within WLS; I'm using
weblogic
jarfiles here purely so I use the same XML implementation both inside
and outside
WLS. Is this a sensible approach?
Any help, anyone?

Application builder error 1055

ed. cross-post: http://lavag.org/topic/18047-application-builder-error-1055/
Hello everyone
I have a big problem with building applications lately. The build is running fine until the end, when it throws:
Error 1055 occurred at Property Node in VISL_findDependentVISvr.vi->VISL_findAndProcessVISvrList.vi->VISL_detectAndCopyVISvr.vi->AB_Engine_Copy_CustomIOServer_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: Object reference is invalid.
Has anyone seen this error in app builder? Does anyone have any idea how can I resolve this problem?

Lennard, Valko
I'm using LV 2013 f2. Let me give you some more details and... The story how I fixed it:
The project is pretty big (~1500 VIs) and highly object-oriented (~300 classes). It has RT (PXI) and PC part. Some of the classes are shared between PC and RT. The problem with build was present only on PC - build for RT was ok.
I had DSC module installed, but it was not used in this project at all. Despite that, when I found information from Lennards link, I've tried to build it using "Enable Enhanced DSC Run-Time support". It didn't help. I started to wonder if the sharing of classes between RT and PC has something to do with the problem. So I refactored the project, splitted it into two projects (one for PC, one for PXI) and reduced number of shared classes (especially some specific classes, which implement "threads"). Afterwards, the build could be done just fine, but only in those refactored projects.
Now for the plot twist: before refactoring, I've tried to build the project on another computer. It was build without any problems! So I started to look for the differences. First of all, just before the build I've updated one of our internal libraries in VIPM and changed its name - so it was my main suspect (I needed to update dependencies in project as the change of VIPM package name changed it folder in vi.lib). This + disconnecting code from VIs and I though that I've just found another way of destroying LV compiler completely. Still, I couldn't fix it in any way...
As per Valko suggestion I've uninstalled DSC module completely. Once again - my project does not explicitly use this module at all! Removing the module didn't broke anything in the project. And guess what? The build was done without problems! I've even tried to do this build again on the code revision before refactoring, and the build was done!
tl;dr: REALLY NI!!?!? REALLY!? YOU'VE BROKEN SOMETHING IN THE MODULE WHICH I DON"T EVEN EXPLICITLY USE AND MADE ME LOSE FEW DAYS OF WORK JUST TO FIND IT OUT? REEEEAAAAALYYYYY!?

Error 1055

I am a project on target CRio 9074 composed by FPGA_vi, RT_vi and a Windows_vi where i read the network published variable that set in RT_vi.
I use property nodes in RT subvi to set the value in a cluster. The reference is an input to subVi that arrived by a Main_RT_vi.
Within the Labview design environment everything works well. However when running the built application I see error 1055.
Why is this error happening?

Hi RIPosa,
Property nodes in the RT environment are typically not suggested unless you're working with a front panel connection. Typically, when building into a RTEXE, there is some optimization to remove front panels which can lead to this particular error. I would suggest taking a look at the list of unsupported features in LabVIEW RT for further explanation and more information. In short, to avoid this error don't use property nodes if possible.
Tim W.
Applications Engineering
National Instruments
http://www.ni.com/support

Passing data to main vi's and error 1055

Hello! I am perplexed by an error that I am getting in LV 8.2 and I would certainly appreciate any insight as to why this might be occurring. I have searched through this forum, but did not find any answers that seemed to be particular to this problem.
All I want to do is pass data from a sub vi to a main vi, while being able to see that data execute in the sub-vi (i.e. from the main vi front panel). One way that I learned to do this is to have a control refnum object on the sub-vi wired to a property node and write the data property. I then create a reference to a control in the main vi. It is the refnum wire from the sub-vi that is then wired to the reference to the control that I wish to update. This however only works for a given VI (executing from the sub-vi and/or the main) about 50% of the time. When it does not work, I get error 1055: Object reference is invalid. This error is originating from the property node in the sub-vi. I can run the sub or main vi again, without changing anything, and it will run fine. I do, however, seem to see the error less often when running from the main vi.
I have tried changing the refnum object in the sub-vi from the generic control class (default) to the exact type of control that I am passing data into in the main vi (in this case a cluster). Both variations seem to execute with and without the error consistently.
Thanks in advance for any replies!
Attachments:
sub-vi.JPG ‏67 KB
main-vi example.JPG ‏17 KB

If you can make it strictly typed I would use that. Then you will know if you are wiring the correct data into the value property node. I am not sure what to say about the error. It seems to me that you are doing it the way I would. One thing you could try is to test the refnum first with a comparision "not a number/path/refnum?". This wont solve the error but maybe you can catch it before it happens. Maybe your main VI is closing the control reference befor the sub VI is finished? From your pics I don't see how this would happen.
orbit wrote:
Everything seems to work fine when running from the main vi, but still gives an error when just running the sub-vi. This behavior is fine as long as I don't get the error in the main vi as I did before!
I just re-read this part above. Are you trying to run the subVI alone? You will for sure get an error 1055 because you didn't pass in a valid reference. This valid reference is generated from the main VI (it is possible you may not get the error if the main VI was run once and still in memory because the subVI will still hold the mainVI's control refnum).
If you want to run the subVI without running from the main VI you will have to handle the invalid refnum or you will get the error.

RT Communication Wizard error 1055

When i use the Real Time Communication Wizard i get this message: Error 1055 occurred at Property Node in RTCW Script NPL (TCP).vi->RTCW Wizard.vi
Whats wrong??? I get this Error in every VI but i´ve already re-installed RT

This is a known and solved issue that is documented in the NI knowledgebase. Please follow this link.
Best regards
Jochen Klier
National Instruments Germany

Error 1055 using XY graph's node property

Similar Messages

Maybe you are looking for