Jump to content

gradi3nt

Members
  • Posts

    2
  • Joined

  • Last visited

LabVIEW Information

  • Version
    LabVIEW 2012
  • Since
    2012

gradi3nt's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I haven't tampered with anything. Unfortunately I didn't notice what action caused the VI to go from working to broken since I made several changes to my program before testing it. My guess is that it was caused by having a build text with many parameters that have been shuffled around, deleted or added (sorry, that's pretty vague). I will pay closer attention in the future, since I have had some mysteriously broken build text VIs in the past too (I just found out today you can convert to normal VI and inspect the code so I can't prove this issue has ever happened to me before).
  2. I couldn't figure out why this build text express vi stopped working after I changed its parameters around a bit. The only error message was that the subVI isn't executable. I decided to convert the expressVI to a normal VI to inspect it (after backing up the original file because the conversion is irreversible). Upon inspection I found a broken wire floating around. Where did that come from? Is this just a bug in the expressVI code? Is there a way I can get rid of it without irreversibly converting the expressVI to a normal VI? Removing the rogue broken wire fixes the error and the VI is able to run.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.