Let us be "firm"ly a"ware" of this fact...
Ih8Siemens said:
It’s been a long day Firmware Rev 21.03
Ken Roach said:
...The solution today is to use the appropriate version of RSLogix 5000 / Studio 5000 that supports both resilient and non-resilient firmware controllers.
For a 1756-L71 controller with version 21.03 firmware, that would be Studio 5000 version 21.00.04.
I am reasonably confident in this compatibility, as I have a couple of systems in the field that I intentionally put 21.03 firmware on 1756-L71 controllers...
The opening title has thrown us a "bum steer" here...
I'm reading a couple of misunderstandings to boot...
I have seen mention of the firmware in relation to the product resiliency releases before...
For those reason I feel is important to make this a bit clearer...
There is no special firmware involved in the product resiliency releases. There is no firmware revision "21.03". There is only revision 21.011. In fact, revision 21.011 is the only firmware available for controllers that support firmware revision 21, whether a resiliency project has been downloaded, or not. The product resiliency features are only related to the software version 21.03 (or 20.03) and are applied to the project file that is compiled and downloaded into the controller. The controller firmware is not involved in the application of, or protection of these features. They are applied offline in the software and then downloaded. Only the same software version offline can then interact with the project in the controller, whether to open it offline, go online, or upload, etc., because only this software version recognizes these features. Having the correct product resiliency version of the software should enable you to interact with a controller project that was previously downloaded using the same version...
Ih8Siemens said:
...I am pretty sure they put the last copy on utilizing .03 thus making it impossible to pull from the controller without the original file...
The product resiliency features do not prevent a user from uploading without the offline project file. That is not its intended purpose. It just prevents a user with a non-resiliency version of software from interacting with it.
Ih8Siemens said:
...Has anyone found a work around or a way to get files off of controllers with that 21.03?
You use resiliency software version 21.03, or the latest fix version 21.00.04.
But, are you guessing or do you have any evidence, besides struggling to upload the project, that version 21.03 software was last used with this controller? Or version 21 anything?...
Ih8Siemens said:
With the help of 6 VM’s and every version of 20/21 you could imagine.
I can imagine quite a lot. But how do you know what firmware the controller is currently using? We know it is not "21.03", but that is all. To be sure of the controller firmware revision, you can access its properties via an RSLinx Classic browse. If you know it to already be using firmware 21.011 (same as 21.11) then you don't need anything version 20 related, for instance (unless used during "other" extraction methods).
If you know it to be at revision 21.011...
What specific software versions have you installed and attempted an upload with? What were the results/errors?
If it was downloaded to using version 21.03 software and you attempt to upload using an ordinary software version, such as version 21.00, then you should get specific error messages. What messages have you been getting when you tried say version 21.00 software?
If you are using version 21.03 software, and you do not have the offline project file, then you can upload a resiliency downloaded project by creating a new file during upload. If it wasn't, and say it was downloaded using version 21.00, then version 21.03 would prompt you to convert the 21.00 project to 21.03. Of course you would not want to do that if it was not resiliency set to begin with.
...and so on...
I'm listing hypothetical scenarios here but really you need to provide this information to us with your actual results, or as best you remember if now offsite. We need specifics as to what errors you are seeing for various things you've tried. Us Bloodhounds thrive on specifics and error messages, you know!
If none of that gets you anywhere then there is still the other possibilities...
Ken Roach said:
...If what's really going on is a Security feature like "OEM Lock" or other routine source code protection, that's a different matter. A customer who ruined their relationship with their integrator/programmer might also have ended up in a conflict over ownership and payment for the content of the controller.
Your issue might have nothing to do with product resiliency features and version 21.03 software, and more to do with the above.
The main aim here is to prevent you misunderstanding a resiliency feature that would then lead on to you believing that this feature must be what is providing the apparent security feature that is blocking you. If it is merely product resiliency set then this should not be preventing you from uploading the project file using the correct software version.
Regards,
George