Troubleshooting Issues with SIMATIC 300 CPU 315-2DP and VIPA 603-1CC21 A1.0: RAM and Communication Errors Fix Needed

Question:

Hello, I am currently using a SIMATIC 300 with the CPU 315-2DP model (6ES7 315-2AF03-0AB0) and a VIPA 603-1CC21 A1.0 with 32KB of RAM and Firmware V4.0.8. I encountered an issue while using an MPI communication cable to upload the program from the station to my PG. The CPU 315-2DP is showing as okay, but the S7 program is not displaying blocks within blocks. When I try to upload the program from my PC, no errors are reported, but my HMI remains not ready. I attempted to copy the project from RAM to ROM, but encountered an error stating there is insufficient memory space or the specified storage medium is not accessible [(8301)]. Additionally, I received an error indicating no reply to step 7 message frame (33:16418). I am seeking assistance on how to resolve these issues. Thank you.

Top Replies

The Siemens S7-300 PLC does not support RAM to ROM transfer. If you're experiencing issues, consider inserting a larger capacity SD card into the processor. Your SD card may be insufficient for the program size, or the processor may have difficulty accessing it.

Thank you for getting back to me, Sir.

This sounds like a tricky situation. I'd like to suggest a few possible solutions. First, check if the MPI cable you are using is reliable. Any communication error could be due to a faulty MPI cable. Second, try clearing some space from your storage or check for any access restrictions that may prevent the uploading of your program and causing the 8301 error. Finally, verify your firmware version and potentially perform an update if one is available. For the block within block issue, check if the blocks are compiled properly before uploading. It might sound basic, but sometimes overlooking simple checks can lead to such problems. Also, ensure the correct network settings are in place in your HMI. Hope this helps, and I'm looking forward to hearing whether you found a solution.

It seems like you're experiencing quite a mixed bag of issues. I'd first suggest double-checking your MPI cable and the port to which it's connected– even a minor cable issue could disturb communication. The 'insufficient memory space' error might mean your project is too large for the VIPA 603-1CC21's 32KB RAM. Consider optimizing your project size, or possibly upgrading your CPU memory. The "no reply" error could possibly be a misconfigured station address. Check your network settings and confirm all devices are properly addressed. As always, remember to backup everything before making changes.

It sounds like you're dealing with quite a few issues there! For the memory error when trying to copy from RAM to ROM, double-check if the amount of free memory in your RAM is sufficient, as it might be competing with other processes. Also, ensure that the storage medium is correctly set and accessible in your configurations. As for the MPI communication issue, try using a different cable or port to see if there's a physical connection issue, and ensure all devices are powered properly. It might also help to update your firmware if there's a newer version available that addresses communication bugs. Good luck, and let us know how it goes!

It sounds like you're dealing with a frustrating set of issues there! The insufficient memory error (8301) often pops up if there's not enough space in the ROM for the project you're trying to copy, so checking how much you've got on the device would be a good first step. Also, double-check your MPI cable and connections, just in case there's a loose link causing the communication error and the HMI not being ready. If there're no issues with the hardware, you might want to try clearing up some space or simplifying your project to see if that helps with the upload. Good luck!

It sounds like you're facing a pretty tricky situation with your SIMATIC setup! For the insufficient memory error, double-check that the RAM on your VIPA unit is actually free and not filled with other projects, as that can often lead to the 8301 error. Also, try using a different MPI cable or check the connections, as a faulty cable can sometimes cause communication issues like the one you’re experiencing with the HMI. If the blocks are not displaying correctly, it might be worth ensuring that your programming software version is compatible with both the CPU and the VIPA unit. Lastly, consider resetting the HMI or cycling power to see if it resolves the "not ready" status. Good luck, and keep us updated!

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.

To add a comment, please sign in or register if you haven't already..   

Frequently Asked Questions (FAQ)

FAQ: 1. FAQ: What could be causing the issue of the S7 program not displaying blocks within blocks on the SIMATIC 300 CPU 315-2DP?

Answer: Answer: The issue with the S7 program not displaying blocks within blocks could be due to various factors like programming errors, communication issues, or memory problems. It would be advisable to check the program logic, connections, and memory settings to address this issue.

FAQ: 2. FAQ: How can I address the error message indicating insufficient memory space or inaccessible storage medium [(8301)] when trying to copy the project from RAM to ROM on the SIMATIC 300 CPU 315-2DP?

Answer: Answer: To resolve the error indicating insufficient memory space or inaccessible storage medium [(8301)], you can try optimizing the program size, checking the memory allocation settings, or ensuring the ROM storage medium is properly connected and accessible.

FAQ: 3. FAQ: What steps can I take to troubleshoot the error message indicating no reply to step 7 message frame (33:16418) on the SIMATIC 300 CPU 315-2DP?

Answer: Answer: When encountering the error message indicating no reply to step 7 message frame (33:16418), you may need to verify the communication settings, cable connections, and configurations between devices. Checking for any network disruptions or addressing possible hardware issues can help in resolving this communication 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  â†’