In my v31 application, I am using multiple G120C drives. The communication with the drives is functioning properly, but the IO tree is displaying an unregistered EDS file. I obtained the EDS file from Siemens' official website, however, when I attempt to run the EDS wizard in Studio, I receive an error indicating that the EDS file does not match the device. After contacting Rockwell support, their suggestion was that the module may be corrupted. Interestingly, when I access the program from a different EWS, the drives display their properties correctly and the EDS file functions as expected. Any insights or suggestions on this issue would be greatly appreciated.
Transfer the eds file from a functional computer to your own and ensure it is properly installed. Chances are, the specific eds file required may not be readily available. Opt for the standalone eds installer instead of the studio version for better results, as it has proven successful when studio installation has failed in the past.
Is it possible to extract the EDS file from the Rockwell EDS directory, which contains lengthy number strings, and then reimport it into the EDS installer on a malfunctioning device? I've observed instances where there is a mismatch between the EDS list in the software studio and the primary EDS application. For example, when I import a file through the main installer, it does not appear in the module list in the studio.
Yes, it is possible to duplicate EDS files. Typically, long-named alphanumeric files are associated with Rockwell products, while 3rd party files, like Siemens, often have identifiable names. In my experience, EDS files loaded through the app have always shown up in studio without any issues. If a file does not appear, it is likely due to a missing AOP, rather than an EDS file problem.
Robertmee mentioned that the absence of an AOP is often a sign that something is wrong, rather than an issue with eds. It is worth noting that Siemens may not have AOPs, which could be a factor in this situation.
mk42 mentioned that Siemens may not have Add-On Profiles (AOPs), although it's not confirmed. This comment was made in response to the OP mentioning a discrepancy they have observed in the past. It is presumed that this past observation may have involved Rockwell devices.
It sounds like the issue is most likely with your local software or settings rather than a corrupted module, given that the drives display correctly from a different EWS. You might want to try a clean reinstall of Studio on your system, ensuring all related files are properly deleted before the new installation. Also consider checking for any available updates or patches for the software, as this could be an issue that's been addressed already by the developers. It's also worth double-checking the version of the EDS file against the specific model of your G120C drives, just to rule out any compatibility issues.
It sounds like the problem might be localized to the specific EWS where you're experiencing the issue, especially given that it works fine on another system. I would start by completely uninstalling and reinstalling the EDS files on the EWS that's giving you problems. If that doesn't work, try checking if there's a difference in the versions of Studio between your two systems. An outdated version could potentially lead to compatibility issues. Additionally, double-check that you don't have any conflicting files on the problematic EWS. It's a bit of a process of elimination, but hopefully, it will help you pinpoint the snag!
It definitely sounds like a puzzling issue, but before jumping to conclusions about a corrupted module, I'd suggest a few other troubleshooting steps. Firstly, try re-downloading the EDS file from Siemens' website, just in case there was an issue with the initial download. It won't hurt to validate the file against the specs of the G120C drive just to ensure compatibility. Secondly, consider the possibility of local issues in your main EWS, as the fact that everything works fine on a different EWS points in this direction. It could be a setting or a software version discrepancy that’s causing the error. Just some thoughts, hope they help!
It sounds like there might be a mismatch between the EDS file and the specific drive version you're using in your v31 application. I've found that not all EDS files are created equal - sometimes a tiny version difference can cause such headaches. Try rechecking the EDS file version against your drive's firmware. Alternatively, since you mentioned it works fine from a different EWS, the issue might lie within the original EWS environment itself - possible a software or hardware compatibility issue. Ensuring EWS environments are consistent might be a good starting point too.
It sounds like you've already done a great job troubleshooting! Since the EDS file works on a different EWS setup, it might be worth double-checking the version compatibility between your current EWS and the G120C drives. Sometimes, subtle differences in firmware or software versions can lead to these mismatches. Have you tried reinstalling the EDS file or clearing the cache in your application? Additionally, if possible, compare the settings and configurations of the working EWS with your current setup to spot any discrepancies that could be causing the issue. Good luck, and I hope you find a solution soon!
It sounds like you've got a classic case of a corrupted EDS file or some version mismatch between your application and the device. Since the EDS file works fine on a different EWS, you might want to check if there are any discrepancies in the software versions or configurations between the two environments. Additionally, consider clearing your cache or re-importing the EDS file in your corrupted EWS instance; sometimes, residual files can cause issues. If all else fails, reaching out to Siemens for a fresh copy of the EDS file might help, just to rule out any corruption. Good luck!
✅ 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: 1. Why is my Studio 5000 showing an unregistered EDS file for Siemens G120C drives? - The error may occur if the EDS file does not match the device, potentially due to corruption or compatibility issues. 2. How can I resolve the issue of an unregistered EDS file in Studio 5000? - You may need to verify the integrity of the EDS file, ensure compatibility with the device, or try accessing the program from a different workstation.
Answer: - The issue might be related to the EDS file not being recognized or matched correctly during communication setup, possibly due to a corrupted module or software configuration problem.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.