Re : cRIO web server

[VdG]

Hi,

i have a cRIO system (with a 9014 controller), that was running NI-RIO 3.1, and a web server based application, without any problem. Now i've switched to LabVIEW 2009 and NI-RIO 3.2.1...I format the cRIO disk, install the new version software, re-compile all my application (FPGA and RT layers), deploy all, reboot the cRIO and...the web server doesn't work anymore. It is of course enabled in the target properties, with all access by default (*) and the cRIO normally answers to ping commands, but the web server seems down : have i miss any step in the upgrade process ?

Thanks,

[ajangot]

Hi,

Make sure that you don't forget to deploy the build application by right clicking the build specifications and clicking 'deploy'. Also make sure you set it as a setup. Make sure that when you reboot the cRIO, the VI is running automatically. Also make sure your windows firewall is disabled. If you follow the guide you referred to step by step, everything should be fine and you should be able to connect. My guess is that your VI is not set to running automatically in the build specifications. Make sure that when you create the build specifications, while not only specifying 'set as startup', to also specify the startup VI in the source files item of its properties.

What is your configuration of your niwebserver.conf file ?

Regards,

[VdG]

Hi, i'm sure my vi's running, because it displays some datas on a LCD connected to the RS232 port of the RIO. Furthermore, i can't connect to the root of the web server, i.e. just entering the RIO ip in my browser. Please find my config files attached

[speleato]

Hello Vincent,

What software do you have installed?  If you did the minimal install it won't include the "Webserver for LabVIEW RT 2.0.0" Component which you will need to have installed.

You should be able to see if it is installed in MAX.  If it isn't there try installing a software set that includes it or add it using the custom install option.

Sebastian

[VdG]

Hi Sebastian,

no, i've installed the full version of RIO3.2.1 (without the scan mode support), not the minimal. Max shows the web server installed too. I've even tried to re-install the web server once, without any change in the controller behavior. Quite strange isn't it ?

[jankl]

Hei

Exactly the same problem for me, no web server after installation of LV2009 and NI-RIO 3.2.1. (default package). Everything else functions flawless. (development system, my remote autorun VIs and a TCP based remote command system for host communication)

The hardware is a 9012 and the system is built and set to "run as startup".

A reinstall of NI-RIO 3.2.1 with reformat of the 9012 disk did not help. I have tried a lot of options in the web server property tab (default command is missing in LV2009?) and a lot of hot and coldstarts of the cRIO.

Checking the ports of the cRIO shows no service at port 80!

How do I verify that the webserver actually is running on the cRIO, any logs that can be viewed?

This seems to be due to the update of LV and NI-RIO. The webserver was operating on the same device with LV 8.6 and an earlier version of NI-RIO.

Jan

[jkurtw]

You can look in the system manager (Tools » Distributed System Manager) to see if your web service is running. 

It will show up along with any shared variables that you have deployed.

Kurt  

[speleato]

Yes, very strange.

Does the webserver work if you aren't running a startup application?

Sebastian

[ajangot]

Hi,

Are you sure to follow all step of this document: How Do I Create a Remote Front Panel for Use on a Real-Time Target Executable?

Can you try to format your cRIO, make an new project with and empty VI with webserver, create executable with "run as startup"and deploy it. Your webserver must be online, after deploy your project.

It seems that webserver have a strange behaviour with LV2009.

Regards,

[VdG]

Hi,

sorry for the delay, i've been out of my office for more then a week...Well, i can try with a new project, starting all from scratch, as you suggest (Jan, did you already try that ?). But the fact is that redeploying under LV2009 and RIO3.2.1 a existing project, that was normally running in LV8.6 and RIO3.1 actually, leads to this deaf web server...I can't imagine that NI developers hasn't noticed such an obvious problem. So i guess i make some mistake in some step of the process.