Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
Example:
When I download revision 1 of my program to a Wago 750-8214 PLC and go online after the download, everything is fine. Codesys recognize my current project I have opened matches the one on the PLC and I can online monitor.
When I copy that entire project folder over to a different computer, and try to go online with the program I just downloaded, Codesys gives me an error of the program on the PLC not matching the Program currently opened, and forcing me to redownload to the PLC.
I have also tried using git to see if that would work, but even with the git pull I get the same issue.
Am I doing something wrong, because this will be a major headache if someone else from my company needs to assist a client with debugging of the PLC code.
Regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please work projectarchives - or use the CODESYS Automation Server to store the project.
Then this should work without problems on two different computer.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have tried using archive but its the same results. when opening the archive and trying to login into the plc, it gives me the same issues. The compiler thinks the offline program is different from the online program.
I can do a video recording as an example, and I will post it.
Regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, sorry to post this on a such a old forum post, but I tested the project archives finally...
So current setup (Laptop 1 + Laptop 2):
Codesys V3.5 SP17 Patch 3
I did a project archive with the following steps (Laptop 1):
File -> Project Archive -> Save Archive
I then proceeded to select all tickboxes that was shown to me. and pressed saved.
On Laptop 1:
I extract the archive and connect to the PLC without having to do a redownload. Which is good
On Laptop 2:
I extract the archive and as soon as I try to connect to the same PLC I can not connect due to source code changes. I get a list of issues of why I cant connect.
Please see attachments of the screenshots I took, regarding the issues to why I cant connect from laptop 2
I have been struggling with this issue for a very long time. I figured that if you have two identical Codesys installation, you should be able to go online from any of the two PCs using the .project file and the .compileinfo file. But when I say identical I mean it. Same Codesys version, same add-ons versions, same runtimes versions, same librairies versions, etc. And I cannot garantee that it always works.
For exemple, I tested it just before writing this post. I downloaded to a PLC from PC1. I transfered the .project and .compileinfo files to PC2. I tried to go online and it did not work. I figured that I had 2 add-ons to update and also some librairies to download. Once this was all done, it still would not go online. Also I had the storage format message popup which I never understood. I still tried to go online without change. It crashed my PLC, and from the message, it seemed to have crashed somewhere in the persistence manager, which is very concerning since it is some module built by Codesys themselves and there is no way to see the source code. Anyway, I did a reset origin, downloaded to the PLC and everything worked fine from PC2.
I then transfered the .project and .compileinfo files from PC2 to PC1 and was able to go online from PC1!
I then decided to do a reset origin and download from PC1 to the PLC, transfered the files to PC2 and tried to go online, and it worked! Without the storage format message.
So now both works but it was not easy.
This has always been a headache. Even when I used to work with Beckhoff/TwinCAT which is also based on Codesys. And I think it was even worst. Sometimes I just could not find a way to make it work.
This is really bad for future support of deployed projects. You may end up having to install dozens of versions of Codesys on your PC with different versions of runtimes, add-ons, librairies, etc. And still you would cross your finger everytime you need to go online with a PLC.
Codesys really need to improve that. And at least provide clear explanations on what is needed in order to always be sure we will be able to go online on a controller without having to download or even crash the PLC like I did today.
Don't get me wrong. I love Codesys and would never go back to my AB days. But I guess this is the price to pay when working with powerfull and flexible software such as Codesys (even though the IDE is free :)). There is always room for improvement.
Good luck
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for giving me tips on how you have tried to solve this issue.
I really cant understand how a feature like this is so "buggy". This makes client debugging literally impossible unless you always use the same laptop with the same installation, library, ect for all projects. In my opinion this should be one of the most important "features" that needs to work flawlessly since in most cases where PLC's are used there are frequent monitoring, code updates and debugging taking place, and without the ability to go online to a PLC even having the exact same project file, is literally unacceptable.
There are so many issues with codesys, and yes it might be free software, but I have used different PLC software that was also free (Delta) and I could open projects on different workstations without having to worry about it. This is the first software package I have used where a "simple" feature like this does not work.
Sad to hear that Beckhoff/Twincat also has problems like this....
E-Cockpit which also uses codesys in the background, does exactly the same as Codesys. So this "feature" has been around for a while and has never been addressed.
I doubt it takes forumn post like this to alert the developers that this is a issue, surely they know about this and has a solution planned for the future....
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I am using Codesys 3.5 SP17 (64bit).
Example:
When I download revision 1 of my program to a Wago 750-8214 PLC and go online after the download, everything is fine. Codesys recognize my current project I have opened matches the one on the PLC and I can online monitor.
When I copy that entire project folder over to a different computer, and try to go online with the program I just downloaded, Codesys gives me an error of the program on the PLC not matching the Program currently opened, and forcing me to redownload to the PLC.
I have also tried using git to see if that would work, but even with the git pull I get the same issue.
Am I doing something wrong, because this will be a major headache if someone else from my company needs to assist a client with debugging of the PLC code.
Regards
Please work projectarchives - or use the CODESYS Automation Server to store the project.
Then this should work without problems on two different computer.
We are primarily using Git in our company. Is this not possible with git?
I have tried using archive but its the same results. when opening the archive and trying to login into the plc, it gives me the same issues. The compiler thinks the offline program is different from the online program.
I can do a video recording as an example, and I will post it.
Regards
Hi, sorry to post this on a such a old forum post, but I tested the project archives finally...
So current setup (Laptop 1 + Laptop 2):
Codesys V3.5 SP17 Patch 3
I did a project archive with the following steps (Laptop 1):
File -> Project Archive -> Save Archive
I then proceeded to select all tickboxes that was shown to me. and pressed saved.
On Laptop 1:
I extract the archive and connect to the PLC without having to do a redownload. Which is good
On Laptop 2:
I extract the archive and as soon as I try to connect to the same PLC I can not connect due to source code changes. I get a list of issues of why I cant connect.
Please see attachments of the screenshots I took, regarding the issues to why I cant connect from laptop 2
I have been struggling with this issue for a very long time. I figured that if you have two identical Codesys installation, you should be able to go online from any of the two PCs using the .project file and the .compileinfo file. But when I say identical I mean it. Same Codesys version, same add-ons versions, same runtimes versions, same librairies versions, etc. And I cannot garantee that it always works.
For exemple, I tested it just before writing this post. I downloaded to a PLC from PC1. I transfered the .project and .compileinfo files to PC2. I tried to go online and it did not work. I figured that I had 2 add-ons to update and also some librairies to download. Once this was all done, it still would not go online. Also I had the storage format message popup which I never understood. I still tried to go online without change. It crashed my PLC, and from the message, it seemed to have crashed somewhere in the persistence manager, which is very concerning since it is some module built by Codesys themselves and there is no way to see the source code. Anyway, I did a reset origin, downloaded to the PLC and everything worked fine from PC2.
I then transfered the .project and .compileinfo files from PC2 to PC1 and was able to go online from PC1!
I then decided to do a reset origin and download from PC1 to the PLC, transfered the files to PC2 and tried to go online, and it worked! Without the storage format message.
So now both works but it was not easy.
This has always been a headache. Even when I used to work with Beckhoff/TwinCAT which is also based on Codesys. And I think it was even worst. Sometimes I just could not find a way to make it work.
This is really bad for future support of deployed projects. You may end up having to install dozens of versions of Codesys on your PC with different versions of runtimes, add-ons, librairies, etc. And still you would cross your finger everytime you need to go online with a PLC.
Codesys really need to improve that. And at least provide clear explanations on what is needed in order to always be sure we will be able to go online on a controller without having to download or even crash the PLC like I did today.
Don't get me wrong. I love Codesys and would never go back to my AB days. But I guess this is the price to pay when working with powerfull and flexible software such as Codesys (even though the IDE is free :)). There is always room for improvement.
Good luck
Hi yannickasselin
Thanks for giving me tips on how you have tried to solve this issue.
I really cant understand how a feature like this is so "buggy". This makes client debugging literally impossible unless you always use the same laptop with the same installation, library, ect for all projects. In my opinion this should be one of the most important "features" that needs to work flawlessly since in most cases where PLC's are used there are frequent monitoring, code updates and debugging taking place, and without the ability to go online to a PLC even having the exact same project file, is literally unacceptable.
There are so many issues with codesys, and yes it might be free software, but I have used different PLC software that was also free (Delta) and I could open projects on different workstations without having to worry about it. This is the first software package I have used where a "simple" feature like this does not work.
Sad to hear that Beckhoff/Twincat also has problems like this....
E-Cockpit which also uses codesys in the background, does exactly the same as Codesys. So this "feature" has been around for a while and has never been addressed.
I doubt it takes forumn post like this to alert the developers that this is a issue, surely they know about this and has a solution planned for the future....