Real-Time Measurement and Control

[jankl · Accepted solution]

Hi and thanks for input,

You will probably end up with a working WEB server Vincent, I did.

Constructing a new project under LV2009 made my CRIO webserver run without any problem.

I inspected the niwebserver.conf file and found that it was completely different for my new "testproject" in comparison to the conf file deployed for my "upgraded" project.

It seems that LV2009 don't uppgrade the niwebserver.conf file correctly from earlier version projects.

My current solution is to overwrite the faulty niwebserver.conf file (that is deployed each time I rebuild my project) with the working one that was generated constructing a new project in LV2009.

Another problem found after uppgrade to LV2009 was that a VI working on the cRIO filesystem stopped working due to a path that had become faulty.

In addition setting the working folder for the webserver seems strange (\:\:\ni-rt\system\ww or C:/\ni-rt\.......).

The VxWorks based cRIO seems to work with a Unix like file system, why can't we just use / meaning root in the same manner as the File Transfer client in MAX?

-Jan-

[VdG]

Thank you Jan, it helps a lot ! I'll either make a testproject like yours and overwrite the conf file, or rebuild a LV2009 from scratch for my application (keeping the vis only).

Have a great day,

[J.Harv]

Vincent-

      The LabVIEW Webserver component should be part of LabVIEW RT.  It was only mentioned that the upgrade was from NI-RIO 3.1 to NI-RIO 3.2.1 and LabVIEW 2009.  To help us isolate what component didn't update correctly, LabVIEW RT or NI-RIO, I wanted to verify that you had also included a LabVIEW upgrade.  What version of LabVIEW were you using with NI-RIO 3.1 prior to the upgrade?  Thank you for your help and sorry for any inconvenience.

Regards,

John Harvey

CompactRIO Product Support Engineer

[VdG]

well, what i've done is to switch from NI Software Solutions package 8.6.1 to 2009. In detail :

- LV core 8.6.1 -> 2009
- RIO 3.1 -> 3.2.1
- LV RT 8.6.1 -> 2009
- LV FPGA 8.6.1 -> 2009

...all at the same time.

Hoping it helps,

[J.Harv]

Vincent-

     That does help.  I just wanted to confirm this behavior was something we were aware of and working to fix.  There is a CAR (Corrective Action Request) already assigned to R&D for this issue. 

Regards,

John

[trouinky]

Same issue here.  Upgraded from 8.6.1 to 2009.  Installed full RIO 3.2.1 and even with a new Project, with the web server enabled, there is no web server default page.

[svein]

I have same issue. Please post link to CAR info and/or workaround.

Svein

[andre.buurman@…]

Dear All,

I found a  workaround to fix an upgraded project once and for all, at least it works for me.

The niwebserver.conf file is defined inside the lvproj file as property

<Property Name="target.WebServer.Config" Type="Str"># Web server configuration file.

---

---

AddHandler copyHandler
DirectoryIndex index.htm
KeepAlive on
KeepAliveTimeout 60
</Property>

Copy the contents of the key in the natively created (in LV2009) project and replace the contents of the key in the upgraded lvproj file.

[J.Harv]

Svein-

The CAR is 166503 if you want to check back with us later and find out if it was fixed.

There were several workarounds written in this forum thread.  Are you still unable to get this working?

-John

[svein]

John, 

I have not been able to resolve my problems. I found that I have problem also with new project/VI, so I may experience another issue. 

I have discovered that I can view the "default" page on the cRIO web server, but when I try to view "my" VI the cRIO crashes/restarts (the yellow status light comes on for a while), but it is not in an OK state, as I have to reboot it again before I can access it. I have contacted NI support to resolve this, so I suggest not to follow up this in this thread.

Svein