Topic: P340

UDI (User Defined Instruction) Management

Purpose

UDI (User Defined Instruction) Management panel is where users can copy, import, export, and configure security for UDI Definitions that can later be instantiated in ladder using the User Defined Instruction.

Accessing UDI Management

The UDI Management panel can be accessed by selecting UDI Management Panel from the Tools Menu of the Main Menu or using shortcut “Alt+T then U

User Defined Instruction Management Panel

Note: In the image above, if the icons are grayed out, it indicates that Structures are currently disabled in the project properties.

Create New UDI: Creates a new UDI definition. Once selected the Add UDI Definition window is displayed.
1. Name: Name of the UDI definition. Maximum of 32 characters allowed.
2. Comment: Comments that are pertinent to or helpful in describing a UDI’s definition. Maximum of 1024 characters allowed.
3. Revision: The revision is not automatically managed by the software. The user is responsible for defining how it is used and when it is updated. A maximum of 32 characters are allowed for Suffix.
  Example: The Revision will read as “1.0revA” when the user enters a 1 in Major, leaves the Minor as 0, and types “revA” into the Suffix field.”
4. Revision Note: Information that is pertinent to changes made in the revision. Maximum of 1024 characters allowed.
5. Author: Name or initials to identify the author of this definition. Maximum of 64 characters allowed.
6. Security Key: Lists of the available security keys that are configured in the UDI Security Management setup.
Copy UDI: A copy of the UDI definition will be generated and _1 will be appended to the new definition.
Delete UDI: Deletes the selected UDI definition.
Manage UDI Security: Opens the UDI Security Management dialog so that users may create, edit, and delete Security Keys as well as Assign the keys to single or multiple UDI Definitions.

Note: To remove an assigned security key from a definition, select the definition and the (No Security) option and move the (No Security) option to the definition by clicking the button, enter the password, and then the security key will be removed from that definition.

Add UDI Security Key:

Key name: Must have a unique name for the UDI Security Key. A maximum of 32 characters are allowed.
Password: The password for the security key.
Confirm Password: The text entered in the Password and Confirm Password fields must match exactly. Passwords must be between 8 and 128 characters in length and there are no restrictions on the types of characters used.

Assigning security key to definition

To assign a key to an existing UDI definition select a definition from the available list (multiples can be selected) and

Then select a security key. Move the security key to the chosen definition(s) by selecting the button.

Edit allows a user to modify the key name or update the password. When changing key name, the current password must be entered to allow the changes.

Delete will delete the security key and remove it from any assigned definitions. A valid password for that key is required prior to deletion.

e. Import UDI(s): Allows the user to import a .udi file that contains a UDI Definition. Once imported, the UDI will be in the list of available definitions.

Note: If a UDI that has security enabled will allow a user to instantiate the UDI and assign parameters but will not allow access or editing of the definition without the end user entering the proper password.

f. Export UDI(s): Exports selected UDI instances from the project. Saved as filename.udi. Definitions can be selected individually or in multiples. They do not need to be contiguous, and could have other UDI’s nested within the UDI definition that is being exported

Note: If Security is enabled on an exported UDI, then a password will be required to edit the UDI Definition if it is imported into another project.

Note: When exporting a UDI Definition that contains one or more nested UDI Definitions, all definitions must be selected for export, or an error will occur.

Note: If a task fro the library is moved into a task folder that contains a task with the same name, then a copy will be generated and _1 will be appended to the task name.

Note: When moving a task from the library, any tags with names that already exist in the tag DB will not inherit any attributes.