show the entry list

S7-300 Memory Cards -- Product information -- Technical data 
In STEP 7 (TIA Portal), how do you format an MMC or MC and why does a message appear saying that the SDB 7 is not loaded? 
Which devices can you use to read from, write to or delete from an S7-300 MMC (Micro Memory Card) outside the CPU? 
How do you format or reset an MMC (Micro Memory Card) for SIMATIC S7-300 CPUs? 
Why does the SFC 54 "RD_DPARM" not work with the new S7-300 CPU with MMC? 
How do you create a label for the Micro Memory Card (MMC)? 
How can you read out the identification data (the serial number of the MMC, for example) with the SFC 51 in STEP 7 V5.5? 
What points do you need to remember during the handling of micro memory cards? 
Why can't I see the values which are transmitted to an unlinked destination DB with SFC84, even though SFC84 is not indicating an error (RET_VAL = W#16#000? 
Which memory cards can you use with an S7-300 CPU? 
What is the effect of the STEP 7 function "Copy RAM to ROM"? 
How do you delete the data on an MMC (micro memory card)? 
How can you also store other files that belong to the project or plant on the MC/MMC? 
How do you copy the user program from the load memory into the main memory without PG with a S7-300 CPU with MC slot? 
How does the CPU 31x/31xC/C7 react when an MMC fault occurs during the save procedure? 

In STEP 7 (TIA Portal), how do you format an MMC or MC and why does a message appear saying that the SDB 7 is not loaded?Go to beginning
Part number:

Description
Micro memory cards (MMC) or memory cards (MC) are used in TIA Portal projects with an S7-300/S7-400 CPU. We describe the following topics in this entry.

  1. Formatting a Micro Memory Card or Memory Card with a USB Prommer
  2. Message: Cannot load SDB 7 for S7-300

Formatting a Micro Memory Card or Memory Card with a USB Prommer

Instructions
You must execute the following steps to format a micro memory card or memory card in TIA Portal using an external USB prommer.
 
No. Procedure
1 The prommer must be connected to the programming device by USB.
 
2 Check which interface is forwarded to STEP 7 (go to "Control Panel" of the Windows operating system and then "Parameterize Memory Card").


Fig. 01

The "External prommer" options must be enabled here (At the connection: USB).

3 Now it is possible to delete the MMC or MC with the menu (if everything has been set correctly).


Fig. 02

If the setting has not been made as in Fig. 1, you get the message shown below.


Fig. 03

4 Confirm the next dialog field with "Yes".


Fig. 04

5 Once the procedure has been completed successfully, the following lines are entered in the "General" tab of the inspector window.


Fig. 05

Table 01

Message: Cannot load SDB 7 for S7-300
Below are reasons why you get the messages indicating that block SDB 7 cannot be loaded or that the block/OS update is too big when downloading with STEP 7 V5.x or STEP 7 (TIA Portal).

  • No MMC. Slot an MMC that has sufficient capacity into the CPU.
  • MMC is defective. Replace the existing MMC with a new MMC.
  • CPU is defective and MMC is not recognized. You should consider this last possibility only if you have already replaced the MMC with a new one.

Creation environment
The screens in this FAQ response were created with STEP 7 (TIA Portal) V12.

Additional Keywords
13:4589

Which devices can you use to read from, write to or delete from an S7-300 MMC (Micro Memory Card) outside the CPU?Go to beginning
Part number:

Device note
The SIMATIC Micro Memory Cards (MMCs) of the S7-300 may be read or written only by the following devices outside the CPU:

  • SIMATIC Field PG
  • SIMATIC Power PG
  • USB prommer (order number 6ES7792-0AA00-0XA0).

Using these devices, you can open an MMC in the SIMATIC Manager for reading or writing or for deleting the content.


Fig. 01

Note
Do not use the MMC for non-SIMATIC purposes and do not format it with a third-party device. This would possibly overwrite the internal structure of the MMC that cannot be restored. In this case, the MMC is no longer recognized/accepted in a SIMATIC S7-300 CPU and can no longer be used with SIMATIC devices.

More information on handling the MMC is available in the manual "S7-300, CPU 31xC and CPU 31x: Installation Instructions" in Entry ID 13008499.

How do you format or reset an MMC (Micro Memory Card) for SIMATIC S7-300 CPUs?Go to beginning
Part number:

Description
It is not possible for users to format a SIMATIC Micro Memory Card (MMC). All you can do is "reset" an MMC, which deletes all user data.
How to reset an MMC is described in Entry ID: 29801950.

Why does the SFC 54 "RD_DPARM" not work with the new S7-300 CPU with MMC?Go to beginning
Part number:

Description  
In the new S7-300 CPUs with micro memory card, SFC 54 "RD_DPRARM" for reading out a data record of a chosen block of the system data configured with STEP 7 has been replaced by SFC 102 "RD_DPARA".

SFC 102 "RD_DPARA", in contrast to the old SFC 54 "RD_DPARM", is a system function that is executed asynchronously. This means that the processing is extended over various SFC calls. 

Blocks containing SFC 54 "RD_DPARM" cannot be loaded to a new S7-300 CPU with MMC? Therefore, please replace the call of the SFC 54 "RD_DPARM" by the call of the SFC 102 "RD_DPARA" and change your programming logic to the asynchronous behavior of the SFC 102 "RD_DPARA".

Below is a comparison of the two system functions.
 
SFC 54 "RD_DPARM" SFC 102 "RD_DPARA" Comments

          Inputs

 
--- REQ Function will be executed only with REQ=1; new for SFC 102.
IOID --- Parameter has been dropped for SFC 102; see LADDR.
LADDR LADDR SFC 54:
any block address, specification of the I or Q address range with IOID (B#16#54=IO input; B#16#55= IO output) SFC 102:
any block address, specification of the I or Q address range with bit 15 of LADDR (most significant bit). Bit 15=0 -> IO input; Bit 15=1 -> IO output. 
RECNUM RECNUM Use identically.

         Outputs

 
RET_VAL RET_VAL Use identically; however, there are additional error numbers available for SFC 102.
--- BUSY BUSY=1; the job has not yet been finished, no results are available yet.
RECORD RECORD Use identically.
Table 1: Comparison of SFC 54 and SFC 102

How do you create a label for the Micro Memory Card (MMC)?Go to beginning
Part number:

Description 
The "Microsoft Office Word 2003" program gives you the option of creating labels. For this you start the "Word 2003" program, go to "Tools > Letters and Postage > Envelopes and Labels..." and open the window shown in Fig. 1.


Fig. 01: Envelopes and Labels

Now, in the "Envelopes and Labels" window you select the menu item "Options... > New Label..." to open the window shown in Fig. 02.


Fig. 02: Dimensions of label created

In the window shown in Fig. 2 you can specify the dimensions of the label. Here you must note that a label for Micro Memory Card (MMC) must not exceed a height of 2.5cm and width of 2.1cm.

Keywords
Label, Labeling

How can you read out the identification data (the serial number of the MMC, for example) with the SFC 51 in STEP 7 V5.5?Go to beginning
Part number:

Description
With the SFC 51 "RDSYSST" (read system status) you can read out system status lists or excerpts of system status lists. More detailed information about parameterizing the SFC 51 and about error evaluation is available in the STEP 7 Online Help. For this you mark the SFC 51 in the SIMATIC Manager and press the "F1" key.

You need the following parameterization in order to read out the serial number of the MMC:

  • SSL ID W#16#011C "Identification of a component"
  • Index W#16#0008 "Serial number of the memory card"

Fig. 01 shows the call and parameters of the SFC 51 "RDSYSST".


Fig. 01

The table below specifies which other identification data can be read out depending on the CPU type and firmware version. For this you use SFC 51 and SSL ID W#16#011C.
 
Index Designation S7-300/C7 S7-400
W#16#0001 Name of automation system Firmware version V2.2 onwards Yes
W#16#0002 Name of CPU Firmware version V2.2 onwards Yes
W#16#0003 Facility ID of CPU Firmware version V2.2 onwards Yes
W#16#0004 Copyright entry Firmware version V2.2 onwards Yes
W#16#0005 Serial number of CPU Firmware version V2.2 onwards As from MLFB 6ES741x-xxx04-0AB0
W#16#0006 Reserved for operating system - -
W#16#0007 CPU type name - Yes
W#16#0008 Serial number of the MMC Firmware version V2.0 onwards
(CPU317: as from firmware version V2.1)
Firmware version V5 onwards

Notes on the output of SFC51 with a Field PG
When you read out the serial number of an MMC with SFC51 on the Field PG, the output data of the SFC51 is different to the serial number of the MMC. The reason for this system-specific behavior is that the digits of the hexadecimal code have been resorted through processing of the SFC51. For the output of a serial number, 1342498713, for example, with the SFC51 you get the value 99E70450Hex .

The table below explains how the SFC51 output is made after resorting of the digits.
 
Serial number of the MMC: 1342498713
Hex code of the serial number: 5 0 0 4 E 7 9 9
Designation of the digits: a1 a2 b1 b2 c1 c2 d1 d2
Digits are resorted with SFC51: d1 d2 c1 c2 b1 b2 a1 a2
Display with SFC 51: 9 9 E 7 0 4 5 0

There is a unique serial number saved on the memory cards of S7-400 version V5 onwards and the MC serial number can be read out using any SIMATIC S7-400 CPU with firmware V5.0 onwards.


Fig. 02

Further Information
The following documents contain further information about the memory cards and the system status list.

  • For MC:
    device manual "S7-400 Automation System, CPU Specifications"
    (Entry ID: 23904550),
  • For SSL:
    reference manual "System and Standard Functions for S7-300/400"
    (Entry ID: 1214574).

Additional Keywords
Memory card, RAM card, FLASH card, FEPROM card, System status list

What points do you need to remember during the handling of micro memory cards?Go to beginning
Part number:

Description:
This entry describes how to work with Micro Memory Cards (MMC). A sample project is also included in Point 4. The program shows how you can check whether specific data in a data block is located in the load memory.

1. How should I save blocks or configuration data on the MMC which are transferred online to the CPU?

When you load blocks (OB, FC, FB, DB) and system data (from the HW Config among other places, for example) into the CPU, they are automatically saved in such a way as to be safeguarded against voltage failure. The MMC is a flash EPROM medium.

2. Is there still need for the "Copy RAM to ROM..." function?

Not for saving blocks. However, if you have changed data blocks, for instance if you have optimized control parameters, this function also allows you to save the changed data values on the MMC (i.e. on the load memory), which means that these new values are also available following general PLC resetting (including in cases where the MMCs are used as spare parts in another CPU).

Warning:
Please note carefully that the "Copy RAM to ROM..." function affects all data blocks that are identified as "unlinked". In the case of these data blocks, when the "Copy RAM to ROM..." function is performed, the initial values in the load memory (on the MMC) are overwritten with the actual values in the main memory.
For all data blocks, the initial values are taken as new values after an overall reset. In the case of non-remanent data blocks the initial values are also taken as new values after POWER OFF/ON or after STOP/RUN operating modes.

If you want to save individual data blocks or data block elements in the load memory, you can use SFC84 to do that. Here, please note the following Point 3.

3. Can I save data blocks on the MMC via the user program, i.e. use the content as new initial values in the load memory?

CPUs with MMCs feature the SFCs 82, 83 and 84 for this purpose:

  • SFC82 allows you to set up a data block in the load memory.
  • SFC83 allows you to copy data areas from the load memory to the main memory, and
  • SFC84 saves data areas in the load memory, i.e. it performs the function which is formulated in the question. However, bear in mind that the MMCs support a limited number of writing cycles (according to the manufacturer's details, 100,000 writing cycles are possible). For details about the memory concept of CPUs (load memory, main memory... ), please refer to the FAQ in Entry ID 7302326.

4. How can I check whether the data is really saved in the load memory with SFC84?

A check is possible if the data block is declared as "unlinked".
After copying an "unlinked" DB with SFC83 to the working area of another DB you can make a check. In the load memory itself it is not possible to access with a variables table or via "Monitor/control variable", because access is made here to the working area. There is an example of how to work with SFC83 attached. This illustrates how the SFC 84 works.
Please also bear in mind that SFC 83 and SFC 84 work asynchronously. This means that the SFCs might need several cycles to complete a job.
If the data block in the load memory has the attribute "unlinked", you can make the check by loading the DB into the PG. Here, STEP 7 retrieves the current values from the load memory during each loading process. In this regard, also refer to the FAQ in Entry ID 21688777.

Sample project:
Save the "MMC_S7_300_SFC83.zip" file in a separate directory and then dearchive it. The S7 project then unpacks with all the associated subdirectories. You can use the SIMATIC Manager to open and process the extracted project.

MMC_S7_300_SFC83.zip ( 158 KB )

5. When is it useful to compress an S7-300 CPU with MMC?

Deleting blocks on the CPU creates gaps in the load and main memories. The gaps are not automatically closed when new or changed blocks are transferred. When you compress, the gaps are closed by copying the existing or new blocks. The procedure is comparable with the defragmenting of hard disks in Windows.
You reduce cycle times by compressing. That is why it is only useful to compress in order to close a large number of gaps after blocks have been deleted frequently in the CPU.
Compressing just after performing the "Load user program onto memory card" function is not useful, because the MMC is deleted when the function is performed and the blocks can be transferred without any gaps onto the MMC.

Warning:
Compressing, transferring and deleting blocks extends the cycle time of the CPU.
In the STOP operating mode you can perform compressing completely. In the RUN-P operating mode, blocks that are open because of the running program cannot be moved when compressing is performed.

Why can't I see the values which are transmitted to an unlinked destination DB with SFC84, even though SFC84 is not indicating an error (RET_VAL = W#16#000?Go to beginning
Part number:

Description:
Data blocks which are declared as unlinked are not monitored in CPUs with MMC. Data in an unlinked DB isn't constantly updated in the online view of the project, even though Monitor (glasses) is enabled. This means that data transfer to the MMC by means of SFC 84 (WRIT_DBL) cannot be monitored dynamically. One-off updates occur if you close the relevant data block and then open it again online. This data is represented by glasses crossed out in the variables table.

Keywords:
Sequence-relevant
Micro Memory Card

Which memory cards can you use with an S7-300 CPU?Go to beginning
Part number:

Description
The attached download shows the S7-300 CPUs and the SIMATIC memory cards to be used with them.

Here we distinguish between the memory card types below:

  • MC (Memory Card)
    You can use an MC with older S7-300 CPUs with MC Slot.
    Dimensions: 57mm x 45mm x 7mm
  • MMC (Micro Memory Card)
    An MMC is imperative for operating all current S7-300 CPUs. 
    Dimensions: 32mm x 24 mm x 1mm


Fig. 01 MC on left and MMC on right

S7-300_Memorycard.pdf ( 76 KB )

What is the effect of the STEP 7 function "Copy RAM to ROM"?Go to beginning
Part number:

 
Description:
This entry describes how the SIMATIC S7 function "Copy RAM to ROM..." works. We will be looking at how it works on data and code blocks in SIMATIC S7-300 CPUs and C7 devices (with reference to the controller part) taking into account various storage concepts. Since deleting the EPROM memory is also partially executed via the "Copy RAM to ROM..." function, this entry also includes an overview of how various storage media can be deleted. There is also a brief description of how to change a memory card (MC) using the "Copy RAM to ROM..." function.
A description of the various storage concepts is available in Entry ID 7302326 for S7-300 and in Entry ID 7302549 for S7-400.

The entry is divided into the following sections:

General

On all CPUs you can only run the "Copy RAM to ROM..." function in the "STOP" operating mode. If the CPU is not yet in the "STOP" operating mode, you are ask whether the CPU should be switched to "STOP" via STEP 7.
The PDF file lists the S7-300 CPUs and C7 devices that support the "Copy RAM to ROM..." function.

  Liste_der_Geraete_e.pdf ( 34 KB )  

SIMATIC S7-300 CPUs and SIMATIC C7 devices with built-in RAM and EPROM as load memory

In the case of CPU modules that have a built-in EPROM you can use the "Copy RAM to ROM..." function to copy the content of the internal RAM load memory to the built-in EPROM load memory so as not to lose data in the case of power failure without battery or overall reset. In the case of SIMATIC S7-300 CPUs or C7 devices with internal EPROM as load memory the code and data blocks are written from the RAM load memory to the EPROM load memory.

Warning:
When you run the STEP 7 "Copy RAM to ROM..." function, the actual values of the runtime-relevant data blocks in the load memory are overwritten with the actual values from the main memory. If the runtime-relevant data blocks are then transferred again to the main memory (e.g. after overall reset), then the CPU takes the actual values from the load memory as initial values. These new initial values are displayed in SIMATIC STEP 7 in the "Actual value" column.
The following table describes the procedure in three figures.
 
No. Procedure
1 In the case of data blocks the initial values and the actual values are transferred from STEP 7 to the CPU in the load memory (internal EPROM). However, the initial value is always then taken as the "First actual value" in the main memory if no actual value has been defined in STEP 7. If an actual value defined in STEP 7, it is transferred to the main memory.


Fig. 01
 

2 When you perform the "Copy RAM to ROM..." function, the actual values in the load memory are overwritten with the actual values from the main memory.


Fig. 02
 

3 If the load memory is transferred again to the main memory (e.g. after overall reset), then the actual values from the load memory are taken as the "First actual values" in the main memory.


Fig. 03
 

Delete EPROM
The built-in EPROM is deleted by deleting the complete contents of the RAM and using the "Copy RAM to ROM..." function to copy the new RAM contents into the internal load memory EPROM. The procedure is described in the table below.
 
No. Procedure
1 Connect the programming device (PG) with the CPU.
2 Open the SIMATIC Manager and go to "PLC/Display Accessible Nodes".
3 Open the view of the blocks "Accessible Nodes / MPI = .../Blocks" (click on "+").
4 Mark the blocks to be deleted (the system data too if you wish). If you want to delete the complete internal EPROM, mark all the blocks to be deleted and the system data.
You cannot delete system functions (SFC) and system function blocks (SFB).
5 Delete the marked blocks via "Edit/Delete" or via the "Del" key.
6 Perform "PLC / Copy RAM to ROM...".
This copies all the valid blocks from the RAM load memory to the internal EPROM memory. The blocks deleted in the internal RAM load memory are thus no longer written to the internal EPROM load memory and are thus also deleted in the EPROM.

SIMATIC S7-300 CPUs and SIMATIC C7 devices with built-in RAM and an external memory card (MC)

When you perform the "Copy RAM to ROM..." function, the runtime-relevant program and data blocks are copied from the internal RAM load memory to the memory card (MC).

Warning:
When you run the STEP 7 "Copy RAM to ROM..." function, the actual values of the runtime-relevant data blocks in the load memory are overwritten with the actual values from the main memory. If the runtime-relevant data blocks are then transferred again to the main memory (e.g. after overall reset), then the CPU takes the actual values from the load memory as initial values. These new initial values are displayed in SIMATIC STEP 7 in the "Actual value" column.
The following table explains how to proceed in three figures. The procedure is identical for all 3 load memory types (internal EPROM, FLASH Memory Card, Micro Memory Card). The figures are repeated so that all the information on the load memory type is together.
 
No. Procedure
1 In the case of data blocks the initial values and the actual values are transferred from STEP 7 to the CPU in the load memory (memory card). However, the initial value is always then taken as the "First actual value" in the main memory if no actual value has been defined in STEP 7. If an actual value defined in STEP 7, it is transferred to the main memory.


Fig. 01
 

2 When you perform the "Copy RAM to ROM..." function, the actual values in the load memory are overwritten with the actual values from the main memory.


Fig. 02
 

3 If the load memory is transferred again to the main memory (e.g. after overall reset), then the actual values from the load memory are taken as the "First actual values" in the main memory.


Fig. 03
 

Change the Memory Card (MC)
 
No. Procedure
1 Set CPU in STOP mode.
2 Remove any slotted memory card.
3 Slot the "new" memory card.
4 Do an overall reset of the CPU.
5 If the memory card does not yet contain the matching user program, you must first load the user program into the CPU (internal RAM load memory) and then use "Copy RAM to ROM..." to transfer it to the memory card. Please note here that blocks already in the RAM load memory that are not overwritten by the new user program are also transferred to the memory card.

But here you can also use the "Load user program onto memory card" function directly.

Note:
It is not permitted to remove and slot the memory card (MC) in the RUN operating mode.
When you remove/slot a memory card the CPU demands an overall reset and so the user program is lost in the RAM.

Delete individual blocks
You cannot delete individual blocks from a memory card on the PG.
You can only delete individual blocks with a combination of the CPU and PG.
The requirement for this is that you slot the memory card in the CPU.
Then proceed as follows.
 
No. Procedure
1 Connect the programming device (PG) with the CPU.
2 Open the SIMATIC Manager and go to "PLC/Display Accessible Nodes".
3 Open the view of the blocks "Accessible Nodes / MPI = .../Blocks" (click on "+").
4 Mark the blocks to be deleted (the system data too if you wish).
5 Delete the marked blocks via "Edit/Delete" or via the "Del" key.
6 Perform "PLC / Copy RAM to ROM...". This copies all the valid blocks to the memory card. The block deleted in the CPU is then no longer written to the memory card and is therefore deleted.

Completely delete the memory card (MC)
 
No. Procedure
1 Slot the memory card into the programming device (PG).
2 In the SIMATIC Manager select "File/S7-MemoryCard/Delete".
3 Acknowledge with "yes" the security question asking whether you really want to delete.

If you are using a CPU with which you cannot write any memory cards or a PC with which you cannot write any memory cards, we recommend the prommer given below with its order number.
 
Order number Description
6ES7792-0AA00-0XA0 SIMATIC PG, USB PROMMER 115/220V

SIMATIC S7-300 CPUs and SIMATIC C7 devices with micro memory card (MMC)

When you perform the "Copy RAM to ROM..." function, the runtime-relevant data blocks are copied from the main memory to the MMC. Here the actual values of the data blocks are overwritten on the MMC so that after an overall reset new initial values (the new actual values) are effective. These new initial values are displayed in SIMATIC STEP 7 in the "Actual value" column.
The following table explains how to proceed in three figures. The procedure is identical for all 3 load memory types (internal EPROM, FLASH Memory Card, Micro Memory Card). The figures are repeated so that all the information on the load memory type is together.
 
No. Procedure
1 In the case of data blocks the initial values and the actual values are transferred from STEP 7 to the CPU in the load memory (MMC). However, the initial value is always then taken as the "First actual value" in the main memory if no actual value has been defined in STEP 7. If an actual value defined in STEP 7, it is transferred to the main memory. The actual values in the main memory are used when processing the program.


Fig. 01
 

2 When you perform the "Copy RAM to ROM..." function, the actual values in the load memory are overwritten with the actual values from the main memory.


Fig. 02
 

3 If the load memory is transferred again to the main memory (e.g. after overall reset), then the actual values from the load memory are taken as the "First actual values" in the main memory.


Fig. 03
 

In the case of CPU modules that work with a micro memory card (MMC) the load memory is on the MMC. When loaded, the program is stored on the MMC in such a way as to be immune to power failure and overall reset. The program is therefore always remanent in the load memory (on the MMC). 

Delete individual blocks on a micro memory card (MMC)

  • With the PG
No. Procedure
1 Slot the MMC into the programming device (PG).
2 In the SIMATIC Manager select "File/S7-MemoryCard/Open".
3 Mark the blocks to be deleted (the system data too if you wish).
4 Delete the marked blocks via "Edit/Delete" or via the "Del" key.
  • Via the CPU
    The requirement for this is that you slot the micro memory card in the CPU.
No. Procedure
1 Connect the programming device (PG) and your CPU.
2 Open the SIMATIC Manager and go to "PLC/Display Accessible Nodes".
3 Open the view of the blocks "Accessible Nodes / MPI = .../Blocks" (click on "+").
4 Mark the blocks to be deleted (the system data too if you wish).
5 Delete the marked blocks via "Edit/Delete" or via the "Del" key.

Completely delete the micro memory card (MMC)
 
No. Procedure
1 Slot the MMC into the programming device (PG).
2 In the SIMATIC Manager select "File/S7-MemoryCard/Delete".
3 Acknowledge with "yes" the security question asking whether you really want to delete.

Note:
In order to be able to read and write micro memory cards (MMC) on your PC too you need a prommer that can read and write the special format of the micro memory cards. A suitable prommer is available under order number 6ES7792-0AA00-0XA0.

You must never format the MMC in a standard slot or card reader with Windows, otherwise you will no longer be able to use the MMC for the SIMATIC-CPUs! (see Entry ID: 21830698)

SIMATIC S7-400 CPUs

The "Copy RAM to ROM..." function is not supported by S7-400 CPUs and the CPU S7-318 2DP. The options offered by the S7-400 are given in Entry ID 23670531.

Keywords:
Change

How do you delete the data on an MMC (micro memory card)?Go to beginning
Part number:

Description
Proceed as follows to delete the blocks on an MMC in the CPU.

  • Slot the MMC to be deleted in the CPU.
  • In the SIMATIC Manager switch to Online mode via "View > Online" or via the relevant button.
  • Select the block folder in the Online window.
  • Mark all the blocks in the folder.
  • Right-click and select "Delete" (you can acknowledge the message indicating that system functions cannot be deleted).

Note
If you wish to delete a password-protected MMC, proceed as follows.

  • Slot the MMC in the programming device (PG) or in the SIMATIC USB prommer on your laptop/PC.
  • In the SIMATIC Manager select "File".
  • Select "S7 Memory Card"    ==>    "Delete..."

Keywords
Flash MC, MC

How can you also store other files that belong to the project or plant on the MC/MMC?Go to beginning
Part number:

Instructions
You can store any files that are to do with the plant on the MC/MMC. 
Proceed as follows:

  • Slot the memory card or micro memory card in the PG.
  • Open the SIMATIC Manager.
  • Go to "File > S7 Memory Card > Open".
  • Then go to "PLC > Save to Memory Card...".


Fig. 01: SIMATIC Manager - S7 memory card

  • In the left file explorer select the required file and designate it for saving via the "-->" button.


Fig. 02: File selection

  • If you wish to remove files from the selection, use the "<--" button.
  • Acknowledge with the "OK" button to save the data selected on the memory card or micro memory card.
  • Once the data has been stored successfully you receive confirmation to that effect.
  • Then you see the data transferred in the "S7 memory card" window.


Fig. 03: Memory card data view

Note
You can only execute this function for an S7-300 micro memory card and S7-400 Flash EPROM card. 

The table below gives the order numbers for these cards.
 
Micro Memory Card / S7-300 Order number
64 Kbytes 6ES7 953-8LF20-0AA0
128 Kbytes 6ES7 953-8LG11-0AA0
512 Kbytes  6ES7 953-8LJ20-0AA0
2 Mbytes 6ES7 953-8LL20-0AA0
4 Mbytes 6ES7 953-8LM20-0AA0
8 Mbytes 6ES7 953-8LP20-0AA0
Memory Card FEPROM / S7-400 Order number
64 Kbytes 6ES7 952-0KF00-0AA0
256 Kbytes 6ES7 952-0KH00-0AA0
1 Mbytes 6ES7 952-1KK00-0AA0
2 Mbytes 6ES7 952-1KL00-0AA0
4 Mbytes 6ES7 952-1KM00-0AA0
8 Mbytes 6ES7 952-1KP00-0AA0
16 Mbytes 6ES7 952-1KS00-0AA0
32 Mbytes 6ES7 952-1KT00-0AA0
64 Mbytes 6ES7 952-1KY00-0AA0
Table 1: Order numbers

Keywords
Flash MC, MC

How do you copy the user program from the load memory into the main memory without PG with a S7-300 CPU with MC slot?Go to beginning
Part number:

Description
When a memory card with user program is slotted into a CPU, the CPU copies the runtime-relevant program sections into the main memory.

  • Slot the memory card.
  • Do an overall reset.
  • CPU copies the runtime-relevant sections of the program from the load memory into the main memory. In particular this initializes the data blocks in the main memory (their initial values are reset).

A PG is not required for this procedure. This applies, for example, also when different user programs are stored on different memory cards and are to run at different times in the same CPU.

Notes

  • The memory card must remain slotted for as long as the CPU is in operation, especially in RUN.
  • The CPU transfers the program from the load memory into the main memory even after "Power off" without buffering (also even if the battery has undervoltage during "Power off").

Keywords
Flash MC, MC

How does the CPU 31x/31xC/C7 react when an MMC fault occurs during the save procedure?Go to beginning
Part number:

Description
The service life of an MMC depends mainly on the number of delete and programming procedures. 
The memory blocks of the MMC memory permit at least 100,000 write/delete operations. This refers to the operations with STEP 7 and data block backups upon power OFF and with SFC 84. In particular, therefore, SFC 84 should only be called at corresponding time intervals (e.g. hourly, daily ...).

If there is an MMC defect during saving, then the relevant application (e.g. load block, SFC) issues a negative acknowledgment or RET_VAL. This indicates that the routine has not been executed.
A resources or memory error is then recorded in the diagnostics buffer of the CPU.

The MMCs are also used with the C7 complete devices C7-613/635/636.

Note
More information on this topic is available in the device manual "CPU 31xC and CPU 31x, Technical Data", in the chapter entitled "Properties of the SIMATIC Micro Memory Card". The manual is available in Entry ID: 12996906 .

 Entry ID:22122201   Date:2014-02-11 
I regard this article....as helpfulas not helpful                                 






























mySupport
My Documentation Manager 
Newsletter 
CAx-Download-Manager 
Support Request
To this entry
Print
Create PDF 
Send to a friend
QuickLinks
Compatibility tool 
Topics
Help
Online Help
Guided Tour