LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

property node broken lvoop

This only started happening recently, no code changes had been implemented leading into this issue.

 

When I start my program it will show a broken arrow, after digging to the cause I find that the property node for a few of my objects (I'm utilizing the LabView object oriented features) are broken.  Please see image below...

 

BrokenPropertyNode.PNG

When I click on one of the broken property nodes it shows that all the properties are still available (see below)

StillAvailable.PNG

If I then select a different property then what is currently programmed and then switch it back the property nodes (all of them in the VI) become fixed and the VI functions fine (see below).  However, even if I save the VI and project which contains it, the next time that I open this VI from scratch (completely exit the project and open again) the problem comes back and I have to repeat the process.  Also, it only appears that this behavior is occuring in one VI in my project even though I use property nodes throughout on the same and other objects.

FixedPropertyNode.PNG

 

Thanks for any help you can give in advance,

 

Randy

 

PS I'm running on Windows 7 with LV2010SP1.

0 Kudos
Message 1 of 10
(4,094 Views)

Randy,

 

*deleted*

 

thanks,

Norbert

 

EDIT: Have you tried to perform a force compile once the node is broken? (Pressing CTRL and press the Run VI button using the mouse)

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 2 of 10
(4,067 Views)

Are you sure that nothing has changed from the last time that the VI worked correctly? Not even something insignificant? The reason I am asking is because it is a little difficult to troubleshoot the issue under those conditions. It is very unlikely that a VI that is working fine all of the sudden stops working for no apparent reason.

0 Kudos
Message 3 of 10
(4,050 Views)

@PedroMunoz wrote:

Are you sure that nothing has changed from the last time that the VI worked correctly? Not even something insignificant? The reason I am asking is because it is a little difficult to troubleshoot the issue under those conditions. It is very unlikely that a VI that is working fine all of the sudden stops working for no apparent reason.


LVOOP, need I say more?

 

What is more likely is the action to "fix" the code is not being saved and that screams BUG in my book.

 

At this point I think the original poster should pack-up a backup of the code so the problem can be repeated and passed to R&D.

 

But that is just my opinion,

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 4 of 10
(4,048 Views)

Hi there,

 

I got the same problem as Redrabbit reported. I am also running Windows 7 (32 Bit) and LabVIEW 2010 SP1.

To get my property nodes back to work, I only place a new object on the block diagram if the described situation occurs. This object could be anything...a simple add function or something else. Immediately after that, the property nodes get back in a normal state and I delete my add.

Not the best way to do it, but better than nothing.

 

The problem is not reproducable on my site...it occurs randomly.

 

Because of further problems with the property nodes on classes (heavy crashes without message) I replaced them in most cases with the accessor VIs. This seem to work more stable but is not that cool for the coding style. I'd like to use the property nodes, but I have no time for searching the crashing error. Smiley Frustrated

 

I read a thread on Lava.org about problems with the oop property nodes, but that was already 2010. Does anyone know if the issue is fixed in 2011?

Here's the link to the lava-thread: Lava-Forum

 

Thanks

 

gibbi

Message 5 of 10
(4,030 Views)

@Gibbi wrote:

...I read a thread on Lava.org about problems with the oop property nodes, but that was already 2010. Does anyone know if the issue is fixed in 2011?

Here's the link to the lava-thread: Lava-Forum

 

Thanks

 

gibbi


 

Thank you Gibbi!

 

NI,

 

Can you please investigate the various CAR's posted in the LAVA thread and tell us if there is an active CAR for this issue?

 

Thank you,

 

Ben

 

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 6 of 10
(4,022 Views)

Nothing was changed...not even something insignificant.

0 Kudos
Message 7 of 10
(4,014 Views)

I have not tried this (forcing a compile, I remember doing this in the past on other issues however), I'll give it a try and post how it goes.

 

Thanks!

0 Kudos
Message 8 of 10
(4,013 Views)

I tried to force a recompile and unfortunately it didn't work.  It would correct the immediate issue but once I save, close and reopen the VI the problem returns.  Any other suggestions would be appreciated.

 

Thanks,

Randy

0 Kudos
Message 9 of 10
(3,998 Views)

@Redrabbit wrote:

I tried to force a recompile and unfortunately it didn't work.  It would correct the immediate issue but once I save, close and reopen the VI the problem returns.  Any other suggestions would be appreciated.

 

Thanks,

Randy


1) Backup what you have.

 

2) Call NI and start a Service request and tell them you have a bug with LabVIEW.

 

3) When you talk to the app engineer tell them you have cod that demonstrates the problem discussed in this thread.

 

4) Tell them how to reproduce the error.

 

5) Let us know what the CAR (Corrective Action Report) number is.

 

6) Wait.

 

Ben

 

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 10 of 10
(3,989 Views)