LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

labview web published vi

Dears we are going to establish a Laboratory for Control Engineering Education that can be accessed from web with LabVIEW 2009. We have full Professional version .Please look at the snap in the attachment. But we are facing some problems. If we keep the viewing mode as Embedded then we have no. of connection problems. Hardly more than one client can connect to our server. Attecment#2 If we keep view mode Monitor (with refreshing time as 1 sec) then the size of LabVIEW in the memory grows and grows and the increment is even more if the no. of connections increases. Please advise me some proper solution. I shall be more than thankful to you for this. Best Regards Syed Shahid Raza
0 Kudos
Message 1 of 11
(2,395 Views)

Apparently no attachment has been provided.

 

Anyhow, what seems strange to me is that "monitor" mode should be simply an updated screenshot of the front panel...

 

Regards,

Marco

 

0 Kudos
Message 2 of 11
(2,390 Views)
0 Kudos
Message 3 of 11
(2,388 Views)
Sorry for forgetting the attachments. But the fact is that in the VIEW MODE Monitor Labview.exe size gorws and grows and the increments is high if the no. of clients is increased.
0 Kudos
Message 4 of 11
(2,380 Views)
Please find the attachments. As upon your recommendation I have put simplest controls on my VI and tested it. It has total size approx 34k (test.vi) and my actual vi size is 149k (HX.vi). After web deployment of test.vi the memory usage of labview.exe is 60,368k and after 1 min or so the size is 60,838k. The size reached up 64,343k when I open anther web page of test.html from the same PC . So still the size of labview.exe increment problem is there. The CPU usage reaches up to 100% as the no. ofclients connects to this PC through LAN increase. The problem with the embedded mode I have is that hardly more than one PC (some time even 1 client can’t) can see my VI(HX) through browser. I am not favoring any mode i.e. the embedded or monitor but just want to enable remote PC to see the updated VI (HX).
Download All
0 Kudos
Message 5 of 11
(2,364 Views)

Hi Syed,

 

I'm not sure what's causing all the memory allocations, but I think it would be good to make sure they aren't originating from an issue with the original VI. You could use the performance and memory tool available through Tools>Profile>Performance and Memory to ascertain this. If you could post a screen shot with the tool open and the vi running, that would be helpful.

 

What are the specs of the computer you're running on? Does it affect matters if you increase the update rate for the front panel or tell it to run continuously? One thing you might consider is switching to hosting a RESTful web service. This should have less effect on your computer. Here's a link on how to do so: http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/build_web_service/

0 Kudos
Message 6 of 11
(2,341 Views)
Please find the attachments of Performance , Computer Spec. and others. But after increasing the update time to 3 sec (first its was 1 sec) the size of labview.exe in the task manger, not increasing at that speed. I have tried RESTful service but i am not happy with it 🙂
0 Kudos
Message 7 of 11
(2,325 Views)

What happens to memory usage if you run your vi for hours, with nobody connecting from the remote interface?

 

regards,

Marco

0 Kudos
Message 8 of 11
(2,317 Views)
It has no change on labview.exe size ( viewing from task manager) but whenever i open that vi in ie from this pc or some other remote LAN PC the size of labview starts growing. You can see the difference in the snap1 and snap2 ( 1 min gap)
Download All
0 Kudos
Message 9 of 11
(2,310 Views)

Hi Syed,

 

With the screenshots and information you've provided, we've looked into this a little further and I think we've identified the issue. A memory leak when using the monitor function for a remote front panel is a known issue in LabVIEW 2009. This was reported to R&D (CAR#182590) and was fixed in LabVIEW 2010. Here is a link to the current evaluation software download for LabVIEW 2011. This fix is recorded on the LabVIEW 2011 Bug Fixes docoument (look for CAR#182590). 

0 Kudos
Message 10 of 11
(2,286 Views)