Jump to content

Micrologix 1100 and LabView

Ricardo de Abreu

By Ricardo de Abreu,
in LabVIEW General

 Share Followers 0

Recommended Posts

Ricardo de Abreu

Ricardo de Abreu 0

Posted
Posted

Hi Guys, I'm with a trouble here.

 

Recently we started to get our outdated temperature test cabinet to work, and the best way is to upgrade our PLC. But there cames 2 problems, the biggest is the budget, we do not have any money so we have to work with what we already have, and the second, i'm intern here and there is no one from automation to guide or help me.

 

Now lets face the problem.

 

PLC Allen Bradley micrologix 1100

cards: 1762-IQ16 and 1762-IQ8W6

 

My first thought is to use Labview to control the PLC, as HMI and data-logger without OPC server to simplify the instalation and cost.

 

The communication: this is really where the problems begin. It will be done through Ethernet. I could not manage Ethernet/IP driver to work, nor pcc or CIP message...

 

which is the best way to communicate?

CIP Message, OPC, or any other i do not know? Do you guys see any problems to make a dataloger without OPC?

 

Some things I have tryed

 

Implementation of Common industrial Protocol (CIP) via EtherNet [EtherNet/IP (CIP)]

https://lavag.org/topic/6104-industrial-ethernet-ethernetip/?page=1

 

Ethernet/IP Driver for Micrologix 1100

https://decibel.ni.com/content/docs/DOC-13024

 

EtherNet/IP Driver for Industrial Communication

https://decibel.ni.com/content/docs/DOC-4065

 

 

Thanks for any help

Ricardo

PS. Originally posted at: https://decibel.ni.com/content/thread/47497

Link to post
Share on other sites
Tim_S

Tim_S 70

Posted
Posted

Nothing like the fun of a Frankenstein project.

I've gotten a ControlLogix processor to talk Ethernet/IP with LabVIEW using NI's Ethernet/IP driver (http://sine.ni.com/nips/cds/view/p/lang/en/nid/209676) by setting up remote I/O device in the PLC and a matching assembly in LabVIEW. I was able to get tags to work, but they were too slow (7 msec per tag and I had 100+ tags, and writing collections of tags (tag composed of tags) required expert knowledge that is not well published.

The other way I would recommend is to use something like KepServerEX which handles the communication and provides an OPC interface to LabVIEW.

If all else fails (and if cost is an option), the PLC has a RS232 port. If the PC doesn't have a RS232 port, then a USB-to-RS232 is cheap.

Link to post
Share on other sites
Ricardo de Abreu

Ricardo de Abreu 0

Posted
  • Author
Posted
18 hours ago, Tim_S said:

Nothing like the fun of a Frankenstein project.

I've gotten a ControlLogix processor to talk Ethernet/IP with LabVIEW using NI's Ethernet/IP driver (http://sine.ni.com/nips/cds/view/p/lang/en/nid/209676) by setting up remote I/O device in the PLC and a matching assembly in LabVIEW. I was able to get tags to work, but they were too slow (7 msec per tag and I had 100+ tags, and writing collections of tags (tag composed of tags) required expert knowledge that is not well published.

The other way I would recommend is to use something like KepServerEX which handles the communication and provides an OPC interface to LabVIEW.

If all else fails (and if cost is an option), the PLC has a RS232 port. If the PC doesn't have a RS232 port, then a USB-to-RS232 is cheap.

 Hi Tim.

the velocity is not that important. it will be just a data logger of a single point.

It has to read 4 Temperatures + Oximeter + State and write some actions, as turn on the resistances, close door, etc...

 

do you still have your project or a sample (with PLC scada). I don't know how to set up remote I/O device in the PLC.

 

Thanks a lot

Link to post
Share on other sites
Tim_S

Tim_S 70

Posted
Posted

In LabVIEW the Help->NI-Industrial Communication for Ethernet/IP has all of the information. There were three VIs I used: open, get/set and close. The important part was using the same assembly ID as configured in the PLC. Otherwise, I just used the shipping examples to test out communication. If you're not worried about speed, and all your data types are simple, then I recommend using tags.

Link to post
Share on other sites
Ricardo de Abreu

Ricardo de Abreu 0

Posted
  • Author
Posted (edited)
On 9/2/2016 at 11:40 AM, Tim_S said:

In LabVIEW the Help->NI-Industrial Communication for Ethernet/IP has all of the information. There were three VIs I used: open, get/set and close. The important part was using the same assembly ID as configured in the PLC. Otherwise, I just used the shipping examples to test out communication. If you're not worried about speed, and all your data types are simple, then I recommend using tags.

Tim_S, thanks for help.

The speed is not the point, as the temperature varies slowly. It is the only data I really need (4 points). I need the oximeter data and some digital inputs, and outputs. not too complicated.

you said i have to use tags, but Micrologix 1100 does not suport tags, it works with the address (ex. N7:0). I manage it to work with Advanced HMI using the address. Now keeps the problem with LabView.

 

Edited by Ricardo de Abreu
Adding information
Link to post
Share on other sites
Tim_S

Tim_S 70

Posted
Posted

I used tags with a ControlLogix processor, which is the difference between a Yugo and a Ferrari.

Without tags you would be left with setting up Assemblies in LabVIEW which the PLC communicates to as remote I/O. With the ControlLogix processor the PLC looked at the PC as if it was a valve stack, point I/O, drive, or similar device.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Followers 0
Go to topic listing

  • Similar Content

    • Abel_Souza
      Error 66 on Modbus Master.lvclass:Read Holding Registers.vi
      By Abel_Souza
      LabVIEW 2016
      Modbus Communication with a PLC Siemens SIMATIC ET 200SP
      Windows 7 Ultimate
       
      Hi,
       
      When I run my code it return error 66 at Read Holding Registers function. I ran this code as a VI on the development virtual machine and as a *.exe on real machine, but received the same error.
      Try in another computer and receive the same error.
      As PLC code was developer by other programmer I ask him if this communication was working on his machine, he showed me a LAbVIEW code running with Modbus communication with the same PLC. He was using a LabVIEW 2013 with old Modbus Library, but I had taken his code and ran on my PC with LV 2016 and receive the same error on MB Ethernet MAster Query Read Holding Registers(Poly).vi. Also generate an exe file and run on my real machine and still receiving error 66.
      In all scenarios I can ping PLC and receive answers, but cannot read or write any data with LabVIEW.
       
      First picture is my code with LV 2016 VIs.
      Second picture is error message.
      Third one is the other programmer code with old Modbus Library.
       

       
      On the first code, if I remove Read Holding Registers VI and connct wires directly or put a property node to set any property it runs without errors. If change this function for any other modbus function return error 66.
       
      Any idea what I am doing wrong?
       
      Thanks in advance!
      ni_support.zip
      Comunicação CLP.vi
      Main_MB_2.vi
    • Gan Uesli Starling
      Allen Bradley PLCs
      By Gan Uesli Starling
      I am assigned to refurbish an airflow instrument having six pressure sensors, four temp sensors, and six on/off outputs. By preference I would use all NI hardware, but this isn't going to be allowed. I'm being pushed toward installing an Allen Bradley PLC instead. I am aware of another, much more complicated liquid flow test stand which, so I'm informed, uses LabVIEW for SCADA on a Seimens PLC. This being the case, cannot I do likewise with Allen Bradley? Can I do it entirely in LabVIEW? Or is something like that always just LabVIEW sending trigger commands and receiving data from a free-standing program written in the PLC's own native SCADA?
      I'll be starting from scratch, with nothing yet purchased. I can purchase whatever I choose. I have perused a couple of PDFs of Allen Bradley ControlLogix programs, and at first glance, to me they look like a major pain. Unlike LabVIEW, almost nothing shows on any one screen. Nothing at all looked to have been nested into a subroutine. I liked ladder and highway diagrams quite well enough back in the 90's when printed out on D-size vellum. Then, at least, I could stand back and see the whole thing. The same thing seen only through a tiny window that you have to scroll up and down I'm not looking forward to learning at all. Thus my hope for a LabVIEW solution, rather than purchase and learn AB's Studio 5000. I'm an old dog, and this looks like a new trick to me.
    • CarlosLuevano
      EtherNet IP toolkit to use for point I/O Allen Bradley
      By CarlosLuevano
      Recently I downloaded EtherNetIP toolkit and I do not know how to use.
      I have to read and to write values into the point I/O Allen Bradley to control some devices from PC to point I/O.
      It will be useful if you can help me with some examples. I used Get Atributte Single.vi but I do not know What are Class, Instance and atributte inputs in VI.
      For example a input in the point I/O is a emergency stop and I need to monitor this input from PC, but I do not how to use the tookit. Another example is I have to active some actuator (output point I/O) from PC.
      I appreciate you can give me information.
      Thank you.
       
    • dterry
      Advice on OPC
      By dterry
      Hello all,
      I recently was presented with the task of integrating a Mitsubishi PLC into our systems. After a good deal of googling, I think the best (maybe only) way to get the data out is going to be via OPC, thanks to their proprietary Melsoft protocol. If anyone else knows a better way, feel free to stop me here.
      Now, we are currently expanding our data generating capabilities (hence the PLC), and I have been thinking about rearchitecting the way we collect data from all over our facility to be more flexible.  Since I may be required to use OPC anyways, I was considering using an OPC server to aggregate all of the facility data, and then redistribute to control rooms, historical logging, etc.  To do this, we would need to integrate our cRIOs and operator PCs into the OPC environment as well.
      I don’t see OPC mentioned very often (in fact it returns 0 results on LAVAG), and a lot of the stuff I see these days seems to be more “roll your own” or lower level (raw TCP/UDP, 0MQ, Network Streams, Transport.lvlib etc.) rather than a monolithic abstracting bridge like OPC. Unfortunately, I won’t have time to roll my own in the near future, but LVRT supports supports OPC UA, so I could potentially integrate the cRIOs fairly easily.  Unfortunately, I think I would have to use LabVIEW DSC (or datasockets...) to integrate the PCs.
      I would be very grateful if anyone has the experience to comment on the following or anything else related to using OPC.
      What are viable update rates for OPC tags?  I will need at the very (very) least 250 ms update rates.  Is OPC typically low latency (time from data generated to to client received)? Does anyone have a recommendation for a product (NI OPC, Kepware, etc.)? Is OPC still popular, or are there other options for data aggregation that would be better suited to a new application? What are the options for logging and alarming with OPC? What are the options for talking to OPC from LabVIEW? How robust are the OPC connections in regards to reconnecting if a wireless connection is temporarily lost? Thanks in advance!
    • Ricardo de Abreu
      Micrologix 1100 and LabView
      By Ricardo de Abreu
      Hi Guys, I'm with a trouble here.
       
      Recently we started to get our outdated temperature test cabinet to work, and the best way is to upgrade our PLC. But there cames 2 problems, the biggest is the budget, we do not have any money so we have to work with what we already have, and the second, i'm intern here and there is no one from automation to guide or help me.
       
      Now lets face the problem.
       
      PLC Allen Bradley micrologix 1100
      cards: 1762-IQ16 and 1762-IQ8W6
       
      My first thought is to use Labview to control the PLC, as HMI and data-logger without OPC server to simplify the instalation and cost.
       
      The communication: this is really where the problems begin. It will be done through Ethernet. I could not manage Ethernet/IP driver to work, nor pcc or CIP message...
       
      which is the best way to communicate?
      CIP Message, OPC, or any other i do not know? Do you guys see any problems to make a dataloger without OPC?
       
      Some things I have tryed
       
      Implementation of Common industrial Protocol (CIP) via EtherNet [EtherNet/IP (CIP)]
      https://lavag.org/topic/6104-industrial-ethernet-ethernetip/?page=1
       
      Ethernet/IP Driver for Micrologix 1100
      https://decibel.ni.com/content/docs/DOC-13024
       
      EtherNet/IP Driver for Industrial Communication
      https://decibel.ni.com/content/docs/DOC-4065
       
       
      Thanks for any help
      Ricardo
      PS. Originally posted at: https://decibel.ni.com/content/thread/47497
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept