Aplicacion Flujometro - OPC Server - Data Socket

Hola a todos:
Estoy realizando una aplicacion para poder capturar los datos de un Medidor de caudal con paleta rotatoria KOBOLD (flujometro) . Cuento con un PLC Micrologix 1200, tengo instalado su OPC Server correspodiente, asi como el Data Socket en una aplicacion industrial ...
Desearia poder realizar hacer una aplicacion sencilla para cerrar una valvula solenoide, cuando el flujometro marca un valor determinado
Saludos
Jorge Poma Deza - LabVIEW Developer

Hola JorgeEPD, para conectarte a tu OPC, solo tienes que indicar la dirección de tu OPC, y datasocket se encarga de la comunicación.
La única limitante que tienes es que vas a tener que realizar una conexión de datasocket por cada elemento de tu OPC Server.
AL solo querer realizar una medición (solo uno de los canales) es probable que con una sola conexión sea suficiente. Hay ejemplos en el find example de cómo usar Datasocket
Para facilidad de manejo de OPC te recomiendo el modulo de DSC de LabVIEW
Saludos
Benjamin C
Senior Systems Engineer // CLA // CLED // CTD

Similar Messages

  • Applicom OPC Server Data Members Identification Help

    I am using an Applicom PC104 Profibus DP card with Lookout. I am using the Applicom OPC Server object in Lookout. When I look/try to configure the Profibus slaves - each slave (equipment) has a bunch of modules associated with it (eg. MODULE0-IX0-0 through MODULE0-IX4-8). How do I know which Module contains the information I am looking for (in this case I am looking for an 4-20 mA analog signal from a pH meter). Any help is greatly appreciated. The document that NI has on "useful consideartions..." did not help. Thanks.
    Sudhi

    1. Which version of Lookout are you using? In an old version of Lookout we might forgot to install the appcyc.dll. That should be in the Lookout folder.
    2. Yes, it would be better to contact Applicom, since they install the server, which has to be configured first, before you can connect with a client (Lookout). To test the server configuration you might use as well our OPC Test Client (Server Explorer, which is installed as well with the latest Lookout 5.0)
    Actually, I have just some minor experience with the PCI-1500PFB which however uses the Applicom 3.4 driver and not the ApplicomIO. Even though, I don't know for sure if the native Lookout applicom.cbx would work with the ApplicomIO. But I assume that underneath you just need to configure
    the PC104PFB with any kind of tool (set EquID, ChanID, Protocol...) and the initialisation has to be started at PC startup.
    I've attached the appcyc.dll, just in case you wouldn't find it on your installation.
    Feel free to add any experience you will make. Other DevZone users might find it helpful.
    Hope this helps.
    Roland
    Attachments:
    Appcyc.dll ‏27 KB

  • Ni hypertrend with opc data socket

    hello,
    i am going to use ni hypertren with labview dsc 8.6 version. i am not using shared variable here but using opc server + data socket i am reading all the channels of data. currently i am reading 300 channels of data over modbus tcp/ip network. all are thermocouple inputs and each module has an 8 channels of array of data which i defined, i tried using shared variable but here i need to create 300 variable for each channel then only i can able to insert these data values to the data base. but using data socket with opc server i can able to group it 8 channels/ module the i can able readuce my data set also it will be traceble one. to inserting data base i am making programming.
    i checked the ni-hypertrend, i gone through the help, my question is can i plot the datas from opc data socket with out using shared variable...?
    Regards,
    Balaji DP

    SOLVED
    I just installed the runtime and copied the exe to the target. That doesn't work.
    After I build a distribution with NI DataSocket component and installing it the copied OpcClient works. Even after uninstalling said distribution...
    /* Nothing past this point should fail if the code is working as intended */

  • Data socket port

    I want to serve data sockets over the internet. I can get them to work over our local network (all the computers are 192.168.1.100, etc), but they're not working beyond our local network. Do I need to forward port requests on our router to enable this (we just have a simple DSL modem and a router)? In Labview, looked under Tools >> Options >> Vi Server Configuration and see Port 3363 listed. Is this the port that data sockets work on? If so, do I just need to configure the router to forward port 3363 requests to my computer that is running the data socket server?
    Alex

    Hi Alex,
    It sounds like you have the right idea. Datasocket uses port 3015, so you should be able to forward requests to this port to a certain local IP address. The links below might be of some help to you:
    Error 63 When Using DataSocket
    http://digital.ni.com/public.nsf/websearch/CE62D869535D602F86256D330060F5F1?OpenDocument
    What Ports Do I Need to Open on My Firewall for National Instruments Software Products?
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/fe6a63983ac8289e86256b22005a067a?OpenDocument
    Hope this helps,
    Travis H.
    LabVIEW R&D
    National Instruments

  • Create OPC I/O server and front panel data socket problem

    Hi all!
    I installed the NI OPC server. When I try to create a new server I/O in a LabVIEW project I don't see the "OPC client" possibility.
    Is something software missing? 
    Other question: I tryed to connect to OPC server using front panel data socket but my problem is same. When I click the numeric control and I go to the "data operation" menu there is no possibility to make data socket connection. 
    I don't know what is the problem.
    I attached two pictures about my problem. 
    Solved!
    Go to Solution.

    Dear vajasgeri1,
    do you have LabVIEW DSC module installed? Without it you will not have the OPC client funtionality.
    And to configure DataSocket binding you need to go to the Data Binding tab in the Properties of a control.
    BR,
    Mateusz Stokłosa
    Applications Engineer
    National Instruments

  • Change what data type data socket requests from OPC server

    I suspect this is a foregone conclusion, however just in case; is there a way to make Datasocket request items from an OPC server in a different data type than variant?
    I have a server that scales integers (native data type) and offers tham as floating point values, however to get those nice floats the client must request the data in the right type. If the client asks for a variant the server will return the integer value (e.g. 2 instead of 2,36...).
    I have not checked whether this is a server behaviour as it must be (according to OPC specs) or if it's just a choice by the vendor (Automated Solutions), but still it may become an obstacle.
    Has anyone implemented OPC Client functionality without using Datasocket (and server for that matter)? Any software componants you can recommend?
    MTO

    Hi Mats
    I once found vi's (..\vi.lib\Platform\dataskt.llb) with different read- and write-types. In fact they are all wrapping up the read- & write-variant functions.
    I use them to communicate with Siemens OPC-Scout and it works. They make life a little easier .
    Hope this helps.
    Thomas
    Using LV8.0
    Don't be afraid to rate a good answer...

  • Use Data Socket vi's to write to a custom namespace OPC server.

    Hi there,
    I'm still having the following problem:
    I'm trying to write an OPC tag to my OPC server that is currently not
    existing in the servers name space.
    Normaly (with other OPC clients) the server fires an event that validates
    and adds such unknown tags
    to the server if they are not existing.
    These event is fired through the labview client, too, but unfortunately the
    parameter that tells the server what
    data type the server should use to register the new OPC item is always zero
    (uninitialized variant typ) instead
    of VT_UI VT_DBL or any other value for a valid typ.
    Does anybody know how to register unknown but type save OPC items to an OPC
    server with LabVIEW 6.1 / 7
    data soket vi's ???

    Hello Bryan,
    The BrowseDeviceList VI was released within NI-FBUS 3.2. For NI-FBUS Configurator 3.1, please unzip the attached file and copy the "addon" and "Ff" folders into "\vi.lib" directory. LabVIEW 7.1 or above version is required for using these addons.
    And for your information, there is a free upgrade (version 3.1.1) for NI-FBUS Configurator 3.1 users. Here is the link to the upgrade kit.
    http://digital.ni.com/softlib.nsf/websearch/00A1614EC291219586256F390020671B?opendocument&node=132070_US
    Hope it helps!
    Regards,
    --Josiane
    Attachments:
    locate_fflv_in_labview82.jpg ‏214 KB
    vi.lib.zip ‏391 KB
    locate_fflv_in_labview71.jpg ‏193 KB

  • Programatically changing data socket IP for OPC

    Hello,
    I am using a string indiactor which is configured with the data socket (OPC lookout) settings. I am having a difficult time changing the IP address of the datasocket URL (ie- lookout:\\172.24.149.2X\LV\digame\Control_Parms) using property nodes. Has any one been able to do this??
    Thanks,
    brad
    Intel Corp
    Brad Whaley
    LabVIEW Certified Engineer

    Brad,
    What version of LabVIEW RT are you running? There was an issue in LabVIEW 6.0.3 the DataSocket VI's could not have different URL's passed through them. E.G. If you had one DataSocket Read in a For Loop that auto-indexed through an array of 10 URL's, you would always get the data from the first URL.
    Also, remember that a number of VI server functions are only available on development machines and not available when built as an executable. Check the online help on the property node to determine whether the property you are using is available at all times or only in development mode.
    Regards,
    Aaron

  • OPC Server does not update data value

    Hello,
    I have a problem with a program that uses an OPC server to comunicate with a PLC.
    It happens randomly, when I update the data, i cannot see any patern, sometimes it happens quickly, sometimes it takes longer...
    The data socket is declared like that:
    hr = DS_OpenEx ("psp://localhost/Server/Automate.405466", DSConst_WriteAutoUpdate, NULL, NULL, DSConst_EventModel, TIMEOUT_OPC_mSEC, &ecr_MW5465);
    And is update like this:
    hr = DS_SetDataValue(ecr_MW5465, CAVT_SHORT, l_buf, 1, 0);
    The function does not return any error, but the value is not updated server side.
    Lookout version is 6.6, the program is made with CVI 8.5.1 and communication is in ethernet modbus. I do not know if further details could be useful.
    Thank you.

    Fred,
    Can you read the value being updated directly from the OPC server?  Usually you can just view the values and see if they are updating. 
    The next thing to check would be to use the shared variable monitor to see if the variables that are bound to the OPC server are updating.  It is under Tools >> Shared Variable >> Variable Manager. 
    Also, when you have the program running, do you get any type of error from reading the shared variable?  If you are seeing an error, it would give us a little more insight into what is going on.
    Brian Coalson
    Software Engineer
    National Instruments

  • Problem with data socket server

    We have developed a program (from LabVIEW 6.1 running on Windows NT) consisting of a main executable and four other executables dedicated to collecting various i/o information. The four i/o executables convert raw data into process data and pass it on to the main executable using Data Sockets. The data is assembled as a cluster, then flattened into a string, which is published to a data socket variable. The data cluster contains a time stamp used by the main executable to verify i/o is being updated periodically (at least once a second). The main executable generates an alarm if the timestamp gets to be more than 5 to 15 seconds old, depending on the expected data. Typically, this alarm never happens, unless an i/o device is powered down o
    r disconnected, or an executable or Data Socket Server is terminated.
    The problem we are is experiencing is that false alarms are being generated, at precise intervals of exactly 5 days, 18 hours, 1 minute, and 1 second. The alarm condition occurs then clears immediately. The only thing I can think of is the data socket is somehow "cleared" for some reason at this interval, causing the main executable to momentarily read a time stamp of zero, and generate an alarm. Is there anything that might be corrupting the data sockets at a long interval like this? The worst thing is that the alarm horn gets falsely triggered, so we are trying to resolve this but can not see anything in any of the code to cause such an occurrence.
    Thanks in advance for your help.
    Brian Hajder
    Despatch Industries
    8860 207th Street West
    Lakeville, MN 55044
    Phone: 952.469.8111
    Fax: 952.469.4513
    [email protected]

    Hello Matt,
    Thank you for reading & responding. I should try to summarize this specific application in a little more detail.
    We have built a manufacturing tool for a customer that is controlled by a single Windows NT PC, for which we have developed 5 executables using LabView 6.1. The main executable provides the user interface. The other four executables are dedicated to control & monitoring of specific i/o devices (serial or IEEE-488). The i/o executables pass data to and receive commands from the main using data sockets. The PC is not on any type of network. The main executable supports an optional SEMI standard host link through its ethernet port, but that is not currently active or connected. A total of 13 data sockets are used, to implement si
    mple "one way" traffic through any socket, making buffering unnecessary. Some data sockets (i/o data to and from main) are updated a few times a second at most, commands from the main may only be updated a few times a day.
    Data from each of the i/o executables includes a time stamp indicating the last valid i/o hardware read time. The main uses this data from each i/o executable to determine whether i/o hardware is responding properly - if the timestamp gets to be anywhere from 5 to 15 seconds old (depending on which i/o is being checked), an i/o failure alarm for that device is raised.
    What seems to be happening is that, periodically, precisely every 496,861 seconds, two or more of the timestamps are found to be too old; I am assuming some external event is momentarily clearing socket data & the zero value timestamps look very old, thus triggering alarms at the exact same second. The alarm conditions clear up in less than one second.
    I wonder what you mean by "the datasocket
    server resetting"? Is this documented anywhere?
    Thanks for plowing through this wordy description, I appreciate any help you can suggest.
    Brian

  • Is there a possibility to retreve Data from the OPC Server with the XML Interface

    Is there a possibility to connect a OPC/DA server with the help of the XML interface with Labview?
    I need to retrieve Data from a OPC Server running on Linux, so i got no Dcom System an I need to use XML. The server is running and with OPC client-tools i can access de different data. So now I want to visualize all Data
    that come from that server on Labview.
    1. Is it possible to realize that?
    2. Is a library or a demo vi available ?
    Regards
    Densel

    Hi Densel,
    Sure, you can use XML within LabVIEW, the question is which syntax do you use?
    Are you able to send the XML statements via TCP/IP?
    Regards, Christian

  • Error 42 occurred when writing to data socket server?

    Hi
    Attached are two programs which use data socket to transfer a boolean value. I want to make sure the value only transfer one time. It occurred error 42 at the test server.vi when it write to the data socket server. How can I solve that? Are there any methods to ensure the data can be transferred one time? Thanks.
    Bill
    Attachments:
    Test_client.vi ‏29 KB
    Test_server.vi ‏47 KB

    I am using LabVIEW 7 and I did not see the error on my machine when I ran your programs.
    From the way you want to transmitt data, I think you need to use TCP/IP instead of datasocket. This way you can be sure that the data only got read once. There are several shipping examples to get you started.
    If you have LabVIEW 7 you might consider using the buffered datasocket. I am not sure if it will work in the way you want so experiment.

  • Why can't I read what I have written to the data socket server?

    Hi,
    I have a problem with DataSocket: I open a socket and in a cycle I read from the socket and write a boolean "TRUE" to the socket. But reading from the socket I always get a "FALSE" value back.
    Monitoring the socket from a second VI where a boolean control is connected to the data socket shows that the "TRUE" value that I write is accepted on the DS-Server.
    Is this a bug or do I miss something?
    Regards
    Tobias
    Attachments:
    readwriteDS.zip ‏17 KB

    hi there
    i'd recommend to use two connections for read and write access (see attachment). The ReadWrite mode does not work properly with DS. you can establish the connections at startup of your app and use them until you are done. when using the URL as a input the server must check for a open connection or create one in each cycle.
    best regards
    chris
    Best regards
    chris
    CL(A)Dly bending G-Force with LabVIEW
    famous last words: "oh my god, it is full of stars!"
    Attachments:
    set_flag_v2_LV7.1.vi ‏43 KB

  • Data Socket Server installation on Labview run-time PC

    How do I install data socket server on a PC with Labview run-time licence only? Is it part of the installer?

    Yes, this will install entire DataSocket software. This includes: DataSocket Server, Manager, and Help.
    Zvezdana S.

  • OPC Server S7 1200 cannot pass data to VI

    Hi,
    I use siemens s7 1200 plc with labview 2011 and Opc server 2012. I can connect to opc server and create tags. Moreover, I am able to see data changes with quick client.
    The problem when I try to create I/O server and bound with shared variable, I pass it to VI. All tags are zero, I believe there is no communication to servers. Although there is no error message. Any suggestions?
    Please see the posts
    Attachments:
    Vi.JPG ‏43 KB
    server.JPG ‏37 KB

    Hello sir,
                   We are too handling a project and stuck with the same problem. The OPC quick client shows the updated value but while using the opc variable in the labview it doesn't shows any changes , So please help as with some good solution.
    AEI_JR wrote:
    I'm late to the party, but if you need to troubleshoot OPC communications, you should start with opening the OPC Quick Client.  Check there to see if you have good connectivity - if it is broken there, you will never receive data to LabVIEW.

Maybe you are looking for