KNX/EIB Home Automation Centre

[erpel]

You can try a different kernel, look if you can access other usb hardware and so on.

I think there was some issue with the default bootloader; and that it was better to replace it with a more recent one. U-Boot does much of the initialisation of the hardware (clocking etc).

[kimx]

Hi erpel, I've installed the plug following this guide http://plugcomputer.org/plugwiki/index.php/Installing_Debian_To_Flash . The uboot version is 3.4.19. The usb works, I've tested it with a usb ir reciver and lirc.

kimx

[davall]

Kimx,

if  you have eibd with usb support (eibd -help) and lsusb -vv gives information to your Berker interface please post output from 'sudo eibd -t1023 -d -i usb:'
Thanks and regards, davall

[kimx]

Hi davall, here the outputs:

Code:

root@sheeva:~# eibd -t1023 -i usb:
Layer 1(00070A20,4B92290C) Detect
Layer 1(00070A20,4B92290C) Close
Layer 1(00070A20,4B92290C) Release
Layer 1(00070A20,4B92290C) Close
initialisation of the backend failed

root@sheeva:~# lsusb -v

Bus 001 Device 004: ID 135e:0021 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x135e
  idProduct          0x0021
  bcdDevice            1.02
  iManufacturer           1 Berker GmbH & Co. KG
  iProduct                2 KNX-USB Data Interface
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           41
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower               50mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.01
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      56
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               2
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               2
Device Status:     0x0000
  (Bus Powered)
...

Thanks
kimx

[davall]

Hi Kimx,

only to be sure. Did you run the commands as root?
If yes please contact Martin Kögler with your eibd problem. He is very helpful.

Greets, davall

[kimx]

Hi, thanks again to all.
I wil contact Martin Kögler, because I don't know where the problem lies.

kimx

[kimx]

Finally I succeed with the compile process of pthsem and eibd on the plug. Thank you very much for the support.

[erpel]

Btw, the new linknx now supports stateless objects; it's really useful to send a command to the bus no matter what the previous status of the object was.

e.g. for non exclusive groups of objects (all shutters/lights down/off; when all the shutters were previously individually controlled).

[BOCA]

Code:

root@sheeva:~# eibd -t1023 -i usb:
Layer 1(00070A20,4B92290C) Detect
Layer 1(00070A20,4B92290C) Close
Layer 1(00070A20,4B92290C) Release
Layer 1(00070A20,4B92290C) Close
initialisation of the backend failed

how do you fixed this?
i'm having exactly the same problem...

the usb interface is there:
generic-usb 0003:135E:0023.0001: hiddev96: USB HID v1.01 Device [ALBRECHT JUNG GMBH & CO. KG KNX-USB Data Interface] on usb-orion-ehci.0-1.4/input0

but findknxusb doesnt find anything:
debian:~# findknxusb
Possible addresses for KNX USB devices:
debian:~#

[erpel]

I would suggest that you go with these kinds of device specifics to the eibd mailing list; Martin will surely help you.

I believe, that for USB devices; a git snapshot needs to be used; not the released version.

[BOCA]

YAY! i got it finally working! 
problem was pthsem installed to /usr/local/bin instead of /usr/bin
so i compiled pthsem from git with ./configure --prefix=/usr
then compiled bcusdk from git and it worked!

debian:/usr/local/bin# findknxusb
Possible addresses for KNX USB devices:
device: 1:4:1:0:0 (ALBRECHT JUNG GMBH & CO. KG:KNX-USB Data Interface)

[erpel]

I hope that Martin releases a version soon with support of this so that the packages work with the USB interface out of the box.

[erpel]

note that the link should consistenly be

http://scorpius.homelinux.org/~marc/eib_sheeva.html

(dyndns account changes)

[erpel]

There is a version of eibd that will be released one of these days that will support the USB devices. This howto only covers connecting over the network atm.

[erpel]

Hey guys,

This story seems to be read quite a bit, if any of you have set up a similar system; why don't you post some screens of the result? I have two systems running, one on a plug computer and another one on an NLSU2; but for that one, I have to create some nice 3D graphics; it's currently a basic setup with a rudimentary line based plan.