Home

FlexLogix Controller System User Manual

1. Instruction Location Languages MDF motion elay ladder Motion Direct Drive Off structured tex MDO motion elay ladder Motion Direct Drive On structured tex MDOC motion elay ladder Motion Disarm Output Cam structured tex MDR motion elay ladder Motion Disarm Registration structured tex MDW motion elay ladder Motion Disarm Watch structured tex MEQ general relay ladder Mask Equal to structured tex unction block MGS motion elay ladder Motion Group Stop structured tex MGSD motion elay ladder Motion Group Shutdown structured tex MGSP motion elay ladder Motion Group Strobe Position structured tex MGSR motion elay ladder Motion Group Shutdown Reset structured tex MID general relay ladder Middle String structured tex MINC process control structured tex Minimum Capture function block MOD general relay ladder Modulo structured tex function block MOV general relay ladder Move MRAT motion relay ladder Motion Run Axis Tuning structured tex MRHD motion relay ladder Motion Run Hookup Diagnostics structured tex MRP motion relay ladder Motion Redefine Position structured tex MSF motion relay ladder Motion Servo Off structured tex MSG general relay ladder Message structured tex MSO motion relay ladder Motion Servo On structured tex
2. Q al iM 0000 FlexLogix system with q senii 0000 a1788 DNBO card irp 91 oes pushbutton im starter E cluster i H K i e m Z bar code input o utput a indicator scanner devices PowerFlex lights ac drive Publication 1794 UM001G EN P January 2007 30 Communicate over Networks For more information Publication 1794 UM001G EN P January 2007 Define Data Blocks How you configure the DeviceNet devices determines how many words you use per device The 1788 DNBO card supports a maximum of e 124 32 bit words of input data e 123 32 bit words of output data e 32 32 bit words of status data Most DeviceNet devices support 16 bit words Take care how you map these into the 32 bit words used in RSLogix 5000 programming software RSNetWorx for DeviceNet lets you DINT align the device data While this might simplify the organization of the data it might also limit the data you have available The DeviceNet Modules in Logix5000 Control Systems User Manual DNET UMO004 provides information on how to e configure DeviceNet communication module e control devices on DeviceNet The Logix5000 Controllers Design Guidelines Reference Manual 1756 RM094 provides guidelines on optimizing a control application on a DeviceNet network Communicate over Networks 31 S
3. For this information See Manage Tasks 69 Develop Programs 70 Organize Tags 75 Select a Programming Language 76 Monitor Controller Status 79 Monitor Connections 80 Select a System Overhead Percentage 82 Use the Event Task 85 A Logix5000 controller lets you use multiple tasks to schedule and prioritize the execution of your programs based on specific criteria This balances the processing time of the controller among the different operations in your application e The controller executes only one task at one time e A different task can interrupt a task that is executing and take control e In any given task only one program executes at one time Publication 1794 UM001G EN P January 2007 70 Develop Applications Develop Programs The controller operating system is a preemptive multitasking system that is IEC 1131 3 compliant This environment provides e tasks to configure controller execution e programs to group data and logic e routines to encapsulate executable code written in a single programming language control application controller fault handler task 8 task 1 configuration status watchdog program 32 program 1 program local main routine tags fault routine other routines controller global tags 1 0 dat
4. j starter Le cluster Ultra 5000 2 servo drive H J bar code input output wa scanner devices lt indicator PowerFlex lights ac drive Communicate over Networks 29 Use these software products when you use a FlexLogix controller on DeviceNet Software Use Required optional RSLogix 5000 programming Use this to configure the Required software FlexLogix project and define DeviceNet communications RSNetWorx for DeviceNet Use this software to Required configure DeviceNet devices and define the scan list for those devices The DeviceNet communications module e supports messaging to devices not controller to controller e shares a common application layer with ControlNet and EtherNet IP e offers diagnostics for improved data collection and fault detection e requires less wiring than traditional hardwired systems You can use a linking device as a e gateway to connect information or control level networks to device level networks for programming configuration control or data collection e router bridge to connect the EtherNet IP or ControlNet network to the DeviceNet network ControlLogix controller with 1756 ENBT module EtherNet IP network mm A i Fa i FlexLogix controller H nis on 4 witha 1 88 ENBT card FLEX adapter and 1 0 linking i devices SS DeviceNet network personal computer
5. FlexLogix controller computers other controllers The FlexLogix controller offers state of art control communications and I O elements in a distributed control package 1794 1 0 modules connected to the FlexLogix controller For a more flexible system use e multiple controllers joined across networks e I O from multiple platforms that is distributed in many locations and connected over multiple I O links network communication cards installed in the controller remote 1 0 modules ee EtherNet IP link ControlNet link Publication 1794 UM001G EN P January 2007 12 Where to Start Design See e FlexLogix Selection Guide 1794 SG001 e Logix5000 Controller Design Considerations Reference Manual 1756 RM094 Publication 1794 UM001G EN P January 2007 The FlexLogix controller part of the Logix family of controllers provides a small powerful cost effective system built on the following components e 1794 L34 FlexLogix controller available in 512 Kbytes of user memory e FlexLogix controller that supports the Logix instructions e RSLogix 5000 programming software that supports every Logix controller e FLEX I O modules that provide a compact DIN rail mounted I O system e 1788 communication daughtercard that provides communication over standard based ControlNet DeviceNet or EtherNet IP networks The controller allows
6. 108 Back up Heartbeat Configuration Rungs 108 Reading Back up State Rung 0 05 112 Reading Back up Status 1 0 0 eee eee 114 Using Indicators to Check Status 0 0 004 115 Development and Debugging Tips 115 Appendix C Where to Find an Instruction o a aaa d gible gee de Gael ots 117 Publication 1794 UM001G EN P January 2007 6 Table of Contents Publication 1794 UM001G EN P January 2007 Summary of Changes Introduction This release of this document contains new and updated information To find new and updated information look for change bars as shown next to this paragraph Updated Information The document contains these changes Topic Page DF1 radio modem 31 Add On Instructions 77 Where to Find an Instruction 117 Publication 1794 UM001G EN P January 2007 8 Summary of Changes Notes Publication 1794 UM001G EN P January 2007 Preface Developing FlexLogix Controller Systems Introduction Use this manual to become familiar with the FlexLogix controller and its features This version of the manual corresponds to controller firmware revision 16 This manual describes the necessary tasks to install configure program and operate a FlexLogix system In some cases this manual includes references to additional documentation that provides the more comprehensive details Related Documentation These core documents address the Logi
7. Quantity per Device Connections rai 1 0 module rack optimized connection on local rail 0 1 0 module direct connection on local rail 1 1 0 module rack optimized connection on extended local rail 0 1 0 module direct connection on extended local rail 1 1788 CNx ControlNet communication card 0 0 1788 DNBO DeviceNet communication card direct connection 2 1788 ENBT Ethernet IP communication card 0 0 total 1 FlexLogix controller connection to remote DeviceNet devices are accounted for in the 2 connect ions to the 1788 DNBO card Remote connections depend on the communication module The number of connections the module itself supports determines how many connections the controller can access through that module To calculate the total number of remote connections the controller uses Remote Connection Type Device Connections Total Quantity per Device Connections remote ControlNet communication module 1 0 configured as direct connection none 0 or 1 0 configured as rack optimized connection 1 remote I O module over ControlNet direct connection 1 remote EtherNet IP communication module 1 0 configured as direct connection none Oor 1 0 configured as rack optimized connection 1 remote I O module over EtherNet IP direct connection 1 remote device over DeviceNet accounted for in rack optimized connection for optional 1788 DNBO card 0 other remote communication adapter produced ta
8. where I_O_LED is a DINT tag that stores the status of the I O LED on the front of the controller Determine if communication has timed out with a specific 1 0 module If communication times out with a device module in the I O configuration of the controller the controller produces a fault code for the module e The GSV instruction gets the fault code for Io_Module and stores it in the Module_Status tag Develop Applications 81 e If Module_Status is any value other than 4 the controller is not communicating with the module This rung is used to check the status of an I O connection We look at the entry status of the connection if the value returned is anything other than 4 The connection is not functioning properly When an error is detected the error code and and info is trapped on a one shot basis This is becuase the controller will try and re establish the connect and when it does this you will loss the true error SY BTD Get System Value Bit Field Distribute Class Name MODULE Source Module_Status Instance Name lo_Module 0 Attribute Name EntryStatus Source Bit 12 Dest Module_Status Dest Module_Status_Easy 0 0 Dest Bit 0 Length 4 EQ Check_ONS SY Not Equal ONS Get System Value Source A Module_Status_Easy Class Name MODULE 0 Instance Name lo_Module Source B 4 Attribute Name FaulttCode Dest Module_Faultt_Code Get System Value Class Name MODULE Instance Name lo_Module Attribute Name Fauttinfo Dest M
9. connection from FlexLogix controller to port 1 or port 2 1761 CBL APO0 or 1747 CP3 or DH 485 network i 1747 AlC rean A Baf efes eses SLC 5 03 controller Publication 1794 UM001G EN P January 2007 40 Communicate over Networks Publication 1794 UM001G EN P January 2007 On the DH 485 network the FlexLogix controller can send and receive messages to and from other controllers on the network A DH 485 network consists of multiple cable segments Limit the total length of all the segments to 1219m 4000 ft For the controller to operate on a DH 485 network you need e a 1761 NET AIC interface converter for each controller you want to put on the DH 485 network You can have two controllers for each 1761 NET AIC converter but you need a different cable for each controller a Connect the serial port of the controller to either port 1 or port 2 of the 1761 NET AIC converter b Use the RS 485 port to connect the converter to the DH 485 network The cable you use to connect the controller depends on the port you use on the 1761 NET AIC converter If you connect to this port Use this cable port 1 1747 CP3 DB 9 RS 232 DTE connection or 1761 CBL ACO0 port 2 1761 CBL AP00 mini DIN 8 RS 232 connection or 1761 CBL PM02 Communicate over Networks y e RSLogix 5000 programming software to configure the serial port of the controller for DH 485 communications Specify these ch
10. Use RSNetWorx for DeviceNet to download the network s scanlist to the 1788 DNBO card You can use either a scanlist from a new configuration or previously used configuration If the scanlist is a new configuration we recommend you save it to a new project for later use Use RSLogix5000 software to download the appropriate user program to the FlexLogix controller The program should contain the explicit message s that enable the back up feature for this controller and scanner The messages are described in the Developing the FlexLogix Back Up Application section beginning on page 108 Put controller into RUN mode Either disable power to the controller or disconnect the scanner from DeviceNet This controller will be the secondary controller FlexLogix Back Up on DeviceNet 107 9 Connect the other FlexLogix controller with a 1788 DNBO scanner on the network 10 Set the node address to 0 11 Power up the controller and scanner 12 Use RSNetWorx for DeviceNet to download the same scanlist used in step 5 It may be necessary to browse the network again before downloading the scanlist This second browsing of the network allows RSNetWorx for DeviceNet to establish communication to the new scanner at the same node number as the previous scanner 13 Use RSLogix5000 to download the user program to the second FlexLogix controller as performed in step 6 Typically the same user program is downloaded to the s
11. communicate with DF1 device 33 connect an isolator 15 17 controller communication 31 38 controller connection 15 20 DH 485 configuration 39 41 driver 18 for more information 34 38 Modbus support 38 modes 31 RSLogix 5000 18 20 select controller path 20 SFC 76 SSV instruction 79 ST 76 start 11 state model See states states compared to PackML 94 compared to S88 94 manually step through 94 overview 91 transition 92 status 79 status indicators 101 store batteries 97 structured text 76 system layout 11 Publication 1794 UM001G EN P January 2007 126 Index T tag consumed 46 for more information 75 organize 75 produced 46 task 69 defining 71 priority 71 troubleshooting 101 Publication 1794 UM001G EN P January 2007 U unscheduled 27 update 63 Ww where to start 11 How Are We Doing PANE Your comments on our technical publications will help us serve you better in the future Thank you for taking the time to provide us feedback wy You can complete this form and mail or fax it back to us or email us at RADocumentComments ra rockwell com Pub Title Type FlexLogix Controller System User Manual Cat No 1794 L34 Pub No 1794 UM001G EN P Pub Date January 2007 PartNo 953014 91 Please complete the sections below Where applicable rank the feature 1 needs improvement 2 satisfactory and 3 outstanding Overall Usefulness 1 2
12. Configure Client Applications 1784 KT KTX D PKTX D PCMK for DH DH 485 devices Configure CIP Options 1784 KTC X for ControlNet devices Status A DF1 Polling Master Driver Driver Diagnostics 1784 PCC for ControlNet devices CIP Diagnostics 1784 PCIC S for ControlNet devices Gateway Diagnostics 1747 PIC 7 AIC Driver DF1 Slave Driver S S SD SD2 for DH devices Virtual Backplane SoftLogix58xx DeviceNet Drivers 1784 PCD PCIDS 1770 KFD SDNPT drivers PLC 5 DH Emulator driver SLC 500 DH485 Emulator driver SoftLogix5 driver Remote Devices via Linx Gatewa 2 Click Add New to add the driver 3 Specify the driver name and click OK Add New RSLinx Driver Choose a name for the new driver OK 15 characters maximum ok AB_DF1 1 era Publication 1794 UM001G EN P January 2007 Directly Connect to the Controller via the Serial Port 19 4 Specify the serial port settings a From the Comm Port drop down list select the serial port on the workstation that the cable is connected to b From the Device drop down list select Logix 5550 Serial Port c Click Auto Configure Configure RS 232 DF1 Devices Device Name AB_DF1 1 Comm Port COM1 X Device ETEA 7 Baud Rate fis20 x Station Number w Sies Me Decimal Parity None X Error Checking BCC Stop Bits 1 hd Protocol Full Duplex ind Auto Contigure Use Modem Dialer Cancel Delete 5 Does the dial
13. Count Up Down function block FSC general elay ladde File Search and Compare D2SD process control structured text Discrete 2 State Device function block GEQ general elay ladde Greater than or Equal to structured tex D3SD process control structured text unction block Discrete 3 State Device function block GRT general elay ladde DDT general relay ladder Greater Than structured tex Diagnostic Detect unction block DEDT process control structured tex GSV general elay ladde Deadtime function block Get System Value structured tex DEG general relay ladder HLL process control structured tex Degrees structured tex High Low Limit unction block function block HPF process control structured tex DELETE general relay ladder High Pass Filter unction block String Delete structured tex i ICON general unction block DERV process control structured tex Input Wire Connector Derivative function block Publication 1794 UM001G EN P January 2007 Instruction Location Languages NSERT general relay ladder nsert String structured text NTG process control structured text ntegrator function block OT general relay ladder mmediate Output structured text REF general function block nput Reference JKFF process
14. Detach from Equipment Phase structured tex PFL phase relay ladde Equipment Phase Failure structured tex P process control structured tex Proportional Integral function block PID general relay ladder Proportional Integral Derivative structured tex Instruction Locator 121 Instruction Location Languages Instruction Location Languages PIDE process control structured tex SIN general elay ladde Enhanced PID function block Sine structured tex unction block PMUL process control structured tex Pulse Multiplier function block SIZE general elay ladde Size In Elements structured tex PPD phase relay ladder Equipment Phase Paused structured tex SNEG process control structured tex Selected Negate unction block POSP process control structured tex Position Proportional function block SOC process control structured tex Second Order Controller unction block PRNP phase relay ladder Equipment Phase New structured tex Sal general elay ladde Parameters Sequencer Input PSC phase relay ladder SOL general elay ladde Phase State Complete structured tex Sequencer Load PXRQ phase relay ladder sao general elay ladde Equipment Phase External structured t
15. Make sure you q 1 EVENT instruction Use a Trigger Event Task EVNT instruction at each point in your logic that you want to trigger the event task q 2 Task priority Configure the event task as the highest priority task If a periodic task has a higher priority the event task may have to wait until the periodic task is done q 3 Number of event tasks Limit the number of event tasks Each additional task reduces the processing time that is available for other tasks This could cause an overlap q 4 Automatic Output Processing For an event task you can typically disable automatic output processing default This reduces the elapsed time of the task For more information on using the event task see Logix5000 Controllers Common Procedures programming manual publication 1756 PMO001 Publication 1794 UM001G EN P January 2007 88 Develop Applications Notes Publication 1794 UM001G EN P January 2007 Chapter Configure PhaseManager Use This Chapter The PhaseManager option of RSLogix 5000 software gives you a state model for your equipment This chapter summarizes For this information See See e PhaseManager User Manual PhaseManager Overview 89 LOGIX UM001 State Model Overview 91 Compare PhaseManager to Other State Models 94 Minimum System Requirements 94 Equipment Phase Instructions 95 PhaseManager Overview PhaseManager lets you add equipment phases to your controller An equipment phase helps you lay o
16. To prevent possible battery leakage even if the BATTERY LED is off replace the battery according to this schedule below the controller is 0 to 35 C No required replacement 36 to 40 C 3 years 41 to 45 C 2 years 46 to 50 C 16 months 51 to 55 C 11 months 56 to 60 C 8 months To estimate how long the battery will support the memory of the controller 1 Determine the temperature C 1 in below the FlexLogix controller 2 Determine the percentage of time that the controller is powered off per week EXAMPLE lf a controller is off e 8 hr day during a 5 day work week e all day Saturday and Sunday Then the controller is off 52 of the time 1 total hours per week 7 x 24 168 hours 2 total off hours per week 5 days x 8 hrs day Saturday Sunday 88 hours 3 percentage off time 88 168 52 Maintain the Battery 99 Use the off time percentage you calculated with the following table to determine battery life Worst case battery life estimate Catalog number Temperature Power off 100 Power off 50 Battery duration after the LED turns on 1794 134 60 C 1 8 years 3 6 years 3 days 25 C 6 7 months 1 1 year 3 days The battery indicators BATTERY warns you when the battery is low These durations are the amounts of time the battery will retain controller memory from the time the controller is powered down after the LED first turns on If the
17. module loses its connection with the controller e use the programming software to display fault data Refer to Displaying fault data on page 5 64 e program logic to monitor fault data so you can take appropriate action Refer to Logix5000 Controllers Common Procedures Programming Manual publication number 1756 PM001 for examples Displaying fault data Fault data for certain types of module faults can be viewed through the programming software To view this data select Controller Tags in the Controller Organizer Right click to select Monitor Tags Scope shh contralle zj Show Show All 2 Value Sot Tao Name xl AB 1769_D16 0_ 2 0000_000 2 0000_000 Gan Binary DINT ee Sal 8 1769 001600 if Locat2 C Config 2 0000_000 Binary INT Locat2C ProgToFaultEn to ao Decimal poo EZE ProgMe 2 0000_000 Binary INT 2 0000_000 Binary INT 20000000 Enay INT 2 0000_000 E Er Binary aM Ga Jt _ a8 1763_D0160 aB 1769_00160 0 The display for the fault data defaults to decimal Change it to Hex to read the fault code 4 Monitor Tags Edt Tags li p Place Configure and Monitor I O 65 Monitor a rack optimized connection The controller views the DIN rail as another module in the system Each DIN rail has its own data To view this data through the
18. remote I 0 e EtherNet IP e ControlNet e DeviceNet Communicate over Networks The FlexLogix controller supports additional networks so that the controller can Example _ FlexLogix controller control network distributed remote 0 platform Produce consume interlock data between controllers e EtherNet IP e ControlNet FlexLogix controller control network other Logix5000 controller Send and receive messages to and from other devices this includes access to the controller via RSLogix 5000 programming software e EtherNet IP e ControlNet e DeviceNet to devices only e serial e DH 485 FlexLogix controller control network other remote devices Publication 1794 UM001G EN P January 2007 22 Communicate over Networks This chapter summarizes the FlexLogix controller s communications capabilities For this information See EtherNet IP 22 ControlNet 25 DeviceNet 28 Serial DH 485 39 Third Party 42 EtherNet IP For EtherNet IP communications install a 1788 ENBT communication card in your FlexLogix controller Use these software products when you use a FlexLogix controller on ae EtherNet IP e EtherNet IP Modules in Logix5000 Control Systems User Manual Software Use Required optional 4 Mea Server Module RSLogix 5000 programming Use this to c
19. 232 dc power source selector switch p terminals for external 24V dc power supply 2 Select the appropriate cable If you are using an isolator Use this cable yes The 1761 CBL APOO cable right angle bend connector to controller or the 1761 CBL PM02 cable straight connector to the controller attaches the controller to port 2 on the 1761 NET AIC isolator The 8 pin mini DIN connector is not commercially available so you cannot make this cable 6 O 1 7 GAl 2 678 le 2 3 e S 4 A 5 5 12 DB 9 right angle or 8 pin mini DIN straight cable end cable end Pin DB 9 end Mini DIN end 1 DCD DCD 2 RxD RxD 3 TxD TxD 4 DTR DTR 5 ground ground 6 DSR DSR 7 RTS RTS 8 CTS CTS 9 na na Publication 1794 UM001G EN P January 2007 Directly Connect to the Controller via the Serial Port 17 If you are using an isolator Use this cable no The 1756 CP3 cable attaches the controller directly to the RS 232 device 1 D 1 CD 2 RDX 2 RDX 3 TXD 3 TXD 4 DTR 4 DTR COMMON COMMON _6 DSR 6 DSR 7 RTS 7 RTS 8 CTS 8 CTS 9 9 straight right angle cable end cable end If you make your own cable it must be shielded and the shields must be tied to the metal shell that surrounds the pins on both ends of the cable You can also use a 1747 CP3 cable from t
20. I O data Tasks at priorities 1 to 5 take precedence over the dedicated I O task Tasks in this priority range can impact I O processing time For example if you use the following configuration e I O RPI 2 ms e a task of priority 1 to 5 that requires 500 us to execute and is scheduled to run every millisecond this configuration leaves the dedicated I O task 500 us to complete its job of scanning the configured I O Publication 1794 UM001G EN P January 2007 72 Develop Applications However if you schedule two high priority tasks 1 to 5 to run every millisecond and they both require 500 us or more to execute no CPU time would be left for the dedicated I O task Furthermore if you have so much configured I O that the execution time of the dedicated I O task approaches 2 ms or the combination of the high priority tasks and the dedicated I O task approaches 2 ms no CPU time is left for low priority tasks 7 to 15 TIP For example if your program needs to react to inputs and control outputs at a deterministic rate configure a periodic task with a priority higher than 5 1 through 5 This keeps the dedicated 1 0 task from affecting the periodic rate of your program However if your program contains a lot of math and data manipulation place this logic in a task with priority lower than 6 7 through 15 such as the continuous task so that the dedicated 1 0 task is not adversely affected by your program The following ex
21. O Configuration folder of the controller You define a scanlist within the DeviceNet adapter to communicate data between devices and the controller For a typical distributed 1 0 network single network device device device device device controller card several smaller distributed networks subnets controller card linking linking device device device device device device device device you build the I O configuration in this order E Controller Tags Controller Fault Handler Power Up Handler 6 Tasks fa MainTask E amp MainProgram 3 Unscheduled Programs Phases E Motion Groups Ungrouped Axes Trends amp Data Types i User Defined Strings H E Predefined Module Defined B E 1 0 Configuration 3 Backplane FlexLogix System aE 1794 134 My_Project pei 1788 DNBO A local_card g FlexBus Local g FlexBus Local2 Add the local scanner module For more information See DeviceNet Communication Modules in Logix5000 Control Systems User Manual DNET UM004 Publication 1794 UM001G EN P January 2007 62 Place Configure and Monitor 0 Address 1 0 Data I O information is presented as a set of tags e Each tag uses a structure of data The structure depends on the specific features of the I O module e The name o
22. characters send characters and automatically append one or two AWA additional characters to mark the end of the data send characters AWT Create and modify strings of ASCII characters If you want to Use this instruction add characters to the end of a string CONCAT delete characters from a string DELETE determine the starting character of a sub string FIND insert characters into a string INSERT extract characters from a string MID Publication 1794 UM001G EN P January 2007 38 Communicate over Networks For more information See e Logix5000 Controllers as Masters or Slaves on Modbus Application Solution CIG AP129 Publication 1794 UM001G EN P January 2007 Convert data to or from ASCII characters If you want to Use this instruction convert the ASCII representation of an integer value to a SINT STOD INT DINT or REAL value convert the ASCII representation of a floating point value to a STOR REAL value convert a SINT INT DINT or REAL value to a string of ASCII DTOS characters convert a REAL value to a string of ASCII characters RTOS convert the letters in a string of ASCII characters to upper case UPPER convert the letters in a string of ASCII characters to lower case LOWER The Logix5000 Controllers General Instructions Reference Manual 1756 RMO003 defines the instructions you can use to manipulate ASCII characters The Logix5000 Controllers Common Procedures Manual 1756 PM
23. communication A rack optimized connection consolidates connection usage between the controller and all the digital 1 0 modules on a rack or DIN rail Rather than having individual direct connections for each 1 0 module there is one connection for the entire rack or DIN rail Connections for local and extendea local I O modules The FlexLogix controller automatically assigns one rack optimized connection for the local DIN rail and one rack optimized connection for the extended local DIN rail You then configure each I O module on a DIN rail to either use that rack optimized connection or to use a direct connection The rack optimized connection for each DIN rail exists whether or not you configure the I O modules to use that rack optimized connection The rack optimized connection lets you organize all the digital I O modules on one DIN rail into one connection to the controller Or you can choose to configure each I O module to have a direct connection to the controller Analog I O modules must have a direct connection to the controller It is not as critical to manage the number of connections for local and extended local I O modules as it is for remote devices because the controller supports a direct connection for each possible local and extended local I O device Publication 1794 UM001G EN P January 2007 58 Place Configure and Monitor 0 For more information Publication 1794 UM001G EN P January 2007 Connections f
24. create a map that defines your assembly instance entries Communicate over Networks 43 Size The size field determines how large the connections are between the owner controller and the I O module Connections are sent in sizes matching the communications format data type selected The default DINT results in 32 bit quantities Complete your system configuration and develop your program logic Then download the project to the controller Publication 1794 UM001G EN P January 2007 44 Communicate over Networks Notes Publication 1794 UM001G EN P January 2007 Chapter 4 Manage Controller Communications Use This Chapter For this information See Produce and Consume Interlock Data 45 Send and Receive Messages 47 Connection Overview 49 Calculate Connection Use 50 Connections Example 52 Produce and Consume The controller supports the ability to produce broadcast and Interlock Data consume receive system shared tags over ControlNet or EtherNet IP networks Produced and consumed tags each require connections Over ControlNet produced and consumed tags are scheduled connections See controller_1 controller_2 e Logix5000 Controllers Common Procedures Manual 1756 PM001 produced tag pe consumed tag e Logix5000 Controllers Design Considerations Reference Manual controller_3 H consumed tag controller _4 L consumed tag Publication 1794 UM0
25. detected 1 Primary scanner forcing IDLE back up in RUN but primary in IDLE Using Indicators to Check Status Development and Debugging Tips FlexLogix Back Up on DeviceNet 115 The 1788 DNBO card s status indicators provide useful information e g determining which controller is primary about back up scanner status Table lists the indicators to monitor when checking back up status If this indicator Module status MS Back up status BS 1 The BS status indicator may not be labelled on current 1788 D exhibits this behavior Flashing red Solid green this condition exists A secondary controller was not found or other minor fault detected This scanner is the primary controller Flashing green This scanner is a qualified secondary controller Off This scanner is not configured for back up mode BO communication cards When you implement the FlexLogix Back Up on DeviceNet solution we recommend you consider the following development and debugging tips e Develop and debug the entire application with only the primary controller and scanner present When the application is totally verified then download the program and exact same scanlist to the secondary controller without the primary controller present Verify that the secondary is also functioning properly and then both primary and secondary can be added to the network at the same time No configuration parameters a
26. how to e produce a tag e consume a tag e produce a large array The Logix5000 Controllers Design Considerations Reference Manual 1756 RM094 provides guidelines on how to e create produced and consumed tags e specify an RPI e manage connections Manage Controller Communications 47 Send and Receive Messages See e Logix5000 Controllers Common Procedures Manual 1756 PMO01 e Logix5000 Controllers Design Considerations Reference Manual If the message executes Messages transfer data to other devices such as other controllers or operator interfaces Messages use unscheduled connections to send or receive data Connected messages can leave the connection open cache or close the connection when the message is done transmitting This message type With this Isaconnected The message communication message can be cached method CIP data table read or write 3 3 PLC2 PLC3 PLC5 or SLG CIP fall types CIP with Source ID DH 3 3 CIP generic your option 32 block transfer read or write 3 3 You can connect CIP generic messages But for most applications we recommend you leave CIP generic messages unconnected 2 Consider caching only if the target module requires a connection Connected messages are unscheduled connections on both ControlNet and EtherNet IP networks Each message uses one connection regardless of how many devices are in the message path You can programmatically ch
27. not match 5 Faulted back up scanner back up node number failure e g the back up scanner is not using a node number the primary node number 1 6 Back up scanner pending primary detection 254 Attempting primary access 255 Attempting back up access Publication 1794 UM001G EN P January 2007 114 FlexLogix Back Up on DeviceNet Reading Back up Status You can read the back up status of the DeviceNet scanner with a single rung of ladder logic The back up state is useful for debugging or more sophisticated back up schemes The message in this rung uses the SINT data type Figure shows the rung you can use to read the back up state OPTIONAL Constantly Read Backup Status Bits Bit 0 No Backup Scanner Detected Bit 1 Primary Scanner forcing IDLE Backup in RUN but Primary in IDLE Read_Backup_Status EN Message Configuration Read_Backup_Status Get Attribute Single ha HEH fi Publication 1794 UM001G EN P January 2007 MSG 4 E Type CIP Generic Message Control Read_Backup_Status D R m Mov Move Source Backup_Status Dest Rung 6 message configuration and communication tabs Message Configuration Read_Heartbeat Backup_Status Table describes the possible values this message may return when reading the back up status of the DeviceNet scanner If the message reads the back up state of the DeviceNet scanner is this value 0 No back up scanner
28. o Control Line No Handshake 7 RTS Send Delay O 20ms RTS Off Dela 0 x20 ms DCD Wait Delay x1 sec Cancel Apply Help 1 Select ASCII protocol fi Controller Properties PLSSampleProject Date Time Advanced SFC Execution File Redundancy Nonvolatile Memory Memory General SerialPort System Protocol User Protocol Major Faults Minor Faults 2 Specify ASCII character settings Protocol C Read write Buffer Size gz H Bytes Termination Character 1 2 SFF Append Character 1 is kg F XONAXOFF I Echo Made Delete Mode Ignore N C CRT C Printer Cancel Apply Help Publication 1794 UM001G EN P January 2007 Communicate over Networks 37 The controller supports several instructions to manipulate ASCII characters The instructions are available in ladder diagram LD and structured text ST Read and write ASCII characters If you want to Use this instruction determine when the buffer contains termination characters ABL count the characters in the buffer ACB clear the buffer ACL clear out ASCII Serial Port instructions that are currently executing or are in the queue obtain the status of the serial port control lines AHL turn on or off the DTR signal turn on or off the RTS signal read a fixed number of characters ARD read a varying number of characters up to and including the ARL first set of termination
29. power supplies and make sure there is sufficient power for the communication adapter and modules Publication 1794 UM001G EN P January 2007 54 Place Configure and Monitor 0 Place Local 1 0 Modules The FlexLogix controller supports a local DIN rail of as many as 8 I O modules and an extended local DIN rail of as many as 8 I O modules The second DIN rail is optional See e FLEX I O Analog Modules User Manual 1794 6 5 2 e FLEX I O Digital Modules User local DIN rail extended local DIN rail gt Selecting a Power Supply In a FlexLogix system select an Allen Bradley power supply In applications that must be compliant with CSA requirements use a Separated Extra Low Voltage SELV power supply that is compliant with IEC 61010 1 Annex H When selecting power supplies e Provide power for the controller separately from the power for the FLEX I O modules To provide power for FLEX I O modules follow the guidelines in the documentation for those modules e When providing power for the 1794 FLA extended local I O adapter treat the adapter as a communication adapter not as an T O module 1794 FLEX power supplies The following power supplies available for use with the FlexLogix system Catalog number Nominal Input Maximum Maximum Maximum Output current input voltage real input apparent input transformer voltage range p
30. programming software 1 In the Controller Organizer select Controller Tags Right click to display the Data Monitor So RSLogix 5000 examples 1794 File Edit View Search Logic Cor alela S e Path lt none gt B Controller examples E Controller Fault Handler 2 Expand the data display as necessary Controller Tags examples controller Scope Jexamples controller 7 Show Show All yj Sot Tag Name 7 7 Value Local 0 C Local 0 1 am an fi 2 0000_0000_0000_0000_0000_0000_0000_0 00 Local l SlotStatusBits Local Data Local 0 Local2 If you have an extended local DIN rail LOCAL2 ora split rail the modules after the 1794 CE1 CE3 cable will fault if the cable is disconnected In this case all outputs are reset regardless of the module configurations You can write logic to monitor the rack bits and take appropriate action if a fault occurs For example the following logic determines whether an error occurs on the Local rail Then the logic determines whether the error occurred at the module in slot 0 You can continue this logic to check each module on the rail F v ve e D se ne ie A Pan Ras F Identify if a fault exists on the rack optimized local rail NEG Locl_error Not Equal o 4 Source A Local SlotStatusBits 2 00
31. this you ase making cenan that you have a backup copy of the anginal sample project that will be poeserved for funuse ene BS Lognc 00 sample projects may indude a mamber of components that you will need to copy mdrashsaby in onder for the sample pacject components tn function propesly in your application These may include bur axe not brated 90 apang ine an eestng poea confor may ocne wet compccent that deeady ear ce the location ot type c moduler does not match the location anramed in the ample project In that case you may need to sezame compone change locations oe make other modifications a necerary x 00 Compuse uty fiechaded on your RSiLoggx SUD voftwase CID to compane the rampie proyect p Sie with an ampe 6 a mao protect fle Thea wil help yos to identify the components you need to modify Refer tothe online bep incueded with the RSLogex S Compare wakey for more snformenon on perio the compawan Sample Projects Chick oe any of Ge ndiadsal vendor names to see the bet of umple peoyect they have pootided Soc tus rebeare provides information on how to select which task to use configure tasks prioritize tasks inhibit tasks Develop Applications 75 Organize Tags With a Logix5000 controller you use a tag alphanumeric name to address data variables In Logix5000 controllers there is no fixed numeric format The tag name itself identifies the data This lets you See e organize your data to mirror y
32. 001 provides information on how to e communicate with an ASCII device e transmit receive ASCII characters Modbus support To use Logix5000 controllers on Modbus you connect through the serial port and execute specific ladder logic routines A sample controller project is available with RSLogix 5000 Enterprise programming software From RSLogix 5000 software select Help gt Vendor Sample Projects to display a list of available sample projects DH 485 1761 NET AIC Communicate over Networks 39 For DH 485 communication use the serial port of the controller However when using a FlexLogix controller it is recommended that you use NetLinx networks EtherNet IP ControlNet or DeviceNet because excessive traffic on a DH 485 network may make it impractical to connect to a controller with RSLogix 5000 programming software If your application uses Select connections to existing DH 485 networks built in serial port The DH 485 protocol uses RS 485 half duplex as its physical interface RS 485 is a definition of electrical characteristics it is not a protocol You can configure the RS 232 port of the FlexLogix controller to act as a DH 485 interface By using a 1761 NET AIC and the appropriate RS 232 cable 1756 CP3 or 1747 CP3 a FlexLogix controller can send and receive data on a DH 485 network FlexLogix controller 1747 CP3 lt or
33. 00_0000_0000_0000_ Source B 0 If fault exists and it is slot 0 set slot O fault bit Locl_eror Local l SlotStatusBits 0 slot0_faulted lt l Publication 1794 UM001G EN P January 2007 66 Place Configure and Monitor 0 Reconfigure an I 0 Module Publication 1794 UM001G EN P January 2007 If an I O module support reconfiguration you can reconfigure the module via e Module Properties dialog in RSLogix 5000 software e MSG instruction in program logic WARNING Use care when changing the configuration of an 1 0 module You could inadvertently cause the 1 0 module to operate N incorrectly Reconfigure a module via RSLogix 5000 software To change the configuration of an I O module via RSLogix 5000 software highlight the module in the I O Configuration tree Right click and select Properties Ea Module Properties flex_adapter 0 1794 IB16D A 1 1 General Connection Module Info Configuration Type 1794 1B16D7A 16 Point 24V DC Diagnostic Input Sink Vendor Allen Bradley Parent flex_adapter Name fremote_diagnostic_input Slot 0 a Description Ea Comm Format Rack Optimization Revision A Electronic Keying Compatible Keying x Status Offline Cancel Apply Help Place Configure and Monitor I O 67 Reconfigure a module via a MSG instruction To change the configuration of an I O module programmatically use a MSG instruction of type Module Reconfigure t
34. 01G EN P January 2007 46 Manage Controller Communications This type of tag produced consumed For more information Publication 1794 UM001G EN P January 2007 Description A produced tag allows other controllers to consume the tag which means that a controller can receive the tag data from another controller The producing controller uses one connection for the produced tag and one connection for each consumer The controller s communication device uses one connection for each consumer As you increase the number of controllers that can consume a produced tag you also reduce the number of connections the controller and communication device have available for other operations like communications and 1 0 Each consumed tag requires one connection for the controller that is consuming the tag The controller s communication device uses one connection for each consumer For two controllers to share produced or consumed tags both controllers must be attached to the same control network such as a ControlNet or Ethernet IP network You cannot bridge produced and consumed tags over two networks The total number of tags that can be produced or consumed is limited by the number of available connections If the controller uses all of its connections for I O and communication devices no connections are left for produced and consumed tags The Logix5000 Controllers Common Procedures Manual 1756 PM001 provides information on
35. 16 48ms for most applications The recommended heartbeat times result in switchover times of 32 96ms However these times do not include controller scan delays IMPORTANT If multiples of 8 are not used for the requested heartbeat then the DeviceNet scanner uses the next higher supported heartbeat value that can be read from the scanner For example if you set the heartbeat to 10 the scanner uses a 16ms heartbeat FlexLogix Back Up on DeviceNet 109 Setting the Heartbeat Constant You can set the heartbeat constant with five rungs of ladder logic Figure shows rungs 0 amp 1 and the message set up used in rung 1 The message in rung 1 uses the INT data type START OF BACKUP INITIALIZATION THE FOLLOWING RUNGS ENABLE BACKUP AS SOON AS PROCESSOR IS CHANGED TO RUN MODE OR IF SCANNER IS MANUALLY CHANGED FROM RUN TO IDLE WITH PROCESSOR IN RUN MODE NOTE SCANNER IS IDLE WHEN CommandRegister Run 0 Initialize heartbeat constant in milliseconds multiple of 8 16 256 Heartbeat is the heartbeat between redundant 1788 DNBQs to detect failure of the processor or scanner switchover Loss of two consecutive heartbeats causes a MOY DeviceNet 0 CommandRegister Run Z Move Source Config_Heartbeat 16 Dest Config_Heartbeat 16 First read Heartbeat Configuration to see if Scanner already configured If after powerup keep reading until scanner is available Get_Attrib_Single to Class 0x90
36. 3 How can we make this publication more useful for you 2 3 Can we add more information to help you Completeness all necessary information procedure step illustration feature is provided a example guideline other explanation definition Technical Accuracy 1 2 3 Can we be more accurate all provided information l is correct text illustration Clarity 1 2 3 How can we make things clearer all provided information is easy to understand Other Comments You can add additional comments on the back of this form Your Name Your Title Function Would you like us to contact you regarding your comments Location Phone ___No there is no need to contact me Yes please call me Yes please email me at Yes please contact me via Return this form to Rockwell Automation Technical Communications 1 Allen Bradley Dr Mayfield Hts OH 44124 9705 Fax 440 646 3525 Email RADocumentComments ra rockwell com Publication ClG C0521C EN P May 2003 PN953014 91957782 91 Other Comments PLEASE FASTEN HERE DO NOT STAPLE PLEASE FOLD HERE BUSINESS REPLY MAIL FIRST CLASS MAIL PERMIT NO 18235 CLEVELAND OH POSTAGE WILL BE PAID BY THE ADDRESSEE Allen Bradley RELIANCE JS ELECTRIC ROCKWELL FESS SOFTWARE DODGE Rockwell Automation 1 ALLEN BRADLEY DR MAYFIELD HEIGHTS OH 44124 9705 NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES PLEASE REMOVE Rockwell Automat
37. 7 software use 25 unscheduled 27 Publication 1794 UM001G EN P January 2007 D design 12 develop application define tasks 71 73 fault handler 81 for more information 74 monitor connection 80 82 monitor status 79 overview 69 programming language 76 programs 70 sample controller projects 74 tag 75 task 69 using event task 85 87 DeviceNet distributed 1 0 61 example configuration 29 FlexLogix back up on the network 103 116 for more information 30 module capability 29 overview 28 30 software use 29 DF1 device 33 DH 485 cables 40 controller communication 39 41 controller configuration 41 overview 39 DHCP 22 direct connection 57 distributed 1 0 ControlNet 60 DeviceNet 61 EtherNet IP 59 overview 21 E electronic keying 56 equipment phase compared to PackML 94 compared to S88 94 instructions 89 monitor 94 overview 89 equipment phase instructions overview 89 EtherNet IP connection use 24 distributed 1 0 59 Publication 1794 UM001G EN P January 2007 example configuration 23 for more information 24 module capability 23 overview 22 24 software use 22 event tasks 85 87 example system 11 F fault data 64 fault handler 81 FBD 76 function block diagram 76 G GSV instruction 79 H hardware installation 13 1 0 address data 62 communication format 56 configuration folder 55 configure 53 connection use 57 COS 56 determine update 63 direct connection 57 distributed via ControlNet 60 distrib
38. Allen Bradley FlexLogix Controller System User Manual 1794 L34 Firmware Revision 16 User Manual Nees seers a Rockwell Automation Important User Information Solid state equipment has operational characteristics differing from those of electromechanical equipment Safety Guidelines for the Application Installation and Maintenance of Solid State Controls publication SGI 1 1 available from your local Rockwell Automation sales office or online at http literature rockwellautomation com describes some important differences between solid state equipment and hard wired electromechanical devices Because of this difference and also because of the wide variety of uses for solid state equipment all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable In no event will Rockwell Automation Inc be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment The examples and diagrams in this manual are included solely for illustrative purposes Because of the many variables and requirements associated with any particular installation Rockwell Automation Inc cannot assume responsibility or liability for actual use based on the examples and diagrams No patent liability is assumed by Rockwell Automation Inc with respect to use of information circuits equipment or s
39. Autodetect v For more information Publication 1794 UM001G EN P January 2007 The Logix5000 Controllers General Instructions Reference Manual 1756 RMO003 defines the instructions you can use to manipulate ASCII characters The SCADA System Application Guide AG UM008 provides information on how to e select a polling mode e configure controllers modems and software e troubleshoot basic DF1 protocol issues Communicate over Networks 35 Communicate with ASCII devices When configured for user mode you can use the serial port to interface with ASCII devices For example you can use the serial port to e read ASCII characters from a weigh scale module or bar code reader e send and receive messages from an ASCII triggered device such as a MessageView terminal connection from the serial port of the controller to the ASCII device we a Publication 1794 UM001G EN P January 2007 36 Communicate over Networks To configure the controller for ASCII communications On this tab Do this 1 Select User Mode f Controller Properties PLSSampleProject Date Time Advanced SFC Execution File Redundancy Nonvolatile Memory Memory General Serial Port System Protocol User Protocol Major Faults Minor Faults 2 S pec i fy communication settin gs Mode Use E R Baud Rate 13200 v Data Bits 8 fhd Parity None Stop Bits Moo
40. BATTERY LED turns on when you apply power to the controller the battery life may be less than the table above indicates Some of the warning time may have been used while the controller was off and unable to turn on the BATTERY LED i Because the controller uses a lithium battery you must follow specific eplacing a battery precautions when handling or disposing a battery The controller uses a lithium battery which contains potentially dangerous chemicals Before handling or disposing a battery review Guidelines for Handling Lithium Batteries publication AG 5 4 1 Turn off power to the FlexLogix controller 2 Does the existing battery show signs of leakage or damage If Then Yes Before handling the battery review Guidelines for Handling Lithium Batteries publication AG 5 4 No Go to the next step Publication 1794 UM001G EN P January 2007 100 Maintain the Battery 3 Remove the old battery 4 Install a new 1756 BA1 battery Only install a 1756 BA1 battery If you install a different battery you may damage the controller 5 Attach the battery label a Write on the battery label the date you install the battery b Attach the label to the inside of the battery compartment 6 On the front of the controller is the BATTERY LED off If Then Yes Go to the next step No A Check that the battery is correctly connected to the controller B If the BATTERY LED remains on install a
41. Held Holding Held Holding Held Restarting none Restarting Stopping Stopped Stopping Stopped Stopping Stopped Aborting Aborted Minimum System Requirements Publication 1794 UM001G EN P January 2007 Aborting Aborted Aborting Aborted To develop PhaseManager programs you need e FlexLogix controller with firmware revision 15 0 or later e communication path to the controller e RSLogix 5000 software version 15 0 or later To enable PhaseManager support you need the full or professional editions of RSLogix 5000 software or the optional PhaseManager add on 9324 RLDPMENE to your RSLogix 5000 software package Configure PhaseManager 95 i The controller supports several instructions to support equipment quipmen ase P p q Instructions phases The instructions are available in ladder diagram LD and structured text ST If you want to Use this instruction signal a phase that the state routine is complete so go to the PSC next state change the state or substate of a phase PCMD signal a failure for a phase PFL clear the failure code of a phase PCLF initiate communication with RSBizWare Batch software PXRO clear the NewlnputParameters bit of a phase PRNP set up breakpoints within the logic of a phase PPD take ownership of a phase to either PATT e prevent another program or RSBizWare Batch software from commanding a phase e make sure another program or RSBizWare Batch software does n
42. Instance 0x01 Attrib 012 DeviceNet 0 CommandRegister Run Read_Heartbeat EN MSG ae Type CIP Generic Message Control Read_Heartbeat Db p Rung 1 message configuration and communication tabs Message Configuration Read_Heartbeat Message Configuration Read_Heartbeat Get Attribute Single E ee Communication Method SoHe Chane Hey po sia o a Gera fi fiz Publication 1794 UM001G EN P January 2007 110 FlexLogix Back Up on DeviceNet Figure shows rung 2 and the message set up used on it The message in rung 2 uses the INT data type If Scanner Configuration needs updating set the Heartbeat using MSG instruction to scanner Set_Attrib_Single to Class 0x90 Instance 0x01 Attrib 0x12 DeviceNet 0 CommandRegister Run Read_Heartbeat DN EQ c Not Equal Source 4 Current_Heartbeat 0 Source B Config_Heartbeat 16 Type CIP Genetic Message Control Set_Heartbeat 7 Rung 2 message configuration and communication tabs Message Configuration Set_Heartbeat Message Configuration Read_Heartbeat Set Attribute Single z D Communication Met ian E Hed foo Destination ii Source Linke zd ictal Do h M Cache Connections Publication 1794 UM001G EN P January 2007 FlexLogix Back Up on DeviceNet 111 Figure shows rungs 3 amp 4 and the message set up used on it The message in rung 3 uses the INT data type If new Heartbeat has been set
43. MSTD process control structured tex Moving Standard Deviation function block MUL general relay ladder Multiply structured tex function block MUX process control function block Multiplexer MVM general relay ladder Masked Move Publication 1794 UM001G EN P January 2007 Instruction Location Languages MVMT general structured tex Masked Move with Target unction bloc NEG general relay ladder Negate structured tex unction bloc NEO general relay ladder Not Equal to structured tex unction bloc NOP general relay ladder No Operation NOT general relay ladder Bitwise NOT structured text function block NTCH process control structured text Notch Filter function block OCON general function block Output Wire Connector ONS general relay ladder One Shot OR general relay ladder Bitwise OR structured text function block OREF general function block Output Reference OSF general relay ladder One Shot Falling OSFI general structured text One Shot Falling with Input function block OSR general relay ladder One Shot Rising OSRI general structured text One Shot Rising with Input function block OTE general relay ladder Output Energize OTL general relay ladder Output Latch OTU general relay ladder Output Unlatch PATT phase relay ladder Attach to Equipment Phase structured tex PCLF phase relay ladder Equipment Phase Clear Failure structured tex PCMD phase relay ladder Equipment Phase Command structured tex PDET phase relay ladde
44. Net IP network 1769 L35E CompactLogix F j controller ME ad personal computer The FlexLogix controller in this example uses these connections Connection Type Device Connections Total Quantity per Device Connections controller to installed DeviceNet communication card 1 2 2 controller to installed EtherNet IP communication card 1 0 0 controller to RSLogix 5000 programming software 1 1 1 message to ControlLogix controller 2 1 2 produced tag consumed by CompactLogix controller 2 1 2 9 total Publication 1794 UM001G EN P January 2007 Chapter 5 Place Configure and Monitor 0 Use This Chapter For this information See Select I O Modules 53 Place Local 1 0 Modules 54 Configure 1 0 55 Configure Distributed I O on EtherNet IP 59 Configure Distributed I O on ControlNet 60 Configure Distributed 1 0 on DeviceNet 61 Address 0 Data 62 Determine When Data Is Updated 63 Reconfigure an 1 0 Module 66 Select I O Modules When selecting 1794 FLEX I O modules select e Select a communication adapter Choose the network for your operating system See e FLEX I O and FLEX EX Selection Guide 1794 SG002 e Select I O modules based on field devices e Select a terminal base Choose an appropriate terminal base for your modules e Select
45. RPI is The EtherNet IP card effectively supports a maximum of this many communication connections 2 ms 2 4ms 5 8 ms 10 16 ms 18 32 ms 25 In the table above with an RPI of 32 ms and greater the EtherNet IP card effectively supports 25 communications connections In this case the remaining 7 connections can be used for non I O purposes The EtherNet IP Modules in Logix5000 Control Systems User Manual ENET UM001 provides information on how to e configure an EtherNet IP communication module o control I O over EtherNet IP e send a message over EtherNet IP e produce consume a tag over EtherNet IP e monitor diagnostics e calculate controller connections over EtherNet IP The Logix5000 Controllers Design Guidelines Reference Manual 1756 RM094 provides guidelines on optimizing a control application on an EtherNet IP network ControlNet See ControlNet Modules in Logix5000 Control Systems User Manual CNET UMO01 Logix5000 Controllers Design Considerations Reference Manual 1756 RM094 ControlNet Daughtercard Installation Instructions 1788 INO02 ControlNet Daughtercard Installation Instructions Communicate over Networks 25 For ControlNet communications install a ControlNet communication card in your FlexLogix controller Use this card 1788 CNF 1788 CNFR 1788 CNC 1788 CNCR If you are using fiber media coaxial media Use these software products when you use a FlexLogix controller
46. Systems User Manual DeviceNet See e DeviceNet Modules in Logix5000 Control Systems User Manual DNET UM004 e Logix5000 Controllers Design Considerations Reference Manual 1756 RM094 e DeviceNet Daughtercard FlexLogix system with CNET UMO001 provides information on how to e configure a ControNet communication module e control I O over ControlNet e send a message over ControlNet e produce consume a tag over ControlNet e calculate controller connections over ControlNet The Logix5000 Controllers Design Guidelines Reference Manual 1756 RM094 provides guidelines on optimizing a control application on a ControlNet network The DeviceNet network uses the Common Industrial Protocol CIP to provide the control configuration and data collection capabilities for industrial devices For DeviceNet communications install a 1788 DNBO communication card in your FlexLogix controller CompactLogix controller PLC 5 controller with 1788 DNBO card with 1769 SDN 1771 SDN scanner module al DeviceNet network sensor a mememe Soaoan IS S pushbutton O amm at motor LJ PanelView lapto terminal ptop Publication 1794 UM001G EN P January 2007 i
47. a system shared data Publication 1794 UM001G EN P January 2007 Develop Applications n Defining tasks A task provides scheduling and priority information for a set of one or more programs You can configure tasks as continuous periodic or event Only one task can be continuous A task can have as many as 100 separate programs each with its own executable routines and program scoped tags Once a task is triggered activated all the programs assigned to the task execute in the order in which they are grouped Programs can only appear once in the Controller Organizer and cannot be shared by multiple tasks Specifying task priorities Each task in the controller has a priority level The operating system uses the priority level to determine which task to execute when multiple tasks are triggered You can configure periodic tasks to execute from the lowest priority of 15 up to the highest priority of 1 A higher priority task will interrupt any lower priority task The continuous task has the lowest priority and is always interrupted by a periodic task The FlexLogix controller uses a dedicated periodic task at priority 6 to process I O data This periodic task executes at the RPI you configure for the FlexBus which can be as fast as once every 2 ms Its total execution time is as long as it takes to scan the configured I O modules How you configure your tasks affects how the controller receives
48. ai luxsiciets oie e Pee eee Nad RY as 38 DHAS ace hse 8 Sof eee ed cece bash ieee Pues eS eas 39 Third Pary nt BNE Getta A ves R de A OSE aD a Pied i ated 42 Communication Format ooo kb ab dns ead bow a 42 Connection Parameters 0 0 0 ee 42 Chapter 4 Use This Chapter u s 4 ho ke eRe ED Oe eee Ae ae 45 Produce and Consume Interlock Data 45 Send and Receive Messages 4 5 ahah eine eae toes 47 Determine whether to cache message connections 47 Connection OVerview 4 04 nde een ee Mkt ee Eee eae 49 Calculate Connection Use igi jock okt de soe pe eo ee Aen ows 50 Connections Pxamples lt 45 3 pec t45 s2oces poe sa Se 8 eS4 52 Publication 1794 UM001G EN P January 2007 4 Table of Contents Place Configure and Monitor 1 0 Develop Applications Publication 1794 UM001G EN P January 2007 Chapter 5 Use This Chapter re am car tine on te retreat Zee E E cee E 53 Select I O Modules a8 44S ad ele Fe ne ate Ye lb eae 53 Place Local I O Modules sete inst amp on iene kee Sakae a deed Rea oS 54 Selecting a Power Supply 0 0 0 0 0 00 eee 54 COMiGuie On e tuna ee eae kets Bae oe SPR e ee eet 55 I O COMMECHONS 4 Ghis a5h amp beh h do OS Oe 4 ch eG RGR 57 Configure Distributed I O on EtherNet IP 59 Configure Distributed I O on ControlNet 60 Configure Distributed I O on DeviceNet 61 Address I OCA As uee tinira nae teil es OE ERE eG meets 62 Dete
49. ample shows the task execution order for an application with periodic tasks and a continuous task Task Priority Level Task Type Example Execution Worst Case Completion Time Time 1 5 20 ms periodic task 2 ms 2 ms 2 6 dedicated I O task ms 3ms 5 ms selected RPI 3 10 10 ms periodic task 4ms 8 ms 4 none lowest continuous task 25 ms 60 ms Task 3 0 5 10 15 20 25 30 35 40 45 50 55 60 65 Time ms Publication 1794 UM001G EN P January 2007 Develop Applications 73 Notes A The highest priority task interrupts all lower priority tasks B The dedicated I O task can be interrupted by tasks with priority levels 1 to 7 The dedicated I O task interrupts tasks with priority levels 7 to 15 This task runs at the selected RPI rate scheduled for the FlexLogix system 5 ms in this example C The continuous task runs at the lowest priority and is interrupted by all other tasks D A lower priority task can be interrupted multiple times by a higher priority task E When the continuous task completes a full scan it restarts immediately unless a higher priority task is running Defining programs Each program contains program tags a main executable routine other routines and an optional fault routine Each task can schedule as many as 100 programs The scheduled programs within a task execute to completion from first to last Programs that are not attached to any task show up as unscheduled pro
50. and add the card to the I O configuration folder e add a ControlNet adapter and I O modules to the I O Configuration folder of the controller Within the I O Configuration folder you organize the modules into a hierarchy tree branch parent child For a typical distributed 1 0 network built n remote ControlNet port adapter controller device you build the 1 0 configuration in this order a Controller Tags Controller Fault Handler Power Up Handler 6 Tasks Z fa MainTask E B MainProgram Unscheduled Programs f Phases H 6 Motion Groups Ungrouped Axes i Trends Data Types Gi User Defined El oa Strings Ep Predefined H E Module Defined 2 6 1 0 Configuration 3 Backplane FlexLogix System a 1794 134 My_Project gt 1788 CNF A local_card les ControlNet a 1 1788 CNF A local_card 2 1794 ACNI15 C Flex_adapter FlexBus amp 0 1794 IE4X0E2 B combo_analog 1 1794 1T8 4 thermocouple_module g FlexBus Local g FlexBus Local2 1 Add the local communication card 2 Add the remote adapter for the distributed 1 0 chassis or DIN rail For more information See ControlNet Communication Modules in Logix5000 Control Systems User Manual CNET UMO01 Publication 1794 UM001G EN P January 2007 Place Configure and Monitor I O 61 Configure Distributed 1 0 To communicate with the I O modules over Device you add the on DeviceNet DeviceNet bridge to the I
51. ange the target of a MSG instruction to optimize message transfer time Determine whether to cache message connections When you configure a MSG instruction you have the option of whether or not to cache the connection Then repeatedly Cache the connection This keeps the connection open and optimizes execution time Opening a connection each time the message executes increases execution time infrequently Do not cache the connection This closes the connection upon completion of the message which frees up that connection for other uses Publication 1794 UM001G EN P January 2007 48 Manage Controller Communications The controller has the following limits on the number of connections that you can cache If you have this software Then you can cache and firmware revision 11 x or earlier e block transfer messages for up to 16 connections e other types of messages up to 16 connections 12 x or later up to 32 total connections For more information The Logix5000 Controllers General Instructions Reference Manual 1756 RMO003 describes how to use the MSG instruction The Logix5000 Controllers Common Procedures Manual 1756 PM001 provides information on how to e execute a MSG instruction e get and set the number of unconnected buffers e convert INT data to DINT data e manage multiple MSG instructions e send one MSG to multiple devices Publication 1794 UM001G EN P January 2007 Manage Controller Communicat
52. ant simplifying online troubleshooting of your Add On Instructions Each instruction contains a revision a change history and an auto generated help page Create Custom Help When you create an instruction you enter information for the description fields in software dialogs information that becomes what is known as Custom Help Custom Help makes it easier for users to get the help they need when implementing the instructions Apply Source Protection As the creator of Add On Instructions you can limit users of your instruction s to read only access or you can bar access to the internal logic or local parameters used by the instruction s This source protection lets you prevent unwanted changes to your instruction s and protects your intellectual property The Logix5000 Controllers Common Procedures Manual 1756 PM001 provides information on how to e design and program sequential function chart SFC logic e program structured text ST logic e program ladder diagram LD logic e program function block diagram FBD logic e force logic The Logix5000 Controllers Execution Time and Memory Use Reference Manual publication 1756 RM087 provides information on memory use and execution times for instructions Monitor Controller Status GSV Get System Value Class name Instance name Attribute Name Dest SY Set System Value Class name Instance name Attribute Name Source For more information Develop Applicat
53. aracteristics on the Serial Port tab default values are shown in bold Characteristic Baud Rate Description Specifies the communication rate for the DH 485 port All devices on the same DH 485 network must be configured for the same baud rate Select 9600 or 19200 Kbps Node Address Specifies the node address of the controller on the DH 485 network Select a number 1 31 decimal inclusive To optimize network performance assign node addresses in sequential order Initiators such as personal computers should be assigned the lowest address numbers to minimize the time required to initialize the network Token Hold Factor Maximum Node Address Number of transmissions plus retries that a node holding a token can send onto the data link each time that it receives the token Enter a value between 1 4 The default is 1 Specifies the maximum node address of all the devices on the DH 485 network Select a number 1 31 decimal inclusive To optimize network performance make sure e the maximum node address is the highest node number being used on the network e that all the devices on the same DH 485 network have the same selection for the maximum node address For more information The Data Highway Data Highway Plus Data Highway I Data Highway 485 Cable Installation Manual 1770 6 2 2 describes how to plan and install a DH 485 network Publication 1794 UM001G EN P January 2007 42 Communicate over Network
54. ase E Mix Phase E Drain Phase E Space Parts Phase Here s how the PhaseManager into RSLogix 5000 programming software A PHASE tag gives you the status of an equipment phase Name amp Data Type _ Add water PHASE Add_Water State DINT Add_Water Running BOOL Add Water Holding BOOL _ Add_Water Restarting BOOL An equipment phase directs 1 activity of your equipment A state model divides the activity into a series of states Running State Routine How to add y y y water E MainProgram Ce My Equipment Program Publication 1794 UM001G EN P January 2007 Equipment phase instructions control the transitions between states handle faults etc PSC POVR PCLF PRNP PATT PCMD PFL PXRO PPD PDET Other code does the specific actions of your equipment Water Feed Conveyor Enable Axes i Configure PhaseManager 91 State Model Overview A state model divides the operating cycle of your equipment into a series of states Each state is an instant in the operation of the equipment It s the actions or conditions of the equipment at a given time In a state model you define what your equipment does under different conditions such as ru
55. control structured text JK Flip Flop function block JMP genera relay ladder Jump to Label JSR genera relay ladder Jump to Subroutine structured text function block JXR genera relay ladder Jump to External Routine LBL genera relay ladder Label LDL2 process control structured tex Second Order Lead Lag function block LDLG process control structured tex Lead Lag function block LEO genera relay ladder Less Than or Equal to structured tex function block LES genera relay ladder Less Than structured tex function block LFL genera relay ladder LIFO Load LFU genera relay ladder LIFO Unload LIM genera relay ladder Limit function block L genera relay ladder atural Log structured tex function block LOG genera relay ladder Log Base 10 structured tex function block LOWER genera relay ladder Lower Case structured tex LPF process control structured tex Low Pass Filter function block AAT motion relay ladder otion Apply Axis Tuning structured tex AFR motion relay ladder otion Axis Fault Reset structured tex AG motion relay ladder otion Axis Gear structured tex AH motion relay ladder otion Axis Home structured tex Instruction Locator 119 Instruction Location Languages MAHD motion relay ladde Motion Apply Hookup structured tex Diagnostics MAJ motion relay ladde Motion Axis Jog structured tex MA motion relay ladde Motion Axis Move structured tex MAOC motion relay ladde Mo
56. ctLogix controller J Distributed 1 0 with built in Control port L PowerFlex 700S drive e N i Z mje E z s l il Pa amp pa E 1756 CNB module H B S K as an adapter with a K 1756 I O modules ControlNet Poh NET oA 4 r _ 2 FlexLogix controller with ii gt 1794 ACN15 adapter 1788 CNC card i 4 PanelView terminal 7 with 1794 I O modules il A 1734 ACNR adapter with CE Is i 1734 1 0 modules Pa PLC 5 40C controller ef Connections over ControlNet You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system Connections are allocations of resources that provide Publication 1794 UM001G EN P January 2007 Communicate over Networks 27 more reliable communications between devices compared to unconnected messages ControlNet connections can be Connection method scheduled Description A scheduled connection is unique to ControlNet communications A scheduled connection unique to ControlNet lets you send and receive data repeatedly at a predetermined interval which is the requested packet interval RPI For example a connection to an I O module is a scheduled connection because you repeatedly receive data from the module at a specified interval Other scheduled connections include connections to e communication devices e produced consumed tags Ona ControlNet network y
57. cts to display a list of available sample projects RSLogix 5000 Programming Software Vendor Sample Projects About the RSLogix 5000 Sample Projects Yoru AS Logix 1000 sofresee comes with many sample ponjects yers can we so make it eases to casate your Harting point See your rey copy end paste posject components from one pesject to anodu Along vida the cary cb pomades ty ackwrl Automsace are many peomded by other vendon that may eant yos im creating pacyects 3 ose with that parbcutlac vadot pedira Sampie pocjects are prreded at examples ony end mest be ured with case Reser to the Disclaimer at the end of tar document and 1 the find Uner License Agreement HULA included ix the BSLogar S000 Raleane Notes Se additional information Foo additonal areatance e wedong wth sample piech in general pleave comtact pour T echmcal Suppoet srpemernaave for spaa quemcen selates to a Senor t ampie pusvect pleace conte the parcar verios foc amnetance Remember thet a with any sew pengram yora thon tea the tampir poogram to make certun chat it woeks wh your eppticesos bescee actually emplemeencg itn pour soxmel operations Mewe iter to the sexe sectae Woskeg With Jamele Proyece Se in cematicn ans wecomerendence co how 3 gt effectreety une there sample pecwca Working with Sample Projects Imponane Before you begn wing a sample ponjec make copy of the penject save st with anew name acd male any edin you need to make to din senamed piect By cong
58. dd an EtherNet IP adapter and I O modules to the I O Configuration folder of the controller Within the I O Configuration folder you organize the modules into a hierarchy tree branch parent child For a typical distributed 1 0 network you build the 1 0 configuration in this order 1 Add the local communication card 2 Add the remote adapter for the distributed 1 0 chassis or DIN rail EtherNet IP card remote controller adapter device I Controller Tags Controller Fault Handler Power Up Handler Tasks a MainTask ic G MainProgram Unscheduled Programs Phases Motion Groups Ungrouped Axes Trends 5 6 Data Types GB User Defined E oe Strings El E Predefined H Module Defined 5 6 1 0 Configuration 5 8 Backplane FlexLogix System aE 1794 134 My_Project gt 1788 ENBT A local_card E a Ethernet b 1788 ENBT A local_card gt FY 1794 AENT A flex_adapter FlexBus amp 0 1794 IB16D A diagnostic_input 8 1 1794 0F41 4 analog_output g FlexBus Local g FlexBus Local2 For more information See EtherNet IP Communication Modules in Logix5000 Control Systems User Manual ENET UMO001 Publication 1794 UM001G EN P January 2007 60 Place Configure and Monitor 1 0 Configure Distributed 1 0 To communicate with distributed I O modules over ControlNet you on ControlNet e install a 1788 CNx communication card in your FlexLogix controller
59. de DINT to String structured tex BTD genera relay ladder Bit Field Distribute DTR general elay ladde Data Transitional BTDT genera structured tex Bit Field Distribute with Target function block EOT general elay ladde End of Transition structured tex BTR genera relay ladder essage structured tex EQU general elay ladde Equal to structured tex BIW genera relay ladder unction block essage structured tex A ESEL process control structured tex BXOR genera structured tex Enhanced Select unction block Boolean Exclusive OR function block EVENT general elay ladde CLR genera relay ladder Trigger Event Task structured tex Clear structured tex FAL general elay ladde CMP genera relay ladder File Arithmetic and Logic Compare FBC general elay ladde CONCAT genera relay ladder File Bit Comparison String Concatenate structured tex FFL general elay ladde COP genera relay ladder FIFO Load Copy File structured tex Oy aeov gt vwvO FFU general elay ladde COS genera relay ladder FIFO Unload Cosine structured tex function block FGEN process control structured text Function Generator unction block CPS genera relay ladder Synchronous Copy File structured tex FIND general elay ladde Find String structured text CPT genera relay ladder Compute FLL general elay ladde File Fill CTD genera relay ladder Count Down FOR general elay ladde Fo CTU genera relay ladder Count Up FRD general elay ladde Convert to Integer unction block CTUD genera structured text
60. e Event Task 4 0 setae eae eek ee 86 Programmatically Determine if an EVENT Instruction Triggered Task cec by ia 8 anh EA e m aga WM sd 87 Checklist for an EVENT Instruction Task 87 Configure PhaseManager Maintain the Battery FlexLogix System Status Indicators FlexLogix Back Up on DeviceNet Instruction Locator Index Table of Contents 5 Chapter 7 Use THS aro a eer cnn rem mee Or er gee ne Or eee ee a O oe ra 89 PhaseManager Overview 650 a Guanes A Sek Bde ek eee ae 8 89 State Model Overview nd eee Gad active asked ek ed 91 How equipment changes states 0 0 92 Manually change states sos n n anaua 94 Compare PhaseManager to Other State Models 94 Minimum System Requirements 000 94 Equipment Phase Instructions ox 4 p44 x4 fs kOe eR OE DS 95 Chapter 8 Using this Appendix bos ad gncsdo hohe He bE whe ngeere ark 97 Storing Replacement Batteries ois iy agency aoe adn wh amp S 97 Estimating Battery eu Maas sad Gite ow naan a 98 Replacing a Battery n a each he os Bost one thus a eS eo sy 99 Appendix A Controler EIS ioe iio ie sai Slavs Ue ue Bite Rae hak oh eT nated 101 Appendix B Using This APPS Sy i tated dock be Bt tee acwnn eae a 103 How the Back up Works nay 274 Soles aca ea eee 104 Requirements of the Back Up 9 4 4 0 a 54 A458 oa SS 105 Power Up and System Start up 0 0 0 0 000000005 106 Developing the FlexLogix Back Up Application
61. e controller and upload and or download a project to the controller For this information See Be Connect the Controller via the Serial Port 15 e EtherNet IP Modules in Logix5000 Configure the Serial Driver 18 Control Systems User Manual ai nu Select the Controller Path 20 e ControlNet Modules in Logix5000 Control System User Manual CNET UM001 e DeviceNet Modules in Logix5000 Control System User Manual DNET UM004 e RSLinx software to configure the serial communication driver For the FlexLogix controller to operate on a serial network you need e a workstation with a serial port e RSLogix5000 programming software to configure the serial port of the controller Connect the Controller via The RS 232 port is a non isolated serial port built in to the front of the the Serial Port FlexLogix controller 1 Determine whether you need an isolator If you connect the controller to a modem or an ASCII device consider installing an isolator between the controller and modem or ASCII device An isolator is also recommended when connecting the controller directly to a programming workstation Publication 1794 UM001G EN P January 2007 16 Directly Connect to the Controller via the Serial Port One possible isolator is the 1761 NET AIC interface converter baud rate selector switch port 1 DB 9 RS 232 DTE port 2 mini DIN 8 RS
62. econd FlexLogix controller as the first However unlike the scanlists the user programs in the controllers do not have to be identical 14 Put the controller into RUN mode This controller is now ready to go and is the primary controller 15 Reapply power to the secondary controller and or reconnect the secondary scanner to the DeviceNet subnet This completes the back up process For more detailed information on some of the steps listed previously see the next section Publication 1794 UM001G EN P January 2007 108 FlexLogix Back Up on DeviceNet Developing the FlexLogix Back Up Application Publication 1794 UM001G EN P January 2007 The FlexLogix back up is enabled from an RSLogix 5000 user program with a few simple ladder rungs or equivalent The following rungs are used in the FlexLogix back up e Back up Heartbeat Configuration Rungs required e Reading Back up State Rung optional e Reading Back up Status optional Back up Heartbeat Configuration Rungs The first and most critical step is to set the back up heartbeat constant in the DeviceNet scanner The heartbeat constant enables the back up feature and determines the switchover time 2 x heartbeat By default the heartbeat is zero this default value disables the back up mode Your user program must set the heartbeat to a non zero value to enable back up The heartbeat occurs in multiples of 8ms i e 8 16 24 etc We recommend a value of
63. erhead RE eens Time Slice Controller My Praias I Controller Ta Controller Fa GD Power Up Ha Tasks Print 1 8 MainTask Ej amp MainProg Verify Publication 1794 UM001G EN P January 2007 Generate Report T Match Project to Controller ah oops Serial Number gt System overhead functions include e communicating with programming and HMI devices such as RSLogix 5000 software e responding to messages e sending messages e re establishing and monitoring I O connections such as RIUP conditions this does not include normal I O communications that occur during program execution e bridging communications from the serial port of the controller to other communication devices The controller performs system overhead functions for up to 1 ms at a time If the controller completes the overhead functions in less than 1 ms it resumes the continuous task As the system overhead percentage increases time allocated to executing the continuous task decreases If there are no communications for the controller to manage the controller uses the communications time to execute the continuous task While increasing Develop Applications 83 the system overhead percentage does increase communications performance it also increases the amount of time it takes to execute a continuous task increasing overall scan time The table below shows t
64. erial The RS 232 port is a non isolated serial port built in to the front of the FlexLogix controller You can configure the serial port of the controller for these modes See Use this mode For e Logix5000 Controllers Common DF1 communication between the controller and one other Procedures Manual 1756 PMO001 point to point DF1 protocol compatible device This is the default system mode Default parameters are e Baud Rate 19200 e Data Bits 8 e Parity None e Stop Bits 1 e Control Line No Handshake e RTS send Delay 0 e RTS Off Delay 0 This mode is typically used to program the controller through its serial port DF1 master mode control of polling and message transmission between the master and slave nodes The master slave network includes one controller configured as the master node and as many as 254 slave nodes Link slave nodes using modems or line drivers A master slave network can have node numbers from 0 to 254 Each node must have a unique node address Also at least 2 nodes must exist to define your link as a network 1 master and 1 slave station are the two nodes DF1 radio modem Compatible with SLC500 and MicroLogix1500 controllers e This mode supports master and slave and store and forward modes Publication 1794 UM001G EN P January 2007 32 Communicate over Networks Use this mode DF1 slave mode For using a controller as a slave station in a master slave serial com
65. ex Sequencer Output Request SOR general elay ladde RAD general relay ladder Square Root unction block Radians structured tex function block SORT general structured tex Square Root RES general relay ladder Reset SRT general elay ladde File Sort structured tex RESD process control structured tex Reset Dominant function block SRTP process control structured tex Split Range Time Proportional unction block RET general relay ladder Return structured tex SSUM process control structured tex function block Selected Summer unction block RLIM process control structured tex SSV general elay ladde Rate Limiter function block Set System Value structured tex RMPS process control structured tex STD general elay ladde Ramp Soak function block File Standard Deviation RTO genera relay ladder STOD general elay ladde Retentive Timer On String To DINT structured tex RTOR genera structured tex STOR general elay ladde Retentive Timer On with Reset function block String To REAL structured tex RTOS genera relay ladder SUB general elay ladde REAL to String structured tex Subtract structured tex unction block SBR genera relay ladder Subroutine structured tex SWPB general elay ladde function block Swap Byte structured tex SCL process contro structured tex TAN general elay ladde Scale function block Tangent structured tex unction block SCRV process contro structured tex S Curve function block TND general elay ladde Temporary End SEL process contro function bloc
66. f the outputs are dependent on a state variable the lack of synchronization can also cause a bumpy switchover e As with all back up and redundancy systems the I O must change at a slower rate than the switchover time If the inputs change faster than the switchover the change of state is lost e Either the user program or user action determine the primary controller In its simplest mode the first scanner to power up or become available on DeviceNet first is the primary e Unlike some back up systems i e PLC5 the primary controller still maintain control of the I O and switchover does NOT occur if the primary controller is set to Program Idle mode The secondary 1788 DNBO scanner also indicates that it is in Idle Mode e By default a switchover will NOT occur if the default fault routine or user fault routine is executed in the primary controller However the user fault routine can force a switchover if so desired e If an operator interface is on DeviceNet then it can work without knowledge which controller is primary or secondary e Online edits are not automatically performed on both Primary and Secondary since no synchronization exists between Primary and Secondary Once an online edit occurs on the Primary then the Primary and Secondary will have different programs e FlexLogix Back up on DeviceNet is not Hot Back up Hot Back up implies complete synchronization of program program variables and I O Also I O switcho
67. f the tags is based on the location of the I O module in the system An I O address follows this format Location Slot Type Member SubMember o IBILE Optional Where Is Location Network location LOCAL same chassis or DIN rail as the controller ADAP TER_NAME identifies remote communication adapter or bridge module Slot Slot number of I O module in its chassis or DIN rail Type Type of data input 0 output C configuration S status Member Specific data from the I O module depends on what type of data the module can store e For a digital module a Data member usually stores the input or output bit values e For an analog module a Channel member CH usually stores the data for a channel SubMember Specific data related to a Member Bit Specific point on a digital 1 0 module depends on the size of the I O module 0 31 for a 32 point module Publication 1794 UM001G EN P January 2007 Determine When Data Is Updated Place Configure and Monitor I O 63 FlexLogix controllers update date asynchronous with the execution of logic Use the following flowchart to determine when a producer controller input module or bridge module will send data input or output data output pe analog or digital digital input analog ana
68. g each consumer consumed tag Publication 1794 UM001G EN P January 2007 Manage Controller Communications 51 Remote Connection Type Device Connections Total Quantity per Device Connections message depending on type 1 block transfer message 1 total Publication 1794 UM001G EN P January 2007 52 Manage Controller Communications Connections Example In this example system the FlexLogix controller e controls local in the same chassis digital I O modules e controls remote I O devices on DeviceNet e sends and receives messages to from a ControlLogix controller on EtherNet IP e produces one tag that the the CompactLogix controller consumes e is programmed via RSLogix 5000 programming software 1769 ADN adapter with Compact 1 0 modules Redistation Series 9000 fig fa photoeye g a T T rE is DeviceNet network a la a ee e 9 4 fo 3 gt FlexLogix with 1788 DNBO and 5 AA co ControlLogix controller 1788 ENBT cards installed i A a E with 1756 ENBT ote eC ae q module Ether
69. gix controller with 1788 ENBT card ControlLogix controller with 1756 ENBT module 1756 ENBT as an adapter with 1756 module I O modules CompactLogix controller MESE with integrated JE EtherNet IP port ie ea i 1 94 AENT adapter with 1794 1 0 modules 1734 AENT adapter with 1734 1 0 modules PowerFlex 700S AC drive with DriveLogix workstation Publication 1794 UM001G EN P January 2007 24 Communicate over Networks For more information Publication 1794 UM001G EN P January 2007 Connections over EtherNet IP You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system Connections are allocations of resources that provide more reliable communications between devices than unconnected messages All EtherNet IP connections are unscheduled An unscheduled connection is a message transfer between controllers that is triggered by the requested packet interval RPI or the program such as a MSG instruction Unscheduled messaging lets you send and receive data when needed The 1788 ENBT card supports 32 CIP connections over an EtherNet IP network With these controllers the number of end node connections they effectively support is dependent on the RPI of the connection If the
70. grams You must specify schedule a program within a task before the controller can scan the program Defining routines A routine is a set of logic instructions in a single programming language such as ladder logic Routines provide the executable code for the project in a controller A routine is similar to a program file or subroutine in a PLC or SLC controller Each program has a main routine This is the first routine to execute when the controller triggers the associated task and calls the associated program Use logic such as the Jump to Subroutine JSR instruction to call other routines You can also specify an optional program fault routine The controller executes this routine if it encounters an instruction execution fault within any of the routines in the associated program Publication 1794 UM001G EN P January 2007 74 Develop Applications Contents Instruction Help Release Notes Online Books Vendor Sample Projects X Quick Tour Tutorial Tip of the Day BM About RSLogix 5000 Scroll down to here and select the appropriate set of sample projects For more information The Logix5000 Controllers Common Procedures Manual 1756 PM001 Publication 1794 UM001G EN P January 2007 Sample controller projects RSLogix 5000 Enterprise programming software includes sample projects that you can copy and then modify to fit your application From RSlogix 5000 software select Help gt Vendor Sample Proje
71. he SLC product family This cable has a larger right angle connector than the 1756 CP3 cable 3 Connect the appropriate cable to the serial port on the controller PL al g BELAKI oO fg el 1761 cable H j isolator 1761 NET AIC user supplied modem cable Publication 1794 UM001G EN P January 2007 18 Directly Connect to the Controller via the Serial Port The FlexLogix controller is grounded through its DIN rail It is important that you understand the workstation s grounding system before connecting it to the controller An isolator is recommended between the controller and the workstation Configure the Serial Driver Use RSLinx software to configure the RS 232 DF1 Device driver for serial communications To configure the driver 1 From the Communications menu in RSLinx software select Configure Drivers Choose the RS 232 DF1 Device driver Qs RSLinx Professional Configure Drivers File Edit View Ken Do ne Station DDE OPC Security Available Driver Types wl a S RiS 232 DF1 devices Add New RS 232 DFI devices Configure Shortcuts ls ener ee aay Ethene river
72. he ratio between the continuous task and the system overhead functions At this time slice The continuous tasks And then overhead occurs runs for for up to 10 9 ms 1 ms 20 4 ms 1 ms 33 2 ms 1 ms 50 1 ms 1 ms At a time slice of 10 system overhead interrupts the continuous task every 9 ms of continuous task time as illustrated below Legend A Task executes Task is interrupted suspended periodic system overhead 1 ms 1 ms 9 ms 9 ms 0 5 elapsed time ms 10 15 20 25 The interruption of a periodic task increases the elapsed time clock time between the execution of system overhead as shown below 1 ms periodic task E 1 ms 1 ms 1 ms 1ms system overhead 1 ms 1 ms 9 ms of continuous task time elapsed time ms 9 ms of continuous task time cotnuoustesk M re ee ee 0 5 10 15 20 25 Publication 1794 UM001G EN P January 2007 84 Develop Applications If you use the default time slice of 20 the system overhead interrupts the continuous task every 4 ms of continuous task time 1ms 1 ms 1 ms 1 ms 1 ms system overhead E E E B pi 4 ms 4 ms 4 ms 4 ms 4 ms 5 10 15 20 25 elapsed time ms If you increase the time slice to 50 the system overhead interrupts the continuous task every 1 ms of continuous task time 1 ms system overhead E i ie E B E H w E E E E E 1 ms continuous task B B B B E B E E E
73. i E E E 5 10 15 20 25 elapsed time ms If the controller only contains a periodic task s the system overhead timeslice value has no effect System overhead runs whenever a periodic task is not running periodic task 5 10 15 20 25 continuous task elapsed time ms Publication 1794 UM001G EN P January 2007 Develop Applications 85 Use the Event Task The event task is available with FlexLogix controllers using firmware version 12 x or greater Previously the only tasks available were the continuous task and periodic task However the event task offers FlexLogix controller users a task that executes a section of logic immediately when an event occurs An event task performs a function only when a specific event trigger occurs Whenever the trigger for the event task occurs the event task e interrupts any lower priority tasks e executes one time e returns control to where the previous task left off For FlexLogix controller the event task trigger can only be the EVENT instruction or a consume tag Prioritizing Periodic and Event Tasks Although a FlexLogix project can contain up to 8 tasks the controller executes only one task at a time If a periodic or event task is triggered while another task is currently executing the priority of each task tells the controller what to do The FlexLogix controller has 15 priority levels for its tasks To assign a priority to a task use the guidel
74. ines described in the table If you want this task to interrupt another task Then Assign a priority number that is less than higher priority the priority number of the other task another task to interrupt this task Assign a priority number that is greater than lower priority the priority number of the other task Notes e A higher priority task interrupts all lower priority tasks e Ahigher priority task can interrupt a lower priority task multiple times this task to share controller time with another task Assign the same priority number to both tasks The controller switches back and forth between each task and executes each one for ims Publication 1794 UM001G EN P January 2007 86 Develop Applications Triggering the Event Task To trigger an event task based on conditions in your logic use the EVENT Instruction trigger fl Task Properties Task_1 General Configuration Program Schedule Monitor Let an event trigger this task Type Een o Let an EVENT instruction trigger the task Trigger EVENT Instruction Only No tag is required Tag knone gt 7 Tl Execute Task If No Event Occurs Within fi 000 000 ms Priority fi 4 Lower Number Yields Higher Priority The EVENT Instruction Only trigger requires that you use a Trigger Event Task EVENT instruction to trigger the task You can use an EVENT instruction from multiple p
75. information on how to e handle major faults e handle minor faults e determine controller memory use Publication 1794 UM001G EN P January 2007 80 Develop Applications Monitor Connections See e Logix5000 Controllers Common Procedures Manual 1756 PMO01 e Logix5000 Controllers Design Considerations Reference Manual Publication 1794 UM001G EN P January 2007 If communication with a device in the I O configuration of the controller does not occur for 100 ms or 4 times the RPI whichever is less the communication times out and the controller produces the following warnings e The I O LED on the front of the controller flashes green e A Z shows over the I O configuration folder and over the device s that has timed out e A module fault code is produced which you can access through Module Properties dialog box for the module GSV instruction Determine if communication has timed out with any device If communication times out with at least one device module in the I O configuration of the controller the I O LED on the front of the controller flashes green e The GSV instruction gets the status of the I O LED and stores it in the I_O_LED tag e If I O_LED equal 2 the controller has lost communication with at least one device GSV EQU Get System Value Equal CIP Object Class MODULE Source A _O_LED CIP Object Name Attribute Name LedStatus Source B 2 Dest _O_LED
76. ion Rockwell Automation provides technical information on the Web to assist you in using its products At http support rockwellautomation com you can Support find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit http support rockwellautomation com Installation Assistance If you experience a problem with a hardware module within the first 24 hours of installation please review the information that s contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running United States 1 440 646 3223 Monday Friday 8am 5pm EST Outside United Please contact your local Rockwell Automation representative for any States technical support issues New Product Satisfaction Return Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned United States Contact your distributor You must provide a Customer Support case numbe
77. ions 49 Connection Overview A Logix5000 system uses a connection to establish a communication link between two devices Connections can be e controller to local I O modules or local communication modules See e controller to remote I O or remote communication modules e Logix5000 Controllers Design e controller to remote I O rack optimized modules Considerations Reference Manual 1756 RM094 e produced and consumed tags e messages e controller access by RSLogix 5000 programming software e controller access by RSLinx software for HMI or other applications The limit of connections may ultimately reside in the communication module you use for the connection If a message path routes through a communication module the connection related to the message also counts towards the connection limit of that communication module This device Supports this many connections FlexLogix controller 100 1788 CNx communication card 32 1788 DNBO communication card 2 1788 ENBT communication card 32 Other controllers and communication modules support different maximum numbers of connections For more information The Logix5000 Controllers Design Considerations Reference Manual 1756 RM094 describes how to optimize connection use Publication 1794 UM001G EN P January 2007 50 Manage Controller Communications Calculate Connection Use To calculate the total number of local connections the controller uses
78. ions 79 The FlexLogix controller uses Get System Value GSV and Set System Value SSV instructions to get and set change controller data The controller stores system data in objects There is no status file as in the PLC 5 processor The GSV instruction retrieves the specified information and places it in the destination The SSV instruction sets the specified attribute with data from the source When you enter a GSV SSV instruction the programming software displays the valid object classes object names and attribute names for each instruction For the GSV instruction you can get values for all the available attributes For the SSV instruction the software displays only those attributes you are allowed to set In some cases there will be more than one instance of the same type of object so you might also have to specify the object name For example there can be several tasks in your application Each task has its own TASK object that you access by the task name You can access these object classes e AXIS e MODULE e CONTROLLER e MOTIONGROUP e CONTROLLERDEVICE e PROGRAM e CST e ROUTINE e DF1 e SERIALPORT e FAULTLOG e TASK e MESSAGE e WALLCLOCKTIME The Logix5000 Controllers General Instructions Reference Manual 1756 RM003 describes how to use the GSV and SSV instructions These instructions support several different attributes of information The Logix5000 Controllers Common Procedures Manual 1756 PM001 provides
79. ix Back Up on DeviceNet is a simple low cost back up system most effective when used in smaller applications that require fast switchovers from a primary to a secondary controller This back up solution will e minimize downtime in case of controller failure when the same program is used in both programs e mitigate the risk of changes adversely affecting the application use old proven program in one controller and new untested program in other controller If the new untested program causes a problem a forced switchover can be made to the older proven program without downloading the program again The FlexLogix Back Up on DeviceNet solution takes advantage of Shared DeviceNet Mastership of Slave I O Devices technology Typically only a single DeviceNet master exists for any particular slave With Shared DeviceNet Mastership two masters can exist Heartbeat communications between primary and secondary controllers determines which scanner is the master and which scanner remains in stand by mode Publication 1794 UM001G EN P January 2007 104 FlexLogix Back Up on DeviceNet How the Back up Works Figure shows an example back up system In the back up system the following occurs e Both controllers scanners simultaneously receive all inputs e Both controllers execute in parallel but are NOT synchronized e Only the primary controllers sends output data to the I O devices A virtual switch in the 1788 DNBO cards is used to s
80. k Select TOD general elay ladde Convert to BCD unction block SETD process contro structured text Set Dominant function block TOF general elay ladde Timer Off Delay SFP general relay ladder SFC Pause structured text TOFR general structured text Timer Off Delay with Reset unction block SFR general relay ladder SFC Reset structured text TON general elay ladde Timer On Delay Publication 1794 UM001G EN P January 2007 122 Instruction Locator Instruction Location Languages TONR general structured text Timer On Delay with Reset function block TOT process control structured text Totalizer function block TRN genera relay ladder Truncate function block TRUNC genera structured tex Truncate UID genera relay ladder User Interrupt Disable structured tex UIE genera relay ladder User Interrupt Enable structured tex X to the Power of Y Publication 1794 UM001G EN P January 2007 UPD process control structured tex Up Down Accumulator function block UPPER genera relay ladder Upper Case structured tex XIC genera relay ladder Examine If Closed XIO genera relay ladder Examine If Open XOR genera relay ladder Bitwise Exclusive OR structured text function block XPY genera relay ladder structured text function block A add on instructions 77 address data 62 AOI 77 architecture 11 ASCII characters 37 38 B back up FlexLogix back up o
81. king product without making scrap Held How do you tell if the equipment is safely holding Restarting How does the equipment resume production after holding Complete How do you tell when the equipment is done with what it had to do Stopping What happens during an normal shutdown Aborting How does the equipment shutdown if a fault or failure happens Aborted How do you tell if the equipment is safely shutdown How equipment changes states The arrows in the state model show to which states your equipment can go from the state it is in now e Each arrow is called a transition e A state model lets the equipment make only certain transitions This gives the equipment the same behavior as any other equipment that uses the same model transition Command Configure PhaseManager 93 PhaseManager uses the following transitions Done No command Use PSC instruction instead I Start Hold Your equipment can go from any state in the box to the stopping or aborting state Restart Restarting i Reset Type of transition Command Stop Abort Fault specific use of the abort Abon command Reset Stopped Aborted Description A command tells the equipment to start doing something or do something different For example the operator pushes the start button to start production and the stop button to shutdown PhaseManager uses these c
82. log or digital digital remote or local analog COS for any point on the N remote 0 No module p eg RTS lt RPI Yes local Yes Data is sent to the backplane Data is sent to the backplane at at the RTS the RTS and RPI y Data is sent to the backplane at the RPI and at the change of a specified point Data is sent to the backplane at the t RPI e Over a ControlNet network remote data is sent at the actual packet interval e Over an EtherNet IP network remote data is sent close to the RPI on average Data is sent to the backplane at the RPI and at the end of every task If you need to ensure that the 1 0 values being used during logic execution are from one moment in time such as at the beginning of a ladder program use the Synchronous Copy instruction CPS to buffer 1 0 data TIP For more information See Logix5000 Controllers Common Procedures Programming Manual publication number 1756 PM001 for examples of I O buffering or to the Logix5000 Controllers General Instruction Set Reference Manual publication number 1756 RM003 for information on the CPS instruction Publication 1794 UM001G EN P January 2007 64 Place Configure and Monitor 1 0 Monitor 1 0 Modules Publication 1794 UM001G EN P January 2007 The FlexLogix controller offers different levels at which you can monitor I O modules You can e configure an I O module so that the controller faults if that I O
83. munication network When there are multiple slave stations on the network link slave stations using modems or line drivers to the master When you have a single slave station on the network you do not need a modem to connect the slave station to the master You can configure the control parameters for no handshaking You can connect 2 to 255 nodes to a single link In DF1 slave mode a controller uses DF1 half duplex protocol One node is designated as the master and it controls who has access to the link All the other nodes are slave stations and must wait for permission from the master before transmitting User mode channel 0 only communicating with ASCII devices This requires your program to use ASCII instructions to read and write data from and to an ASCII device DH 485 Publication 1794 UM001G EN P January 2007 communicating with other DH 485 devices multi master token passing network allowing programming and peer to peer messaging Communicate over Networks 33 1 Determine whether you need an isolator For more information on determining if you need an isolator see page 15 2 Select the appropriate cable 3 Connect the appropriate cable to the serial port Communicate with DF1 devices You can configure the controller as a master or slave on a serial communication network Use serial to get information to and from remote controllers stations when e the system contains three or more stati
84. n hold stop etc You don t need to use all the states for your equipment Use only the states that you want There are 2 types of states Type of state Description Acting Does something or several things for a certain time or until certain conditions are met An acting state runs one time or repeatedly Waiting Shows that certain conditions are met and the equipment is waiting for the signal to go to the next state PhaseManager uses the following states Reset Start Hold Your equipment can go from any state in the box to the stopping or Hold Restart Stop Abort Acting states represent the Reset Abort things your equipment does at Complete Stopping Aborting a given time Stopped Aborted ES Waiting states represent the condition of your equipment when it is in between acting states Publication 1794 UM001G EN P January 2007 92 Configure PhaseManager Publication 1794 UM001G EN P January 2007 With a state model you define the behavior of your equipment and put it into a brief functional specification In this way you show what happens and when it happens For this State Ask Stopped What happens when you turn on power Resetting How does the equipment get ready to run Idle How do you tell that the equipment is ready to run Running What does the equipment do to make product Holding How does the equipment temporarily stop ma
85. n DeviceNet 103 116 battery catalog number 97 how to replace 99 life 98 storage 97 when to replace 98 BOOTP 22 C cables DH 485 link cable length 40 cache message 47 calculate connection use 50 change of state 56 command give 92 communication ControlNet 25 28 determine timeout with any device 80 determine timeout with 1 0 module 80 DeviceNet 28 30 DH 485 39 39 41 EtherNet IP 22 24 format 56 serial 31 38 configuration folder 55 configure ControlNet 1 0 module 60 DeviceNet 1 0 module 61 EtherNet IP I O module 59 1 0 module 55 61 serial driver 18 connect ControlNet 25 28 DeviceNet 28 30 Index DH 485 39 39 41 EtherNet IP 22 24 serial 15 20 31 38 third party network 42 connection calculate use 50 consume data 45 ControlNet 26 determine timeout with any device 80 determine timeout with 1 0 module 80 EtherNet IP 24 example 52 for more information 49 I O module 57 limits 24 27 49 message 47 48 monitor 80 82 monitor rack optmized 65 overview 45 produce data 45 summary 49 consume data connection use 45 for more information 46 overview 21 control distributed 1 0 overview 21 controller consume data 21 control distributed 1 0 21 design 12 fault handler 81 install 13 message 21 monitor status 79 path 20 produce data 21 serial connection 15 20 status 79 ControlNet connection use 26 distributed 1 0 60 example configuration 26 for more information 28 module capability 25 overview 25 28 scheduled 2
86. nother 1756 BA1 battery C If the BATTERY LED remains on after you complete Step B contact your Rockwell Automation representative or local distributor 7 Dispose the old battery according to state and local regulations ATTENTION Do not incinerate or dispose lithium batteries in general trash collection They may explode or rupture violently Follow state and local regulations for disposal of these materials You are legally responsible for hazards created while your battery is being disposed a Publication 1794 UM001G EN P January 2007 Appendix A Controller LEDs If this indicator is in this condition FlexLogix System Status Indicators The table below describes the controller LEDs present on all FlexLogix controllers It means RUN off The controller is in Program or Test mode steady green The controller is in Run mode FORCE off No tags contain 1 0 force values 1 0 forces are inactive disabled steady amber 1 0 forces are active enabled 1 0 force values may or may not exist flashing amber One or more input or output addresses have been forced to an On or Off state but the forces have not been enabled BAT off The battery supports memory steady red Either the battery is e not installed e 95 discharged and should be replaced 1 0 off Either e There are no devices in the 0 configuration of the controller e The controller does not contain a project contr
87. o send new configuration information to an I O module During the reconfiguration e Input modules continue to send input data to the controller e Output modules continue to controller their output devices A Module Reconfigure message requires the following configuration properties In this property Select Message Type Module Reconfigure To reconfigure an I O module 1 Set the required member of the configuration tag of the module to the new value 2 Send a Module Reconfigure message to the module EXAMPLE Reconfigure an I O module When reconfigure 5 is on the MOV instruction sets the high alarm to 60 for the local module in slot 4 The Module Reconfigure message then sends the new alarm value to the module The ONS instruction prevents the rung from sending multiple messages to the module while the reconfigure 5 is on reconfigure 5 reconfigure 6 MOV JE TONS Move Source 60 Dest Local4 C ChOConfig HAlarmLimit 75 0 MSG Type Module Reconfigure Message Control change_Halarm E t gt change_Halarm EN Publication 1794 UM001G EN P January 2007 68 Place Configure and Monitor 0 Notes Publication 1794 UM001G EN P January 2007 Chapter 6 Use This Chapter Manage Tasks See e Logix5000 Controllers Common Procedures Manual 1756 PMO01 e Logix5000 Controllers Design Considerations Reference Manual Develop Applications
88. odule_Fault_Into 0 Module_Connection_Error QU Module_Connection_Error Equal Source A Module_Status_Easy 0 Source B 4 Interrupt the execution of logic and execute the fault handler 1 In the controller organizer right click the module and select Properties 2 Click the Connection tab 3 Select check the Major Fault If Connection Fails While in Run Mode check box Publication 1794 UM001G EN P January 2007 82 Develop Applications Select a System Overhead Percentage 4 Develop a routine for the Controller Fault Handler See the Logix5000 Controllers Common Procedures publication 1756 PMO001 The Controller Properties dialog lets you specify a percentage for system overhead This percentage specifies the percentage of controller time excluding the time for periodic tasks that is devoted to communication and background functions 1 View properties for the controller and select the Advanced tab RSLogix 5000 My_Project_3 1794 L34 File Edit View Search Logic Communications Tc Controller Properties My_Project_3 o A ol x General Serial Port System Protocol User Protocol Major Faults Minor Faults y alsa S elel oA Date Time Advanced SFC Execution File Nonvolatile Memory Memory Offline I F RUN No Forces gt e No Edits A rin Controller Fault Handler lt none gt Bge As a Power Up Handler Enone 7 Boe System Ov
89. oftware described in this manual Reproduction of the contents of this manual in whole or in part without written permission of Rockwell Automation Inc is prohibited Throughout this manual when necessary we use notes to make you aware of safety considerations Identifies information about practices or circumstances that can cause an explosion in a hazardous environment which may lead to personal injury or death property damage or economic loss IMPORTANT Identifies information that is critical for successful application and understanding of the product ATTENTION Identifies information about practices or circumstances that can lead to personal injury or death property damage or economic loss Attentions help you to identify a hazard avoid a hazard and recognize the consequences SHOCK HAZARD Labels may be on or inside the equipment for example a drive or motor to alert people that dangerous voltage may be present BURN HAZARD Labels may be on or inside the equipment for example a drive or motor to alert people that surfaces may be dangerous temperatures gt rind Allen Bradley FlexLogix Logix5000 RSLogix RSLogix 5000 Rockwell Automation RSNetWorx and RSLinx are trademarks of Rockwell Automation Inc Trademarks not belonging to Rockwell Automation are property of their respective companies Summary of Changes Developing FlexLogix Controller Systems Where to Start Directl
90. og box display the following message Auto Configuration Successful If Then Yes Click OK No Go to step 4 and verify that you selected the correct Comm Port Then click Close Publication 1794 UM001G EN P January 2007 20 Directly Connect to the Controller via the Serial Port Select the Controller Path Publication 1794 UM001G EN P January 2007 In RSLogix 5000 software select the controller path on the network 1 Open an RSLogix 5000 project for the controller 2 From the Communications menu select Who Active 3 Expand the communication driver to the level of the controller Ei Workstation USMAYVASCOIO1 ea Linx Gateways Ethernet AB_DF1 1 DF1 Upload Exgetv 901 FlexLogix L34 Processor 1794 L34 B R15 03 18 2s AB_ETHIP 1 Ethernet Download i Se AB_PCIC 1 ContralNet y i Update Firmware k Close al ees E 4 ry Rates SAB DRL Npo cr ea Set Project Path Path in Project lt none gt Bt ft ft Nie ae Pe i Iran Iain irate eee aaa iia innate ty inner lynne AENEAN Aon 4 Select the controller To Choose monitor the project in the controller Go Online transfer a copy of the project from the controller to Upload RSLogix 5000 software transfer the open project to the controller Download You may have to confirm the action Chapter 3 Use This Chapter Supported networks for Control distributed
91. oints in your project Each time the instruction executes it triggers the specified event task EVENT instruction in program A l EVENT instruction in program B l event task a S E Description O Program A executes an EVENT instruction The event task that is specified by the EVENT instruction executes one time Program B executes an EVENT instruction The event task that is specified by the EVENT instruction executes one time Publication 1794 UM001G EN P January 2007 Develop Applications 87 Programmatically Determine if an EVENT Instruction Triggered a Task To determine if an EVENT instruction triggered an event task use a Get System Value GSV instruction to monitor the Status attribute of the task Status Attribute of the TASK Object Attribute Data Type Instruction Description Status DINT GSV Provides status information about the task Once the controller sets a bit you must manually clear the bit to determine if another fault of that type occurred SSV To determine if Examine this bit only A timeout triggered the task event task only 1 An overlap occurred for this task 2 The controller does not clear the bits of the Status attribute once they are set e To use a bit for new status information you must manually clear the bit e Use a Set System Value SSV instruction to set the attribute to a different value Checklist for an EVENT Instruction Task For this
92. oller memory is empty steady green The controller is communicating with all the devices in its 1 0 configuration flashing green One or more devices in the 1 0 configuration of the controller are not responding flashing red The controller is not communicating to any devices The controller is faulted OK off No power is applied flashing red One of the following e The controller requires a firmware update e A major recoverable fault occurred on the controller To clear the fault 1 Turn the controller keyswitch from PROG to RUN to PROG 2 Go online with RSLogix 5000 steady red The controller detected a non recoverable major fault so it cleared the project from memory To recover 1 Cycle power to the chassis 2 Download the project 3 Change to Run mode If the OK LED remains steady red contact your Rockwell Automation representative or local distributor steady green Controller is OK Publication 1794 UM001G EN P January 2007 102 FlexLogix System Status Indicators Notes Publication 1794 UM001G EN P January 2007 Appendix B FlexLogix Back Up on DeviceNet Using This Appendix For information about See page How the Back up Works 104 Power Up and System Start up 106 Developing the FlexLogix Back Up Application 108 Using Indicators to Check Status 115 Development and Debugging Tips 115 This chapter offers a solution to back up your FlexLogix controller on DeviceNet FlexLog
93. ommands reset stop restart start hold abort Done Equipment goes to a waiting state when it s done with what it s doing You don t give the equipment a command Instead you set up your code to signal when the equipment is done The waiting state shows that the equipment is done Fault A fault tells you that something out of the ordinary has happened You set up your code to look for faults and take action if it finds any Suppose you want your equipment to shut down as fast as possible if a certain fault happens In that case set up your code look for that fault and give the abort command if it finds it Publication 1794 UM001G EN P January 2007 94 Configure PhaseManager State that the equipment phase is in right now Equipment Phases e EEG Complete Auto P ause Pause Compare PhaseManager to Other State Models S88 Idle iner s RSLogis 5000 1 Che Sil E Restarting Sto Abort Manually change states RSLogix 5000 software has a window that lets you monitor and command an equipment phase To manually change states Take ownership of the equipment phase ane 9 Hee Give a command Stopping Stopped This table compares PhaseManager s state model to other common state models PackML Starting Ready PhaseManager Resetting Idle Running Complete Producing Running Complete Pausing Paused Standby subroutines breakpoints or both Holding
94. on ControlNet Software Use Required optional Use this to configure the Required FlexLogix project and define ControlNet communications RSLogix 5000 programming software RSLinx Use this software to Required configure the ControlNet communication driver RSNetWorx for ControlNet Use this software to Required configure the ControlNet network define the NUT Network update time and schedule the ControlNet network The ControlNet communications modules e support messaging produced consumed tags and distributed I O e share a common application layer with DeviceNet and EtherNet IP e require no routing tables e support the use of coax and fiber repeaters for isolation and increased distance Publication 1794 UM001G EN P January 2007 26 Communicate over Networks In this example e The controllers can produce and consume tags among each other e The controllers can initiate MSG instructions that send receive data or configure devices e The personal computer can upload download projects to the controllers e The personal computer can configure devices on ControlNet and it can configure the network itself personal computer workstation Compa
95. onfigure the Required User Manual ENET UM527 software FlexLogix project and define e EtherNet IP Performance EtherNet IP Application Guide ENET AP001 communications e Logix5000 Controllers Design BOOTP DHCP Utility This utility comes with Optional Considerations Reference Manual RSLogix 5000 software Use 1756 RM094 this utility to assign IP e EtherNet IP Daughtercard addresses to devices on an Installation Instructions EtherNet IP network 1788 IN054 7 RSNetWorx for EtherNet IP Use this software to Optional configure EtherNet IP devices by IP addresses and or host names Publication 1794 UM001G EN P January 2007 Communicate over Networks 23 The EtherNet IP communication modules e support messaging produced consumed tags HMI and distributed I O e encapsulate messages within standard TCP UDP IP protocol e share a common application layer with ControlNet and DeviceNet e interface via RJ45 category 5 unshielded twisted pair cable support half full duplex 10 Mbps or 100 Mbps operation e support standard switches e require no network scheduling e require no routing tables In this example e The controllers can produce and consume tags among each other e The controllers can initiate MSG instructions that send receive data or configure devices e The personal computer can upload download projects to the controllers e The personal computer can configure devices on EtherNet IP FlexLo
96. ons e communications occur on a regular basis and require leased line radio or power line modems g EtherNet IP 9 3 Publication 1794 UM001G EN P January 2007 34 Communicate over Networks On this tab To configure the controller for DF1 communications Do this f Controller Properties PLSSampleProject s k 1 4 Select System Mode Date Time Advanced SFC Execution File Redundancy Nonvolatile Memory Memory General SerialPort System Protocol User Protocol Major Faults Minor Faults 2 Specify communication settings Mode System JE Baud Rate 19200 Data Bits al Parity None v Stop Bits 1 Control Line No Handshake zi RTS Send Delay 0 420 ms RTS Of Delay O 420 ms DCD Wait Delay 41 sec cae LE f Controller Properties PLSSampleProject olf 1 Select DF1 protocol Date Time Advanced SFC Execution l Fie Redundancy Nonvolatile Memory Memory General SerialPort System Protocol User Protocol Major Faults Minor Faults 2 S p eci fy D F1 settin g S Error Detection Protocol DF1 Point to Point fad pec C CRC Station Address 0 PT IV Enable Duplicate Detection NAK Receive Limit 3 ENQ Transmit Limit 3 ACK Timeout 50 x20 ms Embedded Responses
97. operations not sequenced ladder diagram LD boolean or bit based operations complex logical operations message and communication processing machine interlocking operations that service or maintenance personnel may have to interpret in order to troubleshoot the machine or process continuous process and drive control function block diagram FBD loop control calculations in circuit flow high level management of multiple operations sequential function chart SFC repetitive sequence of operations batch process motion control using structured text state machine operations complex mathematical operations structured text ST specialized array or table loop processing ASCII string handling or protocol processing Publication 1794 UM001G EN P January 2007 Develop Applications 77 Add On Instructions With version 16 of RSLogix 5000 programming software you can design and configure sets of commonly used instructions to increase project consistency Similar to the built in instructions contained in Logix5000 controllers these instructions you create are called Add On Instructions Add On Instructions reuse common control algorithms With them you can e ease maintenance by animating logic for a single instance e protect intellectual property with locking instructions e reduce documentation development time You can use Add On Instructions across multiple projects Yo
98. or remote devices To optimize the number of available connections place remote digital I O in the same location and use a rack optimized connection to the remote adapter that connects the remote I O to the FlexLogix system If you have remote analog I O modules or want a direct connection to specific remote I O modules you do not have to create the rack optimized connection to the remote adapter To use direct connections to remote I O select none for the communication format of the remote communication device IMPORTANT It is vital that you manage your connections to remote devices because while the FlexLogix controller allows up to 100 total connections the communications cards that connect to remote devices are limited to far fewer connections i e 32 connections for Contro Net or EtherNet IP The Logix5000 Controllers Common Procedures Manual 1756 PM001 provides information on how to e configure I O e address I O data e buffer I O data The Logix5000 Controllers Design Guidelines Reference Manual 1756 RM094 provides guidelines on how to e buffer I O e specify an RPI rate e select a communication format e manage I O connections Place Configure and Monitor I O 59 Configure Distributed 1 0 To communicate with distributed I O modules over EtherNet IP you on EtherNet IP e install a 1788 ENBT communication card in your FlexLogix controller and add the card to the I O configuration folder e a
99. ot already own a phase relinquish ownership of a phase PDET override a command POVR For more information The PhaseManager User Manual LOGIX UMO001 provides information on how to design configure and program and phase manager application Publication 1794 UM001G EN P January 2007 96 Configure PhaseManager Notes Publication 1794 UM001G EN P January 2007 Chapter 8 Maintain the Battery Using this Appendix For information about See page Storing Replacement Batteries 97 Estimating Battery Life 98 Replacing a Battery 99 Storing Replacement Because a battery may leak potentially dangerous chemicals if stored Batteries improperly store batteries as follows Store batteries in a cool dry environment We recommend 25 C with 40 to 60 relative humidity You may store batteries for up to 30 days between 45 to 85 C such as during transportation To avoid possible leakage do not store batteries above 60 C for more than 30 days Publication 1794 UM001G EN P January 2007 98 Maintain the Battery Estimating Battery Life Publication 1794 UM001G EN P January 2007 When the battery is about 95 percent discharged the controller provides the following warnings e On the front of the controller the BATTERY LED turns on solid red e A minor fault occurs type 10 code 10 To prevent the battery from leaking potentially dangerous chemicals replace the battery at least as often as
100. ou must use RSNetWorx for ControlNet to enable all scheduled connections and establish a network update time NUT Scheduling a connection reserves network bandwidth to specifically handle the connection unscheduled An unscheduled connection is a message transfer between controllers that is triggered by ladder logic or the program such as a MSG instruction Unscheduled messaging lets you send and receive data when needed Unscheduled messages use the remainder of network bandwidth after scheduled connections are allocated The FlexLogix controller supports 100 connections However the controller is limited by the number of connections each ControlNet communication card supports The 1788 CNx cards support 32 total ControlNet connections 22 of which can be scheduled and used for producing and consuming tags With these controllers the number of end node connections they effectively support is dependent on the application s NUT and RPI If the NUT and RPI are each The controllers effectively support this many communication connections Sms BS 10 ms 6 20 ms 13 40 ms 22 In the table above with a NUT and RPI of 40 ms and greater the ControlNet card supports 22 communications connections In this case the remaining 10 connections can be used for unscheduled connections Publication 1794 UM001G EN P January 2007 28 Communicate over Networks For more information The ControlNet Modules in Logix5000 Control
101. our machinery e Logix5000 Controllers Common e document through tag names your application as you Procedures Manual 1756 PM001 develop it e Logix5000 Controllers Design Considerations Reference Manual Program Tags MainProgram Scope MainProgram x Show Show All ad Sort Tag Nar 7 Alias For Type Base Tag north_tank_mix BOOL north_tank_pressure REAL analog 1 0 device north_tank_temp REAL one_shots DINT recipe TANK 3 integer value jo recipe_number DINT storage bit p replace_bit BOOL counter p gt Fl running_hours COUNTER timer running_seconds O TIMER its start Bo0L digital 1 0 device stop BOOL Monitor Tags Edit Tags F 4 When you create a tag you assign the following properties to the tag e tag type e data type e scope For more information The Logix5000 Controllers Common Procedures Manual 1756 PM001 provides information on how to e define tags e create tags arrays and user defined structures e address tags e create aliases to tags e assign indirect addresses Publication 1794 UM001G EN P January 2007 76 Develop Applications Selecta Programming The FlexLogix controller supports these programming languages both Language online and offline If you are programming Use this language continuous or parallel execution of multiple
102. ower power load 1794 PS3 120 230V ac 85 265V ac 86W 205VA 250VA 3 0A 24V de horizontal mount 2 8A 24Vde non horizontal mount 1794 PS13 36W 53VA 90VA 1 3A 24V de Publication 1794 UM001G EN P January 2007 Place Configure and Monitor I O 55 The FlexLogix controller also supports distributed remote I O via these networks e EtherNet IP e ControlNet e DeviceNet Configure 1 0 To communicate with an I O module in your system you add the module to the I O Configuration folder of the controller See Controller My_Project Controller Tags e Logix5000 Controllers Common E Controller Fault Handler Procedures Manual 1756 PM001 Power Up Handler e Logix5000 Controllers Design E Tasks Considerations Reference Manual 38 MainTask 1756 RM094 amp MainProgram 3 Unscheduled Programs Phases amp Motion Groups 3 Ungrouped Axes Trends amp Data Types User Defined Eg Strings Ep Predefined i Module Defined amp 1 0 Configuration 13 Backplane FlexLogix System EE 1794 134 My_Project Add 1 0 modules gt g FlexBus Local to the FlexBus g FlexBus Local2 Local or Local2 Publication 1794 UM001G EN P January 2007 56 Place Configure and Monitor 0 Configuration Option requested packet interval RPI When you add a module you also define a specific configura
103. r see phone number above to obtain one to your distributor in order to complete the return process Outside United Please contact your local Rockwell Automation representative for States return procedure www rockwellautomation com Power Control and Information Solutions Headquarters Americas Rockwell Automation 1201 South Second Street Milwaukee WI 53204 2496 USA Tel 1 414 382 2000 Fax 1 414 382 4444 Europe Middle East Africa Rockwell Automation Vorstlaan Boulevard du Souverain 36 1170 Brussels Belgium Tel 32 2 663 0600 Fax 32 2 663 0640 Asia Pacific Rockwell Automation Level 14 Core F Cyberport 3 100 Cyberport Road Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Publication 1794 UM001G EN P January 2007 PN 953014 91 Supersedes Publication 1794 UM001F EN P May 2005 Copyright 2007 Rockwell Automation Inc All rights reserved Printed in the U S A
104. re entered from RSNetworx for DeviceNet or RSLogix5000 to enable Back up All configuration occurs in the user program Almost your entire application e g except for a few ladder rungs can be developed without knowledge that the application will have a back up controller and scanner Local I O still works when this solution is used but the Local I O is not backed up Switchover time depends on the user configurable heartbeat After two heartbeats are lost between primary and secondary the switchover occurs This time can be as little as 50ms with a heartbeat of 16ms Publication 1794 UM001G EN P January 2007 116 FlexLogix Back Up on DeviceNet Publication 1794 UM001G EN P January 2007 e The I O during switchover is NOT bumpless Since the programs and I O updates are not synchronized it is possible for the secondary controller to be either slightly faster or slower than the primary For example if output changes during a switchover the fact that the primary and secondary controllers are unsynchronized can cause the output to momentarily switch between an older and newer value If you configure the switchover time slower than the program scan and I O update the secondary lags behind the primary and eliminates this e State variables such as counters or timers are NOT synchronized The user program must synchronize the primary and secondary controllers typically over an EtherNet IP or ControlNet link between controllers I
105. rmine When Data Is Updated 004 63 Monitor I O Modules w 0 6 0s oa uah Pita ae arie hea n ee 64 Displaying fault data 0 64 040060068 a beeen wen 64 Monitor a rack optimized connection 65 Reconfigure an I O Module oonan a ers YOLEN eae Sree 66 Reconfigure a module via RSLogix 5000 software 66 Reconfigure a module via a MSG instruction 67 Chapter 6 Use This Chapter s aana ee en E ae ee AANE 69 Ma nage Tasks rrearen aad othe uy pig a AE e a ete 69 Develop Programs er eased o e oa E E E ES 70 Defining tasks eones e A e e HR Ke he O 71 Defining programs sa rens e p eg Mae AG 73 Defining FOUUNES sc 2645 Go ie Be oe Th Poe lhl oe 73 Sample controller projects 6 pcx sce Wl nah vw edge ose 74 Oroanize LAGS 4 rica ube ys eR UN Rae Pe ANd i 75 Select a Programming Language 000 76 Add On Instructions o oo aa aa sake ek eh Bo OS 77 Monitor Controller Status cock eka aaa aaa 79 M nitor Connections 64 04 32 84 kri CAROL Os POT ewha Gees 80 Determine if communication has timed out with any device 80 Determine if communication has timed out with a specific TNFa TNE gg eee feiss 4 65 ash e E E ra no A Bate een ge 80 Interrupt the execution of logic and execute the fault handler 81 Select a System Overhead Percentage 82 Use the Event TAS os 85 24 0 nh eee ROA ele cg Rt ne edd 85 Prioritizing Periodic and Event Tasks 85 Triggering th
106. s Third Party Publication 1794 UM001G EN P January 2007 The FlexLogix controller can operate on third party networks To operate on a third party network install the 1788 MODULE generic module communication card in the controller Use these software products when you use a FlexLogix controller on third party network Software Use Required optional RSLogix 5000 programming Use this to configure the Required software Version 12 or later 1788 MODULE card as part of the FlexLogix system Third party software Software that configures Required the 1788 MODULE card on the third party network Use RSLogix 5000 programming software to map the 1788 MODULE card as part of the FlexLogix system In the Controller Organizer add the card to the I O Configuration folder Communication Format The Communication Format field chooses a data type for information transmitted between the controller and a remote device connected to the 1788 MODULE communication card This format creates an array in the controller of whatever data type you choose for the input and output data Connection Parameters You must set connection parameters to define data identification and connection size An Assembly Instance and Data Size must be assigned for input output and configuration data Assembly Instance The Assembly Instance is a number that identifies what data transferred between the owner controller and I O module looks like You must
107. s of version 11 x or higher Additional requirements are as follows e When setting up the DeviceNet network you must set the primary and secondary 1788 DNBO cards to the same node address and reserve the next node address We recommend you set the primary and secondary 1788 DNBO node addresses to 0 and reserve node 1 However you can use any successive node numbers e g 30 and 31 e All I O and operator interfaces that required back up must be on DeviceNet e The scanlists in the two DeviceNet scanner must be identical Publication 1794 UM001G EN P January 2007 106 FlexLogix Back Up on DeviceNet Power Up and System Start up Publication 1794 UM001G EN P January 2007 To configure a FlexLogix Back up system on DeviceNet you can take the following steps Some of these steps are described in greater detail in the rest of the appendix 1 Install all I O and operator interfaces that you need to back up on DeviceNet We recommend that you reserve node addresses 0 and 1 for the two FlexLogix controllers used in the back up If you do not use 0 and 1 make sure you reserve two consecutive numbers for the controllers when you install I O and other devices on DeviceNet Connect a FlexLogix controller with a 1788 DNBO scanner to the DeviceNet network Set the controller node address to 0 or the lower of the 2 node addresses reserved for the FlexLogix controllers Power up the controller and the network
108. structured text Arc Cosine function block Arc Tangent ADD genera relay ladder ATN general elay ladde Add structured text Arc Tangent unction block function block AVE general elay ladde AFI genera relay ladder File Average Always False Instruction AWA general elay ladde AHL genera relay ladder ASCII Write Append structured tex ASCII Handshake Lines structured tex AW general elay ladde ALM process control structured tex ASCII Write structured tex Alarm function block BAND general structured tex ALMA general relay ladder Boolean AND unction block Analog Alarm structured tex function block BNOT general structured tex Boolean NOT unction block ALMD general relay ladder Digital Alarm structured tex BOR general structured tex function block Boolean OR unction block Publication 1794 UM001G EN P January 2007 118 Instruction Locator Instruction Location Languages Instruction Location Languages BRK genera relay ladder DFF process control structured tex Brea D Flip Flop unction block BSL genera relay ladder DIV general elay ladde Bit Shift Lef Divide structured tex unction block BSR genera relay ladder Bit Shift Right DTOS general elay lad
109. termines data structure of tags connections network usage ownership whether the module returns diagnostic information electronic keying Publication 1794 UM001G EN P January 2007 When you configure a module you specify the slot number for the module However it is possible to place a different module in that slot either on purpose or accidently Electronic keying lets you protect your system against the accidental placement of the wrong module ina slot The keying option you choose determines how closely any module in a slot must match the configuration for that slot before the controller opens a connection to the module There are different keying options depending on your application needs Connection direct Place Configure and Monitor I O 57 1 0 connections A Logix5000 system uses connections to transmit I O data A connection can be Description A direct connection is a real time data transfer link between the controller and an 1 0 module The controller maintains and monitors the connection between the controller and the 1 0 module Any break in the connection such as a module fault or the removal of a module while under power causes the controller to set fault status bits in the data area associated with the module Typically analog I O modules diagnostic I O modules and specialty modules require direct connections rack optimized For digital 1 0 modules you can select rack optimized
110. the insertion of daughtercards for up to 2 networks e g one for DeviceNet and one for EtherNet IP When designing a FlexLogix system determine the network configuration and the placement of components in each location Make these decisions as you design your system Design Step 01 Select I O devices 02 Select communication cards 03 Select controllers 04 Select power supplies O5 Select software Install Hardware See FlexLogix Controller Installation Where to Start 13 To install a FlexLogix controller follow these steps Installation Step O01 Install a DIN rail 02 Use DIN rail locks that came with your controller 03 Mount an appropriate power supply on the DIN rail 04 Install the battery in the controller See 8 Maintain the Battery 05 Install the communication cards in the controller See Chapter 3 Communicate over Networks o6 Install the controller on the DIN rail 07 Install the extended local adapter optional o8 Make serial connections See Chapter 2 Directly Connect to the Controller via the Serial Port 09 Load controller firmware Publication 1794 UM001G EN P January 2007 14 Where to Start Notes Publication 1794 UM001G EN P January 2007 Chapter 2 Directly Connect to the Controller via the Serial Port Use This Chapter This chapter describes how to connect to the controller via the serial port so you can configure th
111. tion 1756 UMO006 create and configure motion groups and axes configure a coordinated system time master device Publication 1794 UM001G EN P January 2007 10 Developing FlexLogix Controller Systems For this information configure and use EtherNet IP networks communicate over EtherNet IP The documents address network communications Use this publication EtherNet IP Communication Modules in Logix5000 Control Systems publication ENET UM001 configure and use ControlNet networks communicate over ControlNet ControlNet Communication Modules in Logix5000 Control Systems publication CNET UM001 configure and use DeviceNet network communicate over DeviceNet For this information use a state model for your controller configure equipment phase programs Publication 1794 UM001G EN P January 2007 DeviceNet Communication Modules in Logix5000 Control Systems publication CNET UM004 These documents address specific controller applications Use this publication Logix5000 Controllers PhaseManager User Manual publication LOGIX UM001 e To view or download manuals visit www rockwellautomation com literature e To obtain a hard copy of a manual contact your local Rockwell Automation distributor or sales representative Chapter 1 Use This Chapter 1794 1 0 modules connected to the FlexLogix controller EtherNet IP link ControlNet link DeviceNet Where to Start
112. tion Arm Output Cam structured tex MAPC motion relay ladde Motion Axis Position Cam structured tex MAR motion relay ladde Motion Arm Registration structured tex MAS motion relay ladde Motion Axis Stop structured tex MASD motion relay ladde Motion Axis Shutdown structured tex MASR motion relay ladde Motion Axis Shutdown Reset structured tex MATC motion relay ladde Motion Axis Time Cam structured tex MAVE process control structured tex Moving Average function block MAW motion relay ladde Motion Arm Watch structured tex MAXC process control structured tex Maximum Capture function block MCCD motion relay ladde Motion Coordinated Change structured tex Dynamics MCCM motion relay ladde Motion Coordinated Circular structured tex Move MCCP motion relay ladde Motion Calculate Cam Profile structured tex MCD motion relay ladde Motion Change Dynamics structured tex MCL motion relay ladde Motion Coordinated Linear structured tex Move MCR general relay ladde Master Control Reset MCS motion relay ladde Motion Coordinated Stop structured tex MCSD motion relay ladde Motion Coordinated Shutdown structured tex MCSR motion relay ladde Motion Coordinated Shutdown structured tex Reset MCT motion relay ladde Motion Coordinated Transform structured tex MCTP motion relay ladde Motion Calculate Transform structured tex Position Publication 1794 UM001G EN P January 2007 120 Instruction Locator
113. tion for the module While the configuration options vary from module to module there are some common options that you typically configure Description The RPI specifies the period at which data updates over a connection For example an input module sends data to a controller at the RPI that you assign to the module e Typically you configure an RPI in milliseconds ms The range is 0 2 ms 200 microseconds to 750 ms e f a ControlNet network connects the devices the RPI reserves a slot in the stream of data flowing across the ControlNet network The timing of this slot may not coincide with the exact value of the RPI but the control system guarantees that the data transfers at least as often as the RPI change of state COS Digital 1 0 modules use change of state COS to determine when to send data to the controller If a COS does not occur within the RPI timeframe the module multicasts data at the rate specified by the RPI Because the RPI and COS functions are asynchronous to the logic scan it is possible for an input to change state during program scan execution If this is a concern buffer input data so your logic has a stable copy of data during its scan Use the Synchronous Copy CPS instruction to copy the input data from your input tags to another structure and use the data from that structure communication format Many I O modules support different formats The communication format that you choose also de
114. u can define your instructions obtain them from somebody else or copy them from another project Once defined in a project Add On Instructions behave similarly to the built in instructions in Logix5000 controllers They appear on the instruction tool bar for easy access as do internal RSLogix 5000 software instructions Save Time With Add On Instructions you can combine your most commonly used logic into sets of reusable instructions You save time when you create instructions for your projects and then share them with others Add On Instructions increase project consistency since commonly used algorithms all work in the same manner regardless of who implements the project Use Standard Editors You create Add On Instructions by using one of three RSLogix 5000 software programming editors e Standard Ladder e Function Block Diagram e Structured Text Once you have created instructions you can use them in any RSLogix 5000 editor Export Add On Instructions You can export Add On Instructions to other projects as well as copy and paste them from one project to another Give each instruction a Publication 1794 UM001G EN P January 2007 78 Develop Applications For more information Publication 1794 UM001G EN P January 2007 unique name so that you don t accidentally overwrite another instruction of the same name Use Context Views Context views let you visualize an instruction s logic for a specific inst
115. ung You can read the back up state of the DeviceNet scanner with a single rung of ladder logic The back up state is useful for debug or more sophisticated back up schemes The message in this rung uses the SINT data type Figure shows the rung you can use to read the back up state OPTIONAL Constantly Read Backup State Disabled 1 Primary Scanner 2 Backup Scanner 3 Invalid Primary Node Address e g can t be 62 or 63 4 Faulted Backup Scanner CRC Failure e g Scan Lists don t match 5 Faulted Backup Scanner Backup Node Number Failure e g Backup not Primary 1 6 Backup Scanner Pending Primary Detection 254 Attempting Primary Access 255 Attempting Backup Access Source Backup_State 2 Dest DUMMY 2 Message Configuration Read_Backup_State Message Configuration Read_Heartbeat Get Attribute Single ha eH so i Sauce Link z a ictal E o M Cache Connections Publication 1794 UM001G EN P January 2007 FlexLogix Back Up on DeviceNet 113 Table describes the possible values this message may return when reading the back up state of the DeviceNet scanner If the message reads this value the back up state of the DeviceNet scanner is 0 Disabled 1 Primary scanner 2 Back up scanner 3 Invalid primary node address e g the node address cannot be 62 or 63 4 Faulted back up scanner CRC failure e g the scanlists in the scanners do
116. ut your code in sections that are easier to write find follow and change Term Description equipment phase An equipment phase is similar to a program e You run the equipment phase in a task e You give the equipment phase a set of routines and tags An equipment phase is different from a program in these ways e The equipment phase runs by a state model e You use an equipment phase to do 1 activity of your equipment state model A state model divides the operating cycle of your equipment into a series of states Each state is an instant in the operation of the equipment It s the actions or conditions of the equipment at a given time The state model of an equipment phase is similar to the S88 and PackML state models state machine An equipment phase includes an embedded state machine that e calls the main routine state routine for an acting state e manages the transitions between states with minimal coding You code the transition conditions When the conditions are true the equipment phase transitions the equipment to the next required state e makes sure that the equipment goes from state to state along an allowable path PHASE tag When you add an equipment phase RSLogix 5000 software makes a tag for the equipment phase The tag uses the PHASE data type Publication 1794 UM001G EN P January 2007 90 Configure PhaseManager E3 Controller A Controller Tags E3 Tasks ra MainTask E Add Water Ph
117. uted via DeviceNet 61 distributed via EtherNet IP 59 electronic keying 56 for more information 58 local and extended local DIN rails 54 module capability 53 monitor 53 64 65 monitor connection 80 place 53 rack optimized 57 reconfigure module 66 67 RPI 56 select 1794 FLEX 1 0 53 select a 1794 FLEX power supply 54 1 0 module fault data 64 install hardware 13 instruction locator 117 isolator connected to the serial port 15 17 L ladder diagram 76 language 6 locator 117 Logix5000 controller environment 11 low battery 98 message cache 47 connection use 47 48 for more information 48 overview 21 reconfigure I O module 67 Modbus support 38 monitor rack optimized connection 65 network overview 21 P phase See equipment phase priority 71 produce data connection use 45 for more information 46 overview 21 program defining 73 programming language 6 project program 73 routine 73 task 71 rack optimized connection 5 reconfigure 1 0 module 66 67 related documentation 9 10 relay ladder 76 replace the battery Index 125 how 99 when 98 requested packet interval 56 routine defining 73 RPI 56 RS 232 DF1 Device driver 18 RSLinx 25 RSLogix 5000 22 25 29 controller path 20 serial driver 18 19 RSNetWorx for ControlNet 25 RSNetWorx for DeviceNet 29 RSNetWorx for EtherNet IP 22 S scheduled 27 sequential function chart 76 serial cable 33 communicate with ASCII device ASCII device 35
118. ver is completely bumpless is Hot Back up Appendix C Where to Find an Instruction Locator This locator table lists the available instructions which publications describe the instructions and which programming languages are Instruction available for the instructions If the locator lists The instruction is documented in general Logix5000 Controllers General Instructions Set Reference Manual 1756 RM003 process control Logix5000 Controllers Process Control and Drives Instructions Set Reference Manual 1756 RMO006 motion Logix5000 Controllers Motion Instructions Set Reference Manual 1756 RMO007 phase PhaseManager User Manual LOGIX UM001 Instruction Location Languages Instruction Location Languages ABL genera relay ladder AND general relay ladde ASCII Test For Buffer Line structured tex Bitwise AND structured tex function block ABS genera relay ladder Absolute Value structured tex ARD general relay ladde function block ASCII Read structured tex ACB genera relay ladder ARL general relay ladde ASCII Chars in Buffer structured tex ASCII Read Line structured tex ACL genera relay ladder ASIN general structured tex ASCII Clear Buffer structured tex Arc Sine ACOS genera structured tex ASN general relay ladde Arc Cosine Arc Sine function block ACS genera relay ladder ATAN general
119. verify Heartbeat Configuration by reading back from scanner to make sure configuration was accepted Get_Attrib_Single to Class 0x90 Instance 0x01 Attrib 0x12 DeviceNet 0 CommandRegister Run Set_Heartbeat DN sas 3 J JE Type CIP Generic Message Control Read_Heartbeat_Verify p If scanner successfully configured or scanner already in RUN mode then set scanner to RUN mode NOTE Since scanner resets after being configured there may be a delay END OF BACKUP INITIALIZATION DeviceNet 0 CommandRegiste Run Read_Heartbeat DN QU DeviceNet 0 CommandRegister Run 4 3 Equal Source Current_Heartbeat Oe Source B Config_Heartbeat 16 DeviceNet 0 CommandRegister Run Rung 3 message configuration and communication tabs Message Configuration Read_Heartbeat_Verify Message Configuration Read_Heartbeat Get Attribute Single ha reni Heatbeat Z aaa Gores line A Best F cta fi fiz This completes the required portion of ladder logic to enable the FlexLogix back up on DeviceNet The following sections describe how to use additional ladder logic to read back up state and status However these sections are not required to complete the back up solution Publication 1794 UM001G EN P January 2007 112 Read_Backup_State EN MSG 5 Type CIP Generic Message Control Read_Backup_State M R FlexLogix Back Up on DeviceNet Reading Back up State R
120. witch outputs between primary and secondary controllers e After failure or forced switchover outputs are automatically switched by the 1788 DNBO card from the primary controller to secondary When the switch occurs the secondary controller becomes the primary controller The switchover occurs so quickly that the I O devices do not timeout these devices are unaware that redundant controllers scanners exist and are unaware of the switchover DeviceNet Primary controller DOO00000 Secondary controller All backed up devices must operate on DeviceNet f ODOULU000 ie Publication 1794 UM001G EN P January 2007 FlexLogix Back Up on DeviceNet 105 Requirements of the Back Up The FlexLogix Back Up on DeviceNet solution requires that you use the following e RSLogix 5000 version 10 or higher e 2 FlexLogix controllers firmware revision 10 x or higher e 2 1788 DNBO communication cards firmware revision 2 x or higher IMPORTANT Many applications use multiple communications cards ina FlexLogix controller to communicate with several networks This solution requires the software and FlexLogix controllers use version 10 x or higher However if you are using the 1788 ENBT card in your application remember that you must use software and FlexLogix controller
121. x5000 family of controllers For this information where to start for a new user of a Logix5000 controller Use this publication Logix5000 Controllers Quick Start program and test a simple project publication 1756 QS001 how to complete standard tasks Logix5000 Controllers Common Procedures publication 1756 PM001 program logic using sequential function charts SFC ladder diagram LD structured text ST and function block diagram FBD languages Important SFC and ST Programming Languages Programming Manual publication 1756 PM Procedures Manual 003 is an excerpt from the Logix5000 Controllers Common Logix5000 controller reference e LED patterns e controller features e instruction set quick reference Logix5000 C publication ontroller s System Reference 1756 QR107 program sequential applications Logix5000 Controllers General Instruction Set Reference Manual ladder diagram and structured text instructions publication 1756 RM003 program process control and drives applications Logix5000 Controllers Process Control Drives Instruction Set Reference Manual function block diagram instructions publication 1756 RM006 program motion applications Logix5000 Controllers Motion Instruction Set Reference Manual ladder diagram motion instructions publication 1756 RM007 configure and program motion interface modules Logix5000 Motion Module Configuration and Programming Manual publica
122. y Connect to the Controller via the Serial Port Communicate over Networks Manage Controller Communications Table of Contents Important User Information 4 cca Ox eee od ei eed ee OKs 2 TALOGIICHIONS ree a ira 5006 8 a whe oS bao hw Ra abo me 7 Updated Information aye hed NERA ROS EE EES Re 7 Preface TEMG HOR ea serei hae E Meee alk Bows Geylang a eee 9 Related Documentation saasaa AOE eR Alege Be 9 Chapter 1 LG jcFas Nav iow Gare 0 lt a mem cae eee rei ea e Oe cee 11 DES1OM seer cn hk teaa e PAGER Aad a a Bae hae amp BOs 12 Install Hardware o 4 6o54b adh bh eee 4 Ose LSA Oe 13 Chapter 2 Lise This Chapters o eh cor ete he ag VA ee Ree ae Soak oes ae 15 Connect the Controller via the Serial Port 15 Configure the Serial Driver 43 514 pnd Sepals amp es 18 Select the Controller Path a tis onono dw a Meds wth tei s ws 20 Chapter 3 Use This CHapter s s ein a a oes Dae Leah wa wie 21 ALOT NEE UR senate bare 0 goods a n G8 Se A Ea a DE ei 22 Connections over EtherNet IP 0 0004 24 SOMMONNGD e aedor Bir eto ee Riek eek Bee 2 yk Gee dake awoh 25 Connections over ControlNet 000000005 26 DeviceNet amp 6 tush botched 4 4 be Be OE eee bl a 4 28 Define Data Blocks io orea oi Suds wal gis ee oa e te 4 30 DOTA sch he weet A ats oh eh eRe RIOR ee aed ete 31 Communicate with DF1 devices 33 Communicate with ASCII devices 0 35 WOGIDUS SUP DON K

FlexLogix Controller System User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents