View single post by slychiu | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Posted: Friday Dec 7th, 2018 01:50 am |
|
||||||||||||
slychiu
|
You may not have understood my last post The bug is in Comfigurator output status display only, not the actual output state. In other words you may see the wrong output on the output status display but the correct output is actually triggered by the command You have KNX address 2/0/1 mapped to a Virtual Input 41, and Virtual Input 41 has On response Pulse Output 13 for 5 second. If KNX address 2/0/1 ON command is received from KNX, it will trigger Virtual Input 41 ON, which causes a Pulse on Output 13 (BTW Note that you can directly map to an Output ON or OFF or Pulse for 1 second, but not pulse for 5 seconds) This should work - guaranteed You may see the wrong output on the Outputs status in Comfigurator but that display does not affect what the real output is doing Have you actually tested this? Note that this works only for a Received Group address 2/0/1 from KNXYou cannot test this by pressing the Switch Device On and Switch Device Off buttons in the KNX to Comfort window. That sends to telegram to KNX 2/0/1 - It does not cause a telegram to be received from 2/0/1 and so that button does not trigger the Virtual Input. From your Monitor IO window I do not see any Virtual Input report so it may be that you did not actually cause the 2/0/1 device to send to KNX Attachment: Capture.JPG (Downloaded 20 times) Last edited on Friday Dec 7th, 2018 04:10 am by slychiu |
||||||||||||
|