TPC2106T web server problems

[abales]

Labiew 8.6 Pro, Vista SP1, TPC-2106T

What I have done - I have made some simple VI apps that another PC can web browse to and view as well as control.  I can also download the basic template TPC vi and share variables between the TPC 2106T and my PC running two different applications inside the same project file - with two targets [My Computer, NI TPC 2106T Device].   I thought it was odd that I could not create shared variables on the TPC device but had to create them under a library on the PC target.

I used the FTP manager to get this running.  I can also use cerdist.exe to remote into the TPC. 

But:

My problem is that Project Explorer doesn't allow for me to make the NI TPC 2106T device a web server like it does when I just make a normal RT app for the PC.  Rest doesn't exist for the Device Target.  Not sure if I use RESTful.

Going into the TPC_1.vi and trying to setup the web server yeilds this for the web page -

http://WM:100:TP:NI%20TPC-2106T%20Device/TouchTest/TPC_1.lvproj_%7BEB85E6E6-8C04-43F1-9CE2-B4AB0ABC7...

what is going on with this stuff?

Also the 'NI 2106T Device'->'Build Specifications'->TPC_1.vi doesn't have "Startup" listed like Deploy, Run, Debug are listed by the menu.

[Eli_S]

Hi abales,

Let me clarify a few things about the behavior of LabVIEW-build applications for a touch panel. First of all, the shared variables library needs to be created under the "My Computer" target because they cannot be hosted on the TPC. When you create the library under the "My Computer" target, that means that the library will be hosted on and deployed from the host computer. I am not sure what real-time targets you are familiar with but the CompactRIO for example can host the library, but it needs to be deployed from the project explorer. Also along these same lines, there is no "set as startup" option as in RT targets because this is a different target and there is no way (really doesn't even make sense) to have the VI set as start-up. To accomplish this you have to do it from the OS of the TPC once you have deployed the EXE.

Now, regarding the problem you are facing, can you please clarify what you mean by webserver? Are you trying to implement remote front panles for the program running on the TCP? Another thing I am not clear on is what you used the FTP manager for? Can you please clarify that? 

[abales]

Thanks for the overview on shared variables.  I did not realize TPCs could not host them.  I do get a C-RIO in the system sometime, have no idea what/how to use it but it will be tied in with the TPC as a station for monitoring data.  Sounds like I must have a master app that runs on the monitor pc or one of the many CRIOs to control all of these vars.

Web stuff - yes I guess the term is Remote Panel.  I want to deploy a the FrontPanel.html [for FrontPanel.vi] generated file on the remote system, that the web service uses [on that remote system] to allow another pc to connect to the TPC, take control of the front panel, and do whatever.

I got this working on my PC for another project already.  I can generate the html page, got the server turned on and when running the Front Panel I can access this from another PC (with .NET 3.5 installed, a bit of a download).  I want this working on the TPC but the project file looks to be PC centeric on web server configuration and were to put the html file.

I also want to know if there is something I need to turn on in the TPC.

FTP server - I thought I needed that running so I could deploy to the TPC.

I am extremely new to LabView, just got the CLAD but never done any real work.  So I am lousy on the terms but I know what I want to do, just not how to get there from here.

[Eli_S]

Ok, understand now. I am not sure if this is something that is supported in a TPC target but let me investigate if it is. If so, I will also let you know what the proper steps are to get this working. I will post again when I have an answer.

[abales]

Thanks!

We were planning on using many TPCs with many CRIOs [1-1, CRIO dependent on TPC, CRIO collect data and scope stuff and report to the TPC].  The TPC was to control information to the user and read/write data to the SQL database.  TPC was to be the center point for data, user, db and internet and remote controlable.

Sounds like from what you say - we might have to revisit the basic layout to have the CRIO become the center of gravity for the project and the TPC behave more like a dumb terminal with some status screens and a go button or something similiar.  I am going to guess, since the CRIO can fire off shared network variables as the source, it can probably allow for remote front panel and posting the html page to the CRIO.  Sounds like the NI LabView software base on the CRIO is more complete than a TPC?

[Eli_S]

Hi again,

I do think that you should consider restructuring your architecture. Although the TPC's do run a "full blown" operating system (Windows CE), the capabilities that you have in LabVIEW for the TPC's are rather limited as compared to what you can do in the CompactRIO. In terms of LabVIEW programming, you can almost do everything on a CompactRIO as you can on a normal desktop computer. I also think that the processing power of a CompactRIO is higher than the TPC but I am not sure. Typically TPC's are usually only used for providing a user interface to the CompactRIO and not much else.

I am not very familiar with databases, but I wonder how you are planning on logging the data to a database? I know LabVIEW has a Database Connectivity Toolkit but that only runs on a Windows computer.

[abales]

Wow I never even thougth about db limitiations in the TPC.  FIgured it was plug and play.  I think we will have to revisit the design now.  I really appreciate you pointing out the problems ahead of time for us.  I am going to guess that the CRIO can't use those db vi's than either?  I think we will probably wind up using the harddrive file system to save/get xml files and then let the controling pc push/fetch data and then send it to the db.

[Eli_S]

Hi again,

I just found out about the remote front panels issue and I was able to confirm that  LV Touch Panel does not support remote front panels.

I think that having the CompactRIO send the data (XML works fine) to a desktop computer, and having that computer talk to the db, is a much better approach.

Message Edited by Eli_S on 10-06-2008 01:05 PM