Micrologix 1100 User Manual
Aleshia Ducharme
A programmable logic controller (PLC) is a digital electronic device with a programmable memory for storing instructions to implement specific functions, such as logic, sequencing, timing, counting, and arithmetic to control machines and processes.
Another piece of memory that can be helpful to the programmer is the Status file. Inside this file is a large data set that tells the complete story of the current status of the PLC. See page 470 in the instruction set manual for the PLC for more information on the Status File. Review page 479, the watchdog scan time as it will come in handy later. This is the maximum allotted time the PLC has to run through your program once. It prevents the PLC from getting stuck in infinite loops. If the watchdog scan time is exceeded the PLC throws a fault and resets.
I am trying to set up a micrologix for quadrature mode to read in A and B pulses from an incremental encoder. I am using the high speed counter for this. The A pulses are connected to the I/O terminal and the B pulses are connected to the I/1 terminal, as specified from the user manual.
The problem that i am having is that the change in direction is never being picked up by the PLC. Hence regardless of which direction i rotate the encoder, it continually counts in the negative direction.
Hopefully a simple, basic question. I want to utilize the on board Analog input on my Micrologix 1100. What is it called?? How do I address it on my program? It is not an expansion card. Just the built in inputs.
So once you know what PLC you have, then once you have the user manual, and after you have researched the configuration words and what the word addresses are, and after you have wired in your analog input, then you can map the analog input and have it scaled using a SCL function block. Going off of memory...a 4-20mA input will be coming in 0-32766 which you want to scale into whatever (degrees C or F [temp], inches/cm [height], etc.).
Thanks, for once something was easier than expected. :) One weird thing so: I'm using a mixrologix 1100 (1763-l16 awa) with 9 (or 10, don't remember) and two analog inputs. I:0/4 should definitely be digital, but that's where my analog signal us stored. I am using rslogix micro light, and I was only able to chose a generic mixrologix plc. I assume that is the reason? Will this cause problems when I or another person tries to modify the program with rslogix 500?
I found this in the Flexy manual, and I believe that means the Flexy can talk to a MicroLogix 1100 using the Ethernet port and the DF1 driver. The manual only mentions SLC500 and PLC-5, so I am asking if you ever heard of this possibility.
Yes you can absolutely use the DF1 driver for a Micrologix. Simply enter the IP address into the topic config. You do not need to specify a device type or node here. Just the EIP destination is required.
This document provides an overview and user manual for the MicroLogix 1100 programmable controller and 1762 expansion I/O from Rockwell Automation. It describes the hardware components, installation procedures, wiring requirements, communication options, and programming interface. Safety guidelines and considerations are also discussed. The manual is intended for users applying and installing the MicroLogix 1100 controller and I/O.Read less
Get Free Trial >
NET.LOGIX 7.0 provides a direct communication pipeline from Visual Studio.NET to Allen-Bradley series without OPC servers or RSLinx. Fast, powerful and easy to use runtime-free solution for Allen-Bradley. Using NET.LOGIX, you can create, upload and filter tag lists to your application on the fly. Read and write any size or type of large data blocks, including string types, arrays and user-defined types. Form control linking allows you to automatically update form controls. Unsolicited message support for ControlLogix, CompactLogix, SoftLogix and ControlLogix gateway, MicroLogix 1100 and 1400, SLC 5/05 and PLC-5E.
Click Create New Device.
The Devices page is displayed showing the MicroLogix device is added to Ignition. The Status will show as Disconnected and then Connected.
To see all the tags, go to OPC Connections > Quick Client in the Configure section, on the OPC Quick Client page expand the MicroLogix folder which contains all the folders with the individual tags.
The user-defined name for this Device. The name chosen will show up in OPC Item Paths and under OPC-UA Server > Devices of the Status page of the Gateway. The Device Name must be alphanumeric.
The Hostname value is the IP Address of the MicroLogix 1100 processor, MicroLogix 1400 processor or 1761-NET-ENI Ethernet interface. EthernetIP protocol on TCP port 44818 (0xAF12) is used to communicate to the listed devices.
MicroLogix 1200 and 1500 are not fully supported. Browsing is not available on these devices, so the 'Disable Processor Browse' advanced property will need to be set to True on the device connection.
Has anyone tried connecting to the A/B Powermonitor 5000? The Rockwell manual says we can configure RSLinx as a SLC5/03 as it supports PCCC addressing. I tried SLC5/05 in KepwareEX and this didn't work. Neither did the PLC-5 family, Thanks
EDIT: Ended up figuring this out. Utilized the Allen-Bradley ControlLogix Ethernet Driver, and put the device as a MicroLogix 1100. The table for tag addresses is in 1426-um001_-en-p, Power Monitor 5000 User Manual, Appendix A, starting page 219
It looks like there are two primary ways to communicate with a Powermonitor 5000 device.
Ethernet/IP, and DeviceNet, - We do not have a generic Ethernet/IP driver at this time, or a DeviceNet driver.
A potential work-around would be using our Allen Bradly ControlLogix Unsolicited driver, that can act as a slave to the device. There may be a way to have the device push/write data to the server. You may need to reach out to Rockwell for assistance with additional device configuration. Here is a link to page in the Rockwell documentation that covers some of the set up:
Note: Viper Bridge mode cannot filter keepalive and cannot operate in TCP proxy mode.
If the system has very few units and few messages Viper Bridge mode could be used. But for larger systems and PLC doing many keepalives, or on-air network being contentious, it may be required to use router mode. Router mode allows retransmission of messages lost due to on-air contention. Bridge mode only does broadcasts without retries. In Bridge mode the application needs to retry lost messages.
When using TCP protocol and having PLCs where the TCP keepalive rate cannot be controlled, it is important to enable Viper TCP (OIP proxy) mode. This requires that all Vipers are configured in router mode (Viper Bridge mode cannot filter keepalive and cannot operate in TCP proxy mode).
One of the Viper's TCP proxy mode usages allows filtering of keepalive messages and prevents them to be sent over the air. Without this filtering, several PLCs sending keepalive messages could easily load the on-air network.
See Viper user manual and Web pages to enable proxy. By default Viper proxy mode is enabled. See Viper Web page Advanced setup -> OIP optimizations. Also under Network management -> Neighbor Tables (neighbor management) make sure that neighbors are configured with the proxy attribute.
To reestablish TCP proxy context for the TCP connection, the PLC needs to close the old TCP connection and re-open a new TCP connection. Therefore normally after doing Viper maintenance the master PLC needs to be restarted. Future Viper firmware may reestablish proxy automatically.
c80f0f1006