The View > Properties... command opens the Properties dialog box. The properties of the selected object in the Devices tree, Applications tree, or Tools tree is displayed on various tabs, the availability of which depends on the type of the selected object.
|
Properties Tab |
Description |
|---|---|
|
Information on the object. |
|
|
Device-dependent available settings concerning the boot application. |
|
|
For characterizing objects by bitmaps. |
|
|
For an object added as external file. |
|
|
These settings for an application overwrite the default memory size definitions for inputs, outputs, and memory locations on the target controller. |
|
|
Options of the controller. |
|
|
For SFC transition objects. |
|
|
Memory allocation on the controller, generating application information, and encryption for the application. |
|
|
User access to the object. |
|
|
Exclude from build, Enable system call, External implementation, Link Always, Compiler defines. |
|
|
For global variable list read from an external file. |
|
|
For global network variable list. |
|
|
Flags for SFC. |
|
|
For global variable lists, export and import. |
|
|
For Cam objects. |
|
|
CNC |
Properties of a CNC object. |
|
Documentation for folder. |
|
|
For text lists |
|
|
For image pools |
Provides information on the object:
|
Full name |
Object name as used in the tree views (Devices tree, Applications tree, or Tools tree). |
|
Object type |
Type of the object (for example, POU, Application, Interface and so on). |
|
Open with |
Type of the editor which is used to edit the object. |
It depends on the device whether these settings are available:
|
Implicit boot application on download |
If activated, at a download of the project automatically a boot application will be created. |
|
Implicit boot application on Online Change |
If activated, at an online change automatically a boot application will be created. |
|
Remind boot application on project close |
If activated, when closing the project you will be asked whether the boot application should be updated/created. |
In the Bitmap tab, you can associate a bitmap to the current object or remove a currently associated bitmap. The bitmap is used in the graphical display of the object in the Library Manager and in the toolbox of the FBD/LD/IL editor. For specifying the transparency of the bitmap, you can activate the option Render pixels of this color transparently and via a mouse-click on the color rectangle select the color to be made transparent.
|
Render pixels of this color transparently |
Specifies the transparency color of the bitmap. |
Consult the Programming Guide specific to your controller for whether the following options are available on your controller.
These settings define whether during compilation some information on the application content is downloaded, how the memory will be allocated on the controller and whether and how the application gets encrypted.
|
Download Application Info |
If this option is activated, information on the content of the application is downloaded to the controller: As a precondition, the compiler version must be ≥ 3.5.0.0 and the runtime version ≥ 3.5.0.0. An implicitly generated variable <devicename>.App.__ApplicationInfoVariables.appContent stores information and checksums concerning the number of POUs, data, and memory locations. This allows checking for differences between the current project and the downloaded project. The content information is visible via the Content button in the Applications view of the device editor as well as in the message box which appears when you are going to download an application different to that already available on the controller. |
|
Stop parent application in case of exception |
This function is not supported and therefore not available for selection. |
|
Dynamic memory settings |
|
|
Use dynamic memory allocation |
Activate this option to allocate memory dynamically for the application, for example, when using the __NEW operator. In this case, enter the desired Maximum size of memory (bytes). NOTE: The complete memory is not available for dynamic object creation. A part of it is used for system management. The maximum admissible value for the parameter Maximum size of memory (bytes) depends on the individual controller (PacDrive LMC Eco, PacDrive LMC Pro, PacDrive LMC Pro2) as they incorporate different sizes of random access memory, and on the size of the present application. If the threshold value is exceeded, download operations will not be executed successfully. |
These settings for an application overwrite the device-specific memory size definitions for inputs, outputs, and memory locations:
|
Override target memory settings |
The maximum data sizes for the input, output, and memory location memory, defined by the target device, is overridden by the sizes defined below. |
|
Input size [bytes] |
Memory space for variables assigned to input addresses of the target device. Declaration AT %I. |
|
Output size [bytes] |
Memory space for variables assigned to output addresses of the target device. Declaration AT %Q. |
|
Memory size [bytes] |
Memory space for variables assigned to memory location addresses of the target device. Declaration AT %M. |
NOTE: Whether these settings are available depends on the controller. For more information, refer to the Programming Guide of your controller.
The Options (controller) tab is available in the properties of a selected application. The content depends on the device.
This function is not available for all supported controllers. Consult the Programming Guide specific to your controller.
|
Monitoring interval (ms) |
Specifies the time interval for the monitoring (10 ms...1000 ms). |
The Interactive Login Mode helps to avoid an unintended login to a different controller.
|
None |
No interaction with the user while login. Corresponds to the behavior of earlier versions. |
|
Enter ID |
While login, the user is prompted to enter an ID. The ID is stored in the controller. A valid ID is necessary to login. While login a second time, the user is not asked again for the ID if the computer name, the user name, the device name, and the device address has not changed. The information is stored in the project options. |
|
Press key |
While login, a dialog box appears prompting the user to press a key on the controller. The timeout for this action is defined in the device description. |
|
Symbol configuration |
By default, this option is not activated. Consistent access by the system is not always available. Activate the option Access variables in sync with IEC tasks to allow symbolic clients (for example, visualizations or database connections based on the PLCHandler) a consistent read and write access that is synchronized with the IEC tasks. Also refer to the Additional Information on the Option Configure synchronisation with IEC tasks... in the EcoStruxure Machine Expert Programming Guide. In order for the setting to take effect, the applications and boot applications must be downloaded to the controller. |
The Monitoring tab allows you to configure the monitoring of transitions in SFC.
|
Enable monitoring |
If the Enable monitoring option is activated, the variable is assigned when the application calls the transition. The last value that has been stored for the variable is displayed in the monitoring. |
|
Monitoring using call |
If the Monitoring using call option is activated, the transition to be monitored is read by directly calling the transition. NOTE: When you activate this option, be aware that additional operations may have been implemented in the transition and would be executed. |
The External File tab presents the settings you have defined when adding an external file. You can modify these settings.
To have the current settings become effective without closing the Properties dialog box, click the Apply button.
The Access Control tab allows you to configure the access rights on the current object for the available user groups. This corresponds to the configuration via the Permissions dialog box which is available in the Project > User Management menu.
To edit the right for a certain action and group, select the respective field in the table, click or press SPACE to open the selection list, and choose the desired right.
For a description on possible actions, rights and the symbols refer to the Permissions... dialog box.
Concerning the compilation (Build), you can activate the following options:
|
Exclude from build |
The object and recursively its child objects will not be considered during the next Build run. The object node is displayed in green in the Devices tree or Applications tree. NOTE: This option is not supported for safety-related devices. |
|
External implementation |
No code is created for this object during a compilation of the project. The object will be linked when running the project on a target, if it is available there, for example via a library. The object name is extended by the string (EXT) in the Devices tree or Applications tree. |
|
Enable system call |
The ADR operator can be used with function names, program names, function block names, and method names, thus replacing the INSTANCE_OF operator. For further information, refer to the description of function pointers. BUT there is no possibility to call a function pointer within EcoStruxure Machine Expert. In order to enable a system call (runtime system), you must activate the current option for the function object. |
|
Link Always |
The object is marked for the compiler so that it is included into the compile information. As a result, objects will be compiled and downloaded to the controller. This option is relevant when the object is located below an application or is referenced using libraries inserted below an application. The variables selectable for the symbol configuration use the compile information as basis. |
|
Compiler defines |
Here you can enter defines (refer to {define} instruction) and conditions for the compilation of this object. In chapter Conditional Pragmas, you can find a description of the available conditional pragmas. The expression EXPT used in those pragmas can be entered here, several entries can be entered in a comma-separated list. |
Additional compiler definitions from the device description:
|
Defined in device |
List of compiler definitions from the device description. These compiler definitions are used in the build if they are not listed in the Ignored definitions field. |
|
Ignored definitions |
List of compiler definitions from the device description that are not used in the build. |
|
Arrow right button |
Click to copy the selected compiler definition from the Defined in device field to the Ignored definitions field. |
|
Arrow left button |
Click to move the selected compiler definition from the Ignored definitions field to the Defined in device field. The compiler definition is used in the build. |
Example:
It can be useful to make the compilation of an application dependent on the value of a certain variable.
In the following figure, hallo is defined and if a variable test has value 2 the application will be compiled.
If the network variables functionality is supported by the current device, then the network properties of a GVL (Global Variable List) object can be viewed and edited in the Properties dialog box.
Specifying network properties for a GVL means to make available the included variables as network variables. A GVL is to be defined by the sender of the network variables. The receiver must have a corresponding GNVL list. Also refer to the general description on how to use network variables.
|
Network type |
Choose the desired type from the target-dependent selection list. Example: CAN as an abbreviation for a CAN network, or UDP for a UDP transmission system |
|
Task |
From the selection list, choose the task of the current application which should control the sending of the variables. The variables will be sent at the end of a task cycle. |
|
List identifier |
Number (ID) of the first list to be sent (default = 1). Further lists will be numbered in ascending order. |
NOTE: The list identifier must be unique in case the exchanging devices are intended to act as sender AND receiver. This means that each device is providing GVLs as well as GNVLs.
|
Settings |
Protocol-specific settings. The permissible entries depend on the corresponding network library. |
Network settings for a GVL
For UDP networks, define the following parameters:
|
Port |
Number of the port to be used for data exchange with the other network participants. The Default value is 1202. The current value can be modified in the Value field (select the field and press SPACE to open the edit frame). Make sure that the other nodes in the network define the same port. If you have more than one UDP connection defined in the project, then the port number will be automatically modified in all configuration sets according to the input you made here. |
NOTE: Data exchange via network variables are not available if it is not supported by the device (target system). If a firewall blocks communication, or if another client/application has opened the same UDP (user datagram protocol) port as specified in the properties of the network variable list, the communication will be unsuccessful.
|
Broadcast address |
The default value is 255 . 255 . 255 . 255, which means, that data is exchanged with all participants in the network. The current value can be modified in the Value field (select the field and press SPACE to open the edit frame). You can enter the address or the address range of a subnetwork. Example: Enter 197 . 200 . 100 . 255 if you want to communicate with all nodes which have IP addresses 197 . 200 . 100 . x). NOTE: For Win32 systems, the broadcast addresses must match the subnet mask of the TCP/IP configuration of the PC. |
The following options can be activated or deactivated for configuring the transmission behavior of the variables:
|
Pack variables |
For the transfer, the variables are bundled in packets (telegrams) whose size depends on the network. If the option is deactivated, one packet per variable will be set up. |
|
Transmit checksum |
A checksum will be added to each packet of variables. The checksum will be checked by the receiver to make sure that the variable definitions of the sender and the receiver are identical. A packet with a non-matching checksum will not be accepted. |
|
Cyclic transmission |
Variables are sent within the Interval specified after interval. Example for time notation: T#70ms). |
|
Acknowledgement |
An acknowledgement message is sent back for every received data packet. If the sender does not receive an acknowledgement before sending again, an error message will be written to the diagnostic structure. |
|
Transmit on change |
Variables will be sent only if their values have changed. The Minimum gap can define a minimum time lapse between transfers. |
|
Transmit on event |
The variables will be sent as soon as the specified variable gets TRUE. |
NOTE: The network variables will be automatically sent at each boot up. This means that the actual variable values will be transmitted even if none of the other defined transmission triggers (change or event) would force this at this moment.
If the network functionality is supported by the current device, then the Network settings for a GNVL (Global Network Variable List) object can be viewed and edited in the Properties dialog box. Basically these are the settings which have been defined when adding the NVL object via the Add Object dialog box. (Also refer to the general description on how to use network variables).
|
Task |
Name of the task of the current device, which controls the data exchange of the network variables. |
|
Sender |
Here you see either the name of the global variable list of the sending device, which is referenced in the current NVL object, or Import from file. If the name is specified, the squared brackets include the name of the device and the application. In case the sender GVL is imported from a *.gvl file, which previously has been exported from the respective global network variable list, the complete file path is shown here, for example: D:\projects\pr9519\project_xy.gvl. |
|
Import from file |
In case the Sender GVL is specified via a *.gvl export file, which previously has been generated from the respective global network variable list, the file path is shown here. |
The SFC Settings tab allows settings for the current SFC object regarding compilation and flag handling only for this object. Refer to Options SFC, for a description of the particular settings. The settings made in the Project > Project Settings > SFC dialog box are valid for the entire project.
|
Use defaults |
Activate the check box to apply the settings made in the Project > Project Settings > SFC dialog box. |
A Global Variable List - GVL can be defined with the help of an external file in text format. Such a file can be generated by using the export functionality provided in the Properties dialog box of the respective variable list. If the option Export before compile is activated, at each project compilation (for example, by pressing F11) a file with extension gvl is automatically created and stored at the path specified in the Filename field. If the option Import before compile is activated, an existing list export file can be read at each project compilation. This allows importing a GVL created from another project, for example in order to set Network Variables communication.
The Cam tab serves to specify the global settings of a cam object that is its dimensions, its period and continuity requirements and its compile format.
|
Dimensions |
|
|
Master start/end position |
Start and end position of the master define the set of master values and thus the scale of the horizontal axis of the cam. The default settings are thought of in arc degrees and thus adjusted to 0 and 360. |
|
Slave start/end position |
The associated slave positions are determined by the cam-defining mapping. The cutout displayed by the graphs, that is the scale of the vertical axis, may be specified by the minimal and maximal value of the slave display. |
|
Period |
These settings affect the creation of the cam in the cam editor and cam table. Depending on the parameters, the slave start position is adapted automatically if the end position is changed and vice versa. This adaption optimizes the period transition in a way that it moves consistently without jerking. |
|
Continuity requirements |
The check boxes Position, Velocity, Acceleration and Jerk determine whether validation of continuity is performed while editing. You can clear the check boxes for special cases (mapping consisting of linear segments only). However, the lack of continuity may lead to kinks in the position graph. |
|
Compile format |
During compilation, the function block MC_CAM_REF is created. The description of the cam segments is according to one of the following options: polynomial (XYVA), one dimensional point array or two dimensional point array. |
|
polynomial (XYVA) |
Polynomial description on particular points consisting of master position, slave position, slave velocity, and slave acceleration. |
|
one dimensional point array |
One dimensional table of slave positions. |
|
two dimensional point array |
Two dimensional table of related master/slave positions. |
|
Elements |
Number of elements in the arrays. This array has already been created in the library SM3_Basic for the default cases 128 and 256. If you enter another value, you must create the structure in your application (refer to the following example). |
Example of an array with 720 elements:
TYPE SMC_CAMTable_LREAL_720_2 :
STRUCT
Table: ARRAY[0..719] OF ARRAY[0..1] OF LREAL;
fEditorMasterMin, fEditorMasterMax: REAL;
fEditorSlaveMin, fEditorSlaveMax: REAL;
fTableMasterMin, fTableMasterMax: REAL;
fTableSlaveMin, fTableSlaveMax: REAL;
END_STRUCT
END_TYPE
The Documentation tab is available for folders to enter annotations, notes, and comments.
|
Download by visualization |
In a standard case, text lists are used for the visualization and therefore also for the application. In this case, the option is activated. For developing elements, the translation of element properties is performed by using text lists. In this case, deactivate the option because these text lists are not used by the application itself. |
|
Internal |
If activated, the object is only visible in the Applications tree of the current project. If the text list is part of a referenced library it is not displayed in the Library Manager. |
|
Download only used images |
In a standard case, an image pool contains images belonging to a project and an application. In this case, the option is deactivated. If there is an image pool used for different projects, it is not useful to download all these files to the controller. In this case, the option is activated. Then only images are downloaded to the controller which are used in the application. |
|
Internal |
If activated, the object is only visible in the Applications tree of the current project. If the image pool is part of a referenced library it is not displayed in the Library Manager. |
|
Symbol library settings |
|
|
Mark library as symbol library |
Symbol libraries that are installed in the repository are listed in the Symbol Libraries tab of the Project Settings > Visualization dialog box. To use the library and / or the images of the image pool in the visualization of your projects, the library has to be added to your project. The images will then be available in the ToolBox for a visualization. For more information, refer to the Visualization part of the EcoStruxure Machine Expert online help. If a library project is open, click this button to mark the image pool as a symbol library for use in a visualization. This has the following effects: oThe symbol library is assigned the key VisuSymbolLibrary = TRUE as file property in the project information. oThe library System_VisuElems is inserted automatically as a placeholder library in the Library Manager below the Global node of the Applications tree. Add this library to the Library Repository by executing the File > Save Project And Save Into Library Repository command. |
|
Text list for symbol translation |
Select the text list that contains the translated texts for the image pool. |
