New ✨ Introducing Oxmaint Asset Hub for Machine Builders and OEMs. Explore Now

Q&A Community

Troubleshooting FT Studio 5000 Error: Address Offset Out of Range - Fixing HMI Display Stuck on Starting Application

Question:

When the customer turns off the machine and then turns it back on, the HMI display remains stuck on "Starting Application." If you encounter this issue and try to save Studio 5000 online, you may encounter error messages similar to those detailed in this technical note: . The FT Studio errors include "Failed tag information upload on route cip= at and Symbol upload ends with error for CIP= at ," as well as a PLC Save Error: "Error 732-80044402 - Data upload did not complete. CIP Error: Address offset out of range." Following the instructions in the technical note, rebuilding and downloading the project can resolve the errors and restore the display. However, the note does not provide a specific root cause for the issue. Have you encountered this error before?

Top Replies

Absolutely! I was in shock when I finally got mine working. Initially, my HMIs were running on v9, which made my situation even worse. Only when I updated one of them to v12 did the application finally load, but I encountered CIP route errors when uploading tags. Surprisingly, the upgrade to v12 didn't resolve the issue, but upgrading the CPU (specifically, our 5069-L310ERS2 model) to v33 did the trick. I discovered that by creating a UDT through online editing and utilizing it in the program, then cycling power on the machine, I would encounter CIP route errors. While I cannot guarantee that upgrading the CPU alone will solve your issue, I can confirm that there were no issues between v33 and v12. I hope this information proves helpful to you!

Although this issue began a while ago, I am experiencing the same problem. My idea is to increase the Programmable Logic Controller (PLC) from 32.011 to 32.014 instead of 33. However, my current Control Flash programs are not advanced enough to make this change, so they also require an upgrade. It seems that complexity is always present in the world of Rockwell.

I am experiencing the same issue with my Controller V32 and FTV V12. Despite seeking help from ROCKWELL Support, I have yet to find a solution. As the machine is ready for shipment to the US, I am feeling lost and turned to online searches for answers. Here are some key details regarding the problem: 1. The system does not recover after restarting the PLC or HMI. 2. Occasionally, going online with FTV or pressing the "play" button helps in recovering. 3. Compiling and downloading the FTV project to the HMI has also led to recovery. 4. There was one instance where it recovered on its own after 24 hours. 5. Downloading the latest firmware to the HMI took an unusually long time, hinting at a potential network issue. I am looking to prepare a V33 software/firmware for installation on-site. If anyone has any other suggestions or ideas, please share them as the project deadline is approaching quickly. Your input is greatly appreciated. Greetings from Germany.

Is there any involvement of managed switches in this scenario?

We have not experienced this issue since updating to version 33.

More Replies

Within our network, we currently have three Stratix 1783-LMS8 switches that have not been configured. As per the manual, they are supposed to function as unmanaged switches. However, when I directly connected the PLC to the HMI to troubleshoot, I encountered the same issue. An error message appeared stating "write operation failed for 1 items because write connection could not be established on route cip=1." After initiating the running man, I observed a message indicating "write connection established on route cip=2," and the system began functioning properly once more. I am curious about the significance of "cip route x" as I could not locate any information on it, and even the ROCKWELL support team was unable to provide clarification.

In my opinion, leaving managed switches unconfigured is more detrimental than utilizing unmanaged switches. Make sure to review HMI designer shortcuts and delete any that are not being used.

If you encounter the PLC Save Error 732-80044402 with a CIP Error stating "Address offset out of range" while attempting to save your program, try using the Save As feature to resolve the issue. This error is commonly reported on V32 systems. If saving as didn't work, consider using the Compact feature as an alternative solution.

I encountered the same issue with Studio V32.04 on a 1756-L72 controller running V32.11. To resolve this, I performed a direct upload without opening a project file (by accessing Studio 5000 Launcher and selecting Open -> From Upload). None of the previously mentioned solutions were effective, possibly due to changes in AOIs and UDTs causing unoptimized bytes allocation. I discovered that ControlLogix (CLX) does not optimize a sequence of bools with 4-byte gaps between them, allocating 32 bits for each sequence separately. I made adjustments to the UDT to reduce the total byte usage, which was reflected in the block's byte summary. It is likely that the outdated ACD file contained structures and UDTs in a different sequence, causing an error when uploading data from the PLC.

I encountered a communication problem between the 5069-L306MRS2 v32 controller and Panelview 7 v10 at our factory. Despite successful debugging, the HMI-PLC communication failed after the machine was powered off overnight. Upgrading the PLC to version v33 resolved the issue, even after power cycling with a one-minute wait. This demonstrates the importance of keeping your PLC firmware up to date to maintain seamless communication between devices.

Frequently Asked Questions (FAQ)

FAQ: 1. What should I do if my HMI display is stuck on "Starting Application" in FT Studio 5000?

Answer: Answer: If your HMI display is stuck on "Starting Application" in FT Studio 5000, you may encounter error messages such as "Failed tag information upload" and "PLC Save Error: Address offset out of range." You can try rebuilding and downloading the project as a troubleshooting step to resolve these errors.

FAQ: 2. How can I fix FT Studio 5000 errors related to CIP and IP address issues?

Answer: Answer: Errors in FT Studio 5000 related to CIP and IP address issues, such as "Failed tag information upload on route cip= at " and "Symbol upload ends with error for CIP= at ," can be resolved by following the instructions in the technical note provided in the discussion thread.

FAQ: 3. What is the recommended solution for resolving the PLC Save Error related to address offset out of range in FT Studio 5000?

Answer: Answer: If you encounter a PLC Save Error in FT Studio 5000 with the message "Error 732-80044402 - Data upload did not complete. CIP Error: Address offset out of range," you can try rebuilding and downloading the project to fix the error and restore the display functionality.

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