When accessing the Module Information in Simatic Manager under PLC -> Diagnostic/Settings, users will come across three key memory areas: Load Memory, Work Memory, and Retentive Memory. Interestingly, when making changes to the hardware configuration, such as adding I/O Cards, these alterations do not show up in these memory areas. However, switching over to Blocks -> Object properties -> Blocks reveals that changes in hardware configuration do impact the System Data Memory Bytes. This raises the question: Why do changes fail to reflect in Work, Load, or Retentive Memory despite modifications in hardware configuration?
It appears that the hardware is stored in the system data area rather than in working or loading memory. It seems like you have found the answer to your own question regarding hardware storage within the system.
Your query is quite intriguing! I believe the root of this lies in the differing functionalities of the three memory sectors. Load Memory, Work Memory, and Retentive Memory are essentially designed for operational or program data, storing PLC code instructions and runtime decisions. On the other hand, System Data Memory is responsible for storing system-related data, like hardware configuration changes and routing information. This is probably why you see alterations in hardware configuration reflecting in the System Data Memory, but not in Work, Load, or Retentive Memory. Let's remember that each compartment has its unique job, and they work synergistically to run a PLC smoothly!
In my experience dealing with Simatic Manager, the Load, Work, and Retentive Memory areas are largely used to delineate software, user data, and non-volatile data respectively. Hardware configuration changes may not reflect in these areas because they're not explicitly tied to those specific data sectors. However, as you rightly pointed out, they do considerably affect the System Data Memory Bytes. This is because system data serves as the interface between the software (user program) and the hardware, accommodating for inputs and outputs. Therefore, any material change in hardware configuration necessarily influences system data, hence the reported changes. That's the logic as far as I've understood the system.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Changes to the hardware configuration, such as adding I/O Cards, do not reflect in Load Memory, Work Memory, or Retentive Memory because these memory areas store program data and not hardware configuration details. Hardware configuration changes impact System Data Memory Bytes, which are reflected in Blocks -> Object properties -> Blocks.
Answer: The key memory areas related to hardware configuration in Simatic Manager are Load Memory, Work Memory, and Retentive Memory. While changes to the hardware configuration are not directly stored in these memory areas, they can affect System Data Memory Bytes.
Answer: To view the impact of hardware configuration changes on memory areas in Simatic Manager, navigate to Blocks -> Object properties -> Blocks. Changes in hardware configuration, such as adding I/O Cards, are reflected in the System Data Memory Bytes rather than Load Memory, Work Memory, or Retentive Memory.
Answer: A
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.