LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Is it possible to have a VI "run when opened" when accessed via Internet Explorer?

Solved!
Go to solution
Here you go.

Message Edited by Kenny K on 09-19-2007 03:19 PM

Kenny

0 Kudos
Message 11 of 16
(1,078 Views)

I also tried adding in an event structure, and setting the timeout to the same as you have it.  The vi still functioned normally.

I am not sure if it matters or not, but are you running the vi on the same pc you build it on, or are you transfering it to another computer and then trying to run it??

Just a wild guess here, but are you stuck in a loop somewhere when it is in "idle" mode?? 

Also, I would recommend wiring all the error clusters, and doing some error handling.  Remember that a system dialog only appears on the host PC, the remote clients will not see it, so the program can appear locked up when it has an error.

For reference, link to knowledge base article on the same topic.

Kenny

0 Kudos
Message 12 of 16
(1,072 Views)
Sorry, you are also going to need to supply a reference to 'This Application' in order for the RemotePanel.ConnToClients to display properly.  See the attached screenshot.

-Bob
0 Kudos
Message 13 of 16
(1,067 Views)
Solution
Accepted by topic author Pflugh

Gentlemen, thank you for your feedback, it was helpful. What I found out is that 'RemotePanel.ConnToClients' does not work for re-entrant VIs. It works well for non-re-entrant VIs whether the property is in a separate VI running on the server or the target VI. I was not able to see which instances were open and controlled by a remote user from the server side much less control them properly for my re-entrant VI. I did figure out a way to get the remote panel to autostart although indirectly. Instead of using IE I wrote a VI that is run from the client side. I used the remote panel server method to open the target VI from the client with the request control bool set to true then wait for the remote panel server property to let me know when the client is in control of the VI then use the Microsoft keybd_event dll and do a Control+R to run the VI. Sorry for the long sentence. The remote panel server property knows which instance by name was launched where as the remote panel conn to client does not. The client can close the session by entering Control+W, ALT F4 or click the X in the corner and it all goes away.

Thanks again

Bob

 

0 Kudos
Message 14 of 16
(1,027 Views)
Bob, do you have the code for sending the ctrl+r to the VI?
0 Kudos
Message 15 of 16
(746 Views)

Ethan85

Here is the vi that I used for launching the remote; it has the keyboard code plus how I used it. I hope its useful to you.

0 Kudos
Message 16 of 16
(735 Views)