Getting started with UniOP and CoDeSys integrated controller

Tech-noteGetting started with UniOP and CoDeSysintegrated controllerThis technical note explains the sequence of steps to create a very simple CoDeSys project togetherwith its companion Designer application. The installation procedure of the software and the UniOPtarget is not described in this document; please refer to TN200 and to the related documentationprovided by 3S Software.The technical note assume to use CoDeSys programming software V2.3 and Designer 6.04 or above.Contents1 Starting with CoDeSys V2.3..............................................................................................32 Preparing the Designer application...................................................................................73 Continuing the programming...........................................................................................124 Appendix 1 ......................................................................................................................15sn021-1 (Getting Started with UniOP and CoDeSys iPLC).doc - 20.03.2009Getting started with UniOP and CoDeSys integrated controller 1

Tech-note1 Starting with CoDeSys V2.31) Start the CoDeSys workbench from the start menu; by default, CoDeSys software opens thelast opened project.2) Select File / New to create a new project3) Depending on the SCM module, select the proper target configuration from the list ofavailable platforms; in case of an SCM03-C module, select "Exor/SITEK CoDeSys forSCM03…" as target4) In the "New POU" dialog box displayed after the previous confirmation, select the languageyou want to use for the PLC_PRG Program Organization Unit (POU). This program is themain module of your project that is calling all the other POUs of your application. Please,don't change the name of this POU.5) To complete the settings of your project, click on the "Resources" tab in the project treeopen then "Workspace" with a double clicksn021-1 (Getting Started with UniOP and CoDeSys iPLC).doc - 20.03.2009Getting started with UniOP and CoDeSys integrated controller 3

Tech-note6) In the "Options" dialog box, select first "Symbol Configuration", check the "Dump symbolentries" and finally, press the "Configure symbol file…" button:7) In the "Set object attributes" dialog box, the "Export variables of object" is grayed-out andneed to be unchecked and marked back again. This is the final result:IMPORTANT : Please, look at appendix 1 for new informationsn021-1 (Getting Started with UniOP and CoDeSys iPLC).doc - 20.03.2009Getting started with UniOP and CoDeSys integrated controller 4

Tech-note8) Double click now on the PLC Configuration item of the Resource tree:9) In the "PLC Configuration" dialog box, right click on the "SITEK SCM03…" and select infrom the "Append Sub element" the hardware configuration you need to use in your project,following pictures shows how to insert the uIM05 digital inputs.sn021-1 (Getting Started with UniOP and CoDeSys iPLC).doc - 20.03.2009Getting started with UniOP and CoDeSys integrated controller 5

Tech-note10) You are now ready to start writing the PLC program; the following picture shows a verysimple example using the Ladder diagram programming language:During this phase, the variables are declared automatically. Some of them are "local", othersare "Global". These variables will be exported to a file that we will use in our UniOPDesigner project importing them directly into it. The CoDeSys symbols used to name thevariables can be exported to a text file after the project has been compiled.11) Select menu "Project / Rebuild all" to compile the projectWhen building the application the CoDeSys software automatically creates a file withextension “.sym” stored in the same project folder; this file contains all the variables declaredin the project and can be used later in Designer to import them into the project.12) If there are no errors in the project, the Message window will appear as following:sn021-1 (Getting Started with UniOP and CoDeSys iPLC).doc - 20.03.2009Getting started with UniOP and CoDeSys integrated controller 6

Tech-note2 Preparing the Designer application1) Create a new project, select the folder and the name of the project2) Select the UniOP model from “Panel Setup” and open "Project / Configure Controller…"menu. In the "Configure Controller" window, select "Internal controller only" and click "Ok".In the next dialog box select CoDeSys and confirm3) Since CoDeSys PLC does not use fixed addresses, we will need to connect the project to a tagdictionary and import the symbol file we exported during CoDeSys "build project" phase.Select then "Tools / Tag Editor'" from DesignerStart now “Tag Editor” form the “Tools” menu and select "File / New"; create a new databasechoosing its name and its location.Right click the database icon in the tree and select "Import Tags"sn021-1 (Getting Started with UniOP and CoDeSys iPLC).doc - 20.03.2009Getting started with UniOP and CoDeSys integrated controller 7

Tech-note4) Designer will start now a quick wizard to import the CoDeSys symbol file; in the Step1 selecta name for the dictionary and in the list of controller drivers make sure you have selected“iPLC CoDeSys” corresponding to the file "D32Uplc196.dll"Click "Next"5) In the Step 2 use the reference button to locate the CoDeSys symbol file; the file isnormally store in the same folder where it was saved the PLC applicationClick "Next" and "Finish" to complete end the import processThe Tag Editor wizard ends showing the information about the number of imported tags asshown in the following example:(number of imported tags is of course project dependant)IMPORTANT : Please, look at appendix 1 for new informationsn021-1 (Getting Started with UniOP and CoDeSys iPLC).doc - 20.03.2009Getting started with UniOP and CoDeSys integrated controller 8

Tech-note6) The tag dictionary is now ready to be used in the Designer project to create the UniOPapplication:7) In Designer select now “Project / Configure Tag Dictionaries” enable the tag support andbrowse for the database file created in the previous steps:sn021-1 (Getting Started with UniOP and CoDeSys iPLC).doc - 20.03.2009Getting started with UniOP and CoDeSys integrated controller 9

Tech-note8) Create your project using the normal procedure. Variables for the project can be selected fromthe list of imported symbols:9) Let’s now consider the following example as final result of the Designer application:What are these two buttons "1" and "2"?These buttons are Generic Buttons programmed with the macro commands for portassignment.We will use the same cable and same PC/Printer UniOP port to program both devices (HMIand iPLC). The "PC port for UniOP" will assign the PC/Printer port to the UniOP forDesigner programming; note that the port is automatically assigned to the UniOP when thepanel is in Configuration Mode. The "PC port for SCM03C" will connect the PC/Printer portto the SCM module for CoDeSys programming.This is the macro definition for "PC port for UniOP" button…sn021-1 (Getting Started with UniOP and CoDeSys iPLC).doc - 20.03.2009Getting started with UniOP and CoDeSys integrated controller 10

Tech-noteAnd this is the macro definition for "PC port for SCM03C" button…The port assignment can be also done directly from the HMI in the System Menu:- enter the command menu (press for 2 seconds on the touch screen or 2 seconds on theENTER key on non touch screen HMI) and select "SYSTEM"- in the System menu scroll the cursor down until you reach the "PRINTER.....OFF-LINE" line- Use left and right arrows to change the settings:-- "SCMxx #0 APPLICATION" when you want to download the iPLC project withCoDeSys-- "OFF-LINE" when you want to download the UniOP project with Designer- Select then "EXIT" to go out of this system menu.10) Now, you are ready to download your projects (UniOP and CoDeSys) to your HMI- Use standard procedure to download your UniOP project to the HMI with designer.- When the panel is in operation Mode, use the "PC port for SCM03C" button to reserve thePC port for CoDeSys.- In CoDeSys software, select then "Online / Login" menu to connect with the SCM module- CoDeSys will now display a message according to the status of the SCM module; if themodule has already an application loaded on it the following message is displayed:- at the end of the download the PLC_PRG POU will be automatically displayed in monitormode on the CoDeSys programming software.11) By default the CoDeSys application is downloaded in the module RAM memory; to keep it atpower cycle you need to store the project in the internal SCM flash memory; create then the“Boot Project": the PLC application is stored in the flash memory and it will be automaticallystarted at each power cycle. The boot project can be created form "Online / Create bootsn021-1 (Getting Started with UniOP and CoDeSys iPLC).doc - 20.03.2009Getting started with UniOP and CoDeSys integrated controller 11

Tech-noteproject" while in On Line mode.3 Continuing the programmingEach time you modify the iPLC application, you need to recompile your project. Since CoDeSys usesdynamic variable allocation done at each project build, you cannot be sure that the previous internaladdresses used to store the variables are still valid after the last compilation of the project.This means that Tag Dictionary needs to be upgraded each time the iPLC project is re-compiled.1) Select the "Tools / Tag editor" in Designer to re-open the Tag Editor window2) Right click on the tag dictionary name and select "Import Tags"3) Confirm you want to overwrite the existing tag dictionary4) Click "Next" in the "Step 1" dialog box5) Use the reference button to locate the new version of the ".SYM" file generated byCoDeSys. You can verify the generation date if you select the "detail" display mode…Click "Next" when the right file is selected.sn021-1 (Getting Started with UniOP and CoDeSys iPLC).doc - 20.03.2009Getting started with UniOP and CoDeSys integrated controller 12

Tech-noteClick "Finish" in the next window to complete the processTag Editor reports finally the number of imported tags.Close the Tag Editor window and return to DesignerNote : with last versions of Designer and TagEditor, the process is shorter because you canselect at point 2) above the option "Re import tags from [.Sym file previously selected]"6) Select now the "Project / Tag Validation" menu to check the validity of the addresses used inyour UniOP project.- If Tag validation reports "All the tags match with the field address values", no additionalactions are required:- sometimes however, the Tag validation process could detect changes into addresses used tostore your variables and will display for example a report similar to the one in the followingpicture:sn021-1 (Getting Started with UniOP and CoDeSys iPLC).doc - 20.03.2009Getting started with UniOP and CoDeSys integrated controller 13

Tech-noteSelect the line(s) where a change is detected and right click to select "Update Field (withdatabase values)" to adapt your UniOP project accordingly to the new iPLC application.7) The Designer project needs then to be downloaded again to UniOP.sn021-1 (Getting Started with UniOP and CoDeSys iPLC).doc - 20.03.2009Getting started with UniOP and CoDeSys integrated controller 14

Tech-note4 Appendix 1In case you use UIMxx module defined in PLC configuration, the next message can be reported whileimporting into TagEd the .sym file generated by CoDeSys :This message means that two variables with same name are present in the sym file which causesdouble index definition in mdb file.In fact, I/O variables are defined twice in the project :- first definition in "PLC configuration"- second definition in "Global variable"If "export ALL variables" is selected as explained in section 1 point 7) above, the sym file willcontain the two definition which causes the trouble during import in TagEd !To avoid this, please follow the next steps :In the "Set object Attributes" dialog, unselect the "Export variable of object" checkbox. This is theview of the current situation :Click on "POUs" section to select only this one. Pressing the "Ctrl" key on your keyboard, select thenthe "Global Variables" to add this section in the current selection. Finally, select again the "Exportvariables of object" checkbox.sn021-1 (Getting Started with UniOP and CoDeSys iPLC).doc - 20.03.2009Getting started with UniOP and CoDeSys integrated controller 15

Tech-noteThis is the view of the final situation.Press "Ok" to close the dialog.By this way, the "PLC Configuration" section is not exported and the sym file will not contain anydouble variable definition.Import ou RE import this sym file with TagEditor using usual way.Pay attention that this process must be repeated each time you add a new POU in your project or thenew variables will not be exported in the sym file.sn021-1 (Getting Started with UniOP and CoDeSys iPLC).doc - 20.03.2009Getting started with UniOP and CoDeSys integrated controller 16