LAVA Forums Buy cool LAVA gear Forums RSS Feed

Welcome Guest ( Log In | Register )

> Related links

Check out the related Code Repository Files or visit the LabVIEW Wiki Development Environment Portal


Tags
(This content has not been tagged yet)
 
Reply to this topic Start new topic
> Broken code with no broken arrow., Strange bug?
Michael_Aivaliot...
post Nov 16 2007, 12:37 AM
Post #1


Confucius say: Crowded elevator always smell different to midget
Group Icon
*****

Admin
Posts: 2402
Joined: 13-October 02
From: Planet Earth
Member No.: 2
Using LabVIEW Since:1994
LV:8.5 ,8.2.1 ,7.1.1
Greece Canada United States My Blog My Gallery


Not sure what causes this but I've experienced this several times lately.

I run a toplevel VI several times and somewhere I get an error on the error cluster. So I decide to start debugging by opening up the subVI's. When I open one of the subVI's I notice that it has a broken run arrow and now I also notice that my toplevel VI has a broken run arrow. How is it possible for LabVIEW to run broken code? The only thing I can think of is that the broken code has not propogated to the current running application instance until I open it up. Not sure why however since I only have one instance. I have the project environment open too.

--------------------


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
Ad
post Nov 16 2007, 12:37 AM
Post #















Tags
(This content has not been tagged yet)
Go to the top of the page
Quote Post
jdunham
post Nov 16 2007, 01:42 AM
Post #2


Very Active
***

Member
Posts: 230
Joined: 6-March 05
From: Mountain View, CA
Member No.: 1764
Using LabVIEW Since:1994
LV:8.5 ,. ,.
United States us_california Nothing Selected


Do you have a conditional disable structure on the diagram or in a subvi? If you have changed the conditional symbol definition in your project, then the same VI could definitely be working inside the project but broken outside of it.


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
Michael_Aivaliot...
post Nov 16 2007, 07:31 AM
Post #3


Confucius say: Crowded elevator always smell different to midget
Group Icon
*****

Admin
Posts: 2402
Joined: 13-October 02
From: Planet Earth
Member No.: 2
Using LabVIEW Since:1994
LV:8.5 ,8.2.1 ,7.1.1
Greece Canada United States My Blog My Gallery


QUOTE (jdunham @ Nov 15 2007, 05:42 PM) *
Do you have a conditional disable structure on the diagram or in a subvi? If you have changed the conditional symbol definition in your project, then the same VI could definitely be working inside the project but broken outside of it.

No, it's not that.

--------------------


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
silmaril
post Nov 16 2007, 04:45 PM
Post #4


Very Active
***

Member
Posts: 91
Joined: 7-March 07
From: Munich
Member No.: 7932
Using LabVIEW Since:2001
LV:8.6 ,8.5.1 ,7.1.1
Germany ger_bavaria Nothing Selected


Did you try Ctrl-Shift-Run on your top level VI?
Was the run arrow still unbroken after this?

--------------------
The saddest aspect of life right now is that science gathers knowledge faster than society gathers wisdom.
Isaac Asimov


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
Michael_Aivaliot...
post Nov 22 2007, 01:34 AM
Post #5


Confucius say: Crowded elevator always smell different to midget
Group Icon
*****

Admin
Posts: 2402
Joined: 13-October 02
From: Planet Earth
Member No.: 2
Using LabVIEW Since:1994
LV:8.5 ,8.2.1 ,7.1.1
Greece Canada United States My Blog My Gallery


Well, it happened again. Check this out. There's a broken wire on the diagram but the arrow's intact.
Running the VI crashes LabVIEW. thumbdown.gif
Attached thumbnail(s)
Attached Image
Attached Image

 

--------------------


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
Val Brown
post Nov 22 2007, 03:07 AM
Post #6


Extremely Active
****

Member
Posts: 399
Joined: 26-March 06
From: Victoria, BC Canada
Member No.: 4568
Using LabVIEW Since:1998
LV:8.6 ,8.5.1 ,8.2.1
Canada United States Nothing Selected


Are you working in XP or Vista?

--------------------
The power of NeuroCARETM


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
Michael_Aivaliot...
post Aug 20 2008, 06:15 AM
Post #7


Confucius say: Crowded elevator always smell different to midget
Group Icon
*****

Admin
Posts: 2402
Joined: 13-October 02
From: Planet Earth
Member No.: 2
Using LabVIEW Since:1994
LV:8.5 ,8.2.1 ,7.1.1
Greece Canada United States My Blog My Gallery


Here's a video that shows how you can have a broken VI on the diagram of a non-broken VI. No I'm not using a disable structure. If I click on the run arrow of the caller it breaks and shows the error list. The arrow then stays broken.
Attached File(s)
Attached File  broken_fail.mov ( 1.87MB ) Number of downloads: 40
 

--------------------


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
Aristos Queue
post Aug 20 2008, 06:42 AM
Post #8


LV R&D Envoy
*****

NI
Posts: 1273
Joined: 15-August 06
From: Austin, TX
Member No.: 5877
Using LabVIEW Since:2000
LV:8.6 ,6.0 ,.
United States Nothing Selected Nothing Selected My Gallery


You have filed a CAR, right?

--------------------
"A VI outside a class is a gun without a safety. Data outside a class is a target."
--- A message from LabVOOP R&D


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
neB
post Aug 20 2008, 12:36 PM
Post #9


Certified Kool-Aid Kid
*****

Premium Member
Posts: 1188
Joined: 6-December 02
From: Pittsburgh PA USA
Member No.: 29
Using LabVIEW Since:1998
LV:7.1 ,. ,.
United States Germany Nothing Selected


QUOTE (Aristos Queue @ Aug 20 2008, 02:42 AM) *
You have filed a CAR, right?


Have you ever tried to file a CAr without being able to reproduce the issue on demand?

I have seen a couple of those myself, also working LabVIEW 8.5. I'm not using globals so if its the same bug I have seen it is not due them. THe other observation that I can add is that a really fuzzy general type observation. I would swear (if pressed) that code changes are not propagating to all of the VI's that are not open. I say this because I work with a tree.VI open and after amking changes (but before running) I save everything (from tree.vi save all) then close the tree.vi. Backup then re-open and test the code. WHen closing the tree.vi, I see VI's that want to be saved. As a result I ahve resorted to an old habit of opening and closing the tree a couple of times to make sure all of the changes get propogated.

Just reporting what I have ben seing.

Ben


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
hfettig
post Aug 20 2008, 03:27 PM
Post #10


Very Active
***

Premium Member
Posts: 91
Joined: 12-November 04
From: Gatineau, Quebec, Canada
Member No.: 1022
Using LabVIEW Since:2001
LV:8.6 ,8.5.1 ,.
Canada Germany Nothing Selected


Hey Mike,

I think I found your Broken Arrow. Somehow it found its way into my VI. tongue.gif

Attached Image


I seem to be experiencing the opposite of your problem. I have a broken arrow and 0 errors and warnings listed in the error list. wacko.gif

Cheers,
Heiko


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
Michael_Aivaliot...
post Aug 22 2008, 08:14 AM
Post #11


Confucius say: Crowded elevator always smell different to midget
Group Icon
*****

Admin
Posts: 2402
Joined: 13-October 02
From: Planet Earth
Member No.: 2
Using LabVIEW Since:1994
LV:8.5 ,8.2.1 ,7.1.1
Greece Canada United States My Blog My Gallery


QUOTE (neB @ Aug 20 2008, 05:36 AM) *
Have you ever tried to file a CAr without being able to reproduce the issue on demand?

I agree. Reporting this to NI is a futile exercise. Not reproducible at all.
QUOTE (neB @ Aug 20 2008, 05:36 AM) *
I would swear (if pressed) that code changes are not propagating to all of the VI's that are not open. I say this because I work with a tree.VI open and after amking changes (but before running) I save everything (from tree.vi save all) then close the tree.vi. Backup then re-open and test the code. WHen closing the tree.vi, I see VI's that want to be saved. As a result I ahve resorted to an old habit of opening and closing the tree a couple of times to make sure all of the changes get propogated.

Ben, there's a thread for this issue here.

--------------------


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post

Reply to this topicStart new topic

 




Time is now: 7th January 2009 - 09:13 PM