Hi, I have installed Codesys V3.5 SP4 and SP7 pbf(Provided by Festo) and it works in a correct way.
Last week I installed the new version of Codesys V3.5 SP16 and it worked very well but when I was trying to use the oldest versions opening projects (created in this old versions) it caused problems with libraries. When it start, always load the library versions of the Codesys V3.5 SP16 even if I am using SP4 or SP7 and I can´t compile it.
I see that there is a location where the libraries are stored (C:\ProgramData\CODESYS\Managed Libraries)but I don´t know what I have to do to create a special folder for each versions or which could be the solution to install different versions.
I hope that somebody could help me, thank you
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I finally could do it. But now, I have another problem, some library show me the error "No source code available for this object because it is in the compiled library "visuusermgmt, 3.5.7". Do you want to browse for the original library...
Yeah you can't look at the source code of most libraries. The Oscat Libraries do allow you to look at the source code though. So that sounds totally normal. That is if you're in the library manager and double clicking on something like a DUT/interface etc in that library.
👍
1
Last edit: Morberis 2020-07-29
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
we have 4 different genuine Codesys versions installed in W10. But custom versions such as Festo or Schneider run into separate and dedicate virtual machines.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, at the end I chose the option of i-Campbell "For advanced users"
I also upload a video with the steps, maybe could help somebody else...
Thanks...
Though all above solutions are still valid and useful for OEM suppliers, the simplest and now very well supported solution is to install CODESYS SP17.X and be sure to select the "CODESYS installer" along with it.
After a successful install open the new CODESYS Installer via START > CODESYS > CODESYS Installer.
Now select the Button "Add Installation" and the rest is "peanuts"!
Last edit: hermsen 2021-09-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
h-hermsen,
I've been having troubles making this work. My codesys V17.2 and beyond are failing to open projects that v17.1 is opening without issue.
Also, v17.1 and v17.2 are having problems opening projects between different computers (laptop vs desktop) that have different plug-ins installed, despite the project not using the plug-ins at all. For example, if a plug-in for a turck device is installed on the desktop, the laptop is having trouble opening an IFM device project (no reference to the turck plug-in at all). The installer fails to resolve this issue since the plug-in is not part of the codesys repository.
is there a way to resolve this?
I should also mention that it seems the multiple version instruction is now out of date with version 17. changing the settings ini file to point to a different directory seems to have no effect. the installer still creates the programdata/codesys folder, and v17 points to it regardless the ini file definitions.
Last edit: TPTSys 2021-11-19
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Moving a project between computers is a different thing then using 2 or 3 or more versions of codesys on the same computer.
for moving projects between computers I suggest you make use of a projectarchive. This makes sure the project and necessary stuff like libs profiles and whatnot are transported along in a single file.So the extra things from oem xyz can be included.
for long term and backup file storage a projectarchive is the obvious choice too.
Running multiple CODESYS instances on a single Machine is since v17 easier then before. I dont know anything about CODESYS version provided by thirdthird party oems. I suggest you read up on the CODESYS installer via Help.Codesys.com to see what it can bring you and how it works.
good luck
👍
1
Last edit: hermsen 2021-11-19
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I have installed Codesys V3.5 SP4 and SP7 pbf(Provided by Festo) and it works in a correct way.
Last week I installed the new version of Codesys V3.5 SP16 and it worked very well but when I was trying to use the oldest versions opening projects (created in this old versions) it caused problems with libraries. When it start, always load the library versions of the Codesys V3.5 SP16 even if I am using SP4 or SP7 and I can´t compile it.
I see that there is a location where the libraries are stored (C:\ProgramData\CODESYS\Managed Libraries)but I don´t know what I have to do to create a special folder for each versions or which could be the solution to install different versions.
I hope that somebody could help me, thank you
https://faq.codesys.com/display/CDSFAQ/Installation+of+several+CODESYS+versions
Hi, I finally could do it. But now, I have another problem, some library show me the error "No source code available for this object because it is in the compiled library "visuusermgmt, 3.5.7". Do you want to browse for the original library...
Yeah you can't look at the source code of most libraries. The Oscat Libraries do allow you to look at the source code though. So that sounds totally normal. That is if you're in the library manager and double clicking on something like a DUT/interface etc in that library.
Last edit: Morberis 2020-07-29
Hello,
we have 4 different genuine Codesys versions installed in W10. But custom versions such as Festo or Schneider run into separate and dedicate virtual machines.
Well, at the end I chose the option of i-Campbell "For advanced users"
I also upload a video with the steps, maybe could help somebody else...
Thanks...
https://youtu.be/WiAGlzJFYOw
Though all above solutions are still valid and useful for OEM suppliers, the simplest and now very well supported solution is to install CODESYS SP17.X and be sure to select the "CODESYS installer" along with it.
After a successful install open the new CODESYS Installer via START > CODESYS > CODESYS Installer.
Now select the Button "Add Installation" and the rest is "peanuts"!
Last edit: hermsen 2021-09-25
h-hermsen,
I've been having troubles making this work. My codesys V17.2 and beyond are failing to open projects that v17.1 is opening without issue.
Also, v17.1 and v17.2 are having problems opening projects between different computers (laptop vs desktop) that have different plug-ins installed, despite the project not using the plug-ins at all. For example, if a plug-in for a turck device is installed on the desktop, the laptop is having trouble opening an IFM device project (no reference to the turck plug-in at all). The installer fails to resolve this issue since the plug-in is not part of the codesys repository.
is there a way to resolve this?
I should also mention that it seems the multiple version instruction is now out of date with version 17. changing the settings ini file to point to a different directory seems to have no effect. the installer still creates the programdata/codesys folder, and v17 points to it regardless the ini file definitions.
Last edit: TPTSys 2021-11-19
Moving a project between computers is a different thing then using 2 or 3 or more versions of codesys on the same computer.
for moving projects between computers I suggest you make use of a projectarchive. This makes sure the project and necessary stuff like libs profiles and whatnot are transported along in a single file.So the extra things from oem xyz can be included.
for long term and backup file storage a projectarchive is the obvious choice too.
Running multiple CODESYS instances on a single Machine is since v17 easier then before. I dont know anything about CODESYS version provided by thirdthird party oems. I suggest you read up on the CODESYS installer via Help.Codesys.com to see what it can bring you and how it works.
good luck
Last edit: hermsen 2021-11-19