This lab section should take roughly 10 minutes to complete.
Objective:
In this lab you will open a controller project based on the lab station at which you are seated. You will:
Determine the type of controller you are using
Open the project that corresponds to the controller you are using Download the program to the controller
You will be using the program that was created from the steps performed in Lab 1.
Look over the images below if you are unsure of the hardware associated with your lab station demo.
ControlLogix L7x Controller
Digital Output Card
Digital Input Card
Analog Input Card
Downloading the Project to the Controller
In this section of the lab you will download the project.
1. Maximize RSLogix 5000 and your Controller1.ACD project.
2.
From the Communications menu, choose Who Active.
3. Expand the view by clicking on the ‘+’s until you see your controller.
The Logix family of controllers all use RSLogix 5000 software to configure the system. But each controller is set up slightly differently.
4. Click Download. You will be asked to verify the download.
The project will then begin to download to your controller.
If your controller was in the RUN mode prior to the download, you may be prompted to return to the RUN mode. If asked select YES.
5. When the following prompt appears, click Yes to change the controller mode to Remote Run.
At this point you will be online with the controller and the status LEDs in your project will mimic the LEDs on your controller.
Configuring Local 1756-I/O Modules
After completing this lesson, you should be able to perform the following tasks: Add a local 1756-I/O module to an I/O configuration
Identify a local I/O tag
1756-I/O Module Components
1756-I/O modules consist of two main components, the module body and the RTB (removable terminal block):
Removable Terminal Block (RTB): A field wiring connector for I/O modules. Field wiring is connected to an RTB rather than directly to a module terminal block.
Interface Module (IFM): A field wiring arm that uses prewired/factory-wired cable to connect to an I/O module. ControlBus Connector: The backplane connector interface for the ControlLogix system that connects the module to the
ControlBus backplane.
Connector Pins: Pins that create input/output, power and grounding connections to the module through an RTB or IFM. Locking Tab: Anchors the RTB or IFM cable on the module, maintaining wiring connections.
Slots for Keying: Mechanically keys the RTB to prevent inadvertently making the wrong wire connections to the module. Status Indicators: Display the status of communications, module health, and input/output devices. Use these indicators
to help troubleshooting errors or system faults.
RIUP (Removal and Insertion Under Power)
RIUP: A ControlLogix feature that allows 1756 modules to be removed and inserted into a chassis while the backplane power is applied.
LED Status Information
LED indicators are located on the front of all I/O modules to show if all connections and communications are functioning properly:
I/O Status: The yellow status indicator shows the ON/OFF state of the field device. Module Status: This green status indicator shows the module’s communication status.
Fault Status: This display, found on some modules, indicates the presence or absence of various field-side faults. Fuse Status: This display, found on electronically fused modules, indicates the state of the module’s fuse.
Digital and Analog I/O Modules
1756-I/O modules process two types of data:
Digital: Information represented by a discrete value (i.e., 1 or 0).
Analog: Numeric values that represent measurable quantities, such as temperature, weight, and pressure.
Digital 1756-I/O modules provide on/off detection and control for items that utilize digital data. They have the following properties: RIUP (Removal and Insertion Under Power)
8-, 16-, and 32-point varieties Electronic keying
Isolated, non-isolated, and diagnostic varieties:
o Module-level fault reporting and field-side diagnostics Electronic fusing
Analog 1756-I/O modules convert analog signals to digital values for inputs and convert digital values to analog signals for outputs. They have the following properties:
RIUP
Scaling to engineering units calculated in the module
32-bit floating or 16-bit input and 13-16 bit output integer data format depending on the module Alarming
Rolling time stamp of data Diagnostic choices
Local and Remote I/O Modules
Local and remote I/O modules can be configured in a Logix5000 system based on the needs of the application. Local I/O Modules
Local I/O modules communicate with a controller across a backplane, thus limiting their distance from the controller.
Remote I/O Modules
Remote I/O modules are not located in the same chassis as the controller that configures them. This allows I/O to be located in a closer proximity to the process:
1756-I/O Module Identification
To identify a local device tag, the module type must be identified first by referring to the part number on one of the following items:
RSLogix5000 software I/O configuration Plant drawings
Hardware label (inside the module door) Factory sticker on the side of the module RSWho network interface in RSLinxr software
I/O Configuration
All devices that communicate with a Logix5000 controller must be added to the I/O configuration of the controller project, as shown in the following graphic:
Every I/O module that sends process/machine data to a controller must be configured by a controller.
When you add a new I/O module to a project, you are first prompted to enter general module properties in the New Module dialog box:
Once data has been entered in the New Module dialog box, you can then continue module configuration from the Module Properties dialog box.
Parameters for configuring a digital 1756-I/O module are entered on the following tabs in the Module Properties dialog box: General
Connection Configuration
General Tab
The following graphic shows the General tab parameters:
Electronic Keying
To avoid installation or replacement errors, keying prevents controller from communicating with the wrong module: Exact Match: All I/O module information must match (i.e., module type, major revision, and minor revision). Compatible Keying: All I/O module information except minor revision must match.
Disable Keying: Minimum information must match (i.e., module type only). Communications Format (Ownership)
The communications format parameter defines how an I/O module communicates with a controller. The following options are available:
Full Diagnostics: I/O connection where the module is owned by the controller, receiving configuration data from it: o The I/O module returns diagnostic data (e.g., Fuse Blown, No Load) along with a timestamp of when the
diagnostic data changes state.
Listen-Only Connection: I/O connection where another controller owns/provides the configuration data for the I/O module. The I/O module does not write configuration data.
Connection Tab
The following graphic shows the Connection tab parameters:
Requested Packet Interval (RPI): Also referred to as the “multicasting rate,” this is the rate at which data is simultaneously transmitted to all nodes or modules:
The RPI specifies the time that elapses before the module multicasts the current data in the on-board memory The RPI can vary from 200 microseconds (.2 ms) to 750 ms
Inhibit Module Connection Option: An option that allows configuration data for a module to be written but prevents the module from communicating with the owner controller.
Major Fault Option: An option that causes a major fault on the controller if the connection to the module fails.
Configuration Tab
The following graphic shows an example of the Configuration tab parameters:
Depending on the module, 1756 digital and analog diagnostic I/O modules can have the following diagnostic features:
Open Wire Detection: Senses removed or disconnected field wiring on an input module: A leakage resistor must be placed across the contacts of an input device.
Field Power Loss Detection: When field power to a module is lost, a point-level fault is sent to the controller.
No Load Detection: Senses the absence of field wiring or a missing load from each output point in the off state only.
Field-Side Output Verification: Indicates that the ladder logic changes are accurately represented on the power side of a switching device (i.e., the output is on when it is commanded to be on).
Point-Level Electronic Fusing: Internal electronic fusing that prevents too much current from flowing through a module. This feature clears fuses when an instruction in RSLogix 5000 software
resets the fuse or a power cycle resets the fuse.
Diagnostic Latching: Sets and retains a faulted state (bit) upon detection of any diagnostic faults: The fault data is multicast to all controllers.
The I/O module LED displays a fault.
A fault bit is latched and can be examined in the tags list.
Asynchronous Updates
Asynchronous: Actions that occur independently of each other and lack a regular pattern. In Logix5000 controllers, I/O values update asynchronously with the execution of code: Input modules multicast their data to the backplane at the RPI rate set in the modules.
The code is scanned and the output tags are updated immediately after the execution of each output instruction. Values are sent to the output modules at the RPI rate and at the end of each task.
Identifying an I/O Module Tag
Module-Defined Data Type: A data type assigned to a tag that is automatically generated when a communications or I/O module is added to an RSLogix 5000 project.