• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 [2] 3
16  General Category / Success stories / Re: KNX/EIB Home Automation Centre on: March 05, 2010, 08:09:50 AM
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).
17  General Category / Success stories / Re: KNX/EIB Home Automation Centre on: March 05, 2010, 08:05:58 AM

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 -->
18  General Category / Success stories / Re: KNX/EIB Home Automation Centre on: March 05, 2010, 01:42:41 AM
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.
19  General Category / Success stories / Re: KNX/EIB Home Automation Centre on: March 02, 2010, 03:46:46 AM
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.

20  General Category / Success stories / Re: KNX/EIB Home Automation Centre on: March 02, 2010, 01:32:26 AM
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
21  General Category / Success stories / Re: KNX/EIB Home Automation Centre on: March 02, 2010, 01:26:59 AM
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
rtc-mv rtc-mv: setting system clock to 2000-02-07 12:16:19 UTC (949925779)
UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:rootfs", error -19
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            1024 mtdblock0 (driver?)
1f01            4096 mtdblock1 (driver?)
1f02          519168 mtdblock2 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[<c0032b24>] (unwind_backtrace+0x0/0xdc) from [<c041cb3c>] (panic+0x3c/0x128)
[<c041cb3c>] (panic+0x3c/0x128) from [<c0008f24>] (mount_block_root+0x1d4/0x21c)
[<c0008f24>] (mount_block_root+0x1d4/0x21c) from [<c00090fc>] (prepare_namespace
+0x8c/0x1c8)
[<c00090fc>] (prepare_namespace+0x8c/0x1c8) from [<c000844c>] (kernel_init+0xdc/
0x114)
[<c000844c>] (kernel_init+0xdc/0x114) from [<c002e45c>] (kernel_thread_exit+0x0/
0x8)

I've updated the version since then, mainly to include support for a number of DVB devices (see other post). You need to verify your settings and go over the install procedure again. See if you modified your settings correctly under "Booting in the final system".

Code:
setenv mainlineLinux yes
setenv arcNumber 2097
setenv bootargs 'console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs'
setenv boot_nand 'nand read.e 0x2000000 0x100000 0x400000'
setenv bootcmd 'run boot_nand; bootm 0x2000000'
saveenv
reset
22  General Category / Success stories / Re: KNX/EIB Home Automation Centre on: March 01, 2010, 02:28:13 PM
I'm just currenly overloaded at work ^^'.

Join the club :-) releases that should be done yesterday, Indian guys poking for input and requesting packaging yet another weird Java version, giving input on web interfaces and all in between trying to do some gstreamer work on odd and dodgy encoder support.

Anyway, good luck for making the whole thing work, this is tricky, but funny too  Roll Eyes

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.

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

Running the web interface over an ssh tunnel with the firefox foxyproxy extension to filter on your IP/mask is nice to see if you have killed all your lights, if someone arrived or just to switch the heating on if you're getting home early (the normal stuff you've obviously automated that with the sheeva).
23  General Category / Success stories / Re: KNX/EIB Home Automation Centre on: March 01, 2010, 02:22:19 PM
it is currently on hold, while we look into merging Martins' changes on pth in the official branch. I haven't heard about this in a couple of weeks; maybe we should poke Ralph (pth maintainer) again.

All the ITPs are there though.

Since all else is depending on pth(sem), it's a bit of a blocker until this is cleared up.
24  General Category / Success stories / Re: KNX/EIB Home Automation Centre on: March 01, 2010, 01:28:36 PM
I suspect that Martin updated pthsem to do a release depending on the new features of bcusdk later on.

If I have some time at noon (that is a very big if ATM at work); I'll try to get a temporary svn snapshot out for you.
25  General Category / Success stories / Re: KNX/EIB Home Automation Centre on: February 27, 2010, 04:05:55 AM
I'll port pthsem since it has been released; for eibd; it's better to wait for a new release. Maybe the new pthsem release already solves you r problems.

If I would not be swamped with work last week; I would already have prepared the package.
26  General Category / Success stories / Re: KNX/EIB Home Automation Centre on: February 05, 2010, 01:58:22 AM
It looks as if all the building blocks should be there to do what you want on the sheeva plug. I suspect you are missing some specific drivers for the USB version  (I cannot provide much expertise there since I've only worked with the Siemens IP interface).

You do need a different command line (IIRC) in the /etc/default/eibd-server that I proviced; it should be documented somewhere in on the site of the upstream author:
http://www.auto.tuwien.ac.at/~mkoegler/index.php/eibd

There seems to be some other people having looked for solutions:
http://forum.linuxmce.org/index.php?topic=9132.0
http://www.domotiga.nl/projects/domotiga/wiki/Domotiga/EIB

I just did a quick verify and usb should be enabled in the eibd packages. There is always the official mailinglist where you'll certainly get the info from people working with your config.
http://lists.sourceforge.net/lists/listinfo/bcusdk-list]


UPDATE:

I just noticed that there are some mails in my inbox from the mailinglist about USB backends:

Quote
Here you have the trace of eibd when this problem happens:                                                                                                                                                                                   
                                                                                                                                                                                                                                             
eibd -u usb:2:2:*1:0* -t1023*                                                                                                                                                                                                               
                                                                                                                                                                                                                                             
*Layer 1(08E10BE8,4B6ABDD6) Detect                                                                                                                                                                                                           
Layer 1(08E10BE8,4B6ABDD6) Using 2 (2:2:1:0) (2:129)                                                                                                                                                                                         
Layer 1(08E10BE8,4B6ABDD6) Open   


If you get it working; just drop a note and add your example in the config files as comment.
27  General Category / Success stories / Re: KNX/EIB Home Automation Centre on: January 15, 2010, 09:06:25 AM
Just wondering,

Did anyone use this setup or do you have any feedback?

My setup is running at home for quite some time (the always up is much better than the NSLU2) and the plug nature makes it perfect for this. The only improvement I could do, is to add a outlet in my electricity cabinet and connect it there to my switch instead of plugging it into socket in a room.

If you don't have an iron electricity cabinet; combining with a wireless stick could also be a nice touch; then you would not be bound by the proximity of network connection sockets. The 3.0 release claims that this would be included in the plug.
28  General Category / Success stories / Re: DVB-T/S IPTV on: December 30, 2009, 03:12:48 PM
Oops.. just read your post more carefully Smiley. So the Hauppauge Nova-T Stick site I searched is based in UK. Is your setup in Europe or in the US?

The setup is for Europe; but AFAIK; it should be the same around the globe; DVB is pretty standard. The most important differences are the payloads in the transport streams. IIRC, the US sticks with MPEG2 for HD, while the rest of the world uses MPEG4

I even posted the Wikipedia link to Flanders: http://en.wikipedia.org/wiki/Flanders :-)
29  General Category / Success stories / DVB-T/S IPTV on: December 23, 2009, 04:34:08 AM
We have just created a small setup to convert typical DVB-T to IPTV on your home network. It should work with DVB-S too since, at first glance, most of the drivers required for popular USB DVB-S devices are in the 2.6.32 kernel.

Hardware

There is a lot of USB based DVB-T hardware around that is supported in the kernel; this setup used a Hauppauge Nova-T Stick.

Streaming setup.

Since everything we need is already in Debian, setting up the system is easy to do.

Firstly, prepare your Sheeva as described in http://chiana.homelinux.org/~marc/eib_sheeva.html; this just documents readily available information. Once this is done; you'll have a standard GNU/Debian Lenny system.

The kernel is based on one that is available on this forum, but has additional DVB support (see config on http://crichton.homelinux.org/~marc/downloads/sheeva-config-2.6.32.2). The mentioned archive should have all you needed (kernel, modules in the filesystem and the firmware file).

Once you have booted the system, place the file
Code:
dvb-usb-dib0700-1.20.fw
in
Code:
/lib/firmware/
; or install firmware-linux-nonfree from sid http://packages.debian.org/sid/firmware-linux-nonfree.

Point your /etc/apt/sources.list to your favourite Debian mirror and install:

Code:
# apt-get install gstreamer-tools  gstreamer0.10-alsa gstreamer0.10-plugins-bad gstreamer0.10-plugins-base gstreamer0.10-plugins-good gstreamer0.10-tools gstreamer0.10-x libgstreamer-plugins-base0.10-0 libgstreamer0.10-0 

This prepares your system with gstreamer. Finally start

Code:
$ gst-launch-0.10 -v dvbsrc frequency=482000000 ! queue2 ! udpsink host=226.226.226.1 port=2266 sync=False

This command line shows the options for a national broadcaster in Flanders (http://en.wikipedia.org/wiki/Flanders); check for your own regional settings. This command will capture (in this case) 8k packets and send them on a multicast address. When subscribing (e.g. with VLC) on this address; you will receive the full MPTS; which means you can select any program you would have with this DVB-T provider.

Be advised that low cost switch material at home will probably broadcast the stream instead of using multicast; the stream is about 16 Mbps.

The setup for DVB-S should be similar; I have a Terratec USB device on my desk that I really need to test ASAP.
30  General Category / Success stories / Re: USB Webcam as a surveillance camera on: December 08, 2009, 09:11:00 AM
The simplest might be just to

Code:
apt-get install motion

and change the value of the
Code:
webcam_localhost off

in
Code:
/etc/motion/motion.conf

Point your browser to http://sheeva-ip:8081/ and you should have a live feed; the images are saved in /tmp/motion/

Have a look at the config, I disabled some options (save movies), ...
Pages: 1 [2] 3