Beckhoff Automation GmbH & Co. KG TX1200 — 9 Engineering Interface (ENI)

Engineering Interface (ENI) in the data base administration possibly the user (Client) as well as the ENI Server must be registered as valid users with access rights. Anyway, this is required for the 'Visual SourceSafe', if you use another data base system, please see the corresponding documentation for information on the user configuration. for the current project the ENI interface must be activated (to be done in the TwinCAT PLC Control dialog 'Project' 'Options' 'Project data base' ). for the current project the connection to the data base must be configured correctly; this is to be done in the TwinCAT PLC Control dialogs 'Project' 'Options' 'Project data base'.

in the current project the user must log in to the ENI Server with username and password; this is to be done in the Login dialog, which can be opened explicitly by the command ' Project' 'Data Base Link' 'Login' resp. which will be opened automatically in case you try to access the data base without having logged in before. Working with the ENI project data base The data base commands (Get Latest Version,Check Out, Check In, Version History, Label Version etc.) which are used for managing the project objects in the ENI project data base, will be available in the current project as soon as the connection to the data base has been activated and configured correctly.

See for this Preconditions for Working with an ENI project data base. The commands then are disposable in the submenu 'Data Base Link' of the context menu or of the 'Project' menu and refer to the object which is currently marked in the Object Organizer. The current assignment of an object to a data base category is shown in the Object Properties and can be modified there. The properties of the data base categories (communication parameters, access rights, check in/check out behaviour) can be modified in the option dialogs of the project data base ('Project' 'Options' 'Project Source Control').

Object categories concerning the project data base There are four categories of objects of a TwinCAT PLC Control project concerning the project source control: The ENI distinguishes three categories ("ENI object categories") of objects which are managed in the project data base: Project objects, Shared objects, Compile files. If an object should not be stored in the data base, it will be assigned to category 'Local', which means that it will be handled as it is known for projects without any source control.

Thus in the programming system an object can be assigned to one of the categories 'Project objects', 'Shared objects' or 'Local'; the 'Compile files' do not yet exist as objects within the project. Assigning an object to one of the categories is done automatically when the object is created, because this is defined in the project options dialog 'Project source control', but it can be modified anytime in the 'Object Properties' dialog. Each ENI object category will be configured separately in the settings for the ' ENI settings' ('Project' 'Options', category project data base) .

That means that each category gets defined own parameters for the communication with the data base (directory, port, access right, user access data etc.) and concerning the behaviour at calling the latest version, checking out and checking in. These settings then will be valid for all objects belonging to the category. As a result you will have to log in (username, password) to each data base category separately; this will be done via the 'Login' dialog (' Project' 'data base agssignment' 'Login '). It is advisable to create a separate folder for each object category in the data base, but it is also possible to store all objects in the same folder.

(The 'category' is a property of an object, not of a folder.) See in the following the three ENI object categories: TX1200 255 Version: 1.3