VIPA System 300V - Page 69

Manual VIPA System 300V Chapter 4 Deployment CPU 31x
HB130E - CPU - Rev. 11/50 4-17
As external storage medium a MMC is deployed. The MMC (Memory Card)
serves as external transfer medium for programs and firmware for, among
others, it provides the PC compatible FAT16 file system. With an overall
reset or PowerON the MMC is automatically read. There may be stored
several projects and sub-directories on a MMC storage module. Please
consider that the current project is stored in the root directory and has one
of the in the following described file names.
Always after overall reset and PowerON the CPU tries to load a user
program from the MMC into the battery-buffered RAM or in the Flash
memory. Here the following file names may be assigned to the project
depending upon the desired functionality:
• S7PROG.WLD
After overall reset the user program S7PROG.WLD is transferred into
the battery-buffered RAM.
• S7PROGF.WLD (starting with Firmware-Version V. 3.8.6)
After overall reset the user program S7PROG.WLD is transferred into
the battery-buffered RAM and additionally into the Flash memory. An
access to the Flash memory takes only place at empty battery of the
buffer and when no MMC with user program is plugged-in.
• AUTOLOAD.WLD
After PowerON the user program AUTOLOAD.WLD is transferred into
the battery-buffered RAM.
When the MMC has been plugged-in, the write command stores the
content of the battery-buffered RAM as
S7PROG.WLD at the MMC. The
write command is controlled by means of the Siemens hardware
configurator via
PLC > Copy RAM to ROM. During the write process the
"MMC"-LED of the CPU is blinking. When the LED expires the write
process is finished. Simultaneously a write process into the internal Flash
memory of the CPU takes place.
After a write process onto the MMC, an according ID event is written into
the diagnostic buffer of the CPU. To monitor the diagnosis entries, you
select
PLC > Module Information in the Siemens SIMATIC Manager. Via
the register "Diagnostic Buffer" you reach the diagnosis window.
The following events may occur:
Event-ID Meaning
0xE100 MMC access error
0xE101 MMC error file system
0xE102 MMC error FAT
0xE200 MMC writing finished
0xE300 Internal Flash writing finished
More information to the event IDs may be found at the end of this chapter.
Note!
If the size of the user application exceeds the user memory of the CPU, the
content of the MMC is not transferred to the CPU.
Execute a compression before the transfer, for this does not happen
automatically.
Transfer via
MMC
Transfer
MMC→
→→
→RAM→
→→
→ROM
Transfer
RAM→
→→
→MMC→
→→
→ROM
Transfer control