Hi & Welcome to the Forum!
Did you read my post #7 above? If so, have you tried to follow my advice? Can you access the technote I linked?
I'm not sure where on the Internet you are referring to, but I can guarantee you that the files attached in the technote above are both official and a "one-stop-shop" for the EDS files related to the 1769 CompactLogix family of controllers and modules, up to revision 20.
With regard to revisions - the package of EDS files, that I'm advising you to download and register, includes all CompactLogix controller related EDS files, from revision 13-20.
When dealing with equipment predating the introduction of the newer EDS Subsystem (circa revision 20), the highest version I would advise users to go to is RSLinx Classic v2.59. The next version released after this was version 3.51, and this version introduced the new EDS Subsystem. That is just some general advice. You should not need to upgrade to v2.59 here just to resolve your single controller issue. But v2.59 should also work fine with all of your 1769-L32E controllers.
You have not clarified what you mean by the icon for the controller being "not the same"? Do you mean, for instance, it's displaying as a Yellow "?" with no Red "X"? Can you connect to this controller?
My best guess here is that you can connect to the controller but you are just missing the correct EDS file. It's possible that this controller might be at a different firmware revision to the other controllers whose icon displays correctly. Or, it is a different hardware Series to the others. There are separate EDS files required to be registered on your workstation computer for the different hardware Series and firmware revisions.
1769-L32E Series A support firmware revision 13-20.
1769-L32E Series B support firmware revision 16-20.
As an example, your controller could be a Series A firmware revision 15. The others are Series B firmware revision 17. Your workstation does not have the Series A revision 15 EDS files registered. But that example could be possible the other way around.
In other words, there is every chance that you simply need an older, or newer, revision EDS file(s), just for this controller. But, this helps to hammers home the advice I always give here. Don't waste your time trying to figure out how many files, and at which revision, you might need. Just download the EDS package in the technote above and register them all, and get on with your day.
Don't forget to clarify what you see for the icon though. This can help determine if there is more to this than a missing EDS file.
Regards,
George
smichaud said:...We have an old RSLinx Classic (Revision 2.54.00.11 CPR 9 SR 1). We would like to make sure to have the good version of the EDS files for a CompactLogix 1769-L32E...
Did you read my post #7 above? If so, have you tried to follow my advice? Can you access the technote I linked?
smichaud said:...Do you think that the version we find in internet could be ok for our old RSLinx or we really should have an older revision that we are not able to find anymore in internet?...
I'm not sure where on the Internet you are referring to, but I can guarantee you that the files attached in the technote above are both official and a "one-stop-shop" for the EDS files related to the 1769 CompactLogix family of controllers and modules, up to revision 20.
With regard to revisions - the package of EDS files, that I'm advising you to download and register, includes all CompactLogix controller related EDS files, from revision 13-20.
smichaud said:...We know we could change our RSLinx but it works well with all other 1769-L32E we have, except one and we noticed that its icones in RSLinx is not the same than the other...
When dealing with equipment predating the introduction of the newer EDS Subsystem (circa revision 20), the highest version I would advise users to go to is RSLinx Classic v2.59. The next version released after this was version 3.51, and this version introduced the new EDS Subsystem. That is just some general advice. You should not need to upgrade to v2.59 here just to resolve your single controller issue. But v2.59 should also work fine with all of your 1769-L32E controllers.
You have not clarified what you mean by the icon for the controller being "not the same"? Do you mean, for instance, it's displaying as a Yellow "?" with no Red "X"? Can you connect to this controller?
My best guess here is that you can connect to the controller but you are just missing the correct EDS file. It's possible that this controller might be at a different firmware revision to the other controllers whose icon displays correctly. Or, it is a different hardware Series to the others. There are separate EDS files required to be registered on your workstation computer for the different hardware Series and firmware revisions.
1769-L32E Series A support firmware revision 13-20.
1769-L32E Series B support firmware revision 16-20.
As an example, your controller could be a Series A firmware revision 15. The others are Series B firmware revision 17. Your workstation does not have the Series A revision 15 EDS files registered. But that example could be possible the other way around.
In other words, there is every chance that you simply need an older, or newer, revision EDS file(s), just for this controller. But, this helps to hammers home the advice I always give here. Don't waste your time trying to figure out how many files, and at which revision, you might need. Just download the EDS package in the technote above and register them all, and get on with your day.
Don't forget to clarify what you see for the icon though. This can help determine if there is more to this than a missing EDS file.
Regards,
George
Last edited: