Comunicacion entre opc server y allen bradlley micrologix 1500

necesido comunicar Ni opc server con plc micrologix 1500, debido a que el plc trabaja con red devicenet y el opc server trabaja con red ethernet se me ha echo un poco complicado realizar la comunicacion entre el servidor y el plc Una ayuda es urgente.

Buen día:
Observa los siguientes enlaces:
1. OPC Y MICROLOGIX
2. ¿Cómo Puedo Conectar un PLC Allen Bradly Micrologix 1400 con NI OPC Servers?
El primero afirma que es posible utilizar tu dispositivo con NI OPC Server y el segundo explica paso a paso como configurarlo (procedimiento similar a pesar que el hardware es distinto).
Espero esto ayude
Saludos,
Alejandro | Academic Program Engineer | National Instruments

Similar Messages

  • Micrologix 1400 opc server

    Labview OPC Server doesn't support Micrologix 1400 PLC  ( Allen Bradley)???
    Attachments:
    opc server support.JPG ‏6 KB

    I was able to find the Micrologix 1400 in the list of devices on my NI OPC server software, but it doesn't seem to be on the list in your screenshot:
    I will have to add this PLC to the compatibility list.  For more info on how to set this up, the instructions are located in this KnowledgeBase article.  Unfortunately, this document currently has no English translation, but the pictures should outline this process pretty thoroughly.

  • Lookout communication to a micrologix 1500 via 1761-Net-ENI

    We are running Lookout 5.0 server/client setup. We have a number of Allen Bradley SLC500 we communicate with via ethernet. We have just installed 2 new UV water disinfection units that are controlled with Allen Bradley Micro Logix 1500 PLCs. The 1500s are connected serially to a AB 1761-NET-ENI ethernet module/gateway. After setting up an AB Logix Driver in our Lookout server using the ethernet interface option from the drop down list, I'm still unable to communicate with the 1500. Is there a solution to this problem without running a OPC server to communicate with the 1500.

    Another thing to think about is the '4 user' limit to the net-eni. We had this issue at our facility.
    A vendor brought in a new system, it had seversl MicroLogix's with net-eni's on them. They supplied their own mmi package. It consisted of 2 pc's running RS-View. There was a ControLogix5000 running 'supervisory' diuties, talking to all the micros.
    I wanted to gather some performance data with our lookout server, however it couldn't 'find' the MicroLogix.
    After some calls to AB, we were informed that the net-eni would only talk to 4 devices at a time. 2 of them was to the RS-View pc's, 1 was to the ControLogix5000, and the last one was being used by the PLC Programmer's computer's RSLinx (which he keeps running all the time). so there went the 4 'slots' and Lookout couldn't talk to them.
    We decided that we would do a com request in the ControLogix to get the info, and read it into a register, then talk to the ControLogix with Lookout.
    Rich Anderson
    Anamax Group

  • Unable to access only Read Write addresses of AB Micrologix 1400 PLC using NI DSC and NI OPC server

    Hi,
    I have been using NI DSC and OPC servers (NI and Kepware) to communicate with Allen Bradley Micrologix 1400 PLC (1766-L32BXB). Recently at one  site I found that I could access Process values from the PLC correctly (Read Only tags) but could not access the Read Write Tags at all. The latter are addresses to which it should be possible to write Set (i.e., references) values from MMI or PC software. I am able to do so from the MMI not from the PC software. I get communication error message on the MMI and PC, mentioning the PLC address being accessed (e.g. N7:0).
    Support from the supplier is not available. Hence can anyone let me know if ladder logic could have been written to prevent PC software based access of Read/write addresses (N7:0 to 9 in this case), while permitting access to Read only addresses? Is the problem at the PLC end or OPC server end? Is there a way to get around this?
    Thanks in advance.

    The OPC Server cannot force Outputs so if th registers in question are the outputs of ladder rungs you cannot write to them via the server. The controller will accept the write from the server but will not execute the write. In some cases the server event log will post an error if it is the PLC. Do you get errors when you try to write and if so what are the posted error messages.
    Fred Loveless
    Kepware Technologies
    http://www.kepware.com

  • Can Labview v7.0 talk to a Micrologix 1100 PLC via Lookout Protocol Drivers OPC Server v4.5?

    Micrologix 1100 <-> Lookout Protocol Drivers v4.5 <-> Labview v7.0
    Hello all,
    I am helping a local company to use their existing seat of Labview v7.0 to talk over Ethernet with a new Micrologix 1100 PLC.  We were hoping to use their existing OPC server that came with Labview (circa 2000) so that they do not have to purchase a new OPC server.  Their Labview package is the "NI Developer Suite Professional v7.0 Control Edition" which comes with a "DSC Module" which contains an OPC server called "Lookout Protocol Drivers OPC Server v4.5 (build7)".  This software came out several years before the Micrologix 1100 was born, but OPC is supposed to be a cross-platform, cross-generation standard isnt it?
    So, when I set-up the OPC server, it asks me which type of PLC I have and the only choices are AB_Logix (Micrologix 1500), AB_PLC2, AB_PLC5 (15 different flavors), and AB_SLC500 (5 different flavors).  Can I use one of these that might be similar to the ML1100?  I definitely want to use ethernet, not serial.
    My application is just reading and writing a couple of variables from/to the Binary, Integer and Float data storage locations approx once per second.
    Does anyone see a problem doing this without having to upgrade the OPC server to something that "officially supports" the ML1100 (Like Kepware)?
    Thank you very much!!
    frenchy

    Hi Frency,
     You can always just try the 1500 and cross your fingers!  We could try to speculate on the forum, but a quick test would certainly be a better use of time.  However, I do recommend that if you can upgrade the OPC server to one that supports the 1100 driver you should do so.  Kepware and NI-OPC Servers both support this device.
    Cheers, 
    Brian A.
    National Instruments
    Applications Engineer

  • Connecting a plc without opc server

    hi, can i connect a plc to labview 7.1 (to send and read data) without an opc server, using just an rs232 cable from plc to pc.
    Solved!
    Go to Solution.

    syd_b,
    RS232 is just the physical interface, but it says nothing about the communication protocol. Allen Bradley PLCs use several serial protocols, e. g. the DF-1 protocol. You can either try to implement the protocol by yourself by using VISA calls (good documentation is required) or you can purchase a library. NI doesn't offer an Allen-Bradley library for LabVIEW, but I have found a vendor with a quick Google search.
    Jochen

  • Hello!!!ho​w can I control an omron plc (sysmac cqm1)with an OPC server?I want to adquire a signal controllin​g its amplitude and frecuency.​How can it be done with OPC server?I already have the NI CD of OPC drivers.Th​ank you

    Hello!!!how can I control an omron plc (sysmac cqm1)with an OPC server?I want to adquire a signal controlling its amplitude and frecuency.How can it be done with OPC server?I already have the NI CD of OPC drivers.Thank you

    Hola Jose David, que OPC estas utilizando?, Si tienes comunicación entre tu computadora y PLC pero falla la comunicación entre el OPC y el PLC? La configuración y direcciones entre los dos es correcta? La comunicación es por cable serial?
    Espero tus respuestas
    Saludos
    Benjamin C
    Senior Systems Engineer // CLA // CLED // CTD

  • Do I need rslinks and a kepware opc server

    To get 12 words from an Allen Bradley 1500, over an ethernet link, from an existing Labview 6.1 application, will I need an RSLinks sever and an OPC server such as Kepware?  Or one or the other

    kayr,
    RSLinx would be straighforward using DataSocket.  We use DataSocket quite often to communicate with AB hardware through RSLinx.  You could also communicate directly to the AB hardware using some of the tools available at this site.
    http://www.automatedsolutions.com/products/commab.asp
    Mark

  • How to specify Attribute ID in OPC Server DevicenetExplicit

    I'm trying to set up an Allen Bradley 842D Devicenet Absolute Encoder
    using the OPC server.  The manuals for the device mention that the
    data can be retrieved from the various Attribute ID's in each
    class.  From the OPC Server Help example below,  it starts to
    describe the location of the data desired,  but fails to show me
    where I specify the attribute ID.  For example, lets say in the
    example below,  I now want Attribute 2 or 3.  How does the
    below example tell me how?.
    Since I'm trying to get all this data in via the IA OPC server, 
    I'm not planning on using the DNET Vi's.  BUT.....I did look at
    the "GetIdentityAttrs.vi" and notice that the VI's provided allow for
    Class ID, Instance ID, and Attribute ID.  All of which correctly
    gives me the information I want when I run this VI with the 842D
    encoder.
    From OPC Server Online Help:
    NIDeviceNetExplicit Example
    Suppose you want to get attribute 1 from Class ID 1, Instance 3 of an
    object. Class ID 1 is the Identity Class, where all the identification
    information for the device is contained.
    Enter the background information when you create the
    NIDeviceNetExplicit object, setting the Service Code to 14 and the
    Class ID to 1. From the manufacturer’s documentation, you know that
    GetAttribute only accepts an unsigned integer (USINT) as a parameter.
    The baud rate for the object in question is an 8-bit unsigned integer
    (USINT). To read the baud rate, access the IID3.USINT0 data member.
    From the Above,  this is what how i'm interpreting the configuration:  IID ( Instance ID).USINT (data offset)
    To re-iterate my question:  How do I specify the Attribute ID when using the IA OPC Server DeviceNetExplicit Object? 
    Regis

    Hi Regis,
    The general steps to send & receive the explicit message using the NI OPC Server:
    Configure an OPC item to write the explicit message, you have to set the attribute ID for the GET request message here.
    Configure an OPC item to read the explicit message, you will get the explicit response from it.
    Example: Read the Vendor ID (ClassID=1, InstanceID=1, AttributeID=1, DataType=UINT)
    (1) Configure the NIDeviceNetExp object with the right MAC ID, ServiceCode=14(GET), ClassID=1
    (2) Add an OPC item (Data Member) NIDeviceNetExp1.IID1.USINT0 to write the parameter.
    (3) Add an OPC item (Data Member) NIDeviceNetExp1.IID1.UINT0 to read the Vendor ID.
    (4) Then you get the alarm message in IA OPC server and get failure message in your OPC client , if you have one started allready, because it reads the item automatically.
    The magic action is here: you write the value 1 to NIDeviceNetExp1.IID1.USINT0. (then the attribute ID 1 is set correctly).
    You can get the vendor ID then reading NIDeviceNetExp1.IID1.UINT0.
    2. Example: If you want to get the Serial Number (ClassID=1, InstanceID=1, AttributeID=6, DataType=UDINT)
    Add an OPC item NIDeviceNetExp1.IID1.UDINT0
    You write the value 6 to NIDeviceNetExp1.IID1.USINT0
    You can get the Serial Number in NIDeviceNetExp1.IID1.UDINT0
    So you can conclude that:
    (1) if you write to NIDeviceNetExp1.IID1.USINT0, USINT is the data type used to encode the request message parameter.
    (2) if you read from NIDeviceNetExp1.IID1.UDINT0, UDINT is the data type used to decode the response message.
    Attached you can find an example using LV and  Datasocket to read the Vendor ID.
    Hope that helps with your problem.
    DirkW
    Attachments:
    DNET to OPC Item.vi ‏44 KB

  • LabVIEW and OPC Server

    Hola
    Estoy trabajando con LabVIEW 7 Express, una licencia de LabVIEW OPC Server, y quiero comunicarme con los registros de un PLC de la serie Premium de Telemecanique.  El PLC con el que estoy trabajando habla Modbus TCP/IP, y no estoy seguro de si con el OPC Server del lado de LabVIEW es suficiente para comunicarse con el PLC Premium.  ¿Alguien ha tenido experiencias como esta? ¿Ha logrado comunicar LabVIEW con un PLC que hable Modbus TCP/IP?  ¿Tener el OPC es suficiente para garantizar la comunicacion?
    Gracias
    Alfredo

    Estimado Alfredo,
    National Instruments cuenta con un OPC para Modbus, si tu PLC se comunica por medio de Modbus, no habra ningun problema para establecer dicha comunicacion.
    Saludos
    Alvaro

  • 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

  • Lookout and allen bradley micrologix

    Hi,
    Does anybody know (or have experience) of connecting Lookout to an A-B Micrologix
    1500?
    I guess I could use the RSLink OPC server (or even DDE link) as mentioned
    in another post, but I know that the 1500 is very similar to the SLC range
    so can I use that?
    Thanks,
    John

    Hi Carlos,
    Thanks.
    I would love to see that document. Do you know if you can use Linx Lite?
    John
    "Carlos Barberino" wrote:
    >>"John Dunlop" wrote>>Hi,>>Does anybody know
    (or have experience) of connecting Lookout to an>A-B Micrologix>1500?>>I
    guess I could use the RSLink OPC server (or even>DDE link) as mentioned>in
    another post, but I know that the 1500 is very>similar to the SLC range>so
    can I use that?>>Thanks,>>John>>Hi John,>I've used Lookout with Micrologix
    1500 and you are correct. We can use the>RSLinx OPC Server to communicate
    with Lookout Client and actually I wrote>a document that explain how to do
    that and I'll be glad of sending that to>you if you want. Another option
    is using PLC5 object in Look
    out.

  • Can i use OPC server 5.1 to communicate over ethernet to an SLC505 PLC

    i would like to use the industrial automation opc server to communicate with my Allen Bradley SLC505 over ethernet, but the ethernet or 505 options dont seem to be available, i have used lookout opc server 4.5 successfully to do this, but it requires server explorer to be connected to the server before labview datasocket will work. where version 5.1 connects automatically.

    This particular Allen Bradley PLC is not supported by lookout 5.1 (see documentation) and KB on the web 2ZRB25HW.
    hOWEVER, In the SLC500 object you could select ethernet and have limited success in Lookout 5.0. But this was removed in Lookout 5.1. If you replace the attached file with the 5.1 allbrad.cbx file with the 5.0 CBX file then you will have the same unsupported functionality in 5.0
    Attachments:
    allbrad.cbx ‏221 KB

  • Response time between LabVIEW w/DSC module and RSLinx OPC server hosting FlexLogix PLC tags too long

    We are experiencing communication response time delays between LabVIEW with DSC module and RsLinx OPC Server hosting all FlexLogix PLC tags (around 500-600 tags).
    The nominal response time for the system watchdog is < 500ms, but we occasionally have spikes of up to 1.5 seconds once every few days even when the system is idling.
    Changing more than six PLC connected shared variables at the same time from LabVIEW also causes the watchdog response times to spike above 500ms.
    Our watchdog is programmed so that LabVIEW toggles the watchdog bit to 1 as soon the shared variable event detects that the PLC has toggled it to 0. The PLC, however, waits 300 ms until it toggles it.
    Our system:
    Windows XP SP3
    LabVIEW 9 F3
    RSLinx Opc Server v2.54
    Allen Bradley FlexLogix PLC

    What is your update rate set for in the RSLink OPC server?
    You aren't toggling the same flag from both ends are you?
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • How to read enumerated values from an OPC server via Datasocket

    Hi Labviewers,
    I am using LV8.2 and I am trying to find if it is possible to read enumerations from an OPC server via Datasocket, not just the values.
    I can successfully read a value for an OPC server via Datasocket and I get a value for example 3, is it possible to get the enumeration/string that corresponds to this value i.e. "Open".
    Many thanks in advance
    Dimitris

    Hi Sarah,
    With the input type as variant I get the following response:
    1                                     <-This is the current numeric value of the parameter
    4 Attribute(s):
       'Quality' -> 192
       'TimeHigh' -> 29861723
       'TimeLow' -> -665408304
       'Timestamp' -> 39.238E+3
    With the Input set to         Enum constant I get no values or strings coming back. With the Input set to                Ring constant I just get the numeric value   
    Dimitris   

Maybe you are looking for