Embed subpanels and control remotely

[mikeporter]

Yes I remember having the same situation when embedding a web page. The solution was Rudi's idea of having as a default a blank page.

Mike...

[Kyle Thompson]

Good idea on the blank web page and it works stupendously for me. However, I am now finding that the ActiveX connection takes forever...like on the matter of nearly 30 seconds...to load. I know it is not overloading the computers because the CPU usage does not go above 5 percent when it is connecting. However, the server VI freezes completely and the execution is a bit choppy until the VI finishes loading.

Any ideas on the slowness of the connection? I am using a 100Mbit hub and both computers have 10/100 ethernet cards in them that are running at full speed. Is there just more information being transferred back and forth than what I think? It doesn't make much sense that the server VI freezes up completely. I opened the web page in Internet Explorer both on the server and remote PC. Interestingly, when connecting to either of them the server VI freezes so something must be going on. Naturally it isn't frozen as long and the connection is made much faster when I open IE on the server box.

I am beginning to wonder if I should have gone with the .NET browser but the ActiveX had more documentation in the context help. I started messing with a .NET implementation and I was pleased with it for the most part. However, once I called the navigate property node, the web page did not stay connected like with ActiveX.

If I can get the ActiveX to work faster or the .NET to work completely, I would appreciate the help.

Kyle

[mikeporter]

Do you have the blank web page on your local machine? If so it should load very quickly...

Mike...

[Kyle Thompson]

Yes, I have the blank VI on my local machine but it is the VI off the server that I really need to load that is very slow. Granted it is not a small VI but at a 100Mbits per second it shouldn't take that long to load!

Kyle

[Kyle Thompson]

I have figured out the issue with the slow loading. Since I am in a test environment right now I was just setting some dummy network parameters because all I thought I cared about was the IP address. However, I was also specifying a dummy address for the DNS server. Little did I know that the computer would actually look for the DNS server for about 30 seconds before it gave up and actually connected. So what I thought was a slowdown with LabVIEW was actually the computer waiting on something that wasn't actually there!

Now I can connect within a couple seconds on every try.

Thanks for everything. I am sure that I will encounter more issues you can help me with 🙂

Kyle

[mikeporter]

Good catch! Your comment reminded me on something else to always look at: Make sure that all unused network protocols are turned off.

Mike...