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
I have an applicaton where I want to create function blocks based on configuration files read at start up. No function blocks will be added or deleted once the application is initialzed. If the user reconfigures the system, the new configuration would not take effect until a restart of PLC takes place. Is there any disadvantage to using __NEW to create these function blocks as opposed to the fb factory library to create these function blocks? The Codesys documentation indicates that the main disadvantages of __NEW only occur if the memory allocation size cannot be determined or __NEW and __DELETE are used repeatedly. Has anyone done something similar?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have an applicaton where I want to create function blocks based on configuration files read at start up. No function blocks will be added or deleted once the application is initialzed. If the user reconfigures the system, the new configuration would not take effect until a restart of PLC takes place. Is there any disadvantage to using __NEW to create these function blocks as opposed to the fb factory library to create these function blocks? The Codesys documentation indicates that the main disadvantages of __NEW only occur if the memory allocation size cannot be determined or __NEW and __DELETE are used repeatedly. Has anyone done something similar?