Author Topic: [Solved] KNX IP ROUTER 750  (Read 12209 times)

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: KNX IP ROUTER 750
« Reply #15 on: August 06, 2011, 03:55:37 pm »
Bus access function (KNXnet/IP Tunneling)

The KNX IP Router 750 can be used as an interface to
KNX/EIB. KNX/EIB can be accessed from any point in the
LAN. For this purpose, a second physical address must
be assigned as described in the ETS Connection Manager
section
rock your home - http://www.agocontrol.com home automation

Marie.O

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 3675
  • Wastes Life On LinuxMCE Since 2007
    • View Profile
    • My Home
Re: KNX IP ROUTER 750
« Reply #16 on: August 06, 2011, 07:21:16 pm »
Just a FYI. This is how I call eibd:
Code: [Select]
usr/bin/eibd --no-tunnel-client-queuing -D -T -R -S -i -u --eibaddr=0.0.1 --daemon=/var/log/eibd.log ipt:10.1.2.179

brononius

  • Guru
  • ****
  • Posts: 454
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog
Re: KNX IP ROUTER 750
« Reply #17 on: August 08, 2011, 06:25:32 pm »
Thanks...
Doesn't seem to help me out.  :-X

Is there a commando i can try on the console to check the proper working between the server and the light relay? This way, i can narrow it down a bit...



Version: linuxMCE 1404, running virtual on ESXi

Orbiters: ASUS eeePAD, Nexus 5, Huwai, web
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7912-7940-7960
Camera's: Foscam POE

brononius

  • Guru
  • ****
  • Posts: 454
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog
Re: KNX IP ROUTER 750
« Reply #18 on: August 08, 2011, 07:28:29 pm »
Good news? Seems that the connection between the eibd and the hardware is working. When i push a (domotica)button, the debug (=linuxmce server with eibd) is receiving info:

Code: [Select]
Layer 0(09E1AB78,4E401AE8) Recv(021): 06 10 04 20 00 15 04 4E 01 00 29 00 B4 E0 11 0C 09 D4 01 00 80
Layer 1(09E1AB78,4E401AE8) Recv(015): 04 4E 01 00 29 00 B4 E0 11 0C 09 D4 01 00 80
Layer 1(09E1AB78,4E401AE8) Send(004): 04 4E 01 00
Layer 0(09E1AB78,4E401AE8) Send(010): 06 10 04 21 00 0A 04 4E 01 00
Layer 1(09E1A680,4E401AE8) Recv L_Data urgent from 1.1.12 to 1/1/212 hops: 06 T_DATA_XXX_REQ A_GroupValue_Write (small) 00
Layer 2(09E1A680,4E401AE8) Recv L_Data urgent from 1.1.12 to 1/1/212 hops: 06 T_DATA_XXX_REQ A_GroupValue_Write (small) 00
Layer 3(09E3B290,4E401AE8) Recv L_Data urgent from 1.1.12 to 1/1/212 hops: 06 T_DATA_XXX_REQ A_GroupValue_Write (small) 00
Layer 8(09E6BCD0,4E401AE8) Send_Route L_Data urgent from 1.1.12 to 1/1/212 hops: 05 T_DATA_XXX_REQ A_GroupValue_Write (small) 00
Layer 1(09E6BD40,4E401AE8) Send(011): 29 00 B8 D0 11 0C 09 D4 01 00 80
Layer 0(09E6BD40,4E401AE8) Send(017): 06 10 05 30 00 11 29 00 B8 D0 11 0C 09 D4 01 00 80
Layer 4(09E8D0A8,4E401AE8) Recv GroupSocket(002): 00 80
Layer 7(09E9E524,4E401AE8) Recv(002): 00 80
Layer 8(09E8D060,4E401AE8) SendMessage(008): 00 27 11 0C 09 D4 00 80

When i put now 1/1/212 as a port/channel number, it doens't work.
So I suppose it's something wrong with the template?
Version: linuxMCE 1404, running virtual on ESXi

Orbiters: ASUS eeePAD, Nexus 5, Huwai, web
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7912-7940-7960
Camera's: Foscam POE

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: KNX IP ROUTER 750
« Reply #19 on: August 08, 2011, 09:38:47 pm »
please look at http://forum.linuxmce.org/index.php/topic,11870.0.html and follow the steps.

You should be able to send commands with the groupwrite command line utility. Use the same group address in the template.

br Hari
rock your home - http://www.agocontrol.com home automation

brononius

  • Guru
  • ****
  • Posts: 454
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog
Re: KNX IP ROUTER 750
« Reply #20 on: August 14, 2011, 04:01:46 pm »
When i tried the groupwrite command, i see a lot of things happening in the debug, but no lights going on.
  groupwrite ip:192.168.111.1 0/0/3 1
  groupwrite ip:192.168.111.1 0/0/3 1 1
  groupwrite ip:192.168.111.1 1/1/212 1   (this is the group i see in the output when i push a button).

When i check the output, i see it coming from 0.0.0.
Don't i need to configure this somewhere in ETS so that the domotica is listening to it?
I check if i could create a 'dummy' input in ETS, but could'nt find anything about this.


The output
Code: [Select]
Layer 8(09FB5620,4E47D2FF) New Connection
Layer 8(09FF7060,4E47D2FF) ClientConnection Init
Layer 8(09FF7060,4E47D2FF) RecvMessage(005): 00 22 00 03 FF
Layer 7(0A0085F4,4E47D2FF) OpenGroup
Layer 4(09FF70A8,4E47D2FF) OpenGroup 0/0/3 WO
Layer 8(09FF7060,4E47D2FF) SendMessage(002): 00 22
Layer 8(09FF7060,4E47D2FF) RecvMessage(005): 00 25 00 80 01
Layer 7(0A0085F4,4E47D2FF) Send(003): 00 80 01
Layer 4(09FF70A8,4E47D2FF) Send Group T_DATA_XXX_REQ A_GroupValue_Write 01
Layer 3(09FA5290,4E47D2FF) Send L_Data low from 0.0.0 to 0/0/3 hops: 07 T_DATA_XXX_REQ A_GroupValue_Write 01
Layer 2(09F84680,4E47D2FF) Send L_Data low from 0.0.0 to 0/0/3 hops: 07 T_DATA_XXX_REQ A_GroupValue_Write 01
Layer 1(09F84680,4E47D2FF) SendTunnel(016): 04 45 00 00 11 00 BC F0 00 00 00 03 02 00 80 01
Layer 1(09F84B78,4E47D2FF) Send(016): 04 45 00 00 11 00 BC F0 00 00 00 03 02 00 80 01
Layer 0(09F84B78,4E47D2FF) Send(022): 06 10 04 20 00 16 04 45 00 00 11 00 BC F0 00 00 00 03 02 00 80 01
Layer 2(09F84680,4E47D2FF) Recv L_Data low from 0.0.0 to 0/0/3 hops: 07 T_DATA_XXX_REQ A_GroupValue_Write 01
Layer 3(09FA5290,4E47D2FF) Recv L_Data low from 0.0.0 to 0/0/3 hops: 07 T_DATA_XXX_REQ A_GroupValue_Write 01
Layer 8(09FD5CD0,4E47D2FF) Send_Route L_Data low from 0.0.0 to 0/0/3 hops: 06 T_DATA_XXX_REQ A_GroupValue_Write 01
Layer 1(09FD5D40,4E47D2FF) Send(012): 29 00 BC E0 00 00 00 03 02 00 80 01
Layer 0(09FD5D40,4E47D2FF) Send(018): 06 10 05 30 00 12 29 00 BC E0 00 00 00 03 02 00 80 01
Layer 0(09F84B78,4E47D2FF) Recv(010): 06 10 04 21 00 0A 04 45 00 00
Layer 1(09F84B78,4E47D2FF) Recv(004): 04 45 00 00
Layer 7(0A0085F4,4E47D2FF) CloseGroup
Layer 4(09FF70A8,4E47D2FF) CloseGroup
Layer 3(09FA5290,4E47D2FF) deregisterGroupCallBack 09FF70A8 = 0
Layer 8(09FF7060,4E47D2FF) ClientConnection closed
Layer 0(09F84B78,4E47D2FF) Recv(022): 06 10 04 20 00 16 04 45 00 00 2E 00 BC F0 FF FF 00 03 02 00 80 01
Layer 1(09F84B78,4E47D2FF) Recv(016): 04 45 00 00 2E 00 BC F0 FF FF 00 03 02 00 80 01
Layer 1(09F84B78,4E47D2FF) Send(004): 04 45 00 00
Layer 0(09F84B78,4E47D2FF) Send(010): 06 10 04 21 00 0A 04 45 00 00
^CLayer 8(09FB5620,4E47D310) StopServer


Ps, i must use the real ip instead of the local one. Don't think that this is important, but maybe nice to know...
« Last Edit: August 14, 2011, 04:22:11 pm by brononi »
Version: linuxMCE 1404, running virtual on ESXi

Orbiters: ASUS eeePAD, Nexus 5, Huwai, web
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7912-7940-7960
Camera's: Foscam POE

Marie.O

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 3675
  • Wastes Life On LinuxMCE Since 2007
    • View Profile
    • My Home
Re: KNX IP ROUTER 750
« Reply #21 on: August 15, 2011, 07:17:12 am »
brononi,

if you have problems when you use groupwrite, check with the bcusdk guys. That's all part of the eibd arena, maybe they have an idea of what's going on. It has nothing to do with LinuxMCE. See, if you can get help with them, if you can't get back, and we will try to investigate further.

brononius

  • Guru
  • ****
  • Posts: 454
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog
Re: KNX IP ROUTER 750
« Reply #22 on: August 17, 2011, 08:33:04 pm »
Hey,

I'm back. And a bit closer to the solution.

With the help of Martin and the forum of KNX Germany, i've learned that there's a difference between groupwrite and groupswrite (bin and hex).
And when i run in a terminal "groupswrite ip:127.0.0.1 1/1/212 1", the lights are turned on.
And with "groupswrite ip:127.0.0.1 1/1/212 0", the lights are turned out.

When i now add this 1/1/212 into the template, it doesn't work.

Can this have something to do with the groupwrite / groupswrite difference?
Version: linuxMCE 1404, running virtual on ESXi

Orbiters: ASUS eeePAD, Nexus 5, Huwai, web
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7912-7940-7960
Camera's: Foscam POE

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: KNX IP ROUTER 750
« Reply #23 on: August 18, 2011, 12:30:30 am »
did you do a quick reload after changing the port/channel to that new value?

br Hari
rock your home - http://www.agocontrol.com home automation

brononius

  • Guru
  • ****
  • Posts: 454
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog
Re: KNX IP ROUTER 750
« Reply #24 on: August 23, 2011, 03:09:34 pm »
The problem was my EIB interface apperantly.

When i:
- removed this one
- reloaded router
- recreated it (interface > EIB interface > advance ip 127.0.0.1)
- reloaded router
- put a light switch in (controlled by EIB) > only one group address (fe 0/0/3)
- reloaded router

And YEZZZZZ, light are on/off by the test buttons...


ps i'm going to write my installation steps down as clean as possible, I'll post them shortly...
Version: linuxMCE 1404, running virtual on ESXi

Orbiters: ASUS eeePAD, Nexus 5, Huwai, web
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7912-7940-7960
Camera's: Foscam POE