Messages

31

Users / Re: Irrigation & Rain8net

« on: March 25, 2011, 04:13:48 am »

This thread has some info http://forum.linuxmce.org/index.php?topic=8024.0

Rain8 and rain sensor could be created as separate devices which could provide better information. So rain8 setup for controlling the irrigation and then something like the 1-wire rain gauge would monitor rain fall. This would then allow the system to monitor how much rain has fallen plus trigger events in LMCE as to whether irrigation should be turned on. Plus all the timed event functionality is already built.

Also you could use soil moisture sensors (also on 1-wire) to monitor moisture sensors in each irrigation section to control what is needing water depending on their requirements.

Regarding tap presuming you can get to your piping it is not too hard to do. Can get push together connectors which apparently is very easy to use (I'll hopefully be doing some over the next few weeks). Otherwise should be a fairly quick job for plumber.

1-wire devices I mentioned are currently not implemented but big thanks to Hari and Possy for doing the work they have on getting the controller working with temp sensors. It is a very cheap alternative to some of they others like KNX etc.

This is all off the top of my head so anyone feel free to smack me over the head where I'm going wrong

32

Users / Re: An Offer To Help

« on: March 16, 2011, 10:53:33 pm »

Have you seen the user manual? http://wiki.linuxmce.org/index.php/User_Manual also has link to quick guide and install guide.

Very out of date but maybe could take info out/or modify those pages to create the guide and then eventually remove anything non relevant?

Once you decide which way your going with this I'll be happy to help update and and maintain.

33

Users / Re: Feedback wanted

« on: March 16, 2011, 01:07:07 am »

If your electrician says you are too far into the building phase, fire him, and get a better electrician.

Agreed, if it's not to late to put extra conduit in the walls it should not be to late to alter wiring to KNX I would have thought (in fact appears to be easier and quicker).... more to the point your electrician probably doesn't know anything about KNX so put in too hard basket?

How far through the build are you? Personally I'd be wanting to have the best system possible if planning to make it my home for a while even if did stall the build a little.

34

Users / Re: 1wire support

« on: March 11, 2011, 04:45:19 am »

Any idea what this means?

Code: [Select]

/var/log/pluto/46_OneWire.log1 03/11/11 16:37:00 /usr/pluto/bin/Spawn_Device.sh 46 (spawning-device) device: 46 ip: localhost cmd_line: OneWire
0 03/11/11 16:37:00 46 (spawning-device) Entering 46
========== NEW LOG SECTION ==========
1 03/11/11 16:37:00 46 (spawning-device) Starting... 1
1 03/11/11 16:37:00 46 (spawning-device) Found /usr/pluto/bin/OneWire
05 03/11/11 16:37:00.612 Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 46 last error 2 <0xb71a36c0>
05 03/11/11 16:37:00.612 The router must be reloaded before this device is fully functional <0xb71a36c0>
05 03/11/11 16:37:00.613 void ClientSocket::Disconnect() on this socket: 0x8a33de0 (m_Socket: 5) <0xb71a36c0>
05 03/11/11 16:37:00.656 Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 46 last error 2 <0xb71a36c0>
01 03/11/11 16:37:00.694 Opening port: /dev/ttyUSB0 <0xb71a36c0>
01 03/11/11 16:38:39.167 OW_get error: 22, Invalid argument <0xb71a2b90>
01 03/11/11 16:39:25.785 OW_get error: 22, Invalid argument <0xb71a2b90>
01 03/11/11 16:41:59.189 OW_get error: 22, Invalid argument <0xb71a2b90>

35

Users / Re: 1wire support

« on: March 06, 2011, 09:15:19 pm »

Wow that looks very cool.

Anything in particular you had to do to get it working?

36

Users / Re: 1wire support

« on: March 05, 2011, 11:55:19 am »

So the OneWire log in webadmin has no errors? The temp ID you used starts with '10.'?

Do you have a USB-UIRT? When I add my OneWire to webadmin and reload the USB-UIRT semi stops working.

I have managed to get owfs to a point where I can read the temp values so it does work just need to get LMCE to play nice now.

I've tried numerous things so I might need to reload a backup of the system and try a fresh install of OneWire and see how get on.

37

Users / Re: Is LinuxMCE dying?

« on: February 28, 2011, 09:32:10 pm »

Use this page to sort out downloading and installing:

http://wiki.linuxmce.org/index.php/Installing_0810

38

Users / Re: Is LinuxMCE dying?

« on: February 28, 2011, 09:10:11 pm »

It's not going anywhere and a lot of us are committed to having LMCE integrated into our homes. The dev's are putting in a massive amount of work but are always needing more help.

Maybe the forum has dwindled a bit due to the system becoming very solid and reliable so less people need help setting it up

39

Users / Re: 1wire support

« on: February 28, 2011, 06:46:19 am »

no luck, I now have tons of:

[  144.111538] OneWire[20112]: segfault at 0 ip b721d323 sp b7097e4c error 4 in libc-2.8.90.so[b71a6000+158000][ 1007.137883] OneWire[13772]: segfault at 0 ip b71af323 sp b7025e4c error 4 in libc-2.8.90.so[b7138000+158000]


when running OneWire I get:

user@dcerouter:/usr/src/LinuxMCE-0810/src/OneWire$ sudo ./OneWire
[sudo] password for user:
OneWire, v.<=version=>
Visit www.plutohome.com for source code and license information

DEFAULT: owlib.c:LibStart(54) No valid 1-wire buses found
Segmentation fault (core dumped)

I'm getting the same sort of errors

40

Users / Re: 1wire support

« on: February 27, 2011, 10:53:48 am »

If you can track down a windows machine this is what I used

http://www.maxim-ic.com/products/ibutton/software/1wire/OneWireViewer.cfm

There is a linux version but I don't think the USB devices work with it.

41

Users / Re: 1wire support

« on: February 26, 2011, 09:18:04 pm »

sudo /opt/owfs/bin/owfs /dev/ttyUSB0 --allow_other -C -m /home/user/1-wire

/opt/owfs/bin/ exists but not owfs in that folder.

do a "echo /opt/owfs/lib > /etc/ld.so.conf.d/owfs.conf", followed by a "ldconfig -X"

dcerouter_1016565:/home/kerry# echo /opt/owfs/lib > /etc/ld.so.conf.d/owfs.conf
dcerouter_1016565:/home/kerry# ldconfig -X
dcerouter_1016565:/home/kerry#

42

Users / Re: 1wire support

« on: February 26, 2011, 05:18:58 am »

Code: [Select]

dcerouter_1016565:/# lsusb
Bus 010 Device 002: ID 2040:8400 Hauppauge
Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0403:f850 Future Technology Devices International, Ltd
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1 Fob, 1-Wire adapter
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
That's my lsusb and if I enter dmesg I get this repeated (slight variation in values):

Code: [Select]

dcerouter_1016565:/# dmesg
  2a
[   23.361305]                                      reserved:        0
[   23.361308]                                      reserved:        0
[   23.370261] Clearing ep0x83.
[   23.377260] 0x81: count=16, status: 00 00 2f 40 05 04 04 00 20 29 00 00 00 2b 00 00
[   23.377273]                                   enable flag:        0
[   23.377275]                                  1-wire speed:        0
[   23.377278]                        strong pullup duration:       2f
[   23.377280]                    programming pulse duration:       40
[   23.377282]                    pulldown slew rate control:        5
[   23.377285]                              write-1 low time:        4
[   23.377287]      data sample offset/write-0 recovery time:        4
[   23.377289]                      reserved (test register):        0
[   23.377292]                           device status flags:       20
[   23.377294]                  communication command byte 1:       29
[   23.377297]                  communication command byte 2:        0
[   23.377299]           communication command buffer status:        0
[   23.377301]              1-wire data output buffer status:        0
[   23.377304]               1-wire data input buffer status:       2b
[   23.377306]                                      reserved:        0
[   23.377308]                                      reserved:        0
[   23.386261] Clearing ep0x83.
[   23.393260] 0x81: count=16, status: 00 00 2f 40 05 04 04 00 20 21 00 00 00 2c 00 00
[   23.393273]                                   enable flag:        0
[   23.393275]                                  1-wire speed:        0
[   23.393278]                        strong pullup duration:       2f
[   23.393280]                    programming pulse duration:       40
[   23.393282]                    pulldown slew rate control:        5
[   23.393285]                              write-1 low time:        4
[   23.393287]      data sample offset/write-0 recovery time:        4
[   23.393290]                      reserved (test register):        0
[   23.393292]                           device status flags:       20
[   23.393295]                  communication command byte 1:       21
[   23.393297]                  communication command byte 2:        0
[   23.393299]           communication command buffer status:        0
[   23.393301]              1-wire data output buffer status:        0
[   23.393304]               1-wire data input buffer status:       2c
[   23.393306]                                      reserved:        0
[   23.393308]                                      reserved:        0
[   23.402262] Clearing ep0x83.
[   23.409262] 0x81: count=16, status: 00 00 2f 40 05 04 04 00 20 29 00 00 00 2d 00 00
and web-admin log has following which ertries untill gives up

Code: [Select]

== ATTEMPT FRESH START ==
1 02/26/11 16:49:05 /usr/pluto/bin/Spawn_Device.sh 43 (spawning-device) 19088 Dev: 43; Already Running list: 15,16,18,19,30,31,21,27,23,35,
== FRESH START ==
1 02/26/11 16:49:05 /usr/pluto/bin/Spawn_Device.sh 43 (spawning-device) device: 43 ip: localhost cmd_line: OneWire
0 02/26/11 16:49:05 43 (spawning-device) Entering 43
========== NEW LOG SECTION ==========
1 02/26/11 16:49:05 43 (spawning-device) Starting... 1
1 02/26/11 16:49:05 43 (spawning-device) Found /usr/pluto/bin/OneWire
Return code: 127
3 02/26/11 16:49:06 43 (spawning-device) Device died... count=1/50 dev=43
Sat Feb 26 16:49:06 NZDT 2011 died

43

Users / Re: 1wire support

« on: February 23, 2011, 10:36:01 pm »

OK I'll see how I get on and try to get back up and running tonight and let you know what I get from that command.

44

Users / Re: 1wire support

« on: February 23, 2011, 10:24:02 pm »

ok so you can see the sensors if you mount owfs to a directory, right?

I will try to find a windows pc to check if the hardware works...(could take some time -> who uses windows nowadays? lol)

thanks
IF

Ummm no idea I have not tried that... does that require going down the track of dragonK's instructions? The controller does show up in lsusb. No idea if this ticket would cause any issues with it? http://svn.linuxmce.org/trac.cgi/ticket/995

LOL well I had 1-wire running on my windows setup within couple minutes

45

Users / Re: 1wire support

« on: February 23, 2011, 09:47:35 pm »

I've worked through the instructions from here which seems to run through fine but when I add the controller in web-admin I get an error in the log which I think was failing to start. I have run a windows test program that found the device and started reporting temp's straight away so the hardware is working.

I've hosed my setup so hopefully I will rebuild this weekend and have another go at it.

I have used the instructions techstyle posted plus 'cp OneWire /usr/pluto/bin' after 'make bin' which is the last command.