Вопрос по RSLogix 5000 Security

[MadMaxx]

Если я использую в проекте функцию Security, то я блокирую просмотр программы. Но если в контроллер залить новую программу, то эта функция отключается.
Как заблокировать заливку новой программы в контроллер 1769-L32E?

[oldDad]

About the Security Feature

The Security feature allows you to control the individual users’ access to RSLogix 5000 projects and controllers. Using RSI Security Server software, you control access to your projects and controllers based on:

- the individual user logged into a workstation
- the project the user is attempting to access
- the workstation from which the user is attempting to access the project

Typically, you would use RSI Security Server software to grant or deny permission to perform a particular action on a particular project to a particular person at a particular workstation.
Note: The security feature is primarily intended to prevent accidental unauthorized access to your projects and controllers. It is important to note that while the feature does provide some protection against intentional unauthorized access, it is not intended to provide protection against sophisticated system "hackers." You should exercise your own additional precautions against such unwanted access.

RSI Security Server grants or denies access based on four pieces of information:

- user ID (i.e., the user’s login name)
- workstation ID
- action name (i.e., the activity the user is trying to perform, such as data table modification, or processor mode change)
- resource name (i.e., controller name)

In addition, you can group resources, actions, persons, and workstations via access control lists, which define certain characteristics to determine access levels.

RSLogix 5000 and RSI Security Server

When used with RSLogix 5000, RSI Security Server supports 3 global actions and 6 project-related actions. Global actions are not tied to a specific project, and may include:

- securing the controller
- creating a new project (either through the New Controller dialog, or through the Translator Tool utility)
- updating your firmware.

The project-related actions allow you to perform specific tasks on a specific project or group of projects, and may include:

- viewing a project
- going online
- maintaining a project (e.g., saving, converting, exporting, downloading, setting/forcing tag values, etc.)
- full access (e.g., editing a project), unsecuring the controller, or updating firmware.

Note: Access to these actions is hierarchical. For instance, if you have access to the Go Online action, you also have access to the View Project action; if you have access to the Maintain Project action, you can also access Go Online and View Project; and finally, if you have Full Access, you can access Maintain Project, Go Online, and View Project.
Defining your levels of security begins with deciding the type of access you want to allow to each user, project, or workstation. The following tables can help you to identify your security needs.