I am considering a micorlogix 1100 unit for use in a mixing tank application in conjuntion with a small HMI screen. Leaning towards using a PV+600. Seems to have quite a nice mix of I/O built in and the ability to add on expansion modules as needed, and the built in ethernet is appealing for data collection and centralized programmin, at a lower list price than a 1761-net-eni. Has anyone here tried one of these yet. Any pitfalls or limitation I should be aware of?

I've played with them and the only pitfall is the lack of I/O messaging but the 1761-Net-Eni doesn't give you that either. The little display doesn't do anything for me. I guess it might have some maintainence purpose but I don't believe in having to open the control panel for anything but replacing parts.

I'd say go for it. We will probably try it in our small Ethernet applications that don't require I/O message. Unfortunately most of ours do so we will stick with the Compactlogix for most applications

We ran into a problem with a Micrologix 1500 and a NET-ENI trying to do messaging to five Cognex cameras, at a rate of 1 second cycle time. When we had four cameras messaging, it was ok... Mind you, that's alot of information to cram into an Ethernet to DF1 convertor box...

So next time, we are going to do the Micrologix 1100. We feel like having a dedicated ML1100 ethernet port would be better, but haven't tried it yet.

So in the case of using Cognex cameras, and elimating hard wire pass/fail bits direct to our PLC, I think this little ML1100 will have it's place with us.

Again, haven't tried it yet, but it's got to be faster than a ML1500/NET-ENI module running comms throught an RS-232/DF1 port.

Can I get elaboration on I/O messaging?

You are right chakorules. The limit is actually in the 1761-Net-Eni. It can only handle 4 messages at a time. After that you must stagger your messages which is a total pain. You have to make sure that the one message was actually completed before sending the next.

The Micrologix 1100 can handle 16 incoming and 16 outgoing connections at a time. For outgoing connections there is only one connection for each node no matter how many messages you send. One thing I couldn't find in the specs is how does it buffer the messages like the Micrologix 1200 or do you have to buffer the messages like you do in the Controllogix. Have you found any info on that? The practical limit for the Controllogix is 20 messages at a time but the Micrologix with no converter is practically unlimited.

I/O Messaging - This is more of a RsLogix 5000 feature. It allows devices on networks and even through network bridges to become an extension of the I/O in the chassis. In fact you set up the devices in the I/O configuration just like a module in a slot of the chassis. Each module has a polling rate and its pretty much a master/slave relationship. It gives Ethernet devices a deterministic feature similar to devicenet. It is much safer an much more responsive than using messsaging instructions. Timeouts on messaging instructions are usually set around 10 seconds. The highest timeout on an I/O messaging is 200ms. Plus the controller knows when the device such as (I hate to even bring this one back up) a Panelview is not communicating so you could disable dangerous operations that can be done through the Panelview. Through normal method you really do know whats communicating. Guess that sums it up. The controller controls all communications to and from the device and polls constantly just as it would to a module in the plc chassis.

Another great feature of I/O messaging is that its connection limits are much higher. Well above 100 connections depending on how you count them. But I still get confused trying to count connections. We have gone totally to this type of setup on our controllers that require heavy network use.

One other thing is the communications ports on the side of the controller. I'm sure there was some design reason but I really haven't warmed up to this layout. Looks like it is going to hard to deal with the cable connections and limits what can be to the left of the Plc. What are you guys thoughts on this?

Excellent information, wish my AB would have told me this upfront. After reading your post, confused, I went digging. I found in the manual that is says 6 connection, but it looks like a technicality with the last one "2 either incoming or outgoing".

But now I get it.....

2 outgoing: means two Cognex Cameras (from PLC outgoing to Camera)
2 incoming: doesn't mean anything in my application (my messages are all outgoing)
2 either incoming or outgoing: means two more Cognex Cameras (from PLC outgoing to Camera)

So really that means 4 cameras/connections in my application and not 6 connections. Geez, now we have to sit down and analyze the manual for it's true meaning....


http://literature.rockwellautomation.com/i...um006_-en-p.pdf

The ENI and ENIW support a maximum of 6 connections, allowing
simultaneous communication with up to 6 other devices or
applications. The connections are dedicated as follows:
Number of Connections Dedicated to:
2 outgoing messages
2 incoming messages
2 either incoming or outgoing messages
TIP For peer connections, no more than one connection
per destination node is established. If multiple MSG
instructions use the same destination node, they use
the same connection.

You may read on in the 1761-Net-Eni user manual about staggering messages to compactlogix. You can use the same thing for the Micrologix. Just got to make sure the message is completely done before firing the next on. Of course at the cost of the Micrologix 1100 compared to the Micrologix 1200 plus a 1761-Net-Eni you are really better off just buying the 1100. I would like to get some clarifications from Ab on how many messages you can really fire to one connection at at time. I think it would be the same as the Micrologix 1200 which is pretty much unlimited but I would like to find that spelled out somewhere. But you could definately do 16 cameras without staggering

Also what do you make of page F2 of Publication 1763-UM001A-EN-P about Micrologix 1100 Performance Considerations

Thanks for the great information. I think I am gradually catching on now. Ethernet/IP seems to come in a few variations and just because two AB devices have the ethenet port and listed as supporting Ethernet I/P and associated hype over open platform ...etc, does not necesarilly mean that they will be compatible? I/O messaging on ethernet is more deterministic like RIO or DH+? And a micrologix 1100 would not be compatible with for example a 1794-AENT for flex I/O control?
If I understand the connection counting I should be OK with the 1100. One incoming and one outgoing for PV+, ditto for RSView32, kepware or other monitoring and data collection software, and one each for edits when connected with laptop, for a total of 6? Looks like an AIC would just barely make it too on another poject in the early planning stages, but could fall short since a couple of ML1500s are messaging back and forth over 485.
I looked at the F2 page mentioned. It would look like the 1100 is capable of processing 22 transmissions per second. 1100 to 1100 would be half (one encode, one decode), but with RSLinx is faster since it can respond much quicker?
The LCD is cute and perhaps I would find some use for it, but would rather have the processor $50 less.
The ethernet port on the side for me is not that big of a deal since the unit needs the space for ventilaiton anyway, and in my opinion makes for a neater install than a front mount. Top or bottom with no side ventilation clearnce could be better. So I guess as far as panel space goes, the small case size is a bit decieving at first. Maybe they will make a little sidecar hub.

Yes I guess since I'm used to seeing the 1761-Net-Eni on the left side of the Micrologix it throwing me off. What if I want to put some other converter on it? Once I get using them it will probably go away. Display does nothing for me either

Another quick side note

Your are right Hakko808, lots of devices including Ab are claiming devices to be Ethernet/ip. But that doesn't mean they have the compliance logo.

Neither the Micrologix 1100 or the Panelview Plus are Ethernet /ip compliant

I believe all the Logix5000 platforms and the Standard Panelview are at this point. I do know there are plans to make the Panelview Plus Ethernet /ip compliant but I don't if there are plans to do the Micrologix 1100