KNX/EIB Home Automation Centre

[erpel]

You should get something along these lines, note the compile date and stamp (mleeman@bane):

This is the new logging from the kernel while booting after I made the changes to include more DVB support (you'll see the DVB-T stick being initialised at the end of the logging).

Code:

debian:~# dmesg
Linux version 2.6.32.2 (mleeman@bane) (gcc version 4.3.2 (Debian 4.3.2-1) ) #1 PREEMPT Tue Dec 22 15:48:46 CET 2009
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell SheevaPlug Reference Board
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 131072
free_area_init_node: node 0, pgdat c05903f4, node_mem_map c0667000
  Normal zone: 1024 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 130048 pages, LIFO batch:31
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB = 512MB total
Memory: 513024KB available (5184K code, 1034K data, 148K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:114
Console: colour dummy device 80x30
Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A0, TCLK=200000000.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
initial MPP regs: 01111111 11113322 00001111 00100000 00000000 00000000 00000000
  final MPP regs: 01111111 11113322 00001111 00000000 00000000 00000000 00000000
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4009, nTxLock = 32078
msgmni has been set to 1002
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 465 at 0x000003a20000
Bad eraseblock 1349 at 0x00000a8a0000
Bad eraseblock 1423 at 0x00000b1e0000
Bad eraseblock 3397 at 0x00001a8a0000
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd2 to ubi0
UBI: MTD device name:            "root"
UBI: MTD device size:            507 MiB
UBI: number of good PEBs:        4052
UBI: number of bad PEBs:         4
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 4052
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 2/0
UBI: image sequence number: 0
UBI: background thread "ubi_bgt0d" started, PID 450
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:50:43:01:6c:06
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mice: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
Registered led device: plug:green:health
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
Gating clock of unused units
before: 0x00df03dd
 after: 0x00c701d9
rtc-mv rtc-mv: setting system clock to 2000-05-11 14:13:14 UTC (958054394)
UBIFS: recovery needed
usb 1-1: new high speed USB device using orion-ehci and address 2
usb 1-1: configuration #1 chosen from 1 choice
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   515708928 bytes (503622 KiB, 491 MiB, 3997 LEBs)
UBIFS: journal size:       9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: zlib
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:13.
Freeing init memory: 148K
dib0700: loaded with support for 13 different device-types
dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware
usb 1-1: firmware: requesting dvb-usb-dib0700-1.20.fw
dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
dib0700: firmware started successfully.
dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Hauppauge Nova-T Stick)
DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)...
DiB0070: successfully identified
input: IR-receiver inside an USB DVB receiver as /devices/platform/orion-ehci.0/usb1/1-1/input/input0
dvb-usb: schedule remote query interval to 50 msecs.
dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_d
NET: Registered protocol family 10
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0: link up, 1000 Mb/s, full duplex, flow control disabled
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present

[Titus_Crow]

However, if I reload the webpage, the lamp icon don't keep the status of the lamp.
For eg, if I switch on the lamp through knxweb, and then I reload the page,
the lamp icon appears in off state.
It's for sure something noobish, but i found the linknx documentation somewhat lacky  Embarrassed
(if you have any clue, you're welcome  Wink )

The Sheeva is just perfect for this. It was a bit tricky to get the dimmer working perfectly (had to enable bus feedback to get the icons right); but it's working now and unless I add more devices, I wouldn't know what's missing with this combination.

If I understand what you wrote, my issue dealing with the actualisation of my lights icons in knxweb is ETS-configuration related ?

The web interface is just so sweet to see if our 5yr twins are sleeping or yet again playing with the lights on :-)

  Here, the only child we have is a damn fat cat, but it could be cool to see if he's playing with the lights on, too 

@kimx : I'll try to post the .deb of pthsem and a tar.gz of bcu-sdk as soon as I can ^^

[erpel]

If I understand what you wrote, my issue dealing with the actualisation of my lights icons in knxweb is ETS-configuration related ?

Sorry, missed your message.

It depends on what kind of device you are having. Most of the devices are just on/off devices; so they are just object types 1.001. That works out of the box (see the house.xml I install by default). linknx is stateful, if sees a message passing on the bus it will adjust the internal value. Take care though when you restart linknx, it will loose the info and will only pick it up as the data passes on the bus again (like temp values or even light on/off).

I know of a version of linknx that allows stateless devices (e.g. for shutting down groups of lights or shutters no matter what); but that has not been released. I assume that will be matched with a special variable in the XML description.

With dimmers, they are type 3.007; and some others have to be enabled on the bus (ETS) and connected to the linknx interface (which are e.g. 1.001 objects (switching value feedback) or 5.xxx objects (brightness value feedback)).

These values are the 'other' entry you need for dimmers when you create them.

[kimx]

Hi, regarding this:

Take care though when you restart linknx, it will loose the info and will only pick it up as the data passes on the bus again (like temp values or even light on/off).

I've set the read flags on the actor for adresses which indicate lights. Now even when I restart linknx it gets the right values for the object.

kimx

[dlh]

Well third (or is it more) time's a charm.
Thanks,
Dave

[davall]

Hi, I'm very impressed to read all these succes story with eibd on the sheeva plug. I hope my story will have a happy end to . I'm using a usbinterface to connect to the bus. Unfortunatly the packages provided by erpel don't support this feature right now. I've seen that the user Titus_Crow compiled his own version of eibd and pthsem and his attempt was a success. My problem is that I don't know how to do that. I red the mailing list but I didn't understand how to build my own version. Here my question: can someone share his build or could you (erpel) update your packages?

Thank you very much

kimx

Hi Kimx,

can you post the output from command 'eibd --help'
It should look like this:
Usage: eibd [OPTION...] URL
eibd -- a commonication stack for EIB
(C) 2005-2008 Martin Koegler <mkoegler@auto.tuwien.ac.at>
supported URLs are:
ip:[multicast_addr[:port]]
ipt:router-ip[:dest-port[:src-port[:nat-ip[:data-port]]]]]
usb:[bus[:device[:config[:interface]]]]
---------------------------------------------
As you see i've compiled eibd with usb support.
If your eibd has no support for usb devices, it's a pleasure to share my version.

Regards, davall

[davall]

If I understand what you wrote, my issue dealing with the actualisation of my lights icons in knxweb is ETS-configuration related ?

Sorry, missed your message.

It depends on what kind of device you are having. Most of the devices are just on/off devices; so they are just object types 1.001. That works out of the box (see the house.xml I install by default). linknx is stateful, if sees a message passing on the bus it will adjust the internal value. Take care though when you restart linknx, it will loose the info and will only pick it up as the data passes on the bus again (like temp values or even light on/off).

I know of a version of linknx that allows stateless devices (e.g. for shutting down groups of lights or shutters no matter what); but that has not been released. I assume that will be matched with a special variable in the XML description.

With dimmers, they are type 3.007; and some others have to be enabled on the bus (ETS) and connected to the linknx interface (which are e.g. 1.001 objects (switching value feedback) or 5.xxx objects (brightness value feedback)).

These values are the 'other' entry you need for dimmers when you create them.

Hi Erpel,

maybe you missed it. Jeff published a new linknx version in Feb. with stateless objects.
In linknx you can define objects as persistent. So when you restart linknx knows in which state an object was.
For me the actors read flag does not allways work as promised! The linknx persist seems saver. And for self defined objects within linknx you can use it too. I store these values in a mysql database, but you can use the filesystem as storage too.
Maybe this helps some of you?

Greets, davall

[kimx]

Hi davall, here is the output from the command : http://paste.ubuntu.com/388812/
It seems compiled with usb-support, but it doesn't work with my interface.

Another problem that I'm having is: when I restart the plug, the usb-interface doesn't show up in lsusb. I have to plug it out and in again. I don't know where this strange behavior come from, but I get some errors in dmesg:

Code:

dmesg:
usb 1-1: new full speed USB device using orion-ehci and address 3
hub 1-0:1.0: unable to enumerate USB device on port 1

After unplug and replug:

Code:

usb 1-1: new full speed USB device using orion-ehci and address 4
usb 1-1: configuration #1 chosen from 1 choice
generic-usb 0003:135E:0021.0001: hiddev96: USB HID v1.01 Device [Berker GmbH & Co. KG KNX-USB Data Interface] on usb-orion-ehci.0-1/input0

Regards
kimx

[erpel]

maybe you missed it. Jeff published a new linknx version in Feb. with stateless objects.

Yes I did! I was waiting for this do do a conditionless closing of the shutters at dawn (Now I had to mate sure that I pressed the 'all up' function, before the 'all down' worked.

I'll update the package ASAP.

[davall]

Hi Kimx,

o.k. Your eibd has usb support. I recommend to search for your problem on this forum The eibd developer is also active there. Many people have problems with usb connectivity and there seems always be a solution. http://knx-user-forum.de/knx-eib-forum/

Good luck!

Greets davall

PS: I'm using IP with no problems

[kimx]

Hi davall, my setup is working properly on a laptop on ubuntu. I can't understand the difference between this two setups.

kimx

[davall]

Hi davall, my setup is working properly on a laptop on ubuntu. I can't understand the difference between this two setups.

kimx

Hi kimx,

so you can be sure eibd is running with your Berker USB interface, fine!
The difference can be in your Linux config on both systems.
On the one hand a PC x86 with Ubuntu and on the other hand a Sheeva arm architecture with which distro? Ubuntu, Debian, Gentoo??? Bevor i switched to IP i've had a running USB config on the sheeva with debian lenny and a Gira USB interface.
So at first i would build a system with working usb config and then test the eibd functionality.
I can recommend debian lenny or squeeze a lot. In May my sheeva has birthday ;-)

Greets,
davall

[kimx]

Hi davall, I have installed debian on flash and got the kernel from http://sheeva.with-linux.com/sheeva/index.php?dir=2.6.32.8. I can't find the difference between the two installation. The only thing that I've seen is that the usb related stuff is in the kernel instead of being loaded as a module.

Code:

root@sheeva:~# cat /etc/debian_version
squeeze/sid
root@sheeva:~# uname -a
Linux sheeva 2.6.32.8 #1 PREEMPT Tue Feb 9 14:36:02 MST 2010 armv5tel GNU/Linux

kimx

[davall]

for your info: http://plugcomputer.org/plugforum/index.php?topic=828.0
Maybe you have a hardware problem, too.

You can try a different kernel, look if you can access other usb hardware and so on.
And at least find out if  your problem is hw related.
If your usb port is o.k. we can dig deeper with eibd and logging output.

Good luck, davall

[erpel]

Packaged the 0.0.27 version of linknx (tnx davall); the next build will have the following remark about the 'stateless' behaviour in the house.xml example file.

Code:

            <!-- Note that if-false stands for the stateless variant: if
                 for some reason you want to make certain that e.g. a light
                 is on no matter what happened; use "if-true"/"if-false";
                 the command will be put on the bus even if the internal
                 state of linkx thinks it is already on -->