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

Similar Messages

I'm getting error 1055

I'm getting an error 1055 in the report generation - my Labview ver is 8.6.1
I don't know what to do here to resolve this
I thank for your help.
Dana
Solved!
Go to Solution.
Attachments:
err vi.png ‏71 KB

thank you very much that works !!

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.

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

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

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

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.

Error 1055 OA_Get Max Axis Dispaly Value.vi - OUT Orbit Plot (Unfiltered).vi

Hello to Everyone,
I am trying to use OA Orbit.vi, but i having trouble, this error message is displayed: Error 1055 OA OA_Get Max Axis Dispaly Value.vi -> OA Orbit Plot (Unfiltered).vi. Is there any solution?
LabVIEW 8.5 is used.
The way how is connected, followed a LabVIEW Order Analyses Toolkit User Manual:
- signal from tachometer is input to OAT Analog Tacho Procces.vi, output Speed Profile is input for Oat Orbit Plot,OAT Convert to Even Angle Signal.vi
- signal from two proxymity probes is scaled to EU units with SVL Scale Voltage EU.vi
- scaled signal is input to OAT Convert to Even Angle Signal.vi to get Even Angle Signal
- Even Angle Signals (from two sensors) is input to Oat Orbit Plot.vi
- output Even Angle Position Info from OAT Convert to Even Angle Signal.vi is connect with Oat Orbit Plot.vi
Thanks.
Best rigards,
Nandor Spacek

Hi Nandor,
Welcome to the NI forums!
I am not sure that I fully understand your vi based on your description, so I would kindly ask you to create a VI Snippet from the code in question, and embed it in your reply forum post as a picture. This is the recommended best practice when discussing code. Alternatively you can always attach the .vi itself to your post.
Your LabVIEW version 8.5 is fairly dated, did you make sure that you are using a compatible version of the Order Analysis toolkit? You can check the versions of your software in MAX, or by generating a MAX report.
Also, please post a screenshot of the error message you are getting. Sometimes you can also just hit Ctrl+C when you have the error message active, and that will copy the error message to the clipboard so you can post it here.
Best Regards,
T Simon
National Instruments
Applications Engineer
Certified LabVIEW Developer - Certified TestStand Architect

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

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.

Error 1055 occurred at Property Node, only the FIRST TIME I run the VI

hi !
I'm managing some object properties with 2 subVIs,
so I send to the first one a number and a cluster which contains the objects references, so that it controls the "visible" property depending on the number,
and I send to the second one the previous cluster and an other cluster which contain the objects data, so that it controls the data depending on some parameters.
VI is better than explaination, so find it attached !
at the first time you'll run it, the error occurs, so click "stop" button, and run it again, no error, and you'll understand the way it works.
To fond the error again, just close it completely and re-open it.
(I built an example VI as close as possible to my real VI, and I get the same error, so I attached only the example)
hope you'll understand (if no I can explain better)
thanks a lot.
Attachments:
tests erreurs.zip ‏57 KB

yoz'st wrote:
smercurio_fc a écrit :
You have to write to the control/indicator the local variable points to.
sorry but I don't really understand this... (I'm french).
A local variable points to a control or indicator. To "initialize" it you have to write a value to it. Or, you can set the value of the control/indicator to a default value.
I tried to use globals, but the same error occurs...
Of course it will. Because you're not understanding that you have a race condition. http://en.wikipedia.org/wiki/Race_condition

WORD Error message -- Report from Template

Hello everyone,
I try to generate a "Report from Template" with transaction CG03.
I can select the generation variant and the parameter values in the next two pop-ups.
WORD is starting but then there is the error message:
"Word cannot read this document. Maybe it is corrupted. Try the following:
- open and repair the file
- open file with repair-textconverter".
This message is a translation from german to english so the correct messagt might differ from this.
When I look at my frontend PC in the local settings I see that the respective files are written, but I can´t open them.
This problem started two days ago out of nowwhere.
Additional information: Visual Basic pops up after the error message is closed with "runtime error '1055'.
A debugger is opened and this is the content of the window:
Private Sub TmpDDE()
Dim Template
WordBasic.FileOpen "C:DOKUME1chgiLOKALE1TempRehsfil0.WWI"
WordBasic.FileTemplates Template:="C:ProgrammeSAPFrontEndsapguiwwiwwi.dot"
WordBasic.Call "wwiES.S", "S", ""
End Sub
Any ideas?
Thank you in advance for your help!!!!
Best regards,
Christoph
Edited by: Christoph Giehl on Nov 25, 2010 1:04 PM

Hello Christoph
any change happened on your client? New Windows version? New Word Version? New WWI Version installed? Did you manupulated Standad Dot path etc.? Did you change Standard.dot of Word?
Can you open in cg54/cg50 any document (ready, released or historic) without a problem and the problem is related only to "report from template"?
During WWI process a number of files are passed on to your client. Can you use Wordpad to open the files? I am not sure but I believe per WWI document there should be something like 4 or 5 documents in your local WWI path. One containing the data, one containing the template and some others (named something like resfil, lesfil etc.).
An error like you described is normally related to one of the above mentioned changes. Can you use "Report from template "regarding the same spec, same genvariant same language with a different client without a problem => then it is clear you have a local problem
With best regards
C.B.

LV FPGA XYmultiplot error

Hi guys,
First of all, this is a bug report, and not a question. But I wasn't sure where to put this on the website or forum so I put it here. If this does not belong on the forum, please feel free to remove this post and send me a message where I can put this in the future.
This is the error I get when using a multiplot XY-graph:
An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
Error 1055 occurred at Property Node in nirviObjectToResholderInfo.vi->nirviMakeLineInfoSubTagsForDiagramObjectRef.vi->nirviMakeTreeLineInfoTagForDiagramObjectRef.vi->nirviDiagramObjectError.vi->nirviSplitRegisterListBySize.vi->nirviPrintOneClkFramework_bushold.vi->nirviGetImplementation___busholdModGen.vi->nirviGetImplementation___busholdModGen.vi.ProxyCaller
Possible reason(s):
LabVIEW: Object reference is invalid.
and the code you'll find in the attachment. The issue is solved when I use 2 separate waveform charts for the two signals instead of 1.
Best regards,
Dries
Attachments:
lv code xy-multiplot.png ‏17 KB

Hello Dries,
Thank you for taking the effort and bringing this to our attention.
The error you were seeing is not a bug. It's the build array function in the screenshot which is trying to create one big array which most likely does not fit the FPGA.
Depending on the size of the FPGA on your device, the maximum array size will be limited accordingly.
If the workaround which you found yourself doesn't suffice, decreasing the total size of the array will also most likely make the error go away.
Please let me know if any questions remain.
Kind Regards,
Wouter
National Instruments, Northern Europe

Error 1055

Similar Messages

Maybe you are looking for