Plantage labview 8.2.1

bonjour
suite a l'achat d'un nouvel ordi, j'ai installé Labview 8.2.1 sur cet ordi. Ensuite, je peux faire tourner un programme, qui marchait tres bien sur l'ancien PC. Néanmoins, sur le nouveau, lorsque je le fais tourner, il y a bug: l'écran reste figé, au bout d'environ 20 minutes, impossible de bouger la souris. Le seul moyen est de le forcer a s'éteindre pour de nouveau pour avoir la main. Ce programme labview marche suivant le principe de machine état.
L'ordi est neuf, et en même temps que labview, j'ai 2 autres logiciels qui tournent, un pour le controle d'un flux de gaz, et un pour le contrôle d'une caméra
j'espere etre clair;
je ne vois pas trop d'un vient le problème sachant que je n'avais pas de bug sur l'ancien pc
romain
Résolu !
Accéder à la solution.

bonjour
le programme utilisé provient du forum http://forums.ni.com/t5/Discussions-de-produit-de-NI/contr%C3%B4le-d-un-laser-avec-une-rampe/td-p/13... ou ci joint
concernat le systme d'exploitation:
windows XP pro
bien cordialement
Romain
Pièces jointes :
Dossier machine.zip ‏147 KB

Similar Messages

Plantage LabVIEW 2010 F4

Bonjour à tous,
Je viens ici vous rapporter un petit bug concernant LabVIEW
2010 (F4).
Lors que l’on a utilisé une définition de type stricte
comprenant un cluster (obligatoire) qui contient lui-même différents types de
données (peu importe) pour créer une constante sur un diagramme et que cette
définition a été supprimée, cette
constante est affichée en transparence sur le diagramme (jusque là tout est
normal).
Si par malheur on a l’idée d’effectuer l’opération « Visualiser
en tant qu’icône » sur cette constante de type cluster, on obtient un
plantage de LabVIEW.
Est-ce un bug connu ? A-t-il déjà été rapporté ?
Problème uniquement sur la version française ?
Cordialement,
Da Helmut

Hello,
Ca ne sert strictement à rien, c'est sur mais ce n'est pas normal que ça plante ! Au pire on pourrait obtenir un message d'erreur...
J'ai fait remonter l'info ici et sur le forum Américain. Après, c'est à voir qui veut augmenter ses stats de CAR au support
Cordialement,
Da Helmut

Mesure avec HP34401A trop lente : 600ms.... une idée?

Bonjour,
J'utilise Labv 8.0, Windows XP, et un multimètre HP 34401A pr faire une mesure de resistance ( en "4 pointes " ou "4 fils"). Mon problème est que je n'arrive pas a faire plus d'une mesure toutes les 600ms (hors j'aurai besoin d'en faire une au minimum toutes les 100ms). En le configurant pour une mesure de resistance "normale", ou en mesure de tension, il est guère plus rapide ( 400 à 200 ms ).
Il doit y avoir un ou des paramètres que je configure mal. Je n'utilise peut etre pas les bons Vis non plus.
J'ai essayé ceux fournis dans les exemples de la bibliotheque ( ainsi que de désactiver l'autozéro comme conseillé ) mais sans réussite...
Si quelqu'un a une solution, meme si elle n'est pas pr une mesure de résistance 4 pointes, elle est la bienvenue ....!
Merci,
Marc
Attachments:
HP VI.vi ‏40 KB

Bonjour,
Mes tentatives pour ouvrir votre VI se sont soldées par une succession de
plantage LabVIEW… Je ne puis donc pas me pencher sur votre code.
Néanmoins, il existe certains facteurs qui ralentissent l’acquisition,
et ce, pour tout type de données.
Vérifiez que votre système est bien propre et robuste (faire
tourner plusieurs applications en même temps ralenti l’acquisition), vérifiez
que dans votre code, il ne subsiste aucune opérations inutiles dans la boucle d’acquisition…
Typiquement, les phases d’initialisation, de lancement, d’arrêt et de
suppression d’une tâche doivent être positionnées à l’extérieur de la boucle d’acquisition
afin de ne pas la ralentir.
Concrètement, il ne doit rester que le strict minimum dans
votre boucle (DAQmx_read par exemple)
Cordialement,
BRAUD Jean-Philippe
Field Sales Engineer - Nord et Centre France
LabVIEW Certified Developper

LabVIEW 2010 F2 - Plantage - Problème de localisation ?

Bonjour à tous,
Je rencontre un comportement assez bizarre de la part de LabVIEW. En effet celui ci plante lorsque je passe d'un noeud de propriétés (VI Server) à un autre.
Pour reproduire le comportement placez un noeud de propriétés de VI Modifications:VI (CTRL+SHIFT+B). Reliez la sortie de ce noeud de propriétés à une structure condition. Jusque la tout va bien vous obtenez ce diagramme (plus ou moins ) !
Seulement, maintenant si vous changez la propriété Modifications:VI pour Modifications:Face Avant, soit LabVIEW plante, soit il affiche la flèche brisée et si l'on clique dessus, ou tente de sauvegarder le VI, créer un extrait de VI etc...On obtient dans tout les cas l'erreur suivante :
FPSane.cpp ligne 442
Est-ce un bug de version localisée ou un bug pour toutes les versions de LabVIEW ? Si oui y'a t'il déja un CAR en cours ?
On peut contourner ce plantage en créant directement le bon noeud de propriétés et en le reliant ensuite à la structure condition, mais au milieu d'un développement c'est exaspérant.
VI de test téléchargeable ici
Cordialement,
Da Helmut

Bonjour,
Brice et moi même avons remarqué le problème. En effet, dès lors que la représentation de la valeur de sélection de condition est changée en un certain type, il apparait soit une erreur, soit les différentes conditions ne sont pas mises à jour.
La version 2009 FR de LabVIEW accepte le type quad non signé en sélection de condition, ce qui n'est pas le cas de la version 2010 FR.
Ceci étant, nous ne savons expliquer cette erreur et recherchons l'origine du problème (localisation, ou toute version).
Cordialement,
Romain 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;}
>> NIDays 2011, le mardi 8 février au CNIT de Paris La Défense

Fichiers interactifs sous labview comment faire?

Bonjour,
Dans le cadre d'un projet que j'ai déjà developpé, je souhaiterais créer une base de données sour la forme d'une gestions interactive de fichiers. je m'explique. à chaque lancement du programme, j'entre les caractéristiques de l'examen à venir, il s'agit d'une base de données patients: , identifiant, pointure, age, taille poid. a la fin de l'examen, les données acquises sont enregistrées dans un fichier Exel dont le nom est l'identifiant.
a chaque interruption de labview, ces données sont perdues.
D'une part, je souhaiterais pouvoir garder en memoire les dernieres caracteristiques en cas de plantage ou de relance du programme, eventuellement les corriger. mais aussi pouvoir acceder a chaque lancement, à un menu deroulant pour aller chercher un identifiant passé, par exemple pour un patient revenant pour un controle et donc pour eviter de tout reentrer manuellement.
Cela peut paraitre simple à certain mais je ne sais pas comment m'y prendre. je suis débutant, je le precise, même si j'ai developper un programme complet et fonctionnel.
Merci à vous tous pour votre aide

Bonjour Giacomini,
Tout d'abord, par quel moyen enregistres-tu les données dans le fichier Excel ? ActiveX, Report Generation TK ou simples fonctions d'E/S sur fichiers ?
Dans tous les cas, si tu perds tes données dans LabVIEW, c'est normal. Tous les espaces mémoire alloués dans LabVIEW sont vidés lors de la sortie. Si tu perds tes données Excel, c'est que le nécessaire pour sauver les fichiers n'a pas été fait.
Enfin pour ce qui est de récupérer les fichiers des patients a postériori, il est possible de faire quelque chose comme suit :
Cdt,
Rik.
Eric M. - Application Engineering Specialist
Certified LabVIEW Architect
Certified LabWindows™/CVI Developer

Open and close multisim contact with LabVIEW

Can I open and close multisim contact with labview and read the receptor estatus (p.e. lamp)?
Thanks.
Attachments:
Dibujo.JPG ‏13 KB

Hi Guddan,
I created a RFC having a query which is taking a long time to execute. So i want to close RFC connection with portals which is via java connector(JCO) before that query and open the connction again after that query.
I guess i will need to understand your requirement a little more in detail, as i understand you have an RFC which has a query within to fetch some data and is taking a long time to do so. In the meantime you don't want to keep the connection open?
My question would be, Is the role of this RFC to only execute the query and fetch the data or does it do something else?
If it does other things and these are independent of the query execution, then you can span a parallel call within the RFC to execute the query and in the meantime the RFC does the other things (or vice versa) hence reducing the overall time taken.
If the sole purpose of this RFC is to execute the query, then you will not be able(i mean to say there is no simple and direct way of doing this) to close the connection after the Query is started and re-establish the connection after its execution, for a simple reason that - how will you know if the query has completed it's execution, so that you can establish the connection back.
Alternate solutions, make this a two way asynchronous call, 1) You invoke the RFC asynchronously and close the connection, the RFC in turn will execute the query and transfer the data to JCO via another RFC call.
If this needs to be a synchronous call, then you will need to optimize the query to its best.
Regards,
Chen

LabView Exe Application file not launch Excel application for report generation

Dear All,
I created one LabVIEW application file for report generation (using Excel Template).
While I run the program in programming mode it works well and create the report file in the specified path.
After creation of the application file(exe), it gives the correct path of where the excel template is placed. The same path is given to New Report.vi, but it gives the error 'File Not Found'.
Tell me, is any other configuration required for generating Excel reports? (During exe application mode)
Give me the solution.
Thank You
Jegan.

Hello,
Most likely you are encountering a problem of stripping and/or building paths. Probably the easiest thing to do is put a couple indicators on your front panel for the path or paths you care about, build your exe, and make sure you are really using the path you'd like. If you always put the report at some deterministic place relative to the exe (that is, even it the exe is moved, it will go with the exe and remain in the same relative path location, then you can use the Current VIs Path funtion found in the ... File I/O -> File Constants palette as a start path (where you will want to strip at least the exe name off of course).
I think this will bring some clarity to the issue!
Best Regards,
JLS
Best,
JLS
Sixclear

Error involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
Any ideas ?
Greg Klocek

Why do I get "The exception Privileged instruction (0xc0000096) occured in the application" error message when exiting LabVIEW 6.1?

I have created a vi that uses the LV-GPIB and database connectivity vis. The program runs fine and it ends execution by running the "Close Database Connection.vi".
After closing out my front panel windows and exiting LabVIEW 6.1, I get an error dialog box that reads the message "The exception Privileged instruction (0xc0000096) occured in the application". What does this error mean and how do I resolve it?
Thanks,
Taf

Hi Taf,
Given the broad scope of your application, it may be best to try and isolate the problem down by taking out parts of your application and simplifying it down as much as possible until you can get a consistent version that throws this exception. I would first try to take out either the GPIB or database connectivity portions of the application to narrow down our problem. This error generally occurs when accessing DLLs and external applications, so I wouldn't be surprised if it's the GPIB or database. Let's try to see exactly which one it is and then we can dig deeper into that part of the code. Thanks for your cooperation!
Jeremy L.
National Instruments
Jeremy L.
National Instruments

How to run downloaded drivers on Fresh Install of Labview 6.1 on a Mac G4 OS 9

I have just completed a fresh install of Labview 6.1 on an Macintosh G4 running OS9. I can run it and it seems to work just fine. I downloaded some drivers for an oscilloscope (HP 546XX) to run with an HP 54603b. When I installed, I went to open the 'Get Started.VI' I get a freeze and have to force quit out of labview. I am not sure how to resolve this. I am pretty sure that it is independent of the device, since I can open the vi's at least on another computer with no hardware attached. So I guess to boil my situation down. I have 2 questions:
-How do I get a fresh install on a mac G4 OS 9 to run downloaded drivers from the internet
-How do I ensure that I have the hardware configured on
a macintosh to run properly.
I really have little experience with macs so I am not really sure what my options are or what could be the problem so any assistance would be much appreciated.

Hmmm. I wonder if NI-VISA isn't installed correctly on this machine.
When LabVIEW loads a VI that uses a VISA name control on the front panel, it queries VISA for the installed devices. Sometimes this takes a few seconds, but maybe in your case, something has been corrupted and it's hanging.
To try to narrow this down, first run the separate program "VISAConfig". This should list your devices. If this works, this means it's pretty likely that VISA is installed correctly.
Next, run LabVIEW. On an empty front panel, select the "Controls->I/O->VISA Resource Name" and place it on the front panel. When you click on the arrow on this control, you should see a list of your devices. If this works, then that indicates that LabVIEW is successfully talking
to the VISA software.
If both of those succeeded, then we have to take a closer look at this particular instrument driver. Can you drop other VIs (say, Initialize or Close) without hanging?
If either of the first two steps fail, I'd suggest that you reinstall the VISA software. You may want to try the latest version of NI-VISA (from ni.com), but first confirm that it supports LabVIEW 6.1.
I hope this helps.
Brian

Convert PXIe-8135 controller to dual-boot Windows 7 and LabVIEW RT

Hello. I have a PXIe-8135 controller that originally was just running Windows 7. We are trying to convert it to a dual boot system to also run LabView Real Time. (There is host computer that will run LabVIEW 2014 with the RT module, and the controller will become a target).
I have created a FAT32 partition on the hard drive of the controller. Now, I’m trying to install the real-time OS with a USB flash drive made using the MAX utility, but I cannot boot using the USB drive for some reason. I keep getting the message “waiting for USB device to initialize”.
In BIOS, legacy USB support is [ENABLED] and boot configuration is set to [Windows/other OS]. I’ve tried removing the drive, waiting, and reinserting. I’ve tried two different USB drives (both 8 GB, different brands).
I’m not sure what to do next. Apart from the USB boot issue, is converting the PXIe-8135 even possible? I read about SATA/PATA hard drive issues with older controllers, but I don't know about this one.
Thanks, in advance, for your help!
-Jeff
Solved!
Go to Solution.

Per Siana's licensing comment, more information on purchasing a deployment license if you do not have one for this target can be found here.
The RT Utility USB key is used to set up non-NI hardware with LabVIEW Real-Time, but you should not need it in this situation to convert to dual-boot (*). Try this:
1. Since you already have a FAT32 partion created, go into BIOS setup and change to booting 'LabVIEW RT'.
2. The system will attempt to boot LabVIEW RT, see that the partition is empty, and switch over into LabVIEW RT Safe Mode. (this safemode is built into the firmware, which is why you don't really need the USB key).
3. The system should come up correctly and be detectable from MAX, and you can proceed with installing software.
4. To switch back to Windows, go back to BIOS setup and choose 'Windows/Other OS'
(*) One area where the USB key is helpful on a dual boot system is with formatting the disk. If you want to convert from FAT32 to Reliance on the partition designated for LabVIEW RT, the USB key lets you attempt to format a single parition and leave the rest of the disk untouched. If you format from MAX, the standard behavior is to format only one RT partition if found, but if not found, it will format the entire disk. Formatting from MAX on a dual boot system is consequently riskier and you could lose your Windows partition.

Some fonts are not shown correctly in LabVIEW 2012

I found a bug related with fonts in LabVIEW2012 f3 KR.
- When I select NI7SEG in font selection dialog, right font is not shown in the example box.
- Draw text at point.vi shows same problem for some fonts while other fonts are working.
I reported it to Korean NI. As far as I know, this was not reported in previous versions and I couldn't find any related documents in Google.
So, here I would like to know whether it is related with only Korean version. Please let me know if English version is OK.
* OS: Windows 7 32bit KR

Just now, I installed LabVIEW 2012 f3 (32-bit, English) and checked for the issue. But the font(NI7SEG) was not shown properly in VI either.
- Both of Korea and English version of LabVIEW 2012 on Win 7 Korea OS shows wrong results. It is same on 64-bit OS.
- LabVIEW 2010 but on same PC shows correct fonts.
Is there a limit of number of fonts in LabVIEW? There are more than 100 fonts are shown in the "Selection Font" dialog and I can divide them into 3 groups by sequential order. I find that all fonts in the 3rd group are not applied correctly.
(1st group)
Arial Unicode MS...
Bookshelf Symbol 3....
Windings 3
(2nd group)
@Arial Unicode MS...
@Terminal
(3rd group)
Arial...
Consolas...
Courier...
Licida Console...
NI7SEG...
Verdana

Comunicação entre Labview e ANSI's.

Estou definindo Projeto de Graduação e estou interessado em trabalhar na integração entre Labview e ANSI's na análise de elementos finitos. Gostaria de saber se alguém possui alguma informação sobre o tema.

Voce poderia ser mais especifico com relacao a informacao que voce esta precisando?
Atenciosamente
Filipe A.
Applications Engineer
National Instruments

Implementar protocolo de comunicação serial UART no LabVIEW

Boa Tarde,
Estou querendo implementar o protocolo de comunicação serial UART no LabVIEW.
A descrição do projeto é mais ou menos essa:
- Uma Interface no LabVIEW para receber o dados enviados pela serial UART;
- Uma DAQ NI USB-6212 irá receber o dado por um pino digital ou analógico (a princípio estou usando um pino analógico);
- Um microcontrolador que envia dados através da serial UART;
- Sistema operacional Windows 7;
Estou querendo implementar o protocolo de comunicação pelos motivos:
- Usei o Visa da comunicação serial e um cabo USB-Serial genérico, mas não consegui taxas de recepção rápidas como eu preciso, quando eu tentava transmitir dados de forma mais rápida, eles chegavam corrompidos;
- O exemplos que encontrei do protocolo implementado usam o LabVIEW FPGA, e pelo que eu li minha placa de aquisição (NI USB-6212) não suporta FPGA.
Tem algum exemplo ou sugestão de como devo proceder.
Desde já agradeço.
Atenciosamente,
Fernando Esquírio Torres

Good morning, Fernando,
Here are some links to help in its implementation. Any questions please contact us.
What Is the Basic Architecture for Serial Communication?
http://digital.ni.com/public.nsf/allkb/E0D95CB9249FB8CF86256C68007B1F81?OpenDocument
Can I Do 9-bit Serial Communication Instead of 7 or 8 bits?
http://digital.ni.com/public.nsf/allkb/3BDC7FF03541F772862564990057F919?OpenDocument
9-Bit Serial Writing in LabVIEW
http://digital.ni.com/public.nsf/allkb/E0D95CB9249FB8CF86256C68007B1F81?OpenDocument
Serial Communication Starting Point
http://zone.ni.com/devzone/cda/tut/p/id/4049
Serial Communication - Basic Serial Write and Read
http://zone.ni.com/devzone/cda/epd/p/id/2669
Enviar ou Receber Dados Binários / Hexadecimais Utilizando NI-VISA no LabVIEW
http://digital.ni.com/public.nsf/allkb/33C1056D66078118862577450061E683?OpenDocument
Sending and receiving serial commands using VISA
http://zone.ni.com/devzone/cda/epd/p/id/2423
Sincerely,
Mauro Vera
Applications Engineer
National Instruments

Como controlar um motor de passo com labview?

Olá, espero estar perguntando na categoria correta.
Sou iniciante em LabVIEW e preciso construir um programa que controle um motor de passo conforme digito quantos passos ele deve andar. Daí gostaria de uma luz sobre como fazer isso.
Na verdade, o plano total é, para cada quantidade de passos, verificar a posição do equipamento (através de um outro software conectado ao LabVIEW) e, assim, traçar gráficos passos x posição, mas isso fica para depois; primeiro gostaria de um tutorial, alguma coisa que me ajudasse a controlar o motor.

Bom dia,
Esses dois termos são um pouco parecidos com o dilema dos termos sensores e transdutores, isso porque as pessoas às vezes acabam usando ambos como sinônimos e isso gera uma grande discussão sobre as pequenas diferenças de significado. No entanto, se você trocar a palavra sensor por transdutor ou vice-versa, muito provavelmente você será entendido.
O significado exato do termo controlador ou driver vai depender muito do contexto que você o está usando, por exemplo, se eu estou falando de controlador no contexto sistemas de controle, ele provavelmente entendido como "compensador" (exemplo um compensador PI, PID, entre outros). No entanto, em algumas áreas os termos podem se confundir, como é o caso de quando estamos falando sobre um equipamento que aciona algum motor ou equipamento. A pequena diferença nesse último contexto é que quando se fala em driver, entendo como um dispositivo que tem além de um compensador (seja ele de malha fechado ou não), tem uma eletrônica de potência para o acionamento do dispositivo.
Espero ter ajudado a esclarecer um pouco mais sua dúvida.
Atenciosamente,
Plínio Costa
Application Engineer
National Instruments Brazil

Plantage labview 8.2.1

Similar Messages

Maybe you are looking for