Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calaos 3.0 version, output is flickering #5

Open
oeble opened this issue May 13, 2017 · 0 comments
Open

Calaos 3.0 version, output is flickering #5

oeble opened this issue May 13, 2017 · 0 comments

Comments

@oeble
Copy link

oeble commented May 13, 2017

Hello,

On my first try with Calaos 3.0, I have observed while programming with calaos installer the configuration of my house, that the outputs are flickering and relay are switching very quickly when I ask for a lamp to be turned on for example. This issue is not present with the 2.3 version. Note that I have a 881 wago head.
The issue is present whatever I perform the set through Calaos installer or after loading the configuration to the device. I have no Calaos server for now.

I have tried to look a little bit more into the issue, and I have found in the main program the code (a for loop actually) that takes the variable "OutArrState" and write it I guess to the actual output. I have used the debugging tool and observed that after the first loop cycle, the output is set correctly but when the loop is over then the output is off. In step by step I've been as far as i=160 with the output still on but as soon as the loop is over the output is off again.
The same test with the 2.3 version shows that the output stays on after the loop. The only differences I have noticed between the two versions is that the loop goes to 255 in version 3 while it stop at 15 in the version 2.3.
Because each bit of the array represent an output, I am wondering why this index goes so far now (is it even possible to have 2048 outputs ?).

FYI I am discovering CodeSys and it is so difficult to understand how it works, so unfriendly. I hope that this issue has enough information for you to propose a correction. I hope that I could help more in the future (maybe propose some pull requests once I'm more familiar with the project).

PS: I'm Rusty on the forum.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant