LabVIEW 2013 Changer la couleur d' un onglet

Bonjour à tous,
Je souhaite changer la couleur d'un onglet. Le noeud de propriété couleurs avant plan et couleurs arrière plan donne un resultat en lecture, mais refuse d'être commandé... Je n'ai réussi qu'à changer la couleur des étiquettes... Pour terminer, je viens d'installer Labview2013.
Merci d'avance pour tout conseil
Franck
Solved!
Go to Solution.

Bonjour,
Pour avoir plusieurs couleurs, il faut faire un click droit sur l'objet-->Avancé-->Autoriser plusieurs couleurs.
Il vous suffit ensuite de jouer avec les couleurs disponibles dans la palette d'outil pour chaques onglets.
Cordialement
Paolo_P
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;}
Travaux Pratiques d'initiation à LabVIEW et à la mesure
Du 2 au 23 octobre, partout en France

Similar Messages

LabVIEW 2013: Source distribution, destination path for post build VI changed?

Hi,
In a source distribution for an embedded target (Real-Time for instance) you specify both "Local destination directory" and "Target destination directory". Let's say the local directory is "C:\MyProject\MyModules\", and the target directory is "C:\" for instance. Then on my build machine my source distribution will end up in "C:\MyProject\MyModules\c\<source distrib files>", and I can then FTP everything from <source distrib files> to the root of my target's c-drive (or in some cases I can just deploy directly after the build, and LabVIEW will move the files to the target for me).
You can also specify a Post Build VI that can do stuff to your source distribution after the build has completed. Such a Post Build VI has an input named "Destination Path" for use inside your Post Build VI, so you can find your files to operate on :-)
In LabVIEW versions prior to 2013 this destination path would be "C:\MyProject\MyModules\c\", but in LabVIEW 2013 the destination path is only "C:\MyProject\MyModules\" thus missing the target destination directory part. Now my Post Build VI can no longer find my source distribution files, unless I inside that VI hardcode the target destination directory - and that isn't a good solution.
Is this changed by design in LabVIEW 2013, or is it a bug?
Cheers,
Steen
CLA, CTA, CLED & LabVIEW Champion

I don't do a lot of (actually any) source distributions of embedded files, but I can tell you that there was a bug in earlier versions where during an application build, the destination path was reported incorrectly. Perhaps this is related.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

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

Slow LabView 2013

Hi
I have Labview 2013 Professional Dev Sys SP1 ver 13.0.1f2 (32-Bit) and it is slow when I develop any aplication.
For example, if I have a tab control and I change to another tab, it takes about 2 seconds to change tab after I click it.
If i wire a new line, it takes 2 seconds to appear that line in block diagram, and so on.
I have a new computer Dell Optiplex 7010, i7 Processor 3.40Ghz, 64-Bit, 4Gb RAM, WIndows 7 enterprice SP1
If i run Windows task manager it shows 17% CPU usage and 2.14 GB Memory.
If I run for example, excel 2013 it does not seems slow.
Do you have any suggestions ?
Regards
Solved!
Go to Solution.

EDGAR_PLATRONICS wrote:
Hi Yamaeda:
I am not sure about mass compile. You mean rewrite code ? Or create exe file and test?
A this moment I have checked with only one Vi but it is very large. Many sub VIs and code.
Actually it worked correctly in labview 8.5 but i converted to LV 2013.
I will research about transparent borders overlapping.
Hi Altenbach:
17% is overall. 3 cores are high % than others.
The problem is at edit mode and also when I run program.
Yes I have many front panel indicators, but I do not think they have tons of data but I will double check.
When I open my VI in labview it shows 118 MB memory when running and 124MB at edit mode
By the way, last week when by mistake I moved a part of code to some centimeters below, block diagram was frozen and was been updated to new position but line by line until complete full screen. I took about 5 minutes to work normally.
I am using 2 monitors in my PC. One to display LV panel and one for LV code.
I meant Tools -> Advanced -> Mass compile and recompile your upgraded code. In the same manner a ctrl+run array will force recompile your program. It can help. Else you're down to e.g. using VI analyzer tool to find the culprit, it might be some VI that's corrupted and needs to be moved to a new VI.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

Using "panelresize.vi" in Labview 2013, in code originally written for Labview 2006.

Hello,
I'm updating code written in Labview 2006 to make it compatible with Labview 2013. My code calls a custom TDMS file viewer vi. This viewer calls a function called "panelresize.vi". This is a NI vi that has been updated since the 2006 version. The new version includes a "help - boolean refnum" in the input cluster, so that the vi now expects a cluster of 9 elements instead of the 8 that I am sending it. I am not sure what this "help refnum" is, how to use it, or how to add this to my input cluster in the calling function so that the error goes away.
Any suggestions?
Thanks!
Attachments:
Untitled.png ‏392 KB

Hi,
it is a help button. You can add a help button to your customized File Viewer. If you don't want this button, you can make it invisible.
What requirements drive you to make your own customized File Viewer?
FYI. In LabVIEW 2013, we made changes to improve the performance of the file viewer. For the compatibility, we kept the panelresize.vi and added a specific panelresize_tdms.vi for this improvement. panelresize_tdms.vi requires more than 9 elements.

Bug in LabVIEW 2013 RTETT Download

I've called this in to NI, but am posting it here in case you've downloaded LabVIEW 2013 before they fix the problem.
Downloading the toolkits from ni.com/trylabview usually is a three-step process. First, you download a "downloader", a small program (154 KB) that manages the download of the Installer. When you run the Downloader, it downloads the Installer, usually as an executable ZIP file. The final step is to run the Installer, which first unzips itself into a folder (by default, C:\National Instruments Downloads), then executes the unzipped Setup.exe contained therein.
There is a (usually) consistent naming convention to these various files. For example, the files for LabVIEW Real Time are 2013RealTime-Eng_Downloader, 2013RealTime-Eng (the Installer), and LabVIEW RT (the name of the folder that the Installer "unzips" into). I've downloaded 8 modules, and (with the exception below) they all follow a similar pattern.
The "bug" is in the Real Time Execution Trace Toolkit (RTETT). The Downloader is 2013RTETT_downloader, and it brings in 2013RTETT as the Installer. However, the Installer is set to unzip into LabVIEW RT, the same folder that is used for LabVIEW Real Time. The "fix" is to change the name of the UnZip folder to LabVIEW Real Time Trace Execution Toolkit (this name is analogous to the LabVIEW Desktop Execution Trace Toolkit name for 2013DETT). Alternatively, you can run one installer, rename the folder, run the other, and adjust the folder names to your liking.
Bob Schor

I am using Windows 7 (x64), fully patched. As I understand it, the purpose of the Installers is two-fold -- to extract themselves to individual folders (by default in C:\National Instruments Downloads) and then to run their respective Setup executable to actually install themselves.
I have not (yet) installed RTETT, but I have installed LabVIEW RealTime. However, in the interest of time-efficiency, I first did downloads of all of the elements I wanted to install (which included both RealTime and RTETT), ran the Installer, but only the "extractor", then planned to run the actual installations from the folders in the Downloads folder. That's when I discovered that the folder labelled LabVIEW RT did not contain LabVIEW Real Time, but LabVIEW Real Time Execution Trace Toolkit. Thinking I'd forgotten to extract Real-Time, I tried extracting it again, and discovered that it and RTETT "shared" the same folder in NI Downloads. I fixed the problem for myself by manually relabelling the folders so one was LabVIEW RT (for LabVIEW Real Time) and one was LabVIEW Real Time Execution Trace Toolkit. With these distinctive names, I'm much less likely to install "the wrong thing".
I consider this a "bug", as NI clearly (and logically) intended for the different Toolkits to be downloaded into their own folders. I mentioned it here in case others faced a similar confusion of "Where did my download folder go?". Note that if you only download Real Time or only download RTETT, the "reuse" of the folder name won't matter to you.
BS

RTD Temperature Measurements using LabView 2013 and MyRio

Hey everyone. I am VERY new to LabView programming and working with a MyRio. I need to figure out how to measure the resistance of a 2 wire RTD to find a temperature utalizing the MyRio and LabView. I am pretty lost on how to do this. Does anyone know some good resources for making the LabView program off of the tops of their heads? I've figured out how to measure from specific pins, but I am not sure how to get it to constantly output a voltage from the output pins.
Eventually, I would like to have it display the temperature as well as have it turn on or off a heater depending on that temperature, but that will come far later in this process. First things first, how do I take temperature measurements utalizing LabView 2013 and a MyRio with a 2 Wire RTD.
Thanks so much!

Hi JoshEpstein87,
The myRIO can't acquire a change in resistance directly, so you'll need to somehow convert the change in resistance to a change in voltage. There are multiple ways to do this, but you'll need to build an external circuit and then read the voltage output with the myRIO. One example of a circuit that allows you to do this can be found here. To output a voltage on the analog output pins, you should just need to set the output voltage and then it will remain at that voltage until you change it or power cycle the myRIO.
To get started with LabVIEW and myRIO programming, see the following page:
http://www.ni.com/myrio/setup/getting-started/
There are some links to LabVIEW training as well as resources about RIO programming. I also highly recommend you check out the myRIO Community as there are example programs on there that you can take a look at to see how they are designed.
Best Regards,
Matthew B.
Applications Engineer
National Instruments

Running Datasocket in labview 2013 open labview runtime engine 7.0

Hello All,
I am trying to communicate with a COGNEX camera using Labview 2013. I am using Datasocket to read tags from cognex OPC server.
but when I open labview and run the code for the first time. An installer will automatically pop up trying to install labview runtime engine 7.0.
When i cancel the installation datasocket throws an error. Again if i run second time, datasocket works fine and communicate with cognex camera using OPC.
This problem comes everytime I open labview and run the datasocket. I cancel the installer. second time onwards when i run the code everything works fine.
This is actually annoying and i doubt how things will work when i make an executable.
Need help.
Is this due to datasocket version installed... how to resolve this.

Hi phil,
That is interesting that you were unable to find the offending key that the installation is having trouble with. Do you have Administrator privileges on your computer? You may even want to try to log in as the actual Administrator itself to make sure that you have access to all of the proper registry keys. Also, I was going to say that I do think you're right with Windows XP not having the Scanreg/fix function, but there are several free programs that you can download as registry checkers. You may want to try one of those to see if you can find the key and give it the proper permission.
As far as the other part of your question, the Run-Time Engines are very important for LabVIEW to be able to run, but the 7.1.1 Run-Time Engine should not be affecting a LabVIEW 8.2 installation as it will use the 8.2 Run-Time Engine. One thing that you can do is go into your Control Panel under Add or Remove Programs>>National Instruments Software and you can try and repair/modify your Run-Time Engine there. If you already have the 7.1.1 Run-Time Engine on your computer, this is where it will show up so you can make any changes you want. Also, if you go to www.ni.com and click on "Drivers and Updates" on the right, you will be able to find the Run-Time Engine there that you will need, but I would definitely try using a downloadable registry checker first before attempting to change any of the software that is currently on your computer. As stated in the Knowledgebase article, this is actually an error from Windows saying that the registry key does not have the proper permission settings, so I am reluctant to say that downloading the new Run-Time Engine from our website will help much. Please try some of these suggestions out and let me know how they work out for you. Thanks!
Regards
Noah R
Applications Engineering
National Instruments

Changer la couleur de font d'un graphique en fonction des données utilisés

Bonjour,
Je cherche à modifier les couleurs de fond d'un graphique comme ci dessous :
On a ci dessus 3 zones de températures correspondant chacune à 1 température différente.
L'erreur pour chaque température étant paramétré par l'utilisateur je dois pouvoir la changer en fonction ce qu'il aura rentré.
Existe il une méthode pour faire ca ??
Merci d'Avance

Bonjour,
Si j'ai bien compris, tu veux remplir le fond entre des valeurs définit par l'utilisateur.
J'ai fait un bout de code qui doit répondre à ton problème. Tu peux sur un graph, définir les courbes avec un remplissage. Le remplissage, peut être par rapport à 0 l'infini et même par rapport à une autre courbe.
Je te laisse jouer avec l'exemple. J'ai rajouté la possibilité de pouvoir changer la couleur de fond de chaque zone.
Exemple en LabVIEW 2012
Cordialement
MaximeR
.mesLeft{float:left} .mesInfo{border-left:solid 1px #989898;font-size:x-small;color:#989898} .mesLogo{float:right;opacity:0.18} .mesLogo:hover{opacity:0.9}
Maxime R.
  CLD - Certified LabVIEW Developer / Développeur LabVIEW Certifié
  CLAD - Certified LabVIEW Associate Developer
Pièces jointes :
MultiZone Graph.vi ‏19 KB

Upgrade motion vi from Labview 7.1 to Labview 2013

Because we have to update our old Windows XP system with Labview 7.1 to a newer operating system, I tried to upgrade to Labview 2013.
The problem is that now our motion system( PXI realtime) doesn't run smooth anymore.
I generate a predefined position profile at 40Hz (This could be up to 3600s long = 144000 samples). In the loop which runs at 40Hz, the profile is corrected by a factor which is calculated every time based on a function using 2 analog input values.
Therefore I cannot use a predefined buffered contour function and adjust the velocity between 2 points so I get a smooth profile
The thing is that running this identical vi compiled with Labview 2013, it doesn't run well anymore (checked this with the interactive display on MAX, and it is very noticable.).
I this due to the old hardware, is the new Labview 2013 RT engine more demanding on the hardware ?
I have almost 2 identical systems (each having a PXI 8184 (850MHz celeron) controller, one with PXI 7340 motion controller and other with PXI 7344 motion controller).
I first want to have one system running well on the new software before I upgrade the other one.
I was thinking on changing my software to use the contour function together with the gearing function.
I would output the result of the function based on the 2 analog inputs to a analog output and use this voltage as gear input to superimpose the corrected profile.
It would be nicer to not having to reroute this value through a analog output and input but I haven't found any other solution for this.
Any help or suggestions to solve this are appreciated.
Tom Versluys - Dept. of Civil Engineering, Gent University
Technologiepark 904, B-9052 Zwijnaarde (GENT), BELGIUM
TEL.: +32(0)9/264.54.87, FAX: +32(0)9/264.58.37, MAIL:[email protected]

Hello Thierry,
I have included a word document with 2 screenshots of the position & velocity from Interactive 1-D: one from the "old" Labview 7.1 system and one from the "new" Labview 2013 system. you can clearly see the difference, the input values for the motion-profile were identical.
I also include the MAX report for the Labview 2013 realtime controller.
The CPU usage for the "2013" PXI-8184 when not running is about 3%, when running its between 33% and 37%.
Memory use is about 60MB (of the 128MB).
If I run a vi on the 2013 hardware with a predefined trajectory (buffered) the motion is also smooth
Already thanks for looking into my problem
Tom
Tom Versluys - Dept. of Civil Engineering, Gent University
Technologiepark 904, B-9052 Zwijnaarde (GENT), BELGIUM
TEL.: +32(0)9/264.54.87, FAX: +32(0)9/264.58.37, MAIL:[email protected]
Attachments:
Screenshot motion_velocity_RT.docx ‏366 KB
ni_support 2013RT.zip ‏75 KB
MAX7_1.zip ‏15 KB

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.

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?

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/

LabVIEW 2013 Changer la couleur d' un onglet

Similar Messages

Maybe you are looking for