Codesys License Manager

[Maximilian Lozano]

HelloI am currently facing an error while trying to download and update libraries through Package Manager. I am using CODESYS V3.5.18.20. When I select and start the installation of the libraries it throws me an error attached to this issue bellow. However when I abort the installation and start again it does not throw the error again. But the whole instalation of CODESYS is corrupted. How do I fix this problem please ?

I had also a quite similar error today when trying to update packe with the codesys installer 1.4.0.

Is there a solution? Tried to repair codesys V3.5 SP18 Patch 2 several times even installed it from beginning on another computer, had the same issue. Please provide a solution!

Repairing did not work either. I allways need to uninstall and try again. Only thing that worked for me was installing the packages solo by their separate instalators. Codesys installer cant install it properly and allways throws these errors and then the CODESYS installation is corrupted again...

I'm an absolute beginner with CoDeSys Visualization, and am trying to teach myself to build WebVisu applications. I am running CoDeSys v3.5 SP12, and the target system is a Raspberry Pi running firmware 3.5.12.0. I'll be doing real projects with IndraWorks and Indramat XM22 controllers, but the Pi gives me a cheap way to practice and learn.

When I tried to Build the project, the error message was "The configured start visualization is not instantiated. Does it contain an interface or is the instantiation missing within the visualization manager ?"

Once I delete any variables in the VAR_IN_OUT section for the Visualization, and tie all my objects to ordinary Global or Program scope variable in the PLC application, the Visualization appears in the list of Visualizations under the Visualization Manager, and the project Builds and loads and runs correctly. I suppose that's what the error message meant when it said "is the instantiation missing within the visualization manager".

I have the same problem! Worse, when I generate an error of this type, my visualisation never reappeared on the visualisation manager. I need to create a new visualisation and paste all my items into.

So, a solution is to use VAR_GLOBAL. This variables are available into and outside your visualisation.

My understanding is that when you add variables inside the VAR_IN_OUT is that it then becomes a dialog. If you want variables to use inside the visualization without it becoming a dialog you need to add a VAR section so it would look like:

That information helps me understand the error message; when it says "does it contain an interface" it's referring to the VAR_IN_OUT section as an "interface". The fact that this is used for dialogs instead of ordinary windows helps me understand it.

Problem 1.

If i try to plug unplug a contact for a Device sometimes the Manager Hangs..

CanOpen manager is green, Node is red, When i monitor the bus the node sometimes is in operational sometimes in pre operational and sending heartbeats. If i try to send NMT Operational no message goes to the bus. Only way to recover is to cut the power to the PLC and reboot.

After much testing I found a way to make this problem go away.. I configured all my nodes and saved the configuration in the node. I chose the CanOpen manager not to initialize the nodes and instead wrote some code to check if any of my nodes is either stopped or preop and if they were I started them.

[b]Problem 2.[/b]

If we remove the CanOpen GND the same behaivior as above still comes and i need to restart the PLC.. Kernel state is No error or guarding error. The nodes is sending heartbeats but the manager cannot send anything to the bus..

guess this is still a plc problem, which plc is it. (Manufacturer?)

Yup, IFM. (Se bottom of first post for exact model). But we are now testing with another brand.

The only errors I have when watching with CANOPEN_DEBUG is due to erroneous EDS files.

Objects that doesnt exist and such. But that I already knew and have jumps to next line in the SDO configuration.

If you are using 3.5.16.X versions of IDE then codesys package manager is part of that installation itself. Just try to install the development environment properly to suppress your reported error. "Codesys Installer" is introduced in the place of "codesys package manager" from 3.5.17.0 versions. You need to use this for any package related work. One more to add here is "Package designer" is also dropped from 3.5.17.0.

Shan,

I am having issues getting packages installed through Codesys installer, as I get an error that essentially says the package is not 64 bit compatible (I get this for a number of official packages). What is the recourse here? Is this an issue with Codesys installer or is something else going on with my install?

My anwser is based on some info I heard but I cannot recall when been exactly I heard it. As far as I know 64Bit IDE compatibility for the CODESYS has been introduced relatively recently (2018/2019 and in phases) in order to accomodate optimal use of hardware resources in x64 based windows platforms, among some other compiler and memory consumption optimisations. To put it simply, some PLC programs in CODESYS installations grew so big that they reached the physical limits of the 32 Bits Windows OS. So, to overcome this issue, a 64bits version of the IDE had been planned. Every package which is not 64 bit compatible can be used in the backward compatible 32bit version of CODESYS IDE available through CODESYS installer. So, some packages will not install in 64bits IDE by-design due to DLL incompatibility. Some of these packages, like the package manager, are to be replaced with an entirely new overhauled design which enables a more optimised usage for CODESYS installer and the newly introduced software modularity. Because of this the old 32bit package will not get a simple upgrade for 64bit usage. I am not entirely sure this is 100% correct but the explanation seems plausible to me. Maybe someone from CODESYS could step in and anwser/explain if this is correct or not?

I will probably use recipes in one form or another on a new system in the near future. I understand arrays and structures, would be able to just program something with that in ST. However it seems the recipe manager in Codesys 3 provides a readily available building block that takes some of the hassle away from building my own solution from scratch. I don't know if it is me, but I find the documentation for the recipe manager in v3 is very poor. It does not clarify to me what it does and how it can or should be used. I have downloaded the example from the store. That did little or nothing to improve my understanding. I find it messy and unclear to a new user. To me it just seems like a lot of boxes and buttons on one screen with little clarification of how they relate to one another and how it should be used. If I where a customer and my newly purchased machine came with this screen for handling recipes I would send it back for a makeover.

Is there better documentation or better examples available to clarify what exactly the recipe manager does, and how it would add to or replace a self-made recipe system based on structures and arrays?

Imagine that you are testing your program and that you still doesn't have the HMI or the mechanics and electronics mounted. Then you could simulate a bunch of variables to test your code. With those recipes you can simply write all the values at once and you can have the values stored from the beginning to ease the task to prepare the simulations...

I understand that concept, and I would probably do that with a either a few arrays (one per variable) or an array of struct (all variables in one struct type). With an index in the array that I could move up or down at will to select an element.

What I don't see clearly is which part of that is actually taken over by the recipe manager component, or whether the recipe manager adds an additional layer of functionality on top of a base storage structure with arrays. More so since the example project also contains arrays.

I think the main idea of this system is to allow the user to modify data before download it to the Plc or save it to a file. For example you can use the recipe management in order to set parameters of a treatment. A recipe can contains informations about times, temperatures etc. With a recipe manager you can open a file that contains these parameters and modify them, only check their values, use them as basis for a new recipe etc. without download those informations into the Plc. In this situation you can perform these actions while the machine is running a process without modifying anything.

Thank you Massimo (and Joan, too). I had a suspicion this was the case. For now I will not waste my time on the recipe manager and build my system with just structures and arrays, and store the recipes in retain memory.

Hello

I tried to do that with retain persistent global vars but my Raspberry can't keep in memory that on power down. So I think to use recipe manager by ST code. Hope to find a good documentation.

I am new to codesys, and later to the conversation. I am currently recreating a large dynamic program using a ABB PLC that uses Automation Builder (which is just ABB's usage of Codesys). In the ABB PLC documentation I saw that the retention is being held by a super cap that would last about 16 days. This would simply not work for my application. I am utilizing the recipe manager and the external micro sd card to retain all of the settings and values daily for the system. So far it is working well and I am happy with it. I have 4000 mixed variables in there and it works great, I just wish I had more documentation to know how they are doing what they are doing because I put a timer that can check the differential time between calls of a part of the program, and even with the external file being created (which takes 600ms in its task) it does not interrupter the timing of the one that i am checking, I have a variable that if the dw_DifferentialTime > dw_LargestDiffTime THEN dw_LargestDiffTime := dw_DifferentialTime. They must be doing some nifty async stuff in order to pull this off, but it is amazing. Any deeper documentation would be great.

3a8082e126