Micrologix 1100 and LabView

[Ricardo de Abreu 0]

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

[Tim_S 65]

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.

[Ricardo de Abreu 0]

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

[Tim_S 65]

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.

[Ricardo de Abreu 0]

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 September 6, 2016 by Ricardo de Abreu
Adding information

[Tim_S 65]

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.