If you're struggling with Error 8609-0, look no further than Knowledgebase Article 32507. Deleting and recreating modules in the I/O tree may just be the answer you're looking for. Additionally, try exporting the .ACD file to .L5K format and then re-adding the modules. Good luck troubleshooting!
JohnCalderwood inquired about your software upgrade process, asking if you upgraded directly from V20.1 to V24. Due to compatibility issues between V20.1 and V20.3, V20.4 was released to address this. A potential solution would be to uninstall V24, then install V20.4 (available for download from Rockwell), followed by reinstalling V24. Despite V20 still being RSLogix5000 and V24 being Studio5000, they are essentially the same program.
I initially installed V24, using V20 only to access my old program. As I no longer require V20, I have uninstalled and reinstalled Studio5000 V24 multiple times, but the module profile remains incomplete. Your assistance in resolving this issue would be greatly appreciated. Thank you!
In a recent excerpt from Knowledgebase Article 32507, Ron Beaufort mentioned finding a potential solution to a problem, likening it to "another straw at which to grasp." This reference was uncovered during a search for Error 8609-0, indicated in a popup on a posted screenshot. If you're facing a similar issue, best of luck in resolving it. Regarding the addition of a "module profile" in a new project, some modules such as the 1756-EN2T appear to be missing. Despite attempts to download and install AOP for EN2T, the issue persists, potentially stemming from the "registry." Thank you for your attention to this matter, Mr. Ron.
JohnCalderwood asked if you upgraded directly from V20.1 to V24, mentioning compatibility issues with V20.3. It is suggested to uninstall V24, install V20.4 (available for download from Rockwell), and then install V24 again. The versions, V20 and V24, although different (RSLogix5000 and Studio5000 respectively), are essentially the same program. There is no specific order for installing Logix5000 versions. Despite the insistence that the EN2T AOP is installed, it is recommended to uninstall and reinstall it.
To start, let's verify if the required AOP files have been properly installed. Depending on whether you have an x86 or x64 OS, navigate to the following directories: For x86 systems, go to C:\Program Files\Rockwell Software\RSLogix 5000\Module Profiles\, or for x64 systems, go to C:\Program Files(x86)\Rockwell Software\RSLogix 5000\Module Profiles\. Look for the folder named RA 1756 Ethernet, where you will find XML files for certain 1756 Ethernet modules. Additionally, check for a folder at the same path named RA 1756 ENet Comms, where XML files for other 1756 Ethernet modules are located. Both RSLogix 5000 and Logix Designer (Studio 5000) utilize the information in these XML files to configure Ethernet Module Profile instances. If you find both folders, please list the contents of the folders (file names) or share screenshots. Thank you, George.
One of my colleagues encountered a similar issue with his laptop. Despite several attempts, the AOP installation was unsuccessful. It appears that the problem stemmed from him deselecting certain installation options under module profiles. The only solution we found was to perform a hard drive wipe and reinstall the software. He expressed his reluctance to install unnecessary software components.
In a recent forum post, user Kev77 shared their experience with resolving a technical issue by wiping the hard drive and starting over. However, before resorting to such drastic measures, it's important to explore other troubleshooting solutions. Let's not jump to conclusions - there may be alternative methods to fix the issue at hand.
Geospark instructed to start by verifying the installation of the required AOP files. Depending on the operating system being x86 or x64, navigate to either C:\Program Files\Rockwell Software\RSLogix 5000\Module Profiles\ for x86 or C:\Program Files(x86)\Rockwell Software\RSLogix 5000\Module Profiles\ for x64. Look for the folder labeled RA 1756 Ethernet, where you should find specific XML files for certain 1756 Ethernet modules. Additionally, you should also locate a folder at the same path named RA 1756 ENet Comms, containing XML files for other 1756 Ethernet modules. These XML files are utilized by RSLogix 5000 / Logix Designer (Studio 5000) to configure Ethernet Module Profile instances. If both folders are present, kindly list their contents (file names) or share screenshots.
Hello George, I checked the "Module Profiles" folder and did not find the folders you mentioned (refer to image "moduleprof"). I tried installing AOP for Ethernet (see images moduleprof2 to moduleprof4) but was unsuccessful in adding the 1756-EN2T to my module profile list. Thank you, Andrei K.
Kev77 shared a similar experience with a coworker's laptop when trying to install the AOP multiple times without success. The issue seemed to arise from unchecked install options under module profiles during software installation. The only solution was to wipe the hard drive and start fresh, as the coworker opted out of installing additional features. Interestingly, I have never encountered a check/uncheck option for module profiles while installing RSLogix. However, a message "Initializing Module Profiles..." appears before the RSLogix installation process (refer to the attached image). Thank you, Andrei K.
According to Jeff Snyder, there is no specific order for installing Logix5000 installations. Despite the user's insistence, Jeff Snyder believes that the EN2T AOP may not be properly installed and suggests uninstalling and reinstalling it if necessary. However, a co-worker and Rockwell support provided conflicting advice when installing Studio/Logix/etc. 5000 on a new PC. Is it possible to simply install the latest version and then add older versions as needed? This contradicts the guidance given by Rockwell Automation, which advised installing the software versions one at a time, starting with the earliest anticipated need.
Amberman mentioned that despite advice from a co-worker and Rockwell support, installing Studio/Logix/etc. 5000 on a new PC was a matter of proper sequence. Instead of just installing the latest version and reverting to older versions as needed, it was recommended by RA to install them one at a time starting from the earliest anticipated need.
The order of installation is crucial as installing a newer software before an older one may result in overwriting crucial interdependent software versions, potentially causing malfunctions in the newer software. This is notably relevant for FactoryTalk Services Platform (FTSP), Module Profiles, and Motion Databases.
Sincerely, George.
Hello George, Popo Karimu here. I looked into the folders you mentioned in the "Module Profiles" folder but couldn't find any of them (refer to image "moduleprof"). I tried to install AOP for Ethernet (see images moduleprof2 to moduleprof4) but still couldn't add 1756-EN2T to my module profile list. It seems like your "Module Profiles" folder is empty, which is problematic. The most crucial folder that should be present before installing any MPs is the "Core" folder, which contains the MP Core files. Your Studio 5000 v24 installation package seems to be failing to install the MP Core, causing issues with adding any MPs. This is likely why the AOP for Ethernet modules is not showing up and your module selection is empty.
During the installation process, you should see "Initializing Module Profiles" as the setup initializes. This may take some time as there are many files to unpack and prepare. When selecting components and tools for installation, Logix Designer and "Module Profiles" should be automatically selected and cannot be unchecked. It should not be the case that you are forgetting to install "Module Profiles" during the Studio 5000 installation.
If you are encountering issues with the installation, especially related to MPs, check your installation media for the necessary files. Each version of RSLogix 5000/Studio 5000 comes with preloaded MPs, with newer software versions including newer MP versions. For a list of MPs installed with each software version, refer to the link provided.
If the MP Core is not installing properly, you can try installing it separately by running MPSetup.msi from \24.00.00-Studio5000\LogixDesigner\MP\Install. If the folder or file is missing, you may have incomplete installation media. Make sure to have all the necessary folders and files for a successful installation.
Thank you,
Andrei K.
Geospark noted that the "Module Profiles" folder appears to be empty, with the crucial "Core" folder missing. This folder contains the essential MP Core files necessary for installing MPs. The Studio 5000 v24 installation package seems to be failing to install the MP Core, resulting in blank AOP for Ethernet modules and an empty module selection. During the installation process, "Module Profiles" is automatically checked as a default component that cannot be unchecked. Despite this, the necessary MP installation files should be located within the installation media. It is important to closely monitor the installation process for any missed messages or errors. In case of missing files, such as the "MP\Install" folder or "Core" folder, incomplete installation media may be the issue. Optionally, the MP Core can be installed separately by running the "MPSetup.msi" file from the correct directory in the installation media.
If you encounter any issues during the installation process, closely monitor the installation and ensure all necessary folders and files are present in the installation media.
Geospark emphasized the importance of the installation order, stating that it can greatly impact the functionality of interdependent software. For example, installing a newer version before an older one may cause compatibility issues, ultimately rendering the newer software unusable. One such software affected by this is the FactoryTalk Services Platform (FTSP). It is crucial to follow a specific installation sequence to avoid such complications.
In contrast, amberman shared a different perspective, mentioning advice received from a co-worker and Rockwell support. They questioned whether it would have been feasible to install the latest version first and add older versions as needed. Despite a recommendation from Rockwell Automation to install versions sequentially, amberman decided to test this theory by installing versions V28 through V10 in reverse order on a new work computer. This method allowed for time-saving benefits, as it eliminated the need to reinstall additional software with each version, provided that the system could recognize the newer versions already in place. Only through practical implementation will the true outcome of this approach be determined.
After tirelessly working through this frustrating issue, I finally found a solution! It turns out that all I needed to do was install Logix software on a new computer. To troubleshoot the problem, I examined the contents of the RSLogix Module Profile folder located at 'C:\Program Files (x86)\Rockwell Software\RSLogix 5000\Module Profiles' and discovered that the Module Profile folder on my malfunctioning PC was empty.
I then proceeded to install RSLogix software on a fresh PC and observed a list of Module Profiles in the Module Profiles folder. By copying and pasting the Module Profiles folder from the fresh PC to my working laptop, I was able to pinpoint the issue - the presence of 4 "Module Profile dll's" at 'C:\Program Files (x86)\Common Files\Rockwell':
1) ModuleBrowseInfo.dll
2) ModuleDirectory.dll
3) ModuleDirectory.xml
4) MPModuleDirectory.dll
Simply transferring these 4 dll files from the fresh PC to my working laptop resolved the problem completely! I appreciate everyone's assistance and hope that my experience can be beneficial to others facing a similar challenge.
It seems like my challenges persist with the 1756-EN2T module. Every time I try to add it to my project, I receive an error message stating "Failed to instantiate Module Profile. Profile services failed to instantiate. Class not registered,, Error 8612-80040154." This recurring issue is becoming exhausting for me.
If you're looking for a Rockwell KB file that's too large to post, just send me a PM with your email address and I'll forward it to you directly.
- 23-01-2025
- JohnCalderwood
John Calderwood mentioned that he has a Rockwell KB file to share, but it's too large to upload here. Please message him your email address so he can send it directly. Have a great day, John! I've sent you a private message. Thank you!
Great news! After a week of struggling, I finally found the solution to my problem with RSLogix software. Despite having all module profiles present, I couldn't get it to work even after reinstalling everything. However, I discovered that the Module Profile folder on my corrupted PC was empty. The key was to install RSLogix on a new computer, where I found a list of Module Profiles. By copying the Module Profiles folder and the four culprit files - ModuleBrowseInfo.dll, ModuleDirectory.dll, ModuleDirectory.xml, and MPModuleDirectory.dll - from the new PC to my working laptop, the issue was resolved. Thank you to everyone who assisted me, and I hope this information can help others facing the same challenge.
After 8 years, I am encountering a comparable issue with Logix Designer on an 8th generation Logix PLC (5580). I am unable to adjust the Output State and Values when a Fault occurs, which is quite exasperating.
I was informed that upgrading Version 20.xx to a higher version may not be possible, potentially due to compatibility issues with the processor. Unfortunately, I cannot recall the specifics at the moment. - James.
James Mcquade mentioned that there is a limit to converting Version 20.xx to a higher version, possibly due to processor compatibility issues. He noted that Control Logix is up to version 20, while Design Logix is beyond that point. In a thread that is eight years old, an unresolved issue regarding resource-related problems was discussed, rather than corrupted files. Specifically, Logix Designer v35.1 had limitations with modifying module profiles on an 8th generation Logix PLC (5580), leading to frustrations during the system building process. The solution involved reinstalling the software and reconfiguring all Flex5000 I/O modules. For further insights on this topic, visit www.plctalk.net.