Home

Unity Pro 2.2

1. Parameters Data type Meaning TOD_CNF BOOL 1 4x register for hardware system clock was found and the clock is operational 0 time is set at the moment In this case the other outputs keep their values D WEEK BYTE Weekday 1 Sunday 7 Saturday MONTH BYTE Month 1 12 DAY BYTE Day 1 31 YEAR BYTE Year 0 99 HOUR BYTE Hour 0 23 MINUTE BYTE Minute 0 59 SECOND BYTE Second 0 59 33002515 111 GET_TOD 112 33002515 LIMIT_IND_DFB Limit with indicator 1 3 Description Function description Formula This derived function block transfers the unchanged input value Input to the Output if the input value is not less than the minimum value LimitMinimum and does not exceed the maximum value LimitMaximum If the input value Input is less than the minimum value LimitMinimum the minimum value will be transferred to the output If the input value Input exceeds the maximum value LimitMaximum the maximum value will be transferred to the output Additionally a indication is given if the minimum or maximum value is violated If the value at the Input input is less than the value at the LimitMinimum input the MinimumViolation output becomes 1 If the value at the Input input is more than the value at the LimitMaximum input the MaximumViolation output becomes 1 The data types of the LimitMinimun Input LimitMaximum input v
2. 33002515 85 Blocks from Concept to Unity Pro 86 33002515 BYTE_TO_BIT_DFB Type conversion 7 Description Function description Representation in FBD This derived function block converts one input word from the BYTE data type to 8 output values of the BOOL data type The individual bits of the byte at the input are assigned to the outputs according to the output names BITO 2 Bir1 21 aa Bite 28 BIT7 2 EN and ENO can be configured as additional parameters Representation BYTE TO BIT DFB Instance BYTE TO BIT DFB BYTE variable IN BITO BOOL variablel BIT1 BOOL variable2 BIT2 BOOL variable3 BIT3 BOOL variable4 BIT4 BOOL variable5 BIT5 BOOL variable6 BIT6 BOOL variable7 BIT7 BOOL variable8 33002515 87 BYTE_TO_BIT_DFB Representation in LD Representation in IL Representation in ST Representation BYTE variable BYTE TO BIT DFB Instance BYTE TO BIT DFB EN ENO BOOL variablel IN BITO BOOL variable2 BIT1 BOOL variable3 BIT2 BOOL variable4 BIT3 BOOL variable5 BIT4 BOOL variable6 BITS BOOL variable7 BIT6 BOOL variable8 BIT7 Representation B CAL BYTE TO BIT DFB Instance BITO gt BOOI BIT2 gt B001 BIT4 gt BOO BIT6 gt B001 L variable
3. 00 000 c eee eee eee eens 50 Unique Naming required 0 00 51 Incomplete LD Generation llis 51 LD Execution Order Changed ooooccccoccccc eee 51 Constants crio isa OA eae Ed 55 Indices in ST and lirica ae rta 55 Calculate with TIME and REAL o ooccccocccccco eee 55 WORD Assignments to BOOL Arrays 0 00 cece eee ee 55 Topological Address Overlapping liess 56 Structure Alignment Changed o oocccccccccc eee 56 Undefined Output on Disabled EFS 2 0 000 c cece eee eee 57 SFC Section Retains its State When Performing an Online Modification lille 59 Weekday Numbering 000 cece eee ee nh 59 System Timer ise eee ES IH LE e ordi oce uus Sebel Wt Abad 59 Initial Values uem RE ee ee Sate yh e Rea ed es 60 MCI OS tree gripe a padded Ate Gong wee Bea Dope Kia 61 Possible application behavior change 63 Introduction ct eberPU a I eer pene eae ME 63 Generalis ei ru engl Aper vnda diate eua tee s am eo Lad refe DE 64 Concept behavior s seire careg esra stine nia hen 65 7 E se kp ANE AE 65 Unity behavior sore ranta ER a a E rea E D O Aa ears 69 CONSEQUENCES c sucus nee hE RANA ee 71 The Conversion Process 00 seeeeee ee eeeeeeee 77 Conversion Process ille n 77 Conversion Procedure esesseeseeeeee 79 Introduction s ike haath nre e EL hU Ope ERREUR at eod ra 79 Exporting a Project from Concept
4. 140 33002515 READREG Representation Representation in LD READREG Instance READREG EN ENO StartReadOnce SetAfterReadingNewData REQ NDR SetInCaseOfError DeviceAddress NODEADDR ERROR RoutingPath ROUTPATH STATUS ErrorCode OffsetAddress SLAVEREG NumberOfRegisters NO_REG ArrayForValuesRead REG READ REG READ ArrayForValuesRead Representation Representation in IL CAL READREG Instanc REQ StartReadOnce NODEADDR DeviceAddress ROUTPATH RoutingPath SLAVEREG OffsetAddress NO REG NumberOfRegisters REG READ ArrayForValuesRead NDR gt SetAfterReadingNewData ERROR gt SetInCaseOfError STATUS gt ErrorCode Representation Representation in ST READREG Instance REQ StartReadOnce NODEADDR DeviceAddress ROUTPATH RoutingPath SLAVEREG OffsetAddress NO REG NumberOfRegisters REG READ ArrayForValuesRead NDR gt SetAfterReadingNewData ERROR gt SetInCaseOfError STATUS gt ErrorCode 33002515 141 READREG Parameter description Description of the input parameters Parameter Data type Meaning REQ BOOL With a rising edge at the REQ input this function block reads a register area from an addressed slave via Modbus Plus NODEADDR INT Device address within the target segment
5. EN and ENO can be configured as additional parameters Representation GET TOD Instance GET TOD TOD CNF RegisterPresentFlag D WEEK DayOfWeek MONTH I BYTE variable2 DAY BYTE variable3 YEAR L BYTE variable4 HOUR BYTE variable5 MINUTE BYTE variable6 SECOND BYTE variable7 33002515 109 GET_TOD Representation inLD Representation in IL Representation in ST Representation GET TOD Instance GET TOD EN ENO RegisterPresentFlag TOD_CNF D WEEK DayOfWeek MONTH BYTE variable2 DAY BYTE variable3 YEAR BYTE variable4 HOUR BYTE variable5 MINUTE BYTE variable6 SECOND BYTE variable7 Representation CAL GET TOD Instance TOD CNF gt RegisterPresentFlag I DW EK gt DayOfWeek MON DAY gt Byte variable3 Y HOUR gt Byte variable5 SECOND gt Byte variable TH gt Byte variable2 EAR gt Byte variable4 INUTE gt Byte variable Representation GI ET TOD Instance TOD CNF D_WEEK gt DayOfWeek MON I DAY 2Byte variable3 Y HOUR gt Byte variable5 SECOND gt Byte_variable7 gt RegisterPresentFlag TH gt Byte variable2 EAR gt Byte variable4 INUTE gt Byte variable 5 110 33002515 GET_TOD Parameter description Description of the output parameters
6. General description Brief description Conversion Conversion options for Concept projects Objects which cannot be converted The Concept Converter is an integrated function in Unity Pro which is used to convert Concept applications into Unity Pro This means that Concept programs can also be operated in Unity Pro Substitute objects are used in place of objects that cannot be converted and messages are displayed in the output window to find these objects Descriptions of the respective procedures are provided in chapter Conversion Procedure p 79 Note Back conversion from Unity Pro to Concept is not possible The conversion is carried out in 4 steps 1 In Concept Export the Concept application using the Concept converter which creates an ASCII file 2 In Unity Pro Open the exported ASCII file ASC in Unity Pro 3 In Unity Pro Automatic conversion of the ASCII file into Unity Pro source file format 4 In Unity Pro Automatic import of the Unity Pro source file You can enter adjustments in Unity Pro before the conversion that have different effects on the conversion result For more information see Unity Pro User GuideConversion options for Concept projects chapter The following objects cannot be converted into Unity Pro e Compact and Atrium configuration e I O initialization except 0 33002515 11 General Description 12 33002515 Requirement
7. PARA Y Word 3 215 914 913 2912 211 2101299 28 97 26 25 94 93 22 21 20 PAR5 Y Word 4 915 914 913 212 2911 2910 29 28 97 96 95 94 93 92 91 90 PAR6 Y Word 5 915 214 213 212 911 910 99 298 927 96 95 94 93 92 o91 20 Timer address date time of day and the battery monitoring can no longer be assigned to the State RAM with Unity Pro All required information can be accessed via the control panel When Concept is converted to Unity Pro DFBs are created which can be simulated in Unity Pro without further manual modifications of these functionalities Note The Concept Timer Register is 16 bits long and has an accuracy of 10 ms The equivalent system word SW18 in Unity Pro is 32 bits long and has an accuracy of 100 ms If this accuracy is not sufficient the FREERUN function from the System library can be used which delivers accuracy of up to 1 ms Note When dealing with days of the week the value 1 corresponds to Sunday in Concept and Monday in Unity Pro 33002515 21 Requirements Quantum Diagnostics Words Topological Addresses Located Variable Longer cycle time via EBOOL In Unity the diagnostics words are specified to be a certain number e Local I O 16 Words e RIO I O
8. slsseses eese eere 80 Importing a Project into Unity Pro o oooooooococorcr BR 81 Missing Datatypes at the Beginning of the Import o oooo 82 Converting only parts of a Concept applicatiON oooooooocooooo 83 Removing accidentally included Concept Macros 0 000000 83 Part Il Chapter 7 Chapter 8 Chapter 9 Chapter 10 Chapter 11 Chapter 12 Chapter 13 Chapter 14 Chapter 15 Blocks from Concept to Unity Pro 85 INTO UCI es oir a E EROR ta id ead a EE 85 BYTE_TO_BIT_DFB Type conversi0N oo ooo 87 Description ii da aid 87 CREADREG Continuous register reading 91 OVENVIOW Lis isco ria ia das reli be do e 91 prec ELS 92 Mode of Functioning 0 bid orient ttt 95 Parameter description llle 96 Modbus Plus Error CodeS nuanua cee eee eene 97 CWRITREG Continuous register writing 99 OVENIOW 2 eese A a ee a eui T A oe ME 99 Description sc lia sas AR pine ta c RR ae Bae am Ee 100 Mode of Functioning ooooocococco III 103 Parameter description 0 02 0 eee eee eee 104 DINT AS WORD DFB Type conversi0n 105 Description usse sce RR eh RR ERROR SR Saeed ea EE 105 DIOSTAT Module function status DIO 107 peu 107 GET TOD Reading the hardware clock Time Of Day 109 Description e cating venu Tn ROBLPENRMEEXUE E REI ADR ER EE 109
9. m 1 33002515 121 LOOKUP_TABLE1_DFB 122 33002515 PLCSTAT PLC function status 15 Overview Introduction This chapter describes the PLCSTAT block What s in this This chapter contains the following topics 2 Chapter Topic Page Description 124 Derived Data Types 126 PLC status PLC_STAT 128 RIO status RIO_STAT for Quantum 131 DIO status DIO_STAT 132 33002515 123 PLCSTAT Description Function description Evaluation Representation in FBD Representation inLD This derived function block reads the Quantum PLC internal states and error bits and copies this data to the data structures allocated to the respective outputs EN and ENO can be configured as additional parameters Only data with the input bit PLC_READ RIO READ DIO READ setto 1 will be read The evaluation of PLC STAT PLC status RIO STAT I O status and DIO_STAT I O communications status is possible Note The name of the output DIO STAT is confusing This output only relates to the remote I O Drop Status Information S908 and not to the Distributed 1 O status To read the distributed I O status use the function block DIOSTAT See DIOSTAT Module function status DIO p 107 Representation PLCSTAT Instance PLCSTAT CopyPLCStatusFlag PLC READ PLC STAT PLC IO Status CopyRIOStatusFlag RIO READ
10. sync BOO ms lsb BYT ms msb BYT p pH E Manual If an application that includes the DPM time structure is converted the analyze Correction build process will fail for the redefined structure components in the above example ms lsb ms msb The user has to manually change the usage of these structure components in the application accordingly 56 33002515 Language differences Undefined Output on Disabled EFs Outputs of EFs Not Kept Execution Behavior Differs Significantly Manual Correction Concept In case the EN switches from TRUE to FALSE the outputs of EFs from the previous cycle are not kept in Unity This reduces the memory consumption in the PLC This is different from EFBs which keep their value from the previous cycle Concept uses static links to latch the value from the previous cycle If a Concept application relies on the outputs of EFs to keep their old values the execution behavior in UNITY will differ significantly The application has to be changed manually Links from outputs which are assumed to keep their value need to be replaced by variables If the EN of an EF is set to false the EF is not executed and a connected variable is not touched The output of the disabled SEL EF is kept and used as input for the Eo INT function block 16 2 TRUE gt p 3 FALSE 555 gt LA 33002515 57 Language differences Unity Th
11. 16 Words e DIO I O 16 Words In Concept it was also possible to specify a smaller number of diagnostics words for the individual I Os Keep this difference in mind since it can cause problems The topological addresses are assigned so that if the hardware configuration remains the same they occupy the same I O connections as they were assigned in Concept The user sees the hardware addresses in Unity Pro that they are using without having to carry out the intermediate step via the State RAM Located BOOL variables in Concept are converted to EBOOL variables in Unity Pro Unity Pro provides this new EBOOL variable for the detection of transitions edges This Elementary BOOL type is used for Ix Mx and unlocated variables EBOOL variables can be forced The EBOOL variable provides three informational items e Current value e Historical value e Force information Only the current value can be accessed the other values can only be accessed via product specific functions In Unity as opposed to Concept the edge and force information is updated from EBOOL variables during program runtime For this reason on the Quantum CPU 434 CPU 534 and CPU 311 platforms the assignment of EBOOL variables is only half as fast as the assignment of BOOL variables Note If you need variables in the signal memory use BOOL variables and assign them to the memory area MW e g BoolVar BOOL AT MW10 Otherwise use unlocat
12. DIOSTATE yP g word1 WORD Switch on error numbers word2 WORD Cable A error word3 WORD Cable A error word4 WORD Cable A error word5 WORD Cable B error word6 WORD Cable B error word7 WORD Cable B error words WORD Global communication status word9 WORD Global cumulative error counter for cable A wordlO WORD Global cumulative error counter for cable B wordll WORD I O station 1 health status and repetition counter first word wordl2 WORD I O station 1 health status and repetition counter second word word13 WORD I O station 1 health status and repetition counter third word wordl4 WORD I O station 2 health status and repetition counter first word word104 WORD I O station 32 health status and repetition counter first word word105 WORD I O station 32 health status and repetition counter second word word106 WORD I O station 32 health status and repetition counter third word 33002515 127 PLCSTAT PLC status PLC STAT General information PLC status PLCSTATE wordl Note Information corresponds to status table words 1 to 11 in the dialog PLC status The conditions are true when the bits are set to 1 Bit allocation IM e IA ES CM E 10 11 12 18 14 15 16 Bit Allocation 10 Run light OFF 11 Memory protect OFF 12 Battery failed 128 33002515 PLCSTAT Hot Standby stat
13. Identifies the node address within the target segment The parameter can be entered as an address located variable unlocated variable or literal Identifies the routing path to the target segment The two digit information units run from 01 64 see Mode of Functioning p 165 If the slave resides in the local network segment ROUTPATH must be set to 0 or must be left unconnected The parameter can be entered as an address located variable unlocated variable or literal Start of the destination area in the addressed slave to which the source data is written The destination area always resides within the 4x register area SLAVEREG expects the destination address as an offset within the 4x area The leading 4 must be omitted e g 59 contents of the variables or value of the literal 40059 The parameter can be entered as an address located variable unlocated variable or literal Number of registers to be written to slave processor 1 100 The parameter can be entered as an address located variable unlocated variable or literal An ANY ARRAY WORD thatis the same size as the planned transmission must be agreed upon 2 No REG for this parameter The name of this array is defined as a parameter If the array is defined too small then only the amount of data is transmitted that is present in the array The parameter must be defined as a located variable Transition to ON state for one
14. Programming Language ST IL General Generic EFBs Syntax with Concept 2 5 Generic EFBs in Concept Declaring EFBs For some programming languages there are restrictions to observe when converting a project from Concept to Unity Pro Only call generic EFBs instances once Using Concept 2 2 assign the outputs directly after the EFB call of a variable Only use the new syntax for Concept 2 5 from Unity V2 0 onwards it is automatically converted Syntax with Concept 2 5 GenEFB in1 x1 in1 in2 out1 and out2 are type ANY in2 x2 List of generic EFBs in Concept e COMM library XXMIT e CONT_CTL library DEADTIME e EXTENDED library e LI e HYST INDLIM LIMD SAH B984 library FIFO LIFO R2T SRCH T2T GET_3X GET_4X PUT_4X The declaration of EFBs in Unity Pro is found in the variables editor and no longer in the ST IL sections as with Concept EFBs declared this way are no longer limited to only one section 42 33002515 Requirements Programming Language LL984 General For some programming languages there are restrictions to observe when converting a project from Concept to Unity Pro LL984 is no Unity Pro only supports IEC conforming programming The programming languages longersupported LL984 and LL984 specific configurations are not supported by Unity Pro by Unity Pro See also Restrictions for old LL984 configurations p 15 Programm
15. structures derived data types used in the project are exported e Project without DFBs All project information including all data structures derived data types but not DFBs and macros is exported Result The dialog box for selecting the files to be exported is opened 4 Select the following file extension e Export projects Select the extention prj from the format list box 5 Select the project and confirm using OK Result The project is stored in the current directory as an ASCII file asc 6 End the Concept Converter program using File Exit 80 33002515 Conversion Procedure Importing a Project into Unity Pro General A Concept project that should be used in Unity Pro must first be exported from Concept It is then possible to use the Unity Concept Converter to make the conversion to a Unity Pro project Import project Carry out the following steps to convert and import a project Step Procedure 1 Launch Unity Pro 2 Open the project exported from Concept using File Open Select the data type CONCEPT PROJECTS ASC 3 Result The ASCII file is converted to Unity Pro source file format and imported automatically Import errors and messages about objects that cannot be converted and have substitute objects in their place are displayed in an output window 4 Edit the errors and messages in the output window manually to ensure the Unity Pro project runs c
16. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Bit Allocation 1 8 Counts receiver errors 9 16 Counts l O station receiver failures Bit allocation for word4 1 2 3 4 5 6 7 8 9 13 14 15 16 Bit Allocation 1 1 frame too short 2 1 no frame end 13 1 CRC error 14 1 alignment error 15 1 overflow error 134 33002515 PLCSTAT Status of cable B DIOSTATE word5 word6 word7 Global communication status DIOSTATE word8 Bit allocation for word5 112 13 4 5 6 7 8 9 10 11 12 13 14 15 16 Bit Allocation 1 8 Counts frame fields 9 16 Counts DMA receiver overflows Bit allocation for word6 112 13 4 5 6 7 8 9 10 11 12 13 14 15 16 Bit Allocation 1 8 Counts receiver errors 9 16 Counts l O station receiver failures Bit allocation for word7 1 12 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Bit Allocation 1 1 frame too short 2 1 no frame end 13 1 CRC error 14 1 alignment error 15 1 overflow error The conditions are true when the bits are set to 1 Bit allocation for word8 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Bit Allocation 1 Comm function display 2 Cable A status 3 Cable B statu
17. 144 33002515 139 READREG Description Function With a rising edge at the REQ input this function block reads a register area from an description addressed slave via Modbus Plus EN and ENO can be configured as additional parameters Note When programming a READREG function you must be familiar with the routing procedures used by your network Modbus Plus routing path structures will be described in detail in Modbus Plus Network Planning and Installation Guide Note This function block only supports the local Modbus Plus interface no NOM If using a NOM please work with the CREAD_REG block from the communication block library Note This function block does not support TCP IP or SY MAX Ethernet If TCP IP or SY MAX Ethernet is needed please use the CREAD REG block from the communication block library Note Several copies of this function block can be used in the program However multiple instancing of these copies is not possible Representation Representation in FBD READREG Instance READREG StartReadOnce _ REQ NDR SetAfterReadingNewData DeviceAddress NODEADDR ERROR SetInCaseOfError RoutingPath ROUTPATH STATUS ErrorCode OffsetAddress SLAVEREG NumberOfRegisters NO REG ArrayForValuesRead REG READ REG READ ArrayForValuesRead
18. 55 ST 55 Initial values 60 INOUT parameters 48 Instruction List IL 42 L Ladder Diagram LD 30 Ladder Diagram LL984 43 Language differences 45 LD Execution order changed 51 Incomplete generation 51 LD Ladder Diagram 30 LD Networks Wrapping of too wide 38 LD Picture Conversion 30 Limit with Indicator LIMIT IND DFB 113 LIMIT IND DFB 113 LL984 Ladder Diagram 43 LL984 restrictions 15 Located Variable 22 LOOKUP TABLE1 DFB 117 M Macros 43 61 Removing accidentally included Concept Macros 83 Macros LD 41 Missing Datatypes 82 Missing DDT 82 Module Function Status DIO DIOSTAT 107 Module Function Status RIO RIOSTAT 147 N Names Redundant DDT and section 51 O Online modification SFC section 59 Output Picture LD Conversion 34 Outputs M forced 24 P Parallel Alternative Sequence 29 Parameter type Changed 49 Parts of a Concept application 83 Picture LD Conversion 34 pins EF EFB 50 PLC Function Status PLCSTAT 123 PLC Types Quantum 14 PLCSTAT 123 Possible application behavior change 63 Program Execution 17 Programming Language FBD 43 Programming Language IL 42 Programming Language LD 30 Programming Language LL984 43 Programming Language SFC 29 Programming Language ST 42 Protect switch 24 33002515 171 Index Q Quantum PLC Types 14 R Read Register READREG 139 READ_REG 49 Reading the Hardware Clock Time Of D
19. LIMIT IND DFB Limit with indicator 113 Description 52 ep ea 113 LOOKUP TABLE1 DFB Traverse progression with 1st degree interpolation 117 OVGIVIeW sii ce ri eee re Uim nemici c ad 117 Description s r ete ad Ie mad meu rer a dee TUR aS 118 Detailed description 0 00 cee 120 PLCSTAT PLC function StatuS ooo oooooooo 123 OVEIVICW i uenire Mie eie Lo es cido Beh be obi dee RA 123 Descriptiva as Duas een a ec eee te eee P da 124 Derived Data Types 02 0 e eee eee 126 PLC status PLC STAT iets pein ek ice we VR eee Ee 128 RIO status RIO STAT for Quantum 1 2 0 0 00 c cee eee 131 DIO status DID STAT cocina ees PET eee eee niger 132 Chapter 16 Chapter 17 Chapter 18 Chapter 19 Chapter 20 Chapter 21 Index READREG Read register ooooooocooommmmoo 139 OVEIVIOW secon eared ra ek oe dad t eae eet ere 139 Description oe Pa ee ae ae ee eee Gere 140 Mode of Functioning 002 eee eee eee eee 143 Parameter description o oooooocoocoor 144 RIOSTAT Module function status RIO 147 Description iia o Mada pale Da ee 147 SET_TOD Setting the hardware clock Time Of Day 151 D sctiptionzzs eue dot REY eee POS eA Pe po a vee EN 151 WORD AS BYTE DFB Type conversion 155 Description ssi ceti eT ides A ea ER a 155 WORD TO BIT DFB Type conversion 157 Description eh bu
20. PLC status dialog The words show the I O module function status Five words are reserved for each of the maximum 32 I O stations Each word corresponds to one of maximal 2 possible module racks in each I O station Each of the module racks for Quantum hardware can contain up to 15 I O modules except for the first rack which contains a maximum 14 I O modules Bit 1 16 in each word show the corresponding I O module function display in the racks Bit allocation 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Bit Allocation 1 Slot 1 2 Slot 2 16 Slot 16 Four conditions must be fulfilled if an I O module can give a correct function display The data traffic of the slot has to be monitored The slot must be valid for the inserted module Valid communication must be established between the module and the RIO interface at RIO stations Valid communication must be established between the I O processor in the PLC and the RIO interface at the RIO station 33002515 131 PLCSTAT Status words for the MMI user controllers The status of the 32 element button controllers and PanelMate units in a RIO network can also be monitored with an I O function status word The button controllers are located on slot 4 in a I O rack and can be monitored at bit 4 of the corresponding status word A PanelMate on RIO is located on slot 1 in mo
21. PWM Y POS Y NEG QPWM Y POS Y NEG SCON3 ERR_FF VLIM STATUS Extensions FIFO EMPTY FULL Compatibility LIFO EMPTY FULL Note The pins were not changed because in normal operation mode of the blocks this has no influence 76 33002515 The Conversion Process Conversion Process General A Concept project is exported from Concept and then converted automatically into a Unity Pro project using the Unity Pro Concept Converter 33002515 77 The Conversion Process Conversion process Error report and analysis Representation of the conversion process Concept Export ASCII Cavalry XEF Import Unity Pro Project Bid File File Project Concept Unity Pro Concept Converter i Error report Description of the conversion levels Level Description 1 A project is exported from Concept An ASCII file is created 2 The Unity Pro Concept Converter is called The ASCII file is converted into an XEF file 3 The XEF file is imported into Unity Pro A Unity Pro project is created 4 The error report is checked There must be no errors 5 The project is now available in Unity Pro and can be generated and then loaded into a PLC or processed in Unity Pro Errors that occur during conversion are logged in an error report and displayed in an output window Substitute objects are used in pla
22. RIO STAT RIO IO Status CopyDIOStatusFlag 4 DIO READ DIO_STAT DIO IO Status Representation PLCSTAT Instance PLCSTAT EN ENO CopyPLCStatusFlag PLC READ PLC STAT L PLC IO Status CopyRIOStatusFlag RIO READ RIO STAT RIO IO Status CopyDIOStatusFlag DIO READ DIO STAT H DIO_ IO Status 124 33002515 PLCSTAT Representation in IL Representation in ST PLCSTAT parameter description Representation CAL PLCSTAT Instance PLC READ CopyPLCStatusFlag RIO READ CopyRIOStatusFlag DIO READ CopyDIOStatusFlag PLC STAT 2PLC IO Status RIO STAT RIO IO Status DIO STAT DIO IO Status Representation PLCSTAT Instance PLC READ CopyPLCStatusFlag RIO READ CopyRIOStatusFlag DIO READ CopyDIOStatusFlag PLC STAT 2PLC IO Status RIO STAT RIO IO Status DIO STAT DIO IO Status Description of the input parameters Parameters Data type Meaning PLC READ BOOL 1 copies the PLC status from the status table to the output PLC STAT RIO READ BOOL 1 copies the RIO status from the status table to the output RIO STAT DIO READ BOOL 1 copies the DIO status from the status table to the output DIO STAT Description of the output parameters Parameters Data type Meaning PLC STAT PLCSTATE Contains the PLC status RIO STAT RIOSTATE C
23. WORD AS UDINT For example WAUD UDINT WORD AS UDINT LOW WAUL WORD HIGH WAUH WORD looks like this after conversion WAUD UDINT FBI ST1 75 33 LOW WAUL WORD HIGH WAUH WORD FBI ST1 75 33isthe instance name of the provided DFB wrapper However the call is still invalid for the analyzer because the converter cannot yet do multi object syntax corrections in ST Will be present in V2 0 You must correct this manually to FBI ST1 75 33 LOW WAUL WORD HIGH WAUH WORD OUT gt WAUD 46 33002515 Language differences EFB replaced by function Error message Manual correction Some standard Concept EFBs are implemented in Unity as functions If the converted application contains in an ST or IL section a call to such an EFB an error will be generated while analyzing the project The following figure is a sample explanation of the SET_BIT function block B RES resl IN true NO 54 E1063 call of non function block The SET BIT function officially replaces SET BITX which is not implemented in UNITY SET BIT now is a function and therefore the instance has been eliminated and the function name itself has been inserted instead However an additional manual correction of the call is required The converter does not do multi object syntax corrections in ST or IL will be present in V2 0 Since this is a f
24. located words Unity Comm EFBs no longer accept a single WORD address for the communication field because more than one WORD is written So the converter introduces an artificial array shown in the conversion report that can be reached from the project tree through the appropriate hyperlink For var WORD1 type ARRAY 0 0 OF WORD generated The array has a single word size because the converter can not determine its size The user therefore needs to manually configure the correct array size 33002515 49 Language differences ANY_ARRAY_WORD parameters Error Message Change of Parameter Type Redefine Back to a One Dimensional WORD Array For EF EFB pins that have the type WORD in Concept and have been changed to ANY ARRAY WORD in Unity Cannot import variables will be the reported type Such pins usually have a single register address as a formal parameter in Concept but it is actually used to point to an array of words for which the size has not been explicitly declared In Unity an array of words has to be declared for this purpose This is why the converter changes the type to ARRAY 0 0 OF WORD However the converter cannot determine the required size because a size declaration is absent in the Concept application Therefore the converter defines one data element 0 0 as a replacement for the original variable It is up to the user to replace this default range of one element with the
25. old LL984 configurations Unity Pro only supports IEC conformant programming Concept sections created using the LL984 programming language are converted to the LD programming language in Unity Pro in a later version The following points from LL984 configurations are no longer supported by Unity Pro Not supported by Unity Pro Supported by Unity Pro LL984 loadables Concept system and IEC loadables are completely integrated ASCII messages Will not be converted User loadables Unity Pro provides the equivalent EFBs or DFBs instead 6x range register in expanded memory Will not be converted Mixed programmed projects LL984 IEC When you want to convert mixed programmed projects please contact Product Support at Schneider Electric Data memory write protection Unity Pro provides write protection variables instead 33002515 15 Requirements Hot Standby HSBY There are the following differences for converting the Concept Hot Standby to Unity Pro Concept Unity Pro The Hot Standby system in Concept is based on the 140 CHS 111 00 module This module is no longer supported by Unity Pro The 140 CHS 111 00 module is purely a Hot Standby Module for a single slot The power is supplied via the rack The CPU 671 60 module is a CPU module for two slots with a fixed assigned connection for data exchange The Hot Sta
26. program scan signifies data have been transferred The parameter can be entered as an address located variable or unlocated variable 166 33002515 WRITEREG ERROR Transition to ON state for one program cycle signifies detection of a new error The parameter can be specified as an address located variable or unlocated variable STATUS Error code see Modbus Plus Error Codes p 97 The parameter can be specified as an address located variable or unlocated variable 33002515 167 WRITEREG 168 33002515 Index Mx Register 23 A ANY_ARRAY_WORD 50 Application behavior change 63 Automatically created connections LD 33 Battery Monitoring 21 Behavior change 63 Behavior of Concept 65 Behavior of Unity 69 BOOL arrays WORD assignment 55 BYTE_TO_BIT_DFB 87 C Change of application behavior 63 Cold start 24 Concept behavior 65 Concept EFBs CREAD REG 49 CWRITE REG 49 READ REG WRITE REG 49 Concept Macros Removing accidentally included Concept Macros 83 Concept Version 14 Configuration 15 Connection to the right bus bar 32 Consequences 71 Constants 23 DFBs 55 Continuous Register Reading CREADREG 91 Continuous Register Writing CWRITREG 99 Conversion Report 51 Conversion of the LD Output Picture 34 Conversion of the LD Picture 30 Conversion options for Concept projects 11 Conversion Procedure 79 Conversion Process 77 Converting only par
27. the output parameters Parameter Data type Meaning Y REAL Output variable QXHI BOOL Indicator X Xm QXLO BOOL Indicate x lt X1 33002515 119 LOOKUP_TABLE1_DFB Detailed description Parameter description Principle of interpolation Each two sequential inputs xi Yi represent a support point pair The first input XiYi corresponds to X1 the next one to Y1 the one after that to x2 etc For all types of input value in x found between these support points the corresponding Y output value is interpolated while the traverse progression between the support points is viewed linearly For X X4 is Y 2 Y4 For X gt Xm is Y Ym If the value at input x is higher than the value of the last support point Xm the output QXHI becomes 1 If the value at input x is less than the value of the first support point x1 the output QXLO becomes 1 Traverse progression with 1st degree interpolation Xi X Xi 1 Xm 1Xm 120 33002515 LOOKUP_TABLE1_DFB Interpolation The following algorithm applies to a point Y o Yi 1 Y i xic1 Xi for x X x 4 andi 1 m 1 Y Y x X Xi Assuming X4 Xp XX XXji 4 Xm 1 Xm The x values must be in ascending order Two consecutive x values can be identical This could cause a discrete curve progression In this instance the special case applies Y 20 5 x Yi Yi4 for Xj X Xj andi 1
28. the output pin in Concept The Concept Converter keeps the variable at the output side of the IN OUT pin and adds the variable additionally at the input side of the pin e Case 2 A link is connected to the output pin in Concept The Concept Converter removes the link creates a new variable of the needed type and writes this new variable to the start and end position of the removed link Additionally the variable is added to the input side of the pin 33002515 73 Possible application behavior change Further potential problems The following tables contain blocks where also trouble may arise in case of multi assignment because in Concept e The blocks do not write their listed output pin in case of errors inside the block e The blocks do not write their listed output pin in COLD or WARM INIT scan e The blocks write their listed output pin conditionally depending from internal mode of operation Library CONT_CTL Family Function Block Concerned Pin Conditioning DTIME OUT SCALING OUT TOTALIZER OUT INFO Controller AUTOTUNE TRI INFO PI B OUT D DEV PIDFF OUT D INFO STEP2 DEV STEP3 DEV Output Processing MS OUTD STATUS MS DB OUTD STATUS SPLRG OUT1 OUT2 Setpoint Management RAMP SP RATIO KACT SP SP_SEL LSP_MEM Library I O Management Family Function Block Concerned Pin Analog I O _SET CHANNEL Configu
29. the requirement that several write accesses to the Ox 1x register are possible during a cyclical sweep there can be differing Online behavior between Concept and Unity Pro The objects affected are e Contact to recognize positive transitions e Contact to recognize negative transitions In Concept the Old Value to recognize a transition will only be updated once per cycle In Unity Pro the Old Value will be updated during every write access Example 20X1 QX2 HA 20X2 Pl inc MW1 20X1 QX2 HA OX2 PBL inc MW2 Concept Switch QX1 from 0 gt 1 and the value of MW1 and MW2 increase Unity Pro Switch QX1 from 0 gt 1 and only the value of MW1 increases Note Use objects to recognize transitions with a certain variable only once per cycle Also see Located Variable p 22 and Unity Pro Reference Manual Use of set and reset coils leads to edge loss 40 33002515 Requirements Macros Macros name begins with will be rejected by the converter because macros cannot be implemented in Unity However if you try to import an application with macros the macros will be replaced with Dummy DFBs indicated with the in the application name Error messages regarding these Dummy DFBs will appear during the analysis of the project To correct these errors simply remove all DFBs that were created to replace macros 33002515 41 Requirements
30. to the outputs according to the output names EN and ENO can be configured as additional parameters Representation WORD variable IN WORD_AS BYTE LOW LowByte HIGH HighByte Representation EN WORD variable IN WORD AS BYTE ENO LOW LowByte HIGH HighByte 33002515 155 WORD AS BYTE DFB Representation in IL Representation in ST Parameter description Representation CAL WORD AS BYTE DFB Instance IN WORD variable LOW gt LowByte HIGH gt HighByte Representation WORD_AS BYTE E _DFB_Instance IN WORD variable LOW gt LowByte HIGH gt HighByte Description of the input parameters Parameter Data type Meaning IN WORD Input Description of the output parameters Parameter Data type Meaning LOW BYTE least significant byte HIGH BYTE most significant byte 156 33002515 WORD TO BIT DFB Type conversion 2 0 Description Function This derived function block converts one input word from the WORD data type to 16 description output values of the BOOL data type The individual bits of the word at the input are assigned to the outputs according to the output names BITO 2 BIT1 2 BIT14 214 BIT15 215 ZN EN and ENO can be configured as additional parame
31. were appearing inside the asc file itself 82 33002515 Conversion Procedure Converting only parts of a Concept application General Single DFB Single section The Concept converter is prepared to convert complete applications If only parts of a Concept application are needed provide a reduced application using Concept If a single DFB is needed make a new application with one single section and place a call to the desired DFB into this section Export the application using the menu item Export with used DFBs of the Concept own export tool DBConv Convert the resulting asc file as usual via Unity File Open If a single section is needed open the source application with Concept and delete all sections except for the desired one Open the Concept variable editor sort for usage by clicking on the column title of usage and delete all unused variables by selecting them all and pressing delete Save the reduced application with a new name and export this reduced application as usual Another way to get this is to open a new application choose the menu item export and program sections select the source application and the desired section and follow the user guidance to get a reduced application However if the section contains references to SFC steps Concept requires to export the referenced SFC section as well and the user has to find this out first Removing accidentally incl
32. 33002515 04 a brand of Schneider Electric Unity Pro 2 2 Concept Application Converter User s manual 09 2005 Telemecanique Table of Contents Part Chapter 1 Chapter 2 About the BO0kK 0 0 occcccccc eee 7 Requirements and conversion 9 Introductions Su as Ra RE ER RNINRUR hats 9 General Description of the Unity Pro Concept Converter oo oooooooo 11 General description l l ren 11 Fequiremebls o A RT e EROR wea AU Aa RR 13 Introduction c esr tee AAS Space AER M EY ua dE RONDA 13 Concept Version 0 cette nee n 14 Supported Hardware Platforms 2 0 0 0 eee eese 14 Configuration c cbe id Pe ee EDI 15 SY SM ie ee re ae de uo Rae Ru ees 17 EROS ant Medias AALS GR RE ae ere Ata 26 Programming Language SFC 0 0 cette eee 29 Programming Language LD cee tte 30 Programming Language ST IL 2 eee ttt 42 Programming Language LL984 0 cece ees 43 Programming Language FBD cece eee et tees 43 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Language differences 00 cece eee e eee eens 45 Introduction c ico ened Visca pet eA ie E a da ee 45 Functions Not Present in Unity 0 0 0 ees 46 EFB replaced by fUNCHON ooooooooocor eee 47 INOUT parameters 1 0 20 0 cece RI a N 48 Parameter type changed 2 cece eet teens 49 ANY ARRAY WORD parameters
33. ALL MAST r 26 c 68 E1194 oarameter IN2 has to be assigned ALL MAST r 26 c 68 E1194 oarameter IN1 has to be assigned 60 33002515 Language differences Solution Macros Macros Replaced by Dummy DFBs AXx EPARx Parameters To solve this problem create a variable of the pin s type and initialize it with the original values Connect this constant to the appropriate pin of each DFB instance Example 1194 parameter IN1 has to be assigned 1194 parameter IN2 has to be assigned H Macros name starting with are refused by the converter because Unity does not implement macros However if you try to import an application containing macros they will be replaced by dummy DFBs as indicated by the character in the application name While analyzing the project you will get error messages regarding these dummy DFBs To correct these errors simply remove all of the DFBs that were created as a replacements for macros AXxandEPARx parameters in Concept s extensible motion blocks are automatically invoked with the newly required array instead of with Unity s formerly present extensible pins Constants present at the Concept pins are also placed as initialization values to such arrays However variables and links must be attached manually with move blocks to these arrays 33002515 61 Language differences 62 33002515 Possible application beha
34. G READ REG READ I ErrorCode ArrayForValuesRead Representation CAL CREA ROU NO RI m PATH G REG READ PUS gt 1 STA DREG_Instance NODEADDR DeviceAddress RoutingPath SLAVEREG umberOfRegisters ArrayForValuesRead ErrorCode OffsetAddress Representation CR EADREG_Instance NODEADDR DeviceAddress ROU NO m R PATH RoutingPath SLAVEREG REG STA n US gt EG NumberOfRegisters READ ArrayForValuesRead ErrorCode OffsetAddress 33002515 93 CREADREG Parameter description Description of the input parameters Parameters Data type Meaning NODEADDR INT Device address within the target segment ROUTPATH DINT Routing path to target segment SLAVEREG DINT Offset address of the first 4x register in the slave to be read from NO_REG INT Number of registers to be read from slave Description of input output parameters Parameters Data type Meaning REG READ ANY ARRAY WORD Writing data For the file to be read a data structure must be declared as a located variable Description of the output parameters Parameters Data type Meaning STATUS WORD Error Code 94 33002515 CREADREG Mode of Functio
35. GER OF UNINTENTIONAL SYSTEM BEHAVIOR Reforce the outputs following a cold start The behavior of forced outputs 96M between Modsoft Proworx Concept and Unity Pro has changed e With Modsoft ProWORX Concept forced outputs maintain their values following a cold start e With Unity Pro forced outputs lose their values following a cold start Failure to follow this instruction can result in death serious injury or equipment damage 24 33002515 Requirements Quantum In Concept only LL984 sections can be assigned I O stations Drops This is not Remote I O possible in Concept projects with IEC conforming sections FBD LD SFC IL ST Control Unity Pro offers this option in which a logic is recreated in accordance with LL984 This logic must be entered manually however Example of a section processing order in Unity Pro Section n 2 Section n 1 RIO call u v w Section n Section n l RIO call utl w x Section n 2 RIO call u42 x y RIO x y z is the explicit I O call here e Write the outputs to the I O station x e Wait at the inputs of the I O station y e Prepare the inputs of the I O station z Note Take these new settings into consideration when structuring your project Setting Variables Unlocated variables cannot be set cyclically in Unity Pro It is possible in Concept Cyclically If you need to set variables cyclically in your project you should u
36. IN BYTE variable L variablel BIT1 gt BOOL variable2 L variable3 BIT3 gt BOOL variable4 L variable5 BIT5 gt BOOL variable6 BIT7 gt BOOL variable8 Representation BYTE TO BIT DFB Instance L variablel BIT L variable3 BIT L variable5 BIT L variable7 BIT BIT BIT BIT l 0 BOOI l 2 BOOI l 4 BOOI l 6 BOOI IN BYTE variable T1 gt BOOL variable2 3 gt BOOL variable4 5 gt BOOL variable6 BIT7 gt BOOL variables 88 33002515 BYTE_TO_BIT_DFB Parameter Description of the input parameters description Parameter Data type Meaning IN BYTE Input Description of the output parameters Parameter Data type Meaning BITO BOOL Output bit O BIT1 BOOL Output bit 1 BIT7 BOOL Output bit 7 33002515 89 BYTE_TO_BIT_DFB 90 33002515 CREADREG Continuous register reading Overview Introduction What s in this Chapter This chapter describes the CREADREG block This chapter contains the following topics Topic Page Description 92 Mode of Functioning 95 Parameter description 96 Modbus Plus Error Codes 97 33002515 91 CREADREG Description Function This derived function block reads the register area continuously It reads data from description addressed nodes via Modbus Plus EN and ENO can be configured as addition
37. ITEREG four write operations may be active at the same time It makes no difference whether blocks these operations are performed using this function block or others e g MBP_MSTR CWRITE_REG All function blocks use one data transaction path and require multiple cycles to complete a task If several WRITEREG function blocks are used within an application they must at least differ in the values of their NO REG or REG WRIT parameters The status signals DONE and ERROR report the function block state to the user program The complete routing information must be separated into two parts e inthe NODEADDR of the destination node regardless of whether it is located in the local segment or in another segment and e the routing path in case there is a link via network bridges The resulting destination address consists of these two information components The routing path is a DINT data type which is interpreted as a sequence of two digit information units It is not necessary to use 00 extensions e g both routing paths 4711 and 47110000 are valid for NODEADDR 34 the result is destination address 47 11 34 00 00 33002515 165 WRITEREG Parameter description REQ NODEADDR ROUTPATH SLAVEREG NO_REG REG WRIT DONE A rising edge triggers the write transaction The parameter can be entered as an address located variable unlocated variable or literal
38. L BYTE WORD Limit of minimum value um DWORD INT DINT UINT UDINT REAL TIME Input BOOL BYTE WORD Input DWORD INT DINT UINT UDINT REAL TIME LimitMaxim BOOL BYTE WORD Limit of maximum value um DWORD INT DINT UINT UDINT REAL TIME Description of the output parameters Parameter Data type Meaning MinimumVio BOOL Display of minimum value violation lation Output BOOL BYTE WORD Output DWORD INT DINT UINT UDINT REAL TIME MaximumVio BOOL Display of maximum value violation lation 33002515 115 LIMIT_IND_DFB 116 33002515 LOOKUP_TABLE1_DFB Traverse progression with 1 4 1st degree interpolation Overview Introduction What s in this Chapter This chapter describes the LOOKUP_TABLE1_DFB block This chapter contains the following topics Topic Page Description 118 Detailed description 120 33002515 117 LOOKUP_TABLE1_DFB Description Function description Representation in FBD Representation inLD Representation in IL This function block linearizes characteristic curves by means of interpolation The function block works with variable support point width The number of xivi inputs can be increased to 30 by modifying the size of the block frame vertically This corresponds to a maximum of 15 support point pairs The number of inputs must be even The X values must be in ascending order EN a
39. LOW LowWord HIGH HighWord Representation DINT AS WORD EN ENO DINT variable IN LOW LowWord HIGH HighWord 33002515 105 DINT AS WORD DFB Representation Representation ine CAL DINT AS WORD DFB Instance IN DINT variable LOW gt LowWord HIGH gt HighWord Representation Representation in ST DINT_AS WORD DFB Instance IN DINT variable LOW gt LowWord HIGH gt HighWord Parameter Description of the input parameters ription F descriptio Parameters Data type Meaning IN DINT Input Description of the output parameters Parameters Data type Meaning LOW WORD least significant word HIGH WORD most significant word 106 33002515 DIOSTAT Module function status DIO 11 Description Function This function provides the function status for I O modules of an I O station DIO description Each module slot is displayed as an output status bit The bit on the far left side in status corresponds to the slot on the far left side of the I O station Note If a module of the I O station is configured and works correctly the corresponding bit is set to 1 EN and ENO can be configured as additional parameters Representation Representation in FBD DIOSTAT Instance DIOSTAT LinkNumber LINK STATUS Status DropNumber DROP Representat
40. R ROUTPATH SLAVEREG NO_REG STATUS REG READ Identifies the node address within the target segment The parameter can be entered as an address located variable unlocated variable or literal Identifies the routing path to the target segment The two digit information units run from 01 64 see Mode of Functioning p 95 If the slave resides in the local network segment ROUTPATH must be set to O or must be left unconnected The parameter can be entered as an address located variable unlocated variable or literal Start of the area in the addressed slave from which the source data are read The Source area always resides within the 4x register area SLAVEREG expects the Source reference as offset within the 4x area The leading 4 must be omitted e g 59 contents of the variables or value of the literal 40059 The parameter can be entered as an address located variable unlocated variable or literal Number of registers to be read from slave processor 1 100 The parameter can be entered as an address located variable unlocated variable or literal Error code see Modbus Plus Error Codes p 97 The parameter can be specified as an address located variable or unlocated variable AnANY ARRAY WORD thatis the same size as the requested transmission must be agreed upon No REG for this parameter The name of this array is defined as a parameter If the array is defined
41. RITEREG 161 WRITE_REG 49 WRITEREG 161 33002515 173 Index 174 33002515
42. ROUTPATH DINT Routing path to target segment SLAVEREG DINT Offset address of the first 4x register in the slave to be read from NO_REG INT Number of registers to be read from slave Description of input output parameters Parameters Data type Meaning REG READ ANY ARRAY WORD Writing data For the file to be read a data structure must be declared as a located variable Description of the output parameters Parameters Data type Meaning NDR BOOL Set to 1 for one cycle after reading new data ERROR BOOL Set to 1 for one scan in case of error STATUS WORD Error Code 142 33002515 READREG Mode of Functioning Function mode Although a large number of READREG function blocks can be programmed only four of READREG DFB read operations may be active at the same time It makes no difference whether blocks these operations are performed using this function block or others e g MBP_MSTR CREAD REO All function blocks use one data transaction path and require multiple cycles to complete a task The status signals NDR and ERROR report the function block state to the user program The complete routing information must be separated into two parts e inthe NODEADDR of the destination node regardless of whether it is located in the local segment or in another segment and e the routing path in case there is a link via bridges The
43. ST r 8 c 3 E1189 converter error Overwrite happened when generating LD network see report SAFETY INTERLOCKS PLC3 MAST r 8 c 3 E1002 syntax error In the conversion report which may be opened after being imported through the hyperlink in the project tree some additional detail about the message is given 09 29 05 953 Error LD Object PTFDTP1 ENABLED with type coil overwritten The user should compare the conversion result to a printout of the original section and correct the converted section accordingly LD Execution Order Changed Different Execution Orders Note Unity s LD execution order can differ from Concept s In Unity one LD network can be completed before the next is started The converter follows the Concept execution order in graphical positioning making the original order visible to the user However since Unity calculates the order anew without the possibility of forcing it from the converter there can be execution order discrepancies 33002515 51 Language differences Concept When analyzing in Concept the execution order is calculated The result is shown in parentheses after the instance names in this image The selected block is executed in the middle of the other network even though it has no direct connection to it Concept calculates the execution order from the block position This is the origin
44. SY MAX Ethernet If TCP IP or SY MAX Ethernet is needed please use the WRITE REG block from the communication block library Note Several copies of this function block can be used in the program However multiple instancing of these copies is not possible Representation WRITEREG Instance WRITEREG StartWriteOnce REQ DONE SetAfterWritingData DeviceAddress NODEADDR ERROR SetInCaseOfError RoutingPath ROUTPATH STATUS ErrorCode OffsetAddress SLAVEREG NumberOfRegisters NO REG SourceDataArea REG WRIT REG WRIT SourceDataArea 162 33002515 WRITEREG Representation in LD Representation in IL Representation in ST Representation WRITEREG Instance WRITEREG EN ENO StartWriteOnce SetA fterWritingData REQ DONE SetInCaseOfError DeviceAddress J NODEADDR ERROR RoutingPath ROUTPATH STATUS ErrorCode OffsetAddress J SLAVEREG NumberOfRegisters NO_REG SourceDataArea _ REG WRIT REG_WRIT H SourceDataArea Representation CAL WRITEREG Instance REQ StartWriteOnce NODEADDR DeviceAddress ROUTPATH RoutingPath SLAVEREG OffsetAddress NO REG NumberOfRegisters REG WRIT SourceDataArea DONE gt SetAfterWritingData ERROR gt SetInCaseOfError STATUS
45. al parameters Note It is necessary to be familiar with the routing procedures of your network when programming a CREADREG function Modbus Plus routing path structures will be described in detail in Modbus Plus Network Planning and Installation Guide Note This function block only supports the local Modbus Plus interface no NOM If using a NOM please work with the block CREAD_REG from the communication block library Note This function block does not support TCP IP or SY MAX Ethernet If TCP IP or SY MAX Ethernet is needed please use the block CREAD REG of the communication block library Note Several copies of this function block can be used in the program However multiple instancing of these copies is not possible Representation Representation in FBD CREADREG Instance CREADREG DeviceAddress NODEADDR STATUS ErrorCode RoutingPath ROUTPATH OffsetAddress SLAVEREG NumberOfRegisters NO REG ArrayForValuesRead REG READ REG READ ArrayForValuesRead 92 33002515 CREADREG Representation in LD Representation in IL Representation in ST Representation CREADREG Instance NumberOfRegisters ArrayForValuesRead DeviceAddress RoutingPath OffsetA ddress CREADREG EN ENO NODEADDR STATUS ROUTPATH SLAVEREG NO REG RE
46. al section as it appears in Concept enn 1 ADD_INT enn 2 ADD INT enn 5 EN ENO The used variables are initialized in a way that the result of the comparator EO INT becomes true after execution of the first cycle in Concept var2 INT 2 var3 INT 3 52 33002515 Language differences Testing execution in single cycle mode in Concept shows the expected result The comparator result becomes true after the first cycle y ADD_INT EN ENO ADD_INT EN ENO 33002515 53 Language differences Unity The converted network reflects the Concept execution order in the graphical position of the blocks The image also shows the execution status stopped at a breakpoint in the first cycle The comparator EQ_ INT is already executed and will not deliver a true result because the first ADD_INT integrator block is executed after it Solution Replace the connection via a variable by a link to achieve the same result as in Concept 54 33002515 Language differences Constants Losing the Read Constants are not accepted as private DFB variables Therefore they are converted Only Behavior to initialized variables in DFBs in this way losing the read only behavior Indices in ST and IL High Resolution In addition to INT now DINT will be allowed as array index type in all areas of Unity Pro but with limited value ranges For DINT the index may only contain INT val
47. alues and the Output output value must be identical EN and ENO can be configured as additional parameters Block formula OUT IN if IN MX amp IN 2 MN OUT MN if IN MN OUT MX if IN gt MX MN IND O if IN gt MN MN_IND 1 if IN lt MN MX IND O if IN MX MX IND 1 if IN gt MX 33002515 113 LIMIT_IND_DFB Representation in FBD Representation inLD Representation in IL Representation in ST Representation LIMIT IND DFB Instance LIMIT IND DFB LimitMinimum MN MN IND MinimumvViolation Input IN OUT Output LimitMaximum MX MX IND MaximumViolation Representation LIMIT IND DFB Instance LIMIT IND EN ENO H Minimum Violation LimitMinimum MN MN_IND Input 4 IN OUT Output Maximum Violation LimitMaximum J MX MX_IND Representation CAL LIMIT IND DFB MN LimitMinimum IN INPUT MX LimitMaximum MN IND MinimumViolation OUT gt Output MX IND 2MaximumViolation Representation LIMIT IND DFB MN LimitMinimum IN INPUT MX LimitMaximum MN IND MinimumViolation OUT gt Output MX IND 2MaximumViolation 114 33002515 LIMIT_IND_DFB Parameter Description of the input parameters description P Parameter Data type Meaning LimitMinim BOO
48. anch may not be directly followed by an alternative branch Alternative This type of sequence is not permitted according to IEC 1131 Sequence Unity Pro does not support this type of sequence although it is possible in Concept The converter transfers this type of project to Unity Pro but manual modifications are subsequently required This problem can be solved by inserting an dummy step between the branches S_5_10 S_5_11 a m b S_5_12 S_5_13 9 Lnd S 5 16 Co d S 5 14 S 5 15 C m fo 33002515 29 Requirements Programming Language LD General For some programming languages there are restrictions to observe when converting a project from Concept to Unity Pro Conversion of When converting a Concept project to Unity Pro the ladder diagram LD Picture is the picture also converted which can lead to a restructuring of the picture 30 33002515 Requirements Crossovers with In Concept FFB connections between Boolean objects may be edited connections This may result in crossovers between Boolean objects Example of an FFB connection between Boolean objects coils contacts horizontal and vertical connections in Concept c1 c2 l c3 l q20 c5 l c4 l B cB c Following the conver
49. ay GET_TOD 109 READREG 139 REAL Calculating 55 REAL_TO_DINT 55 Recognize and disconnect LD Networks 36 Recognizing transitions LD 40 Redundant names DDTs and sections 51 Reference Data Editor RDE 18 Remote I O Control 25 Removing accidentally included Concept Macros 83 Requirements 13 Restrictions for LL984 15 Right bus bar Connections to 32 RIOSTAT 147 S Sections Redundant names 51 Security 17 Sequential Function Chart SFC 29 SET_BIT 47 SET_BITX 47 SET_TOD 59 151 Setting the Hardware Clock Time Of Day SET_TOD 151 Setting Variables Cyclically 25 SFC Chart Modifying 59 SFC Sequential Function Chart 29 Single Sweep Function 17 Specified execution order 17 ST code 55 ST Structured Text 42 State RAM 19 Statistics LIMIT_IND_DFB 113 Structure Alignment changed 56 Structured Text ST 42 System 17 System timer 59 T The Conversion Process 77 TIME Calculating 55 Timer 21 Topological address overlapping 56 Topological Addresses 22 Traverse progression with 1st degree interpolation LOOKUP TABLE1 DFB 117 Type Conversion BYTE TO BIT DFB 87 DINT AS WORD DFB 105 WORD AS BYTE DFB 155 WORD TO BIT DFB 157 U Unique name requirement 51 Unity behavior 69 172 33002515 Index W Weekday numbering 59 WORD assignment BOOL arrays 55 WORD_AS_BYTE_DFB 155 WORD_TO_BIT_DFB 157 Wrapping networks LD that are too wide 38 Write Register W
50. be occupied by one connection Example of a picture in Concept F 3 FBI 4 355 e A o emo ei e 6 EN ENO f A d 3 f f 5 i a c10 5 cu nu A Wl E A 35 36 of 012 CD QD f 027 f i ota E R can 20 T T m 038 f f i 34 2876 Py EV pit caa c32 34 33002515 Requirements The picture after the conversion to Unity The following actions were performed during the conversion according to the rules above e The space that is occupied by the FFB was expanded to two columns e One column each was added at the Input and Output sides of the FFB e The connections between coils contacts and the FFB were realized with FFB connections not with horizontal connections with multiple segments 33002515 35 Requirements Recognize and The converter must recognize networks in LD sections during the conversion To disconnect LD achieve this the following rules are applied Networks e An LD Network is a group of objects that are connected with each other without any other connections to other objects except the bus bar e The minimum distance is always applied to a complete column of a network This means that if an object of a column requires a certain minimum distance all other objects are also moved with a higher or equal horizontal position e If there are several networks
51. between objects must be checked to avoid unwanted implicit linking by the Unity import functions 36 33002515 Requirements The LD Network after the conversion to Unity E TN y PUE ae 33002515 37 Requirements Wrapping Since the width of the networks is expanded during the conversion the maximum networksthatare section width may be exceeded too wide To show the network that is now too wide the part of the network that reaches beyond the far right edge of the section will be shown in a new row The connections are shown as connectors Example of an LD Network in Concept c2 c2 c4 02222 Fog c3 04 c3 03333 l 04444 1 1 Vf Vf FBI 604 FBI 613 FBI 622 q50 cru cru ctu EN ENO EN ENO IENL TER d E 06668 Two cells left in original cu ak cu ae cu a network wrapping happens oF oF enm a51 R R R 1230 Pv cv L 1230 Pv cv 12333b PV cv I 38 33002515 Requirements The wrapped LD Network after the conversion to Unity 02 02 04 02222 gt CON_00001 3 gt CON_00002 gt 33002515 39 Requirements Objects to recognize transitions The different ways of handling ladder diagram LD objects in Concept calling an FB and in Unity Pro system call makes the use of State RAM variables 0x 1x register necessary Because of
52. cation within the function block of a variable declared in a VAR IN OUT block is operator interface function or the 66 33002515 Possible application behavior change EN and ENO in function blocks In out variables For function blocks also an additional Boolean EN Enable input or ENO Enable Out output or both can be provided by the manufacturer or user according to the declarations When these variables are used the execution of the operations defined by the function block shall be controlled according to the following rules 1 If the value of EN is FALSE 0 when the function block instance is invoked the assignments of actual values to the function block inputs may or may not be made in an implementation dependent fashion the operations defined by the function block body shall not be executed and the value of ENO shall be reset to FALSE 0 by the programmable controller system 2 Otherwise the value of ENO shall be set to TRUE 1 by the programmable controller system the assignments of actual values to the function block inputs shall be made and the operations defined by the function block body shall be executed These operations can include the assignment of a Boolean value to ENO 3 If the ENO output is evaluated to FALSE 0 the values of the function block outputs VAR OUTPUT keep their states from the previous invocation In out variables are a spec
53. ce of objects that cannot be converted and messages are displayed in the output window to find these objects The Unity Pro project can be analyzed using the main menu Create Analyze Project The errors displayed in the output window must be corrected manually to ensure the Unity Pro project runs correctly 78 33002515 Conversion Procedure Introduction Overview This chapter contains the procedures required to convert a Concept project into a Unity Pro project What s in this This chapter contains the following topics Chapter Topic Page Exporting a Project from Concept 80 Importing a Project into Unity Pro 81 Missing Datatypes at the Beginning of the Import 82 Converting only parts of a Concept application 83 Removing accidentally included Concept Macros 83 33002515 79 Conversion Procedure Exporting a Project from Concept General A Concept project that should be used in Unity Pro must first be exported from Concept It is then possible to use the Unity Concept Converter to make the conversion to a Unity Pro project Export project Perform the following steps to export a project Step Procedure 1 Start the Concept Converter program from the Concept program group 2 Select File gt Export to open the menu for selecting the export range Select the export range e Project with DFBs All project information including the DFBs and data
54. d to the type of the element The currents known addressing modes are e by value VAL e by address L ADR e by address Number of elements L ADR LG Table with four columns and legend EDT STRING DDT Array DDT ANY ANY Except Struct ARRAY STRING Input VAL L ADR LG L ADR LG L ADR L ADR LG L ADR LG parameter Input Output ADR L ADR LG L ADR LG L ADR L ADR LG L ADR LG parameter Output VAL VAL L ADR LG VAL L ADR LG L ADR LG parameter Public VAL VAL VAL Variable Private VAL VAL VAL Variable 1 Except for BOOL type the addressing mode is VAL The following rules must be taken into account while invoking a Function Block instance e All input output parameters have to be filled e All input parameters using the L ADR or L ADR LG addressing modes have to filled e All output parameters using the L ADR or L ADR LG addressing modes have to filled All other kind of parameters could be omitted while Function Block Instance invocation For input parameters the following rules are applied in the given order e The values of the previous invocation are used e f no previous invocation the initial values are used 70 33002515 Possible application behavior change Consequences Potential problems Because of this architectural change there might be trouble when an application is migrated from Concept to Unity in the
55. dule rack 1 of the I O station and can be monitored at bit 1 of the first status word for the I O station Note The ASCII keyboard communication status can be monitored with the error numbers in the ASCII read write instructions DIO status DIO_STAT General information Note The information corresponds to status table words 172 to 277 in the PLC status dialog The words contain the I O communication status DIO status Words 1 to 10 are global status words Of the remaining 96 words three words are allocated to each of the up to 32 I O stations wordl saves the switch on error numbers This word is always O when the system is running If an error occurs the PLC does not start but generates a PLC stop status word5 from PLC_ STAT The conditions are true when the bits are set to 1 132 33002515 PLCSTAT Switch on error numbers DIOSTATE wordl The conditions are true when the bits are set to 1 Switch on error numbers Code Error Meaning location of error 01 BADTCLEN Traffic cop length 02 BADLNKNUM RIO link number 03 BADNUMDPS I O station number in traffic cop 04 BADTCSUM Traffic cop checksum 10 BADDDLEN I O station descriptor length 11 BADDRPNUM I O station number 12 BADHUPTIM I O station stop time 13 BADASCNUM ASCII port number 14 BADNUMODS Module numb
56. e GI Concept value ET TOD reads Unity value and returns to User the Note We do not recommend that you mix GI with the use of system words e g SW49 in the same application ET TOD and SET TOD programming Concept s system timer was located on a user defined register word 16 bit and incremented at 10 ms Unity provides an incremental timer with 100 ms updating 3SW18 A 10 ms timer can be logically created using the FRE ERUN function sec timer 33002515 59 Language differences Initial Values Definition of Initial Values Pins to be Connected Concept allows the initial values on DFB pins of a structured array to be defined Unity forbids this option for pins of array type This option is reserved for output pins of structure type The converter reflects this with the following error message in the conversion log amp jCConv ALLDFB 20030409 230133 log Notepad File Edit Format Help 23 02 17 140 Config 140CPU534144 Quantum 232022176203 gt Error Rallo 0 23 02 17 203 gt Error Cannot convert initial values of call 23 02 17 203 Modify Inst calcul of SECT CTRL to calcul_Sctl Error Cannot convert initial values of call by reference data pin Add PV inl At the same time Unity enforces pins of array type and input pins of structured type to be connected which in this case leads to analysis errors
57. e output of the disabled SEL EF gets an undefined value in this case 0 Therefore the output of EQ INT function block has become true Solution If the EN of the SEL is set to false the ENO of the EQ INT is also set to false but the connected output variable keeps its value from the previous cycle A variable is mandatory to be used to retain the network results in the case an EF will be disabled Note The use of a variable is mandatory to retain network results in case an EF becomes disabled 58 33002515 Language differences SFC Section Retains its State When Performing an Online Modification Online Modifications Without Resetting In Unity it is possible to do online modifications of an SFC chart without resetting it The SFC chart retains its state and will continue the execution Note In Concept the online modification of an SFC chart usually results in the resetting of the chart Weekday Numbering Different Numbering SET TOD GET TOD System Word SW49 System Timer Concept Unity In Unity the numbering of weekdays is different than Concept Number Unity Concept 1 Monday Sunday 7 Sunday Saturday Function blocks SET_TOD and Gi work in both directions ET_TOD will be converted to Unity as DFBs which Because SET_TOD expects a Concept numbered weekday and translates it as a Unity coded value Also th
58. eceived 80 Unexpected response received F001 Wrong destination node specified for MSTR operation 98 33002515 CWRITREG Continuous register writing Overview Introduction What s in this Chapter This chapter describes the CWRITREG block This chapter contains the following topics Topic Page Description 100 Mode of Functioning 103 Parameter description 104 33002515 99 CWRITEREG Description Function This derived function block writes continuously to the register area It transfers data description from the PLC via Modbus Plus to a specified slave destination processor EN and ENO can be configured as additional parameters Note When programming a CWRITREG function you must be familiar with the routing procedures used by your network Modbus Plus routing path structures will be described in detail in Modbus Plus Network Planning and Installation Guide Note This function block only supports the local Modbus Plus interface no NOM If using a NOM please work with the CWRITE REG block from the communication block library Note This function block does not support TCP IP or SY MAX Ethernet If TCP IP or SY MAX Ethernet is needed please use the CWRITE REG block from the communication block library Note Several copies of this function block can be used in the prog
59. ed data types In Concept data structure elements begin at BYTE limits In Unity Pro data structure elements begin at WORD limits Example of a derived data type TYPE SKOE STRUCT PAR1 BOOL PAR2 BYTE PAR3 BOOL PAR4 WORD PAR5 BOOL PAR6 WORD END_STRUCT END TYPE The derived data types are stored in the state RAM when using Concept PAR2 PAR1 Y Y Word 1 215 214 213 212 211 910 99 28 27 26 25 24 23 22 21 90 PARA LSB PAR3 Y Y Word 2 215 214 213 212 211 910 99 28 97 96 25 24 23 22 21 90 PARS PARA MSB Y Y Word 3 215 214 213 212 211 910 99 28 27 96 25 94 93 92 21 20 PAR6 MSB PARE LSB Y Word 4 215 214 913 212 911 910 99 28 97 26 25 24 23 22 21 90 20 33002515 Requirements Timer Date Battery Monitoring The same derived data types are stored in the state RAM when using Unity Pro PAR2 PAR1 Y Y Word 1 2915 914 213 2912 211 210299 28 97 96 295 94 93 292 91 90 PAR3 Y Word 2 2915 914 213 912 211 910 99 28 97 26 25 24 93 92 91 20
60. ed BOOL variables 22 33002515 Requirements Constants Mx Register Constants in Concept are converted to write protected variables in Unity Pro Unity Pro does not provide constants Comparable functionality is achieved using write protected variables In Concept the Ox registers are not buffered They are reset to zero with every warm restart In Unity Pro the Mx registers are buffered RETENTIVE VAR_RETAIN i e Conform to IEC Do not use the possibility to set the Ox register to zero on every warm restart if you use a project in Concept that you want to convert to Unity Pro Note If you require non buffered behavior define the warm restart event with the SYSSTATE function block and explicitly copy the value 0 zero to the Mx register 33002515 23 Requirements Forced outputs M WARNING DANGER OF UNINTENTIONAL SYSTEM BEHAVIOR Do not relay on the Memory Protect switch The behavior of forced outputs 96M between Modsoft Proworx Concept and Unity Pro has changed e With Modsoft ProWORX Concept you cannot force outputs when the Memory Protect switch of the Quatum CPU is set to the On position e With Unity Pro you can force outputs even when the Memory Protect switch of the Quatum CPU is set to the On position Failure to follow this instruction can result in death serious injury or equipment damage WARNING DAN
61. ept D PRE D GRP the extensible inputs IN1 INx are gathered together in oneinput This is implemented using a nested logic AND link In the FBD language the AND block is positioned at the same location as the DIAGNO block by the converter This overlap must be resolved manually by the user The SKP RST SCT FALSE and LOOPBACK EFBs cannot be used in Unity Pro The FUZZY library is no longer supported by Unity Pro 26 33002515 Requirements HANDTABL The HANDTABL library is no longer supported by Unity Pro library EXPERTS library The following Concept EFBs are converted to DFBs in Unity Pro e ERT_TIME SIMTSX22 EFBs from the EX family EFBs from the MVB family EFBs from the ULEX family Note These DFBs created in Unity Pro have all the Concept parameters but no programmatic content An error message is displayed that says that the programmatic content for these DFBs must still be created The data structures DPM_TIME and ERT_10_TTAG from the time stamp module 140 ERT 854 10 have been changed The MS element was broken up into MS_LSB and MS_MSB For more information about this see State RAM assignment using derived data types p 20 Outputs which describe data structures must be assigned event variables using the gt assignment operator within the parameter brackets in the ST and IL languages This happens automatically during conversion from Unity 2 0 onwards The functionalit
62. er in I O station 15 PRECONDRP I O station is already configured 16 PRECONPRT Port is already configured 17 TOOMNYOUT More than 1024 output locations 18 TOOMNYINS More than 1024 input points 20 BADSLTNUM Module slot address 21 BADRCKNUM Rack address 22 BADOUTBC Number of output bytes 23 BADINBC Number of input bytes 25 BADRF1MAP First reference number 26 BADRF2MAP Second reference number 27 NOBYTES No input or output bytes 28 BADDISMAP 1 0 marker bit not at 16 bit limit 30 BADODDOUT Unmated odd output module 31 BADODDIN Unmated odd input module 32 BADODDREF Unmated odd module reference 33 BAD3X1 XRF 1x reference after 3x register 34 BADDMYMOD Dummy module reference already in use 35 NOT3XDMY 3x module is not a dummy module 36 NOT4XDMY 4x module is not a dummy module 40 DMYREAL1X Dummy module then real 1x module 41 REALDMY1X Real then 1x dummy module 42 DMYREAL3X Dummy module then real 3x module 43 REALDMY3X Real then 3x dummy module 33002515 133 PLCSTAT Status of cable A DIOSTATE word2 word3 word4 Bit allocation for word2 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Bit Allocation 1 8 Counts frame fields 9 16 Counts DMA receiver overflows Bit allocation for word3
63. es the modification meets better the reality since it is read from the concerned output pins and so they are in fact IN OUTs The following tables summarize the EFBs where at least one pin was changed from OUT to IN OUT during migration from Concept to Unity Library CONT_CTL Family Function Block Concerned Pin Controller PI B OUT PIDFF OUT Output Processing MS OUT Setpoint Management SP SEL SP Library Motion Family Function Block Concerned Pin MMF Start CFG CP F MFB CFG BLK CFG CP V MFB CFG BLK CFG CS MFB CFG BLK CFG FS MFB CFG BLK CFG IA MFB CFG BLK CFG RA MFB CFG BLK CFG SA MFB CFG BLK DRV DNLD MFB DRV UPLD MFB IDN CHK MFB IDN XFER MFB MMF BITS MFB MMF ESUB MFB MMF INDX MFB MMF JOG MFB MMF MOVE MFB MMF RST MFB MMF SUB MFB MMF USUB MFB 72 33002515 Possible application behavior change Library Obsolete Lib Family Function Block Concerned Pin CLC_PRO ALIM Y COMP_PID Y YMAN_N OFF_N SP_CAS_N DERIV Y INTEG Y LAG Y LAG2 Y LEAD_LAG Y PD_OR_PI Y Pl Y PID Y PID_P Y PIP Y PPI Y VLIM Y Extensions R2T OFF Compatibility SRCH INDEX T2T OFF Concept The Concept Converter normally handles the layout change in the following way Converter when a Concept application is imported into Unity behavior e Case 1 A variable is connected to
64. et segment SLAVEREG DINT Offset address of the first 4x register in the slave to be written to NO_REG INT Number of registers to be written from slave Description of input output parameters Parameters Data type Meaning REG WRIT ANY ARRAY WORD Source data field A data structure must be declared as a located variable for the source file Description of the output parameters Parameters Data type Meaning STATUS WORD Error Code 102 33002515 CWRITEREG Mode of Functioning Function mode of CWRITREG blocks Although an unlimited number of CWRITREG function blocks can be programmed only four write operations may be active at the same time It makes no difference whether these operations are performed using this function block or others e g MBP_MSTR WRITEREG All function blocks use one data transaction path and require multiple cycles to complete a task If several CWRITREG function blocks are used within an application they must at least differ in the values of their NO REG or REG WRIT parameters The complete routing information must be separated into two parts e inthe NODEADDR of the destination node regardless of whether it is located in the local segment or in another segment and e the routing path in case there is a link via network bridges The resulting destination address consists
65. expects the destination address as an offset within the 4x area The leading 4 must be omitted e g 59 contents of the variables or value of the literal 40059 The parameter can be entered as an address located variable unlocated variable or literal Number of registers to be written to slave processor 1 100 The parameter can be specified as an address located variable unlocated variable or literal An ANY ARRAY WORD that is the same size as the planned transmission must be agreed upon 2 No REG for this parameter The name of this array is defined as a parameter If the array is defined too small then only the amount of data is transmitted that is present in the array The parameter must be defined as a located variable If MSTR error code is returned see Modbus Plus Error Codes p 97 The parameter can be specified as an address located variable or unlocated variable 104 33002515 DINT AS WORD DFB Type conversion 1 0 Description Function description Representation in FBD Representation in LD This derived function block converts one input word from the DINT data type to 2 output values of the WORD data type The individual words of the DINT input are assigned to the outputs according to the output names EN and ENO can be configured as additional parameters Representation DINT_AS WORD DINT variable IN
66. fied as an address located variable unlocated variable or literal Number of registers to be read from slave processor 1 100 The parameter can be specified as an address located variable unlocated variable or literal Transition to ON state for one program cycle signifies receipt of new data ready to be processed The parameter can be specified as an address located variable or unlocated variable Transition to ON state for one program cycle signifies detection of a new error The parameter can be specified as an address located variable or unlocated variable 144 33002515 READREG STATUS Error code see Modbus Plus Error Codes p 97 The parameter can be specified as an address located variable or unlocated variable REG READ An ANY ARRAY WORD that is the same size as the requested transmission must be agreed upon 2 NO REO for this parameter The name of this array is defined as a parameter If the array is defined too small then only the amount of data is transmitted that is present in the array The parameter must be defined as a located variable 33002515 145 READREG 146 33002515 RIOSTAT Module function status RIO 1 7 Description Function This function block provides the function status for I O modules of an I O station description local remote 1 0 Quantum I O or 800 I O can be used An output STATUSx is allocated to each rack Each mod
67. following cases e Multi assignment of connected output variables In Concept there are function blocks mainly in the closed loop control area which do not write their output values to the connected variables in special operating modes manual mode In these special modes it was possible to write the variables from other locations inside the application This will work in Unity only if the variables are written after the function block call If they are written before the function block call the copy process from the instance data to the connected variables will overwrite this value with the old value from the instance data Controlling output variables by animation table or HMI If a block doesn t write his outputs in special operating modes like manual mode see above it was possible to modify the connected output variables by animation tables or HMI This will no longer work in Unity since the copy process from the instance data to the connected variables of the function block will overwrite the modified value with the old value from the instance data 33002515 71 Possible application behavior change Changed EFB layout To avoid major problems a lot of function blocks mainly in the Motion and CLC area were changed in their layout from Concept to Unity to ensure a correct mode of operation in the intended way for the function blocks The concerned pins were changed from type OUT to IN OUT In nearly all cas
68. from Concept to Unity is as exact as possible To achieve this the following rules are applied Rules for Object Positioning The distance between two objects must be at least one cell When two FFBs are connected the minimum distance must equal the number of cells of the first FFB s width The cells in Unity are smaller If an FFB partially occupies another cell an additional cell is required for the FFB If an object contact or coils has a vertical connection OR Link this vertical connection will be located at the end of the cell of the object An additional cell is required if e avertical connection OR Link with an INPUT FFB exists e the source FFB has output variables e the target FFB has input variables A coil may not be directly connected to the left bus bar Rules for the conversion of FFB connections FFB connections between variables constants and FFBs will be ignored In these cases Unity will automatically create a connection Purely horizontal FFB connections between objects that are not FFBs will be replaced with horizontal connections with multiple segments When two OR objects are connected a horizontal connection is first connected to the right side of the source OR object An FFB connection will then be created between this horizontal connection and the target object This occurs because the two OR objects would otherwise be combined during the import into Unity Each point of the left bus bar can only
69. g EL ia EC eI RO eee ae E CLE 157 WRITEREG Write register lt lt ooooooommoo 161 OVeIVI6W 1 1 a La eL pk p pU shang eden eere Ea 161 DDescriptiorii s uu sessed ia Y Ride ba kde 162 Mode of Functioning 0 00 e eee eee III 165 Parameter description oooooooocooocoo ene 166 REC at eal ae let A o o net fac tees 169 About the Book A At a Glance Document Scope Validity Note Related Documents This document describes the functionality and performance scope of the Concept Application Converter for Unity Pro This document is valid for Unity Pro starting from Version 2 2 The data and illustrations found in this document 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 Title of Documentation Reference Number Unity Pro Software Reference Manual Unity Pro Software Operating Modes Manual 33002515 About the Book Product Related Warnings User Comments 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 e
70. gt ErrorCode Representation WRITEREG Instance REQ StartWriteOnce ODEADDR DeviceAddress ROUTPATH RoutingPath SLAVEREG OffsetAddress NO REG NumberOfRegisters REG WRIT SourceDataArea DONE gt SetAfterWritingData ERROR gt SetInCaseOfError STATUS gt ErrorCode 33002515 163 WRITEREG Parameter description Description of input parameters Parameter Data type Meaning REQ BOOL With a rising edge at the REQ input this function block writes a register area from the PLC to an addressed slave via Modbus Plus NODEADDR INT Device address within the target segment ROUTPATH DINT Routing path to target segment SLAVEREG DINT Offset address of the first 4x register in the slave to be written to NO_REG INT Number of registers to be written from slave Description of input output parameters Parameters Data type Meaning REG WRIT ANY ARRAY WORD Source data field A data structure must be declared as a located variable for the source file Description of the output parameters Parameters Data type Meaning DONE BOOL Set to 1 for one scan after writing data ERROR BOOL Set to 1 for one scan in case of error STATUS WORD Error Code 164 33002515 WRITEREG Mode of Functioning Function mode Although a large number of WRITEREG function blocks can be programmed only of WR
71. ial kind of variable used with program organization units POUs i e functions function blocks and programs They do not represent any data directly but reference other data of the appropriate type They are declared by use of the VAR IN OUT keyword In out variables may be read or written to Inside a POU in out variables allow access to the original instance of a variable instead of a local copy of the value contained in the variable 33002515 67 Possible application behavior change Function block invocation A function block invocation establishes values for the function block s input variables and causes execution of the program code corresponding to the function block body These values may be established graphically by connecting variables or the outputs of other functions or function blocks to the corresponding inputs or textually by listing the value assignments to input variables If no value is established for a variable in the function block invocation a default value is used Depending on the implementation input variables may consist of the actual variable values addresses at which to locate the actual variable values or a combination of the two These values are always passed to the executing code in the data structure associated with the function block instance The results of function block execution are also returned in this data structure Hence if the function block invocation is implemen
72. in the same row in Concept the following network will be moved vertically until it no longer occupies the same rows with the preceding network e To avoid undesired automatically created FFB connections the space that is occupied by an FFB and its connection space will be checked for crossovers In the event of crossovers the following objects will be moved horizontally Example of an LD Network in Concept with crossovers horizontally eniarged Fale cruo e en eno O POLOS cruD qu wr TES EN eno ES eo of EN eno JR RS son eo o 4s af uo EN eno R ri sev evp FLS et 68 31 ih es LOOKUP_TABLET ir N o w ADD_DINT CER H EN Eno m m Sev even eno TON 84 dx re H EN ENO j me DIV REAL Feo q RE wni LOOKUP_TABLEI ar jw afte ENO pS xw oof EN Eno im aH H TRI Mex Y uid INTEGRATORI Es FAO 10 CERE 8 18 LOOKUP TABLET et al EN ENDS TON P TIME DIV REAL aig Hen ENO pana ooj mu EN ENO EN eno 4x yes IL sar qm aH E Fels SELI om LOOKUP TABLET 4x Y ooo qe by Jue mob en eno oan owx H Pause nex YE ymax omn reo 12 Lookur raser 200x008 ow mn EN Eno Jue mot Lan A specific challeng is that it is not sufficiet to rely only on connected m E objects also proximity
73. ing Language FBD General For some programming languages there are restrictions to observe when converting a project from Concept to Unity Pro Macros When converting a Concept project to Unity Pro sections created using macros are also converted These sections can also be manually copied and modified 33002515 43 Requirements 44 33002515 Language differences Introduction Overview What s in this Chapter This chapter contains information about language differences This chapter contains the following topics Topic Page Functions Not Present in Unity 46 EFB replaced by function 47 INOUT parameters 48 Parameter type changed 49 ANY_ARRAY WORD parameters 50 Unique Naming required 51 Incomplete LD Generation 51 LD Execution Order Changed 51 Constants 55 Indices in ST and IL 55 Calculate with TIME and REAL 55 WORD Assignments to BOOL Arrays 55 Topological Address Overlapping 56 Structure Alignment Changed 56 Undefined Output on Disabled EFs 57 SFC Section Retains its State When Performing an Online Modification 59 Weekday Numbering 59 System Timer 59 Initial Values 60 Macros 61 33002515 45 Language differences Functions Not Present in Unity DFB wrapper Manual correction Functions from Concept that are not present in Unity get a DFB wrapper if they are called in ST sections e g
74. ion Representation in LD DIOSTAT Instance DIOSTAT EN ENO LinkNumber LINK STATUS Status DropNumber DROP 33002515 107 DIOSTAT Representation in IL Representation in ST Parameter description Representation CAL DIOSTAT Instance STATUS gt Status LINK LinkNumber DROP DropNumber Representation DIOSTAT Instance STATUS gt Status LINK LinkNumber DROP DropNumber Description of the input parameters Parameter Data type Meaning LINK UINT Link No 0 2 DROP UINT I O station no 1 64 Description of the output parameters Parameter Data type Meaning STATUS WORD Status bit pattern See Function description p 107 of an I O station 108 33002515 GET_TOD Reading the hardware clock Time Of Day 1 2 Description Function description Representation in FBD This function block searches together with the other function blocks in the HSBY group the configuration of the respective PLC for the necessary components These components always refer to the hardware actually connected Therefore the correct functioning of this function block on the simulators cannot be guaranteed The GET_TOD function block reads the hardware clock if relevant registers are provided with this configuration If these registers are not present the TOD_CNF output is set to 0
75. le7 TOD_CNF gt ClockReady Representation DW DAY Byte v T SET TOD Instance S PULSE InputAcceptedFlag EK DayOfWeek MONTH Byte variable2 ariable3 YEAR Byte variable4 HOUR Byte variable5 S ECO D Byte variable INUTE Byte variable6 TOD CNF ClockReady 152 33002515 SET_TOD Parameter description Description of the input parameters Parameters Data type Meaning S PULSE BOOL 0 gt 1 the input values are accepted and written into the clock D WEEK BYTE Day of week 1 Sunday 7 Saturday MONTH BYTE Month 1 12 DAY BYTE Day 1 31 YEAR BYTE Year 0 99 HOUR BYTE Hour 0 23 MINUTE BYTE Minute 0 59 SECOND BYTE Second 0 59 Description of the output parameters Parameters Data type Meaning TOD CNF BOOL 1 MW register 4x for the hardware system clock was found and the clock is operational 0 Time is currently being set or hardware clock was not found 33002515 153 SET_TOD 154 33002515 WORD_AS_BYTE_DFB Type conversion 1 9 Description Function description Representation in FBD Representation in LD This derived function block converts one input word from the WORD data type to 2 output values of the BYT E data type The individual bytes of the word at the input are assigned
76. lectronic 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 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 use Schneider Electric software or approved software with our hardware products may result in injury harm or improper operating results Failure to observe this product related warning can result in injury or equipment damage We welcome your comments about this document You can reach us by e mail at techpub schneider electric com 33002515 Requirements and conversion Introduction Overview What s in this Part This section contains requirements and information about the conversion This part contains the following chapters Chapter Chapter Name Page 1 General Description of the Unity Pro Concept Converter 11 2 Requirements 13 3 Language differences 45 4 Possible application behavior change 63 5 The Conversion Process 77 6 Conversion Procedure 79 33002515 Requirements and conversion 10 33002515 General Description of the Unity Pro Concept Converter 1
77. ncept is determined first of all by how the FFBs are positioned If the FFBs are then linked graphically the execution order is determined by the data flow After this the execution order can be changed based on the intention In Unity Pro after conversion it is not possible to see in what order the FFBs were positioned Therefore whenever the order cannot be determined unambiguously from the data flow rule alone the order is defined by the Concept project The defined execution sequence is shown by means of a rectangle with the step number in the upper right hand corner of the FFB The single sweep function is no longer supported by Unity Pro The corresponding functionality can be realized in Unity Pro using the Debug function Breakpoints 33002515 17 Requirements EFB Download Reference Data Editor RDE Global Variable Values Using Concept all platform dependent EFBs can be placed at any time and loaded in all PLC platforms Any errors during runtime are written to the message memory In Unity Pro only valid EFBs can be placed Download to the PLC is only possible if the EFBs used are consistent with the PLC platform RDE tables created in Concept are converted to Unity Pro when they are placed in the same directory as the Concept ASCII file Because of different restart behaviors after a power failure it is possible that the global variable states of two PLCs that restart differently are not
78. nd ENO can be configured as additional parameters Representation LOOKUP_TABLE1 DFB Instance LOOKUP_TABLE1_DFB InputVariable X Y OutputVariable X Coord 1 SupportPoint XiYil QXHI IndicatorSignalX gt Xm Y Coord 1 SupportPoint XiYi2 QXLO IndicatorSignalX X1 Representation LOOKUP TABLE DFB Instance LOOKUP TABLE DFB EN ENO InputVariable X Y OutputVariable IndicatorSignalX gt Xm X Coord 1 SupportPoint 4 XiYil QXHI IndicatorSignalX X1 Y Coord 1 SupportPoint XiYi2 QXLO Representation CAL LOOKUP TABLE1 DFB Instance X InputVariable XiYil X Coord 1 SupportPoint XiYi2 Y Coord 1 SupportPoint Y gt OutputVariable OXHI gt IndicatorSignalX gt Xm OXLO gt IndicatorSignalX lt X1 118 33002515 LOOKUP_TABLE1_DFB Representation in ST Parameter description Representation LOOKUP_TABLI OXHI gt IndicatorSignalX gt Xm El DFB Instance X InputVariable XiYil X Coord 1 SupportPoint XiYi2 Y Coord 1 SupportPoint Y gt OutputVariable OXLO gt IndicatorSignalX lt X1 Description of the input parameters Parameter Data type Meaning XiYil REAL X coordinate 1 Support point XiYi2 REAL Y coordinate 1 Support point XiYin REAL X coordinate m 2 Support point XiYim REAL Y coordinate m 2 Support point X REAL Input variable Description of
79. ndby system is integrated into the CPU 671 60 module The Concept converter replaces the CPU from Concept with the new Hot Standby CPU 671 60 and the Concept Hot Standby Module 140 CHS 111 00 is removed All Hot Standby parameters will be transferred to the Unity application Note As the CPU in Concept only requires one slot but the new Unity CPU requires two overlaps in the rack my arise These must be resolved manually by the user 16 33002515 Requirements System Security Program Execution Specified execution order Single Sweep Function The access authorizations defined in Concept are not converted to Unity Pro Security under Unity Pro does not refer to the corresponding installation as it does under Concept Program execution using Concept and Unity Pro are different It can lead to different behavior during the first program run after a restart Program execution for Concept 1 Write the outputs program run n 1 2 Read the inputs program run n 3 Program processing Program execution for Unity Pro 1 Read the inputs 2 Program processing 3 Write the outputs Example In Concept you have assigned a 4x register to a digital output and stopped the PLC when the value is true After a restart the value remains True during the first program run even if you have modified the process conditions The execution order in the function block language in Co
80. ning Function mode of CREADREG blocks Although a large number of CREADREG function blocks can be programmed only four read operations may be active at the same time It makes no difference whether these operations are performed using this function block or others e g MBP_MSTR READREG All function blocks use one data transaction path and require multiple cycles to complete a task The complete routing information must be separated into two parts e inthe NODEADDR of the destination node regardless of whether it is located in the local segment or in another segment and e the routing path in case there is a link via network bridges The resulting destination address consists of these two information components The routing path is a DINT data type which is interpreted as a sequence of two digit information units It is not necessary to use 00 extensions e g both routing paths 4711 and 47110000 are valid for NODEADDR 34 the result is destination address 47 11 34 00 00 Note This function block puts a heavy load on the network The network load must therefore be carefully monitored If the network load is too high the program logic should be reorganized to work with the READREG function block which is a variant of this function block that does not operate in continuous mode but is command driven 33002515 95 CREADREG Parameter description NODEADD
81. number of elements required by the application In case the application defined data structures that are mapped to registers that describe the data to be worked with significant work to redefine this back to a one dimensional WORD array is required However this is necessary for Unity V1 0 for example Echanges CR2 MAST r 42 c 7 E1092 data types do not match CREADREG REG READ ANY ARRAY WORD lt gt table rec cr2 peer Table Example XXXXXXXXXXXXXXXXXXXXXXXXXXXX Lecture depuis API CR2 XXXXXXXXXXXXXXXXXXXXXXXXXXXX Fa 126 8 defaut rec c2 table rec c2 mmm The Unity converter V2 0 will change these EFB parameter types to ANY avoiding this problem 50 33002515 Language differences Unique Naming required Unique name In Concept applications section names can have the same name as a DDT That is not the case in Unity The converter checks section names to see if they are redundant of DDT names If so the converter appends _Sect to the section name Incomplete LD Generation LD Generation Not Done Completely Details in Conversion Report In some cases LD generation cannot be completed This can happen when the algorithm allows an object that requires the same position as an existing object In these cases the pre existing object is overwritten Messages are issued to make you aware of this SAFETY INTERLOCKS PLC3 MA
82. nverted application works in the intended way 64 33002515 Possible application behavior change Concept behavior Parameters are handled by reference Function block code IEC demands Function block In Concept all function block parameters are handled by reference means the blocks receives a pointer to the data of every function block pin and works directly on the connected variable Connected variables Connected input variable Connected output variable Instance data EFB Code Therefore in Concept it is up to the function block code to decide whether to behave IEC compliant or e to write input data or e to read output data or e not to write output data For the purposes of programmable controller programming languages a function block is a program organization unit which when executed yields one or more values Multiple named instances copies of a function block can be created Each instance shall have an associated identifier the instance name and a data structure containing its output and internal variables and depending on the implementation values of or references to its input variables All the values of the output variables and the necessary internal variables of this data structure shall persist from one execution of the function block to the next Therefore invocation of a function block with the same arguments in
83. of these two information components The routing path is a DINT data type which is interpreted as a sequence of two digit information units It is not necessary to use 00 extensions e g both routing paths 4711 and 47110000 are valid for NODEADDR 34 the result is destination address 47 11 34 00 00 Note This function block puts a heavy load on the network The network load must therefore be carefully monitored If the network load is too high the program logic should be reorganized to work with the WRI TEREG function block which is a variant of this function block that does not operate in continuous mode but is command driven 33002515 103 CWRITEREG Parameter description NODEADDR ROUTPATH SLAVEREG NO_REG REG WRIT STATUS Identifies the node address within the target segment The parameter can be specified as an address located variable unlocated variable or literal Identifies the routing path to the target segment The two digit information units run from 01 64 see Mode of Functioning p 103 If the slave resides in the local network segment ROUTPATH must be set to 0 or must be left unconnected The parameter can be specified as an address located variable unlocated variable or literal Start of the destination area in the addressed slave to which the source data are written The destination area always resides within the 4x register area SLAVEREG
84. ontains the RIO status I O status for Quantum DIO STAT DIOSTATE Contains the DIO status I O communication status Note The name of this output is confusing This output only relates to the remote I O Drop Status Information S908 and not to the Distributed I O status To read the distributed I O status use the function block DIOSTAT See DIOSTAT Module function status DIO p 107 33002515 125 PLCSTAT Derived Data Types Element Description of the PLCSTATE element description Element Data t Meani PLCSTATE ype Ag wordl WORD CPU status word2 WORD Hot Standby Status word3 WORD PLC status word4 WORD RIO Status word5 WORD Reserve word6 WORD Reserve word7 WORD Reserve words WORD Reserve word9 WORD Reserve word10 WORD Reserve wordll WORD Reserve Element Description of the RIOSTATE element description Element Data type Meanin RIOSTATE yP 9 wordl WORD I O station 1 module rack 1 word2 WORD I O station 1 module rack 2 word5 WORD I O station 1 module rack 5 word6 WORD I O station 2 module rack 1 word7 WORD I O station 2 module rack 2 word160 WORD I O station 32 module rack 5 126 33002515 PLCSTAT Element Description of the DIOSTATE element description Element Data type Meanin
85. orrectly 5 To ensure that a project contains no more errors select the menu command Build Analyse Project again 33002515 81 Conversion Procedure Missing Datatypes at the Beginning of the Import General Concept system data types Concept dty files If the dialog at the beginning of the import claims for unknown DDTs search for local type declarations in this DDT and find out which of these are undefined Further types unused but present in the opened asc file are reported as unknown in a dialog during import This happens for Concept system data types which are considered for Concept to be always presented and therefore not included in the export by Concept The Converter automatically includes the standard system data types of Concept individually if they are needed They are part of the converter command and include file CConv xml present in the execution directory of Unity If the read only flag is removed this file can be extended to include additional data types for user EFB libraries Such data type files beyond the global local ones are placed in the lib subdirectory of Concept to be merged into the Concept application but these data types do NOT appear in the Concept export file The V1 1 version of the Concept converter will have the capability to add Concept dty files which are stored in the same directory as the asc file to the converted application as if their content
86. put parameters description Parameter Data type Meaning IN WORD Input Description of the output parameters Parameter Data type Meaning BITO BOOL Output BITO BIT1 BOOL Output BIT1 BIT15 BOOL Output BIT15 33002515 159 WORD_TO_BIT_DFB 160 33002515 WRITEREG Write register 21 Overview Introduction What s in this Chapter This chapter describes the WRITE REG block This chapter contains the following topics Topic Page Description 162 Mode of Functioning 165 Parameter description 166 33002515 161 WRITEREG Description Function description Representation in FBD With a rising edge at the REQ input this function block writes a register area from the PLC to an addressed slave via Modbus Plus EN and ENO can be configured as additional parameters Note When programming a WRITEREG function you must be familiar with the routing procedures used by your network Modbus Plus routing path structures will be described in detail in Modbus Plus Network Planning and Installation Guide Note This derived function block only supports the local Modbus Plus interface no NOM If using a NOM please work with the WRITE REG block from the communication block library Note This derived function block also does not support TCP IP or
87. put variables need not always yield the same output values 33002515 65 Possible application behavior change Assignment of a value Assignment of a value to an output variable of a function block is not allowed except from within the function block The assignment of a value to the input of a function block is permitted only as part of the invocation of the function block Unassigned or unconnected inputs of a function block shall keep their initialized values or the values from the latest previous invocation if any Allowable usage of function block inputs and outputs are summarized in table below using the function block FF75 of type SR The examples are shown in the ST language Usage Inside function block Outside function block Input read IF IN1 THEN Not allowed 1 2 Input Not allowed FB INST IN1 A IN2 B assignment Output read OUT OUT AND NOT IN2 C FB INST OUT Output OUT 1 Not allowed assignment In out read IF INOUT THEN IF FB1 INOUT THEN In out INOUT OUT OR IN1 3 FB_INST INOUT D assignment permitted 1 Those usages listed as not allowed in this table could lead to implementation dependent unpredictable side effects 2 Reading and writing of input output and internal variables of a function block may be performed by the communication function programming testing and monitoring functions defined in IEC 61131 1 3 Modifi
88. ram However multiple instancing of these copies is not possible Representation Representation Ir FBD CWRITREG Instance CWRITREG DeviceAddress j NODEADDR STATUS ErrorCode RoutingPath J ROUTPATH OffsetAddress SLAVEREG NumberOfRegisters NO_REG SourceDataArea REG_WRIT REG WRIT SourceDataArea 100 33002515 CWRITEREG Representation Representation Mia CWRITREG Instance CWRITREG EN ENO DeviceAddress NODEADDR STATUS ErrorCode RoutingPath ROUTPATH OffsetAddress SLAVEREG NumberOfRegisters NO_REG SourceDataArea REG_WRIT REG_WRIT SourceDataArea Representation Representation in IL CAL CWRITREG Instance NODEADDR DeviceAddress ROUTPATH RoutingPath SLAVEREG OffsetAddress NO REG NumberOfRegisters REG WRIT SourceDataArea STATUS gt ErrorCode Representation Representation in ST CWRITREG Instance NODEADDR DeviceAddress ROUTPATH RoutingPath SLAVEREG OffsetAddress NO_REG NumberOfRegisters REG WRIT SourceDataArea STATUS gt ErrorCode 33002515 101 CWRITEREG Parameter description Description of the input parameters Parameters Data type Meaning NODEADDR INT Device address within the target segment ROUTPATH DINT Routing path to targ
89. rationj O_SET CHANNEL Analog I O Scaling I_NORM_WARN WARN PHYS WARN WARN SCALE WARN WARN Quantum I O ACIO40 CHANNL1 16 Configurationj ACO130 CHANNEL1 8 AII330 CHANNEL1 8 INTERNAL AII33010 CHANNEL1 8 AIO330 CHANNEL1 8 ARIOSO CHANNEL1 8 74 33002515 Possible application behavior change Library Motion Family Function Block Concerned Pin MMF Start CFG_CP_F Q ERROR CFG_CP_V Q ERROR CFG_CS Q ERROR CFG_FS Q ERROR CFG_IA Q ERROR CFG_RA Q ERROR CFG_SA Q ERROR DRV_DNLD Q ERROR IDN_CNT DRV_UPLD Q ERROR REG_CNT DATA_B LK IDN_CHK Q ERROR NOT_EQ IDN_XFER Q ERROR OUT_RAW OUTCONV MMF_ESUB Q ERROR RET1 RET2 RET MMF_INDX Q ERROR MMF_JOG Q ERROR MMF_MOVE Q ERROR MMF_RST Q MMF_SUB Q ERROR RET1 RET2 RET MMF_USUB Q ERROR RET1 RET2 RETS 33002515 75 Possible application behavior change Library Obsolete Lib Family Function Block Concerned Pin CLC DELAY Y PI ERR PID1 ERR PIDP1 ERR THREE_STEP_CON1 ERR_EFF THREEPOINT_CON1 ERR_EFF TWOPOINT_CON1 ERR_EFF CLC_PRO COMP_PID STATUS ERR DEADTIME Y FGEN Y N INTEG STATUS PCON2 ERR_EFF PCON3 ERR_EFF PD_OR_PI ERR STATUS PDM Y_POS Y_NEG PI ERR STATUS PID ERR STATUS PID P ERR STATUS PIP ERR SP2 STATUS PPI ERR SP2 STATUS
90. resulting destination address consists of these two information components The routing path is a DINT data type which is interpreted as a sequence of two digit information units It is not necessary to use 00 extensions e g both routing paths 4711 and 47110000 are valid for NODEADDR 34 the result is destination address 47 11 34 00 00 33002515 143 READREG Parameter description REQ NODEADDR ROUTPATH SLAVEREG NO_REG NDR ERROR A rising edge triggers the read transaction The parameter can be specified as an address located variable unlocated variable or literal Identifies the node address within the target segment The parameter can be specified as an address located variable unlocated variable or literal Identifies the routing path to the target segment The two digit information units run from 01 64 see Mode of Functioning p 143 If the slave resides in the local network segment ROUTPATH must be set to 0 or must be left unconnected The parameter can be specified as an address located variable unlocated variable or literal Start of the area in the addressed slave from which the source data is read The source area always resides within the 4x register area SLAVEREG expects the source reference as offset within the 4x area The leading 4 must be omitted e g 59 contents of the variables or value of the literal 40059 The parameter can be speci
91. rnRack3 STATUS4 gt StatusBitPatternRack4 STATUS5 gt StatusBitPatternRack5 DROP Local RemoteDropNo 148 33002515 RIOSTAT Representation Representation in ST RIOSTAT Instance DROP Local RemoteDropNo STATUS1 gt StatusBitPatternRackl STATUS2 gt StatusBitPatternRack2 STATUS3 gt StatusBitPatternRack3 STATUS 4 gt StatusBitPatternRack4 STATUS5 gt StatusBitPatternRack5 Parameter Description of the input parameters ription descriptio Parameters Data type Meaning DROP UINT Local remote I O station no 1 32 Description of the output parameters Parameters Data type Meaning STATUS1 WORD Module rack 1 status bit pattern STATUS2 WORD Module rack 2 status bit pattern 800 I O only STATUS5 WORD Module rack 5 status bit pattern 800 I O only 33002515 149 RIOSTAT 150 33002515 SET_TOD Setting the hardware clock Time Of Day 1 8 Description Function This function block searches together with the other function blocks in the HSBY description group the configuration of the respective PLC for the necessary components These components always refer to the hardware actually connected Therefore the correct functioning of this function block on the simulators cannot be guaranteed The function block sets the hardware system clock if the corresponding registers are provided within this configuration If the
92. s Introduction Overview This chapter contains the requirements for converting a Concept project into a Unity Pro project What s in this This chapter contains the following topics Chapter Topic Fage Concept Version 14 Supported Hardware Platforms 14 Configuration 15 System 17 EFBs 26 Programming Language SFC 29 Programming Language LD 30 Programming Language ST IL 42 Programming Language LL984 43 Programming Language FBD 43 33002515 13 Requirements Concept Version General Projects from Concept versions 2 11 and 2 5 and 2 6 can be converted to Unity Pro projects Preconversion If an older version of a Concept project should be converted to Unity Pro the project must be first converted within Concept to bring it to version 2 6 status for security reasons Supported Hardware Platforms General Unity Pro supports the hardware platform Quantum Quantum PLC The following Quantum PLC types are supported by Unity Pro after downloading Types the respective EXEC file 140 CPU 311 10 140 CPU 431 20 140 CPU 434 12A 140 CPU 531 40 140 CPU 534 14A 140 CPU 651 50 140 CPU 651 60 140 CPU 671 70 Types which no longer exist are replaced by the A type e g 140 CPU 434 12 replaced by 140 CPU 434 12A Lower PLC types are automatically adjusted to the 140 CPU 311 10 14 33002515 Requirements Configuration General Restrictions for
93. s 5 8 Communication counter lost 9 16 Cumulative repetition counter 33002515 135 PLCSTAT Global cumulative error counter for cable A DIOSTATE word9 Global cumulative error counter for cable B DIOSTATE word10 The conditions are true when the bits are set to 1 Bit allocation for word9 112 3 4 5 6 7 8 10 11 12 13 14 15 16 Bit Allocation 1 8 Counts recognized errors 9 16 Counts zero responses The conditions are true when the bits are set to 1 Bit allocation for word10 1 2 8 4 5 6 7 8 10 11 12 13 14 15 16 Bit Allocation 1 8 Counts recognized errors 9 16 Counts zero responses 136 33002515 PLCSTAT RIO status DIOSTATE word11 to word106 Words 11 to 106 are used to describe the RIO station status three status words are planned for each I O station The first word in each group of three shows the communication status for the corresponding I O station 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Bit Allocation 1 Communication health 2 Cable A status 3 Cable B status 5 8 Counter for lost communications 9 16 Cumulative repetition counter The second word in each group of three is the cumulative I O sta
94. se located variables Mx 1x registers EBOOL can be forced MWx IWx registers can be set cyclically only numerical values 33002515 25 Requirements EFBs General DIAGNO library SYSTEM library FUZZY library The following options are available for converting Concept EFBs to Unity Pro e The EFBs are also supported in Unity Pro they are mapped on a one to one basis e The EFBs are no longer supported in Unity Pro Instead of EFBs appropriate DFBs are placed in the application The functionality remains unaffected by this e The EFBs are no longer supported by Unity Pro Instead of EFBs DFBs with no programmatic content are placed in the application These DFBs contain all the Concept parameters An error message is displayed that says that the programmatic content for these DFBs must still be created When converting Concept to Unity Pro for all DIAGNO blocks the station parameter is omitted The following EFBs from the DIAGNO library in Concept are converted to empty DFB s in Unity Pro e ACT_DIA XACT_DIA ERR2HMI ERRMSG Note These DFBs created in Unity Pro have all the Concept parameters but no programmatic content An error message is displayed that says that the programmatic content for these DFBs must still be created During the program creation in Unity Pro replace the DFBs ACT_DIA and XACT_DIA with the DFB XACT For all DIAGNO blocks which can be extended in Conc
95. se registers are not present the TOD_CNF output is set to 0 The function block reads the input values on the S PULSE input at a rising edge and transfers them to the hardware clock For all input values e lf the value exceeds the specified maximum value the maximum is used e lf the value falls below the specified minimum value the minimum is used EN and ENO can be configured as additional parameters Representation Representation in FBD SET TOD Instance SET TOD InputAcceptedFlag S PULSE TOD CNF ClockReady DayOfWeek D WEEK BYTE variable2 MONTH BYTE variable3 DAY BYTE variable4 YEAR BYTE variable5 HOUR BYTE variable6 MINUTE BYTE variable7 SECOND 33002515 151 SET_TOD Representation inLD Representation in IL Representation in ST Representation SET TOD Instance SET TOD EN ENO InputAcceptedFlag ClockReady S_PULSE TOD CNF DayOfWeek D WEEK BYTE variable2 MONTH BYTE variable3 DAY BYTE_variable4 J YEAR BYTE variable5 HOUR BYTE variable6 MINUTE BYTE variable7 4 SECOND Representation CAL SET TOD Instance S PULSE InputAcceptedFlag T DW DAY Byte v SECO EK DayOfWeek MONTH Byte variable2 ariable3 YEAR Byte variable4 HOUR Byte variable5 MINUT E Byte variable6 D Byte variab
96. sion from Concept to Unity an FFB connection between Boolean objects may look like this In the Unity LD Editor such FFB connection may be e deleted e moved e copied and pasted However such FFB connection cannot be created in the Unity LD Editor 33002515 31 Requirements The FFB connection will remain after moving in Unity o 3 Position after moving old Position Connection to A connection to the right bus bar is no longer required the right bus bar e m el ez ex e ep oo q13 E oF eaa cea elo I I l Il oti 012 i O el el ex e e oo q20 O 74 da d ea Ls di de 32 33002515 Requirements Automatically In Concept the contact c9 is not connected with INPUT PV of the component created l connections FBI 0 143 CTUB of qan EN ENO HH e l 502 cu ou L eto qb0z f CD Qb c R a Lo ca Pu cy In Unity the contact c9 would automatically be connected with INPUT PV because both cells directly border in Concept During the conversion from Concept to Unity the contact c9 is therefore moved down to avoid the creation of an automatic connection in Unity FBI 9 143 33002515 33 Requirements Conversion of the output picture During the conversion it is desired that the conversion of the picture
97. ted as a procedure call only a single argument the address of the instance data structure need be passed to the procedure for execution 68 33002515 Possible application behavior change Unity behavior Changed To fulfill the IEC demands the normal EDT Elementary Data Types parameter parameter handling was changed from Concept to Unity handling The following figure describes the actual implementation in Unity Connected input variable Connected output variable 1 3 Copy of inputs Copy of outputs Instance data EFB Code The EFBs no longer get pointers to their connected pin variables They always get the data by value In every scan the application code updates the copy of the input data in the instance data before the function block is called 1 The copy of the pin data is located in the instance data of the block and the function block code always works on the instance data 2 After the function block code execution the application code copies the updated function block output data from the instance data to the connected output variables 3 This is valid for all EDTs Derived data types and more complex data types are treated still by reference in some cases 33002515 69 Possible application behavior change Addressing modes Function Block invocation The addressing mode of a Function Block element is directly linke
98. tent response by network 6mss Routing path error See ss hexadecimal value in 6mss error code p 98 Subfield m shows where the error occurred a 0 value means local node 2 means 2nd device in route etc 33002515 97 CREADREG ss hexadecimal value in 30ss error code ss hexadecimal value in 6mss error code ss hexadecimal value in 30ss error code ss hex Value Meaning 01 Slave does not support requested operation 02 Non existent slave registers were requested 03 An unauthorized data value was requested 05 Slave has accepted a lengthy program command 06 Function cannot currently be carried out lengthy command running 07 Slave has rejected lengthy program command Note Subfield m in error code 6mss is an Index in the routing information that shows where an error has been detected a 0 value indicates the local node 2 means the second device in the route etc The ss subfield in error code 6mss is as follows ss Meaning hexadecimal value 01 No response receipt 02 Access to program denied 03 Node out of service and unable to communicate 04 Unusual response received 05 Router node data path busy 06 Slave out of order 07 Wrong destination address 08 Unauthorized node type in routing path 10 Slave has rejected the command 20 Slave has lost an activated transaction 40 Unexpected master output path r
99. ters 33002515 157 WORD_TO_BIT_DFB Representation in FBD Representation inLD Representation in IL Representation WORD TO BIT DFB Instance WORD TO BIT DFB WORD variable IN BITO Bit1 BITI Bit2 BIT2 Bit3 BIT3 Bit4 BIT4 Bit5 BIT5 Bit6 BIT6 Bit7 BIT7 Bit8 BIT8 Bit9 BIT9 Bit10 BIT10 Bit11 BIT11 Bit12 BIT12 Bit13 BIT13 Bit14 BIT14 Bit15 BIT15 Bit16 Representation WORD TO BIT DFB Instance WORD TO BIT DFB EN ENO Bit WORD variable IN BT HL 2 Bit16 BITIS AL 2 Representation CAL WORD TO BIT DFB Instance BIT BIT BIT BIT P4 gt Bit5 BIT5 gt Bit6 BIT6 gt Bit7 8 gt Bit9 BIT9 gt Bit10 BIT10 gt Bitl1l1 112 gt Bit13 BIT13 gt Bit14 BIT14 gt Bit1 BIT BI IN WORD variable TO gt Bit1 BIT1 gt Bit2 BIT2 gt Bit3 3 gt Bit4 7 gt Bits8 BIT11 gt Bit12 L5 BIT15 gt Bit16 158 33002515 WORD_TO_BIT_DFB Representation Representation in ST WORD TO BIT DFB Instance IN WORD variable BITO gt Bitl BIT1 gt Bit2 BIT2 gt Bit3 BIT3 gt Bit4 BIT4 gt Bit5 BIT5 gt Bit6 BIT6 gt Bit7 BIT7 gt Bit8 BIT8 gt Bit9 BIT9 gt Bit10 BIT10 gt Bitll BIT11 gt Bit12 BIT12 gt Bit13 BIT13 gt Bitl4 BIT14 gt Bit15 BIT15 gt Bit16 Parameter Description of the in
100. the same after the first program run There are two different types of restart behavior 1 All 16 bit PLCs all Momentum Quantum 113 213 424 continue executing the program at the point at which it was interrupted 2 All 32 bit PLCs Quantum 434 534 start the program run at the beginning Unity Pro supports the 1st type of restart behavior described above 18 33002515 Requirements State RAM The Concept State RAM registers are assigned IEC conforming addresses in Unity Pro I O module addresses are converted to topological addresses State RAM register withoutan assigned I O module Concept Unity Pro 4x MWx 3x IWx Ox Mx 1x lx To describe a state RAM register withoutan assigned I O module a flat address is used For this the register number is added to the end of the introduction The address reads as follows IM W Register number State RAM register with an assigned I O module Concept Unity Pro Ax QW IW mixed 1 0 3x 9elW Ox Q 1x l The following information is read from the configuration to provide a sufficient topological description of a State RAM register with assigned I O modules Bus number corresponds to drop head in Concept Drop Rack Module Channel The complete address reads as follows IQ W Busnumber Rack Drop Module Channel 33002515 19 Requirements State RAM assignment using deriv
101. tion error counter at cable A for the corresponding I O station 112 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Bit Allocation 1 8 Minimum one error in words 2 to 4 9 16 Counts zero responses The third word in each group of three is the cumulative I O station error counter at cable B for the corresponding I O station 1 2 13 4 5 6 7 8 9 10 11 12 13 14 15 16 Bit Allocation 1 8 Minimum one error in words 5 to 7 9 16 Counts zero responses Note For PLCs where the I O station 1 is reserved for the local I O words word11 to word13 are allocated as follows 33002515 137 PLCSTAT word11 shows the global I O station status 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Bit Allocation 1 All modules OK 9 16 Counts how often a module is regarded as not OK counter overflow is at 255 word12 is used as a 16 bit I O bus error counter word13 is used as a 16 bit I O repetition counter 138 33002515 READREG Read register 16 Overview Introduction This chapter describes the READREG block What s in this This chapter contains the following topics 2 Chapter Topic Page Description 140 Mode of Functioning 143 Parameter description
102. too small then only the amount of data is transmitted that is present in the array The parameter must be defined as a located variable 96 33002515 CREADREG Modbus Plus Error Codes Form of the function error code Hexadecimal error code The form of the function error code for Modbus Plus is Mmss which includes e Mis the high code e mis the low code e ss is a subcode Hexadecimal error code for Modbus Plus Hex Error Meaning Code 1001 Abort by user 2001 An operation type that is not supported was specified in the control block 2002 One or more control block parameters were modified while the MSTR element was active this only applies to operations which require several cycles for completion Control block parameters my only be modified in inactive MSTR components 2003 Illegal value in the length field of the control block 2004 Illegal value in the offset field of the control block 2005 Illegal value in the length and offset fields of the control block 2006 Unauthorized data field on slave 2007 Unauthorized network field on slave 2008 Unauthorized network routing path on slave 2009 Routing path equivalent to own address 200A Attempting to retrieve more global data words than available 30ss Unusual response by Modbus slave See ss hexadecimal value in 30ss error code p 98 4001 Inconsistent response by Modbus slave 5001 Inconsis
103. ts of a Concept application 83 CREAD REG 49 CREADREG 91 Crossovers with connections of Boolean objects 31 CWRITE REG 49 CWRITREG 99 33002515 169 Index D Datatypes missing 82 Date 21 DDT missing 82 DDTs Redundant names 51 Declaring EFBs 42 DFB variables Private 55 DFBs Constant variables 55 Initialized variables 55 DINT_AS_WORD_DFB 105 DIOSTAT 107 DPM_time Concept 56 Structure 56 structure 56 Unity 56 E Edge Recognition LD 40 EF EFB pins type 50 EFBs 26 replaced by function 47 values 57 EFs correction 57 disabled 57 executive behavior 57 outputs 57 Execution order 17 Execution order LD changed 51 Export from Concept 80 Extension Compatibility BYTE_TO_BIT_DFB 87 CREADREG 91 CWRITREG 99 DINT AS WORD PDFB 105 DIOSTAT 107 GET TOD 109 LOOKUP TABLE1 DFB 117 PLCSTAT 123 READREG 139 RIOSTAT 147 SET TOD 151 WORD AS BYTE DFB 155 WORD TO BIT DFB 157 WRITEREG 161 F FBD Function Block Diagram 43 FBI ST1 75 33 46 forced outputs 96M 24 Function EFB replaced by 47 Not present in Unity 46 Function Block Diagram FBD 43 G General Description 11 Generic EFBs 42 GET TOD 59 109 Global Variables 18 H Hardware Platforms 14 Hot Standby 16 HSBY 16 170 33002515 Index IEC demands 65 IL Instruction List 42 Implicated connections LD 33 Import to Unity Pro 81 Incomplete LD generation 51 Indices 55 IL
104. uded Concept Macros General If a Concept Macro has been included into the Concept export this Macro is converted as if it were a DFB and appears in the project browser tree as a DFB Delete this DFB 33002515 83 Conversion Procedure 84 33002515 Blocks from Concept to Unity Pro Introduction Overview This part contains a description of the blocks which are not part of Unity Pro as standard However if these blocks were used in Concept they are generated during the project conversion from Concept to Unity Pro in order to map the functionality configured in Concept into Unity Pro on a one to one basis What s in this This part contains the following chapters Fart Chapter Chapter Name Page 7 BYTE_TO_BIT_DFB Type conversion 87 8 CREADREG Continuous register reading 91 9 CWRITREG Continuous register writing 99 10 DINT AS WORD DFB Type conversion 105 11 DIOSTAT Module function status DIO 107 12 GET TOD Reading the hardware clock Time Of Day 109 13 LIMIT IND DFB Limit with indicator 113 14 LOOKUP_TABLE1_DFB Traverse progression with 1st 117 degree interpolation 15 PLCSTAT PLC function status 123 16 READREG Read register 139 17 RIOSTAT Module function status RIO 147 18 SET_TOD Setting the hardware clock Time Of Day 151 19 WORD_AS_BYTE_DFB Type conversion 155 20 WORD_TO_BIT_DFB Type conversion 157 21 WRITEREG Write register 161
105. ues 32768 32767 Calculate with TIME and REAL Manual When TIME and REAL variables are multiplied in ST REAL TO DINT must be Correction inserted into the REAL variable manually WORD Assignments to BOOL Arrays Manual Assignments of HEX WORDS to complete Bool arrays sent to Word registers are Correction possible in Concept but not in Unity A manual correction must be done for example AR2 BOOL 0 BOOL lt gt 16 0100 DINT AR2 BYTE 0 BYTE lt gt 16 55AA DINT AR2 BYTE 0 BYTE lt gt 16 AA55 DINT Solution The ST code must be changed to single component assignments The hex word must be split into single bits AR2 BOOL 17 true 33002515 55 Language differences Topological Address Overlapping Same In Unity you are warned during application analysis if the same topological Topological address is assigned to multiple variables Address Structure Alignment Changed DPM_Time Unity uses a 2 byte alignment for structures in contrast to Concept 1 Byte to speed Structure up the access to structure components This affects system structures mapped to StateRam because the same structures in Unity can be bigger including some byte gaps The concerned structure is DPM_Time which has been redefined for Unity to re map to the correct hardware addresses Concept s DPM_Time definition sync BOOL ms WORD Unity s DPM_Time definition
106. ule slot of this rack is characterized by a bit of the corresponding STATUSx output The bit on the far left hand side in STATUSx corresponds to the slot on the far left hand side of the rack x Using STATUS1 to STATUSS e Quantum I O There is only one rack for an l O station e g only STATUS1 is used e 8001 0 There can be up to 5 racks for an l O station e g STATUS1 corresponds to module rack 1 STATUS5 corresponds to module rack 5 Note If a module on the module rack has been configured and works correctly the corresponding bit is set to 1 EN and ENO can be configured as additional parameters 33002515 147 RIOSTAT Representation in FBD Representation inLD Representation in IL Representation RIOSTAT Instance RIOSTAT Local RemoteDropNo DROP STATUSI StatusBitPatternRack1 STATUS StatusBitPatternRack2 STATUS3 StatusBitPatternRack3 STATUS4 StatusBitPatternRack4 STATUSS StatusBitPatternRack5 Representation RIOSTAT Instance RIOSTAT EN ENO Local RemoteDropNo DROP STATUSI StatusBitPatternRack1 STATUS2 StatusBitPatternRack2 STATUS3 StatusBitPatternRack3 STATUS4 StatusBitPatternRack4 STATUSS H StatusBitPatternRack5 Representation CAL RIOSTAT Instance STATUS1 gt StatusBitPatternRackl STATUS2 gt StatusBitPatternRack2 STATUS3 gt StatusBitPatte
107. unction call the result must appear on the left side of a function assignment resl SET BIT IN true NO 4 33002515 47 Language differences INOUT parameters Manual Correction Output Parameters Change of Variable Type INOUT parameter syntax in ST and IL must be corrected manually Examples are shown Ascii FIFO OUT Pile AscFifo Mess AscFifo Out Ascii FIFO OUT DataOut iS Manually corrected to Ascii FIFO OUT Pile AscFifo Mess DataOut gt AscFifo Out INOUT parameters in ST sections that were output parameters in Concept e g DataOut of FIFO must be moved manually in ST and IL to the parameters inside parentheses associated with the call If INOUT parameters that were outputs only in Concept are connected only to a link at the output side they must get a manually declared variable at the input side as well The link must be deleted if it is not connected to another IN OUT variable Targets of the deleted link must be assigned to the manually declared variable This is done automatically in V2 0 The converter changes the type of direct variables at INOUT parameters of communication blocks to ARRAY 0 0 OF WORD This must be corrected manually to correspond to the size of the array 48 33002515 Language differences Parameter type changed Change Explanation The parameter type has been changed from type WORD to an array of
108. us PLCSTATE word2 PLC status PLCSTATE word3 Bit allocation 112 Sad 5 OA 7 e8 70 iw 12 13 14 15 16 Bit Allocation CHS 110 S911 R911 present and OK 11 0 CHS shift switch set to A 1 CHS shift switch set to B 12 0 PLCs have equal logic 1 PLCs have unequal logic 13 14 Remote system condition Dec binary 1 0 1 Offline 2 10 Primary 3 1 1 Standby 15 16 Local system condition Dec binary 1 0 1 Offline 2 1 0 Primary 3 1 1 Standby Bit allocation 112 Sd M58 MCN NOM EOM EON NI 12 13 14 15 16 Bit Allocation First cycle 33002515 129 PLCSTAT RIO status PLCSTATE word4 01 no response 02 Loopback defect Bit allocation 1 2 3 4 MARRAS 10 11 12 13 14 15 16 Bit Allocation 1 IOP defect 2 IOP timeout 3 IOP Loopback 4 IOP memory disturbance 13 16 0010 has not responded 130 33002515 PLCSTAT RIO status RIO_STAT for Quantum General information Function display for Quantum hardware 1 O module function status Conditions for a correct function display Note The information corresponds to status table words 12 to 171 in the
109. vior change 4 Introduction Overview What s in this Chapter This chapter contains information about possible application behavior change when migrating from Concept to Unity Pro This chapter contains the following topics Topic Page General 64 Concept behavior 65 IEC demands 65 Unity behavior 69 Consequences 71 33002515 63 Possible application behavior change General Concept Changes in Unity Behavior may change In Concept all parameters of EFBs Elementary Function Blocks were generally handled by reference Because of this it was possible without any problem to modify a variable connected to an output of a function block from another location inside the application or by an HMI tool when the function block was NOT writing the output This behavior was used to realize for example the manual mode of closed loop control function blocks Because of IEC compliance the parameter handling was changed from Concept to Unity and the way of multi assignment described above doesn t work any longer If an application is converted from Concept to Unity and uses this way of multi assignment the behavior may change in some use cases in a way that the output connected variable is no longer modifiable from another location Note If the application uses multi assignment on EFB outputs you should carefully read the following chapter to verify that the co
110. y remains the same but the section of the program looks a little different EFBs that use In Unity Pro function components using Time functions Timer Diagnostic Control Time functions Components remain in RUN mode even if the SPS is set to STOP mode CAUTION UNEXPECTED BEHAVIOR OF THE CONTROL Function components using Time functions behave differently in Unity Pro and Concept You must take these different behaviors into consideration during the conversion of Concept applications Failure to follow this instruction can result in injury or equipment damage Converted EFBs During conversion Unity Pro standardizes the EFB offer by grouping redundant EFBs The respective EFBs are automatically converted and the project adjusted accordingly 33002515 27 Requirements Renamed EFBs The following diagnostics EFBs are renamed when converting Concept to Unity Pro Concept Unity Pro XACT D_ACT XREA_DIA D_REA XLOCK D_LOCK XGRP_DIA D_GRP XDYN_DIA D_DYN XPRE_DIA D_PRE The Quantum configuration EFB for the Backplane Expander 140 XBE 100 00 is renamed when converting Concept to Unity Pro Concept Unity Pro XBP XBE 28 33002515 Requirements Programming Language SFC General For some programming languages there are restrictions to observe when converting a project from Concept to Unity Pro Parallel A parallel br

Unity Pro 2.2

Contents

Download Pdf Manuals

Related Search

Related Contents