Chapter 2. CPU Features & Specifications
GFK-2222AD April 2018 27
Security
When the application is written to the RDSD from a controller that has passwords and/or an OEM key
defined, the passwords and OEM key are encrypted and stored on the RDSD. When the project is written
from the RDSD to a CPE302/CPE305/CPE310/CPE330
, the passwords and OEM key are copied to it.
If an OEM key is defined on the RDSD, when transfer is complete, the OEM protection will be enabled
(locked). When an application is being stored to a CPE302/CPE305 that already has passwords and/or an
OEM key defined, the passwords/key on the RDSD must match the passwords/key in the target
CPE302/CPE305/CPE310/CPE330, or the transfer will fail.
RDSD Error Reporting
Errors are indicated when the RDSD LED becomes solid red (not blinking). All errors are reported in the
Controller fault tables. If the Controller has faults in its fault tables before it receives a store, the fault
tables are written to plcfaultbefore.dat and iofaultbefore.dat on the RDSD. If the Controller has faults in
its fault tables after it receives a store, the fault tables are written to plcfaultafter.dat and iofaultafter.dat
on the RDSD. Previous versions of these files are deleted before the transfer. If either fault table is empty,
the corresponding file is not written and will not be present.
To read any of the .dat files mentioned above, open PACS Analyzer. In settings, enable file analyze. Then
click the file analyze button on the main screen. Select as Input File the .dat file to be analyzed. Select as
Output File the filename and folder into which you wish to deposit the resulting text. The text will be in
English.
If a hardware configuration that disables the USB port is stored to the CPU, the fault tables will not be
written to the RDSD at completion of the store operation because the USB port will be disabled at the
end of the store process.
To Next Page
Loading...
Need help?
General
