Accessing vi front panel using labview webserver

[k-waris]

It is rather embarassing for me to spend hours reading few lines of instruction and still failing to access vi front panel using labview web server!

-I have labview 2014 64 bit, Windows 7 PC and firewall is disabled. By default webserver in Tools>>Option>>Webserver page was configured with Port 8000(i tried both 8000 and 80). I enabled webserver, created simple vi saved it on desktop and tried all following urls but still could not get front panel updated on browser. Although when I tried url http://localserver:8000 on 'Chrome' server, the message on html page was

'

LabVIEW Web Server

Use the LabVIEW Web Server to create HTML documents, publish front panel images on the Web, and embed VIs in a Web page. You can control browser access to the published front panels and configure which VIs are visible on the Web.

You can use the Web Publishing Tool to create Web pages with embedded panel images. Refer to the LabVIEW Help Web Server topics for more information about viewing and controlling VIs remotely.

'

Following urls were tried but front panel still did not appear in browsers- explorer/chrome 

http://localhost:8000/.snap?Testwebserver.vi

http://localhost:8000/.snap?Testwebserver.html

http://localhost:80/.snap?Testwebserver.vi

http://localhost:80/.snap?Testwebserver.html

http://localhost/.snap?Testwebserver.vi

http://localhost/.snap?Testwebserver.html

http://localhost/Testwebserver.vi

http://localhost/Testwebserver.html

All above were tried also with 127.0.0.1 instead of localhost but still no good results. I must be doing something really daft! Any comments?

[Sam_Sharp]

Are you talking about Remote Front Panels? Did you use the Web Publishing Tool to generate the .html file that embeds the VI into a web-page?

Also - Remote Front Panels are no longer supported by the Chrome browser. You'll need to use IE (or perhaps Firefox).

[k-waris]

Hi Sam

yes I did use Web publishing tool as well. In the generated html page, I get a message in the centre 'Invalid Server IP Address'. The only setting as far as I know which needs to be done is checking 'Enable Remote Panel Server' in Tools>>Option>>Webserver page!. Any comments?

[Sam_Sharp]

Can you attach the HTML file here - if you open the source of the file, what is the URL it points to? (in the <object> tag, I think?)

You might also need to enable access to the VI on VI Server - check in the VI Server properties of 'My Computer' in your project and check that you have '*' in the allowed list (to allow access from anywhere).

[k-waris]

HTML attached

I do not think it is adding the full link with ip address in the <img></img> tag. Also I checked and I have * in vi server

 

[Sam_Sharp]

Do you have the Remote Front Panel plugin installed for Firefox? http://digital.ni.com/public.nsf/allkb/151BE12C055F57CE86257043006CB4B3

I would also try with Internet Explorer.

[k-waris]

By Adding * to the browser access in Webserver Settings,

I can now see 'snapshot' of my vi but using the url directly such as http://localhost:8080/.snap?TestWebserver.vi

Unfortunately, html pages created by webservices utility still do not show 'snap' or vi with monitoring capabilities!!

[JakeA]

Hi k-waris,

Can you give me a list of the steps that you have taken thus far to get to this point? You've said that you went through some fo the documentation, have you come across either of the following documents?

http://www.ni.com/tutorial/4791/en/

http://digital.ni.com/public.nsf/allkb/6F58D8300ACB743C862579F8006E2800

The first document is a tutorial which goes through the process of using remote panels; it sounds like you've already tried something similar but I would recommend going through and confriming that everything you've done matches up with the tutorial.

The second document is a knowledgebase article which discusses use of remote panels with executables, I can't see any mention of executables in your posts but I wanted to link to it anyway in case you were using a LabVIEW executable or if this was a functionality you might want to add in the future.

I also found a KB which seemed to describe the problem you're experiencing, can you have a read through it and check to make sure that these settings are correctly configured?

http://digital.ni.com/public.nsf/allkb/C4127DFFF4152FE3862571DA0006018A?OpenDocument

Regards,

Jake