Home

Unity Pro

1. Introduction Conversion replaces the PL7 objects by their Unity Pro equivalent Tables of The following table describes any correspondence and differences between the memory and symbolized tables of PL7 and Unity Pro memory and constant objects constant objects PL7 Unity Pro Status Address Associated Address Associated symbol variable 1 Tables of memory sMWi L TABA L SMWi L TABA L Modified 2 and constant SMDi L TABB L SMDi L TABB_L objects SMi L TABC L SMi L TABC_L SMFi L TABD L SMFi L TABD_L SKWi L TABE L SMWi L TABE_L KDi L TABF L SMDi L TABF_L SKFi L TABG L SMFi L TABG L Legend 1 In Unity Pro a variable is associated with each symbolized table See Symbolized tables p 161 2 The table is declared from 0 L 1 its type and location depending on the address Example MWi L declared in PL7 as TABA L in converted into TABA_L TABA_Lis therefore a declared table from 0 L 1 of type INT located at sMwi and with the same comment as TABA 35006148 03 October 2005 75 Correspondences between common language elements I O object tables The following table describes any correspondence and differences between the symbolized tables of PL7 and Unity Pro input output objects PL7 Unity Pro Status Address Associated Address Associated symbol variable 1 1 O object SI L TABA L SI L
2. Sections The following table describes any correspondence and differences between PL7 and Unity Pro section characteristics PL7 Unity Pro Status Sections Yes Yes Converted Activation condition Yes Yes Converted Objects 1 Si Equivalent Unity Pro objects Modified 2 SMi MWi Xj SWi Xj SKWi Xj SMi 2M03 SMi SSWj SMi 5Kw3 Protection of sections Write Write Converted Read Write Read Write None None Section attributes Long name 16 characters gt 16 characters Modified 3 Short name 8 characters gt 8 characters Modified Comment 250 characters 256 characters Modified Number of MAST FAST AUXi 4096 No limitation Modified sections in EVT 1 1 Converted DFB 1 gt 1 Modified SR 1 1 Converted Language LD ST IL LD ST IL Converted Legend 1 Objects that define the execution condition of a section 2 The PL7 application converter replaces these objects by their Unity Pro equivalents See Correspondences between PL7 and Unity Pro language objects p 64 3 The section name cannot already be used to define one of the variables of the application 56 35006148 03 October 2005 Correspondence between application structures 6 2 Correspondences between PL7 and Unity Pro functional modules Functional modules Introduction Conversion replaces PL7 functional module characteristics by their Unity Pro
3. oooooooocoorroror eee 89 Comparison instructions 0 0 0 cece tees 90 Bit table instructions 0 0 0 a e a Aa PE EE E ew 92 Arithmetic instructions asus uasaa nua eee eee 93 LOGIC INStFUCTIONS 21 4 ce ri r E eee Mea aed 96 Shift INSTrUCHONS tirar a alee eae 97 35006148 03 October 2005 7 4 Chapter 8 Chapter 9 9 1 9 2 Chapter 10 10 1 10 2 Numerical conversion instructions 0 0 0 cee eee eee Table Instructions 008 ia di td ess ea ees Character string instructions 0 0 000 cee ett tees Time management instructionS 0 00 ee Exchange Instructions 0 0 00 eect tte Input output instructions 0 0 0 eee Process control instructions 0 0 0 eee eet tte Other instrUctiONS ori eo fee choi hats ae RE ORD AA ee Communication instructions s 0 000 TCP Open instructions o oocccocccccoco eee Diagnostics instructions 0 0 0 cece tees Grafcet instructions 6 0 0 0 eee Human Machine Interface HMI instructions 000 0c eee ee Correspondences between PL7 and Unity Pro SFBs Ata Glance tit het Ree eek bed teed ie ae are Fee ee is Types of Unity Pro EFB instances 0 0 2 0 eee eee eee Call of an SFB in structured text 2 0 0 eects Call of an SFB in instruction list language cece eee eee Call of an SFB in ladder language 00 c cece ee
4. 2 000 K bytes 52 35006148 03 October 2005 Correspondence between application structures At a Glance Subject of this Chapter What s in this Chapter This chapter contains the tables of correspondence between PL7 and Unity Pro application structures This chapter contains the following sections Section Topic Page 6 1 Correspondences between PL7 and Unity Pro structural 54 elements 6 2 Correspondences between PL7 and Unity Pro functional 57 modules 35006148 03 October 2005 53 Correspondence between application structures 6 1 Correspondences between PL7 and Unity Pro structural elements At a Glance Subject of this Section What s in this Section This section contains the tables of correspondence between PL7 application structure elements and their Unity Pro equivalents PL7 application structure elements are divided into three categories e those that remain unchanged and are translated automatically status converted e those that have a Unity Pro equivalent and are translated automatically status modified e those that have no Unity Pro equivalent status deleted Note if a PL7 element has no Unity Pro correspondence a warning and a conversion error message are generated See Analysis p 40 This section contains the following topics Topic Page Tasks events and SRs 55 The section
5. Differences between PL7 and Unity Pro IV At a Glance Subject of this Part What s in this Part This part presents the main differences between PL7 programming and its equivalent in Unity Pro This part contains the following chapters Chapter Chapter Name Page 13 Differences between the application structures 151 14 Differences between common language elements 153 15 Differences between Structured Text language elements 169 16 Differences between Instruction List language elements 171 17 Different display in runtime screens 173 35006148 03 October 2005 149 Differences between PL7 and Unity Pro 150 35006148 03 October 2005 Differences between the application structures 13 At a Glance Subject of this Chapter What s in this Chapter This chapter describes the main differences between the PL7 application structure and its Unity Pro equivalent This chapter contains the following sections Section Topic Page 13 1 Differences between PL7 and Unity Pro functional modules 152 35006148 03 October 2005 151 Differences between the application structures 13 1 Differences between PL7 and Unity Pro functional modules Functional Modules Introduction Converting a PL7 application into a Unity Pro application generates certain differences which are described in the following parag
6. 1 In the application browser double click on the DFB type to be unprotected Result The DFB type Editor opens the screen for the selected DFB type Select the Properties command from the Edit menu Check the Not protected box Confirm with OK Note The confirmation is only effective once the password is entered CAUTION Conversion precautions The user s own diagnostics DFBs must be completed manually after conversion To complete them e erase the private variables ADR_ PROG COMMENT INST NAME e create two private variables PIN NB type INT and PIN VAL type BOOL e modify the algorithm of the DFB in order to calculate the values of PIN_NB and PIN_ VAL which contain the pin number in error and its expected value e modify the call parameters of the EF REGDFB replace the parameters ADR_PROG COMMENT INST NAME with PIN NB and PIN VAL e adapt the DFB code Failure to follow this instruction can result in injury or equipment damage 35006148 03 October 2005 33 Conversion of a PL7 DFB Exporting the source file CAUTION Conversion precautions The Schneider PL7 Diagnostics DFBs ALRM_DIA EV_DIA MV_DIA NEPO_DIA TEPO_DIA and SAFETY_MONITOR are automatically converted to Schneider Unity Pro Diagnostics DFBs It is therefore not necessary to unprotect these DFBs before starting the conversion procedure The other PL7 diagnostic
7. 62 35006148 03 October 2005 Correspondences between common language elements Operations between mixed types Introduction Operations between mixed types are not always possible in Unity Pro Conversion replaces these PL7 operations by their Unity Pro equivalent Mixed types The following table describes any correspondence and differences between operations between mixed types Operations PL7 Unity Pro Status Between words and double words Yes No Modified 1 indexed or not Between a word table and a double word table Between 2 word or double word tables Yes Yes Converted 2 Between word and double word tables Yes No Modified 3 and words or double words Assignment of a bit table into another bit Yes Yes Converted table Assignment of a word or double word Yes No Modified 4 table into a bit table Legend 1 Operations between words and double words are not possible in Unity Pro See Words and double words p 156 2 This type of operations is possible in Unity Pro See Table instructions p 101 3 Operations between word or double word tables and words or double words are not possible in Unity Pro See Tables and double words p 156 4 The assignment of a word or double word table into a bit table is not possible in Unity Pro See Assignment of tables p 156 35006148 03 October 2005 63 Correspondences betwe
8. p 158 2 The converter selects the bus number PL7 Unity Pro x r Rack y m Position in the rack module i Channel e d Data Operational if equal to zero c e Connection point equipment r n Network Operational if equal to zero s s Station num num SFB b Bus 35006148 03 October 2005 67 Correspondences between common language elements Labels Introduction Conversion replaces the PL7 objects by their Unity Pro equivalent Labels The following table describes any correspondence and differences between PL7 and Unity Pro objects PL7 Unity Pro Status Syntax Type of Syntax Type of data data Program label SLi 1 label Li label Modified DFB label Identifier label Identifier label Converted Legend 1 i 0 999 35006148 03 October 2005 Correspondences between common language elements System objects Introduction Conversion replaces the PL7 objects by their Unity Pro equivalent System objects The following table describes any correspondence and differences between PL7 and Unity Pro objects PL7 Unity Pro Status Syntax Type of Syntax Type of data data System bit Si 1 EBOOL Si BOOL Converted or SXi System word SSWi 1 WORD SSWi INT Converted Real time clock system 2SW50 4 AR_W SSW50 4 ARRAY Converted word 0 3 OF INT at SSW50 System double word SSDi DWORD SDi DINT Conve
9. PL7 Unity Pro Syntax Type of Syntax 1 Type of data data ADR xy i e AR_W 6 ADDR r m c d ARRAY OF ADR 2 1 3 ADDR 0 2 1 3 INT ADR xy i SYS AR_W 6 ADDR r m c SYS ARRAY OF ADR 102 1 SYS ADDR 1 2 1 SYS INT ADR xy SYS AR_W 6 ADDR r m SYS ARRAY OF ADR 102 SYS ADDR 1 2 SYS INT ADR SYS AR_W 6 ADDR SYS ARRAY OF INT ADR APP AR_W 6 ADDR APP ARRAY OF INT ADR xy i c SYS AR_W 6 ADDR b e SYS ARRAY OF ADR 4 0 23 SYS ADDR 4 23 SYS INT 2 ADR s xy i e AR_W 6 ADDR n s r m c d ARRAY OF ADR 2 4 2 1 3 ADDR 12 4 0 2 1 3 INT ADR r s xy i SYS AR_W 6 ADDR n s r m c SYS ARRAY OF ADR 2 4 102 1 SYS ADDR 2 4 1 2 1 SYS INT ADR r s xy SYS AR_W 6 ADDR n s r m SYS ARRAY OF ADR 2 4 102 SYS ADDR 2 4 1 2 SYS INT ADR r s SYS AR_W 6 ADDR n s SYS ARRAY OF ADR 2 4 SYS ADDR 2 4 SYS INT ADR r s APP AR_W 6 ADDR n s APP ARRAY OF ADR 4 APP ADDR 4 APP INT ADR r s APP num AR_W 6 ADDR n s APP num ARRAY OF ADR 2 4 APP 0 ADDR 2 4 APP 0 INT ADR r s xy i c SYS AR_W 6 ADDR n s b e SYS ARRAY OF ADR 2 4 4 0 23 SYS ADDR 2 4 4 23 SYS INT 2 66 35006148 03 October 2005 Correspondences between common language elements Legend 1 The address ADR is replaced by an EF See Network address words
10. See Bit table instructions p 92 Example M0 16 3MW20 is converted into MOVE INT_ ARX MW20 M0 16 156 35006148 03 October 2005 Differences between common language elements 14 2 Differences between PL7 and Unity Pro objects At a Glance Subject of this This section describes the main differences between PL7 objects and their Unity Pro Section equivalent What s in this This section contains the following topics Section Topic Page Immediate values 158 Memory objects variables and constants 159 Word bits 160 Symbolized tables and indexed objects 161 35006148 03 October 2005 157 Differences between common language elements Immediate values Introduction Integer and long integer words Converting a PL7 application into a Unity Pro application generates certain differences which are described in the following paragraphs WORD and DWORD types are converted into INT and DINT types by the PL7 converter A hexadecimal immediate value greater than 16 7FFF 32767 is converted to a negative decimal value the original value is shown in the comment example SMWO 16 ABCD is converted to 2MW0 21555 16 ABCD The conversion of the immediate value of a long integer is identical for values greater than 16 7FFFFFFF 2147483647 example 2MD80 16 ABCDABCD is converted to 3MD80 1412584499 16 ABCDABCD Network address The addre
11. TABINT1 TABINT2 TABINT3 are integer tables TABINT1 TABINT2 AND TABINT3 is replaced with TABINT1 AND ARINT TABINT2 TABINT3 The operators AND OR XOR between a table and an integer or long integer word have been deleted in Unity Pro The PL7 application converter replaces these operators with EF equivalents See Integer and long integer word tables logic instructions p 104 A single EF is used for each switching operator Example INT1 is an integer TABINT1 and TABINT2 are integer tables Both TABINT1 INT1 AND TABINT2 and TABINT1 TABINT2 AND INT1 are replaced with TABINT1 AND ARINT INT TABINT2 INT1 35006148 03 October 2005 163 Differences between common language elements Tables functions The table functions for which you must indicate a rank rank of an element in the table behave in the same way as the corresponding PL7 functions except when the rank is negative In this case operation is as follows Functions Operation when the rank is negative COPY_ARDINT_AREBOOL COPY_ARINT_AREBOOL COPY_AREBOOL_ARDINT COPY_AREBOOL_ARINT COPY_AREBOOL_AREBOOL If one of the ranks is negative source or destination the function is not executed and the resulting table is not modified In PL7 the ranks are set automatically to O and the function is executed EQUAL_ If the rank from which the comparison is launched is negative the result is equal to this n
12. the converted PL7 application and output window are opened and displayed on the screen in the Unity Pro software To correct any conversion errors click on the error line displayed in the output window to go directly to the part of the program to be modified See Convertor message in the analysis procedure p 43 35006148 03 October 2005 15 Overview Semi Automatic Conversion The procedure for converting a PL7 DFB is as follows gt Unity Pro DFB xdb source file PL7 DFB gt dfb source file The dfb PL7 source file is converted into a xdb Unity Pro source file At the end of the procedure the converted PL7 DFB is saved in its source format In order for this DFB to be exploitable by Unity Pro it must be manually imported into a Unity Pro application Following this import you must start the project s analysis phase manually in order to detect any conversion errors and display them on the screen in the form of an output window To correct any conversion errors click on the error line displayed in the output window to go directly to the part of the program to be modified See Convertor message in the analysis procedure p 43 16 35006148 03 October 2005 Overview Conversion Principle Applications and Processors General Points The PL7 application converter transforms PL7 source files fef dfb into Unity Pro source files xef xdb and during the conversi
13. 4 L Legend 1 The KBxy i r Land KF2 3 4 L character strings are replaced by a single character string See Memory objects variables and constants p 159 PL7 Unity Pro Optional if equal to zero x Rack y m Position in the rack module i Channel number r d Rank 82 35006148 03 October 2005 Correspondences between common language elements Remote input output objects Introduction Remote Fipio bus objects Conversion replaces the PL7 objects by their Unity Pro equivalent The following table describes any correspondence and differences between PL7 and Unity Pro objects objects SI 0 2 34 1 2 1 I 2 34 0 1 2 1 1 PL7 Unity Pro Status Syntax Syntax Remote Fipio bus 1I p 2 c xy i r I b e r m c d Modified Legend 1 In Unity Pro the bus identifier has been added In order to convert Remote Fipio bus objects the selected b identifier is assigned the value 2 PL7 Unity Pro p Module address c e Connection point i c Channel number r d Rank b Bus identifier x r Rack y m Position in the rack 35006148 03 October 2005 83 Correspondences between common language elements Remote AS i bus The following table describes any correspondence and differences between PL7 objects and U
14. Correspondences between common language elements Input output instructions Introduction Instruction list Conversion replaces the PL7 instructions by their Unity Pro equivalent The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status EF MOD_CAM MOD_CAM Modified 1 MOD_PARAM MOD_PARAM Modified 1 MOD_TRACK MOD_TRACK Modified 1 TRF_RECIPE TRF_RECIPE Modified 1 DETAIL_OBJECT DETAIL_OBJECT Modified 1 Legend 1 The function is replaced by an EF The parameters are entered between brackets example MOD_CAM CH0 2 0 1 2 9 110 35006148 03 October 2005 Correspondences between common language elements Process control instructions Introduction Instruction list Conversion replaces the PL7 instructions by their Unity Pro equivalent The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status EF PID PID_INT Modified 1 PID_MMI Deleted PWM PWM_INT Modified 1 SERVO SERVO_INT Modified 1 Legend 1 The function name is modified its operation remains the same but the order of its parameters has been changed See IN OUT INOUT parameters p 165 35006148 03 October 2005 111 Correspondences between common language elements Othe
15. EAD ASYN EAD GDATA EAD VAR END_REQ R R READ GDATA R S END_REQ R R R READ VAR S S ERVER UNITE SERVER 35006148 03 October 2005 165 Differences between common language elements The following diagram shows the example of the communication instruction OUT_IN_CHAR OUT_IN_ CHAR EN ENO Address ADR RECP Received_Data Mode _ TYPE Data_to Send EMIS Management_Param GEST GEST Management Param The following table describes the parameters of the communication instruction OUT_IN_CHAR Input parameters IN Input output parameters INOUT Output parameters OUT ADR GEST RECP TYPE EMIS The ST representation of the instruction OUT_IN_ CHAR in PL7 is as follows OUT_IN CHAR Address Mode Data_to Send Received Data Management Param The ST representation of the instruction OUT_IN_CHAR in Unity Pro is as follows OUT_IN CHAR Address Mode Data_to Send Received Data Management _ Param 166 35006148 03 October 2005 Differences between common language elements 14 4 Differences between PL7 and Unity Pro SFBs Types of Unity Pro EFB instances Introduction Value of current step The conversion of a PL7 application into a Unity Pro application generates certain differences which are described in the following paragraphs The PL7_ DRUM
16. INT SKWi S3MW3 L AR_W SKWi SMW3 L ARRAY OF INT SKWi SKW3 L AR_W SKWi SKW3 L ARRAY OF INT SKWi n L AR_W SKWi n L ARRAY OF INT 72 35006148 03 October 2005 Correspondences between common language elements variables and constants p 159 PL7 Unity Pro Status Syntax Type of Syntax Type of data data Constant double words 3KDi WORD SKDi DINT Converted SKDi SMW3 DWORD SKDi Mw3 DINT SKDi SKW3 DWORD KDi SKWj DINT KDi n DWORD KDi n DINT KDi L AR_D SKDi L ARRAY OF DINT SKDi S3MW3 L AR_D SKDi SMW3 L ARRAY OF DINT SKDi SKW3 L AR_D SKDi 5KW3 L ARRAY OF DINT KDi n L AR_D KDi n L ARRAY OF DINT Constant reals SKFi REAL SKFi REAL Converted SKFi SMW3 REAL SKFi SMW REAL SKFi SKWj REAL SKFi 23K0W3 REAL KFil n REAL KFil n REAL SKFi L AR_R SKFi L ARRAY OF REAL Common network No 3NW 3 k 1 WORD SNWs d INT Modified words 0 other SNW i j k 1 WORD NWn s d INT Modified networks Variable type character MBi L STRING xxx_L String L STRING Modified string 2 Constant type character 3KBi L STRING xxx_L String L STRING Modified string 2 Legend 1 PL7 Unity Pro pil n network number j s station number k d word number 2 Objects MBi L and KBi L are replaced by a character string See Memory objects 35006148 03 Octobe
17. Recycle E Asadoc Ey Kpcms Ey Pl7user Ey Softoft y Complex 3 Multimedia Files Pm6 E TC Toolbox E Concept EY My Music y Program Files Temp E Confad EY notes Ey Psfonts Y tempef 4 gt File name Open Files of type DFB files DFB M Cancel Options d ouverture Open the project in read only mode Open XEF File with Wizard mO pen Options Type Name Version Last modification Comment LE Choose the hard drive and or the directory containing the file to be converted Select the file dfb to be opened and therefore converted The name of the file then appears in the File name field Conversion procedure Step 1 2 5 Confirm with Open 35006148 03 October 2005 35 Conversion of a PL7 DFB Step Action 6 The conversion procedure is then started The status bar shows how the procedure is progressing 7 At the end of conversion a screen appears indicating the end of the procedure Conversion of Protected DFBs Procedure If you have sold protected DFBs to your customers you must use the following procedure to convert them from PL7 to Unity Pro Step Action 1 In PL7 clear the code for your protected DFBs 2 Unprotect your DFBs Send your customers the unprotected DFBs without the code and ask them to replace the protected DFBs in their PL7 applications by these unprotected DFBs
18. SET Modified 1 RESET RESET Modified 1 Legend 1 Replaced by an EF 35006148 03 October 2005 89 Correspondences between common language elements Comparison instructions Introduction Integer words Long integer words Conversion replaces the PL7 instructions by their Unity Pro equivalent The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status WORD INT Operator gt gt Converted lt lt Converted lt lt Converted 2 2 Converted Converted Converted The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status DWORD DINT Operator gt gt Converted lt lt Converted lt lt Converted 2 2 Converted Converted Converted 90 35006148 03 October 2005 Correspondences between common language elements Real words The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Floating point Unity Pro REAL Status Operator gt gt Converted lt lt Converted IA IA Converted IV IV Converted Converted Converted 35006148 03 October 2005 91 Correspondences b
19. Sa ae oe SE eee ee e 139 Command instructions 0 20 0 00s 140 Boolean instructions 0 0 00 eee 141 Instruction List language extensions aeua e eee eee eee 142 Correspondences between Grafcet language elements 143 Ata Glance ci AE fe Pe Peed ee et ak Rhee ae Pees 143 Grafcet instructions 2 0 cee teens 144 Conversion restrictions PL7 Grafcet language 000 eee eee 145 Other correspondences between PL7 and Unity Pro elements ieren a Rae Oe a ae we ee a 147 Printouts animation tables and runtime screens ooooooo 147 Differences between PL7 and Unity Pro 149 Ata Glance usada eee Ree et a Ae ie ek ie eee 149 Differences between the application structures 151 Ata Glance i ccc544 dere en eee Pe be ie an ee aed 151 Differences between PL7 and Unity Pro functional modules 152 Functional Modules 0 0 0c eee ttt 152 Differences between common language elements 153 AL AGIAN Ce esac E Arce ate Gh ele aera ed dette oh 153 Differences between PL7 and Unity Pro types and tables 154 Ata Glance diia aa a geal dius Malate wes eh eS 154 Typesandtables wi aco eas a AO Pa EE te al Ode eS 155 Operations between mixed types cocococcccococ eee 156 Differences between PL7 and Unity Pro ObjectS o o oooooo 157 ACACIA Ped ws a Red eh aa 157 Immediate values occ ib 158 Memory objects va
20. TABA_L Modified 2 tables SIWO L TABB L SIWO L TABB_L 00 L TABC L 00 L TABC_L SOWO L TABD L SOWO L TABD_L Legend Addressing of the in rack See In rack Input Output objects p 81 and or remote See Remote input output objects p 83 input output objects 1 In Unity Pro a variable is associated with each symbolized table See Symbolized tables p 161 2 The table is declared from 0 L 1 its type and location depending on the address Example 51 L declared in PL7 as TABA L in converted into TABA_L TABA_L is therefore a declared table from 0 L 1 of type EBOOL located at 51 and with the same comment as TABA 76 35006148 03 October 2005 Correspondences between common language elements Indexed memory and constant objects The following table describes any correspondence and differences between PL7 and Unity Pro symbolized indexed memory and constant objects PL7 Unity Pro Status Address Associated Address Associated symbol variable 1 Indexed SMWi 3 TABA j SMWi 3 TABA_AR j Modified 2 memory and SMDi 3 TABB j SMDi j TABB AR j constant i gt SMi j TABC 3 SMi 3 TABC AR J objects SMFi 3 TABD j SMFi lj TABD AR j SKWi TABE J SKWi TABE_AR j SKDi TABF j SKDi TABF_AR j SKFi 3 TABG 3 SKFil j TABG AR j Legend 1 In Unity Pro a variable is ass
21. TEMPBOOL I 0 0 0 I SRi ST TEMPBOOL CAL Ri R 0 1 TEMPBOOL O 0 O Ri ST TEMPBOOL CAL Ri R 0 1 0 0 TEMPBOOL 32 lt SRi L lt R Ri ST TEMPBOOL 255 CAL Ri R TEMPBOOL 1 0 0 0 I SRi ST TEMPBOOL CAL Ri R 0 1 TEMPBOOL O 0 O Ri ST TEMPBOOL CAL Ri R 0 1 0 0 TEMPBOOL SFB SDR R DRi ST TEMPBOOL Converted CAL DRi R TEMPBOOL U 0 1 U SDRi ST TEMPBOOL CAL DRi R 0 U TEMPBOOL 1 Key 1 You must also assign the values of the current step to the DRUM output objects See Types of Unity Pro EFB instances p 167 Note reversible SFBs BLK END_BLK are not converted a warning and a conversion error message are generated See Analysis p 40 122 35006148 03 October 2005 Correspondences between common language elements Call of an SFB in ladder language Introduction Call of an SFB in Ladder The conversion automatically replaces SFBs with equivalent EFBs insofar as these exist The following table describes the correspondence and possible differences between SFBs and EFBs PL7 Unity Pro State SFB PL7 Timer TM10 IN MODE TOF TB Is TM P 600 MODIF Y TOF Timer 1 IN PL7_TOF TM10 IN TM MODE TON TB Is TM P 600 MODIF Y TON_Timer_1 IN PL7_TON TM10 IN TM MODE TP TB Is TM P 600 MODIF Y TP_Timer_1
22. application converted into Unity Pro p 39 manually in order to check the syntax of your application Note If during the import or analysis phase an output window See End of the analysis procedure p 42 is displayed on the screen this means that there are conversion errors In this case correct these errors See Convertor message in the analysis procedure p 43 35006148 03 October 2005 29 The conversion of a PL7 application Results of the PL7 application conversion Introduction Results The results of the conversion of a PL7 application into a Unity Pro application are described in the following paragraphs At the end of the conversion procedure there are two possible scenarios e the application has been correctly converted e conversion errors have been generated If the application has been correctly converted it is displayed on screen and may be saved in Unity Pro application format stu file In the event of conversion errors you must manually correct the application in order for it to be exploitable The output window See End of the analysis procedure p 42 which can be used to manually correct these errors is automatically displayed on the screen Note the converted PL7 application may be saved in Unity Pro application format stu even if conversion errors have not been corrected If this is the case the next time the application is opened you must first launch an Analy
23. application processor e the application as well as the sections functional modules and DFBs it contains to be unprotected e the application source file to be exported and saved Update All PL7 applications earlier than version 4 0 must be updated before being converted into a Unity Pro application To update a PL7 application execute the following actions running PL7 V4 3 Step Action 1 Choose the Open command from the File menu 2 Select the hard disk and or directory containing the file to be opened Select the file to be opened the name of this file then appears in the File Name field Confirm with Open In the Application Browser double click on the Configuration directory Double click on the Hardware configuration sub directory Result The Configuration screen appears Select a version TSX eee e3 processor that is compatible with your application from the drop down menu in the top left hand corner of the Configuration screen Result The Change Processor screen appears Confirm your selection with OK Select the Save command from the File menu 26 35006148 03 October 2005 The conversion of a PL7 application Disabling the To deactivate the protection of a PL7 application execute the following actions protection running PL7 V4 3 Step Action 1 Select the Properties command from the
24. between ladder language elements 8 At a Glance Subject of this Chapter What s in this Chapter This chapter contains the tables of correspondence between ladder language elements The PL7 ladder language elements are divided into two categories e those that remain unchanged and are translated automatically status converted e those that have a Unity Pro equivalent and are translated automatically status modified This chapter contains the following topics Topic Page The definition of a ladder network 128 The rungs 129 Coils 130 Operate and compare blocks 131 Conversion restrictions PL7 ladder language 132 35006148 03 October 2005 127 Correspondences between ladder language elements The definition of a ladder network Introduction Conversion replaces the PL7 ladder language elements by their Unity Pro equivalent Definition of a The following table describes any correspondence and differences between PL7 ladder network and Unity Pro ladder language objects PL7 Unity Pro Status Label SLi Li Modified Comment Network comment Network comment Converted 128 35006148 03 October 2005 Correspondences between ladder language elements The rungs Introduction Rungs Conversion replaces the PL7 ladder language elements by their Unity Pro equivalent The following table describes any correspondence and differ
25. by TABA in PL7 Mwi Lis symbolized by TABA L This is no longer possible in Unity Pro The PL7 application converter replaces TABA L by a long integer table L named TABA_L and located on the basis of Mwi In Unity Pro you can associate a symbol with a simple object but cannot use the same symbol to refer to an indexed object Example if sMwi is symbolized by TABA in PL7 MWi j is symbolized by TABA 3 This is no longer possible in Unity Pro The PL7 application converter replaces TABA j by a maximum length integer table named TABA AR and located on the basis of SMWi Note symbolized indexed input output objects cannot be converted into equivalent tables as the length of this table is unknown These objects are therefore converted into their non symbolized form address 35006148 03 October 2005 161 Differences between common language elements 14 3 Differences between PL7 and Unity Pro instructions and functions At a Glance Subject of this Section What s in this Section This section describes the main differences between PL7 instructions and functions and their Unity Pro equivalent This section contains the following topics Topic Page Table instructions and functions 163 Process control Other and Communication instructions 165 162 35006148 03 October 2005 Differences between common language elements Table instructions a
26. converting a PL7 DFB into Unity Pro 35 Conversion of Protected DFBS 0 000 e cece tees 36 Procedure for importing a PL7 DFB into Unity Pro 37 Results of the PL7 DFB conversion 0 cece eee eee eens 38 Analysis of a PL7 application converted into Unity Pro 39 Ata Glance icici SAE Set SEO ee SEA te die Sedan hed eae 39 GSMO Tle wes Sion E reais A A Gao he ce ete 40 Analysis Procedure n es4a jee dia AAA eth 41 End of the analysis ProCeQure oooooccoccoo tees 42 35006148 03 October 2005 Part Ill Chapter 5 Chapter 6 6 1 6 2 Chapter 7 7 1 7 2 7 3 Convertor message in the analysis procedure 0e eee aee 43 Miscellaneous errors in the analysis procedure 0 eee eens 44 Correspondence between PL7 and Unity Pro 45 Ata Glance is ita Ga A a ie ee ee Ta ee Ga a ee 45 Inter platform equivalence 2 000 ee eee eee eee 47 Abia lO putas a cee acral nbn data ees 47 Premium processors 0 00 e eee eee teens 48 Atrium Processors vnc wae Sc ate Bae ty Be WY See ee o e ea a Aa 51 Correspondence between application structures 53 Ata Glance cerraba A ee ee Gite dt eee hes 53 Correspondences between PL7 and Unity Pro structural elements 54 Aba GIANG fae static naeran a lank oe Roe aah otek TE ame veya en dea ata eka 54 Tasks events and SRS eis bie a it e tati a
27. instruction has no Unity Pro correspondence a warning and a conversion error message are generated See Analysis p 40 35006148 03 October 2005 87 Correspondences between common language elements What s in this This section contains the following topics Section Topic Page Boolean instructions 89 Comparison instructions 90 Bit table instructions 92 Arithmetic instructions 93 Logic instructions 96 Shift instructions 97 Numerical conversion instructions 99 Table instructions 101 Character string instructions 107 Time management instructions 108 Exchange Instructions 109 Input output instructions 110 Process control instructions 111 Other instructions 112 Communication instructions 113 TCP Open instructions 114 Diagnostics instructions 115 Grafcet instructions 116 Human Machine Interface HMI instructions 117 88 35006148 03 October 2005 Correspondences between common language elements Boolean instructions Introduction Instruction list Conversion replaces the PL7 instructions by their Unity Pro equivalent The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status Operator Converted AND AND Converted OR OR Converted XOR XOR Converted NOT NOT Converted RE RE Modified 1 FE FE Modified 1 SET
28. instructions PL7 Unity Pro Status Operator between two Converted tables Operator between a table MOVE_REAL_ARREAL Modified 1 and a real word EF EQUAL_ARR EQUAL_ARREAL Modified 3 FIND_EQR FIND_EQ_ARREAL Modified 2 FIND_EQRP FIND_EQP_ARREAL Modified 3 FIND_GTR FIND_GT_ARREAL Modified 2 FIND_LTR FIND_LT_ARREAL Modified 2 LENGTH_ARR LENGTH_ARREAL Modified 2 MAX_ARR MAX_ARREAL Modified 2 MIN_ARR MIN_ARREAL Modified 2 OCCUR_ARR OCCUR_ARREAL Modified 2 ROL_ARR ROL_ARREAL Modified 2 ROR_ARR ROR_ARREAL Modified 2 SORT_ARR SORT_ARREAL Modified 2 SUM_ARR SUM_ARREAL Modified 2 Legend 1 The operator is replaced by an EF 2 The function name is modified but the operation remains the same 3 The function name is modified but the operation remains the same except in the case of negative ranks See Tables functions p 164 106 35006148 03 October 2005 Correspondences between common language elements Character string instructions Introduction Instruction list Conversion replaces the PL7 instructions by their Unity Pro equivalent The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status EF STRING_TO_INT STRING_TO_INT Converted STRING_TO_DINT STRING_TO_DINT Converted INT_TO_STRING INT_TO_STRING Converted DINT_TO_STRING DINT_T
29. of safety and to ensure compliance with documented system data only the manufacturer should perform repairs to components When controllers are used for applications with technical safety requirements please follow the relevant instructions Failure to observe this product related warning can result in injury or equipment damage 35006148 03 October 2005 About the Book User Comments We welcome your comments about this document You can reach us by e mail at techpub schneider electric com 10 35006148 03 October 2005 The PL7 application converter general Ata Glance Subject of this Part What s in this Part This part provides a general overview of the PL7 application converter and the conversion principle This part contains the following chapters Chapter Chapter Name Page 1 Overview of the converter 13 35006148 03 October 2005 11 General 12 35006148 03 October 2005 Overview of the converter At a Glance Subject of this This chapter presents the PL7 application converter and describes the procedure for Chapter converting PL7 applications into Unity Pro applications What s in this This chapter contains the following topics Chapter Topic Page Overview of the PL7 Applications Converter 14 Conversion Principle General Points 15 Conversion Principle Applications and Processors 17 Conversion prin
30. 2 TSX P 57203 2 TSX P57 204 Processor replaced TSX P57 103 1 Not necessary TSX P57 104 Processor replaced TSX P57 153 1 Not necessary TSX P57 154 Processor replaced TSX P57 20 202 TSX P 57203 2 TSX P57 204 Processor replaced TSX P57 252 TSX P 57253 2 TSX P57 254 Processor replaced T PMX P57 202 TSX P 57203 TSX P57 204 Processor replaced TSX P57 203 1 Not necessary TSX P57 203 with new OS Processor version updated TSX P57 253 1 Not necessary TSX P57 253 2 with new OS Processor version updated TSX P57 2623 1 Not necessary TSX P57 2623 with a new OS identified by Unity as a TSX P57 2634 Processor version updated TSX P57 30 302 TSX P 57303 1 2 TSX P57 304 Processor replaced TSX P57 352 TSX P 57353 1 2 TSX P57 354 Processor replaced T PMX P57 352 TSX P 57353 1 TSX P57 354 Processor replaced TSX P57 303 1 Not necessary TSX P57 303 with new OS Processor version updated TSX P57 353 1 Not necessary TSX P57 353 with new OS Processor version updated TSX P57 3623 1 Not necessary TSX P57 3623 with a new OS identified by Unity as a TSX P57 3634 Processor version updated TSX P57 402 TSX P 57453 1 TSX P57 454 Processor replaced TSX P57 452 TSX P 57453 1 TSX P57 454 Processor replaced T PMX P57 452 TSX P 57453 1 TSX P57 454 Processor replaced TSX P57 453 1 Not necessary TSX P57 454 Processor replaced Le
31. 3 1 index 10 2 3 1 index Ixy i r L AR_X vosdsh ARRAY PTZ Zo EL 10 2 3 1 L OF EBOOL Word SIWxy i r WORD SIWr m c d INT Modified IW2 3 1 21W0 2 3 1 Double word SIDxy i r DWORD IDr m c d DINT Modified ID2 3 1 ID0 2 3 1 Real SIFxy i r REAL SIFr m c d REAL Modified IF2 3 1 1F0 2 3 1 Outputs Q Bit SOxy i r EBOOL SQr m c EBOOL Modified 202 3 1 200 2 3 1 SQxy i r index EBOOL 0r m c d index EBOOL Q2 3 1 index Q0 2 3 1 index 0xy i r L AR_X Qr m c d L ARRAY Q2 3 1 L 00 2 3 1 L OF EBOOL Word SOWxy i r WORD SQWr m c d INT Modified SQW2 3 1 2010 2 3 1 35006148 03 October 2005 81 Correspondences between common language elements PL7 Unity Pro Status Syntax Type of Syntax Type of data data Double word SQDxy i r DWORD QDr m c d DINT Modified 0D2 3 1 QD0 2 3 1 Real SOFxy i r REAL QFr m c d REAL Modified 0F2 3 1 SOF0 2 3 1 Variables M Word SMWxy i r WORD SMWr m c d INT Modified SMW2 3 1 SMWO 2 3 1 Double word SMDxy i r DWORD SMDr m c d DINT Modified SMD2 3 1 SMD0 2 3 1 Real SMFxy i r REAL SMFr m c d REAL Modified SMF2 3 1 MF0 2 3 1 Constants K Word SKWxy i r WORD KWr m c d INT Modified SKW2 3 SRWO 2 361 Double word SKDxy i r DWORD KDr m c d DINT Modified SKD2 3 SEDO 24 dad Real SKFxy i r REAL KFr m c d REAL Modified KF2 3 KFO 2 3 1 Character string SKBxy i r L STRING 1 STRING Modified KF2 3
32. 35006148_03 a brand of Schneider Electric Unity Pro PL7 application converter User manual October 2005 eng Telemecanique 35006148 03 October 2005 Table of Contents Part Chapter 1 Part Il Chapter 2 Chapter 3 Chapter 4 About the BOOk oocoocoococrornn eee 9 The PL7 application converter general 11 Ata Glancest at oe tet e asar pe de tk o Le E bela 11 Overview Of the converter oooooooccococooon oo 13 Ata Glance oare a a A a o waked ete 13 Overview of the PL7 Applications Converter 0 00 cece eee eee 14 Conversion Principle General Points 000 e eee eee eee 15 Conversion Principle Applications and Processors 00e0 eeu 17 Conversion principle technical aspects 0 0 eee eee eee eee 19 Conversion to Unity V2 0 0 0 0 22 PL7 application conversion procedure 23 Alia Glace arde e feet eet ON os a cd aa dot ce Saks te ahs orld 23 Conversion of a PL7 application o ooo 25 Ata Glane oct AA Hates a tingle alae aut eeee 25 General enina e Gee we E ep OI Ae ee EA AE ee 26 Procedure for Converting a PL7 Application into a Unity Pro Application 28 Results of the PL7 application conversion 002000eeeeeeee 30 Conversion of a PL7 DFB 20 2 0c eee eee eee eee 31 Ata Glace a seni td Ae tester Ea neta al ees Seen 31 Generali caca a Lek ata la ork tae ed 32 Procedure for
33. 55 The sections 54 Tio bY aa glade nha dlaae e a 56 Correspondences between PL7 and Unity Pro functional modules 57 Functional modules sussa ra e a e eee eee 57 Correspondences between common language elements 59 Abia Glance sa catar pela da Lass ane ea ia a baca puta 59 Correspondences between PL7 and Unity Pro types and tables 60 Atala it o ear ia AE E E Mee Sen nati amp big ene nose ean wee Oana eS 60 Types andtables 2c 2 0i6 steered Rh pee ee be Peed he ote eee eS 61 Operations between mixed types 0 00 eects 63 Correspondences between PL7 and Unity Pro language objects 64 Ata Glance triana oe Pee tee ee ae Sci Gade ee we 64 Immediate valueS s wie cv ee ee ba OP ee Ph eee a ee eee ares 65 A Haat een dete ek Gee eet de Beene eee cae A 68 Systemi OD SCtSes c 2 se goer esau eae te ele Bled Gales BARR EE a oa Beats 69 Memory objects variables and constants 20020 cece eeeees 71 Wordibils lt i see cree tetra ai tee doth acces nena tae a aerated es 74 Symbolized tables and indexed objects 0 02 e eee eee ee 75 SEBS es e da aan ee sear acetate eau O Aa ata 79 In rack Input Output objects 0 6 eee 81 Remote input output objects 2 2 cee eee 83 Grafcet objects sicuris Ar dt ald asics lid Glee ed be 85 Correspondences between PL7 and Unity Pro instructions 87 Ata Glance ci 2c ites id eos Olio ta at e 87 Boolean instructions
34. 7 35006148 03 October 2005 45 Correspondence between PL7 and Unity Pro 46 35006148 03 October 2005 Inter platform equivalence At a Glance Subject of this Chapter What s in this Chapter This chapter contains the hardware equivalence tables processor memory card This chapter contains the following topics Topic Page Premium processors 48 Atrium Processors 51 35006148 03 October 2005 47 Inter platform equivalence Premium processors Introduction The PL7 application converter ensures that the converted application is operational by providing a table of correspondences between the original processor and the updated processor Each processor is associated with an equivalent processor If the original processor is equipped with a memory card with or without data storage the equivalent processor will also be equipped with the same type of card except for the few specific cases indicated in the legend of the following table 48 35006148 03 October 2005 Inter platform equivalence Processor Equivalence The following table indicates the equivalence between original processors and updated processors Original processor Processor upgrade to be performed using PL7 V4 Updated processor Action performed TSX P57 10 102 TSX P 57103 1 TSX P57 104 Processor replaced T PMX P57 10 10
35. Ask your customers to convert their applications from PL7 to Unity Pro Convert your DFBs with the code and protect them Send them to your customers NN QO oy A Ask your customers to update the unprotected DFBs with the protected DFBs containing the code 36 35006148 03 October 2005 Conversion of a PL7 DFB Procedure for importing a PL7 DFB into Unity Pro Introduction When a PL7 DFB is converted into Unity Pro you must manually launch the import and analysis operations that follow conversion Import The following table describes the procedure for initializing the import and analysis of procedure a PL7 DFB converted into Unity Pro Step Action 1 Open a Unity Pro application 2 Select the Import command from the File menu 3 Select the hard disk and or directory containing the file to be imported 4 Select the file to be imported The name of this file then appears in the File name field 5 Confirm with Open which launches the import procedure When the screen indicating the end of the import procedure is displayed select the Analyse command from the Build menu which launches the analysis procedure 7 Should any conversion errors occur the output window See End of the analysis procedure p 42 is displayed on the screen allowing you to correct them 35006148 03 October 2005 37 Conversion of a PL7 DFB Results of the PL7 DFB con
36. B The following table describes any correspondence and differences between PL7 and Unity Pro objects PL7 Unity Pro Status Syntax Type of Syntax 1 Type of data data PL7_3 Timer 2 STi T dent EFB PL7_TIMER Modified current value word Ti V WORD dent ET INT preset value word STi P WORD dent PT INT elapsed timer bit Ti D BOOL dent D BOOL current timer bit STi R BOOL dent R BOOL PL7 Timers 2 STMi TM dent EFB PL7_TON Modified PL7_TOF PL7_TP current value word STMi V WORD dent ET INT preset value word STMi P WORD dent PT INT current timer bit STMi Q BOOL dent Q BOOL Monostable 2 SMNi M dent EFB Modified PL7_MONOSTABLE current value word SMNi V WORD dent ET INT preset value word SMNi P WORD dent PT INT current timer bit SMNi R BOOL dent R BOOL Up down counter SCL C dent EFB PL7_COUNTER Modified current value word Ci V WORD dent Cv INT preset value word Ci P WORD dent PV INT upcounting overrun bit Ci E BOOL dent E BOOL standby preset bit Ci D BOOL dent D BOOL downcounting overrun bit Ci F BOOL dent F BOOL 35006148 03 October 2005 79 Correspondences between common language elements PL7 Unity Pro Status Syntax Type of Syntax 1 Type of data data Register SRL R dent EFB Modified PL7_REGISTER_32 PL7_REGISTER_255 input word SRi I WORD dent INW INT output word SRLi O
37. B_DT SUB_DT_PL7 Modified 1 DAY_OF_WEEK DAY_OF_WEEK Converted TRANS_TIME TRANS_TIME Converted DATE_TO_STRING DATE_DINT_TO_STRING Modified 1 TOD_TO_STRING TOD_DINT_TO_STRING Modified 1 DT_TO_STRING DT_ARINT_TO_STRING Modified 1 TIME_TO_STRING TIME_DINT_TO_STRING Modified 1 SCHEDULE SCHEDULE Converted Legend 1 The function name is modified but the operation remains the same 108 35006148 03 October 2005 Correspondences between common language elements Exchange Instructions Introduction Instruction List Conversion replaces the PL7 instructions by their Unity Pro equivalent The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status EF READ_STS READ_STS Modified 1 WRITE_CMD WRITE_CMD Modified 1 READ_PARAM READ_PARAM Modified 1 WRITE_PARAM WRITE_PARAM Modified 1 RESTORE_PARAM RESTORE_PARAM Modified 1 SAVE_PARAM SAVE_PARAM Modified 1 SMOVE SMOVE Modified 1 XMOVE XMOVE Modified 1 LXM_SAVE LXM_SAVE Modified 1 2 LXM_RESTORE LXM_RESTORE Modified 1 Key 1 The function is replaced by an EF The parameters are entered between brackets example READ _STS CHO 4 0 2 The order of the function parameters has been modified See Process control Other and Communication instructions p 165 35006148 03 October 2005 109
38. EFB has an extra output parameter compared with its PL7 equivalent This parameter contains the value of the current step Henceforth the values of the current step are assigned in the user program to DRUM output objects Example in structured text RESET DRi is replaced by RESET PL7 DRUM DRi WORD TO BIT INT TO WORD DRi W SM4 02 3 04 5 SM6 ror np nr hr nr nr ro noe r Note in the case of converting the ladder language if the network including the call to DRUM contains the output objects of this DRUM an error message is displayed If these objects are assigned in the network you must modify the program manually using the Converror message See Convertor message in the analysis procedure p 43 in the output window 35006148 03 October 2005 167 Differences between common language elements 168 35006148 03 October 2005 Differences between Structured Text language elements 1 5 At a Glance Subject of this Chapter What s in this Chapter This chapter describes the main differences between Structured Text language elements This chapter contains the following sections Section Topic Page 15 1 Differences between PL7 and Unity Pro Structured Text 170 language instructions 35006148 03 October 2005 169 Differences between Structured Text language elements 15 1 Differences between PL7 and Unity Pro Struc
39. Edit menu 2 Select the Protection tab 3 In the Application field uncheck the Global application protection checkbox 4 In the Sections field check Protection deactivated 5 Confirm with OK The confirmation is only effective once the password is entered CAUTION Incomplete procedure If a PL7 application to be converted contains DFBs whose protection cannot be disabled See Disabling the protection p 33 the converter converts neither the DFB declaration nor the calls from the DFB in the application The networks containing the call from a protected DFB are not converted an error message is displayed in the output window See Convertor message in the analysis procedure p 43 In the conversion report file the list of protected DFBs whose codes have not been able to be converted is provided Failure to follow this precaution can result in injury or equipment damage Exporting the To export a PL7 application execute the following actions running PL7 V4 3 source file Step Action 1 Select the Export application command from the File menu 2 Select the disk and or directory where the file must be stored 3 Enter the file name in the Name field 4 Confirm with Save 35006148 03 October 2005 27 The conversion of a PL7 application Procedure for Converting a PL7 Application into a Unity Pro Application Introduction The PL7 application converter is built into the Unity Pro software The application to be c
40. Internal bits SMi EBOOL SMi EBOOL Converted or SMxi SMi SMW3 EBOOL SMi SMW3 EBOOL SMi SKW3 EBOOL SMi SKW3 EBOOL Mi n EBOOL Mi n EBOOL Mi L AR_X Mi L ARRAY OF EBOOL Internal words MWi WORD MWi INT Converted SMWi SMW5 WORD SMWi SMW5 INT SMWi SKW5 WORD SMWi SKW5 INT SMWi n WORD SMWi n INT SMWi L AR_W SMWi L ARRAY OF INT SMWi SMW3 L AR_W SMWi SMW3 L ARRAY OF INT SMWi SKW3 L AR_W SMWi SKW3 L ARRAY OF INT MWi n L AR_W SMWi n L ARRAY OF INT 35006148 03 October 2005 71 Correspondences between common language elements PL7 Unity Pro Status Syntax Type of Syntax Type of data data Internal double words SMDi WORD SMDi DINT Converted SMDi SMW3 DWORD mDi SMWw3 DINT SMDi SKW3 DWORD mMDi KW3 DINT MDi n DWORD MDi n DINT SMDi L AR_D SMDi L ARRAY OF DINT SMDi SMW3 L AR_D SMDi SMW3 L ARRAY OF DINT SMDi SKW3 L AR_D SMDi SKW3 L ARRAY OF DINT SMDi n L AR_D SMDi n L ARRAY OF DINT Internal reals SMFi REAL SMFi REAL Converted SMFi 2M0W3 REAL SMFi 2M0W3 REAL SMFi SKW3 REAL SMFi SKW3 REAL SMFi n REAL SMFi n REAL SMFi L AR_R SMFi L ARRAY OF REAL Constant words SKWi WORD SKWi INT Converted SKWi SMw3 WORD SKWi SMW3 INT SKWi SKW3 WORD SKWi SKW3 INT KWi n WORD KWi n INT SKWi L AR_W SKWi L ARRAY OF
41. NT Modified 2 RORD ROR_DINT Modified 2 Legend 1 Replaced by an EF whose name depends on the type of operand 2 The function name is modified but the operation remains the same 98 35006148 03 October 2005 Correspondences between common language elements Numerical conversion instructions Introduction Conversion replaces the PL7 instructions by their Unity Pro equivalent Instruction list and Unity Pro instructions The following table describes any correspondence and differences between PL7 PL7 Unity Pro Status EF BCD_TO_INT BCD_TO_INT Converted INT_TO_BCD INT_TO_BCD Converted GRAY_TO_INT GRAY_TO_INT Converted INT_TO_REAL INT_TO_REAL Converted DINT_TO_REAL DINT_TO_REAL Converted DINT_TO_DWORD DINT_TO_DWORD Converted DINT_TO_INT DINT_TO_INT Converted DINT_TO_WORD DINT_TO_WORD Converted DWORD_TO_DINT DWORD_TO_DINT Converted DWORD_TO_INT DWORD_TO_INT Converted DWORD_TO_WORD DWORD_TO_WORD Converted INT_TO_DINT INT_TO_DINT Converted INT_TO_WORD INT_TO_WORD Converted REAL_TO_DINT REAL_TO_DINT Converted REAL_TO_INT REAL_TO_INT Converted WORD_TO_DINT WORD_TO_DINT Converted WORD_TO_INT WORD_TO_INT Converted WORD_TO_DWORD WORD_TO_DWORD Converted TRUNC REAL_TRUNC_INT Modified 1 REAL_TRUNC_DINT DEG_TO_RAD DEG_TO_RAD Converted 35006148 03 October 2005 99 Correspondences between common langu
42. O_STRING Converted STRING_TO_REAL STRING_TO_REAL Converted REAL_TO_STRING REAL_TO_STRING Converted Operators gt lt lt 2 F gt Spans Converted EF FIND FIND_INT Modified 1 EQUAL_STR EQUAL_STR Converted LEN LEN_INT Modified 1 MID MID_INT Modified 2 INSERT INSERT_INT Modified 2 DELETE DELETE_INT Modified 2 CONCAT CONCAT_STR Modified 1 REPLACE REPLACE_INT Modified 2 LEFT LEFT_INT Modified 2 RIGHT RIGHT_INT Modified 2 ROUND STR_ROUND Modified 1 Legend 1 The function name is modified but the operation remains the same 2 In order to comply with the IEC standard the function name is modified and the operation stays the same except in extreme cases Refer to the documentation on these EF for further details 35006148 03 October 2005 107 Correspondences between common language elements Time management instructions Introduction Conversion replaces the PL7 instructions by their Unity Pro equivalent Instruction list and Unity Pro instructions The following table describes any correspondence and differences between PL7 PL7 Unity Pro Status EF RRTC RRTC Converted WRTC WRTC Converted PTC PTC Converted ADD_TOD ADD_TOD_PL7 Modified 1 ADD_DT ADD_DT_PL7 Modified 1 DELTA_TOD DELTA_TOD Converted DELTA_D DELTA_D Converted DELTA_DT DELTA_DT Converted SUB_TOD SUB_TOD_PL7 Modified 1 SU
43. PL7_TP Modified 1 35006148 03 October 2005 123 Correspondences between common language elements PL7 Unity Pro State SFB PL7_3 Timer TO PL7 3 Timer 1 Modified E 1 PL7 3 TIMER 1 SE T DL TB 1 mn R C T P 9999 MODIF Y SFB PL7 Monostable MNO Mn 1 Modified PL7_MONOSTABLE 1 S MN S R TB 1 mn MN P 9999 MODIF Y SFB PL7 Counter C0 Counter 1 Modified PL7 COUNTER 1 R C E s S DH sl AS C P 9999 cu cU CD MODIF Y CD SFB PL7 Register R1 R 1 Modified PL7 REGISTER 32 1 MODE LIFO i FL LEN 16 o I 0 124 35006148 03 October 2005 Correspondences between common language elements PL7 Unity Pro State SFB PL7 Drum DRO PL7 Drum 1 Modified 1 PL7_DRUM 1 R DR Fr R F TB 1 mn U LEN 16 3 Key 1 The PL7 SFBs are converted into Unity Pro EFBs 2 Depending on the register length See Types of instances p 119 can be converted into PL7 REGISTER_255 3 You must also assign the values of the current step to the DRUM output objects See Types of Unity Pro EFB instances p 167 35006148 03 October 2005 125 Correspondences between common language elements 126 35006148 03 October 2005 Correspondences
44. Printouts Animation tables Converting a PL7 application into a Unity Pro application generates certain correspondences which are described in the following paragraphs No conversion of the printed parts title pages headers and footers is possible between PL7 and Unity Pro because in PL7 no page setup file is saved on the disk after the generation of a document The animation tables are automatically converted into Unity Pro format by the PL7 application converter The list of PL7 variables contained in each animation table is replaced by the corresponding list of Unity Pro variables Note if a PL7 variable has no Unity Pro equivalent an error will be signaled in the conversion report file 35006148 03 October 2005 147 Other correspondences between PL7 and Unity Pro elements Runtime screens The animation tables are automatically converted into Unity Pro format by the PL7 application converter The list of PL7 variables contained in each runtime screen is replaced by the corresponding list of Unity Pro variables Note if a PL7 variable has no Unity Pro equivalent an error will be signaled in the conversion report file Note the files which describe the runtime screens are contained in the sub folders whose addresses are specified in the fef source file The conversion procedure from PL7 to Unity Pro maintains this structure 148 35006148 03 October 2005
45. RN RETURN Converted Legend 1 Conversion of this instruction generates an error message during the analysis phase See FOR instruction p 170 2 The instruction is replaced by an EF 3 This instruction is replaced by a section call 35006148 03 October 2005 135 Correspondences between Structured Text language elements 136 35006148 03 October 2005 Correspondences between Instruction List language 1 0 elements At a Glance Subject of this This chapter contains the tables of correspondence between Instruction List Chapter language elements The PL7 Instructions List language elements are divided into three categories e those that remain unchanged and are translated automatically status converted e those that have a Unity Pro equivalent and are translated automatically status modified e those that have no Unity Pro equivalent status deleted Note if a PL7 Instruction List language element has no Unity Pro correspondence both a warning and aconversion error message are generated See Analysis p 40 What s in this This chapter contains the following sections 2 Chapter Section Topic Page 10 1 Correspondences between PL7 and Unity Pro Instruction List 138 language sequences 10 2 Correspondences between PL7 and Unity Pro Instruction List 139 language instructions 35006148 03 October 2005 137 Corr
46. V 16 controllers on a Fipio bus e using PL7 remove the ATV 16 controllers from the Fipio bus ATV 16 no longer recognized by Unity e the simulation is not possible using PL7 e export the PL7 application to obtain a new FEF file e restart the conversion opening the FEF file with Unity Pro the hardware configuration of the FEF file has CCX 17 controllers on a Fipio bus e using PL7 remove the CCX 17 controllers from the Fipio bus CCX 17 no longer recognized by Unity e the simulation is not possible using PL7 e export the PL7 application to obtain a new FEF file e restart the conversion opening the FEF file with Unity Pro the hardware configuration of the FEF file has a TSX P57 2823 or TSX P57 4823 processor e using PL7 replace the processor with one that is recognized by Unity then modify the configuration to obtain equivalent functionalities for example use a TSX P57 253 processor and ETY module to replace a TSX P57 2823 e export the PL7 application to obtain a new FEF file e restart the conversion opening the FEF file with Unity Pro the PL7 application to convert has a TSX SPY 400 simulation module or TSX ISPY 100 weighing module e using PL7 delete all the parts concerning these configuration sections etc e export the PL7 application to obtain a new FEF file e restart the conversion opening the FEF file with Unity Pro an indexed variable is used as an activation cond
47. WORD dent ouTW INT full register bit SRi F BOOL dent F BOOL empty register bit SRi E BOOL dent E BOOL Drum S DRi DR dent EFB PL7_DRUM Modified full drum bit SDRi F BOOL dent F BOOL current step SDRi S WORD dent sS INT duration word SDRi V WORD dent V INT i step states SDRi Wj WORD dent Wj INT j 0 15 Legend 1 The SFBs are replaced in Unity Pro by equivalent EFBs The PL7 application converter must therefore replace the names of the SFBs with the names of the corresponding EFBs See Correspondences between PL7 and Unity Pro SFBs p 118 2 The correspondence between PL7 and Unity Pro for the value of the basic time TB is as follows e 10ms 1 e 100 ms 2 eo 1s 4 e 1mn 8 Ident EFB instance name 80 35006148 03 October 2005 Correspondences between common language elements In rack Input Output objects Introduction Conversion replaces the PL7 objects by their Unity Pro equivalent In rack I O The following table describes any correspondence and differences between PL7 objects and Unity Pro objects PL7 Unity Pro Status Syntax Type of Syntax Type of data data Channel lo DTT scHxy 0 CHANNEL CHr m c Modified 2CH3 2 2CH0 3 2 Inputs l Module orchannel 3Ixy i ERR BOOL Ir m c ERR BOOL Modified fault 12 3 ERR 10 2 3 ERR Bit SIxy i r EBOOL Ir m c d EBOOL Modified 12 3 1 T0ie2 3 SIxy i r index EBOOL Ir m c d index EBOOL I2
48. _ARINT NOT_ARDINT Operator between two tables AND EF Modified 1 AND_ARINT AND_ARDINT OR EF Modified 1 OR_ARINT OR_ARDINT XOR EF Modified 1 XOR_ARINT XOR_ARDINT Operator between a table AND EF Modified 1 and an integer word or along AND_ARINT_INT integer word AND_ARDINT_DINT Operator between a table OR EF Modified 1 and an integer word or a long OR_ARINT_INT integer word OR_ARDINT_DINT Operator between a table XOR EF Modified 1 Legend 1 The operator is replaced by an EF which depends on the type of operand See Integer and long integer word tables logic instructions p 163 104 35006148 03 October 2005 Correspondences between common language elements Bit tables logic instructions The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status EF AND_ARX AND_AREBOOL Modified 1 NOT_ARX NOT_AREBOOL Modified 1 OR_ARX OR_AREBOOL Modified 1 XOR_ARX XOR_AREBOOL Modified 1 Legend 1 The function name is modified but the operation remains the same 35006148 03 October 2005 105 Correspondences between common language elements Floating point tables The following table describes any correspondence and differences between PL7 and Unity Pro instructions
49. age elements PL7 Unity Pro Status EF RAG_TO_DEG RAG_TO_DEG Converted CONCATW INT_AS_DINT Modified 2 DBCD_TO_DINT DBCD_TO_DINT Converted DBCD_TO_INT DBCD_TO_INT Converted DINT_TO_DBCD DINT_TO_DBCD Converted HW HIGH_INT Modified 2 INT_TO_DBCD INT_TO_DBCD Converted LW LOW_INT Modified 2 Legend 1 Replaced by an EF whose name depends on the type of operand 2 The function name is modified but the operation remains the same 100 35006148 03 October 2005 Correspondences between common language elements Table instructions Introduction Conversion replaces the PL7 instructions by their Unity Pro equivalent Integer and long integer word The following table describes any correspondence and differences between PL7 and Unity Pro instructions tables S 4 PL7 Unity Pro Status mSirucuons WORD or INT or DINT DWORD Operator between two tables Converted Operator between a table MOVE_INT_ARINT Modified 1 and an integer word or along MOVE_DINT_ARDINT integer word Operator between two tables EF Modified 2 ADD_ARINT ADD_ARDINT EF Modified 2 SUB_ARINT SUB_ARDINT EF Modified 2 MUL_ARINT MUL_ARDINT EF Modified 2 DIV_ARINT DIV_ARDINT Operator between two tables REM EF Modified 2 MOD_ARINT MOD_ARDINT Operator between a table EF Modified 2 and an integer word o
50. and Unity Pro Structured Text 135 language instructions 35006148 03 October 2005 133 Correspondences between Structured Text language elements 9 1 Correspondences between PL7 and Unity Pro Structured Text language sequences The sequences Introduction Conversion replaces the PL7 Structured Text language elements by their Unity Pro equivalent Sequences and Unity Pro Structured Text language sequences The following table describes any correspondence and differences between PL7 the sequence the sequence PL7 Unity Pro Status Label SLi Li Modified Comment Comment linked to Comment linked to Converted 134 35006148 03 October 2005 Correspondences between Structured Text language elements 9 2 Correspondences between PL7 and Unity Pro Structured Text language instructions Command instructions Introduction Instruction list Conversion replaces the PL7 Structured Text language elements by their Unity Pro equivalent The following table describes any correspondences and differences between PL7 and Unity Pro Structured Text command instructions PL7 Unity Pro Status Instructions IF IF Converted CASE CASE Converted WHILE WHILE Converted REPEAT REPEAT Converted EXIT EXIT Converted FOR FOR Modified 1 HALT HALT Modified 2 JUMP JUMP Converted SRi SRi Modified 3 RETU
51. by the sequence RRE indicating that the size of the zone is insufficient to display the value in its entirety You must then either resize the display zone of the text or lower the size of the font used 35006148 03 October 2005 173 Different display in runtime screens 174 35006148 03 October 2005 Appendices At a Glance Subject of this Appendix What s in this Appendix This appendix presents the solutions to the different problems most commonly met when converting PL7 applications into Unity Pro The appendix contains the following chapters Chapter Chapter Name Page A Recommendations 177 35006148 03 October 2005 175 Appendices 176 35006148 03 October 2005 Recommendations A Recommendations during conversion Ata Glance When converting PL7 applications certain cases have been identified in which manual solutions are required These are described in this appendix CAUTION Control loop variables are not recovered by PL7 If you are using control loops parametered using PL7 variables MW MF in the FEF file to be converted you must enter them again using Unity Pro Failure to follow this instruction can result in injury or equipment damage 35006148 03 October 2005 177 Recommendations What to do when the conversion fails The following table shows the procedure when the conversion fai
52. ciple technical aspects 19 Conversion to Unity V2 0 22 35006148 03 October 2005 13 Overview Overview of the PL7 Applications Converter General Points Conversion Principle The PL7 application conversion tool is integrated into Unity Pro and enables PL7 applications to be converted into Unity Pro applications In order to perform a conversion you first need to e update the application to PL7 V4 3 e unprotect where necessary the application as well as all sections functional modules and DFBs e export and save the source file Note The PL7 Micro applications are not converted The PL7 application converter transforms the source files exported by PL7 V4 3 into Unity Pro source files Conversion stops automatically if the source file is from a earlier version of PL7 than 4 0 or if the configuration has not been exported See Software Applications p 17 version earlier than V4 3 Conversion is e called automatic when a complete application is converted e called semi automatic when one or more DFBs are converted If the conversion is automatic the software generates a source file that can be directly analyzed using Unity Pro The application is imported automatically after the Unity Pro project analysis is manually started the output window See Convertor message in the analysis procedure p 43 containing the list of conversion errors is displayed on the screen If th
53. cks Introduction Operate and compare blocks The conversion replaces the PL7 ladder language elements with their Unity Pro equivalent The following table describes the correspondence and possible differences between PL7 and Unity Pro ladder language graphic objects PL7 Unity Pro State Graphical representation Graphical representation Operate block Modified 1 m OPERATE m OPERATE ST expression ST expression Horizontal Converted compare block m COMPARE m COMPARE ST expression STexpression Vertical compare EF Modified 2 block m COMPARE EN gt variable tb variable lt bh lt gt A semi colon is added to the end of the ST expression The operate block is replaced by an EF 35006148 03 October 2005 131 Correspondences between ladder language elements Conversion restrictions PL7 ladder language Conversion of blocks The blocks in Unity Pro ladder language are taller than the blocks in PL7 ladder language The PL7 application converter automatically reorganizes the height of the blocks to guarantee that the application works correctly However if a block is embedded between two outputs of another block the procedure for converting the application e clears the network e displays a Converror message See Convertor mes
54. cribed in the following paragraphs MPS MRD MPP The instructions MPS MRD and MPP do not exist in Unity Pro The PL7 application instructions converter replaces these instructions with variables adapted to the environment For each module of a PL7 application in which an MPS MRD or MPP instruction appears the converter declares a 8 BOOL table and an INT type index simulating the behavior of the instruction to be replaced Note before replacing MPS MRD and MPP instructions the PL7 applications converter verifies that the names of the created variables have not already been used in the application 172 35006148 03 October 2005 Different display in runtime screens 1 7 Runtime screens Introduction Converting a PL7 application into a Unity Pro application generates certain differences which are described in the following paragraphs Runtime screens The display format of the values of text objects Binary and Hex have been modified in the Runtime Screen tool The new format is identical to the one used in all other tools of Unity Pro animation tables and language editors Example The WORD type variable 0 in binary format 2 0000000000000000 is converted into 2 0000 0000 0000 0000 The PL7 applications to be converted may therefore show display errors If the display zone has been adjusted to the maximum size of the text in animation running Unity Pro the value of the variable will be replaced
55. ctions PL7 Unity Pro Status Floating point REAL Operator Converted Converted 7 j Converted Converted EF SQRT SQRT_REAL Modified 1 ABS ABS_REAL Modified 1 ACOS ACOS_REAL Modified 1 ASIN ASIN_REAL Modified 1 ATAN ATAN_REAL Modified 1 COS COS_REAL Modified 1 EXP EXP_REAL Modified 1 EXPT EXPT_REAL Modified 1 LN LN_REAL Modified 1 LOG LOG_REAL Modified 1 SIN SIN_REAL Modified 1 TAN TAN_REAL Modified 1 Operator Converted Legend 1 The function name is modified but the operation remains the same 35006148 03 October 2005 95 Correspondences between common language elements Logic instructions Introduction Integer words Long integer words Conversion replaces the PL7 instructions by their Unity Pro equivalent The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status WORD INT Operator AND AND Converted OR OR Converted XOR XOR Converted NOT NOT Converted The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status DWORD DINT Operator AND AND Converted OR OR Converted XOR XOR Converted NOT NOT Converted 96 35006148 03 October 2005 Correspondence
56. d XOR XOR Converted Converted N N Converted R RESET Modified 1 S SET Modified 1 MPS MRD MPP Modified 2 Legend 1 These instructions are replaced by an EF See Unity Pro Standard Block Library Manual Logic family 2 The instructions MPS MRD and MPP do not exist in Unity Pro See MPS MRD MPP instructions p 172 35006148 03 October 2005 141 Correspondences between Instruction List language elements Instruction List language extensions Introduction IL extensions In Unity Pro the operation and comparison blocks of Instruction List language written in Structured Text language are not converted The following table describes the Instruction List language extensions which have no Unity Pro equivalents PL7 Unity Pro Status OF Deleted 1 MASKEVT UNMASKEVT expression Legend 1 It is necessary to manually replace this part of the application 142 35006148 03 October 2005 Correspondences between Grafcet language elements 11 Ata Glance Aim of this section What s in this Chapter This section contains the tables showing correspondence between Grafcet language elements This chapter contains the following topics Topic Page Grafcet instructions 144 Conversion restrictions PL7 Grafcet language 145 35006148 03 October 2005 143 Corres
57. dence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status EF FCT_ACCEPT Deleted FCT_BIND Deleted FCT_LISTEN Deleted FCT_RECEIVE Deleted FCT_SELECT Deleted FCT_CONNECT FCT_CONNECT Converted FCT_SEND Deleted FCT_SHUTDOWN Deleted FCT_SOCKET Deleted FCT_SETSOCKOPT Deleted The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status EF FCT_ACCEPT_DFB FCT_ACCEPT Modified 1 FCT_BIND_DFB FCT_BIND Modified 1 FCT_LISTEN_DFB FCT_LISTEN Modified 1 FCT_RECEIVE_DFB FCT_RECEIVE Modified 1 FCT_SELECT_DFB FCT_SELECT Modified 1 FCT_SEND_DFB FCT_SEND Modified 1 FCT_SHUTDOWN_DFB FCT_SHUTDOWN Modified 1 FCT_SOCKET_DFB FCT_SOCKET Modified 1 FCT_SETSOCKOPT_DFB FCT_SETSOCKOPT Modified 1 Legend 1 The function name is modified but the operation remains the same 114 35006148 03 October 2005 Correspondences between common language elements Diagnostics instructions Introduction Instruction list Conversion replaces the PL7 instructions by their Unity Pro equivalent The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status EF DEREG DEREG Converted REGDFB REGDFB Modified 1 REGIO Deleted Lege
58. dified 4 LENGTH_ARW LENGTH_ARINT Modified 4 MAX_ARD MAX_ARDINT Modified 4 MAX_ARW MAX_ARINT Modified 4 MIN_ARD MIN_ARDINT Modified 4 MIN_ARW MIN_ARINT Modified 4 OCCUR_ARD OCCUR_ARDINT Modified 4 OCCUR_ARW OCCUR_ARINT Modified 4 ROL_ARD ROL_ARDINT Modified 4 ROL_ARW ROL_ARINT Modified 4 ROR_ARD ROR_ARDINT Modified 4 ROR_ARW ROR_ARINT Modified 4 SORT_ARD SORT_ARDINT Modified 4 SORT_ARW SORT_ARINT Modified 4 Legend 1 The operator is replaced by an EF which depends on the type of operand 2 The operator is replaced by an EF which depends on the type of operand See Integer and long integer word tables instructions p 163 3 Replaced by an EF whose name depends on the type of operand 4 The function name is modified but the operation remains the same 5 The function name is modified but the operation remains the same except in the case of negative ranks See Tables functions p 164 35006148 03 October 2005 103 Correspondences between common language elements Integer and long integer word tables logic instructions The following table describes any correspondence and differences between PL7 and Unity Pro instructions and an integer word or along integer word XOR_ARINT_INT XOR_ARDINT_DINT PL7 Unity Pro Status WORD or INT or DINT DWORD Operator NOT EF Modified 1 NOT
59. e conversion is semi automatic the converter generates a source file anda conversion report file In order for the contents of the converted source file to be usable it needs to be imported manually into an application Following this import the output window See Convertor message in the analysis procedure p 43 containing the list of conversion errors is displayed on the screen WARNING Note The PL7 application converter translates the application but does not guarantee its correct operation Failure to follow this precaution can result in death serious injury or equipment damage 14 35006148 03 October 2005 Overview Conversion Principle General Points Introduction The PL7 application converter is used to convert e acomplete PL7 application This procedure is called automatic e a PL7 DFB This procedure is called semi automatic Automatic The procedure for converting a PL7 application into a Unity Pro is as follows Conversion PL7 application gt fef source file Unity Pro application xef source file Unity Pro Application in memory The fef PL7 source file is converted into a xef Unity Pro source file then imported and analyzed automatically in the Unity Pro project The analysis phase must be started manually in order to detect any conversion errors and display them on the screen in the form of an output window At the end of the procedure
60. e eee Correspondences between ladder language elements Ata Glance sca vices Yea A eee kth alien wae AT pon ean es The definition of a ladder network 0 2 00 0 cee eee TNE TUN titi Sawa A alien ete es COIS 252 suites 4 ee ei eatin RSet hal eA Rae eg a a Operate and compare blocks 00 00 cece eee tees Conversion restrictions PL7 ladder language 0 0 eee eens Correspondences between Structured Text language elements 00 eee e eee eee eee eee Ata Glance iii a a coe AM ale wee ee Correspondences between PL7 and Unity Pro Structured Text language SEQUENCES xis coed wealth da deed ata kee pe verte ETA ares The SOQUENGES v 08 sa eyed ee ia eet Se ay Correspondences between PL7 and Unity Pro Structured Text language INSTUCIONS 2 2 2 cree eS ieee a eA ated ed eee nde a eee ee eat a e Command instructions 0 000 c cette eee Correspondences between Instruction List language elements 0 0 0c c ence eee eee eens Ata Glance ia A ae i Ge ee De E e Correspondences between PL7 and Unity Pro Instruction List language sequences shee Behr a da eet The SOQUENCES cio Seal cea AA A Correspondences between PL7 and Unity Pro Instruction List language INST CIONS asi siria di eee cs hes eee Ai 35006148 03 October 2005 Chapter 11 Chapter 12 Part IV Chapter 13 13 1 Chapter 14 14 1 14 2 14 3 14 4 Chapter 15 15 1 Ata G aNCe fase rice ned oe eee a
61. ee Correspondences between PL7 and Unity Pro instructions p 87 35006148 03 October 2005 155 Differences between common language elements Operations between mixed types Introduction Words and double words Tables and double words Assignment of tables Converting a PL7 application into a Unity Pro application generates certain differences which are described in the following paragraphs Operations between different object types are not possible in Unity Pro During the conversion procedure operations of this type are detected and replaced by their corresponding EFs See Correspondences between PL7 and Unity Pro instructions p 87 Example MDO MD0 MWw4 is converted into SMD0 SMDO INT TO DINT MW4 Example sMw20 MD10 is converted into SMW20 DINT TO INT MD10 Operations between word tables or double word tables and words or double words are not possible in Unity Pro During the conversion procedure operations of this type are detected and replaced by their corresponding EFs See Table instructions p 101 Example MW100 20 3 MwW10 5 is converted into MOVE_INT_ARINT MW10 5 MW100 20 Example 3Mw100 20 SMW100 20 5 is converted into SMW100 20 ADD ARINT INT MW100 20 5 The assignment of a word or double word table into a bit table is not possible in Unity Pro During the conversion procedure the assignment operator is replaced by the corresponding EF
62. egative rank and the function is not executed In PL7 the function is executed from rank 0 FIND_EQP_ If the rank from which the search is launched is negative the result is equal to this negative rank and the function is not executed In PL7 the function is executed from rank 0 164 35006148 03 October 2005 Differences between common language elements Process control Other and Communication instructions Introduction Converting a PL7 application into a Unity Pro application generates certain differences which are described in the following paragraphs IN OUT INOUT parameters In Unity Pro for all EFs that use input output and input output parameters IN OUT and INOUT the order of these parameters has been modified Example in PL7 the order of the parameters is as follows IN OUT INOUT In Unity Pro this becomes IN INOUT OUT The EFs concerned by this modification are the following Process control Other instructions See Communication instructions See instructions See Other instructions Communication instructions Process control p 112 p 113 instructions p 111 PL7 Unity Pro PL7 Unity Pro PL7 Unity Pro PID PID INT FTOF FTOF DATA_EXCH DATA_EXCH PWM PWM_INT FTON FTON NPUT_CHAR NPUT_CHAR SERVO SERVO_INT FTP FTP OUT_IN_CHAR OUT_IN_CHAR SCOUNT SCOUNT PRINT_CHAR PRINT_CHAR FPULSOR FPULSOR CV_TLG CV_TLG EAD ASYN
63. en common language elements 7 2 Correspondences between PL7 and Unity Pro language objects At a Glance Subject of this This section contains the tables of correspondences between PL7 language objects Section and their Unity Pro equivalent The PL7 objects are split into three categories e those that remain unchanged and are translated automatically status converted e those that have a Unity Pro equivalent and are translated automatically status modified e those that have no Unity Pro equivalent status deleted Note if a PL7 object has no Unity Pro correspondence a warning and a conversion error message are generated See Analysis p 40 What s in this This section contains the following topics ion Section Topic Page Immediate values 65 Labels 68 System objects 69 Memory objects variables and constants 71 Word bits 74 Symbolized tables and indexed objects 75 SFBs 79 In rack Input Output objects 81 Remote input output objects 83 Grafcet objects 85 64 35006148 03 October 2005 Correspondences between common language elements Immediate values Introduction Conversion replaces the PL7 objects by their Unity Pro equivalent Immediate The following table describes any correspondence and differences between PL7 values and Unity Pro ob
64. ence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status WORD INT Operator Converted Converted l il Converted Converted REM MOD Modified 1 EF SQRT SQRT_INT Modified 2 ABS ABS_INT Modified 2 Operator INC INC_INT Modified 2 DEC DEC_INT Modified 2 Converted Legend 1 The operator name is modified but the operation remains the same 2 Replaced by an EF whose name depends on the type of data processed 35006148 03 October 2005 93 Correspondences between common language elements Long integer words The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status DWORD DINT Operator Converted Converted k y Converted Converted REM MOD Modified 1 EF SQRT SQRT_DINT Modified 2 ABS ABS_DINT Modified 2 Operator INC INC_DINT Modified 2 DEC DEC_DINT Modified 2 Converted Legend 1 The operator name is modified but the operation remains the same 2 Replaced by an EF whose name depends on the type of data processed 94 35006148 03 October 2005 Correspondences between common language elements Real words The following table describes any correspondence and differences between PL7 and Unity Pro instru
65. ences between PL7 and Unity Pro ladder language graphic objects Type of rung PL7 Unity Pro Status Graphic Graphic representation representation Direct _l _l Converted Reverse l l l Converted Rising edge P l P l Converted Falling edge N l N l Converted 35006148 03 October 2005 129 Correspondences between ladder language elements Coils Introduction Coils The conversion replaces the PL7 ladder language elements with their Unity Pro equivalent The following table describes the correspondence and possible differences between PL7 and Unity Pro graphic objects PL7 Unity Pro State Graphical Graphical representation representation Direct coil Converted Negated coil Converted Set coil S S Converted Reset coil R R Converted Jumps to a label gt gt Li gt gt Li Converted Subroutine return lt RETURN gt lt RETURN gt Converted Program halt coil lt HALT gt EF Modified 1 Coil Mame Modified 2 SR call coil C EF Modified 1 Key 1 The coil is replaced by an EF 2 The coil is replaced by a direct coil with the transition name Pame superimposed 130 35006148 03 October 2005 Correspondences between ladder language elements Operate and compare blo
66. equivalents Functional The following table describes any correspondence and differences between PL7 modules and Unity Pro functional module characteristics PL7 Unity Pro Status Functional modules Yes Yes Converted Nesting of functional modules No limitation No limitation Converted Comment 0 127 characters 0 255 characters Modified Size of description file No limitation No limitation Converted Maximum capacity Number of functional modules No limitation No limitation Converted of a functional Number of sections LD ST IL No limitation No limitation Converted module Grafcet 1 No limitation Modified 1 Number of events in a section No limitation No limitation Converted 2 Number of macro steps Limited by the None Deleted 1 processor Number of animation tables No limitation No limitation Converted Number of runtime screens No limitation No limitation Converted Legend The PL7 application converter does not convert all types of functional modules See Functional modules p 152 2 The possible programming languages are the following e LD ST IL 35006148 03 October 2005 57 Correspondence between application structures 58 35006148 03 October 2005 Correspondences between common language elements At a Glance Subject of this Chapter What s in this Chapter This chapter contains the tables of correspondences be
67. es 177 Recommendations During Conversion 0 00 eee eee eee 177 E tae eid Sark Seas Sos axle Sta Gy Steal sh aa tee ee Sov Sees Bie 183 iis nds Slee CaaS Caw eS te ede ewes ew et ett oe oe 185 35006148 03 October 2005 35006148 03 October 2005 About the Book A At a Glance Document Scope Validity Note Product Related Warnings This manual presents the PL7 application converter and describes the procedure for converting PL7 applications into Unity Pro applications It also contains correspondence tables between PL7 programming elements and those of Unity Pro programming The data and illustrations found in this documentation are not binding We reserve the right to modify our products in line with our policy of continuous product development The information in this document is subject to change without notice and should not be construed as a commitment by Schneider Electric Schneider Electric assumes no responsibility for any errors that may appear in this document If you have any suggestions for improvements or amendments or have found errors in this publication please notify us No part of this document may be reproduced in any form or by any means electronic or mechanical including photocopying without express written permission of Schneider Electric All pertinent state regional and local safety regulations must be observed when installing and using this product For reasons
68. espondences between Instruction List language elements 10 1 Correspondences between PL7 and Unity Pro Instruction List language sequences The sequences Introduction Sequences Conversion replaces the PL7 Instruction List language elements by their Unity Pro equivalent The following table describes any correspondence and differences between PL7 and Unity Pro Instruction List language sequences the sequence the sequence PL7 Unity Pro Status Label SLi Li Modified Comments Comments linked to Comments linked to Converted 138 35006148 03 October 2005 Correspondences between Instruction List language elements 10 2 Correspondences between PL7 and Unity Pro Instruction List language instructions At a Glance Subject of this This section contains the tables of correspondence between PL7 Instruction List Section language instructions and their Unity Pro equivalent What s in this This section contains the following topics ion Section Topic Page Command instructions 140 Boolean instructions 141 Instruction List language extensions 142 35006148 03 October 2005 139 Correspondences between Instruction List language elements Command instructions Introduction Instruction list Conversion replaces the PL7 Instruction List language elements by their Unity Pro equivalent The following table describes a
69. etween common language elements Bit table instructions Introduction Conversion replaces the PL7 instructions by their Unity Pro equivalent Instruction list The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status Operator between two Converted bit tables Operator between a bit MOVE_INT_AREBOOL Modified 1 table and an integer or MOVE_DINT_AREBOOL long integer word Operator between an MOVE_AREBOOL_INT Modified 1 integer or long integer MOVE_AREBOOL_DINT word and a bit table EF BIT_D COPY_AREBOOL_ARDINT Modified 2 BIT_W COPY_AREBOOL_ARINT Modified 2 COPY_BIT COPY_AREBOOL_AREBOOL Modified 2 D_BIT COPY_ARDINT_AREBOOL Modified 2 LENGTH_ARX LENGTH_AREBOOL Modified 3 W_BIT COPY_ARINT_AREBOOL Modified 2 Legend 1 The operator is replaced by an EF which depends on the type of operand 2 The function name is modified but the operation remains the same except in the case of negative ranks See Tables functions p 164 3 The function name is modified but the operation remains the same 92 35006148 03 October 2005 Correspondences between common language elements Arithmetic instructions Introduction Integer words Conversion replaces the PL7 instructions by their Unity Pro equivalent The following table describes any correspond
70. gend 1 Processors that do not accept 160K word cards Using PL7 57 1 type processors do not accept memory cards greater than 64K words 2 These processors require two slot spaces whereas the initial processors using PL7 require only one Note Processors TSX P57 2823 and TSX P57 4823 are not converted You must therefore adapt your configuration using PL7 in order to convert it into Unity Pro 35006148 03 October 2005 49 Inter platform equivalence Memory card For all processors except those indicated 1 in the above table the cartridge equivalence correspondence is as follows Memory card using PL7 Corresponding memory card using Unity Pro None None 32 K words 96 K bytes 64 K words 192 K bytes 128 K words 384 K bytes 128 K words Storage 768 K bytes 160 K words 448 K bytes 160 K words Storage 1000 K bytes 256 K words 768 K bytes 256 K words Storage 2000 K bytes 384 K words 2000 K bytes 512 K words Storage 2000 K bytes 50 35006148 03 October 2005 Inter platform equivalence Atrium Processors Introduction The PL7 application converter ensures that the converted application is operational by providing a table of correspondence between the original processor and the updated processor Each processor is associated with an equivalent processor If the original processor is equipped with a mem
71. h versions V4 0 V4 1 and V4 2 35006148 03 October 2005 17 Overview Processors WARNING The conversion of complete applications or DFB using a version of PL7 earlier than PL7V4 3 is performed under your complete responsibility Failure to follow this precaution can result in death serious injury or equipment damage Sometimes the conversion procedure requires the size of the converted application to be increased By default the PL7 application converter automatically updates the processor memory card configuration and proposes an equivalent configuration See Inter platform equivalence p 47 However this default selection may be modified Note All PL7 applications earlier than version V4 0 must be updated For applications managed by the following processors the update procedure involves the compulsory replacement of the processor e Premium processor See Premium processors p 48 TSX P57 0 TSX P57 ee2 or T PMX P57 e2 e Atrium processor See Atrium processors p 51 T PCX 57 eee2 18 35006148 03 October 2005 Overview Conversion principle technical aspects Introduction The PL7 application converter is used to convert e acomplete PL7 application the procedure is automatic e aPL7 DFB the procedure is semi automatic Automatic The following diagram shows the technical aspects of the conversion procedure for conversion a comple
72. iagrams in Unity Pro SFC language SFC language The corresponding Unity Pro SFC language has a single programming page with a maximum of 200 lines In the rare cases when the Grafcet programming exceeds this limits a Converror message See Convertor message in the analysis procedure p 43 will be displayed in the output window 35006148 03 October 2005 145 Correspondences between Grafcet language elements Link from bottom In Unity Pro SFC language it is not possible to have several links going towards the to top same connector The PL7 application converter automatically replaces this configuration with an equivalent Unity Pro configuration However it is impossible in SFC language to have a link from bottom to top If your PL7 application to be converted contains this type of link you must manually complete the diagram using the Converror message See Convertor message in the analysis procedure p 43 that is displayed in the output window The following screen gives an example of a link from bottom to top drawn up in PL7 Grafcet language this part of the program cannot be automatically converted EA GRAFCET MAST G7_test Chart a a from the low gt converror rt lall al Bis All el El 146 35006148 03 October 2005 Other correspondences between PL7 and Unity Pro elements 1 2 Printouts animation tables and runtime screens Introduction
73. ition using Unity Pro write the missing condition without using indexed variables 35006148 03 October 2005 Recommendations What to do when the generation of the project fails The following table describes the procedure when the Unity Pro generation phase fails If in the generation report one of the following cases appears Then a section written in ST language has a truncated line e using Unity Pro correct the faulty line return generated during editing the ST editor does not authorize lines of over 300 characters e generate the project again an error occurs on a macro step bit e using Unity Pro check that the macro step is declared using PL7 it is possible to use a macro step bit without it being declared e if this is the case correct the program accordingly e generate the project again an error on input or output type objects Q1 2 48 16 for example is generated e check that these objects are configured using PL7 e if this is not the case correct the program accordingly e generate the project again an error on FIPIO objects IW 2 80 0 0 0 3 for example is generated e check that these objects are configured using PL7 e if this is not the case correct the program accordingly e generate the project again e if you are using ADM 390 10 modules it is no longer possible to use FIPIO objects under Unity Pro an error in the system
74. jects PL7 Unity Pro Status Syntax Type of Syntax Type of data data Boolean FALSE TRUE BOOL 0 1 or FALSE TRUE BOOL Converted Decimal integer base 1234 WORD 1234 INT Converted 10 Long decimal integer 123456 DWORD 123456 DINT Converted base 10 Base 2 integer 2HX WORD If 2 x 2HX INT Modified 1 16 figures lt 32767 If 2 x decimal value gt 32767 1 Base 2 long integer 2 x DWORD If2 x 2 x DINT Modified 17 32 figures lt 2147483647 If 2 x decimal value gt 2147483647 1 Base 16 integer 16 x WORD Iflo x 2 x INT Modified 1 4 figures lt 32767 If1l6 x decimal value gt 32767 1 Base 16 long integer 16 x DWORD If16 x 2 x DINT Modified 5 8 figures lt 2147483647 If 16 x decimal value gt 2147483647 1 Real 1 32e 12 REAL 1 32e 12 REAL Converted Character string aAbBcC STRING aAbBcC STRING Converted Network address ADR 2 AR_W 6 ADDR 2 ARRAY Modified OF INT Legend 1 This decimal value may be negative if the sign bit is equal to 1 See Integer and long integer words p 158 2 See table below 35006148 03 October 2005 65 Correspondences between common language elements Network address The following table describes any correspondence and differences between PL7 and Unity Pro network address objects
75. llowing topics Topic Page Types and tables 155 Operations between mixed types 156 154 35006148 03 October 2005 Differences between common language elements Types and tables Introduction Converting a PL7 application into a Unity Pro application generates certain differences which are described in the following paragraphs Types WORD and DWORD types exist in Unity Pro but do not make it possible to carry out arithmetic operations Arithmetic and logic operations are performed in Unity Pro with INT and DINT type objects For this reason the PL7 converter converts WORD or DWORD type objects into INT or DINT type objects Example The SHL operation on WORD or DWORD type objects is converted into SHL_INT or SHL_DINT See Correspondences between PL7 and Unity Pro instructions p 87 Tables The PL7 converter modifies the syntax of the declaration in the tables Boolean word double word floating point and byte tables Example ARRAY1 M1 10 is converted intoARRAY1 ARRAY 0 9 OF BOOL Note in Unity Pro elements keep the same name as in PL7 example ARRAY 1 Specific types WORD words and DWORD double words in TIME DATE TOD and DT formats and tables are converted into INT and DINT Example MD10 ADD_TOD MD20 MD30 is converted into 2MD10 ADD_TOD_PL7 MD20 MD30 Time management EFs in PL7 are converted into their corresponding EFs in Unity Pro S
76. ls just after opening unknown hardware configuration the FEF file If Then an error message appears consult the report file to obtain additional information in the report file the error concerns an e open the STX file using version 4 3 of PL7 modify the processor version export the PL7 application to obtain a new FEF file restart the conversion opening the FEF file with Unity Pro in the report file the error concerns the name of acharacter string longer than 32 characters using PL7 modify the name of the variable to lower the size to under 32 characters export the PL7 application to obtain a new FEF file restart the conversion opening the FEF file with Unity Pro in the report file the error concerns a name conflict between variables sections etc using PL7 modify the names or symbols concerned export the PL7 application to obtain a new FEF file restart the conversion opening the FEF file with Unity Pro the FEF file was created with a version of PL7 previous to 4 0 open the FEF file using version 4 3 of PL7 See Conversion Principle Applications and Processors p 17 export the PL7 application to obtain a new FEF file restart the conversion opening the FEF file with Unity Pro the FEF file was created with a 4 0 4 1 or 4 2 version of PL7 open the FEF file using version 4 3 of PL7 See Conversion Principle Applications and Processors p 17 expor
77. ments Communication instructions Introduction Instruction list Conversion replaces the PL7 instructions by their Unity Pro equivalent The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status EF CALL_MODEM CALL_MODEM Converted CANCEL CANCEL Converted DATA_EXCH DATA_EXCH Modified 1 INPUT_CHAR INPUT_CHAR Modified 1 OUT_IN_CHAR OUT_IN_CHAR Modified 1 PRINT_CHAR PRINT_CHAR Modified 1 RCV_TLG RCV_TLG Modified 1 READ_ASYN READ_ASYN Modified 1 READ_GDATA READ_GDATA Modified 1 READ_VAR READ_VAR Modified 1 ROR1_ARB ROR1_ARB Converted SEND_REQ SEND_REQ Modified 1 SEND_TLG SEND_TLG Converted SERVER UNITE_SERVER Modified 1 2 SWAP SWAP_ARINT Modified 2 WRITE_ASYN WRITE_ASYN Converted WRITE_GDATA WRITE_GDATA Converted WRITE_VAR WRITE_VAR Converted Legend 1 The order of the function parameters has been modified See IN OUT INOUT parameters p 165 2 The function name is modified but the operation remains the same 35006148 03 October 2005 113 Correspondences between common language elements TCP Open instructions Introduction Instruction list TCPIP_LEVEL1 Instruction list TCPIP_DFB Conversion replaces the PL7 instructions by their Unity Pro equivalent The following table describes any correspon
78. n are generated Conversion A txt conversion report file is generated It contains all data and warnings report relating to the conversion procedure Once conversion is complete the PL7 application converter stops The following diagram shows the technical aspects of the procedure for manually importing a converted PL7 DFB into a Unity Pro application E T Output window 20 35006148 03 October 2005 Overview The following table describes the different steps in the manual import procedure Step Description Import In order for the converted xfb source file to be exploitable by Unity Pro it must be manually imported into a Unity Pro application Analysis The imported file is analyzed by Unity Pro Any conversion errors are detected Note You must manually launch this analysis phase Output Any conversion errors are shown in the output window See End of the window analysis procedure p 42 which is automatically displayed at the end of analysis 35006148 03 October 2005 21 Overview Conversion to Unity V2 0 At a Glance Fipio Applications Lexium EF TSX WMY 100 Module CANopen Applications The conversion of a PL7 application to a Unity Pro project may be achieved from version 4 3 of PL7 However you can convert V4 4 PL7 applications to Unity Pro V1 0 or to Unity V2 0 For the conversion of a V4 4 PL7 to Unity Pro V1 0 e Ifthe func
79. nd 1 The function interface is modified You must modify this function manually See General p 32 before launching the conversion procedure 35006148 03 October 2005 115 Correspondences between common language elements Grafcet instructions Introduction Instruction list Conversion replaces the PL7 instructions by their Unity Pro equivalent The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status EF RESET_XIT Deleted 116 35006148 03 October 2005 Correspondences between common language elements Human Machine Interface HMI instructions Introduction Instruction list Conversion replaces the PL7 instructions by their Unity Pro equivalent The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status EF ADJUST No equivalent Deleted ASK_MSG ASK_VALUE ASSIGN_KEYS CONTROL_LEDS DISPLAY_ALRM DISPLAY_GRP DISPLAY_MSG GET_MSG GET_VALUE PANEL_CMD SEND_ALARM SEND_MSG 35006148 03 October 2005 117 Correspondences between common language elements 7 4 Correspondences between PL7 and Unity Pro SFBs At a Glance Aim of this sub In Unity Pro SFBs are replaced by equivalent EFBs state conve
80. nd Unity Pro types PL7 Unity Pro Status Type BOOL BOOL Converted EBOOL EBOOL Converted WORD INT Modified 1 DWORD DINT Modified 1 REAL REAL Converted Legend 1 The WORD and DWORD types are converted into INT and DINT types See Types p 155 The following table describes any correspondence and differences between PL7 and Unity Pro tables PL7 Unity Pro Status Table Boolean table EBOOL Mi n ARRAY 0 n 1 OF Modified 1 EBOOL Word table WORD MWi n ARRAY 0 n 1 OF Modified 1 EBOOL Table of double words DWORD ARRAY 0 n 1 OF DINT Modified 1 SMDi n Floating point table REAL 3MFi n ARRAY 0 n 1 OF REAL Modified 1 Bytes table SMBi n STRING n Modified 1 Legend 1 The converter modifies the declaration See Tables p 155 35006148 03 October 2005 61 Correspondences between common language elements Specific types The following table describes any correspondence and differences between specific and tables PL7 and Unity Pro types and tables PL7 Unity Pro Status Type The TIME DATE and TOD formats are DINT Modified 1 double words DWORD Table The DTformat is a table of 4 words ARRAY 0 3 OF INT Modified 1 SMWi 4 Legend 1 WORD and DWORD types are converted into INT and DINT types See Specific types and tables p 155
81. nd functions Introduction Integer and long integer word tables instructions Integer and long integer word tables logic instructions Converting a PL7 application into a Unity Pro application generates certain differences which are described in the following paragraphs The operators REM between two integer and long integer word tables have been deleted in Unity Pro The PL7 application converter replaces these operators with EF equivalents See Integer and long integer word tables instructions p 101 Example TABINT1 TABINT2 TABINT3 are integer tables TABINT1 TABINT2 TABINT3 is replaced with TABINT1 ADD_ARINT TABINT2 TABINT3 The operators REM between a table and an integer or long integer word have been deleted in Unity Pro The PL7 application converter replaces these operators with EF equivalents See Integer and long integer word tables instructions p 101 A single EF is used for each switching operator Example INT1 is an integer TABINT1 and TABINT2 are integer tables Both TABINT1 INT1 TABINT2 and TABINT1 TABINT2 INT1 are replaced with TABINT1 ADD ARINT_ INT TABINT2 INT1 The operators AND OR XOR NOT between two integer and long integer word tables have been deleted in Unity Pro The PL7 application converter replaces these operators with EF equivalents See Integer and long integer word tables logic instructions p 104 Example
82. nity Pro objects PL7 Unity Pro Status Syntax Syntax Remote AS i bus SI xy 0 n i I b e r m c Modified objects 11104 012 3 I 15 2 0 0 3 1 Legend 1 In Unity Pro the bus identifier has been added In order to convert remote AS i bus objects the selected b identifier corresponds to the number of the xy rack module PL7 Unity Pro x E Rack y m Position in the rack AS i channel the module TSX SAY 100 has only one channel n e Slave number i c Channel b Bus identifier 84 35006148 03 October 2005 Correspondences between common language elements Grafcet objects Introduction Conversion replaces the PL7 objects by their Unity Pro equivalent Grafcet objects The following table describes any correspondence and differences between PL7 and Unity Pro objects PL7 Unity Pro Status Syntax Type of data Syntax Type of data Grafcet objects Xi BOOL X dox SFCSTEP_STATE Modified 1 XMj XM j x Xj i KJER Xj IN X_j_IN x Xj OUT X_j_OUT x Grafcet objects Xi T WORD X i t SFCSTEP_STATE Modified 1 XMj T XM j t 3X3 1 T XM_j_ i t 2 X3 IN T XM_j_IN t Xj OUT T XM_j_OUT t Legend 1 PL7 steps and macrosteps become in Unity Pro structured objects SFCSTEP_STATE For the activity times of the steps we advise you to check your program in order to use the TIME type instead of the a whole val
83. ny correspondences and differences between PL7 and Unity Pro Instruction List command instructions PL7 Unity Pro Status Instructions HALT HALT Modified 1 HALTC ST ACCU Modified HALT EN ACCU HALTCN STN ACCU Modified HALT EN ACCU END END Modified 1 ENDC ST ACCU Modified END EN ACCU ENDCN STN ACCU Modified END EN ACCU JMP JMP Converted JMPC JMPC Converted JMPCN JMPCN Converted RET RET Converted RETC RETC Converted RETCN RETCN Converted SRi CAL SRi Modified 2 NOP Deleted Edge management 3 F FE Modified R RE Modified Legend 1 The instruction is replaced by an EF 2 This instruction is replaced by a conditional section call 3 In Unity Pro edges are managed by EFs 140 35006148 03 October 2005 Correspondences between Instruction List language elements Boolean instructions Introduction Conversion replaces the PL7 Instruction List language elements by their Unity Pro equivalent Instruction list The following table describes any correspondences and differences between the Boolean instructions of PL7 and Unity Pro Instruction List language PL7 Unity Pro Status Instructions LD LD Converted LDF LDF Converted LDN LDN Converted LDR LDR Converted ST ST Converted STN STN Converted AND AND Converted OR OR Converte
84. ociated with each indexed symbolized object See Symbolized indexed objects p 161 2 The table is declared from 0 NbMaxMW i 1 its type and location depending on the address Example sMwi j declared in PL7 as TABA 3 in converted into TABA_AR j TABA_AR j is therefore a declared table from 0 NbMaxMW i 1 of type INT located at smwi and with the same comment as TABA 35006148 03 October 2005 77 Correspondences between common language elements Indexed I O The following table describes any correspondence and differences between PL7 objects and Unity Pro symbolized indexed input output objects PL7 Unity Pro Status Address Associated Address Associated symbol 1 variable Indexed I O SI j TABA 3 SI 3 Modified objects SIWO j TABB j zwe j l SQ 5 TABC 3 SQ 5 s SQWe 3 TABD j sQWG 3 Legend Addressing of the in rack See In rack Input Output objects p 81 and or remote See Remote input output objects p 83 input output objects 1 Indexed input output objects are converted into their non symbolized form address See Symbolized indexed objects p 161 78 35006148 03 October 2005 Correspondences between common language elements SFBs Introduction Conversion replaces the PL7 objects by their Unity Pro equivalent SF
85. omment associated with the first element of a table from MB or from KB the converter declares a character string of length 1 and associates the comment with this example TABLE symbol of 3MB500 20 This is the TABLE comment is converted to TABLE 1 STRING 1 This is the TABLE comment 35006148 03 October 2005 159 Differences between common language elements Word bits Introduction Converting a PL7 application into a Unity Pro application generates certain differences which are described in the following paragraphs Extracted bit In order to avoid any conflicts of syntax in the PL7 user applications to be converted the Unity Pro syntax for extracted bits has been modified The PL7 syntax for the extracted bit xi is therefore replaced with Unity Pro syntax FAs Example 1W12 3 1 X5 is converted into 1W12 3 1 5 The Unity Pro syntax for the extracted bit on the rank O object is as follows 1W12 3 0 5 160 35006148 03 October 2005 Differences between common language elements Symbolized tables and indexed objects Introduction Symbolized tables Symbolized indexed objects Converting a PL7 application into a Unity Pro application generates certain differences which are described in the following paragraphs In Unity Pro you can associate a symbol with a simple object but cannot use the same symbol to refer to a table Example if sMwi is symbolized
86. ommon language elements Call of an SFB in structured text Introduction The conversion automatically replaces SFBs with equivalent EFBs insofar as these exist Call of an SFB in The following table describes the correspondence and possible differences between ST SFBs and EFBs PL7 Unity Pro State SFB T START STi START PL7_3 TIMER Ti Converted STOP Ti STOP PL7 3 TIMER Ti PRESET Ti PRESET PL7 3 TIMER Ti SFB TM TON START TMi START_PL7_ TON TMi Converted DOWN TMi DOWN _PL7_TON TMi TOF START TMi START_PL7_TOF TMi DOWN TMi DOWN_PL7_TOF TMi TP START TMi START_PL7_TP TMi DOWN TMi DOWN_PL7_TP TMi SFB 3c RESET Ci RESET PL7 COUNTER Ci Converted PRESET Ci PRESET PL7 COUNTER Ci UP Ci UP_PL7_COUNTER Ci DOWN Ci DOWN PL7_ COUNTER Ci SFB 3MN START MNi START_PL7_MONOSTABLE MNi Converted SFB R SRi L lt 32 RESET Ri RESET PL7 REGISTER 32 Ri Converted PUT SRi PUT_PL7_REGISTER_32 Ri GET Ri GET_PL7 REGISTER _32 Ri 32 lt Ri L lt 255 RESET Ri RESET PL7 REGISTER 255 Ri PUT Ri PUT_PL7 REGISTER _255 Ri GET SRi GET_PL7_ REGISTER 255 Ri SFB DR RESET DRi RESET PL7_ DRUM DRi Converted WORD_TO BIT INT_TO WORD DRi W list of 16 DRUM output objects 1 UP SDRi UP_PL7_DRUM DRi WORD_TO_BIT INT_TO WORD DRi W li
87. on of a complete application fef associates an equivalent to the old processor Software The conversion of a complete application is called automatic Applications At the end of conversion and after a manual analysis is started the user has e asource file that is directly exploitable by Unity Pro e a Unity Pro application in memory e aconversion report file including all data warnings and errors relating to the conversion e an output window containing the list of conversion errors Note The recommended version of PL7 is V4 3 However you may under your own responsibility convert the exported applications with versions V4 0 V4 1 and V4 2 if the hardware configuration has been explicitly exported in the FEF file To export the hardware configuration you must modify the PL7SYS INI file located in the WINNT or Windows folder on your PC This file must contain the following two lines PL7TOOL1 32 ExportConf True The conversion of a DFB PL7 is called semi automatic At the end of conversion the user has e the source file of the converted DFB e aconversion report file including all data and warnings relating to the conversion Following a manual import of this converted DFB and the analysis in a Unity Pro project the output window containing the list of conversion errors is displayed Note The recommended version of PL7 is V4 3 However you may under your own responsibility convert the exported DFB wit
88. onverted is accessible using the command File gt Open which allows you to start the conversion Conversion The following table describes the procedure for converting a PL7 application into a Procedure Unity Pro application Step Action 1 Choose the Open command from the File menu 2 In the Files of type field select the type fef PL7 applications E AE Look in C y fal c y Adobe y Drivers EP E Unity Proemp y Adobeapp y 1386 y Pl7temp E Recycle y Asadoc J Kpcms 3 Pluser Ey Softoff EY Complex 2 Multimedia Files 1 Pm6 J TC Toolbox EY Concept A My Music y Program Files gt Temp 3 Confad 3 notes 3 Psfonts 3 tempef q gt File name Open Files of type Ena ly Cancel m Information on the application Type Name Version Last modification Comment 4 Open the application in read only mode Choose the hard drive and or the directory containing the file to be converted 4 Select the file fef to be opened and therefore converted The name of this file then appears in the File name field 28 35006148 03 October 2005 The conversion of a PL7 application Step Action 5 Confirm with Open Result The conversion procedure is then started The status bar shows how the procedure is progressing 6 After the automatic import phase you must start the analysis procedure See Analysis of a PL7
89. ory card with or without data storage the equivalent processor will also be equipped with the same type of card except for the few specific cases indicated in the legend of the following table Processor The following table indicates the equivalence between original processors and Equivalence updated processors Original processor Processor upgrade to be Updated processor Action performed performed running PL7 v4 T PCX 57 1012 T PCX 57 203 TSX PCI 57 204 Processor replaced T PCX 57 203 Not necessary TSX PCI 57 204 Processor replaced T PCX 57 3512 T PCX 57 353 TSX PCI 57 354 2 Processor replaced T PCX 57 353 1 Not necessary TSX PCI 57 354 2 Processor replaced Processors that do not accept 160K word cards These processors are available for Unity Pro versions higher than V1 0 35006148 03 October 2005 51 Inter platform equivalence Memory Card Equivalence For all processors except those indicated 1 in the above table the cartridge correspondence is as follows Memory card using PL7 Corresponding memory card using Unity Pro None None 32 K words 96 K bytes 64 K words 192 K bytes 128 K words 384 K bytes 128 K words Storage 768 K bytes 160 K words 448 K bytes 160 K words Storage 1 000 K bytes 256 K words 768 K bytes 256 K words Storage 2 000 K bytes 384 K words 2 000 K bytes 512 K words Storage
90. pondences between Grafcet language elements Grafcet instructions Introduction Grafcet instructions in ladder language Grafcet instructions in structured text Grafcet instructions in instruction list The conversion replaces the PL7 Grafcet language elements with their Unity Pro equivalent The following table describes the correspondence and possible differences between PL7 and Unity Pro ladder language Grafcet instructions PL7 Unity Pro State Instructions xi OPERATE Modified S SETSTEP X_i xi ORAE Modified S RESETSTEP X_i The following table describes the correspondence and possible differences between PL7 and Unity Pro structured text Grafcet instructions PL7 Unity Pro State Instructions SET Xi SETSTEP X_i Modified RESET Xi RESETSTEP X_i Modified The following table describes the correspondence and possible differences between PL7 and Unity Pro instruction list language Grafcet instructions PL7 Unity Pro State language Instructions SXi CAL SETSTEP X_i Modified R Xi CAL RESETSTEP X_i Modified 144 35006148 03 October 2005 Correspondences between Grafcet language elements Conversion restrictions PL7 Grafcet language Size of Diagrams in PL7 Grafcet language are automatically restructured by the PL7 programming in application converter into d
91. r 2005 73 Correspondences between common language elements Word bits Introduction Conversion replaces the PL7 objects by their Unity Pro equivalent Word bits The following table describes any correspondence and differences between PL7 and Unity Pro objects PL7 Unity Pro Status Syntax Type of Syntax Type of data data Bit j SSWi Xj BOOL SSWi j BOOL Converted j 1 15 SMW X5 BOOL SMWi j BOOL 1 SMWi SMwW3 X3 BOOL SMWi SMwW3 3 BOOL SMWi SKw3 X3 BOOL SMWi SKw3 3 BOOL MWi n X3 BOOL MWi n 3 BOOL SKWi Xj BOOL SKWi j BOOL SKWi SMw3 X3 BOOL SKWi SMW 3 BOOL SKWi SKW3 X3 BOOL SKWi SKw3 3 BOOL SKWi n X3 BOOL SKWil n 3 BOOL SNW r s k X9 BOOL SNWn s d j BOOL SNW s k X3 BOOL SNWs d j BOOL input output SIW Xj BOOL SIWC j BOOL Modified addresses 2 SOWR xX BOOL SONO j BOOL SMW Xj BOOL SMW 3 BOOL SKW Xj BOOL SKW j BOOL Legend 1 The syntax of the bits extracted into Unity Pro is modified See Extracted bit p 160 2 The address has been replaced by the PL7 converter e conversion of local addresses See In rack Input Output objects p 81 e conversion of remote addresses See Remote input output objects p 83 74 35006148 03 October 2005 Correspondences between common language elements Symbolized tables and indexed objects
92. r along ADD_ARINT_INT integer word ADD_ARDINT_DINT Operator between a table EF Modified 1 and an integer word or a long SUB_INT_ARINT integer word SUB_ARINT_INT SUB_DINT_ARDINT SUB_ARDINT_DINT Operator between a table id EF Modified 2 and an integer word or along MUL_ARINT_INT integer word MUL_ARDINT_DINT 35006148 03 October 2005 101 Correspondences between common language elements PL7 Unity Pro Status WORD or INT or DINT DWORD Operator between a table EF Modified 1 and an integer word or a long DIV_INT_ARINT integer word DIV_ARINT_INT DIV_DINT_ARDINT DIV_ARDINT_DINT Operator between a table REM EF Modified 1 and an integer word or along MOD_INT_ARINT integer word MOD_ARINT_INT MOD_DINT_ARDINT MOD_ARDINT_DINT EF SUM SUM_ARINT Modified 3 or SUM_ARDINT EF EQUAL EQUAL_ARINT Modified 5 or EQUAL_ARDINT 102 35006148 03 October 2005 Correspondences between common language elements PL7 Unity Pro Status WORD or INT or DINT DWORD EF FIND_EQD FIND_EQ_ARDINT Modified 4 FIND_EQDP FIND_EQP_ARDINT Modified 5 FIND_EQW FIND_EQ_ARINT Modified 4 FIND_EQWP FIND_EQP_ARINT Modified 5 FIND_GTD FIND_GT_ARDINT Modified 4 FIND_GTW FIND_GT_ARINT Modified 4 FIND_LTD FIND_LT_ARDINT Modified 4 FIND_LTW FIND_LT_ARINT Modified 4 LENGTH_ARD LENGTH_ARDINT Mo
93. r instructions Introduction Conversion replaces the PL7 instructions by their Unity Pro equivalent Instruction list and Unity Pro instructions The following table describes any correspondence and differences between PL7 PL7 Unity Pro Status EF FTOF FTOF Modified 1 FTON FTON Modified 1 FTP FTP Modified 1 SCOUNT SCOUNT Modified 1 MASKEVT MASKEVT Converted 2 UNMASKEVT UNMASKEVT Converted 2 FPULSOR FPULSOR Modified 1 READ_PCMCIA READ_PCMCIA Modified 3 READ_PCMEXT READ_PCMCIA Modified 4 SET_PCMCIA SET_PCMCIA Modified 3 SET_PCMEXT SET_PCMCIA Modified 4 WRITE_PCMCIA WRITE_PCMCIA Modified 3 WRITE_PCMEXT WRITE_PCMCIA Modified 4 Legend 1 The order of the function parameters has been modified See IN OUT INOUT parameters p 165 2 In Unity Pro the operation and comparison blocks of Instruction List language written in Structured Text language See L extensions p 142 are not converted Consequently the MASKEVT and UNMASKEVT instructions located in one of these blocks are not converted 3 The function name remains the same but a parameter is added in the first position When the call is made the value 0 must be entered in this parameter 4 The function name is modified but the operation remains the same 112 35006148 03 October 2005 Correspondences between common language ele
94. raphs Functional The PL7 application converter converts only the functional models which modules e contain a complete Grafcet section PRL Chart Pos e donot contain isolated elements of Grafcet e donot contain macro steps Note a functional model containing a Grafcet function even it is complete is not converted if it also contains a macro step The names of the functional modules which cannot be converted are listed in the conversion report file 152 35006148 03 October 2005 Differences between common language elements 14 At a Glance Subject of this This chapter describes the main differences between the objects common to Chapter different languages What s in this This chapter contains the following sections Chapter Section Topic Page 14 1 Differences between PL7 and Unity Pro types and tables 154 14 2 Differences between PL7 and Unity Pro objects 157 14 3 Differences between PL7 and Unity Pro instructions and 162 functions 14 4 Differences between PL7 and Unity Pro SFBs 167 35006148 03 October 2005 153 Differences between common language elements 14 1 Differences between PL7 and Unity Pro types and tables At a Glance Subject of this Section What s in this Section This section describes the main differences between PL7 types and tables and their Unity Pro equivalent This section contains the fo
95. riables and constants 0 0c eee eee eee 159 Word BINS oo coat sic isa ra ad a be cate 160 Symbolized tables and indexed objects u un uana 0 eee eee eee 161 Differences between PL7 and Unity Pro instructions and functions 162 AtaiGlane dna daa wel die del a 162 Table instructions and functions 0 0c eee ees 163 Process control Other and Communication instructions 165 Differences between PL7 and Unity Pro SFBs 000 eee ae 167 Types of Unity Pro EFB instances 2 0 eee eee 167 Differences between Structured Text language elements 169 Ata Glance 26 ceca aed ain bt ere bak mee node Oe ieee 169 Differences between PL7 and Unity Pro Structured Text language INSTFUCTIONS els eee dls Sb ek RS ree tog thine cd 170 Command instructions 00 0 tees 170 35006148 03 October 2005 Chapter 16 16 1 Chapter 17 Appendices Appendix A Glossary Index Differences between Instruction List language elements 171 Ata Glance ieo scopic a a a eed Deen Ge ee ede pee Ra ws 171 Differences between PL7 and Unity Pro Instruction List language INSTUCIIONS usina apn Set eee Sack okt Maw Meares Skee 172 Boolean instructions 0 000 c eee tees 172 Different display in runtime ScreensS 173 Runtime Screens ca Ra 173 E A E A 175 Ata Glance n n e ee ee ce ed Se nt 175 Recommendations 0 0 0c cece eee e
96. rocedure 41 End of the analysis procedure 42 Convertor message in the analysis procedure 43 Miscellaneous errors in the analysis procedure 44 35006148 03 October 2005 39 Analysis of a converted PL7 application General Introduction Analysis Output window The analysis allows the detection of errors generated in the application during conversion During the analysis phase the following errors are detected syntax errors semantic errors missing program parts objects that have no Unity Pro equivalent graphic objects or Grafcet drawings that have no Unity Pro equivalent other errors EFs developed by the user etc All types of error detected during the analysis phase are automatically shown on the screen in the output window Errors necessitating manual correction are signaled by the message Converror This message which appears in inverted commas in the output window allows you to directly access the part of the program to be corrected by a left double click 40 35006148 03 October 2005 Analysis of a converted PL7 application Analysis Procedure Introduction The analysis procedure must be manually launched after the automatic import phase Manual analysis The following table describes the procedure for manually running the analysis procedure phase Step Action 1 Selectthe Analyse command from the Build menu which launches the analy
97. rted SFB section What s in this Section instances are also converted automatically Example the SFB STi is translated by an EFB of instance name Ti and type PL7 3 TIMER This sub section therefore contains the tables showing correspondence between SFBs and EFBs Note where a PL7 SFB has no correspondence in Unity Pro a warning and a conversion error message are generated See Analysis p 40 This section contains the following topics Topic Page Types of Unity Pro EFB instances 119 Call of an SFB in structured text 120 Call of an SFB in instruction list language 121 Call of an SFB in ladder language 123 118 35006148 03 October 2005 Correspondences between common language elements Types of Unity Pro EFB instances Introduction Whatever the language used each SFB instance is converted into an EFB instance Types of The following table shows the types of instances instances SFB Types of Unity Pro instances ST PL7 3 TIMER STM TON PL7_TON TOF PL7_TOF TP PL7 TP SC PL7 COUNTER SMN PL7 MONOSTABLE SR Ri L lt 32 PL7 REGISTER 32 32 lt Ri L lt 255 PL7 REGISTER 255 SDR PL7 DRUM Key 1 The PL7_DRUM EFB contains an extra output parameter See Types of Unity Pro EFB instances p 167 compared with the PL7 DR instance type 35006148 03 October 2005 119 Correspondences between c
98. rted Legend 1 See table below 35006148 03 October 2005 69 Correspondences between common language elements System bits and words The following table describes any correspondence and differences between PL7 and Unity Pro bits and system words PL7 Unity Pro Status Syntax Syntax System bits 836 Deleted 537 595 System words SW160 SSW76 Modified SSW161 SSW77 SSW162 SSW78 Grafcet system bits 5521 SGT_21 Modified 1 2822 SGT_22 2823 SGT 23 824 SGT _24 825 Deleted 526 Grafcet system 5W20 Deleted words 2821 y SSW22 SWGT_22 Modified 1 5W23 SWGT_23 SSW24 SWGT_24 SW25 SWGT_25 SW125 Deleted SSW126 gt SSW127 Legend 1 Grafcet system bits and words are replaced in Unity Pro by equivalent EFs See Correspondences between Grafcet language elements p 143 Note all other system bits and words are converted 70 35006148 03 October 2005 Correspondences between common language elements Memory objects variables and constants Introduction Conversion replaces the PL7 objects by their Unity Pro equivalent Memory objects The following table describes any correspondence and differences between PL7 and Unity Pro objects PL7 Unity Pro Status Syntax Type of Syntax Type of data data
99. s 56 54 35006148 03 October 2005 Correspondence between application structures Tasks events and SRs Introduction Conversion replaces PL7 tasks EVT and SR by their Unity Pro equivalents Tasks EVTi SR EVT and SR tasks in PL7 and Unity Pro The following table describes any correspondence and differences between the depends on the processor depends on the processor PL7 Unity Pro Status MAST task Cyclic or periodic Cyclic or periodic Converted FAST task Periodic Periodic Converted Event processing EVTi The number of events available The number of events available Converted The system words manage the events The system words manage the events Converted 1 MASKEVT MASKEVT Converted 2 UNMASKEVT UNMASKEVT EVTIi priority level Priority level management Priority level management Converted Subroutines SRi SRi SR Section Modified 3 Legend 1 The same system objects exist in Unity Pro See System objects p 69 2 The same EFs exist in Unity Pro See Other instructions p 112 3 The SR name is modified but the operation remains the same In Unity Pro the SRi becomes an SR section named SRi 35006148 03 October 2005 55 Correspondence between application structures The sections Introduction Conversion replaces PL7 section characteristics by their Unity Pro equivalents
100. s DFBs are not converted All Schneider Diagnostics DFBs available using Unity Pro are catalogued in the diagnostics family See Unity Pro Standard Block Library Manual SIN Function of the diagnostics library Failure to follow this instruction can result in injury or equipment damage To export a PL7 DFB execute the following actions running PL7 V4 3 Step Action 1 e To export from the application browser e select the type of DFB by left clicking e To export from the DFB type editor e double click on the DFB type Select the Export command from the File menu Select the disk and or directory where the file must be stored Enter the file name in the Name field oa A ow hp Confirm with Save 34 35006148 03 October 2005 Conversion of a PL7 DFB Procedure for converting a PL7 DFB into Unity Pro Introduction The PL7 application converter is built into the Unity Pro software The DFB to be converted is accessible using the command File gt Open which allows you to start the conversion The following table describes the procedure for converting a PL7 DFB into Unity Pro Action Choose the Open command from the File menu In the Files of type field select the type dfb DFB file Look in C lv fal E E y Adobe y Drivers EP y Unity P roemp y Adobeapp y 1386 E Pl7temp y
101. s between common language elements Shift instructions Introduction Integer words Conversion replaces the PL7 instructions by their Unity Pro equivalent The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status WORD INT EF SHL SHL_INT Modified 1 SHR SHRZ_INT Modified 1 ROL ROL_INT Modified 1 ROR ROR_INT Modified 1 ROLW ROL_INT Modified 2 RORW ROR_INT Modified 2 WSHL_RBIT SHL_RBIT_INT Modified 2 WSHR_RBIT SHR_RBIT_INT Modified 2 WSHRZ_C SHRZ_RBIT_INT Modified 2 Legend 1 Replaced by an EF whose name depends on the type of operand 2 The function name is modified but the operation remains the same 35006148 03 October 2005 97 Correspondences between common language elements Long integer words The following table describes any correspondence and differences between PL7 and Unity Pro instructions PL7 Unity Pro Status WORD INT EF SHL SHL_DINT Modified 1 SHR SHRZ_DINT Modified 1 ROL ROL_DINT Modified 1 ROR ROR_DINT Modified 1 SHL_DWORD SHL_DWORD Converted SHR_DWORD SHR_DWORD Converted ROL_DWORD ROL_DWORD Converted ROR_DWORD ROR_DWORD Converted DSHL_RBIT SHL_RBIT_DINT Modified 2 DSHR_RBIT SHR_RBIT_DINT Modified 2 DSHRZ_C SHRZ_RBIT_DINT Modified 2 ROLD ROL_DI
102. sabling the protection 26 32 E End of procedure 42 Equivalent configuration 17 Exporting a DFB 32 Exporting an application 26 Exporting the source file 26 32 Extracted bit 160 F File Open 28 35 Fipio 83 FOR instruction 170 G GR7 143 Grafcet 143 IL 137 Import 14 15 19 Import procedure 37 IN OUT INOUT parameters 165 In rack l Os 81 Instruction List 137 L Ladder language 127 LD 127 M MDI tool 43 185 Index Miscellaneous errors 44 MPS MRD MPP instructions 172 N Nesting of functional modules 57 Network address 66 New processors 17 O Output window 14 15 19 28 37 40 43 P PL7 application converter 14 PL7 converter recommendations 177 PL7 Micro applications 14 PL7 V4 14 26 32 Premium processors 17 48 Printouts 147 Protections disabled 26 R Report file 14 15 17 Runtime screens 147 PL7 application conversion 173 S Saving a converted application 42 Schneider diagnostics DFB 32 Semi automatic conversion 14 15 17 19 Source file 14 15 17 19 ST 133 Status converted 54 deleted 54 modified 54 STRING 159 Structured Text 133 T TCP Open 114 Technical conversion procedure 19 186
103. sage in the analysis procedure p 43 in the output window enabling you to complete the drawing manually The following screen gives an example of a block embedded between two outputs of another block this part of the program cannot be automatically converted ES LD MAST Fgh MWD AM1 COMPARE M1 i F TMO M2 IN Q gt MODE TON lt H TB 1mn TM P 9999 lt gt H MODIF Y E alala im m am res e ka a akala salen lea len PE 132 35006148 03 October 2005 Correspondences between Structured Text language 9 elements At a Glance Subject of this This chapter contains the tables of correspondence between structured text Chapter language elements The PL7 Structured Text language elements are divided into three categories e those that remain unchanged and are translated automatically status converted e those that have a Unity Pro equivalent and are translated automatically status modified e those that have no Unity Pro equivalent status deleted Note if a PL7 Structured Text language element has no Unity Pro correspondence both a warning and aconversion error message are generated See Analysis p 40 What s in this This chapter contains the following sections 2 Chapter Section Topic Page 9 1 Correspondences between PL7 and Unity Pro Structured Text 134 language sequences 9 2 Correspondences between PL7
104. sing Unity Pro with a TSX CPP 110 card and you must check or modify the CO configuration file of the CANopen bus for this to be implemented with a TSX CPP 110 card 22 35006148 03 October 2005 PL7 application conversion procedure f Ata Glance Subject of this Part What s in this Part This part presents the different steps involved in converting a PL7 application or PL7 DFB into Unity Pro This part contains the following chapters Chapter Chapter Name Page 2 Conversion of a PL7 application 25 3 Conversion of a PL7 DFB 31 4 Analysis of a PL7 application converted into Unity Pro 39 35006148 03 October 2005 23 Conversion procedure 24 35006148 03 October 2005 Conversion of a PL7 application At a Glance Subject of this Chapter What s in this Chapter This chapter describes the procedure for converting a complete PL7 application into a Unity Pro application This chapter contains the following topics Topic Page General 26 Procedure for Converting a PL7 Application into a Unity Pro Application 28 Results of the PL7 application conversion 30 35006148 03 October 2005 25 The conversion of a PL7 application General Introduction Converting a PL7 application into a Unity Pro application requires the following e the application to be saved using PL7 V4 3 software e alevel TSX eee ee4
105. sis procedure Should any conversion errors occur an output window is displayed on the screen allowing you to correct them 35006148 03 October 2005 41 Analysis of a converted PL7 application End of the analysis procedure Introduction The procedure of analyzing a PL7 application or a PL7 DFB converted into Unity Pro ends when the output window is displayed on the screen End of analysis Once the analysis procedure is over there are two possible scenarios e the output window contains Convertor messages in order for the converted application or DFB to be exploitable you must manually correct these conversion errors See Convertor message in the analysis procedure p 43 e the output window does not contain Convertor messages the converted application or DFB is directly exploitable for compilation and transfer to the PLC Note At any time during the manual correction of the converted PL7 application or PL7 DFB you may save the application in Unity Pro format stu file If this is the case the next time the application is opened you must first launch an Analysis of the application See Manual analysis procedure p 41 in order to display the output window on the screen 42 35006148 03 October 2005 Analysis of a converted PL7 application Convertor message in the analysis procedure Introduction The Convertor message appears in the output window if e you ha
106. sis of the application in order to display the output window on the screen See Manual analysis procedure p 41 Note conversion errors appear in the report but not concerning errors not related to the program e g an incomplete configuration in the FEF are listed in a section located at the start of the master task 30 35006148 03 October 2005 Conversion of a PL7 DFB At a Glance Subject of this This chapter describes the procedure for converting a PL7 DFB into Unity Pro Chapter What s in this This chapter contains the following topics Chapter Topic Page General 32 Procedure for converting a PL7 DFB into Unity Pro 35 Conversion of Protected DFBs 36 Procedure for importing a PL7 DFB into Unity Pro 37 Results of the PL7 DFB conversion 38 35006148 03 October 2005 Conversion of a PL7 DFB General Introduction Update Converting a PL7 DFB into Unity Pro requires the following e aPL7 V4 3 application e the DFB to be unprotected e the DFB source file to be exported and saved All PL7 applications earlier than version 4 3 must be updated to V4 3 before being converted into a Unity Pro application See Update p 26 32 35006148 03 October 2005 Conversion of a PL7 DFB Disabling the protection To deactivate the protection of a PL7 DFB execute the following actions running PL7 V4 3 Step Action
107. ss ADR is replaced in Unity Pro by an EF For a given address words ADR r s xy i c xy i SyYS there are two possible scenarios e xy corresponds to the bus address e the converter replaces xy by a bus number e the converter chooses the bus number which is specified in the Unity Pro configuration e xy corresponds to the rack number and position e the converter replaces xy by r m e the rack 0 information becomes explicit If xy lt 100 the rack number is equal to O example xy 12 r m 0 12 If xy gt 100 the rack number is equal to the first digit example xy 715 r m 7 15 158 35006148 03 October 2005 Differences between common language elements Memory objects variables and constants Introduction Converting a PL7 application into a Unity Pro application generates certain differences which are described in the following paragraphs Character The converter replaces the MB and KB objects with character strings their position strings in the memory remains identical The name associated with the new character string is e if no symbol is associated with the object sMB or KB MBi_l e i integer e length of character table example 3MB1000 20 is converted to MB1000 20 STRING 20 e if no symbol is associated with the object MB or SKB symbole_l e symbol symbol of variable e length of character table example 3MB1000 20 with the symbol TABLE is converted into TABLE 20 STRING 20 If there is a c
108. st of 16 DRUM output objects 1 SDRi S number FSTEP_PL7_DRUM number_of step _of step DRi Key 1 The precise syntax of the EFB is given in the following sections See Types of Unity Pro EFB instances p 167 120 35006148 03 October 2005 Correspondences between common language elements Call of an SFB in instruction list language Introduction Call of an SFB in IL The conversion automatically replaces SFBs with equivalent EFBs insofar as these The following table describes the correspondence and possible differences between SFBs and EFBs CAL MNi S TEMPBOOL PL7 Unity Pro State SFB 3T Not used in instruction list language SFB TM TON IN TMi ST TEMPBOOL Converted CAL TMi IN TEMPBOOL TOF IN TMi ST TEMPBOOL CAL TMi IN TEMPBOOL TP IN TMi ST TEMPBOOL CAL TMi IN TEMPBOOL SFB 32 R Ci ST TEMPBOOL Converted CAL Ci CU 0 CD 0 R TEMPBOOL LD 0 LD Ci ST TEMPBOOL CAL Ci CU 0 CD 0 R 0 LD TEMPBOOL CU Ci ST TEMPBOOL CAL Ci CU TEMPBOOL CD 0 R 0 LD 0 CD Ci ST TEMPBOOL CAL Ci CU 0 CD TEMPBOOL R 0 LD 0 SFB 3MN SMNi ST TEMPBOOL Converted 35006148 03 October 2005 121 Correspondences between common language elements PL7 Unity Pro State SFB SR SRi L lt 32 R SRi ST TEMPBOOL Converted CAL Ri R
109. steps is insufficient increase the maximum number of steps as indicated in the output window use the command Tools gt Project settings gt Language extensions The calculation of the maximum number of steps using Unity Pro includes macro steps an error indicates an incompatibility between the different types of an assignment probably a multi assignment using PL7 modify the program to remove these incompatibilities an error occurs on a multi assignment in an LD operate block modify the program by writing as many blocks as there are assignments 182 35006148 03 October 2005 Glossary D DFB User Function Block DT Date and Time E EF Elementary Function EFB Elementary Function Block EVT Event l IL Instruction List language 35006148 03 October 2005 183 Glossary L LD Ladder language S SFB Standard Function Block SFC Sequential Function Chart language SR Subroutine ST Structured Text language STRING Character string 184 35006148 03 October 2005 Index A ADR 65 Analysis 40 Animation tables 147 Application structure 53 AS i 84 Atrium processors 17 51 Automatic conversion 14 15 17 19 C Character strings 159 Converror 40 Conversion 14 Conversion procedure 28 35 Conversion results 30 38 Conversion to Unity V2 0 22 Converter Analysis 41 Convertor 43 Correspondence 45 D Di
110. t the PL7 application to obtain a new FEF file restart the conversion opening the FEF file with Unity Pro 178 35006148 03 October 2005 Recommendations If Then the processor is not level 3 e open the FEF file using version 4 3 of PL7 See Conversion Principle Applications and Processors p 17 modify the processor version See Conversion Principle Applications and Processors p 17 export the PL7 application to obtain a new FEF file restart the conversion opening the FEF file with Unity Pro in the FEF file built in control loops are used set using PL7 variables MF for example using PL7 modify the loops concerned export the PL7 application to obtain a new FEF file restart the conversion opening the FEF file with Unity Pro you have modified the configuration of a TSX SCY 21601 module just before exporting the FEF file using PL7 save the stx file before exporting the application this allows you to save all last minute modifications export the PL7 application to obtain a new FEF file restart the conversion opening the FEF file with Unity Pro 35006148 03 October 2005 179 Recommendations What to do when The following table describes the procedure when the import phase fails this phase the import fails is launched automatically after the conversion phase If Then the hardware configuration of the FEF file has AT
111. te PL7 application fef gt onversion mport Analysis xef OCA OR onversion report Dutput window txt The following table describes the different steps involved in automatic conversion Step Description Conversion During this phase the fef PL7 source file is converted into a xef Unity Pro source file Any data and warnings relating to the conversion are generated Conversion report A txt conversion report file is generated It contains all data warnings and errors relating to the conversion procedure Import The xef source file is imported automatically into Unity Pro Analysis The imported file is analyzed by Unity Pro Any conversion errors are detected and generated Note You must manually launch this analysis phase Output window Any conversion errors are shown in the output window See End of the analysis procedure p 42 which is automatically displayed at the end of conversion 35006148 03 October 2005 19 Overview Semi automatic The following diagrams show the technical aspects of the conversion procedure for conversion a PL7 DFB i gt esi a id The following table describes the different steps involved in semi automatic conversion Step Description Conversion During this phase the dfb PL7 source file is converted into a xfb Unity Pro source file Any data and warnings relating to the conversio
112. tionalities or modules do not exist in V1 0 they will be indicated and not acknowledged in the new Unity project e If all functionalities or modules are available in Unity V1 0 the conversion is performed normally For a V4 4 PL7 conversion to Unity Pro V2 0 the new functionalities and new modules are converted The following paragraphs describe the new features and conversion rules to be used The PL7 applications containing the functionalities that implement a Fipio bus are converted form V4 3 or V4 4 PL7 to V2 0 Unity Pro The Fipio I O objects are converted in line with the new topological addressing rule See Remote Fipio bus objects p 83 PL7 applications containing Lexium EFs LXM_SAVE and LXM_RESTORE See Exchange Instructions p 109 are converted from V4 3 or V4 4 PL7 to V2 0 Unity Pro Note These EFs are used as part of applications that implement Lexium controllers on a Fipio bus PL7 V4 3 service pack 1 is used in the TSX WMY 100 module Applications containing this module are converted from PL7 V4 3 service pack 1 to Unity Pro V2 0 PL7 applications containing CANopen functionalities are converted to Unity Pro V2 0 according to the following rules e Only the TSX CPP 110 card is available using Unity Pro V2 0 e A PL7 application containing a TSX CPP 110 card is entirely converted in Unity Pro V2 0 e For PL7 applications containing a TSX CPP 100 card the TSX CPP 100 card is replaced u
113. tured Text language instructions Command instructions Introduction Converting a PL7 application into a Unity Pro application generates certain differences which are described in the following paragraphs FOR instruction The PL7 application converter converts the FOR command instruction In Unity Pro the index variable used in the FOR instruction is usable only within the programming loop During conversion of the first FOR instruction of a PL7 application an error message will warn you to check that each of the programming loop variables is used only within the loop If this is not the case the variable not having been declared the command is not carried out 170 35006148 03 October 2005 Differences between Instruction List language elements 1 6 At a Glance Subject of this Chapter What s in this Chapter This chapter describes the main differences between Instruction List language elements This chapter contains the following sections Section Topic Page 16 1 Differences between PL7 and Unity Pro Instruction List 172 language instructions 35006148 03 October 2005 171 Differences between Instruction List language elements 16 1 Differences between PL7 and Unity Pro Instruction List language instructions Boolean instructions Introduction Converting a PL7 application into a Unity Pro application generates certain differences which are des
114. tween the objects instructions and SFBs common to the different languages This chapter contains the following sections Section Topic Page 7 1 Correspondences between PL7 and Unity Pro types and 60 tables 7 2 Correspondences between PL7 and Unity Pro language 64 objects 7 3 Correspondences between PL7 and Unity Pro instructions 87 7 4 Correspondences between PL7 and Unity Pro SFBs 118 35006148 03 October 2005 59 Correspondences between common language elements 7 1 Correspondences between PL7 and Unity Pro types and tables At a Glance Subject of this Section What s in this Section This section contains the tables of correspondence between PL7 types and tables and their Unity Pro equivalents PL7 types and tables are divided into two categories e those that remain unchanged and are translated automatically status converted e those that have a Unity Pro equivalent and are translated automatically status modified This section contains the following topics Topic Page Types and tables 61 Operations between mixed types 63 60 35006148 03 October 2005 Correspondences between common language elements Types and tables Introduction Types Tables Conversion replaces the PL7 types and tables by their Unity Pro equivalent The following table describes any correspondence and differences between PL7 a
115. ue converted into PL7 35006148 03 October 2005 85 Correspondences between common language elements Grafcet words and bits The following table describes the correspondence and possible differences between Grafcet words and bits PL7 Unity Pro Status Syntax Syntax Indexed Grafcet SXi SMW SMi MW3 Modified 1 words and bits Xi T 2MM5 z Deleted 2 Grafcet words and Xi L SMi L Modified 1 bits table Xi T L Deleted 2 Legend 1 The objects of steps are no longer contiguous in the memory Therefore a set of Mi objects is assigned by the PL7 application converter to simulate indexed Grafcet words or bits and the tables of Grafcet words or bits 2 You must replace these objects manually in the program 86 35006148 03 October 2005 Correspondences between common language elements 7 3 Correspondences between PL7 and Unity Pro instructions At a Glance Subject of this Section This section contains the tables of correspondences between PL7 common language instructions and their Unity Pro equivalent The PL7 instructions are split into three categories e those that remain unchanged and are translated automatically status converted e those that have a Unity Pro equivalent and are translated automatically status modified e those that have no Unity Pro equivalent status deleted Note if a PL7
116. ve to correct the errors resulting from the conversion e you have to complete missing programming parts Illustration The following diagram shows the Unity Pro software screen at the end of the procedure of analyzing a PL7 application or a converted PL7 DFB Application MDI tool Output window Description The following table describes the various parts of the Unity Pro screen Part Description Application Browser of the converted PL7 application or the Unity Pro application into which you are importing the converted PL7 DFB Output window Window containing all conversion or analysis error messages Convertor Message displayed if you have to manually correct part of the program of the converted application or DFB By double clicking on the left button of the mouse on the word Convertor you access the MDI tool MDI tool The part of the program to be corrected associated with the Convertor message is displayed in the field You can correct the error directly in the MDI tool using Unity Pro commands 35006148 03 October 2005 43 Analysis of a converted PL7 application Miscellaneous errors in the analysis procedure Introduction User developed EFs Conversion error messages are normally displayed in the output window The following paragraphs contain examples of these errors If the PL7 application to be converted contains EFs developed b
117. version Introduction Results The results of the conversion of a PL7 DFB into Unity Pro are described in the following paragraphs At the end of the conversion procedure there are two possible scenarios e the DFB has been correctly converted e conversion errors have been generated If the DFB has been correctly converted it may be used in a Unity Pro application and saved in the application format stu file In the event of conversion errors you must manually correct the DFB in order for it to be exploitable The output window See End of the analysis procedure p 42 which can be used to manually correct these errors is automatically displayed on the screen at the end of the analysis procedure Note The Unity Pro application containing the converted DFB may be saved in stu format even if the DFB conversion errors have not been corrected If this is the case the next time the application is opened you must first launch See Manual analysis procedure p 41 an Analysis of the application in order to display the output window on the screen 38 35006148 03 October 2005 Analysis of a PL7 application converted into Unity Pro At a Glance Subject of this Chapter What s in this Chapter This chapter presents the analysis phase of a PL7 application converted into Unity Pro This chapter contains the following topics Topic Page General 40 Analysis P
118. word tables is generated e create a table of integers with 4 elements e assign each element one by one e generate the project again an error occurs on a table type DFB output a table type DFB output is no longer accessible outside the DFB To access it you must use the variable connected to the corresponding output pin For further information on DFBs See General p 32 an error on the DINT type variables recognized as INT by Unity Pro e modify the program to make the types compatible e example SD52 the solution consists of creating a DINT type SD52 object by writing SD52 INT_AS_DINT SW52 SW53 e generate the project again 35006148 03 October 2005 181 Recommendations If in the generation report one of the following cases appears Then an error occurs on the l or IW assigned in the program modify the program to delete these assignments Assignment on inputs is no longer accepted by Unity Pro an error occurs on a vertical comparison block located in the first column of the editor using the Copy Paste function modify the program to move this block by one column an error occurs in an SFC An error message indicates that alternative divergences or parallel convergences must be followed respectively by a transition or a step modify the SFC following the indications of the output window an error indicates that the maximum number of configured
119. y the user with TLX L SDKC PL7 41M software the converter does not recognize them and therefore cannot convert them A warning message is then displayed in the conversion report file and in the output window Availability of During the conversion of an EF the converter does not guarantee the availability of EFs the equivalent Unity Pro EF In the event that after converting the EF from the PL7 library the equivalent EF is missing from the Unity Pro library a conversion error is displayed A warning message is then displayed in the conversion report file and in the output window 44 35006148 03 October 2005 Correspondence between PL7 and Unity Pro At a Glance Subject of this This part contains the tables of correspondence between PL7 programming and its Part Unity Pro equivalent as well as the equivalence tables for hardware devices processor memory card What s in this This part contains the following chapters Part Chapter Chapter Name Page 5 Inter platform equivalence 47 6 Correspondence between application structures 53 7 Correspondences between common language elements 59 8 Correspondences between ladder language elements 127 9 Correspondences between Structured Text language 133 elements 10 Correspondences between Instruction List language elements 137 11 Correspondences between Grafcet language elements 143 12 Other correspondences between PL7 and Unity Pro elements 14

Unity Pro

Contents

Download Pdf Manuals

Related Search

Related Contents