LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

programmatically regain control of a VI

Solved!
Go to solution

I have an application that on request does the following actions:

 - generate a VI

 - run the VI

 - publish the VI on the Web trough the WebServer

 

But now I need to programmatically regain control of Front Panel.

 

I now the local user can at any time do this, but it seems it can’t be done in an automatic fashion.

 

Any thought?

 

Thanks.

0 Kudos
Message 1 of 8
(3,502 Views)

Hi Tonitos,

how needs the control back? The running vi itself?

 

Mike

Message 2 of 8
(3,494 Views)

The application that launched the VI needs to regain control back.

 

Let’s see:

-         Application 1 creates VI

-         Application 1 runs the VI

-         Application 1 publishes the VI trough the WebServer

-         Remote Client acquires control of the VI

 

And now I want that the Application 1 regains control of the VI when one of a given number of events occur.

0 Kudos
Message 3 of 8
(3,480 Views)
Solution
Accepted by topic author Tonitos

It's so simple that I lost a few hours finding the solution...

0 Kudos
Message 4 of 8
(3,476 Views)

Hi Tonitos,

can you unlock the vi or give us the password? I think it's then easer for others to learn from it. 🙂

 

Mike

Message Edited by MikeS81 on 01-21-2009 07:08 PM
Message 5 of 8
(3,462 Views)

I’m sorry, I didn’t realize it was locked.

 

The password is 123.

 

By the way, it was set programmatically, does anyone know how to set it manually? 🙂

 

Thanks

0 Kudos
Message 6 of 8
(3,441 Views)

Hi Tonitos,

right click in the front panel on the icon and select VI properties. Change to security. There you can set the password.

 

Mike

0 Kudos
Message 7 of 8
(3,435 Views)

Here goes.

To test the application one must first publish the soma.vi on the web, then access it trough one web browser, the control will then be given to the remote user.

On demand, just execute the teste_01.vi and the control will be taken from the remote user e locked to you.

I’m currently using this as a sub-vi that is called when ever a given event occurs.

 

Before I forget, the soma.vi must be in d:\soma.vi, or you can just change the path. 🙂

Download All
0 Kudos
Message 8 of 8
(3,429 Views)