Troubleshooting Insufficient Memory Module Size Issue with 1747-M13 EEPROM Memory Card on SLC500 5/03 PLC

Question:

Hello everyone, I am currently facing a challenge with adding an eeprom memory card to my SLC500 5/03 PLC. I aim to have the program load from the eeprom upon boot or in case of a memory issue with the main 5/03 PLC. However, I am encountering an error message stating "insufficient memory module size" every time I attempt to download the file to the eeprom. The eeprom module in question is 1747-M13 with a capacity of 64kb. I am unsure if the issue lies with my actions or the file itself. Interestingly, my program indicates a size of 70kb, but upon creating a blank program with just one line, it showed a size of 65kb. Any guidance on this matter would be highly appreciated as this is my first experience with an eeprom module, leading me to believe that I may be overlooking a simple step.

Top Replies

Is it possible that the PLC requires a firmware update? If so, double-check the memory card labeling. Consider upgrading the firmware to resolve any issues. - James

James Mcquade asked about the firmware version of the PLC and suggested that it may require an update for optimal performance. In addition, the processor manual specifies that the OS302 series C is necessary to utilize a memory module. Mr. Ro Bot shared a humorous anecdote about program file sizes, highlighting that the size on a computer may not accurately reflect the memory usage in the processor. Different 5/03 models come in 8k, 16k, and 32k memory sizes, making the 1747-M13 a suitable option for any model.

I have encountered an issue with my 5/03 w/ OS302 series C PLC. Despite adding a memory module, I am unable to download the program as it shows an error message: "StoreToEeprom failed: 0x4". I am currently in PROG mode and can proceed to selecting a permanent write option, but the download fails immediately after clicking ok. Any ideas on how to troubleshoot this issue?

Inquiring about the timeframe of "right after" in connecting devices? One possible explanation for connection issues is that the SLC may stop communicating with your PC during a write operation, causing a timeout depending on the connection method (such as using a 1747-UIC). If this is the case, allow for more time for the write to complete (approximately a couple of minutes) and monitor the processor's LEDs for confirmation. Unfortunately, there is no direct way to verify the success of the write operation other than attempting to load from the EEPROM and checking if the stored program is intact.

I had previously referenced that particular thread, but initially brushed off the error code I received when saving to EEPROM. After further investigation, I confirmed that the data is indeed being saved correctly. It is odd, however, that an error message persistently appeared despite successful saving. Moving forward, I will be sure to double-check my work to avoid any future misunderstandings. Thank you to everyone who provided assistance!

Hi there! It sounds like you're on the right track with your troubleshooting. That error message is typically indicative of a mismatch between the program size and the EEPROM capacity. Given that your blank test program still exceeded the EEPROM's 64kb capacity, it seems there might be some additional data or overhead that is typically stored on the EEPROM which your software is counting in that total. It's possible that this overhead data might be causing your real program to exceed the EEPROM's capacity. Your best bet might be to either cut down your program size or switch to a larger capacity EEPROM module. I hope this helps and good luck with your project!

Hi there! Your program file size might be larger than the capacity of your eeprom. As you mentioned, your program is 70kb but the eeprom module 1747-M13 has a 64kb capacity, so that could be where the "insufficient memory module size" error message is coming from. You should also check the size of your "blank" program because if it's showing a size of 65kb, that still exceeds the capacity of the eeprom. It might be worth trying to streamline or optimize your program to reduce the file size. Also, keep in mind, the SLC500 5/03 PLC does not directly load programs from the EEPROM, it must be manually loaded into the PLC after a power cycle. You might need to consult the programming manual to see if there's a discrepancy in your process. Happy to help further, if needed!

Hey there! Based on the information you've provided, it sounds like you might be running into an issue with the program size exceeding the eeprom's capacity. The 1747-M13 module can hold up to 64kb, while your program is 70kb. Hence, the "insufficient memory module size" error message makes sense. Even your blank program is slightly over capacity at 65kb. Could it be possible that your PLC software is reserving some memory for system files or processes, thus impacting the available storage on your eeprom module? You might want to consider streamlining your current program to fit within the eeprom's capacity, or perhaps look into an eeprom module with a larger memory size. Additionally, ensure your PLC isn't running any unnecessary background processes that could be hogging some precious memory.

It sounds like you’re really close to getting it working! The “insufficient memory module size” error typically means that your program is exceeding the capacity of the EEPROM. Since your main program is 70kb but the basic test is 65kb, it could be that there are some hidden elements or configuration settings in your program that also contribute to the size. Have you checked for additional data files or tags that might not be immediately visible? Also, consider breaking your program into smaller sections or optimizing it to fit within the EEPROM limits. Good luck, and I hope you get it sorted out soon!

It sounds like you're almost there, but the memory mismatch is definitely the sticking point. Since your program size is exceeding the EEPROM capacity, you might need to optimize or trim down the code to fit within the 64kb limit. Consider looking into unused tags, unnecessary instructions, or maybe even splitting the program into smaller functional blocks. Also, double-check the configuration settings in your software to ensure you're targeting the EEPROM correctly. If it's still giving you trouble, it might help to reach out to someone who's done similar tasks or check the user manual for any overlooked nuances with your PLC model. Good luck!

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

✅   Work Order Management

✅   Asset Tracking

✅   Preventive Maintenance

✅   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

You must be a registered user to add a comment. If you've already registered,
sign in. Otherwise, register and sign in.

Frequently Asked Questions (FAQ)

FAQ: 1. Why am I receiving an "insufficient memory module size" error when trying to download the file to the EEPROM on my SLC500 5/03 PLC?

Answer: Answer: The error message indicates that the file size exceeds the capacity of the EEPROM module (1747-M13 with a capacity of 64kb). This could be due to the actual program size being larger than the available memory on the EEPROM.

FAQ: 2. How can I resolve the "insufficient memory module size" issue with the 1747-M13 EEPROM on my SLC500 5/03 PLC?

Answer: Answer: To resolve this issue, you may need to optimize your program to fit within the 64kb capacity of the EEPROM module. You can try reducing the program size by removing unnecessary code or optimizing existing code to make it more memory-efficient.

FAQ: 3. Why does my program show a size of 70kb, but when I created a blank program with just one line, it showed a size of 65kb on the EEPROM module?

Answer: Answer: The discrepancy in program sizes could be due to how the program is compiled or stored in memory. It's important to ensure that the actual program size does not exceed the capacity of the EEPROM module to avoid the "insufficient memory module size" error.

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  →