Express Vi "Unable to view properties"

[ejoseph]

I'm trying to create an express vi, but when I go to drop it on a block diagram I get the error: "Unable to view properties".  I've seen the online document

"Placing an express vi causes 'unable to open properties' error" (http://digital.ni.com/public.nsf/allkb/9d2d226bb343372886256d6e007521f5

Rebooting does nothing, and I've tried the vi on multiple machines, so it isn't something wrong with a particular installation or vi.lib.  I've looked through the vi hierarchy and didn't see any vi's that might have conflicting names as anything in the vi.lib\express\express shared folder. 

Any suggestions?

[JeffBoettcher]

The most likely reason I could think of for this error is that your top-level Config Page VI is broken.  If you open the config page VI, is it runable?  I assume you are using the Express VI Development Toolkit?  What happens if you create a new blank Express VI?  If that one doesn't give you the error, you might start comparing between yours and what you start with to see if you can isolate what is different about yours such that the error occurs.

Good luck!

[ejoseph]

Yes I am using the Express Development toolkit.  I have opened the Config Page vi, both through the express wizard, and by locating it on the c drive.  It is not broken, and I can set it running without the error.  I have opened other pre-existing express vi's that work, and created express vi's since that all work.  I thought the problem might be occurring in the ex_Read Properties, so I disabled it with a case structure to just see, but still received the error.  The rest of the Config vi is basically just an event structure in the main while loop, so I don't see that as being the problem. 

[JeffBoettcher]

If you're able to post the block / config LLBs here I can try to take a look.  I know due to 3rd-party hardware or software components it can be difficult to package things up such that they'd work for just anyone, but that'd be our best bet to figure out what's wrong.  Let me know if you can do this.

[ejoseph]

I think I've included everything.  Let me know. 

By the way, thanks for all of your help.

[JeffBoettcher]

Interesting.  It was not what I expected.

In editing your Config Page VI, it looks like you (probably accidentally) deleted an indicator that came with it.  There's nothing special about it other than its type, direction, name, and connector pane connection though, so it should be easy enough to fix.  It is required for the config page to launch, however.  🙂

On the main config page VI, do the following:

1. Scroll down a bit to part that won't be visible to the user.
2. Drop a new boolean indicator, I'd suggest a Round LED.
3. Name this indicator "Data Valid".
4. Connect the boolean wire coming out of your main event loop (indicates the OK button was pressed) to your "Data Valid" indicator.
5. On the front panel, right-click the icon in the upper-right and "Show Connector".
6. Connect your "Data Valid" boolean to the unwired terminal.
7. Save the VI.

That should get you up and going, good luck!

[ejoseph]

Awesome, it worked.  Didn't realize that was necessary to keep.  Again, thanks for your help.