1wire support

[Techstyle]

where should it be installed to?

do I have the directories correct or am I missing a step?

[Techstyle]

after running the ./configure step I get the following:

Code:

Current configuration:

    Deployment location: /opt/owfs

Compile-time options:
                  Caching is enabled
                      USB is DISABLED
                      I2C is enabled
                   HA7Net is enabled
                       W1 is enabled
           Multithreading is enabled
    Parallel port DS1410E is enabled
        TAI8570 barometer is enabled
             Thermocouple is enabled
         Zeroconf/Bonjour is enabled
             Debug-output is enabled
                Profiling is DISABLED
Tracing memory allocation is DISABLED
1wire bus traffic reports is DISABLED

Module configuration:
                    owlib is enabled
                  owshell is enabled
                     owfs is DISABLED
                  owhttpd is enabled
                   owftpd is enabled
                 owserver is enabled
                    ownet is enabled
                 ownetlib is enabled
                    owtap is enabled
                    owmon is enabled
                   owcapi is enabled
                     swig is DISABLED
                   owperl is DISABLED
                    owphp is DISABLED
                 owpython is DISABLED
                    owtcl is DISABLED

is this correct?

[Techstyle]

when I run 'make' I get the following at the end:

Code:

make[4]: Leaving directory `/usr/src/owfs-2.8p5/module/owcapi/src/c'
Making all in include
make[4]: Entering directory `/usr/src/owfs-2.8p5/module/owcapi/src/include'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/usr/src/owfs-2.8p5/module/owcapi/src/include'
make[4]: Entering directory `/usr/src/owfs-2.8p5/module/owcapi/src'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory `/usr/src/owfs-2.8p5/module/owcapi/src'
make[3]: Leaving directory `/usr/src/owfs-2.8p5/module/owcapi/src'
make[3]: Entering directory `/usr/src/owfs-2.8p5/module/owcapi'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/usr/src/owfs-2.8p5/module/owcapi'
make[2]: Leaving directory `/usr/src/owfs-2.8p5/module/owcapi'
Making all in owtap
make[2]: Entering directory `/usr/src/owfs-2.8p5/module/owtap'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/src/owfs-2.8p5/module/owtap'
Making all in owmon
make[2]: Entering directory `/usr/src/owfs-2.8p5/module/owmon'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/src/owfs-2.8p5/module/owmon'
make[2]: Entering directory `/usr/src/owfs-2.8p5/module'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory `/usr/src/owfs-2.8p5/module'
make[1]: Leaving directory `/usr/src/owfs-2.8p5/module'
make[1]: Entering directory `/usr/src/owfs-2.8p5'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/usr/src/owfs-2.8p5'

does this look correct?

[hari]

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

[Techstyle]

Hari,

Did that and rebooted.  The log looks a little better:

1   01/22/11 17:20:41   57 (spawning-device)   Starting... 4
1   01/22/11 17:20:42   57 (spawning-device)   Found /usr/pluto/bin/OneWire
05   01/22/11 17:22:18.939      Creating child 58 <0xb70f96c0>
05   01/22/11 17:22:18.939      Note: Device manager has attached a device of type 1946 that this has no custom event handler for.  It will not fire events. <0xb70f96c0>
05   01/22/11 17:22:18.939      Note: Device manager has attached a device of type 1946 that this has no custom handler for.  This is normal for IR. <0xb70f96c0>
Return code: 139
3   01/22/11 17:22:41   57 (spawning-device)   Device died... count=4/50 dev=57
Sat Jan 22 17:22:41 CST 2011 died

I still cannot locate the sensor ID

[DragonK]

after running the ./configure step I get the following:

Code:

Current configuration:

   Module configuration:
                    owlib is enabled
                  owshell is enabled
                    owfs is DISABLED
                  owhttpd is enabled
                   owftpd is enabled
                 owserver is enabled
                    ownet is enabled
                 ownetlib is enabled
                    owtap is enabled
                    owmon is enabled
                   owcapi is enabled
                     swig is DISABLED
                   owperl is DISABLED
                    owphp is DISABLED
                 owpython is DISABLED
                    owtcl is DISABLED

is this correct?

OWFS is disabled, that might be your problem.
Module configuration:
                    owlib is enabled
                  owshell is enabled
                   owfs is DISABLED
                  owhttpd is enabled
                   owftpd is enabled
                 owserver is enabled
                    ownet is enabled
I installed it following the steps from here,
http://www.mail-archive.com/owfs-developers@lists.sourceforge.net/msg04821.html

Code:

Here's the steps for OWFS.

Basic ubuntu install and added lots of fluff.

Then for OWFS ---

sudo apt-get install cvs

sudo apt-get install autoconf
sudo apt-get install automake
sudo apt-get install libtool

# For filesystem (FUSE)
sudo apt-get install libfuse-dev

# For USB support
sudo apt-get install libusb-dev
sudo apt-get install libusb++-dev

# For languages
sudo apt-get install swig
sudo apt-get install php5
sudo apt-get install php5-dev
sudo apt-get install python-dev
sudo apt-get install libperl-dev
sudo apt-get install tcl-dev

and mine seems to be working. just need the interface and sensors now.

Karel

[hari]

we don't need owfs support.. the dce devices uses the capi.

@Techstyle: we have another error there, please provide me with ssh access to your core.

br Hari

[RayBe]

Hi,

Hari, just a question, i do not want to stress you in any way, i just want to know for future plans.
Are you planning to implement other features of 1-wire in the driver?
Like LCD support, Humidity sensors, I/O channels etc?

thanks for al your hard work,
br,
Raymond

[_if_]

Hey guys,

I finally got an 1-wire interface and want to know if anybody was able to get it running so far?
I get no errors during install but when I start OneWire I get:

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

also if I try to mount owfs to a directory I can't see my sensor in it and it says:
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

any ideas?

[Kezza]

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.

[_if_]

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

[Kezza]

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

[_if_]

it should be enough to do a: sudo /opt/owfs/bin/owfs /dev/ttyUSB0 --allow_other -C -m /home/user/1-wire

in my case this will actually mount owfs to the 1-wire directory (showing bus.0, settings, ...) but no sensor is showing up...

i see the interface in lsusb and dmesg as well.

[Kezza]

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.

[Techstyle]

I have had other things to sort recently but when I was looking for this I found an article that suggested that my device shared a driver name with another device and that the driver picked up for my device would need to be replaced manually. I am travelling right now but may be able to put a link to this up soon. It may be my problem as well as others