Reconnaissance TPC 2106 avec labview 2013

Bonjour,
Je suis passé à labview 2013 depuis peu (auparavent sous lv2009). Nous possédons plusieurs écrans tactiles TPC2106 mais ils ne sont plus supportés par labview 2013.
Ma question est donc : quelqu'un connait-il le "truc" pour remédier à ce problème ?

Bonjour Buckaroo,
Malheureusement, le support de votre TPC 2106 s'est arrété à LabVIEW 2012.
Voici la liste des TPC compatibles avec LabVIEW 2013 : 
Cordialement,
Vincent.O
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Été de LabVIEW 2014
12 présentations en ligne, du 30 juin au 18 juillet

Similar Messages

  • Mise a niveau Labview 2013 vers 2014

    Bonjour,
    Je dispose d'un programme de labview dernierement compilé avec labview 2013, et apres installation de labview 2014, j'ai essayer d'ouvrir mon programme dernierement compilé avec labview 2013,avec labview  2014, mais cela souvre mais je n'arrive pas a le compilé et il m'affiche des erreurs sur une des mes sous VI,
    Etant donné que je suis novice avec labview, puissez vous m'aider svp en m'éclairant sur cette question.
    Je vous remercie d'avance de votre réponse;
    Cordialement,

    Kathiaswe wrote:
    Hi,
    My error is: your Vi can't executed, can you corect your error. ça donne ça car j'utilise la version en français.
    Mercii
    Il n'y a définitivement pas assez d'information pour être d'une quelconque aide. Ouvrir le sous-vi en erreur et cliquer sur la flèche blanche (run) et une fenêtre d'erreur ouvrira. Poster l'information détaillée de cette fenêtre d'erreur, à partir de cet information nous seront plus en mesure de vous aider.
    Ben64

  • Problème connexion TPC 2106

    Bonjour,
    Je suis actuellement en stage chez DCNS Brest, et je dois réaliser une valise de tests pour relais.
    Je possède un Touch Panel TPC 2106, et lorsque je connecte l'écran à l'ordinateur, par liaison ethernet, le réseau se créé. Mais lorsque je créé mon projet sous Labview 2009, dans les propriétés du Touch Panel, lorsque je test la communication, cela me met que la connection est impossible.
    Pourriez vous m'indiquer si j'ai oublier des configurations nécessaires ou d'autres choses!
    Merci
    Résolu !
    Accéder à la solution.

    Bonjour Julien,
    Une fois de plus, notre site regorge de documents qui peuvent vous aider, ou vous guider, avec beaucoup d'exemples pour vous faciliter le développement.
    Je vous invite donc à regarder ce document:
    Creating LabVIEW Applications to Communicate Between PACs and the NI TPC-2006 Industrial Touch Panel...
    Je voudrais alors faire une mise au point sur l'utilisation du TPC avec un cRIO.
    Ce qu'il faut comprendre, c'est que sur votre PC de développement, vous allez créer une interface Hôte qui servira d'interface utilisateur et qui communiquera avec le CompactRIO.
    Vous allez également créer une application autonome cRIO, qui fera l'accès aux E/S et gèrera la communication avec le TPC.
    En aucun cas vous ne pouvez utiliser la face avant de votre VI RT comme affichage, comme vous le faites actuellement avec votre PC de développement. Il va falloir modifier votre VI RT pour y inclure une communication réseau, comme expliqué dans le lien précédent.
    Cordialement,
    Olivier L. | Certified LabVIEW Developer

  • Problem activating license on Touch Panel TPC-2106

    I have activated the license for the the Touch Panel Module on our Labview PC, but so far any test VIs running on the TPC-2106 itself timeout after 5 minutes ie. it's still in evaluation mode. I have tried de-activating, then re-activating the license, un-installing and re-installing the Touch Panel Module to no avail.
    How can I get the touch panel VIs to respect the license?
    Thanks 
    Solved!
    Go to Solution.

    Why Does My Touch Panel Application Expire After Five Minutes  ->  http://digital.ni.com/public.nsf/allkb/B9271769EB8319E7862574C900774F06?OpenDocument

  • Communication Agilent 82357B GBPIB/USB avec Labview

    Bonjour tout le monde,
    Je suis actuellement en stage et je dois piloter un analyseur de spectre AQ-6315A à l'aide de Labview 2013. J'ai un cable Agilent 82357B GBPIB/USB qui me permet de faire l'interface. Après plusieurs petits problèmes de détection j'arrive enfin à visualiser mon analyseur de spectre sur MAX et je peux communiquer avec lui à travers "Open VISA Test Panel" dans MAX. Je lui envoie *IDN?, j'ai bien son nom en lecture. J'ai d'autre petites fonctions pour lui imposer de ne pas afficher certaines courbes qui marche à travers ce panneau et tout marche bien.
    Cependant quand je passe sous Labview 2013 et que lui passe la même commande à travers un GPIB Write, il me renvoie le message d'erreur suivant :
    Error 7 occurred at GPIB Write in test_com.vi
    Possible reason(s):
    LabVIEW:  File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.
    =========================
    NI-488:  Nonexistent GPIB interface.
    Je ne comprends pas d'où vient le problème et ce que j'ai pu oublier de faire malgré toute la doc que j'ai pu lire ici et ailleurs... Ce petit VI marche parfaitement lorsque j'utilise un cable GPIB de NI mais je ne peux l'utiliser indéfiniment.
    Est ce que quelqu'un aurait une idée du problème ? Je désespère un peu là.
    Par avance merci.

    Thanks for the responses, but I finally found it.  From the Agilent IO Libraries Suite 15.5 Help:
    Enabling the NI-VISA Passport for Tulip
    For NI software to recognize Agilent hardware, you must enable the NI-VISA Passport for Tulip. This is a software module included with NI-VISA for support of Agilent hardware, and is not enabled by default. Use the NI Measurement and Automation Explorer (NI MAX) to enable the Passport for Tulip.
    In versions 3.0 and later of NI MAX, you can do this by:
    Start NI MAX
    Click Tools > NI-VISA > VISA Options ...,
    Select Passports in the tree view.
    Select the Passport for Tulip check box.
    Click Save to save your settings
    Exit NI MAX, wait a few seconds, and restart NI MAX (you must restart NI MAX for your changes to take effect).
    For specific details for your version of NI MAX, refer to NI's documentation.
    Doing this worked like a charm.
    Thanks,
    Sean

  • Problems with Applicatio​n Build for TPC-2106

    I have a project that involves a Compact FP PAC and a TPC 2106 touch panel.  I plan on using the built in web server on the PAC for remote monitoring, and then I want to use the TPC as a local operator interface.  I started to create a VI to run on the TPC that uses network shared variables to communicate with the PAC.  When I go to build the executable on the TPC, I have several errors that say "missing VI or C file".  I've checked out the forum, but the suggested fix to a similar problem has not solved the problem.  Below is an excerpt from the build report:
    Generating Code...
    NI_Variable_RT_lvlib_lvvar_RTSinglePointCreate_BOO​L.obj : error LNK2019: unresolved external symbol LVNBSinglePointCreate referenced in function NI_Variable_RT_lvlib_lvvar_RTSinglePointCreate_BOO​L_BlockDiagram
    NI_Variable_RT_lvlib_lvvar_RTSinglePointRead_BOOL.​obj : error LNK2019: unresolved external symbol LVNBSinglePointRead referenced in function NI_Variable_RT_lvlib_lvvar_RTSinglePointRead_BOOL_​BlockDiagram
    NI_Variable_RT_lvlib_lvvar_RTSinglePointWrite_BOOL​.obj : error LNK2019: unresolved external symbol LVNBSinglePointWrite referenced in function NI_Variable_RT_lvlib_lvvar_RTSinglePointWrite_BOOL​_BlockDiagram
    NI_Variable_RT_lvlib_NetVar_RT_Subscribe.obj : error LNK2019: unresolved external symbol netvar_subscribe referenced in function cln_wrapper_2EE0B3C
    NI_Variable_RT_lvlib_Var_RT_SetCleanupProc.obj : error LNK2019: unresolved external symbol RTSetCleanupProc referenced in function cln_wrapper_2EE0A24
    myProj.exe : fatal error LNK1120: 5 unresolved externals
    Any suggestions?
    Thanks

    I was able to track down what looks to be the same issue.  There was a bug that was reported to R&D (# 54707) and was fixed in LabVIEW 8.6.  It appears that there was a problem with RT Shared Variables using FIFO's when targeting mobile operating systems, like the one on your Touch Panel.
    Sorry for the inconvenience, and kudos to you for figuring out the problem!  The solution would be an upgrade to 8.6, or disabling the FIFO as you have done.  You can find a little more info comparing FIFO vs. no FIFO for shared variables here.  Otherwise, no more suggestions here.  Sounds like you are well on your way with your application!
    Brian A.
    National Instruments
    Applications Engineer

  • Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop).

    Hi all.  Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop).  This really slows things down!  Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini.  Has anyone seen similar, and/or any hints towards a solution?  

    Jeff-P wrote:
    As a side note, LabVIEW.ini is a file that gets generated by LabVIEW when it is launched if the file does not exist. So if you are missing the 32-bit ini file, launch 32-bit LabVIEW and that file should be created.
    I thought that the message: "Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini"  might indicate that the labview.ini file cannot even be created... strange...
    LabVIEW Champion . Do more with less code and in less time .

  • Report Generation Toolkit labview 2013 64bits?

    Muy buenas tardes.
    Estoy buscando el Report Generation Toolkit para labview 2013 64bits, lo he buscado pero no logro encontrarlo y con este mismo pero de 32 bits me marca error al instalarlo.

    Hola Antonio,
    Intenta con esta liga : http://www.ni.com/gate/gb/GB_EVALTLKTREPGEN/US
    Espero que por aqui lo puedas descargar,
    saludos
    Erwin Franz R.

  • Report Generation Toolkit failure with Win 7 and Labview 2013

    I recently had my computer updated to Windows 7 and am now seeing a problem with the Report Generation toolkit (version 2013) when working with Excel files.  If I try to run the New Report.vi with report type Excel selected I get  error -2146777998.  Doing the same thing with Word selected eventually opens Word, although this takes about ten seconds, but it does not generate an error.  Selecting Standard Report or HTML also run without errors.
    I've researched this error on line but I keep ending up .NET and C# forums where everything goes over my head. Has anybody got any suggestions?
    Solved!
    Go to Solution.

    I found the solution to this particular source of error code -2146777998. There are two template files that reside in C:\Program Files (x86)\National Instruments\LabVIEW 2013\templates\Report  by the name of MSOffice_RGT_Template.dot and MSOffice_RGT_Template.xlt.  The problem came down to that these templates got corrupted somehow during the fresh install. As soon as I replaced them with versions from another machine the problem disappeared.
    Just as a side note, I discovered the problem by kicking off the MS Office Report Express vi and out came a much clearer message that aimed me at the templates. Not quite sure why that message isn't echoed into the individual subvi's on the pallette, but life is a mystery.

  • Labview 2013 report generation toolkit word 2010 insert table problem

    Hi,
    I am currently evaluating LV2013 with respect to the report generation toolkit for use with word 2010. My Vi/program won't insert the correct table and gives me an error message. see below:-
    Exception occured in Microsoft Word: The requested member of the collection does not exist.Help Path is wdmain11.chm and context 25421 in NI_ReportGenerationToolkit.lvlib:Word_Insert_Table​.vi->NI_Word.lvclass:Append Text Table to Report.vi->Word Table save.vi
    I have since run the following word example.vi provided by NI within LV2013 office examples:- Growable table.vi. this gives me the same error!
    Exception occured in Microsoft Word: The requested member of the collection does not exist.Help Path is wdmain11.chm and context 25421 in NI_ReportGenerationToolkit.lvlib:Word_Insert_Table​.vi->NI_Word.lvclass:Append Text Table to Report.vi->Growable table.vi
    It would seem that regardless of my own Vi there is a fundamental problem in the office example vi.
    I have found examples of a similar problem in LV2011/2012 but the work around code doesn't seem to match the LV2013 vi's code for a direct replacement.
    Can anyone help/shed some light on this? 
    Thanks in advance,
    Dan.

    Because the upgrade of Word from 2007 to 2010 I needed to upgrade an existing application from LabVIEW 2009 to 2013. This didn't work because of the insert table error. I discovered that the problem is the vi called "Word_Insert_Table.vi" located in the ..Program Files (x86)\National Instruments\LabVIEW 2013\vi.lib\addons\_office\_wordsub.llb. There is a "Cut" command implemented, this command removes the created cell instead of clearing it. Therefore the table will be filled half and then returnes with an error. I have removed this command. I have posted the changed vi (LV 2013).
    Attachments:
    Word_Insert_Table.vi ‏30 KB

  • How can I build a LabView application that uses the 2012 runtime, on a development system with LabView 2013 or 2014 installed?

    I need to build a LabView application .exe to run with the 2012 Runtime, for legacy support. I currently have LabView 2013 installed on my development system, and have 2014 available. How can I build an application that uses the 2012 runtime on this development system? Do I have to downgrade to 2012? Thank you.

    We have existing customers that have installed our application that was originally built with 2012 (provided by a contractor that is no longer available).  Due to IT regulations, it is far easier to update these customers by simply replacing the .exe file, than creating an install that their IT department must run.
    If I have to downgrade to LabView 2012, where can I get the installation for this?

  • Nilvaiu.dll pas trouvé avec LabVIEW 821...

    nilvaiu.dll pas trouvé avec LabVIEW 821...
    Impossible de reprendre un vi créé avec LabVIEW 820 : pb au niveau de l'assistant DAQ.
    Merci d'avance.
    T.

    Peux être un début de solution :
    http://digital.ni.com/public.nsf/allkb/A64B6D4665F7C8C686257248001D7656
    Trouvé sur la knowledge base NI, un bon point de départ pour trouver des solutions
    When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

  • LabVIEW 2013: An error occured trying to load the assembly

    Hey all,
    I'm trying to load a .NET 4.5 dll into LabVIEW 2013.
    When I place any of the .NET VIs and try to select the one I'm after it says "An error occured trying to load the assembly" and won't let me load it.
    I also tried importing the dll, but that gave errors too.
    It's defintely a .NET 4.5 dll as the .NET reflector gives me
    [assembly: ComVisible(false)] [assembly: TargetFramework(".NETFramework,Version=v4.5", FrameworkDisplayName=".NET Framework 4.5")] [assembly: SecurityRules(SecurityRuleSet.Level1)] [assembly: SecurityPermission(SecurityAction.RequestMinimum, SkipVerification=true)]
    To try and get around the import issue, I added the following to my LabVIEW.exe.config file
    <?xml version ="1.0"?>
    <configuration>
      <runtime>
        <loadFromRemoteSources enabled="true" />
      </runtime>
    </configuration>
    but it made no difference.
    Any suggestions? All the things I've read so far are for 2010.
    Solved!
    Go to Solution.

    Hornless.Rhino wrote:
    Wart wrote:
    I had the same issue a while back.  Unfortunately mine magically resolved itself, but I made a post with what I'd been reading and got a reply with another suggested link.  It sounds like you've gone down the same road, but I figure every little bit helps:
    http://forums.ni.com/t5/LabVIEW/Error-Loading-NET-Assembly-in-2013/m-p/2521098
    Thanks.
    Hopefully mine will resolve itself too. LV2013 is meant to support the newer stuff without me having to mess about.
    We shall see...
    So far no dice.
    It's really bizarre. It works with sample c# code in visual studio (see link below), but for some reason LabVIEW doesn't like the dll (tried both LV 2012 and 2013).
    Sample code (not mine) is available at http://elbruno.com/2013/12/01/kinectone-hello-world-with-kinectsdk-v2-body-count/

  • Conversion of VIs from LabView 2013 to 2011

    Hi,
    I would be grateful for conversion of zipped VIs from LabView 2013 to 2011.
    Thank You,
    Michal
    Solved!
    Go to Solution.
    Attachments:
    main VIs.zip ‏38 KB

    Here you go.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Attachments:
    main VIs 2011.zip ‏27 KB

  • FPGA FlexRIO SCTL LabVIEW 2013 Compilation Problems

    Hi,
    I have an FPGA FlexRIO (7962R) VI that interfaces to a 6585 LVDS board that consists of a SCTL running at 200MHz and using a Xilinx Coregen FIFO.
    In LabVIEW 2012 using Xilinx 13.4 I have had no problems compiling this at 200Mhz, but in LabVIEW 2013 using Xilinx 14.4 I am unable to get it to compile reliably about about 170MHz with absolutely no modifications to the code.
    The Xilinx FIFO is probably irrelevant as I have tried cloning the VI and removing the FIFO and still get the same problem.
    Any ideas, things to try or solutions? 
    Thanks,
    Dave
    David Clark
    CLA | CTA
    CLA Design Ltd
    Hampshire, England

    Have you tried optimising the Xilinx compiler for Timing?
    You can't modify the Xilinx compile options of a FlexRIO target.
    In LabVIEW 2012 using Xilinx 13.4 I have had no problems compiling this at 200Mhz, but in LabVIEW 2013 using Xilinx 14.4 I am unable to get it to compile reliably about about 170MHz with absolutely no modifications to the code.
    What compile error are you getting? Does not reliably mean that sometimes it does compile correctly? Can you upload a simple example of a piece of code that works in 2012 but not 2013?
    National Instruments
    FlexRIO Product Support Engineer

Maybe you are looking for