Wago 750-841- labview pour piloter le process

Bonjour,
je suis étudiant en stage, je veux mettre sur place une application capable de piloter un système automatisé ( des vannes tout ou rien, pilotée et commandée) via le controleur ethernet Wago 750-841 en utilisant le langage graphique Labview. Je dispose du logiciel CodeSys et mon automate est relié directement au PC, donc je ne suis pas en réseau.
Mon soucis est que je ne sais pas si on peut utiliser Labview dans CodeSys sans etre relié à un serveur pour communiquer avec l' automate wago afin de commander mes vannes et effectuer une supervison des pressions sur le process.
Je sollicite vivement votre aide.
Merci d'avance:smileyhappy :
Transistor.

Merci Yoann, pour ton éclaircissement.
J'ai utilisé CodeSys pour configurer le controleur Wago. Juste une question est ce que par programmation graphique (Labview ou Ladder) j'arriverai à commander mon process, sans passer par internet car je travail en local.

Similar Messages

Programme pour piloter un appareil via adaptateur GPIB-USB

Bonjour,
Nous possédons un appareil HP70004A (avec port GPBI) dans
lequel et intégré un second appareil HP70340A.
Mon problème est le suivant : j’aimerai pouvoir
commander ces appareils via LabView avec un connecteur GPIB-USB mais je n’ai
pas trouver (sur votre site et autre) le programme permettant de le faire.
En revanche je possède un programme en « .id » qui lui n’est pas
compatible avec LabView.
Existe-t-il un moyen pour convertir un fichier « .id » en fichier «.vi » ?
Si oui le quel et comment faire.
Ou alors possédez vous directement les programmes de LabView pour piloter ces
appareils ?
Cordialement.

Bonjour,
Pour ta question, je ne sais pas si cela est possible. Je suis dans le même cas que toi. Je suis en stage et j'ai du commander un multimétre HP34401A via un convertisseur GPIB-USB, qui est pour moi un GPIB-USB-HS de NI (qu'elle est le tien?)
Pour commander ton appareil commence par regarger sur internet si tu ne trouve pas des VI déja crée pour le mettre en oeuvre, si tu ne trouve pas il suffit de regarder dans le doc de tes appareils et de regarder les commande qui lui sont propre.
A-tu déja réalisé un programme simple juste pour réaliser un RESET ou une identification pour commancer ou utiliser Measurement et Automation?
Cordialement.

Has anyone managed to program a Wago 750-650 module attached to a Wago 750-341/841 controller

Hi,
I'm planning to use 2 Wago 750-650 modules (serial to ethernet converter) attached to either a Wago 750-341 or 841 ethernet controller to communicate with a vacuum controller which uses a serial interface.
I wonder if anyone has accomplished this? I have written a small VI using MODBUS commands to try and achieve this but I am unsure how to input commands of longer than 3 bytes and it seems that it is not working yet.
Any tips or help would be welcomed.
Thanks
Keith.

Hello Keith,
Apparently the brackets were accidentally included in the link. Here's the right one:
http://zone.ni.com/devzone/cda/tut/p/id/3141
Kind Regards,
Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
CLD, CTA
If someone helped you, let them know. Mark as solved and/or give a kudo.

Measurement studio et Wago 750

Bonjour à tous,
Je dois développer un programme en C# couplé à un système WAGO 750-341.
Je fais donc des recherches sur les systèmes existant et j'envisage l'utilisation de MeasurmentStudio. Ma question est la suivante :
MesurmentStudio peut-il me fournir la communication avec mon module Wago et donc un accés aux modules IOs connectés ?
Je n'ai pas encore téléchargé de version de MeasurmentStudio, j'en suis à la phase recherche papier.
Merci de vos réponse

Bonjour Nico84,
Votre systeme Wago est il fournit avec des drivers ? Quel genre de communication ou protocole est utilisé pour communiquer avec ce système ?
J'imagine que ce système WAGO est fournit avec des drivers et donc des fonctions qui vous permettront de communiquer avec lui en C#, Measurement Studio vous fournira des fonctions complementaire (contrôles d'interface utilisateur comme des graphiques, des tableaux et des jauges, des fonctions avancées d'analyse des données et des outils de génération de code pour la communication de matériel, etc...)
Je vous invite à prendre contact avec notre service commercial qui pourra vous renseigner davantage.
Je vous souhaite une bonne continuation dans votre projet.
Cordialement,
Eloise
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;}
LabVIEW Tour
Journées Techniques dans 10 villes en France, du 4 au 20 novembre 2014

Error 56 wago 750-341

Hi,
I'm using LabVIEW 7.0 and trying to comunicate with wago 750-341 via ethernet connection. I'm using the standard vi's downloaded from wago's web.
Could somebody help me and explain how to fix this problem?
Best regards,
Aleksandar.

Ummm, it might be helpful if we knew what the problem was that you were having...
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 as a Service - process stays in memory despite finishing execution

I have a fairly interesting/unique problem with trying to run a LabVIEW built executable as a service using srvstart (http://www.nick.rozanski.org.uk/services). Srvstart allows you run any application as a service (similar to srvany or firedaemon) but it has the advantage that when you shutdown the service, you can set it to send a WM_CLOSE message which can be picked up in LabVIEW using the Application Instance Close? filter event and shutdown the service gracefully without killing it (as is the case with srvany).
To debug this, I put a simple file write into the Application Instance Close? and Panel Close? events, my 'Exit' case and in a sequence structure at the very end of my application. If the application shuts down gracefully, a file will be created for at least the 'Exit' case and the the final file write.
When I run the application in the LabVIEW development environment or as a normal executable (by double clicking on the EXE), it shuts down gracefully (by queueing up an 'Exit' command and executing the 'Exit' case) when I close the front panel (which is just an empty front panel - no controls/indicators as it runs without a UI as a service) - it creates the files and the application closes (and the process in task manager disappears).
When I run the application and try to shut it down by using 'End Task' or run the application as a service. This should fire the Application Instance Close? filter event, which is then discarded (with silent shutdown) which will should queue up an 'Exit' command and shut down the software gracefully.
What actually happens is that If I'm running the EXE normally and I 'End Task', the front panel closes but the application process stays in the system (i.e. in task manager). None of the files are written so the application hasn't gracefully shutdown. I then have to kill the process in task manager.
When I'm running as a service and 'Stop' the service, the files for Application Instance Close?, my 'Exit' case and the last call get created, the memory usage goes from 30to 80mb and the process stays in memory (in task manager) - the service doesn't respond and I have to shut it down via task manager. I call 'Quit LabVIEW' right at the end of my VI, just after the last call file is created, if I disable this, the same thing happens but the memory usage doesn't go up. In both cases though, the service/application doesn't respond.
I have to be a little careful about what I post in terms of VIs/screenshots for IP reasons but I'll try to illustrate my setup:
In terms of other considerations, the VI does some asynchronous calls for handling TCP connections but these will finish execution when the main event queue is destroyed and the problem still occurs even if no TCP connections occur (and hence no calls are made to the asynchronous VI). I'm running LabVIEW 2011 SP1 on a Windows 7 64-bit.
I tried to use the Desktop Trace Execution toolkit to help debug the issue but it seems that the VI Server shuts down and doesn't show me any trace information after I tell the service to Stop.
The things I don't understand are:
- If I 'End Task' on the EXE, shouldn't that fire the Application Instance Close? filter event in LabVIEW? I understand that Windows would give a 'This application is not responding...' message if it then didn't shutdown or if I didn't discard the event but I don't understand why that event isn't being captured/discarded on my EXE.
- Why doesn't the process end when the VI has finished executing - even though I call the 'Quit LabVIEW' VI as the last call in my application?
- Finally, why does the memory usage go from 30mb to 83mb depending on whether or not I call the 'Quit LabVIEW' VI (but the process still stays in Task Manager)?
The key one is the second one - as this is the one that stops me from being able to stop/restart the service from 'Services'. I'd like to be able to use my 'Exit' case to try and send a last ditch 'Hey I'm shutting down now' message before the PC switches off by gracefully shutting down my service (and you know - because it's better to shutdown things in a controlled manner - hence the reason for using srvstart in the first place!)
If anyone can help shed some light on this I'd really appreciate it as I've been trying to debug this for a lot longer than I'd like and despite asking around a few people not been able to come to any sort of solution.
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

Since about LabVIEW 8.5 it is a very bad idea to add the Application Close? filter event and expect LabVIEW Quit to still do anything! It simply behaves as No Operation when this filter event is registered in any event structure.
The proper way to handle this is to make the LabVIEW code terminate gracefully (terminate every loop in there) and as last operation close the Front Panel explicitedly with the VI Server method.
LabVIEW Quit is btw. anyhow only a emergency bandaid. It is really analogous to crashing your car in a wall to make it stop. Pretty effective but also dangerous for various reasons. The proper way to terminate a LabVIEW built application is and has always been to make sure every loop has terminated and then close every and any front panel of your application as last measure. An open front panel (even when hidden) will keep your executable alive forever.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Problems with Labivew 2013 / 14 install - Ni Variable Engine error and Labview does not close, processes do not stop when I run Vis.

Hi All,
I am hoping at all my problems are relateded to a problem I am experancing, when I look into my windows 7 (64bit) event viewer near every time I boot up I get an error regarding the NI Variable Engine which reads.
The description for Event ID 0 from source NI Variable Engine cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
C:\Program Files (x86)\National Instruments\Shared\Tagger\ni_tagger_plugin_mxs.dll: Failure to load plugin: Unexpected Error: Unable to get the Interface from the plug-in.
and a second which is the same apart fomr the last line
Unable to load the MXS configuration plugIn: Failed to get MAX Configuration interface for Tagger: 0x80040318
I have tried uninstalling all labview things and I have tried repairing all labivew programs. Along with this I got this error when I installed Labview 2013 so I thougth why not try 2014 and I still get the same problems. I also shoudl point out I use bot 32 bit and 64 bit versions of labivew. I have installed labview on many machines before but never encountered this problem. That being said this was a new clean windows install.
Along with thiese errors labview heardly ever shuts down properly when I close the program it just freezes and needs forshed shut down.
Apart form this I noticed that when I run any of my Vis which I have never had problems with in the past and I stop the program somtiems processes keep using CPU such as "lktsrv.exe"
I really need to get this sorted out because its morstly the crushing and processes not stopping which is rather annoying.
I shoudl also say that these problems are both in the 32bit and 64 bit versions of labview not difference. and no difference if its 2013 or 2014
Cheers

Hi GajanS,
Thanks for your reply sorry I havetn noticed anybody had replied as I stopped hoping for any responce before then.
I have attached a screenshot of the four processes that seems to be giving me a problem.
I have actually managed to find the program causing labivew to crash was in fact my antivirus software which I have now removed and have no more problems with labview crashing on shutdown.
After removing it I tried the repair feature again for all my labview programs but sadly the one persistant problem remaining is still the four processes using around 13% processor each. I have found out this happens sometime after booting up regardless of if I run labivew or not. So it does not directly seem related to the running of any labview applications but rather a bug in the labview software.
the processes are:
lktsrv.exe
tagsrv.exe
nidmsrv.exe
lkads.exe
as shown in the task manager.
I would relaly help if I can get this sorted out.
Cheers
Attachments:
Screenshot 2015-03-24 21.50.00.png ‏12 KB

How to run the LabVIEW exe as background process?

Dear All,
               I want to run my LabVIEW exe as background process, which wont show as the process in the task bar as shown in the .jpeg file.
                I want to run it as a background services as like runs in the windows processes.
                Please suggest me something.
Thanks,
Nishant

Dear Smercurio,
           Thanks for the good one, but it still requires the windows XP or later OS, when i extract the software, it gives me this error.
           Even Fire Daemon software (same one provided by Alessio in this post) is also running the same, and we even dont have to make it Automatic to start at boot up time, it automatically creates the automatic service which also runs at boot time, so not to worry about anything.
Thanks,
Nishant
Message Edited by Nishant on 12-05-2006 10:12 PM
Message Edited by Nishant on 12-05-2006 10:16 PM
Attachments:
rktools error.jpg ‏12 KB
rktools error.jpg ‏12 KB
rktools error.jpg ‏12 KB

Bonjour , je possède une version labview 7.0 je voudrais procéder à l'installation de l'interface labview pour Arduino je n'y arrive pas ,VIPM ne voit pas la version de labview 7.0 Pouvez vous m'indiquer une procédure ? merci cordialement Laurence

Bonjour ,
je possède une version labview 7.0
je voudrais procéder à l'installation de l'interface labview pour Arduino
je n'y arrive pas ,VIPM ne voit pas la version de labview 7.0
Pouvez vous m'indiquer une procédure ?
merci
cordialement
Laurence

Bonjour Laurence,
L'interface LabVIEW pour Arduino n'est disponible qu'à partir de la version 9 de LabVIEW comme décrit ici:
LabVIEW Interface for Arduino FAQ
https://decibel.ni.com/content/docs/DOC-16024
Bon courage
Cindy

Comment creer une interface labview pour simuler une cle hasp

bonjour,
je souhaite creer une interface labview pour simuler une cle hasp.
si quelqu'un sait comment faire je vous remercie d'avance de votre aide

Hello,
Please post this question on the French forums to get a prompt response to your question:
http://forums.ni.com/t5/Discussions-au-sujet-de-NI/bd-p/4171
Regards
Arham H
Applications Engineer
National Instruments

[TestStand][LabVIEW]faire module labview pour teststand

Bonjour,
Je suis a la recherche de tutoriel pour faire des modules LabVIEW pour TestStand.
J'ai trouvé les fonctions TestStand dans LabVIEW "Get Property Value" and co. mais je n'arrive pas à les mettre en oeuvre.
Merci
Résolu !
Accéder à la solution.

Bonjour,
Je cherche à envoyé des requêtes en TCP/IP sur un module 'maison', et récupérer les éventuels réponse. (LabVIEW)
Faire cette procédure en boucle jusqu'a ce que je reçoive une réponse comportant une anomalie, l'arrêter (par ex) et l'inscrire dans un rapport. (TestStand)
J'ai déjà fait le Module LabVIEW, j'aimerai intégrer ce module dans une séquence TestStand pour automatisé l'envoie et la prise de décision en fonction de la réponse reçu.
Donc au final pouvoir choisir ce que j'envoie avec TestStand:
[TestStand: requêtes -> [LabVIEW] -> réponses ]
Assez compréhensible ?
Cordialement,
Anthelme
P.S.: Je dois avoué ne pas avoir compris vos solutions proposé...

Peut-on utiliser le deuxième port TCP/IP de mon NI cRIO pour piloter un appareil de mesure Agilent

Bonjour,
J'aimerai utiliser le deuxième port TCP/IP de mon NI cRIO-9024 pour piloter mon générateur de pulses Agilent 33210A.
Est-ce possible?
Mon appariel ne possède pas de port RS232, mais seulement du TCP/IP et GPIB.
Cordialement.

Bonjour,
Merci pour votre réponse.
Je voudrai untiliser le VISA TCP/IP.
Comme c'est un apareil Agilent il faut activer le passport NIVisaTulip.dll et
celui-ci n'existe pas sous NI-RIO, il a y des passports nom.out.(Cf pièce jointe1).
De toute façon dans un premier temps je n'arrive pas à ajouter un nouveau périférique réseau
à partir de mon NI cRIO (Creat New VISA TCP/IP Resource).
J'ai activer mon deuxième port avec une adresse IP qui correspond bien avec mon appareil.(Cf pièce jointe3)
Il faut bien procéder comme cela ? (Cf pièce jointe2).
Cordialement,
Attachments:
Passports.PNG ‏79 KB
Périohérique réseau.PNG ‏110 KB
Cartes réseau.PNG ‏27 KB

LabVIEW as an in-process COM-server

Hello:
At the moment, I evaluating if LabVIEW is the best tool suitable for my next task.
I would like to know if LabVIEW is an in-process COM server—an ActiveX DLL—that implements the IDTExtensibility2 interface. I am trying to add a COM add-in for a current Microsoft product.
The MS notes also states the following:
Non-modal forms cannot be displayed directly from a COM add-in. If you have non-modal forms, you can have your add-in call an external program (such as a Visual Basic executable) that enables a connection.
Does LabVIEW meet these criteria or do I have to program in VB?-((
Robert

rberger wrote:
> I would like to know if LabVIEW is an in-process COM server—an
> ActiveX DLL—that implements the IDTExtensibility2 interface. I
> am trying to add a COM add-in for a current Microsoft product.
LabVIEW is not an in-process COM server. LabVIEW is started as a
separate process either as development system or as runtime executable
and the Active X interface is out of process to the other application
invoking LabVIEW's Active X interface.
LabVIEW is also not embeddable into other applications through Active X.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Problèmes pour piloter controleur ISEL C 142-1 avec Labview 8.5

Bonjour,
J'utilise un controleur ISEL C 142-1 pour faire bouger un seul axe, mon PC est relié au controleur avec un cable USB-RS-232.
J'ai essayé d'utiliser l'exemple Labview "Lire et écrire série avancé" pour envoyé du code au controleur mais je n'ai aucun résultat.
Il est possible que je n'écrive pas le bon code...
Si quelqu'un à déjà utilisé ce type de controleur, je serai ravi que l'on me vienne en aide.
Merci.
PS: ci joint les exemples de code de programmation
http://www-subatech.in2p3.fr/~electro/infoaq/TISSAGE/ISEL_commande_programmation.pdf

Bonjour dukti999,
Avez-vous pensé à configurer votre port série, pour qu'il soit en accord avec la configuration du C142? Ce lien vers le site ISEL permet d'obtenir plus d'information sur l'utilisation du contrôleur, notamment sur la configuration COM à utiliser:
9600 bauds
8 bits de données
1 bit de stop
pas de parité
Pendant vos essais, avez-vous eu des messages d'erreurs remontés par l'application LabVIEW en relation avec votre application?
Autrement, lors de l'utilisation de LabVIEW (Drivers NI-VISA), je vous invite fortement à utiliser le cluster d'erreur sur chaque VI utilisé, et a utiliser également le VI de gestion d'erreur simple pour remonter tout eventuel problème à l'utilisateur (controleur non connecté, mauvaise interpretation de la commande...).
De plus si vous débutez avec LabVIEW je vous encourage à suivre ce tutorial, qui permet de prendre en main l'outil de développement:
Getting Started with NI LabVIEW Student Training
http://zone.ni.com/devzone/cda/tut/p/id/7466
Instrument Control Fundamentals: Instrument Control Software
http://zone.ni.com/devzone/cda/tut/p/id/4357
Enfin, je vous invite à contacter ISEL pour savoir si des drivers d'instrument ont été développés par leur centre de R&D et compatibles LabVIEW.
Cordialement,
Rémi D.
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;}
>> Les rencontres techniques de NI - Mesures et acquisition de données : de la théorie à la mise en ...

TCP connection error when sending MODBUS commands to WAGO 750-881 controller after 113655 bytes of data have been sent

Hi all,
I am new to the world of labview and am attempting to build a VI which sends commands to a 750-881 WAGO controller at periodic intervals of 10ms.
To set each of the DO's of the WAGO at once I therefore attempt to send the Modbus fc15 command every 10ms using the standard Labview TCP write module.
When I run the VI it works for about a minute before I recieve an Error 56 message telling me the TCP connection has timed out. Thinking this strange, I decided to record the number of bytes sent via the TCP connection whilst running the program. In doing so I noticed that the connection broke after exactly 113655 Bytes of data had been sent each time.
Thinking that I may have been sending too many messages I increased the While-loop delay from 10ms to 20, 100 and 200 ms but the error remained. I also tried playing with the TCP connection timeout and the TCP write timeout but neither of these had any effect on the problem.
I cannot see why this error is occuring, as the program works perfectly up untill the 113655 Bytes mark.
I have attached a screenshot of the basic VI (simply showing a MODBUS command being sent every second) and of a more advanced VI (where I am able to control each DO of the WAGO manually by setting a frequency at which the DO should switch between ON and OFF).
If anybody has any ideas on where the problems lie, or what I could do to further debug the program this would be greatly appreciated.
Solved!
Go to Solution.
Attachments:
Basic_VI.png ‏84 KB
Expanded_VI.png ‏89 KB

AvdLinden wrote:
Hi ThiCop,
Yes the error occurs after exactly 113655 bytes every time. The timeout control I would like to use is 10ms, however even increasing this to 1s or 10s does not remove the error, which leads me to believe that this is not the issue (furthermore, not adding any delay to the while loop, thus letting it run at maximum speed, has shown that the TCP connection is able to send all 113655 bytes in under 3 seconds again pointing towards the timeout control not being the issue here).
I attempted Marco's suggestion but an having difficulty translating the string returned into a readable string, (rightnow the response given is " -# + ").
As to your second suggestion, I implemented something similar where I created a sub VI to build a TCP connection, send a message and then close the connection. I now build each message and then send the string to this subVI which successfully sends the command to my application. Whilst not being the most elegant method of solving the issue, it has resolved the timeout problem meaning I am able to send as many commands as I want. So in that sense the problem has been solved.
If you still have tips on how to correctly read the TCP read output, I would however like to see if I could not get my first program to work as it is slightly more robust in terms of timing.
Modbus TCP RTU is a binary protocol, as you show in your Basic VI, where you format the data stream using byte values. So you have to interprete the returned answer accordingly with the Modbus RTU spec in hand. Now what is most likely happening is that the connection gets hung after a while since you do NOT read the data the device sends as response to your commands. The TCP/IP stack buffers those bytes and at some point the internal buffers overflow and the connection is blocked by the stack. So adding the TCP Read at strategic places (usually after each write) is the proper solution for this. Is there any reason that you didn't use the NI provided Modbus TCP library?
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Wago 750-841- labview pour piloter le process

Similar Messages

Maybe you are looking for