06-23-2021 03:36 PM
Hey all,
I have a NI cRIO-9082 that is running a RT Application that I created and deployed using a win10 PC. Now, I wish to view and control the front panel of the VI that is running on the cRIO. I followed the steps for creating a webserver using this NI link. However, when I connect to the cRIO using Internet Explorer, I can only see the html bits (header, title and footer). The remote panel section shows an error, "Server does not support Remote Panels". I have followed everything listed here to try to fix the issue, but that hasn't seemed to work. I'm sure I'm missing something trivial. I have also come across some forum posts where people have mentioned that Remote Front Panels aren't recommended for RT systems. Any workarounds or help would be appreciated!
11-13-2022 01:42 PM
Setting up Remote Panels for VI's on RT systems is a process of many steps. Attached is a link to the best *so far* on how to set them up.
Essentially these steps are:
1. In Max: Assure you have installed the Web Server package as part of the RT Software deployment. Don't confuse the WebDav with the VI Panel Server.
2. In the LabVIEW Project: Right-click on the RT system on the project Tree - Enable the Web server - then right-click -> Deploy the Front Panel Web Server Enabled configuration.
3. Create your RT Main VI
4. In the LabVIEW Project: follow the examples in the link to access Tools>Web Publishing Tool and create the html file template for your main VI. SIMPLIFY the name of your hmtl with NO SPACES - as you'll get the %20 html gobbledeegook [the default html name offered by the web tool interface is insanely long and complex...keep it simple - you'll need to type the exact http:\\ path and you can make many hairpulling mis-typing mistakes...]
5. In the LabVIEW Project -> RT Build Specifications: You need to follow the example link to essentially, push the .html file with your deploy Vi to a www directory on the RT.
*** the destination path for the www on the RT should be /var/local/natinst/labview/www
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YHxcCAG&l=en-US
What can be a pain is figuring out the exact web address - for example here is an actual web panel access path: notice I used underscore _ in lieu of spaces - I also *think* it might be case sensitive.
http://10.0.10.5:8000/Mosaic_Ctrl_Main.html
I have to say this is very hit and miss - half the time I can deploy a Web panel with no issues - then on some systems - I can't...get the 'Server service is not running' or the VI does not exist...This leads me to believe there is an order to configuring that has a fragility - so if you don't do that - it breaks the function.
Regards
Jack Hamilton