Standalone Executable Help

[leroy27336]

Guys,

I have a question about the standalone executable feature in LabView 8.  I made an executable for an Oscilloscope driver that i've been working on.  However, when I run the executable I am only able to work with the front panel.  The problem is, that some of the parameters leading to the sub vi's that run the Oscilloscope may need to be changed at some point.  Is there anyways to create a standalone executable and still be able to access the block diagrams in order to be able to make changes?  Thanks.

Andy

[becktho]

Hi Andy

There is no way of directly modifying the block diagram if you work with an executable.

Basically, if you want to use an executable and you still need to modify the block diagram, then there is something wrong with your code. You definitely have to take a look over it once more. Working this way could be compared to a normal application (let's say MS Word) - if you want to change a setting you don't modify the code Word, do you?

As you say you want to change parameters, you can use files to store parameters which are loaded depending on some user input or program state.

Thomas

[JLS]

Hello,

You can use files as suggested, where your application reads from those files and uses the values you have defined there, or simply use controls on your front panel to set those values.

Best Regards,

JLS

[ian_fung]

Juz a suggestion...

In your application, insert a Button, say "Configure" or anything that make sense. And, this Button calls a subvi when it is clicked

subvi: Consist of all Controls that your system may require changes to be made during runtime.

Upon entering the subvi:

• Check if *.ini file exist? If yes, read all keys & update all respective controls. If not, create one with all required controls name as 'key' and control value as 'value'
• User is now able to make changes to any control's value
• 'Save' button maybe provided to update changes to the *.ini file
• After exiting the subvi, update your main VI with the latest values from *.ini

There could be many ways of preparing the subvi as well as the *.ini file.

Last but not least, *.ini is read by the application program everytime the program is invoked or when changes is made through the subvi.

Cheers!