BOS Tasks + Fysical button

stephen andries

2 months ago
updated 2 months ago

Hello,

I have made a task that opens or closes all my blinds.
There are 2 blinds in a corner that interfere with each other. So I've put a block the actuator that doesn't allow the 2 blinds to move together.
It's been working perfectly for over a year now. I've been activating the task on the visualisation until now.

They all move together, but 1 of the 2 in the corner stays stationairy until the other one is fully opened or closed. Then the last one does it's thing.

Now I've programmed a fysical button to trigger the task but it's got an issue.

The blind that waits til the other one has finished, doesn't close all the way. It stops at half the length it should travel. When i look in the visualisation, it thinks it's fully opend or closed.

I don't understand why it does this when triggered on a fysical button, but doesn't when i trigger it on the visualisation. It's the same task

It almost looks like the time it is waiting in blocked mode, doesn't get added up after. But all this logic should be executed on the KNX actuators rather then the BOS?

Replies 5

Newest first
Newest first Oldest first

Jürgen Jürgenson

2 months ago

Maybe you can use a program to control the fine tuning of the blinds. I see that the scene is triggered but scene may not be the best solution to do advanced delays/blocking etc. So yeah its hard to say. I would test it with a program and then trigger it from a scene.

Reply Link

I've enabled allow retrigger, but it still doesn't work.

When i use the visualisation, 1 blind gets blocked to make sure the 2 blinds don't colide. But when i use the fysical button the blockage on the actuator doesn't work. They all move at the same time. But 1 stops prematurly because the all of the suden the blockage kicks in. 20seconds when all blinds are finished, that one starts to turn.

so it looks like the blockage doesn't kick in at the beginning as intended, but gets delayed to when the other blind is finished.

I just don't get why it acts differently between fysical button and visualisation. They both trigger the same groupadress

Change the bOS scene trigger to "allow retrigger". Then it should work without needing to get the 0. Also use debug monitor to see what actually happens on the line when you send the trigger from your siemens switch.

i've created a groupadres in ETS to activate the scene. the scene is created in BOS and I've set the trigger to that groupsadres. In the visualisation I've made a button to send a switching item to the groupadres.

But when i add a physical button to that groupsadres, the physical button gives a different result.

this is the setting on the fysical button (touch screen siemens), i need to use the bell function witch results in having to hold the button for 1second. If i use switching it doesn't work, and if i send a value of 1, it only works 1 time, cause i cant get the value back to 0. I've tried to add at the end of the task to set the value to 0, but it's not possible in BOS.

Hey

How did you program the physical button in KNX? So it now ignores the bOS scene? If it works correctly with bOS trigger then why not link it to the physical button to trigger the scenes?