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
Hi all,
Recently I stuck on Codesys 3.5.16 error "Index was outside the bounds of the array", when try to add a new POU.
And I found the reason of this error and how to avoid it. Hope, this will be useful for all, until next service pack released.
For me this happens, when Devices menu field on left side of the screen was set to Auto Hide mode. During operations to add a new POU I select menu item Application, then Add Object. Usually at this moment mouse pointer goes outside Devices menu field borders and Devices menu hides. Then, when menu item POU is selected, the CODESYS error message window "Index was outside the bounds of the array" appeared. But, if Devices menu field 'pinned' (no Auto Hide selection) all goes right way.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I posted about it around an year ago and still see the same issue. However, it only happens if the device tree is set to Auto Hide. If it's pinned, everything works.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
Recently I stuck on Codesys 3.5.16 error "Index was outside the bounds of the array", when try to add a new POU.
And I found the reason of this error and how to avoid it. Hope, this will be useful for all, until next service pack released.
For me this happens, when Devices menu field on left side of the screen was set to Auto Hide mode. During operations to add a new POU I select menu item Application, then Add Object. Usually at this moment mouse pointer goes outside Devices menu field borders and Devices menu hides. Then, when menu item POU is selected, the CODESYS error message window "Index was outside the bounds of the array" appeared. But, if Devices menu field 'pinned' (no Auto Hide selection) all goes right way.
It did work. Same issue in 3.5.17 also.
Wow I ran into the same thing. Can't believe this is even an issue. Thanks!!
3.5.18 still a thing. And thanks for posting this, I could not figure out what I was missing causing this error.
I posted about it around an year ago and still see the same issue. However, it only happens if the device tree is set to Auto Hide. If it's pinned, everything works.
Still a problem in 3.5.19.20 which is absolutely ridiculous.