KNX Binding : KNX Source Address

296 views
Skip to first unread message

Karel Goderis

unread,
Dec 3, 2013, 5:17:33 PM12/3/13
to ope...@googlegroups.com
Kai,

Maybe you can answer this before I dig into the code of the Calimero Communicator but when I do a clean set-up of the KNX binding (TUNNEL mode, IP 192.168.0.5, KNX Address of the gateway 1/0/250), all telegrams sent by OH on the bus have 1.1.0 as KNX source address. The messages are correctly formatted etc, but the source address is not the KNX address of the IP gateway? I glanced at the code of the KNX binding and at (first sight) nowhere you specify which KNX source address has be used, and thus that this is determined by the Calimero lib, assuming that it would be the address of the gateway.... (I ask the question as I also have the group address monitor running in ETS4)

Here is a little excerpt from the logs:

23:07:20.549 DEBUG o.o.b.ntp.internal.NtpBinding[:83] - Got time from be.pool.ntp.org: Tuesday, December 3, 2013 11:07:20 PM CET
23:07:20.549 INFO  runtime.busevents[:26] - Date state updated to 2013-12-03T23:07:20
23:07:20.575 DEBUG o.o.b.k.i.bus.KNXBinding[:145] - Wrote value '2013-12-03T23:07:20' to datapoint 'state DP 9/1/1 Date, DPT main 0 id 11.001, low priority'
23:07:20.601 DEBUG o.o.b.k.i.bus.KNXBinding[:145] - Wrote value '2013-12-03T23:07:20' to datapoint 'state DP 9/1/2 Date, DPT main 0 id 10.001, low priority'
23:07:33.196 INFO  runtime.busevents[:22] - Temperature_Living received command 27.8

[Believe it or not, I am finally running a live installation ;-) ]

Thanks
Karel

Thomas Eichstädt-Engelen

unread,
Dec 4, 2013, 6:17:22 PM12/4/13
to ope...@googlegroups.com
Hi Karel,

[Believe it or not, I am finally running a live installation ;-) ]

Woohoooo, congrats, Karel ;-)

Best,

Thomas E.-E.

Karel Goderis

unread,
Dec 5, 2013, 2:31:12 AM12/5/13
to ope...@googlegroups.com
Thomas
you see the same source address in your KNX installation?
Karel

--
You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/groups/opt_out.

Cyril Jaquier

unread,
Dec 6, 2013, 2:53:36 AM12/6/13
to ope...@googlegroups.com
As far as I remember, I see one of the possible physical addresses as source on my KNX bus when using OH. I think the source address is set by your KNX IP gateway, not by the application running behind it. You probably have a gateway that support multiple tunnel connections. Since you are able to use the group monitor and OH at the same time, it seems that you activated this feature in your gateway. The address you gave to your gateway in your ETS4 project is not the one that will be used as source address. Have a look here, in the chapter "ETS Connection Manager":

http://www.weinzierl.de/download/products/730/KnxIP_Interface_730_BMA_EN.pdf

Even if your gateway is not a Weinzierl one, there is a good chance that it is similar.

Cheers,
Cyril

Karel Goderis

unread,
Dec 6, 2013, 8:11:40 AM12/6/13
to ope...@googlegroups.com
Cyril

I use the MDT IP gateway, and the only configurable parameter is the IP address. (exactly as the Weinzierl) (apart from its own Physical Address, which is not the one I see on the monitor, and it isn't the Local Address that you can set in ETS4 either). 

K

Cyril Jaquier

unread,
Dec 6, 2013, 9:43:39 AM12/6/13
to ope...@googlegroups.com
You can try to start another instance of OH at the same time and see which source address is used. It should be a different one for every OH instance. I can check during the week-end how the source address looks like on my bus but I'm pretty such it's one of the 5 tunneling addresses.

Cyril
Reply all
Reply to author
Forward
0 new messages