HS/FS iKO for night/day is not sending

[mmb4]

Hi

Since a few months I am wrestling with the HS3, trying to understand how things work. At the moment I am getting things to work, however not all is going wel...
My question:
I am trying to create an iKO which can control night and day, for example to block lights from going on during the day or to control my rollo's. I made a logic which sets the iKO at 1 when the sun sets through the "sunset building stone" and sets the iKO at 0 when the sun goes up. However when I try to use that iKO to control other LOgic it does nothing. Is it not possible going this way? Or do I have to alter something to make the iKO send it's value when it changes?
Thanks!

[MatthiasS]

It send when it's changing

Show us your GLE page!

[mmb4]

That was fast! Thanks.

Here are my GLE pages. I hope it isn't too silly what I am doing

[MatthiasS]

Not too silly ;9 The input selector is not necessary, you can connect your donker directly.

You sunrise module has a cycle of 60 minutes. It will be calculated each hour. That's a pretty lon period.

But anyway, many people have problems with this logic modules. That is because they just fire in the moment of sunrise, after a restart of your HS they do not show the actaul state.

Try another module. I wrote a sun position module in order to overcome the problems with the original modules:

https://knx-user-forum.de/downloads.php?do=file&id=9

I think it's selfexplaining?

[mmb4]

Thanks Matthias, i 'll try your building stone tonight whem I am at home.

However, the input selector is used to invert the 0 (light) to a 1. Connecting it directly would block the staircaselighting during the night and allow it during the day. That's not what I want. What is in HS-land the best way to invert a binary value? I cannot find a building block for that.

[MatthiasS]

Right-Click (on input) - Invert

[mmb4]

Right-click on what exactly? Clicked everyting but I cannot find invert
Sorry for my ignorance...

[MatthiasS]

Example:

E2 has bee inverted. You can release inverting by clicking on "Negierung aufheben"

[mmb4]

It was the little grey thing :-)
Well, I am learning. That's nice.

[mmb4]

Hi Matthias

I just had a look at your building stone. What I don't understand is how I can use the twilight function. You cannot differentiate between morning (sun is coming up) and evening (sun going down)?

[MatthiasS]

Of course one can decide:

0 -> 1: sunset
1 -> 0: sunrise

The deviation of 6° is called "civil twiglight". You can set this to zero for the "exakt" moment. I'm using 6° because at 0° is not dark, yet.

Twilight - Wikipedia, the free encyclopedia

[mmb4]

Thanks. I have it running now thanks to this building stone.

About the "twilight" option. Is it sending 1 during the whole night, or just in the twilight? I mean two times a day (before sunrise and after sunset).

Another question, just for my interest, is how one could detect the transit from 0 -> 1 and from 1 -> 0 in the HS?

Many thanks for your help! I am moving on to the "Rolladenbaustein".

[MatthiasS]

I believe that you have a general problem in understanding KNX. KNX is works on events, always. And the HS, too. That mean, whenever something "happens", a telegram is sent to the bus.

The HS works this way, too. He has to. This is a big difference to SPS-behaviour!

For logic modules: Whenever an input gets a new telegram, the module will be calculated and outputs will be set. "Will be set" means: output sends a telegram. Depending on the parameters of this special output, it will send the telgeram each time the module will be calculated (=every time an input gets a new telegram) or only if the output changes (SBC output, send by change).

So for my module, the output is "sent by change", but when the HS starts, it calculates the output so that at start the output is always right. If you connect an internal KO to the output, it will be "1" during the night an "0" during the day.

Therefore, you do not need a ramp detection! The HS has one module for this, but I never used it on sbc-outputs. It makes no sense there. You can use it on outputs that will be fired on each caluclation to detect a change. But the faster way is to use the sbc-output.