Elapsed Time Express VI Occasionally Missing

[Jacobson-ni]

Here's just a bit of other strangeness. Once you drop the express to fix the missing one, it seems like they are linked somehow.

[Hooovahh]

Just got an email remind from the forums asking if this is solved.  Anything else from NI that I should try?  Anything else I can do to help isolate and resolve this issue?  And thank you Jacobson that just adds so much more to the mystery.

[rsmayer]

Hi Hooovahh,

I spent some time looking into this and brought it up with a lot of my colleagues. I can't say for sure what has caused this issue, and we have not seen this type of behavior before. It might be an issue with your installation of LabVIEW. I wish I could be of more assistance, but we could not replicate your issue on our end (without using your attached .vi).

-Ryan

[JÞB]

Here is another clue.

Using your broken vi, drop Almost ANY Express.vi on the BD.  That crazy missing vi is looking for missing vi "0"  The only one I found that does not link to "0" is Express Formula Node.  

[Hooovahh]

Are you suggesting the corrupt install of LabVIEW then corrupts the VI?  Because how else would you explain the fact that this behaves this way on multiple computers (including your own).  I can't be certain but I think this has happened on more than just one PC.  I usually only develop on my own PC but some times I will develop on the industrial PC the software is intended for.  I know I've committed code from my development machine and had this issue on both the development, and then the industrial PC (after pulling in the latest from SCC).  But I think this has happened in the reverse where I commit on the industrial PC, then pull it to my development machine with SCC and had it missing there too.  To me that suggests that it isn't linked to a particular installation.

Regardless I'll try a repair of LabVIEW if I get some time.

[rsmayer]

Whoops, I thought you were only having this problem with VIs developed on your one single PC. Having this issue on multiple PCs definitely makes it more interesting. I know someone else in the thread mentioned it already, but are there any unique modifications or settings you have on both machines?
-Ryan

[Hooovahh]

Lots of settings are shared, the two PCs are setup very similarly because I jump back and forth from developing on one to the other.  I didn't copy the LabVIEW.INI from one machine to the other but most of the common settings were set by a VI that is ran as part of the reuse installation.  This is done with a VIPC package using VIPM.  It installs OpenG, MGI, internal reuse, and several other tools.  I generally leave existing files alone but there are a few exceptions.  A couple of QuickDrop functions are edited through scripting on install of our VIPC, but other than that all existing files shouldn't be touched.  Both PCs are running Windows 7 x64 but were not part of any kind of image, and even LabVIEW and NI products were installed separately.  One using the DVD media, one from a network install which was a dump of the DVDs.  Both share the majority of the same tookits including RT, XNet, DAQmx, and VISA.

[JÞB]

---

@Hooovahh wrote:

Lots of settings are shared, the two PCs are setup very similarly because I jump back and forth from developing on one to the other.  I didn't copy the LabVIEW.INI from one machine to the other but most of the common settings were set by a VI that is ran as part of the reuse installation.  

---

AH HA!

Lets just try the old 8-Ball

~~~Yo! 8-Ball... Wake up!  When Hooovahh looks into his ini files will he find inconsistent settings for Configure Express VIs Immediately?~~~

A: No Way! That would suck if he saved an un onfigured vi on one machine and opened it on another that knows it had to be configured immediately!  

[Hooovahh]

Nice guess Jeff.  It's not right but is a good guess.  I have Configure Immediately on my main development machine (which created the VI I posted earlier).  I don't have access to the deployment PC at the moment because...it's deployed, but I'm pretty certain I didn't change that setting.  I actually prefer configure immediately.  Even so if I don't configure it I'd assume it just defaults to some values right?

EDIT:  Just tested in my 2016 (my 2015 is doing stuff).  If you don't configure the Elapsed Time express VI it defaults to 1 seconds and with auto reset on.

[JÞB]

Well, you definitely have an "Express.vi Shell" for lack of a better term.  I really can't understand how even a "From DDT" Node can get sucked into the shell.

Heck, even a new blank Express.vi fills in the shell