Library- Versioning one POU

2021-03-30T06:37:20.566000Z

It is impossible to reference lib version w.x.y.z AND version w.x.y.z + 1 in the same project at once. A library can always only be referenced ONCE. I've never seen this this feature in ANY IDE I worked with and I highly doubt this is useful.

All is explained straightforward here:
https://help.codesys.com/webapp/_cds_struct_installing_libraries;product=codesys;version=3.5.16.0

Library- Versioning one POU

2021-03-30T04:44:34.626000Z

Thanks h-hermsen
One last question, using the same scenario and example as before, I have FB_Motor V1 and later I modified it to FB_V2 and saved that to the repo as well as saved the library with the new changes. So in the standard project I have access to both V1 and V2 which is great but in the library project it opens with the last saved version which is V2. Is there a way to open V1?
I can copy and paste from standard project to library but curious, since the both versions exist in the repo there must be a way to open either one.

Thanks

Library- Versioning one POU

2021-03-29T06:19:38.616000Z

No, the way you describe your preferred workflow is not possible in CODESYS. I do recognize your described workflow from from a different IDE but it is not possible here.

You cannot edit the preferred FB (which resides in library w.x.y.z) directly from the project as the library is loaded as a reference, just like in VS.Net or similair.

Getting a hang of the preferred way of working in CODESYS isn't that hard though. Just open CODESYS twice. Load your library in IDE1 and load your project in IDE2. Editing and saving the library to your library Repo (commit as you call this) is entirely done via IDE1.
Modifying your project itself and testing of the library component from IDE1 is done in IDE2. This is the normal vanilla way of managing it in CODESYS.

Regards

Library- Versioning one POU

2021-03-28T23:37:17.909000Z

How do you guys work with libraries in general.

I would like to use it like this:
Create a standard project for a specific controller and develop, let's say FB_Motor, and work with that and other POUs. Then at some point I will be happy with it and want to archive it so I will create a project and add it. Then sometime later I will want to modify it but I need to do that in a project where its functionality can be tested and compiled, what to do then?
I can not edit it on its own in the library project because I need to test its functionality in a working project.

I am looking for something like how SVN does it, or Siemens TIA, where the library is linked to the project and I can modify the FB right where I have it being used and test and compile it then when I'm happy with it I can "commit" or save it to a new version FB_Motor V2
Is that possible?

Thanks again.

Library- Versioning one POU

2021-03-28T22:41:39.598000Z

Thanks everyone.
I figure out some of it and working on the rest.
So what I wanted to do is this:
I have FB_Motor and its version in the library is 0.0.0.1 and that's how it shows up in the repository. Then I go back later to make some changes to it and want to have a new version 0.0.0.2 while keeping the other version available.
What I figured out thus far is that I have to do that manually but going to "Project Information" and changing the version number there then save and install the repo to have it available in the project.
Is that the way it is done?
Could it be done automatically, somehow?
After making changes and saving FB_Motor V2, how can I go back to FB_Motor V1 if I want to?

Thanks

Library- Versioning one POU

2021-03-28T08:07:43.717000Z

If you have for example FB_Motor (v1) and FB_Motor (V2), and you want to reference both of them in a project, you will need to have different names for them.
For Codesys libraries, the developers make only compatible changes to a POU. If the library developer wants to make a new POU which is not compatible, they change the name, eg. AddLog and AddLog2. In your case you could name them FB_Motor and FB_Motor2.

If you however mean that you wish to know how to update your .project, so it uses now library V2.
1. Install library V2 to library repository as you have already done.
2. In your project use Menu > Project > Project Environment... to identify and update any libraries.
OR you can select the versions from Library Manager > Placeholders
3. If you have changed the inputs and outputs of the POU, in graphical languages you can right click it and "update pins". In ST you must add or remove the entries manually.

Library- Versioning one POU

2021-03-28T06:22:37.625000Z

Maybe i do not understand. If you have opened 2 CODESYS Developmentsytems, it ist exactly what you need, one for edit the Lib the other to Test the Pou's from your library

Library- Versioning one POU

2021-03-27T03:42:52.369000Z

Thanks. So here's what I did:
-Created a library project and added a POU with some code and
Saved the project and updated the repo.
-Opened a standard project and added the library and opened and FB then I inserted an empty EN/ENO and selected my POU from the library
-Now here's what I want to do,
1- Make changes to the POU in the library and version to 2.0. In the my library project I will have to versions of the same POU, version 1 and version 2.
2-Go to my standard/work project when I am using and instance of that version 1 POU and update it to latest version 2

Thanks

Library- Versioning one POU

2021-03-26T05:18:26.330000Z

you just open two instances of CODESYS - one with the library the other open your testproject.
Then you add changes in the library and after doing this press the yellow icon ( which installs the changes to the libraryreporsitory)
You see in the message view of the project instance that this has successfully done - and now compile your project and do your tests with your code changes.

BR
Edwin

Library- Versioning one POU

2021-03-26T01:32:12.450000Z

I take it either no one knows or it is not possible, which is it?
Thanks

Recent posts to Library- Versioning one POU

Library- Versioning one POU

Library- Versioning one POU

Library- Versioning one POU

Library- Versioning one POU

Library- Versioning one POU

Library- Versioning one POU

Library- Versioning one POU

Library- Versioning one POU

Library- Versioning one POU

Library- Versioning one POU