LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Type-def'd cluster constant on diagram is not allowed!

Error message is "Could not determine data types of all wires in this VI.
 
See attached VI and type-def.
 
 
Changing the cosntant to a control clears the error.
 
Changing it back, recreates the error message.
 
Note:
The VI started as functional global but when this error was noticed we deleted everything except the constant.
 
Ben
 
 

Message Edited by Ben on 03-31-200611:40 AM

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

If you force a re-compile of the VI (ctrl-shift-click Run arrow), the problem goes away.  Also, it appears to be fixed in the next version of LabVIEW as well (i.e., the VI does not open broken).

-D

0 Kudos
Message 2 of 7
(3,430 Views)

Hi Darren,

That worked at this end but...

When you say "next version" is that 8.0.1 or are you talking about the un-released LV 8.1?

If you are talking about LV 8.1 then is there a CAR for this issue?

I ask becuase I have heard of bugs being fixed in the "next version" before the release, only to find out it was later "un-fixed".

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 3 of 7
(3,419 Views)
Personally I don't see the problem go away when I force recompile the VI, and I see an internal error in datamgr.cpp warning when you change it to a control.  I will add that it appears to be fixed not only in "the next version" but also in the already-released 8.0.1.
0 Kudos
Message 4 of 7
(3,419 Views)

Now I am really confused. Smiley Surprised

Well at least you have been warned.

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 5 of 7
(3,414 Views)

I didn't try it in 8.0.1, so that's good news that it appears to be fixed there.

Jeff:  When you force re-compiled, did you do Ctrl-Shift-click to force recompile all?  That's what I had to do to get it to work...just a force recompile of the VI (Ctrl-click) did not work.

-D

0 Kudos
Message 6 of 7
(3,404 Views)

Hey Ben,

Sorry for the confusion, I may have been running in a debug version of LabVIEW 8.0 that shows warnings at a higher granularity than the release build.  These are things that allow us to catch unexpected scenarios during development, but are situations that aren't catastrophic to LabVIEW's execution such that a crash would occur.  I'd guess that's why you didn't see the warning.

And Darren - good point, I'd read your first message too quickly - I didn't include SHIFT on my recompile, so the CTL file probably wasn't getting re-compiled and therefore the problem wasn't going away.

Take care,

Jeff

Message Edited by Jeff B on 03-31-2006 02:08 PM

0 Kudos
Message 7 of 7
(3,391 Views)