You can certainly achieve setup you described above. Here is a general topology
-Create LabVIEW project
-Add your devices to the project (cDAQ and touchpanel)
- Write your real time application for cdaq 9139 which is interacting with host(we will treat touch panel as host)
Here is an article that talks about different communication methods between RT and Host
- Based on the article above setup your host vi (touch panel VI)
- Once you have everything working on development machine, that is your real-time VI is able to talk to Host VI. Build start-up application for your controller and another application for touch panel.
Building and deploying stand-alone RT application:
Application deployment to touch panels
Now, all of the above steps will require some development time especially if you are new to this process. Everything is documented on ni.com and simple searching will get you everything you need. If you happen to get stuck with something then post on the forum.
Your touch panel should be already preinstalled with NI software. Generally, you would need to have LabVIEW Run-Time engine installed on your touch panel. Essentially, touch panel is nothing else but another computer compacted in a small roughed form.
If you are using LabVIEW 2014 then you should be able to add TPC-2212 touch panel to your project.
Right Click on Project: Title >>Targets and Devices>>Specify a target or device by IP address>> Type in IP address of your touch panel and select your touch panel model under Touch Panel section.
Look at your controller, you should have 4 LEDs there. One of them is User 1 LED and you have an ability to toggle it ON and OFF. You should be able to access it from your LabVIEW project via I/O node.
Drop this I/O node in your code and toggle it ON/OFF. This will give you some visual and you'll know if your code is running.
Thanks Miro, actually i knew about the user LED. And as I suspected my startup aplication doesn't run on the cDAQ at start up (despite the fact that it was successfully deployed as startup application).
Is there any way to know what is the reason for that? is there any error log which I can see?
Here are some things you can do:
-Enable console out on your cRIO and connect a monitor to your controller. You should be able to see controller processes.
- enable application debugging then debugg it remotly
I hope this helps