TCP 2230 no connection

[Cardex]

Hi,

I have a Problem with the Touchpanel TCP 2230. We worked with it for 2 months now and have runtime on it. And now suddenly we cannot connect with it anymore. We don't really see indicators for possible errors and are desperate.

One thing that is unusual is that when the touchpanel is started, a NI program is searching for a document. We think that the program is NI Labview Remote Developement but we don't know what it is searching for because it only says: "choose a file" (like in the picture)

Do you know something about this?

Best regards

[Bob_Schor]

Wow!  You really leave us guessing!  I'm assuming LabVIEW is running somewhere (I saw a LabVIEW screen in the background of your image).  Here are some questions:

• Is your LabVIEW Program running on the TCP 2230?
• Is your LabVIEW Program running on a PC, and you are trying to use the TCP 2230 as a "remote screen", or a "remote PC"?
• You say you have "run time" on it.  What does this mean?  It would really help if we didn't have to guess.
• Please post any and all LabVIEW code (attach the .VI files, don't make us "guess" by attaching pictures of block diagrams or front panels).
• Tell us any other information that will help us to understand what you are trying to do.

Bob Schor

[automatix99]

Same Problem here.

We have two TPC-2230 connected to a crio9074 to act as HMI for machine Operation without any external LabVIEW Computer.

Both have similar Front pages that have been developed with LabVIEW 2015.

In principle everything is working, but:

One TPC can be connected to the Project Explorer of the development Computer as usual.

The other Fails to connect, however it is still reachable with the DOS ping command. Ist behaviour is as described by the OP: After loading the compiled LabVIEW exe, it starts some LabVIEW component and is Pops up with a file selection Dialog searching for some unknown *,vi, *.ctl, *.lvproj, ... in the .\my Documents folder

when portscanning, it has extra ports open (2869, 5357) compared to the fully working TPC.

I can update its executable via USB-Stick and it seems to deliver and fetch data to/from the machine, but cannot be connected to the development Computer for watching its Network variables.

The System is up for a year now. Any clue what happened this week?

Joe

[Bob_Schor]

Wow!  An almost-two-year-old question, where the request for "extra information" so we could try to help was ignored by the OP, and, now, you have "the same problem", again with not a lot of detail to give us clues what might be happening.

You might look at the request for information I posted 22 months ago, and see what additional information you can provide to help us help you.  One thing to think about is whether you recently upgraded (voluntarily or because someone "pushed" an update through you) any Software or Operating Systems.

Bob Schor

[automatix99]

Many thanks for your resonse!

I was already prepared to start a new thread, but this was the only one I could find addressing such a problem however not solved at all. Main reason IMHO is hat the OP felt misunderstood with his problem.

Think of the most obvious situation. This is "automation world" where you try to omit all those "buggy and update - hungry" IT components and OS to maintain operation for decades.

My Touch Panels have been installed to replace a Windows PC for machine operation controlled by a crio RT system - for the same reason. 

No updates to the TPC-2230, they are still as delivered by NI two years ago. They came shipped with Windows embedded 7 and installed LV Runtime 15 (together with 14 and 12). All you do is put a compiled "frontpage.exe" in its Startup folder and reboot. It acts as HMI to the other non-PC components.

This works for both Panels here. Odd is that one TPC tries to Startup some *.vi/exe even _without_ transferred app.

In this situation it should come up with WES7 Desktop only. The other works as expected...

[automatix99]

...sorry, was interrupted...

regarding your questions to OP:

*my Labview app is running / can be run on the TPC 2230

*my Labview app cannot be started for testing on PC because that would need connection to the TPC 2230

*Runtime environment 15 is installed on TPC as delivered, OP probably meant "compiled .vi app" if this is clear enough.

*In my case "all LabVIEW code" could be only: Empty project with just 2 TPCs, and "HelloWorld.vi" frontpage with no code underneath. I can fully understand the attached picture: some unknown  Labview component is started on the plain desktop requesting a file, possibly on top or even without the transferred LabVIEW app frontpage.

*My dev computer is Windows 7 with LV 2015, but I would expect that I could fire up my old XP computer with the old LV version on it and connect to my two Touch Panels, since they have two older runtimes on it, too.

*Just in case: No, there's no internet connection, neither dev computer, nor machine with Touch Panels. They are only connected together.

I suspect, that something happened to the LV setup on the WES7 that skips starting the communication channels used by LabVIEW.

Its nothing with the network hardware, since I still can open the "Public" folder of the WES7 remotely on my dev computer and place files in it.

Maybe it was myself modifying some setup while fumbling around with the touch interface.

Or some broken deployment of unwanted thing from the dev computer to the panel.

I can find nothing in the "Startup folder" so I may need to dig into the registry of the WES7 or into the running services to find out what has been changed compared to the working TPC.

Again, the problem persists even without transferred LV app and even without any network connection to the TPC.

Without understanding of the LV architecture I have no clue what is the communication counterpart to my dev computer. One of the runtime environments? Maybe another LV service that should have been started on the Touch and listening for incoming connections?

Thanks for further assistance!