TOUCH PANEL MODULE PROBLEM

[F.WalkJr]

Hello Everyone!! 

  If you are are here to help I thank you in advance.   I have just updated my LabVIEW environment from 8.5.1 to 8.6 ( the quarterly update) and up until now everything has been OK.    My setup is a touch panel computer (NI-TPC2012)  communicating with the cRIO controller.    Everything was working perfectly until I updated the touch panel code with 8.6 and redownloaded it to the unit, now my touch panel application times out stating that I need to activate the product.   I've activated my product on my host computer where I do all of the programming, do I need to activate software onboard the touch panel and how do I go about doing this?

[Brinoceros]

Hi F.WalkJr,

At exactly what point do you receive this message about activating?  When running a built EXE that you have FTPed to the TP?

Check your NI license Manager (under Start>>Programs>>National Instruments) just to be sure both your LabVIEW and Touch Panel Module are both activated for 8.6.  Any screenshots you can take would help (although if you take one of your License Manager, please be sure that no serials numbers are visible).

Regards, 

[F.WalkJr]

Thanks for the response Brian,

  The message pops up a few seconds after starting the built EXE that I've FTPed to the TP.    Checked the license manager, solid green square for every version I have.   If I have the license on the computer where I built the application it should automatically apply to the TPC-2012 correct?    I've used the same hardware setup since 8.0 and never had this problem after an update.  Question, the 8.6 DVD set also included the Mobile Module, which I installed but do not plan on purchasing, could this somehow cause my problem?    I'm going to uninstall it just in case...

Thanks  

[Brinoceros]

Your guess might be exactly the problem.  It seems that because of the shared resources between Touch Panel and the Mobile Module, your touch panel application may run as an evaluation because your Mobile Module is not activated.  Go for the uninstall of the Mobile Module, and let us know how that goes!