• No results found

Legacy/Enhanced Security Comparison

In document PACSystems RX3i and RSTi-EP CPU (Page 175-179)

Section 4: CPU Operation

4.9 System Security

4.9.4 Legacy/Enhanced Security Comparison

Table 4-5: Legacy/Enhanced Security Comparison

Feature Legacy (less secure) Enhanced (more secure) Level 2, 3 and 4

protection

Levels 2, 3 and 4 must be set or modified simultaneously. (If you only want to change one, you must enter all three.)

Passwords can be set individually or in a group. When changing passwords, the old password for that level is required in order to change it.

Maximum password length

7 characters 31 characters

Clearing passwords Passwords can be cleared back to initial blank password values.

Once a password is set, the Enhanced Security mode in PME will not allow it to be cleared back to a blank password. To revert to a blank password, the CPU memory must be cleared and power cycled.

7 characters. 31 characters.

OEM keys ≤7 characters, set with Enhanced Security

Can change OEM Protection Lock state

Cannot change the OEM key.

Can change OEM Protection Lock state and the OEM key.

Can change OEM Protection Lock state and the OEM key.

4.10 PACSystems I/O System

The PACSystems I/O system provides the interface between the CPU and other devices. The PACSystems I/O system supports:

• I/O and Intelligent option modules.

• Ethernet Interface

• Motion modules (RX3i) PROFINET:

• RX3i CPE330, CPE400, CPL410 and RSTi-EP CPE100/CPE115 all permit one of their LANs to be configured as an embedded PROFINET Controller (see Section 2.1.6). Alternately, the RX3i PROFINET Controller IC695PNC001 installs in the RX3i Main I/O Rack74. The embedded PROFINET Controller and the IC695PNC001 are used to control remote I/O drops. Refer to PACSystems RX3i & RSTi-EP PROFINET IO-Controller Manual, GFK-2571G or later. Some examples of remote drops are:

• Standard rack-mounted I/O modules in RX3i racks scanned by the PROFINET scanner IC695PNS001and IC695PNS101. Refer to PACSystems RX3i PROFINET Scanner Manual, GFK-2737.

• A mini-drop consisting of one or two I/O modules and supervised by the IC695CEP001. Refer to PACSystems RX3i CEP PROFINET Scanner User Manual, GFK-2883.

• A Genius Bus supervised by a Genius Communications Gateway (IC695GCG001). Refer to PACSystems RX3i Genius Communications Gateway User Manual, GFK-2892.

The Genius I/O System

• A Genius I/O Bus Controller (GBC) module provides the interface between the CPU and a Genius I/O bus. Refer to Series 90-70 Genius Bus Controller User’s Manual, GFK-2017.

• RX3i: A Genius Communications Gateway (IC695GCG001) provides the interface between devices on the Genius I/O bus and a PROFINET Controller (IC695PNC001) which is installed in the RX3i Main I/O rack. Refer to PACSystems RX3i Genius Communications Gateway User Manual, GFK-2892.

• For information on Genius I/O, refer to Genius I/O System User’s Manual, GEK-90486-1 and Genius I/O Analog and Discrete Blocks User’s Manual, GEK­90486­2.

4.10.1 I/O Configuration

Module Identification

In addition to the catalog number, the programming software stores a Module ID for each configured module in the hardware configuration that it delivers to the CPU. The CPU uses the Module ID to determine how to communicate with a given module.

When the hardware configuration is downloaded to the CPU (and during subsequent power-ups), the CPU compares the Module IDs stored by the programmer with the IDs of the modules physically present in the system. If the Module IDs do not match, a System Configuration Mismatch fault will be generated.

Because I/O modules of similar type may share the same Module ID, it is possible to download a configuration containing a module catalog number that does not match the module that is physically present in the slot without generating a System Configuration Mismatch.

Certain discrete modules with both reference memory inputs and reference memory outputs will experience invalid I/O transfer if incorrect configuration is stored from a similar mixed I/O module. No fault or error condition will be detected during configuration store and the module will be operational, although not in the manner described by configuration.

For example, a configuration swap between the IC693MDL754 output module and IC693MDL660 input module will not be detected as a configuration mismatch, but I/O data transfer between the module and the CPU reference memory will be invalid. If the input module (MDL660) is sent the configuration of the output module (MDL754) with the following parameters:

Reference Address: %Q601 Module Status Reference: %I33 Hold Last State Enable

It will receive inputs at the module status reference %I33 and the status of the module will be received at %Q601.

If the output module is sent the configuration of the input module with the following parameters:

Reference Address: %I601 Input Filter: Enable

Digital Filter Settings Reference: %I65

It will output values at the digital filter settings reference %I65 and the status of the module will be received at %I601.

Default Conditions for I/O Modules

Interrupts

Some input modules can be configured to send an interrupt to the application program. By default, this interrupt is disabled and the input filter is set to slow. If changed by the programming software, the new settings are applied when the configuration is stored and during subsequent power-cycles.

Outputs

Some output modules have a configurable output default mode that can be specified as either Off or Hold Last State. If a module does not have a configurable output default mode, its output default mode is Off. The selected action applies when the CPU transitions from RUN/Enabled to RUN/Disabled or STOP Mode, or experiences a fatal fault.

At power-up, Series 90-30 discrete output modules default to all outputs off. They will retain this default condition until the first output scan from the PACSystems controller. Analog output modules can be configured with a jumper located on the removable terminal block of the module. The jumper may be set to cause outputs to either default to zero or retain last state.

Inputs

Input modules that have a configurable input default mode can be configured to Hold Last State or to set inputs to 0. If a module does not have a configurable input default mode, its input default mode is Off. The selected action applies when the CPU transitions from RUN/Enabled to RUN/Disabled or STOP Mode, or experiences a fatal fault.

For details on the power-up and STOP Mode behavior of other modules, refer to the documentation for that module.

Multiple I/O Scan Sets

Up to 32 I/O scan sets can be defined for a PACSystems CPU. A scan set is a group of I/O modules that can be assigned a unique scan rate. A given I/O module can belong to one scan set. By default, all I/O modules are assigned to scan set 1, which is scanned every sweep.

For some applications, the CPU logic does not need to have the I/O information every sweep. The I/O scan set feature allows the scanning of I/O points to be more closely scheduled with their use in user logic programs. If you have a large number of I/O modules, you may be able to significantly reduce scan time by staggering the scanning of those modules.

A disadvantage of placing all modules into different scan sets appears when the CPU is transitioning from Stop to Run. In that case, scan sets with a programmed delay are not scanned on the first sweep.

These modules' outputs are not enabled until the new data has been scanned to them, perhaps many scans later. Therefore, there is a period of time during which the user logic is executing and some modules' outputs are disabled. During that time, outputs of those modules are in the module’s stop-mode state. Stop-stop-mode behavior is module-dependent. Some modules zero their outputs, some hold their last scanned state (if any), and some force their outputs to a configured default value. When the module's outputs are enabled, the module uses the last scanned value, which will either be zero or the contents of the register the module uses to hold the corresponding output values from the reference tables.

In document PACSystems RX3i and RSTi-EP CPU (Page 175-179)