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 need to be able from the runtime enable the GPio as we have applications where the GPios isnt controlled from codesys and we have the same codebase..
I have used the DED.Reconfigure before but when trying to enable/disable I get the error not supported.. Am I doing something wrong or is the reconfiguration of GPIO really not supported?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Maybe a workaround:
drive your GPIOs from one task only (double check this in the 'task deployment' view). Do this in an Event task, which you trigger from a cyclic task, but only when you want to use those GPIOs.
This way you have control over, what's written to the GPIOs during runtime. The initialization is still done by the CODESYS driver, but then you are able to reconfigure them in your external application.
Cheers,
Ingo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello.
I need to be able from the runtime enable the GPio as we have applications where the GPios isnt controlled from codesys and we have the same codebase..
I have used the DED.Reconfigure before but when trying to enable/disable I get the error not supported.. Am I doing something wrong or is the reconfiguration of GPIO really not supported?
AFAIK it is not.
Maybe a workaround:
drive your GPIOs from one task only (double check this in the 'task deployment' view). Do this in an Event task, which you trigger from a cyclic task, but only when you want to use those GPIOs.
This way you have control over, what's written to the GPIOs during runtime. The initialization is still done by the CODESYS driver, but then you are able to reconfigure them in your external application.
Cheers,
Ingo