Exit function in programme makes KNX to disconnect

Avatar
Paul G
  • updated
  • Under review

Hi,

When the exit function is used in a programme, bOS makes de KNX to restart completely, the only thing that should happen is for the programme logic to finish, however KNX is restarted. It took me some time to find out this, to the point that I had to put traces so that when the building and KNX were connected a trace would be logged.

I tis now confirmed, every single programme that includes the Exit sentence makes the building to restart, a significant bug to get fixed ASAP

Replies 8
Avatar
0
Paul G

Yes, it does, always. The moment I remove the Exit function from the above programme, the server no longer restarts. Effectively the above programme shows the Exit being executed only on weekend and bank holidays, as it happens every time the logic hits the 'festive or vacation' paragraph the server restarts, it happens the same in other places where I used to have the Exit function, in the end I have had to remove it because it simply does nto work, hence forcing the server to waste powr and CPU cycles

Avatar
0
ComfortClick Support

Hello,

looking trough the task, it shouldn't cause the server to restart.. Does the server restart each time Sun changes value?

Best regards.

Avatar
0
Paul G

See below examples that make the server restart

Avatar
0
Paul G

Hi, I put back the exit in the programmes I removed it from and get the details once it abends again

Avatar
0
ComfortClick Support
  • Under review

Hello Paul,

can you send us a screenshot of the program you use that causes the KNX to restart? We haven't noticed this issue so far and noone else reported it and exit function is used in many of our program tasks, without any KNX disconnects.

Best regards.

Avatar
0
Paul G

Thanks Ricardo, I am using the latest version of server 4.7

Yes, all sort of tricks refreshing config..ect have been attempted, though that should not be necessary if proper memory management is done and hence memory allocation space allocated to procceseses is properly cleaned by the OS after usage. 


The exit function is being used for what it has to be used for, the weird thing is that it basically makes bOS to abend, effectively kicking out the KNX connection. One I have remove use of Exit no more abends, which is a nice coincidence, or a fact.

The exit function is properly used in programming to avoid further CPU waste by using it within nested if logics, so effectively, plus further triggering the OS to clean and wipe memory usage, all programming languages wipe out the working memory allocated to them by the OS once an exit sentence is invoked

The following two programmes do the same, but one uses higher CPU consumption than the other,

Programme A (series of IFs)

IF X THEN Y EXIT

ELSE DO Z EXIT

IF W THEN F EXIT

ELSE DO O EXIT

Programme B

IF X THEN Y

ELSE 

   IF W THEN F

   ELSE DO O

EXIT    

Avatar
1
Ricardo Pinto

Hi,

I think that some additional info would be useful for them:

What server version are you using?

Have you already tried to backup the configuration, reload / restart the server and import the configuration again?


Not saying that's not a bug. But sometimes we push the servers so much back and forward, that the software gets lunatic. And sometimes a restart or reload helps. It won't hurt trying :-)

May I ask in what conditions you're using the exit function? I use tasks a lot, and never used exit in any of them.

Also, even if it's a bug, it will take time to fix. And probably it will be pushed under other bug priorities.

Best regards

Avatar
0
Paul G

hi, comfortclick team, ay luck with this one?


Customer support portal powered by UserEcho