You are on page 1of 34

LAB 14 Introduction to Function Block Programming

WELCOME TO THE INTRODUCTION TO FUNCTION BLOCK PROGRAMMING HANDS ON LAB ________5 ABOUT THIS HANDS-ON LAB __________________________________________________5 LAB MATERIALS ___________________________________________________________5 DOCUMENT CONVENTIONS ____________________________________________________6 LAB 1: INTRODUCTION TO FUNCTION BLOCK PROGRAMMING IN RSLOGIX 5000 (45 MIN.)________7 REVIEWING IEC61131-3 PROGRAMMING LANGUAGES _______________________________7 LAUNCHING RSLOGIX 5000 AND CREATING A NEW PROJECT __________________________8 CREATING AND CONFIGURING A NEW PERIODIC TASK AND PROGRAM ___________________9 CREATING A FUNCTION BLOCK ROUTINE AND SCHEDULING IT TO RUN __________________10 EDITING THE FUNCTION BLOCK ROUTINE ________________________________________11 EDITING THE FUNCTION BLOCK LOOP SIMULATION ROUTINE _________________________15 AUTOTUNING THE PIDE LOOP ________________________________________________18 CREATING A TREND TO TRACK PROCESS VARIABLES _______________________________22 ON-LINE EDIT OF A FUNCTION BLOCK ROUTINE ___________________________________25 LAB 2: EXERCISING THE PIDE USING ACTIVE X FACEPLATES ____________________________29 CONFIGURING A TOPIC IN RSLINX _____________________________________________29 ADDING A PIDE FACEPLATE TO AN MS EXCEL SPREADSHEET ________________________31 CONFIGURING COMMUNICATIONS IN THE PIDE FACEPLATE __________________________33 EXERCISING THE PIDE FACEPLATE ____________________________________________34 LAB SUMMARY ___________________________________________________________34

L14 - Introduction to FunctionBlock Programming.doc Integrated Architecture On Tour 2008 Page 3 of 34

.

such as Function Block Diagrams. Who Should Complete This Lab This lab is intended for customers with minimal prior exposure to alternate programming languages. Lab Materials For this Hands-On lab. You will also learn that some applications can be programmed more quickly and easily if you use languages other than ladder logic.Introduction to FunctionBlock Programming.doc Integrated Architecture On Tour 2008 Page 5 of 34 . Hardware This hands-on lab requires one of the following Demo boxes: ControlLogix Demo Box CompactLogix demo box (either L43 or L35E) L14 . we have provided you with the following materials that will allow you to complete the labs in this workbook.Welcome to the Introduction to Function Block Programming Hands on Lab About This Hands-On Lab During this lab you will learn the basics of programming with Function Blocks.

Note: When you type the text in the field. Document Conventions Throughout this workbook. enclosed in single quotes (e. You will be creating your projects as you go. The text that follows this symbol may provide you with helpful hints that can make it easier for you to use this product. but not information that is required reading in order for you to complete the lab exercises. 'Controller1') Note: If the mouse button is not specified in the text. FYI The text that follows this symbol is supplemental information regarding the lab materials.g. remember that you do not need to type the quotes.. L14 .g. This style or symbol: Words shown in bold italics (e. Words shown in Courier text.Software The IBM-compatible PC in front of you has been loaded with: RSLogix 5000 RSLinx Classic Windows O/S Microsoft Excel Files There are no pre-configured lab files for this lab exercise..doc Integrated Architecture On Tour 2008 Page 6 of 34 .. This is information that you must supply based on your application (e.. Controller1). you should click on the left mouse button. a variable).g. An item that you must type in the specified field.g.Introduction to FunctionBlock Programming. or a menu name from which you must choose an option or command. we have used the following conventions to help guide you through the lab materials. This will be an actual name of an item that you see on your screen or in an example. simply type the words that are contained within them (e. RSLogix 5000 or OK) Indicates: Any item or button that you must click on.

IL supports a limited number of changes in program flow and is not considered a “high level language”. like other PLC manufacturers. One of the advantages of IL is that it is very easy to design PLC’s that can use this language. Instruction List (IL) The IEC developed the specification for the IL language after reviewing the low level languages (similar in structure to machine assembly language) used by a wide range of PLC manufacturers. it is possible to download Instruction List programs without an interim software compiler.) This lab demonstrates the use of the Function Block Diagramming. In appearance it resembles electrical schematic diagrams. Anyone that has used relay ladder logic to program PLC’s will know that the RLL functionality has multiplied exponentially and now includes at least 200 different instructions. you will learn how to create and edit a Function Block Diagram. In this lab.Introduction to FunctionBlock Programming. Function Block language is designed to control “parameter areas”. L14 . Rockwell Automation does not offer an Instruction List Editor for user programming. expands on the basic function blocks to provide functionality that can be easily configured for various application types. Reviewing IEC61131-3 Programming Languages IEC 61131-3 and Programming Languages The IEC 61131-3 standard includes specifications for 5 graphical programming languages. Each language has the ability to access data controlled by another routine using a different language.doc Integrated Architecture On Tour 2008 Page 7 of 34 . The IEC 61131-3 sets forth a standard set of function blocks. Relay Ladder Logic (RLL) First developed to replace hard wired relays and timers in the field. such as all the inputs/outputs required to control a PID loop. On the other hand.Lab 1: Introduction to Function Block Programming in RSLogix 5000 (45 Min. Function Block. Your application will determine which language Editor you will choose. An FB diagram is similar in appearance to P&ID diagrams used in instrumentation and control. a Function Block Diagram can directly access the accumulated value of a counter controlled by a Relay Ladder Logic routine. Function Block (FB) Function Blocks are the basic elements of a control system. Allen-Bradley relay ladder logic conforms to the IEC 61131-3 standard. While Relay Ladder Logic. Structured Text and Sequential function charts can all be converted to Instruction List. Rockwell Automation. Thus. which is based on the IEC 61131-3 specification and integrated into the RSLogix 5000 software. Often. a set of input and output parameters and an algorithm specific to the specific type of function block. Function Blocks consist of two parts.

choose the type of controller at your student station. Software Developers will find ST easy to learn. IEC 61131-3 Structured Text is particularly well suited for managing a wide variety of data types and behaviors. it can be utilized anywhere logical states repeatedly initiate similar sequences of events. This language bears a resemblance to a graphical system that was first used in computer system designs to describe the behavior of programs with multiple states. From the toolbar menu select File > New. to launch 3. When the New Controller screen appears. type 'Language_Example'. If you are unsure. double-click on the RSLogix5000 icon RSLogix5000 software. Important: You MUST know which demo box you are using before you proceed. Structured Text (ST) As a high level language.Sequential Function Chart (SFC) Unlike Function Block. While batch/recipe control may be the obvious application for this language. program and document. From the Revision pull-down menu. 2. specify 16. Sequences can have converging or diverging paths and can operate simultaneously with other sequences. SFC uses a series of steps and transitions to control the flow of a program. From the computer desktop. L14 . ask your instructor. The RSLogix5000 screen appears. similar in syntax to other structured text languages such as PASCAL. 1. The New Controller dialog appears. which is natively suited for continuous processes. In the Name field. the Sequential Function Chart language is based on current methods of describing a sequence of events. Launching RSLogix 5000 and Creating a New Project In this section of the lab you will launch RSLogix 5000 software and use it to create a new controller file. Configure slot number of controller.Introduction to FunctionBlock Programming. if applicable 4. configure the controller as follows: From the Type pull-down menu. Another strength of this language is the ability to program complex mathematical algorithms. Click OK to accept your changes and exit the New Controller dialog box.doc Integrated Architecture On Tour 2008 Page 8 of 34 .

From the Controller Organizer. and I/O Configuration folders as we’ll be referencing these later in the lab. right click on FB_Task and choose New Program. From the Controller Organizer. take a moment to locate the Controller. 3. L14 . right click on the Tasks folder and choose New Task. The New Program dialog appears. Creating and Configuring a New Periodic Task and Program In this section of the lab you will create a new periodic task and configure it.Introduction to FunctionBlock Programming. Tasks. 2. 1. Your Controller Organizer should now appear as follows: Notice that the Organizer is similar to a Windows-type hierarchy with folder structures.5.doc Integrated Architecture On Tour 2008 Page 9 of 34 . 6. Enter the parameters as shown below. then click OK to accept your changes. The New Task dialog appears. From the Controller Organizer.

It can be made up of any of the supported languages of the controller: ladder diagram.Introduction to FunctionBlock Programming. 1. From the Controller Organizer. sequential function chart. structured text. The New Routine dialog appears.4. then click OK to accept your changes. then click OK to accept your changes. 2. The Tasks folder in the Controller Organizer should appear as follows (note you may have to expand the FB_Task folder): Creating a Function Block Routine and Scheduling it to Run The routine is the basic container for your program. Many times the choice of language at this level is driven by the actual functionality of the specific routine and the suitability of one of the supported languages to accomplish the task due to the specific language feature set. Enter the parameters as shown below.doc Integrated Architecture On Tour 2008 Page 10 of 34 . Fill in the New Routine dialog as shown below. The Tasks folder in the Controller Organizer should now appear as follows: L14 . function block. 5. Note that the Type is a Function Block Diagram. right click on FB_Prog and choose New Routine. 3.

To schedule the routine. On the Process tab on the toolbar. Double-click on FB_Routine routine in the Controller Organizer. Editing the Function Block Routine 1. as shown below. Click on Apply. 2. Click on the Configuration tab and choose the FB_Routine routine from the Main pull-down menu.4. 5. 3. The Program Properties dialog appears. click on the PIDE function. L14 . 6.Introduction to FunctionBlock Programming. The first block to add to the diagram is the Enhanced PID Block (PIDE) to regulate the simulated loop. and then click on OK to exit the dialog box. A blank sheet (sheet 1) opens in the workspace. Name this sheet 'TIC101' in the namespace edit box.doc Integrated Architecture On Tour 2008 Page 11 of 34 . right click on FB_Prog and choose Properties.

Note that the first column tells whether the parameter is an input (I) or an output (O) to the block. Output Wire Connector 10. 9. the Parameters tab lists all parameters in the block. Note: If you are over a valid connection point. Click on the Properties button parameters. Move the Output Wire Connector (by dragging) to the output side of your PIDE block and connect it to your CVEU point by clicking once on the PIDE CVEU pin and once on the Output Wire Connector input pin. Click on OK to close the PIDE properties dialog. and press Enter to accept. the pin turns green. Input Wire Connector 7. Click on the Input Wire Connector from the toolbar. type ‘PID_PV’. Also in the parameters tab. Move the Input Wire Connector (by dragging) to the input (left) side of your PIDE block and connect it to the PV point with a wire by clicking once on the input reference output pin and once on the PIDE PV input pin.doc Integrated Architecture On Tour 2008 Page 12 of 34 . L14 . 8. for this block and take a minute to view all of the available Note they are organized into 7 tabs. 5. Note: You can click and drag the instructions to maneuver them around the sheet. 6.The PIDE block should now appear on the diagram. Click on the Output Wire Connector from the toolbar.Introduction to FunctionBlock Programming. you can use the checkbox in the second column to expose or hide parameter pins on the block diagram itself. Double-click on the wire connector reference to open a box for tag name entry. 4.

PV and choose Assume Data Available from the list that appears as shown: Setting this line as the “available first” data point will tell the sheet to assume that this path should be evaluated first. Right click on the wire leading from the PID_PV input wire connector to the PIDE_01. L14 .doc Integrated Architecture On Tour 2008 Page 13 of 34 . The simulation in the next section will create a loopback to the PIDE_PV parameter.Introduction to FunctionBlock Programming. 13. double-click on the ? to enter the Autotune tag name.11. At the bottom of the PIDE function block. 12. type ‘PID_CV'. Double-click on the wire connector reference. and press Enter to accept. The AutoTune feature needs a PIDE_AUTOTUNE tag associated with it in order to autotune the loop.

Save the Project. 16. Right click on the PIDTune tag reference and choose New “PIDTune” to create the AutoTune tag.Introduction to FunctionBlock Programming. then click OK to accept your changes. 15. L14 . Type ‘PIDTune’ in the field and press Enter to accept. Complete the New Tag dialog as follows.14. 17.doc Integrated Architecture On Tour 2008 Page 14 of 34 .

designated sheet 2 of 2. Next. Make this tag a Real Array type of program: FB_Prog scope with a dimension of 100. 4. and press Enter to accept. You should now be on a clean sheet. Name the sheet ‘Simulation’. you’ll create a storage array for this instruction’s use. Click OK on both dialogs to accept your changes. L14 . Double-click on the ? after StorageArray and type ‘Dead_Array’.Editing the Function Block Loop Simulation Routine 1. select and place a dead-time (DEDT) block onto sheet 2 (you may have to use the scroll arrows to find the DEDT instruction within the Process tab). 2. Right click on the tag reference and choose New “Dead_Array” to create the deadtime array tag. Click on the Add Sheet button to create a new sheet for the simulation elements. From the Process tab on the toolbar.doc Integrated Architecture On Tour 2008 Page 15 of 34 . This sheet will contain the simulation. 7. 5. 3. 6.Introduction to FunctionBlock Programming.

Introduction to FunctionBlock Programming. From the Process tab on the toolbar.4.8. 9. Open the DeadTime Properties Dialog (by clicking on the ellipsis). Connect DEDT_01.0 seconds and a Gain of 1. 13.doc Integrated Architecture On Tour 2008 Page 16 of 34 . select the Parameters tab and configure a Deadtime of 5. select and place a Lead-Lag (LDLG) block onto sheet 2. 10.Out to LDLG_01. Apply the change and click on OK. Apply the change and click on OK. 11. Open the LeadLag parameters by clicking on the ellipsis as shown below: and configure a 40 second lag 12.In as shown below: L14 .

Click on the Input Wire Connector object from the toolbar and connect it to the input of the DeadTime block. 16. choose PID_CV. Verify the routine by clicking the button in RSLogix 5000 software: 19. Input Wire Connector 15. select File > Save. Output Wire Connector 17. click on the arrow for a drop-down list of available connector references. You should have a diagram for sheet 2 similar to this: 18. Double-click on the wire connector reference.doc Integrated Architecture On Tour 2008 Page 17 of 34 . select Communications > Who Active and browse to your controller at your student station.14. Double-click on the wire connector reference. and press Enter to accept. 20. choose PID_PV.Introduction to FunctionBlock Programming. and press Enter to accept. Drop an Output Wire Connector onto the sheet and connect it to the output of the LeadLag. From the toolbar menu. L14 . From the toolbar menu. click on the arrow for a drop-down list of available connector references.

ellipses of the PIDE instruction and 2.Introduction to FunctionBlock Programming.doc Integrated Architecture On Tour 2008 Page 18 of 34 . Go back to sheet 1 and click on the properties button click on the Autotune tab. You should notice a green border around the workspace indicating that the code is being scanned by the controller. Autotuning the PIDE Loop 1. The tag should now be available for use with this PIDE and autotune. Download the program to the controller and go into Remote Run mode. Acquire the autotune resource (tag) by clicking the Acquire Tag button.21. L14 .

The amount (in percent) entered here will be added to the current CV amount for the duration of the autotune run.Introduction to FunctionBlock Programming. As such. This is important because it may influence the type of model (integrating / non-integrating. there must be a way to “Acquire” the resource for use and to “Release” the resource so that another PIDE can Acquire and use. then click Apply to accept your changes.FYI The Autotune tag that was entered at the bottom of the PIDE in RSLogix 5000 is a resource that can either be dedicated to a single PIDE or shared between many PIDE’s.doc Integrated Architecture On Tour 2008 Page 19 of 34 . The CV Step Size is the amount by which the autotune will change the PIDE CV to exercise the system. This section of the dialog deals with that resource acquisition and subsequent release. The Autotune will tune a “temperature” process by increasing the PIDE CV by 30 percent from its current value and will abort the autotune run if the process variable is going to rise above 100 before the autotune run is complete. 3. The status indicator displays the current status of the autotuning resource (tag). simply click the appropriate button. Configure the Autotune as shown below. etc) chosen for the autotune test. L14 . In a shared resource situation. FYI The Process Type specifies what type of system is to be tuned. a single PIDE can use the Autotune tag at a time for an individual tuning. To acquire or release the resource. The PV Change Limit is an absolute limit (in the engineering units) for the referenced PIDE configuration to stop (abort) the autotune procedure if the system will violate that limit in the course of the autotune run.

Note that the Execution State is In Progress and the Abort button is active. L14 .Introduction to FunctionBlock Programming.doc Integrated Architecture On Tour 2008 Page 20 of 34 . This process will take a couple minutes.4. Click on the Start button to begin the Autotune process. Click on the Autotune button to display the PIDE Autotune start screen as shown below: 5.

Click on the Set Gains in PIDE button. the first thing you should verify is that the Execution State is Complete and your gains should appear as shown below: This section shows the recommended gains based upon the last successful autotune run as well as the current gains being used in the PIDE.doc Integrated Architecture On Tour 2008 Page 21 of 34 . 8. Load the Slow Response set of gains into the PIDE by selecting the radio button for Slow Response.Introduction to FunctionBlock Programming. L14 .6. Close the Autotune and Tune dialogs so that you are back to sheet 1 of the FBD. Notice the PID_PV value changing. When the autotune is finished. 7. Note that the Current gains in the PIDE have changed to reflect the Slow Response selection. 9.

doc Integrated Architecture On Tour 2008 Page 22 of 34 . select FB_Prog from the Scope pull-down menu and expand the PIDE_01 tag in the Available Tags window. L14 .Creating a Trend to Track Process Variables 1. When the New Trend window appears. Select the PIDE_01. right click on the Trends folder and select New Trend.SP elements. 5. 2. enter the trend name as shown below.CV and PIDE_01. then click Next. When the following screen appears.Introduction to FunctionBlock Programming. From the Controller Organizer. 4. 3.PV tag from the list and click the Add button. Repeat step 4 for the PIDE_01.

Introduction to FunctionBlock Programming.The configuration window should appear as follows: L14 .doc Integrated Architecture On Tour 2008 Page 23 of 34 .

L14 . 8. The trend chart will appear as shown below: 7. Click on the X-Axis tab and set the time span to 3 minutes. Click Finish to accept your changes.doc Integrated Architecture On Tour 2008 Page 24 of 34 . 9. Right click on the black area and choose Chart Properties.Introduction to FunctionBlock Programming.6. Click on the Y-axis tab.

10. Navigate to the routine FB_Routine so that sheet 1 is in the editor workspace. 1. Assemble the edited copy to replace the original. So two copies of the routine being edited are held in memory from the time that the edits are verified until the edits are either cancelled or assembled. Click once on the Start Pending Routine Edits button in the function block toolbar.Introduction to FunctionBlock Programming. Test the edited copy (swap the original and the edited version in the execution thread). The trend display has now been defined. then click OK to exit the trend properties window.doc Integrated Architecture On Tour 2008 Page 25 of 34 . Click on the Custom radio button and set the min and max values as shown below: 11. L14 . Click Apply to accept your changes. it will be used later in this lab. Optionally Untest to return execution to the original. In the Function Block editor the edit ‘zone’ is the entire routine upon which edits are being performed. Verify (Accept) the edits in the copy. 2. On-Line Edit of a Function Block Routine The on-line editing functionality is procedurally identical to that of ladder routines: Start edits on the selected routine (the original routine is running while edits are made on a copy) Make the desired edits on the copy.

This is because the program is not running the routine being edited. L14 . In order to view the original. Note that the border around the function block diagram is no longer green. click once on the Pending Edits View button.You should now be in the Pending Edits view.Introduction to FunctionBlock Programming. click once on the Original View button. It is still running the original. To return to the Pending Edits View.doc Integrated Architecture On Tour 2008 Page 26 of 34 .

doc Integrated Architecture On Tour 2008 Page 27 of 34 .Introduction to FunctionBlock Programming. 5. L14 . place an Input Reference (IREF) on the sheet to the left of the PIDE and wire it to the SPProg input. 4.3. Type RemoteSP into the IREF and create this tag as a REAL. Click once on the Accept Pending Routine Edits button to verify and accept the edits. From the instruction toolbar.

the view has changed to the Test ? view and the border around the sheet has changed to reflect the fact that it can be activated by testing.doc Integrated Architecture On Tour 2008 Page 28 of 34 . 6. click Yes. then review the steps in this section. Do not Cancel the edit or you will not be able to exercise the edits that you have made unless you redo this entire section. Click once on the Assemble Accepted Program Edits button to make the program edit into the working program and to leave edit mode. Also. Notice that edit symbols have been removed from the border around the edited sheet indicating that it is now the only copy in the program. and the Test and UnTest capability. * Note: If the Edit toolbar does not resemble this or errors were noted during verification. When prompted to Assemble Program Edits. Notice that the border around the edited sheet becomes green indicating that it is now the active copy. Click once on the Test Accepted Program Edits button to activate the new routine effectively swapping it with the currently active routine. 8. 7. L14 . click Yes to proceed.Introduction to FunctionBlock Programming. When prompted to Test Program Edits. At this time you can explore the Original and Test views.The Edit toolbar will now change available options to reflect that the routine has been verified and is ready to either be tested or cancelled. 9.

Faceplates are available for the following function blocks: Alarm. We will create an Enhanced PID faceplate in Excel. From the toolbar menu in RSLinx. Minimize your RSLogix 5000 project using the Restore Down button. but first we need to set up an OPC topic in RSLinx that the faceplates can use to communicate with the controller. L14 . Discrete 3 State Device. Discrete 2 State Device.Lab 2: Exercising the PIDE using Active X Faceplates RSLogix5000 provides seven Active X faceplates that can be used in FTView or any Active X container (such as MS Excel). and Enhanced PID. Ramp/Soak.Introduction to FunctionBlock Programming.doc Integrated Architecture On Tour 2008 Page 29 of 34 . 3. click on the RSLinx icon. Totalizer. Configuring a Topic in RSLinx 1. From computer desktop. 2. Enhanced Select. select DDE/OPC > Topic Configuration.

expand the AB_ETHIP_1 driver. L14 . ask your instructor. click on the Language_Example topic.Introduction to FunctionBlock Programming.4. When the following window appears. Note: If you are unsure about the controller. and select the controller at your student station.doc Integrated Architecture On Tour 2008 Page 30 of 34 .

go to View. Now we can start Excel and place a PIDE faceplate on a worksheet. From the computer desktop.5. Click Apply and then Done when finished. select Toolbars. You should have a blank worksheet on your screen. select the More Controls icon in the bottom of the toolbox. Adding a PIDE Faceplate to an MS Excel Spreadsheet 1. Since the faceplates are Active X controls. L14 .doc Integrated Architecture On Tour 2008 Page 31 of 34 . If the Control Toolbox is not visible. configure the topic as shown below: 6. 7. 2. 3. Minimize your RSLinx session. scroll down to select Logix 5000 PIDE Faceplate Control.Introduction to FunctionBlock Programming. Under the Data Collection tab. From the Control Toolbox on the spreadsheet. we must access the “Control Toolbox” in Excel to insert any Active X objects on our sheet. Your cursor should now turn to a crosshair. then select Control Toolbox. double-click on the Microsoft Office Excel 2003 icon. From the scroll list that appears.

doc Integrated Architecture On Tour 2008 Page 32 of 34 . L14 .4. Draw a box with your cursor on your sheet so you have the following: Next we need to link this faceplate to the PIDE instruction in the controller using the RSLinx topic we defined earlier.Introduction to FunctionBlock Programming.

click Apply to accept your changes. 2. Exit the design mode by selecting the triangular icon in the Control Toolbox. Under Online tags. 4. L14 . In Excel. then click OK.Configuring Communications in the PIDE Faceplate 1. expand Program:FB_Prog and select the PIDE_01 tag.doc Integrated Architecture On Tour 2008 Page 33 of 34 . 5. right click on the PIDE Faceplate and choose Logix 5000 PIDE Faceplate Control Object > Properties. Once you have verified that your configuration appears as follows. click on the ellipsis next to the tag entry. Click OK. This will launch the tag browser.Introduction to FunctionBlock Programming. 6. 3. Expand the + sign next to your topic (Language_Example) to browse the Online tags. When the following screen appears.

From the toolbar menu in both RSLogix 5000 and Microsoft Excel. With the PIDE in manual mode. 3. change the SP to 30 by either manually entering the value in the SP edit field or by using the vertical slider. Created a program called FB_Prog and scheduled it to execute as part of FB_Task. Change the SP to 0 and observe the trend. click the Run button in your trend and view the process changes as you exercise the PIDE.Exercising the PIDE Faceplate 1. select File > Exit and exit the your projects without saving your changes. 2. 5. 4. 6. Back in your RSLogix 5000 project. Lab Summary In this lab. you completed the following tasks: Launched RSLogix 5000 and created the project which you will use for the duration of this lab exercise Viewed the Controller Organizer in preparation for proceeding to the next section of the lab exercise Created a periodic task called FB_Task and configured it to execute every 100ms. Created a Function Block routine called FB_Routine Scheduled FB_Routine to execute as the Main Routine for program FB_Prog Created a FB Loop Simulation Autotuned a PIDE Created a trend to view process variable changes Exercised the PIDE using Active X Faceplates L14 .doc Integrated Architecture On Tour 2008 Page 34 of 34 . Observe the changes in the process variable (PV) on the faceplate and in RSLogix 5000. The PV should settle to 0.Introduction to FunctionBlock Programming. Go into automatic mode by clicking the Auto button.