LinuxMCE Forums

General => Users => Topic started by: hari on January 19, 2011, 11:12:15 am

Title: 1wire support
Post by: hari on January 19, 2011, 11:12:15 am
Hi Folks,

I did write a DCE device for the owfs 1wire driver. Device Template #2161. The code is here: http://svn.linuxmce.org/trac.cgi/browser/branches/LinuxMCE-0810/src/OneWire/

Just create "Multilevel Sensor" Childs and put the 1wire ID into the port/channel field. The DCE device will store the last measurement and only send events when things have changed. Only temperature sensors supported atm:

35   01/19/11 11:11:30.628      Temperature for 28.B3795602000: 25.62 <0xb78c9b70>
35   01/19/11 11:11:30.628      Old temperature for 28.B3795602000: 25.56 <0xb78c9b70>
07   01/19/11 11:11:30.629      Received Message from 233 (1wire temp / ) to -1001 (unknown / ), type 2 id 25 Event:Temperature Changed, retry none, parameters: <0xb2cfdb70>
07   01/19/11 11:11:30.629        Parameter 30(Value): 25.62 <0xb2cfdb70>

br Hari
Title: Re: 1wire support
Post by: posde on January 19, 2011, 11:22:34 am
hari,

you should change your description to LinuxMCE HA Device Driver God :)

Thank you for your dedication!
Title: Re: 1wire support
Post by: _if_ on January 19, 2011, 04:18:16 pm
good job, thanks Hari!
Title: Re: 1wire support
Post by: tschak909 on January 19, 2011, 04:54:11 pm
are there packages in the package database now for owfs/any other deps?

-Thom
Title: Re: 1wire support
Post by: posde on January 19, 2011, 05:57:41 pm
Thom,

just take a look at your packages list in web admin :p
Title: Re: 1wire support
Post by: hari on January 19, 2011, 06:46:15 pm
are there packages in the package database now for owfs/any other deps?

-Thom

no.. I was quite busy with the code and did not yet care to do that administrative task...

br Hari
Title: Re: 1wire support
Post by: DragonK on January 19, 2011, 07:18:10 pm
Stupid Question,

How do I get it on my core?

apt-get upgrade?

Karel
Title: Re: 1wire support
Post by: _if_ on January 19, 2011, 07:40:53 pm
I guess as long as there are no packages in the database we need to install owfs manually, right?
Title: Re: 1wire support
Post by: hari on January 19, 2011, 07:48:51 pm
yes, and after installing owfs, you need to do something like the following to compile the binary:
Code: [Select]
sudo -i
cd /usr/src/
svn co http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src LinuxMCE-0810/src
cp /usr/pluto/lib/* LinuxMCE-0810/src/lib
cd LinuxMCE-0810/src/OneWire
make bin
cp OneWire /usr/pluto/bin

br Hari
Title: Re: 1wire support
Post by: DragonK on January 19, 2011, 08:00:08 pm
Thanx Hari
Title: Re: 1wire support
Post by: DragonK on January 19, 2011, 10:31:51 pm
Hari,

I cant complete the install as per your instructions, I get stuck on the last step.
 
Code: [Select]
dcerouter_1011060:/usr/src/LinuxMCE-0810/src/OneWire# make bin
g++ -c -I.. -I../DCE -I/usr/include/mysql -DKDE_LMCE -DDEBUG -DTHREAD_LOG -DLOG_ALL_QUERIES -I/opt/owfs/include  -Wall -fPIC -ggdb3  Main.cpp -o Main.o
In file included from ../db_wrapper/db_wrapper.h:112,
                 from ../PlutoUtils/DBHelper.h:23,
                 from ../pluto_main/Database_pluto_main.h:3,
                 from ../pluto_main/Table_Device.h:21,
                 from ../DCE/DeviceData_Router.h:25,
                 from ../DCE/DCERouter.h:28,
                 from Main.cpp:18:
../db_wrapper/db_wrapper_mysql.h:7:25: error: mysql/mysql.h: No such file or directory
In file included from ../db_wrapper/db_wrapper.h:112,
                 from ../PlutoUtils/DBHelper.h:23,
                 from ../pluto_main/Database_pluto_main.h:3,
                 from ../pluto_main/Table_Device.h:21,
                 from ../DCE/DeviceData_Router.h:25,
                 from ../DCE/DCERouter.h:28,
                 from Main.cpp:18:
../db_wrapper/db_wrapper_mysql.h:17: error: expected constructor, destructor, or type conversion before â*â token
In file included from ../pluto_main/Database_pluto_main.h:3,
                 from ../pluto_main/Table_Device.h:21,
                 from ../DCE/DeviceData_Router.h:25,
                 from ../DCE/DCERouter.h:28,
                 from Main.cpp:18:
../PlutoUtils/DBHelper.h:36: error: ISO C++ forbids declaration of âMYSQL_RESâ with no type
../PlutoUtils/DBHelper.h:36: error: expected â;â before â*â token
../PlutoUtils/DBHelper.h: In constructor âPlutoSqlResult::PlutoSqlResult()â:
../PlutoUtils/DBHelper.h:37: error: class âPlutoSqlResultâ does not have any field named ârâ
../PlutoUtils/DBHelper.h: In member function âvoid PlutoSqlResult::ClearResults()â:
../PlutoUtils/DBHelper.h:44: error: ârâ was not declared in this scope
../PlutoUtils/DBHelper.h:46: error: âmysql_free_resultâ was not declared in this scope
../PlutoUtils/DBHelper.h: At global scope:
../PlutoUtils/DBHelper.h:64: error: ISO C++ forbids declaration of âMYSQLâ with no type
../PlutoUtils/DBHelper.h:64: error: expected â;â before â*â token
../PlutoUtils/DBHelper.h:164: error: âMYSQLâ has not been declared
../PlutoUtils/DBHelper.h:180: error: ISO C++ forbids declaration of âMYSQL_RESâ with no type
../PlutoUtils/DBHelper.h:180: error: expected â;â before â*â token
Main.cpp:253: error: expected `;' at end of input
Main.cpp:253: error: expected `}' at end of input
../PlutoUtils/DBHelper.h: In constructor âDBHelper::DBHelper()â:
../PlutoUtils/DBHelper.h:74: error: âm_pDBâ was not declared in this scope
../PlutoUtils/DBHelper.h: In constructor âDBHelper::DBHelper(std::string, std::string, std::string, std::string, int)â:
../PlutoUtils/DBHelper.h:97: error: âm_pDBâ was not declared in this scope
../PlutoUtils/DBHelper.h: In destructor âvirtual DBHelper::~DBHelper()â:
../PlutoUtils/DBHelper.h:111: error: âm_pDBâ was not declared in this scope
../PlutoUtils/DBHelper.h:112: error: âmysql_closeâ was not declared in this scope
../PlutoUtils/DBHelper.h:113: error: âm_pDBâ was not declared in this scope
../PlutoUtils/DBHelper.h: In member function âbool DBHelper::DBConnect(bool)â:
../PlutoUtils/DBHelper.h:133: error: âm_pDBâ was not declared in this scope
../PlutoUtils/DBHelper.h:137: error: âmysql_closeâ was not declared in this scope
../PlutoUtils/DBHelper.h:140: error: âm_pDBâ was not declared in this scope
../PlutoUtils/DBHelper.h:142: error: âdb_wrapper_initâ was not declared in this scope
../PlutoUtils/DBHelper.h:151: error: âm_pDBâ was not declared in this scope
../PlutoUtils/DBHelper.h:151: error: âmysql_real_connectâ was not declared in this scope
../PlutoUtils/DBHelper.h:154: error: âmysql_errorâ was not declared in this scope
../PlutoUtils/DBHelper.h: In member function âvoid DBHelper::SetConnection(int*)â:
../PlutoUtils/DBHelper.h:166: error: âm_pDBâ was not declared in this scope
../PlutoUtils/DBHelper.h: In member function âstd::string DBHelper::md5(std::string)â:
../PlutoUtils/DBHelper.h:173: error: âMYSQL_ROWâ was not declared in this scope
../PlutoUtils/DBHelper.h:173: error: expected `;' before ârowâ
../PlutoUtils/DBHelper.h:174: error: âclass PlutoSqlResultâ has no member named ârâ
../PlutoUtils/DBHelper.h:174: error: âdb_wrapper_query_resultâ was not declared in this scope
../PlutoUtils/DBHelper.h:174: error: ârowâ was not declared in this scope
../PlutoUtils/DBHelper.h:174: error: âclass PlutoSqlResultâ has no member named ârâ
../PlutoUtils/DBHelper.h:174: error: âmysql_fetch_rowâ was not declared in this scope
../PlutoUtils/DBHelper.h:177: error: ârowâ was not declared in this scope
../PlutoUtils/DBHelper.h: At global scope:
../PlutoUtils/DBHelper.h:178: error: expected unqualified-id at end of input
make: *** [Main.o] Error 1
dcerouter_1011060:/usr/src/LinuxMCE-0810/src/OneWire#

Thanx
Karel
Title: Re: 1wire support
Post by: hari on January 19, 2011, 10:54:10 pm
you need to install mysql devel headers (iirc "apt-get install libmysqlclient-dev" or something like that)

br Hari
Title: Re: 1wire support
Post by: DragonK on January 20, 2011, 05:20:36 am
you need to install mysql devel headers (iirc "apt-get install libmysqlclient-dev" or something like that)

br Hari

Thanx Hari.

That was it.
Title: Re: 1wire support
Post by: Kezza on January 20, 2011, 06:14:45 am
Hi DragonK, Can you update the wiki page once up and running with the instructions on how to get working and maybe list equipment etc? http://wiki.linuxmce.org/index.php/1-Wire

I've got some stuff on order from www.hobby-boards.com so should get that in the next few weeks and I can update also.


Cheers,
Title: Re: 1wire support
Post by: Techstyle on January 20, 2011, 06:31:05 am
Hari,

what was the adapter used to set up the template?  was it the RS232 or USB
Title: Re: 1wire support
Post by: _if_ on January 20, 2011, 07:02:01 am
it was USB...
Title: Re: 1wire support
Post by: hari on January 20, 2011, 02:04:16 pm
http://www.ibuttonlink.com/linkusb.aspx

any device working as serial device with owfs should work

br Hari
Title: Re: 1wire support
Post by: DragonK on January 20, 2011, 07:13:37 pm
Hi DragonK, Can you update the wiki page once up and running with the instructions on how to get working and maybe list equipment etc? http://wiki.linuxmce.org/index.php/1-Wire

I've got some stuff on order from www.hobby-boards.com so should get that in the next few weeks and I can update also.


Cheers,


Once im done I'll updatethe wiki, thats if you dont beat me to it. _IF_ is getting me the 1-wire interface and sensors. Cant get it in South Africa......  :(

Karel
Title: Re: 1wire support
Post by: Kezza on January 20, 2011, 08:55:53 pm
Once im done I'll updatethe wiki, thats if you dont beat me to it. _IF_ is getting me the 1-wire interface and sensors. Cant get it in South Africa......  :(

Karel

Ok thats cool had thought you already had the gear. Hobby-boards seem to ship worldwide by the looks of it and I presume there stuff is all good.
Title: Re: 1wire support
Post by: DragonK on January 20, 2011, 08:58:32 pm
Hari,

I cant choose the template... says "ERROR: the device template does not exist or invalid controlled via"
template number i chose was 2161

Karel
Title: Re: 1wire support
Post by: hari on January 20, 2011, 09:05:55 pm
from schema.linuxmce.org:
Code: [Select]
PK_DeviceTemplate_DeviceCategory_ControlledVia FK_DeviceTemplate FK_DeviceCategory Description RerouteMessagesToParent AutoCreateChildren psc_id psc_batch psc_user psc_frozen psc_mod psc_restrict
5167 2161 6 0 0 2200 3085 35987 0 2011-01-17 12:03:39

FK_DeviceCategory == 6 # Computers

that should be fine and the template does exist...

Did you sqlCVS update the whole DCE repository?

br Hari
Title: Re: 1wire support
Post by: DragonK on January 20, 2011, 09:13:29 pm
Thanx for ur patients with me Hari,

I did a sqlCVS update via the webadmin, and checked everything. But I dont think it did update, There wasnt much traffic on my router when i did it.....

Im I doing something wrong?

Karel
Title: Re: 1wire support
Post by: hari on January 20, 2011, 10:06:49 pm
just tested with rperre on irc (thanks), he was able to create a child device of the core.

br Hari
Title: Re: 1wire support
Post by: Techstyle on January 21, 2011, 02:15:28 am
I will try the version below at the weekend:

http://www.embeddeddatasystems.com/DS9490R--USB-to-1-Wire-iButton-Adapter_p_131.html (http://www.embeddeddatasystems.com/DS9490R--USB-to-1-Wire-iButton-Adapter_p_131.html)
Title: Re: 1wire support
Post by: Techstyle on January 21, 2011, 02:53:36 am
So how is everyone connecting the sensors up?

I had some old phone cords around but found that some have only 2 wires and some have 4 but none have the power (pin1) and Data (3) and Ground (4).  is everyone using parasitic power ie just 3 and 4?
Title: Re: 1wire support
Post by: posde on January 21, 2011, 09:09:41 am
I did a sqlCVS update via the webadmin, and checked everything.

Did you select all repos, or did you select all tables within dce? Make sure to not do the former, but only the latter
Title: Re: 1wire support
Post by: DragonK on January 21, 2011, 05:59:16 pm
Posde,

Is this correct? It seems to take longer now.
This time only chose dce.

Karel

Edit: What should the default username and password be?
Mine is "anonymous" and "nopass"
Title: Re: 1wire support
Post by: posde on January 21, 2011, 07:02:20 pm
username and password are irrelevant and stay the same. They are only relevant from your system to sqlCVS, not for the other way round.
Title: Re: 1wire support
Post by: Techstyle on January 22, 2011, 06:48:38 pm
Hari,

I am struggling a little getting this to work but I have written down everything I did as I was going to update the Wiki page, here goes:

1. install this package: 'sudo apt-get install libmysqlclient-dev'
You may receive the following message:

"Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package libmysqlclient-dev is a virtual package provided by:
  libmysqlclientXX-dev 5.0.67-0ubuntu6.1
You should explicitly select one to install.
E: Package libmysqlclient-dev has no installation candidate"

if you do receive this message the re-run the command replacing the your original command with the start of line 4 of the message, for example: 'sudo apt-get install libmysqlclientXX-dev'

2. go to http://sourceforge.net/projects/owfs/files/owfs and find out what the latest package is, for me that was 'owfs-2.8p5.tar.gz' in directory 'http://sourceforge.net/projects/owfs/files/owfs/2.8p5/' (i.e. http://sourceforge.net/projects/owfs/files/owfs/2.8p5/owfs-2.8p5.tar.gz - we will use this later) I will use http://sourceforge.net/projects/owfs/files/owfs/XXXXX/owfs-XXXXX.tar.gz in the steps.

2. follow the code below, you may have to have root privileges so use 'sudo' in front of the follow code:

Code: [Select]
cd /usr/src
wget http://sourceforge.net/projects/owfs/files/owfs/XXXXX/owfs-XXXXX.tar.gz
tar zxpf owfs-XXXXX.tar.gz
cd owfs-XXXXX
./configure
make
make install

(from Hari's post in the forum - http://forum.linuxmce.org/index.php?topic=11328.0)
Code: [Select]
sudo -i
cd /usr/src/
svn co http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src LinuxMCE-0810/src
cp /usr/pluto/lib/* LinuxMCE-0810/src/lib
cd LinuxMCE-0810/src/OneWire
make bin


I get some errors at this point:

Code: [Select]
Computing dependencies for ../Gen_Devices/OneWireBase.cpp done
Computing dependencies for OneWire.cpp done
Computing dependencies for Main.cpp done
g++ -c -I.. -I../DCE -I/usr/include/mysql -DKDE_LMCE -DDEBUG -DTHREAD_LOG -DLOG_ALL_QUERIES -I/opt/owfs/include  -Wall -fPIC -ggdb3  Main.cpp -o Main.o
g++ -c -I.. -I../DCE -I/usr/include/mysql -DKDE_LMCE -DDEBUG -DTHREAD_LOG -DLOG_ALL_QUERIES -I/opt/owfs/include  -Wall -fPIC -ggdb3  OneWire.cpp -o OneWire.o
OneWire.cpp:26:21: error: owcapi.h: No such file or directory
OneWire.cpp: In member function ‘virtual bool DCE::OneWire::GetConfig()’:
OneWire.cpp:74: error: ‘OW_init’ was not declared in this scope
OneWire.cpp: In member function ‘virtual void DCE::OneWire::readDevices()’:
OneWire.cpp:243: error: ‘OW_get’ was not declared in this scope
make: *** [OneWire.o] Error 1

Any ideas what went wrong?
Title: Re: 1wire support
Post by: tschak909 on January 22, 2011, 06:50:01 pm
OWFS was not properly installed. You need to make sure it's compiled and installed.

-Thom
Title: Re: 1wire support
Post by: Techstyle on January 22, 2011, 07:23:50 pm
where should it be installed to?

do I have the directories correct or am I missing a step?
Title: Re: 1wire support
Post by: Techstyle on January 22, 2011, 07:31:59 pm
after running the ./configure step I get the following:

Code: [Select]
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?

Title: Re: 1wire support
Post by: Techstyle on January 22, 2011, 07:34:24 pm
when I run 'make' I get the following at the end:

Code: [Select]
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?
Title: Re: 1wire support
Post by: hari on January 22, 2011, 10:10:40 pm
Techstyle, you also need to do a "echo /opt/owfs/lib > /etc/ld.so.conf.d/owfs.conf", followed by a "ldconfig -X"
Title: Re: 1wire support
Post by: Techstyle on January 23, 2011, 12:38:02 am
Hari,

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

Quote
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
Title: Re: 1wire support
Post by: DragonK on January 23, 2011, 07:30:10 am
after running the ./configure step I get the following:

Code: [Select]
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: [Select]
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
Title: Re: 1wire support
Post by: hari on January 23, 2011, 12:17:03 pm
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

Title: Re: 1wire support
Post by: RayBe on January 23, 2011, 04:11:34 pm
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
Title: Re: 1wire support
Post by: _if_ on February 23, 2011, 05:51:10 pm
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?
Title: Re: 1wire support
Post by: Kezza 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.


Title: Re: 1wire support
Post by: _if_ on February 23, 2011, 10:18:39 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
Title: Re: 1wire support
Post by: Kezza 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 ;)
Title: Re: 1wire support
Post by: _if_ on February 23, 2011, 10:34:34 pm
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.
Title: Re: 1wire support
Post by: Kezza 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.
Title: Re: 1wire support
Post by: Techstyle on February 24, 2011, 05:29:18 am
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
Title: Re: 1wire support
Post by: DragonK on February 24, 2011, 07:01:27 am
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.

Hi,

Pls post output of lsusb

Karel
Title: Re: 1wire support
Post by: _if_ on February 24, 2011, 04:15:27 pm
@dcerouter:~$ lsusb
Bus 004 Device 004: ID 0bc7:0001 X10 Wireless Technology, Inc. ActiveHome (ACPI-compliant)
Bus 004 Device 002: ID 0b95:7720 ASIX Electronics Corp. AX88772
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


thanks
IF
Title: Re: 1wire support
Post by: DragonK on February 24, 2011, 08:18:13 pm
Sorry,

dmesg to pls.
Wat else do you have connected to te usb, because that might influence wich USB device the 1-wire interface would be.
It might be /dev/ttyUSB1 or /dev/ttyUSB2.

Hari pls correct me if I'm wrong.

Karel
Title: Re: 1wire support
Post by: _if_ on February 24, 2011, 10:57:17 pm
in my case its on ttyUSB0, here is a part of dmesg:

[   21.217743] ftdi_sio 3-2:1.0: FTDI USB Serial Device converter detected
[   21.217832] ftdi_sio: Detected FT232RL
[   21.218131] usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB0

do you want to see the whole dmesg?

on USB ports I got X10 interface, second NIC and the 1-wire interface...
Title: Re: 1wire support
Post by: Techstyle on February 25, 2011, 03:12:20 am
Are people using DS9490R?

If so, this may be causing the issue
http://owfs.org/index.php?page=usb-ds9490r (http://owfs.org/index.php?page=usb-ds9490r)

This is the device I am using
Title: Re: 1wire support
Post by: _if_ on February 25, 2011, 06:39:09 am
Hi,

the interface uses DS9097U...

thanks
IF
Title: Re: 1wire support
Post by: Kezza 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
Title: Re: 1wire support
Post by: hari on February 26, 2011, 02:59:04 pm
do a "echo /opt/owfs/lib > /etc/ld.so.conf.d/owfs.conf", followed by a "ldconfig -X"
Title: Re: 1wire support
Post by: Kezza 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#
Title: Re: 1wire support
Post by: _if_ on February 26, 2011, 09:21:09 pm
I believe owfs should be existing and running, is that right Hari?
Title: Re: 1wire support
Post by: hari on February 27, 2011, 12:48:40 am
I believe owfs should be existing and running, is that right Hari?
you don't need to mount owfs
Title: Re: 1wire support
Post by: _if_ on February 27, 2011, 10:38:11 am
ok thanks, and how would I find out the sensors ID then?
Title: Re: 1wire support
Post by: Kezza 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 (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.
Title: Re: 1wire support
Post by: _if_ on February 27, 2011, 02:39:08 pm
had no success on the windows pc and on my xubuntu desktop as well  :(
can install and run owfs on xubuntu fine but no sensors showing up...maybe I really need to replace the interface
Title: Re: 1wire support
Post by: _if_ on February 27, 2011, 03:17:01 pm
just found out I got a problem with libc-2.8.90.so on my core, any ideas what that means? I don't think that was showing up before...

dmesg:
[17035.150677] ftdi_sio 3-2:1.0: FTDI USB Serial Device converter detected
[17035.151071] ftdi_sio: Detected FT232RL
[17035.151800] usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB0
[17060.090978] OneWire[20769]: segfault at 0 ip b71fa323 sp b7070e4c error 4 in libc-2.8.90.so[b7183000+158000]
Title: Re: 1wire support
Post by: hari on February 27, 2011, 07:06:21 pm
please compile the latest svn revision and try again
Title: Re: 1wire support
Post by: _if_ on February 27, 2011, 07:40:28 pm
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]
[  155.417211] OneWire[21861]: segfault at 0 ip b72bd323 sp b7137e4c error 4 in libc-2.8.90.so[b7246000+158000]
[  166.583748] OneWire[22192]: segfault at 0 ip b719d323 sp b7017e4c error 4 in libc-2.8.90.so[b7126000+158000]
[  177.736162] OneWire[22794]: segfault at 0 ip b71de323 sp b7058e4c error 4 in libc-2.8.90.so[b7167000+158000]
[  188.896788] OneWire[22964]: segfault at 0 ip b724c323 sp b70c6e4c error 4 in libc-2.8.90.so[b71d5000+158000]
[  200.015275] OneWire[23148]: segfault at 0 ip b7208323 sp b7082e4c error 4 in libc-2.8.90.so[b7191000+158000]
[  211.115800] OneWire[23354]: segfault at 0 ip b72bb323 sp b7135e4c error 4 in libc-2.8.90.so[b7244000+158000]
[  222.264434] OneWire[23530]: segfault at 0 ip b72d6323 sp b7150e4c error 4 in libc-2.8.90.so[b725f000+158000]
[  233.422038] OneWire[24353]: segfault at 0 ip b72d3323 sp b714de4c error 4 in libc-2.8.90.so[b725c000+158000]
[  244.654483] OneWire[25316]: segfault at 0 ip b72e6323 sp b7160e4c error 4 in libc-2.8.90.so[b726f000+158000]
[  255.767390] OneWire[25557]: segfault at 0 ip b71c2323 sp b703ce4c error 4 in libc-2.8.90.so[b714b000+158000]
[  266.864594] OneWire[25742]: segfault at 0 ip b71cc323 sp b7046e4c error 4 in libc-2.8.90.so[b7155000+158000]
[  277.979072] OneWire[25929]: segfault at 0 ip b7253323 sp b70cde4c error 4 in libc-2.8.90.so[b71dc000+158000]
[  289.080605] OneWire[26137]: segfault at 0 ip b72fb323 sp b7175e4c error 4 in libc-2.8.90.so[b7284000+158000]
[  300.169165] OneWire[26297]: segfault at 0 ip b7300323 sp b717ae4c error 4 in libc-2.8.90.so[b7289000+158000]
[  311.268674] OneWire[26475]: segfault at 0 ip b7216323 sp b7090e4c error 4 in libc-2.8.90.so[b719f000+158000]
[  322.379194] OneWire[26645]: segfault at 0 ip b72c4323 sp b713ee4c error 4 in libc-2.8.90.so[b724d000+158000]
[  333.496761] OneWire[26850]: segfault at 0 ip b723b323 sp b70b5e4c error 4 in libc-2.8.90.so[b71c4000+158000]
[  344.619316] OneWire[27011]: segfault at 0 ip b7314323 sp b718ee4c error 4 in libc-2.8.90.so[b729d000+158000]
[  355.801843] OneWire[28178]: segfault at 0 ip b72c7323 sp b7141e4c error 4 in libc-2.8.90.so[b7250000+158000]
[  366.915373] OneWire[28629]: segfault at 0 ip b721e323 sp b7098e4c error 4 in libc-2.8.90.so[b71a7000+158000]
[  378.030907] OneWire[28791]: segfault at 0 ip b7357323 sp b71d1e4c error 4 in libc-2.8.90.so[b72e0000+158000]
[  389.170462] OneWire[29011]: segfault at 0 ip b7233323 sp b70ade4c error 4 in libc-2.8.90.so[b71bc000+158000]
[  400.534971] OneWire[29290]: segfault at 0 ip b7179323 sp b6ff3e4c error 4 in libc-2.8.90.so[b7102000+158000]
[  411.729500] OneWire[29647]: segfault at 0 ip b71ef323 sp b7069e4c error 4 in libc-2.8.90.so[b7178000+158000]
[  422.921379] OneWire[30104]: segfault at 0 ip b72a1323 sp b711be4c error 4 in libc-2.8.90.so[b722a000+158000]
[  434.044746] OneWire[30352]: segfault at 0 ip b72ce323 sp b7148e4c error 4 in libc-2.8.90.so[b7257000+158000]
[  445.240279] OneWire[30611]: segfault at 0 ip b7260323 sp b70dae4c error 4 in libc-2.8.90.so[b71e9000+158000]
[  456.391669] OneWire[31094]: segfault at 0 ip b7256323 sp b70d0e4c error 4 in libc-2.8.90.so[b71df000+158000]
[  467.521314] OneWire[32242]: segfault at 0 ip b735b323 sp b71d5e4c error 4 in libc-2.8.90.so[b72e4000+158000]
[  478.689709] OneWire[326]: segfault at 0 ip b72e9323 sp b7163e4c error 4 in libc-2.8.90.so[b7272000+158000]
[  489.796268] OneWire[489]: segfault at 0 ip b720f323 sp b7089e4c error 4 in libc-2.8.90.so[b7198000+158000]
[  500.891839] OneWire[650]: segfault at 0 ip b7175323 sp b6fefe4c error 4 in libc-2.8.90.so[b70fe000+158000]
[  512.008326] OneWire[838]: segfault at 0 ip b7236323 sp b70b0e4c error 4 in libc-2.8.90.so[b71bf000+158000]
[  523.099885] OneWire[1039]: segfault at 0 ip b7210323 sp b708ae4c error 4 in libc-2.8.90.so[b7199000+158000]
[  534.232441] OneWire[1223]: segfault at 0 ip b72c3323 sp b713de4c error 4 in libc-2.8.90.so[b724c000+158000]
[  545.323930] OneWire[1411]: segfault at 0 ip b7239323 sp b70b3e4c error 4 in libc-2.8.90.so[b71c2000+158000]
[  556.431497] OneWire[1572]: segfault at 0 ip b727e323 sp b70f8e4c error 4 in libc-2.8.90.so[b7207000+158000]
[  567.522035] OneWire[1739]: segfault at 0 ip b7201323 sp b707be4c error 4 in libc-2.8.90.so[b718a000+158000]
[  578.621578] OneWire[1927]: segfault at 0 ip b71d5323 sp b704fe4c error 4 in libc-2.8.90.so[b715e000+158000]
[  589.747242] OneWire[2133]: segfault at 0 ip b720d323 sp b7087e4c error 4 in libc-2.8.90.so[b7196000+158000]
[  600.907646] OneWire[3418]: segfault at 0 ip b71e5323 sp b705fe4c error 4 in libc-2.8.90.so[b716e000+158000]
[  612.028185] OneWire[4292]: segfault at 0 ip b732f323 sp b71a9e4c error 4 in libc-2.8.90.so[b72b8000+158000]
[  623.116735] OneWire[4471]: segfault at 0 ip b735f323 sp b71d9e4c error 4 in libc-2.8.90.so[b72e8000+158000]
[  634.196299] OneWire[4661]: segfault at 0 ip b72ad323 sp b7127e4c error 4 in libc-2.8.90.so[b7236000+158000]
[  645.281903] OneWire[4867]: segfault at 0 ip b7315323 sp b718fe4c error 4 in libc-2.8.90.so[b729e000+158000]
[  656.401358] OneWire[5029]: segfault at 0 ip b71cd323 sp b7047e4c error 4 in libc-2.8.90.so[b7156000+158000]
[  667.496873] OneWire[5191]: segfault at 0 ip b7181323 sp b6ffbe4c error 4 in libc-2.8.90.so[b710a000+158000]
[  678.611474] OneWire[5360]: segfault at 0 ip b72b7323 sp b7131e4c error 4 in libc-2.8.90.so[b7240000+158000]
[  689.728992] OneWire[5577]: segfault at 0 ip b7283323 sp b70fde4c error 4 in libc-2.8.90.so[b720c000+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)
Title: Re: 1wire support
Post by: Kezza 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
Title: Re: 1wire support
Post by: DragonK on February 28, 2011, 07:50:11 am
Guys,

As far as I can see from the thread this would be the steps for the 1-wire support. I unfortuanately dont have an interface unit.

1.Do a sqlCVS update from the webadmin. Select only tables within DCE.
Did you select all repos, or did you select all tables within dce? Make sure to not do the former, but only the latter


2.Install mysql devel headers
you need to install mysql devel headers (iirc "apt-get install libmysqlclient-dev" or something like that)

br Hari


3.Install OWFS. These are the steps I used, Maybe TEchstyle can post his steps. Or Hari could you point us to the correct steps of installing OWFS.
http://www.mail-archive.com/owfs-developers@lists.sourceforge.net/msg04821.html

4.Compile OneWire Binary
yes, and after installing owfs, you need to do something like the following to compile the binary:
Code: [Select]
sudo -i
cd /usr/src/
svn co http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src LinuxMCE-0810/src
cp /usr/pluto/lib/* LinuxMCE-0810/src/lib
cd LinuxMCE-0810/src/OneWire
make bin
cp OneWire /usr/pluto/bin

br Hari


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

6. Add the sensor in webadmin. We still need to confirm, where to retrieve the sensor's ID from.
Hi Folks,

I did write a DCE device for the owfs 1wire driver. Device Template #2161. The code is here: http://svn.linuxmce.org/trac.cgi/browser/branches/LinuxMCE-0810/src/OneWire/

Just create "Multilevel Sensor" Childs and put the 1wire ID into the port/channel field. The DCE device will store the last measurement and only send events when things have changed. Only temperature sensors supported atm:

35   01/19/11 11:11:30.628      Temperature for 28.B3795602000: 25.62 <0xb78c9b70>
35   01/19/11 11:11:30.628      Old temperature for 28.B3795602000: 25.56 <0xb78c9b70>
07   01/19/11 11:11:30.629      Received Message from 233 (1wire temp / ) to -1001 (unknown / ), type 2 id 25 Event:Temperature Changed, retry none, parameters: <0xb2cfdb70>
07   01/19/11 11:11:30.629        Parameter 30(Value): 25.62 <0xb2cfdb70>

br Hari

Anyone feel free to add to this or change anything accordingly. Once we get the installation procedure correct, I'll update the Wiki.

Karel
Title: Re: 1wire support
Post by: hari on February 28, 2011, 03:37:45 pm
no luck, I now have tons of:
...

can I get ssh access to your system?

br Hari
Title: Re: 1wire support
Post by: _if_ on February 28, 2011, 04:17:24 pm
jep, will set it up as soon as I get home...
Title: Re: 1wire support
Post by: _if_ on February 28, 2011, 08:01:34 pm
should remote ssh be working at the moment? If I try to enable it, the webadminpage starts loading but never stops...
Title: Re: 1wire support
Post by: hari on February 28, 2011, 08:25:53 pm
does not work atm
Title: Re: 1wire support
Post by: _if_ on March 02, 2011, 10:47:33 pm
does not work atm

do you have any advice what I can try until remote ssh is working again?
Title: Re: 1wire support
Post by: hari on March 02, 2011, 11:36:22 pm
regular ssh?
Title: Re: 1wire support
Post by: _if_ on March 03, 2011, 05:59:04 pm
regular ssh is set up, you got mail!
Title: Re: 1wire support
Post by: hari on March 03, 2011, 09:10:46 pm
there is some problem with your interface. What exact kind is it?

I've added some more error handling to the code:

Code: [Select]
DEBUG: ow_parseobject.c:OWQ_create(160) /
   CALL: ow_parsename.c:FS_ParsedName_anywhere(91) path=[/]
  DEBUG: ow_dir.c:FS_dir(63) path=/
   CALL: ow_dir.c:FS_dir_both(98) path=/
  DEBUG: ow_cache.c:Cache_Get_Dir(805) Looking for directory 00 00 00 00 00 00 00 00
  DEBUG: ow_cache.c:Cache_Get_Common_Dir(818) Get from cache sn 00 00 00 00 00 00 00 00 pointer=0xb710fdd4 extension=0
  DEBUG: ow_cache.c:Cache_Get_Common_Dir(847) Dir not found in cache
  DEBUG: ow_search.c:BUS_first(32) Start of directory path=/ device=00 00 00 00 00 00 00 00
  DEBUG: ow_select.c:BUS_select(78) Selecting a path (and device) path=/ SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00
  DEBUG: ow_select.c:BUS_select(86) Continuing root branch
  DEBUG: ow_tcp_read.c:tcp_read(64) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:tcp_read(114) read: 1 - 0 = 1
CONNECT: ow_reset.c:BUS_reset(36) 1-wire bus short circuit.
  DEBUG: ow_tcp_read.c:tcp_read(64) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:tcp_read(114) read: 1 - 0 = 1
  DEBUG: ow_bus_data.c:BUS_send_data(38) Response doesn't match data sent
  DEBUG: ow_select.c:BUS_select(78) Selecting a path (and device) path=/ SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00
  DEBUG: ow_select.c:BUS_select(86) Continuing root branch
  DEBUG: ow_tcp_read.c:tcp_read(64) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:tcp_read(114) read: 1 - 0 = 1
CONNECT: ow_reset.c:BUS_reset(36) 1-wire bus short circuit.
  DEBUG: ow_tcp_read.c:tcp_read(64) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:tcp_read(114) read: 1 - 0 = 1
  DEBUG: ow_bus_data.c:BUS_send_data(38) Response doesn't match data sent
  DEBUG: ow_select.c:BUS_select(78) Selecting a path (and device) path=/ SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00
  DEBUG: ow_select.c:BUS_select(86) Continuing root branch
  DEBUG: ow_tcp_read.c:tcp_read(64) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:tcp_read(114) read: 1 - 0 = 1
CONNECT: ow_reset.c:BUS_reset(36) 1-wire bus short circuit.
  DEBUG: ow_tcp_read.c:tcp_read(64) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:tcp_read(114) read: 1 - 0 = 1
  DEBUG: ow_bus_data.c:BUS_send_data(38) Response doesn't match data sent
   CALL: ow_parsename.c:FS_ParsedName_anywhere(91) path=[/bus.0]
  DEBUG: ow_parsename.c:FS_ParsedName_destroy(55) /bus.0
   CALL: ow_parsename.c:FS_ParsedName_anywhere(91) path=[/uncached]
  DEBUG: ow_parsename.c:FS_ParsedName_destroy(55) /uncached
   CALL: ow_parsename.c:FS_ParsedName_anywhere(91) path=[/settings]
  DEBUG: ow_parsename.c:FS_ParsedName_destroy(55) /settings
   CALL: ow_parsename.c:FS_ParsedName_anywhere(91) path=[/system]
  DEBUG: ow_parsename.c:FS_ParsedName_destroy(55) /system
   CALL: ow_parsename.c:FS_ParsedName_anywhere(91) path=[/statistics]
  DEBUG: ow_parsename.c:FS_ParsedName_destroy(55) /statistics
   CALL: ow_parsename.c:FS_ParsedName_anywhere(91) path=[/structure]
  DEBUG: ow_parsename.c:FS_ParsedName_destroy(55) /structure
  DEBUG: ow_dir.c:FS_dir_both(193) ret=-5
  DEBUG: ow_parsename.c:FS_ParsedName_destroy(55) /
01 03/03/11 21:08:33.364 OW_get error: 22 <0xb7061b90>
please note the BUS_send_data error, after that the OW_get call returns errno 22...

br Hari
Title: Re: 1wire support
Post by: hari on March 03, 2011, 09:26:28 pm
I've tried owfs and get the same problem. You need to make sure that your interface runs nice with owfs before trying the OneWire LinuxMCE driver.

br Hari
Title: Re: 1wire support
Post by: _if_ on March 03, 2011, 09:26:59 pm
it's the totally same interface as I send to you...
Title: Re: 1wire support
Post by: hari on March 03, 2011, 09:42:35 pm
weird...

did you connect a temp sensor?
Title: Re: 1wire support
Post by: _if_ on March 03, 2011, 10:01:59 pm
yes it's connected.
I have the blue wire at the middle pin (data) and the blue/white at the other 2 pins of the sensor, should be right?
Title: Re: 1wire support
Post by: _if_ on March 05, 2011, 11:28:24 am
arg, I found the problem: there was a little little assholewire in the lanjack which connected the 2 wires together...I put a new jack on it and I can now mount owfs perfectly and read the sensors value.

Altough if I run ./OneWire I still get:

./OneWire
OneWire, v.<=version=>
Visit www.plutohome.com for source code and license information

01   03/05/11 11:24:55.323      Opening port: ERR Parameter not found <0xb70356c0>
DEFAULT: owlib.c:LibStart(54) No valid 1-wire buses found
01   03/05/11 11:24:55.328      OW_init error: 22, Invalid argument <0xb70356c0>
01   03/05/11 11:24:55.328      Connect() Failed <0xb70356c0>


I also entered the sensors ID at webadmin to the multilevelsensor, but no value is shown in the orbiter - just the tempsymbol...
Title: Re: 1wire support
Post by: Kezza 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.
Title: Re: 1wire support
Post by: _if_ on March 05, 2011, 12:15:38 pm
the log has an error at: Opening port: /dev/ttyUSB0 <0xb717d6c0>
my ID starts with '28.'
At my cores usb ports I have only: 2nd nic, X10 Interface, and the 1-wire interface.
Title: Re: 1wire support
Post by: _if_ on March 06, 2011, 08:09:43 pm
it's working! big thanks to hari!!

(http://s3.directupload.net/images/110306/temp/7ibhtcby.png) (http://s3.directupload.net/file/d/2455/7ibhtcby_png.htm)

is this cool or what?
Title: Re: 1wire support
Post by: Kezza on March 06, 2011, 09:15:19 pm
Wow that looks very cool.

Anything in particular you had to do to get it working?
Title: Re: 1wire support
Post by: _if_ on March 06, 2011, 09:51:45 pm
well not really, the big problem was the short circuit in my jack.
all other things were like unexplainable things and solved themselves  ;D

oh and the value in my floorplan did not came up until I added a new respond event (not shure if those 2 things are really related...)

Next things to check: why my respond events are not responding at the moment and I will try to get datalogger running the next few days to check if logging works as well...
Title: Re: 1wire support
Post by: Kezza 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>
Title: Re: 1wire support
Post by: hari on March 11, 2011, 02:22:00 pm
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>

first, do a quick reload

2nd, make sure that you can read out the sensors with owfs.

br Hari
Title: Re: 1wire support
Post by: hari on March 11, 2011, 06:34:19 pm
3rd, get the latest svn version, it spits out more debug information

br Hari
Title: Re: 1wire support
Post by: _if_ on March 12, 2011, 08:55:02 pm
just to add: I added a second sensor today and the new 'auto sensor recognition' feature works really well.

Connect the sensor, quick reload, a new multilevelsensor device is created, you enter the sensors ID (you get it out of the interface log), quick reload. After that you can place the new sensor in your floorplan. That's it!
Title: Re: 1wire support
Post by: Techstyle on March 12, 2011, 11:07:25 pm
So as this support increases what are the steps now needed to get this to work?
Title: Re: 1wire support
Post by: _if_ on March 13, 2011, 02:44:46 pm
I think the steps on post #63 from DragonK should be enough, do you run into any problems?
Title: Re: 1wire support
Post by: Techstyle on March 13, 2011, 06:49:11 pm
I originally had problems but have reinstalled since so I am effectively starting from scratch
Title: Re: 1wire support
Post by: _if_ on March 13, 2011, 07:08:41 pm
that is cool, so we can check if that description works and we can put a wiki page together...
Title: Re: 1wire support
Post by: hari on March 13, 2011, 07:17:52 pm
just to add: I added a second sensor today and the new 'auto sensor recognition' feature works really well.

Connect the sensor, quick reload, a new multilevelsensor device is created, you enter the sensors ID (you get it out of the interface log), quick reload. After that you can place the new sensor in your floorplan. That's it!

it does not put the sensor id in the port/channel field automatically?

br Hari
Title: Re: 1wire support
Post by: _if_ on March 13, 2011, 07:25:48 pm
I will add a third sensor and check again...
Title: Re: 1wire support
Post by: _if_ on March 13, 2011, 07:41:20 pm
nope: ID, ObjectType and room are empty...
Title: Re: 1wire support
Post by: hari on March 13, 2011, 11:14:06 pm
nope: ID, ObjectType and room are empty...
then we have a bug, the ID should be filled in automatically..
Title: Re: 1wire support
Post by: Techstyle on March 13, 2011, 11:37:04 pm
I just destroyed my install while trying to set up owfs.  I think those instructions need some work
Title: Re: 1wire support
Post by: tschak909 on March 14, 2011, 04:27:27 am
Guys, why haven't we worked towards putting this in as part of the build? to get owfs packages, and the 1Wire device, put them into the Package database, so that the system can automatically deal with it?

come on, guys...

-Thom
Title: Re: 1wire support
Post by: hari on March 14, 2011, 03:08:14 pm
come on tschak, I did ask in the devel channel how to add an external package to our over-engineered build system.. nobody knows..

My part was the code, I have no time right now to fiddle with packages.

br Hari
Title: Re: 1wire support
Post by: hari on March 14, 2011, 03:09:19 pm
I just destroyed my install while trying to set up owfs.  I think those instructions need some work
I think you should provide more details what the hack you were doing..
Title: Re: 1wire support
Post by: Techstyle on March 14, 2011, 09:28:27 pm
while trying to install OWFS i was following the instructions:

http://www.mail-archive.com/owfs-developers@lists.sourceforge.net/msg04821.html (http://www.mail-archive.com/owfs-developers@lists.sourceforge.net/msg04821.html)

specifically:

Code: [Select]
sudo apt-get install cvs autoconf automake libtool libfuse-dev libusb-dev swig php5 php5-dev php5-cli python-dev libperl-dev tcl-dev
Which casue some dependency issues which were not resolved, I asked some questions in the irc channel and did some Googling that made me do something stupid which ultimately killed my install.

I will give exact issues later when I get back to my irc client
Title: Re: 1wire support
Post by: hari on March 15, 2011, 12:27:24 am
thanks possy for taking care of the packaging!

Guys be patient, proper OneWire and libowfs packages will be available very soon.

br Hari
Title: Re: 1wire support
Post by: Techstyle on March 15, 2011, 12:50:38 am
No Problem, I will wait.  Just let me know if you want me to test anything

Thanks for all your work
Title: Re: 1wire support
Post by: hari on March 15, 2011, 07:09:47 pm
nope: ID, ObjectType and room are empty...
should be fixed now, please checkout rev 23832 and test again

br Hari
Title: Re: 1wire support
Post by: _if_ on March 15, 2011, 07:34:40 pm
should be fixed now, please checkout rev 23832 and test again

br Hari

update is working! only room and objtype needs to be filled in manually now. Thanks!
Title: Re: 1wire support
Post by: Zaerc on March 21, 2011, 12:29:14 am
off-topic posts removed by moderator - Hari
Title: Re: 1wire support
Post by: uplink on March 21, 2011, 09:58:54 am
That depends, are you going to keep pretending that you're retarded?

Zaerc, this time around you're digging yourself a big hole on your own. I wonder what you'll do to yourself when you're the one who screwed you over.
Title: Re: 1wire support
Post by: hari on March 21, 2011, 10:09:07 am
thanks to possy we have working 1004 packages for owfs and the OneWire DCE device. 0810 will follow soon.

br Hari
Title: Re: 1wire support
Post by: _if_ on March 21, 2011, 10:52:07 pm
Hari, did you ever look into which event parameter is needed for 'respond events'?

thanx
IF
Title: Re: 1wire support
Post by: tschak909 on March 22, 2011, 05:53:00 am
you mean, what's required to get your custom event to show up in the wizard > Respond to Events?

-Thom
Title: Re: 1wire support
Post by: hari on March 22, 2011, 08:15:47 pm
the device emits temperature changed events

br hari
Title: Re: 1wire support
Post by: _if_ on March 22, 2011, 09:01:28 pm
I can't choose "temperature changed" events in wizard > respond to event...should that be there?
Title: Re: 1wire support
Post by: hari on March 23, 2011, 07:22:40 pm
Any idea what this means?

Code: [Select]
01 03/11/11 16:41:59.189 OW_get error: 22, Invalid argument <0xb71a2b90>
an OW_get error 22 means that there is no sensor available. You need to properly attach a 1wire sensor to the interface.

br Hari
Title: Re: 1wire support
Post by: Kezza on March 25, 2011, 10:09:14 pm
Hi Hari,

Reading through the code in svn and noticed it's looking for family code "28." for your temp sensors but mine is "10." http://owfs.sourceforge.net/family.html

Could this be why I'm getting the error?

For future devices, is this the only section of code that gets modified?.... just trying to learn how these template work.

Cheers,

Title: Re: 1wire support
Post by: hari on March 26, 2011, 12:03:12 am
Hi Hari,

Reading through the code in svn and noticed it's looking for family code "28." for your temp sensors but mine is "10." http://owfs.sourceforge.net/family.html
ok, I will add them

Quote
Could this be why I'm getting the error?
no, the OW_get error means that owfs cannot see any devices

Quote
For future devices, is this the only section of code that gets modified?.... just trying to learn how these template work.
for reading out sensors, yes. We need a bit more code if we want to control devices, too.

br Hari
Title: Re: 1wire support
Post by: hari on March 26, 2011, 06:52:58 pm
http://svn.linuxmce.org/trac.cgi/changeset/23856
Title: Re: 1wire support
Post by: twodogs on March 29, 2011, 05:27:14 am
I'd like to join this party and get my temp sensor working. After some initial problems with getting OWFS to install, I think I'm close. However, the 1wire device only lists ttyS0 and ttyS1 for ports and I have a USB temp sensor. Also, I don't see a way to create a multilevel sensor child.

John
Title: Re: 1wire support
Post by: Kezza on March 31, 2011, 06:29:18 am

Thanks Hari,

Any idea why the log is not being created on my machine? This is on 1004 I had not problems on 810.

Whats the status with 810 packages?

Cheers,
Title: Re: 1wire support
Post by: hari on March 31, 2011, 07:08:19 pm
I'd like to join this party and get my temp sensor working. After some initial problems with getting OWFS to install, I think I'm close. However, the 1wire device only lists ttyS0 and ttyS1 for ports and I have a USB temp sensor. Also, I don't see a way to create a multilevel sensor child.

John
the child is created automatically.

only serial devices are supported right now (or devices with built in serial/usb adapter)
Title: Re: 1wire support
Post by: twodogs on April 01, 2011, 03:24:19 pm
OK, but just so I don't make a mistake, I need to stop trying to use the DS9490R-A...

(http://img577.imageshack.us/img577/1159/ds9490ra.jpg) (http://img577.imageshack.us/i/ds9490ra.jpg/)

and buy a DS9097U-A...

(http://img88.imageshack.us/img88/7443/ds9097ua.jpg) (http://img88.imageshack.us/i/ds9097ua.jpg/)

Is that what everyone is using to connect their 1-wire network to the core?
Title: Re: 1wire support
Post by: Techstyle on April 01, 2011, 04:48:34 pm
I also have the DS9490R and have not been able to get it to work
Title: Re: 1wire support
Post by: Kezza on April 03, 2011, 02:30:25 am
hmm that might explain why mine has never worked on LMCE but flawless in windows.
Title: Re: 1wire support
Post by: twodogs on April 03, 2011, 03:02:16 am
I'm looking for a serial adapter and I'm finding a variety from $12-$65. Is the Hobby Boards adapter pictured above the best choice or is their another part number I should get?

John
Title: Re: 1wire support
Post by: hari on April 03, 2011, 08:34:45 pm
hmm that might explain why mine has never worked on LMCE but flawless in windows.
is it supported by owfs at all? Is it supported by owfs as serial device?
Title: Re: 1wire support
Post by: hari on April 03, 2011, 08:35:44 pm
This one works fine: http://www.ibuttonlink.com/linkusb.aspx
Title: Re: 1wire support
Post by: Techstyle on April 03, 2011, 08:48:47 pm
Hari,

Are we saying that we should replace our DS9490R's with the one you suggest com would you like me to send you mine to test?
Title: Re: 1wire support
Post by: twodogs on April 03, 2011, 11:04:23 pm
It looks like _if_ got his USB device working, so now I'm confused. I don't know if I have incompatible hardware, or if I need to keeping going with the USB adapter I have. I've had it working on Windows XP. I'll see if I can get it going with OWFS and Linux.

John
Title: Re: 1wire support
Post by: hari on April 03, 2011, 11:18:49 pm
Hari,

Are we saying that we should replace our DS9490R's with the one you suggest com would you like me to send you mine to test?
you can also provide ssh access to your system..
br Hari
Title: Re: 1wire support
Post by: Techstyle on April 04, 2011, 06:29:22 am
Hari

we should arrange a time next weekend for you to ssh in, PM me
Title: Re: 1wire support
Post by: DragonK on December 29, 2011, 03:18:55 pm
IF,

What does your respond to events look like?

Karel
Title: Re: 1wire support
Post by: _if_ on December 29, 2011, 05:26:06 pm
they work perfectly now, you just need to set them under advanced-configuration-events and not at eventshandler-respond to events...thats all
Title: Re: 1wire support
Post by: DragonK on December 30, 2011, 08:53:42 am
IF,

Maybe Im doing something wrong on my 0810 install.....  :)
Is it all autodetect or do we have to manually enter required fields? If so, what needs to be entered where?

Karel
Title: Re: 1wire support
Post by: _if_ on December 30, 2011, 12:58:59 pm
on 10.04 everything is autodetected, I'm not shure if that is now for 8.10 as well...

basically you connect the interface, everything gets installed, then I believe you need a reload or even a restart, then there should show up childdevices in webadmin unter climate for each connected sensor with its ID already filled in, as far as I remember you need to set the type ("thermometer") manually and then place it at the floorplan. That should be it.
Title: Re: 1wire support
Post by: DragonK on December 30, 2011, 05:31:53 pm
I Noticed that on my 1004 install, that I completed today.
Only thing I couldnt get working was the floorplan, but I'll change the type to thermometer and see if it works.

Karel
Title: Re: 1wire support
Post by: Gangsingen on January 02, 2012, 09:49:17 pm
Wow!

A couple years ago I bought a kit with one USB-adapter and two sensors from china for like 30bucks. I never got the USB adapter to work in linux using either digitemp nor OWFS, so it has been collecting dust ever since...

Guess if I got surprised when I plugged it into my 10.04 core and added it manually in web-admin and IT WORKS!! All I had to do was to plug it in, add the device in webadmin and assign it to a USB port. It detected the sensors automatically and now I can read the temp on my orbiters, WOW!

Is it possible to strip out the uninteresting device state data from whats displayed on the orbiters (ON/AUTO/) ?
Title: Re: 1wire support
Post by: _if_ on January 03, 2012, 10:31:12 am
@Gangsingen: I asked hari (who wrote the driver for 1wire) about that a while ago and his answer was that there would be needed a little modification in the climate plugin. I have not looked into it yet, but would like to get just the value displayer as well...


IF
Title: Re: 1wire support
Post by: Gangsingen on January 03, 2012, 12:15:51 pm
@Gangsingen: I asked hari (who wrote the driver for 1wire) about that a while ago and his answer was that there would be needed a little modification in the climate plugin. I have not looked into it yet, but would like to get just the value displayer as well...


IF

Yeah! "A little modification"..... Maybe a good starting point to start learning how the stuff really works under the hood?!!
Title: Re: 1wire support
Post by: DragonK on January 03, 2012, 08:54:44 pm
Maybe Im going about it all wrong......

I added the device in Webadmin and chose the port it was connected to. Then added a Multilevel sensor as a child.
The Interface's serial numer and other details where detected automatically, but the multilevel sensors's details dont get detected.

BTW.... the device and sensors is fully functional on a Windows install....  :(
Title: Re: 1wire support
Post by: DragonK on January 03, 2012, 11:09:08 pm
Everytime I add a multilevel sensor, on the orbiter is a message

"Downloading libowfs....."
and then
"Failed to download libowfs..."

The core does have internet access.....
Title: Re: 1wire support
Post by: posde on January 04, 2012, 05:16:45 pm
Please be a bit more verbose in your error messages.
Title: Re: 1wire support
Post by: hari on January 05, 2012, 10:23:09 am
There is no need to manually add the childs
Title: Re: 1wire support
Post by: DragonK on January 05, 2012, 11:23:50 am
Ok Hari,

Tonight I'll remove everything and only add the interface.
Then I'll obey Rule #1.........

Thanx.
Title: Re: 1wire support
Post by: DragonK on January 05, 2012, 09:24:25 pm
So this is where Im at.....

Removed everything related to 1wire. Rebooted the core. Then I connected my usb 1-wire Interface.
I then added the 1wire interface in the webadmin and waited for the core to finish what it needed to do. After I chose the port that the device is connected to, I left the core to do its thing again. I rebooted the core.After it was up and running again, I went back into the webadmin, and the serial number field of the 1wire interface, was automaticly populated, and under advanced it reflected as "Registered YES".

So now I left the core for about an hour to add the child devices automaticly, but no luck.
Here are part of the logs.
Code: [Select]
daemon.log:Jan  3 23:57:25 dcerouter OWFS[17258]: DEFAULT: owlib.c:SetupSingleInboundConnection(196) Cannot open USB bus master
daemon.log:Jan  3 23:57:25 dcerouter OWFS[17258]: DEFAULT: owlib.c:LibStart(54) No valid 1-wire buses found
daemon.log:Jan  4 00:16:45 dcerouter OWFS[1389]: DEFAULT: owlib.c:SetupSingleInboundConnection(196) Cannot open USB bus master
daemon.log:Jan  4 00:16:45 dcerouter OWFS[1389]: DEFAULT: owlib.c:LibStart(54) No valid 1-wire buses found
daemon.log:Jan  5 20:07:34 dcerouter OWFS[1523]: DEFAULT: owlib.c:SetupSingleInboundConnection(196) Cannot open USB bus master
daemon.log:Jan  5 20:07:34 dcerouter OWFS[1523]: DEFAULT: owlib.c:LibStart(54) No valid 1-wire buses found
daemon.log:Jan  5 20:16:44 dcerouter OWFS[1526]: DEFAULT: owlib.c:SetupSingleInboundConnection(196) Cannot open USB bus master
daemon.log:Jan  5 20:16:44 dcerouter OWFS[1526]: DEFAULT: owlib.c:LibStart(54) No valid 1-wire buses found
daemon.log:Jan  5 21:10:34 dcerouter OWFS[1510]: DEFAULT: owlib.c:SetupSingleInboundConnection(196) Cannot open USB bus master
daemon.log:Jan  5 21:10:34 dcerouter OWFS[1510]: DEFAULT: owlib.c:LibStart(54) No valid 1-wire buses found
and
Code: [Select]
syslog:Jan  5 20:07:34 dcerouter OWFS[1523]: DEFAULT: owlib.c:SetupSingleInboundConnection(196) Cannot open USB bus master
syslog:Jan  5 20:07:34 dcerouter OWFS[1523]: DEFAULT: owlib.c:LibStart(54) No valid 1-wire buses found
syslog:Jan  5 20:16:44 dcerouter OWFS[1526]: DEFAULT: owlib.c:SetupSingleInboundConnection(196) Cannot open USB bus master
syslog:Jan  5 20:16:44 dcerouter OWFS[1526]: DEFAULT: owlib.c:LibStart(54) No valid 1-wire buses found
syslog:Jan  5 21:10:34 dcerouter OWFS[1510]: DEFAULT: owlib.c:SetupSingleInboundConnection(196) Cannot open USB bus master
syslog:Jan  5 21:10:34 dcerouter OWFS[1510]: DEFAULT: owlib.c:LibStart(54) No valid 1-wire buses found
syslog.1:Jan  3 23:57:25 dcerouter OWFS[17258]: DEFAULT: owlib.c:SetupSingleInboundConnection(196) Cannot open USB bus master
syslog.1:Jan  3 23:57:25 dcerouter OWFS[17258]: DEFAULT: owlib.c:LibStart(54) No valid 1-wire buses found
syslog.1:Jan  4 00:16:45 dcerouter OWFS[1389]: DEFAULT: owlib.c:SetupSingleInboundConnection(196) Cannot open USB bus master
syslog.1:Jan  4 00:16:45 dcerouter OWFS[1389]: DEFAULT: owlib.c:LibStart(54) No valid 1-wire buses found

Onewire Log
Code: [Select]
dcerouter_1024512:/var/log/pluto# cat 63_OneWire.log
== ATTEMPT FRESH START ==
1       01/03/12 22:14:23       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     27453 Dev: 63; Already Running list: 15,16,18,19,30,40,62,21,22,37,25,27,26,23,
== FRESH START ==
1       01/03/12 22:14:24       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     device: 63 ip: localhost cmd_line: OneWire
0       01/03/12 22:14:24       63 (spawning-device)    Entering 63
========== NEW LOG SECTION ==========
1       01/03/12 22:14:24       63 (spawning-device)    Starting... 1
1       01/03/12 22:14:24       63 (spawning-device)    Found /usr/pluto/bin/OneWire
05      01/03/12 22:14:24.179           Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 63 last error 2 <0xb78786d0>
05      01/03/12 22:14:24.180           The router must be reloaded before this device is fully functional <0xb78786d0>
05      01/03/12 22:14:24.182           void ClientSocket::Disconnect() on this socket: 0x832ddb8 (m_Socket: 5) <0xb78786d0>
05      01/03/12 22:14:24.191           Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 63 last error 2 <0xb78786d0>
01      01/03/12 22:14:24.259           TranslateSerialUSB pci0000:00/0000:00:1d.1+1 result /dev/ttyUSB0 <0xb78786d0>
01      01/03/12 22:14:24.259           Opening port: /dev/ttyUSB0 <0xb78786d0>
05      01/03/12 22:33:12.219           Got a reload command from 0  <0xb6475b70>
05      01/03/12 22:33:12.477           void ClientSocket::Disconnect() on this socket: 0x832e350 (m_Socket: 7) <0xb78786d0>
Return code: 2
2       01/03/12 22:33:12       63 (spawning-device)    Device requests restart... count=1/50 dev=63
Tue Jan  3 22:33:12 SAST 2012 Restart
========== NEW LOG SECTION ==========
1       01/03/12 22:33:20       63 (spawning-device)    Starting... 1
1       01/03/12 22:33:21       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 22:33:24.548           TranslateSerialUSB pci0000:00/0000:00:1d.1+1 result /dev/ttyUSB0 <0xb78776d0>
01      01/03/12 22:33:24.548           Opening port: /dev/ttyUSB0 <0xb78776d0>
05      01/03/12 22:55:11.771           Got a reload command from 0  <0xb6474b70>
05      01/03/12 22:55:12.023           void ClientSocket::Disconnect() on this socket: 0x94e5350 (m_Socket: 7) <0xb78776d0>
Return code: 2
2       01/03/12 22:55:12       63 (spawning-device)    Device requests restart... count=1/50 dev=63
Tue Jan  3 22:55:12 SAST 2012 Restart
========== NEW LOG SECTION ==========
1       01/03/12 22:55:20       63 (spawning-device)    Starting... 1
1       01/03/12 22:55:20       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 22:55:23.992           TranslateSerialUSB pci0000:00/0000:00:1d.1+1 result /dev/ttyUSB0 <0xb782e6d0>
01      01/03/12 22:55:23.992           Opening port: /dev/ttyUSB0 <0xb782e6d0>
05      01/03/12 23:02:35.536           Creating child 65 <0xb782e6d0>
05      01/03/12 23:02:35.536           Note: Device manager has attached a device of type 1946 that this has no custom event handler for.  It will not fire events. <0xb782e6d0>
05      01/03/12 23:02:35.536           Note: Device manager has attached a device of type 1946 that this has no custom handler for.  This is normal for IR. <0xb782e6d0>
== ATTEMPT FRESH START ==
1       01/03/12 23:14:06       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     22193 Dev: 63; Already Running list: 15,16,18,19,30,
== FRESH START ==
1       01/03/12 23:14:06       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     device: 63 ip: localhost cmd_line: OneWire
0       01/03/12 23:14:06       63 (spawning-device)    Entering 63
========== NEW LOG SECTION ==========
1       01/03/12 23:14:06       63 (spawning-device)    Starting... 1
1       01/03/12 23:14:06       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:14:07.001           TranslateSerialUSB pci0000:00/0000:00:1d.1+1 result /dev/ttyUSB0 <0xb776f6d0>
01      01/03/12 23:14:07.001           Opening port: /dev/ttyUSB0 <0xb776f6d0>
01      01/03/12 23:20:45.444           OW_init error: 22, Invalid argument <0xb776f6d0>
01      01/03/12 23:20:45.444           Connect() Failed <0xb776f6d0>
Return code: 1
3       01/03/12 23:20:45       63 (spawning-device)    Device died... count=1/50 dev=63
Tue Jan  3 23:20:45 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:20:55       63 (spawning-device)    Starting... 2
1       01/03/12 23:20:55       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:20:55.644           Opening port:  <0xb78c76d0>
01      01/03/12 23:20:55.645           Connect() Failed <0xb78c76d0>
Return code: 1
3       01/03/12 23:20:55       63 (spawning-device)    Device died... count=2/50 dev=63
Tue Jan  3 23:20:55 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:21:05       63 (spawning-device)    Starting... 3
1       01/03/12 23:21:05       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:21:05.808           Opening port:  <0xb78996d0>
01      01/03/12 23:21:05.809           Connect() Failed <0xb78996d0>
Return code: 1
3       01/03/12 23:21:05       63 (spawning-device)    Device died... count=3/50 dev=63
Tue Jan  3 23:21:05 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:21:15       63 (spawning-device)    Starting... 4
1       01/03/12 23:21:15       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:21:16.004           Opening port:  <0xb76f76d0>
01      01/03/12 23:21:16.004           Connect() Failed <0xb76f76d0>
Return code: 1
3       01/03/12 23:21:16       63 (spawning-device)    Device died... count=4/50 dev=63
Tue Jan  3 23:21:16 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:21:26       63 (spawning-device)    Starting... 5
1       01/03/12 23:21:26       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:21:26.164           Opening port:  <0xb77d86d0>
01      01/03/12 23:21:26.164           Connect() Failed <0xb77d86d0>
Return code: 1
3       01/03/12 23:21:26       63 (spawning-device)    Device died... count=5/50 dev=63
Tue Jan  3 23:21:26 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:21:36       63 (spawning-device)    Starting... 6
1       01/03/12 23:21:36       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:21:36.324           Opening port:  <0xb784a6d0>
01      01/03/12 23:21:36.324           Connect() Failed <0xb784a6d0>
Return code: 1
3       01/03/12 23:21:36       63 (spawning-device)    Device died... count=6/50 dev=63
Tue Jan  3 23:21:36 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:21:46       63 (spawning-device)    Starting... 7
1       01/03/12 23:21:46       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:21:46.544           Opening port:  <0xb78956d0>
01      01/03/12 23:21:46.544           Connect() Failed <0xb78956d0>
Return code: 1
3       01/03/12 23:21:46       63 (spawning-device)    Device died... count=7/50 dev=63
Tue Jan  3 23:21:46 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:21:56       63 (spawning-device)    Starting... 8
1       01/03/12 23:21:56       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:21:56.708           Opening port:  <0xb77416d0>
01      01/03/12 23:21:56.708           Connect() Failed <0xb77416d0>
Return code: 1
3       01/03/12 23:21:56       63 (spawning-device)    Device died... count=8/50 dev=63
Tue Jan  3 23:21:56 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:22:06       63 (spawning-device)    Starting... 9
1       01/03/12 23:22:06       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:22:06.868           Opening port:  <0xb77b46d0>
01      01/03/12 23:22:06.868           Connect() Failed <0xb77b46d0>
Return code: 1
3       01/03/12 23:22:06       63 (spawning-device)    Device died... count=9/50 dev=63
Tue Jan  3 23:22:06 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:22:16       63 (spawning-device)    Starting... 10
1       01/03/12 23:22:16       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:22:17.028           Opening port:  <0xb78896d0>
01      01/03/12 23:22:17.028           Connect() Failed <0xb78896d0>
Return code: 1
3       01/03/12 23:22:17       63 (spawning-device)    Device died... count=10/50 dev=63
Tue Jan  3 23:22:17 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:22:27       63 (spawning-device)    Starting... 11
1       01/03/12 23:22:27       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:22:27.188           Opening port:  <0xb77b46d0>
01      01/03/12 23:22:27.188           Connect() Failed <0xb77b46d0>
Return code: 1
3       01/03/12 23:22:27       63 (spawning-device)    Device died... count=11/50 dev=63
Tue Jan  3 23:22:27 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:22:37       63 (spawning-device)    Starting... 12
1       01/03/12 23:22:37       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:22:37.348           Opening port:  <0xb77d36d0>
01      01/03/12 23:22:37.348           Connect() Failed <0xb77d36d0>
Return code: 1
3       01/03/12 23:22:37       63 (spawning-device)    Device died... count=12/50 dev=63
Tue Jan  3 23:22:37 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:22:47       63 (spawning-device)    Starting... 13
1       01/03/12 23:22:47       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:22:47.508           Opening port:  <0xb78616d0>
01      01/03/12 23:22:47.508           Connect() Failed <0xb78616d0>
Return code: 1
3       01/03/12 23:22:47       63 (spawning-device)    Device died... count=13/50 dev=63
Tue Jan  3 23:22:47 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:22:57       63 (spawning-device)    Starting... 14
1       01/03/12 23:22:57       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:22:57.672           Opening port:  <0xb77696d0>
01      01/03/12 23:22:57.672           Connect() Failed <0xb77696d0>
Return code: 1
3       01/03/12 23:22:57       63 (spawning-device)    Device died... count=14/50 dev=63
Tue Jan  3 23:22:57 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:23:07       63 (spawning-device)    Starting... 15
1       01/03/12 23:23:07       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:23:07.904           Opening port:  <0xb78106d0>
01      01/03/12 23:23:07.904           Connect() Failed <0xb78106d0>
Return code: 1
3       01/03/12 23:23:07       63 (spawning-device)    Device died... count=15/50 dev=63
Tue Jan  3 23:23:07 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:23:17       63 (spawning-device)    Starting... 16
1       01/03/12 23:23:17       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:23:18.064           Opening port:  <0xb77896d0>
01      01/03/12 23:23:18.064           Connect() Failed <0xb77896d0>
Return code: 1
3       01/03/12 23:23:18       63 (spawning-device)    Device died... count=16/50 dev=63
Tue Jan  3 23:23:18 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:23:28       63 (spawning-device)    Starting... 17
1       01/03/12 23:23:28       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:23:28.224           Opening port:  <0xb78296d0>
01      01/03/12 23:23:28.224           Connect() Failed <0xb78296d0>
Return code: 1
3       01/03/12 23:23:28       63 (spawning-device)    Device died... count=17/50 dev=63
Tue Jan  3 23:23:28 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:23:38       63 (spawning-device)    Starting... 18
1       01/03/12 23:23:38       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:23:38.384           Opening port: 0 <0xb77ff6d0>
01      01/03/12 23:23:38.386           OW_init error: 22, Invalid argument <0xb77ff6d0>
01      01/03/12 23:23:38.386           Connect() Failed <0xb77ff6d0>
Return code: 1
3       01/03/12 23:23:38       63 (spawning-device)    Device died... count=18/50 dev=63
Tue Jan  3 23:23:38 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:23:48       63 (spawning-device)    Starting... 19
1       01/03/12 23:23:48       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:23:48.548           Opening port: 0 <0xb772d6d0>
01      01/03/12 23:23:48.550           OW_init error: 22, Invalid argument <0xb772d6d0>
01      01/03/12 23:23:48.550           Connect() Failed <0xb772d6d0>
Return code: 1
3       01/03/12 23:23:48       63 (spawning-device)    Device died... count=19/50 dev=63
Tue Jan  3 23:23:48 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:23:58       63 (spawning-device)    Starting... 20
1       01/03/12 23:23:58       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:23:58.708           Opening port: 0 <0xb78c46d0>
01      01/03/12 23:23:58.710           OW_init error: 22, Invalid argument <0xb78c46d0>
01      01/03/12 23:23:58.710           Connect() Failed <0xb78c46d0>
Return code: 1
3       01/03/12 23:23:58       63 (spawning-device)    Device died... count=20/50 dev=63
Tue Jan  3 23:23:58 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:24:08       63 (spawning-device)    Starting... 21
1       01/03/12 23:24:08       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:24:08.868           Opening port: 0 <0xb77b36d0>
01      01/03/12 23:24:08.870           OW_init error: 22, Invalid argument <0xb77b36d0>
01      01/03/12 23:24:08.870           Connect() Failed <0xb77b36d0>
Return code: 1
3       01/03/12 23:24:08       63 (spawning-device)    Device died... count=21/50 dev=63
Tue Jan  3 23:24:08 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:24:18       63 (spawning-device)    Starting... 22
1       01/03/12 23:24:18       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:24:19.028           Opening port: 0 <0xb78dd6d0>
01      01/03/12 23:24:19.030           OW_init error: 22, Invalid argument <0xb78dd6d0>
01      01/03/12 23:24:19.030           Connect() Failed <0xb78dd6d0>
Return code: 1
3       01/03/12 23:24:19       63 (spawning-device)    Device died... count=22/50 dev=63
Tue Jan  3 23:24:19 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:24:29       63 (spawning-device)    Starting... 23
1       01/03/12 23:24:29       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:24:29.188           Opening port: 0 <0xb77516d0>
01      01/03/12 23:24:29.190           OW_init error: 22, Invalid argument <0xb77516d0>
01      01/03/12 23:24:29.190           Connect() Failed <0xb77516d0>
Return code: 1
3       01/03/12 23:24:29       63 (spawning-device)    Device died... count=23/50 dev=63
Tue Jan  3 23:24:29 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:24:39       63 (spawning-device)    Starting... 24
1       01/03/12 23:24:39       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:24:39.352           Opening port: 0 <0xb771f6d0>
01      01/03/12 23:24:39.354           OW_init error: 22, Invalid argument <0xb771f6d0>
01      01/03/12 23:24:39.354           Connect() Failed <0xb771f6d0>
Return code: 1
3       01/03/12 23:24:39       63 (spawning-device)    Device died... count=24/50 dev=63
Tue Jan  3 23:24:39 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:24:49       63 (spawning-device)    Starting... 25
1       01/03/12 23:24:49       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:24:49.528           Opening port: 0 <0xb77776d0>
01      01/03/12 23:24:49.530           OW_init error: 22, Invalid argument <0xb77776d0>
01      01/03/12 23:24:49.530           Connect() Failed <0xb77776d0>
Return code: 1
3       01/03/12 23:24:49       63 (spawning-device)    Device died... count=25/50 dev=63
Tue Jan  3 23:24:49 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:24:59       63 (spawning-device)    Starting... 26
1       01/03/12 23:24:59       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:24:59.708           Opening port: 0 <0xb777f6d0>
01      01/03/12 23:24:59.710           OW_init error: 22, Invalid argument <0xb777f6d0>
01      01/03/12 23:24:59.710           Connect() Failed <0xb777f6d0>
Return code: 1
3       01/03/12 23:24:59       63 (spawning-device)    Device died... count=26/50 dev=63
Tue Jan  3 23:24:59 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:25:09       63 (spawning-device)    Starting... 27
1       01/03/12 23:25:09       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:25:09.901           Opening port: 0 <0xb781f6d0>
01      01/03/12 23:25:09.903           OW_init error: 22, Invalid argument <0xb781f6d0>
01      01/03/12 23:25:09.903           Connect() Failed <0xb781f6d0>
Return code: 1
3       01/03/12 23:25:09       63 (spawning-device)    Device died... count=27/50 dev=63
Tue Jan  3 23:25:09 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:25:19       63 (spawning-device)    Starting... 28
1       01/03/12 23:25:19       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:25:20.092           Opening port: 0 <0xb77966d0>
01      01/03/12 23:25:20.094           OW_init error: 22, Invalid argument <0xb77966d0>
01      01/03/12 23:25:20.094           Connect() Failed <0xb77966d0>
Return code: 1
3       01/03/12 23:25:20       63 (spawning-device)    Device died... count=28/50 dev=63
Tue Jan  3 23:25:20 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:25:30       63 (spawning-device)    Starting... 29
1       01/03/12 23:25:30       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:25:30.392           Opening port: 0 <0xb778b6d0>
01      01/03/12 23:25:30.394           OW_init error: 22, Invalid argument <0xb778b6d0>
01      01/03/12 23:25:30.394           Connect() Failed <0xb778b6d0>
Return code: 1
3       01/03/12 23:25:30       63 (spawning-device)    Device died... count=29/50 dev=63
Tue Jan  3 23:25:30 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:25:40       63 (spawning-device)    Starting... 30
1       01/03/12 23:25:40       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:25:40.784           Opening port: 0 <0xb78026d0>
01      01/03/12 23:25:40.786           OW_init error: 22, Invalid argument <0xb78026d0>
01      01/03/12 23:25:40.787           Connect() Failed <0xb78026d0>
Return code: 1
3       01/03/12 23:25:40       63 (spawning-device)    Device died... count=30/50 dev=63
Tue Jan  3 23:25:40 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:25:50       63 (spawning-device)    Starting... 31
1       01/03/12 23:25:50       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:25:51.008           Opening port: 0 <0xb781d6d0>
01      01/03/12 23:25:51.010           OW_init error: 22, Invalid argument <0xb781d6d0>
01      01/03/12 23:25:51.010           Connect() Failed <0xb781d6d0>
Return code: 1
3       01/03/12 23:25:51       63 (spawning-device)    Device died... count=31/50 dev=63
Tue Jan  3 23:25:51 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:26:01       63 (spawning-device)    Starting... 32
1       01/03/12 23:26:01       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:26:01.236           Opening port: 0 <0xb77de6d0>
01      01/03/12 23:26:01.238           OW_init error: 22, Invalid argument <0xb77de6d0>
01      01/03/12 23:26:01.238           Connect() Failed <0xb77de6d0>
Return code: 1
3       01/03/12 23:26:01       63 (spawning-device)    Device died... count=32/50 dev=63
Tue Jan  3 23:26:01 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:26:11       63 (spawning-device)    Starting... 33
1       01/03/12 23:26:11       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:26:11.484           Opening port: 0 <0xb78076d0>
01      01/03/12 23:26:11.486           OW_init error: 22, Invalid argument <0xb78076d0>
01      01/03/12 23:26:11.486           Connect() Failed <0xb78076d0>
Return code: 1
3       01/03/12 23:26:11       63 (spawning-device)    Device died... count=33/50 dev=63
Tue Jan  3 23:26:11 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:26:21       63 (spawning-device)    Starting... 34
1       01/03/12 23:26:21       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:26:21.644           Opening port: 0 <0xb785a6d0>
01      01/03/12 23:26:21.645           OW_init error: 22, Invalid argument <0xb785a6d0>
01      01/03/12 23:26:21.646           Connect() Failed <0xb785a6d0>
Return code: 1
3       01/03/12 23:26:21       63 (spawning-device)    Device died... count=34/50 dev=63
Tue Jan  3 23:26:21 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:26:31       63 (spawning-device)    Starting... 35
1       01/03/12 23:26:31       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:26:31.804           Opening port: 0 <0xb76ea6d0>
01      01/03/12 23:26:31.806           OW_init error: 22, Invalid argument <0xb76ea6d0>
01      01/03/12 23:26:31.806           Connect() Failed <0xb76ea6d0>
Return code: 1
3       01/03/12 23:26:31       63 (spawning-device)    Device died... count=35/50 dev=63
Tue Jan  3 23:26:31 SAST 2012 died
========== NEW LOG SECTION ==========
1       01/03/12 23:26:41       63 (spawning-device)    Starting... 36
1       01/03/12 23:26:41       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:26:42.018           TranslateSerialUSB pci0000:00/0000:00:1d.0+1 result /dev/ttyUSB0 <0xb77616d0>
01      01/03/12 23:26:42.018           Opening port: /dev/ttyUSB0 <0xb77616d0>
05      01/03/12 23:33:13.584           Creating child 65 <0xb77616d0>
05      01/03/12 23:33:13.585           Note: Device manager has attached a device of type 1946 that this has no custom event handler for.  It will not fire events. <0xb77616d0>
05      01/03/12 23:33:13.585           Note: Device manager has attached a device of type 1946 that this has no custom handler for.  This is normal for IR. <0xb77616d0>
05      01/03/12 23:48:50.027           Got a reload command from 0  <0xb635eb70>
05      01/03/12 23:48:50.280           void ClientSocket::Disconnect() on this socket: 0x9908350 (m_Socket: 7) <0xb77616d0>
Return code: 2
2       01/03/12 23:48:50       63 (spawning-device)    Device requests restart... count=36/50 dev=63
Tue Jan  3 23:48:50 SAST 2012 Restart
========== NEW LOG SECTION ==========
1       01/03/12 23:48:58       63 (spawning-device)    Starting... 36
1       01/03/12 23:48:58       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/03/12 23:49:00.959           TranslateSerialUSB pci0000:00/0000:00:1d.0+1 result /dev/ttyUSB0 <0xb77c86d0>
01      01/03/12 23:49:00.959           Opening port: /dev/ttyUSB0 <0xb77c86d0>
05      01/03/12 23:59:52.775           Got a reload command from 0  <0xb63c5b70>
05      01/03/12 23:59:53.028           void ClientSocket::Disconnect() on this socket: 0x9365350 (m_Socket: 7) <0xb77c86d0>
Return code: 2
2       01/03/12 23:59:53       63 (spawning-device)    Device requests restart... count=36/50 dev=63
Tue Jan  3 23:59:53 SAST 2012 Restart
========== NEW LOG SECTION ==========
1       01/04/12 00:00:01       63 (spawning-device)    Starting... 36
1       01/04/12 00:00:01       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/04/12 0:00:03.783            TranslateSerialUSB pci0000:00/0000:00:1d.0+1 result /dev/ttyUSB0 <0xb77c36d0>
01      01/04/12 0:00:03.783            Opening port: /dev/ttyUSB0 <0xb77c36d0>
05      01/04/12 0:06:30.376            Creating child 67 <0xb77c36d0>
05      01/04/12 0:06:30.376            Note: Device manager has attached a device of type 1946 that this has no custom event handler for.  It will not fire events. <0xb77c36d0>
05      01/04/12 0:06:30.376            Note: Device manager has attached a device of type 1946 that this has no custom handler for.  This is normal for IR. <0xb77c36d0>
05      01/04/12 0:15:09.511            Got a reload command from 0  <0xb63c0b70>
05      01/04/12 0:15:09.769            void ClientSocket::Disconnect() on this socket: 0x82f9350 (m_Socket: 7) <0xb77c36d0>
Return code: 2
2       01/04/12 00:15:09       63 (spawning-device)    Device requests restart... count=36/50 dev=63
Wed Jan  4 00:15:10 SAST 2012 Restart
========== NEW LOG SECTION ==========
1       01/04/12 00:15:18       63 (spawning-device)    Starting... 36
1       01/04/12 00:15:18       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/04/12 0:15:22.714            TranslateSerialUSB pci0000:00/0000:00:1d.0+1 result /dev/ttyUSB0 <0xb774e6d0>
01      01/04/12 0:15:22.715            Opening port: /dev/ttyUSB0 <0xb774e6d0>
== ATTEMPT FRESH START ==
1       01/04/12 00:20:09       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     15533 Dev: 63; Already Running list: 15,16,18,19,30,
== FRESH START ==
1       01/04/12 00:20:09       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     device: 63 ip: localhost cmd_line: OneWire
0       01/04/12 00:20:09       63 (spawning-device)    Entering 63
========== NEW LOG SECTION ==========
1       01/04/12 00:20:09       63 (spawning-device)    Starting... 1
1       01/04/12 00:20:09       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/04/12 0:20:10.192            TranslateSerialUSB pci0000:00/0000:00:1d.0+1 result /dev/ttyUSB0 <0xb77726d0>
01      01/04/12 0:20:10.192            Opening port: /dev/ttyUSB0 <0xb77726d0>
05      01/04/12 0:27:26.778            Creating child 68 <0xb77726d0>
05      01/04/12 0:27:26.778            Note: Device manager has attached a device of type 1946 that this has no custom event handler for.  It will not fire events. <0xb77726d0>
05      01/04/12 0:27:26.778            Note: Device manager has attached a device of type 1946 that this has no custom handler for.  This is normal for IR. <0xb77726d0>
05      01/04/12 6:20:22.505            Got a reload command from 0  <0xb636fb70>
05      01/04/12 6:20:22.764            void ClientSocket::Disconnect() on this socket: 0x8116350 (m_Socket: 7) <0xb77726d0>
Return code: 2
2       01/04/12 06:20:22       63 (spawning-device)    Device requests restart... count=1/50 dev=63
Wed Jan  4 06:20:23 SAST 2012 Restart
========== NEW LOG SECTION ==========
1       01/04/12 06:20:31       63 (spawning-device)    Starting... 1
1       01/04/12 06:20:31       63 (spawning-device)    Found /usr/pluto/bin/OneWire
05      01/04/12 6:20:32.442            Connect() failed, Error Code 111 (Connection refused)) <0xb77206d0>
01      01/04/12 6:20:46.923            TranslateSerialUSB pci0000:00/0000:00:1d.0+1 result /dev/ttyUSB0 <0xb77206d0>
01      01/04/12 6:20:46.923            Opening port: /dev/ttyUSB0 <0xb77206d0>
05      01/04/12 6:27:58.478            Creating child 68 <0xb77206d0>
05      01/04/12 6:27:58.478            Note: Device manager has attached a device of type 1946 that this has no custom event handler for.  It will not fire events. <0xb77206d0>
05      01/04/12 6:27:58.478            Note: Device manager has attached a device of type 1946 that this has no custom handler for.  This is normal for IR. <0xb77206d0>
== ATTEMPT FRESH START ==
1       01/05/12 20:10:52       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     15548 Dev: 63; Already Running list: 15,16,18,19,30,
== FRESH START ==
1       01/05/12 20:10:52       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     device: 63 ip: localhost cmd_line: OneWire
0       01/05/12 20:10:52       63 (spawning-device)    Entering 63
========== NEW LOG SECTION ==========
1       01/05/12 20:10:52       63 (spawning-device)    Starting... 1
1       01/05/12 20:10:52       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/05/12 20:10:52.713           TranslateSerialUSB pci0000:00/0000:00:1d.0+1 result /dev/ttyUSB0 <0xb78496d0>
01      01/05/12 20:10:52.713           Opening port: /dev/ttyUSB0 <0xb78496d0>
05      01/05/12 20:10:53.102           Creating child 68 <0xb78496d0>
05      01/05/12 20:10:53.102           Note: Device manager has attached a device of type 1946 that this has no custom event handler for.  It will not fire events. <0xb78496d0>
05      01/05/12 20:10:53.102           Note: Device manager has attached a device of type 1946 that this has no custom handler for.  This is normal for IR. <0xb78496d0>
01      01/05/12 20:10:54.413           No Child found for 28.A8A28003000, trying to create <0xb7848b70>
01      01/05/12 20:10:54.498           Child 69 created <0xb7848b70>
== ATTEMPT FRESH START ==
1       01/05/12 20:48:45       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     2012 Dev: 63; Already Running list: 15,16,18,19,30,40,62,21,22,23,26,37,25,27,
== FRESH START ==
1       01/05/12 20:48:45       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     device: 63 ip: localhost cmd_line: OneWire
0       01/05/12 20:48:45       63 (spawning-device)    Entering 63
========== NEW LOG SECTION ==========
1       01/05/12 20:48:45       63 (spawning-device)    Starting... 1
1       01/05/12 20:48:45       63 (spawning-device)    Found /usr/pluto/bin/OneWire
05      01/05/12 20:48:45.627           Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 63 last error 2 <0xb778c6d0>
05      01/05/12 20:48:45.627           The router must be reloaded before this device is fully functional <0xb778c6d0>
05      01/05/12 20:48:45.630           void ClientSocket::Disconnect() on this socket: 0x8f78db8 (m_Socket: 5) <0xb778c6d0>
05      01/05/12 20:48:45.639           Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 63 last error 2 <0xb778c6d0>
01      01/05/12 20:48:45.710           TranslateSerialUSB pci0000:00/0000:00:1d.0+1 result /dev/ttyUSB0 <0xb778c6d0>
01      01/05/12 20:48:45.710           Opening port: /dev/ttyUSB0 <0xb778c6d0>
== ATTEMPT FRESH START ==
1       01/05/12 21:13:13       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     14048 Dev: 63; Already Running list: 15,16,18,19,30,
== FRESH START ==
1       01/05/12 21:13:13       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     device: 63 ip: localhost cmd_line: OneWire
0       01/05/12 21:13:13       63 (spawning-device)    Entering 63
========== NEW LOG SECTION ==========
1       01/05/12 21:13:13       63 (spawning-device)    Starting... 1
1       01/05/12 21:13:13       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/05/12 21:13:13.983           TranslateSerialUSB pci0000:00/0000:00:1d.0+1 result /dev/ttyUSB0 <0xb780f6d0>
01      01/05/12 21:13:13.984           Opening port: /dev/ttyUSB0 <0xb780f6d0>
05      01/05/12 22:04:49.943           void ClientSocket::Disconnect() on this socket: 0x9468350 (m_Socket: 7) <0xb780f6d0>
Return code: 0
2       01/05/12 22:04:49       63 (spawning-device)    Shutting down... count=1/50 dev=63
Thu Jan  5 22:04:50 SAST 2012 Shutdown
== ATTEMPT FRESH START ==
1       01/05/12 22:12:38       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     22911 Dev: 63; Already Running list: 15,16,18,19,30,40,62,21,22,27,23,26,25,37,
== FRESH START ==
1       01/05/12 22:12:38       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     device: 63 ip: localhost cmd_line: OneWire
0       01/05/12 22:12:39       63 (spawning-device)    Entering 63
========== NEW LOG SECTION ==========
1       01/05/12 22:12:39       63 (spawning-device)    Starting... 1
1       01/05/12 22:12:39       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/05/12 22:12:39.532           TranslateSerialUSB pci0000:00/0000:00:1d.0+1 result /dev/ttyUSB0 <0xb775c6d0>
01      01/05/12 22:12:39.533           Opening port: /dev/ttyUSB0 <0xb775c6d0>
== ATTEMPT FRESH START ==
1       01/05/12 22:19:27       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     14810 Dev: 63; Already Running list: 15,16,18,19,30,
== FRESH START ==
1       01/05/12 22:19:27       /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)     device: 63 ip: localhost cmd_line: OneWire
0       01/05/12 22:19:27       63 (spawning-device)    Entering 63
========== NEW LOG SECTION ==========
1       01/05/12 22:19:28       63 (spawning-device)    Starting... 1
1       01/05/12 22:19:28       63 (spawning-device)    Found /usr/pluto/bin/OneWire
01      01/05/12 22:19:28.292           TranslateSerialUSB pci0000:00/0000:00:1d.0+1 result /dev/ttyUSB0 <0xb77296d0>
01      01/05/12 22:19:28.292           Opening port: /dev/ttyUSB0 <0xb77296d0>
dcerouter_1024512:/var/log/pluto#

If I unplug the 1wire device from the usb port, in the webadmin,port section changes to "Please select port" and the serial number field is blank.
But if plug the 1wire device back in, and choose the port, and do a quick reload, the serial number is detected again. But the child devices dont get created.
 
1wire interface -- LinkUSBi http://www.homechip.com/catalog/product_info.php?cPath=22&products_id=171
Temp Sensors -- DS18B20 http://www.homechip.com/catalog/product_info.php?cPath=26&products_id=99

Karel

Edit:: The Onewire device and sensors work on a windows Pc....  :(
Title: Re: 1wire support
Post by: hari on January 06, 2012, 09:08:36 pm
from your log:

01      01/05/12 20:10:54.413           No Child found for 28.A8A28003000, trying to create <0xb7848b70>
01      01/05/12 20:10:54.498           Child 69 created <0xb7848b70>

Are you sure that there is no child 69?
Title: Re: 1wire support
Post by: DragonK on January 07, 2012, 01:38:15 pm
Hari,

Last night when I got home, there was no child devices under the climate menu or under the 1-wire interface.
After adding an Old Acer laptop as an MD, the MD's Xineplayer is now #69.

But After a few reboots this morning (Powerfailures) the Temp sensor child was added to the climate menu with a device number of #74.

Now Im going to add another 2 sensors to the bus.

Hari, Thanx for ur patience and willingness to help.
Its greately appreciated.

Karel
Title: Re: 1wire support
Post by: twodogs on January 23, 2012, 08:27:41 pm
I've reread this topic many times, and still completely confused. I have a USB 1-wire adapter as shown in the picture. When I go to add the interface, there is only a single option (1wire template 2161). When I pick the template, it seems that the correct software downloads. However when I go to configure the device, the only options I get are rs232 ports, not USB. The wiki seems to indicate that only rs232 adapters are supported. But earlier in this thread, both _if_ and Gangsingen state that they have USB devices working (see links). How can I get my USB device to work?

Twodogs

http://forum.linuxmce.org/index.php/topic,11328.msg86425.html#msg86425
http://forum.linuxmce.org/index.php/topic,11328.msg79599.html#msg79599
http://wiki.linuxmce.org/index.php/1-Wire_Basics

(http://img577.imageshack.us/img577/1159/ds9490ra.jpg) (http://img577.imageshack.us/i/ds9490ra.jpg/)

Title: Re: 1wire support
Post by: mkbrown69 on January 23, 2012, 09:27:41 pm
Twodogs,

You're not alone ;-)

I've been wondering too, mostly because I'm looking to implement 1-wire, but on a remote host.  OWFS supports that, but it looks like the 2161 Template was done to configure owserver for a serial port adapter like a 9097U.  I've been wondering if I should create a new 1-wire template, or modify the 2161 to support the other methods.

Would someone more knowledgeable about the 1-wire template like to suggest a course of action for USB and remote 1-wire support?

Thanks!

/Mike
Title: Re: 1wire support
Post by: twodogs on January 24, 2012, 01:23:14 am
It also looks like DragonK might not have completed the install of his USB 1-wire system.
Title: Re: 1wire support
Post by: DragonK on January 24, 2012, 06:36:50 am
Yip I did with alot of patience...... Rule #1 of LinuxMCE.
Im glad to say that when addidng more than one temp sensor to the bus, it gets added automaticly.
All you need to do is assign a room and place it on the floorplan.

What devices do you guys have?
LMCE 0810 or 1004?

These are the devices that I have.
1wire interface -- LinkUSBi http://www.homechip.com/catalog/product_info.php?cPath=22&products_id=171
Temp Sensors -- DS18B20 http://www.homechip.com/catalog/product_info.php?cPath=26&products_id=99


Karel

Oh and im running LMCE 1004
Title: Re: 1wire support
Post by: hari on January 24, 2012, 11:01:04 am
most usb 1-wire interface show up as serial port
Title: Re: 1wire support
Post by: Techstyle on January 24, 2012, 06:04:36 pm
Twodogs,

What is the part number of your interface?

Techstyle
Title: Re: 1wire support
Post by: twodogs on January 24, 2012, 07:00:21 pm
It is a DS9490R that I bought from Hobby Boards some time ago.

http://www.hobby-boards.com/catalog/product_info.php?products_id=1503

Hari's comment that the 1-wire adapters usually show up as serial devices was interesting. I think I have one of the few that actually show up as USB devices. The output of "LSUSB is...

Code: [Select]
Bus 002 Device 003: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1 Fob, 1-Wire adapter

I wanted to see if I could get this device running on my Ubuntu 11.04 desktop. The following links were helpful - the first shows how to install the software, and the second shows how to bring the DS9490R to life. Combining the instructions got things working.

https://help.ubuntu.com/community/1wireSoftware
http://apartment-automation.blogspot.com/2009/09/installing-1-wire-usb-adapter-ds9490r.html

To prepare, insert the DS9490R into the USB port (without the temperature sensor)
download latest owfs tar from sourceforge. Paste in /usr/src and extract.
Then...
Code: [Select]
sudo apt-get install automake autoconf autotools-dev gcc g++ libtool libusb-dev fuse-utils libfuse-dev swig python-dev tcl8.4-dev php5-dev
cd /usr/src/owfs-2.8p14
./configure
make
sudo make install
sudo mkdir /media/1-wire
sudo /opt/owfs/bin/owfs --allow_other -u /media/1-wire

-u key means USB and "/media/1-wire" is mountpoint and --allow_other means that non-root users can read 1-wire directory.
Plug the temp sensor into the DS9490R
Open the folder /media/1-wire and look for a folder named 10.E66CE1010800 or similar. It should contain a "temperature" file that shows the Celsius readout.

So awesome, now I've got it working in Ubuntu. Next question is how much effort to make it work with LMCE? Maybe I have to  change some configuration file to contain the -u option for USB? Also maybe change the LMCE 1-wire template so that it gives me something other than serial port options? As always, I'm feeling like a weak swimmer in deep waters!
Title: Re: 1wire support
Post by: Techstyle on January 24, 2012, 07:11:57 pm
I have the same device, good luck.
Title: Re: 1wire support
Post by: twodogs on January 24, 2012, 07:20:08 pm
Damn! If only I'd held out a little longer, you'd be floundering and I'd be watching.

Forgot to mention that I've set this up on a 1004 test rig (not my installed 0810 system).

Twodogs
Title: Re: 1wire support
Post by: Techstyle on January 24, 2012, 08:08:21 pm
My system is all in pieces at the moment, I have no idea where the device is
Title: Re: 1wire support
Post by: Techstyle on January 25, 2012, 01:50:32 am
I found it plugged it in (0810) without the sensor and added device template #2161, waited for a bit then got this:

Code: [Select]
========== NEW LOG SECTION ==========
1 01/24/12 17:43:02 43 (spawning-device) Starting... 9
1 01/24/12 17:43:03 43 (spawning-device) Found /usr/pluto/bin/OneWire
01 01/24/12 17:43:03.140 Opening port: /dev/ttyUSB0 <0xb70096c0>
01 01/24/12 17:43:03.143 OW_init error: 22, Invalid argument <0xb70096c0>
01 01/24/12 17:43:03.143 Connect() Failed <0xb70096c0>

in an earlier message Hari said the error: 22 was a error because is no sensor.  Plugged in the sensor and get nothing.

I added a multilevel sensor as a child but I am stuck on what the port address of the sensor is
Title: Re: 1wire support
Post by: twodogs on January 25, 2012, 02:56:00 am
I plugged my adapter into my working 0810 installation and got the same result. Looks like things are trying to work - apparently the device is recognized and assigned to a USB port. The 1-wire software appears to attempt a handshake but can't quite get there. So maybe there is hope for us. I had just about resigned myself to finding a new rs232 adapter.
Title: Re: 1wire support
Post by: DragonK on January 25, 2012, 06:44:52 am
Hi Guys,

You only need to had the 1-wire interface in the webmin. Choose the port its connected.
You have prewired sensors?
No need to add the childs manually. Mine showed up in the webmin after a couple of reboots.

Karel
Title: Re: 1wire support
Post by: twodogs on January 25, 2012, 01:43:56 pm
Here are a few pictures. The adapter plugs into the USB port, then a phone cable with sensors plugs into the adapter. I only have one temp sensor on a short pigtail right now, but the house is wired for temp sensing in almost every room. My plan is to use this info to make decisions for the HVAC system.

One of the problems is that the template won't allow me to select the ttyUSB port the adapter is connected to. It only allows me to select ttyS0-3 (rs232 ports).


(http://img838.imageshack.us/img838/5981/img3356hj.jpg) (http://imageshack.us/photo/my-images/838/img3356hj.jpg/)
(http://img696.imageshack.us/img696/9126/img3357nx.jpg) (http://imageshack.us/photo/my-images/696/img3357nx.jpg/)


Title: Re: 1wire support
Post by: DragonK on January 25, 2012, 02:38:33 pm
The screenshots from the 0810 or your 1004 testrig?
I couldn't get mine to work on 0810. But managed to get it installed on 1004.

You'll have better luck allowing Hari to ssh into your box to see if he maybe can fix it.

Karel
Title: Re: 1wire support
Post by: twodogs on January 25, 2012, 03:08:27 pm
The shot is my 0810 installation, but it appears to be the exact same template in 1004.
Title: Re: 1wire support
Post by: posde on January 25, 2012, 03:57:03 pm
twodogs,

the template should show you all available serial ports, including USB serial ports.
Title: Re: 1wire support
Post by: hari on January 25, 2012, 07:03:42 pm
yes, it should show ttyUSB, too. Maybe run UpdateAvailableSerialPorts.sh and see if it shows up in the list..
Title: Re: 1wire support
Post by: Techstyle on January 25, 2012, 11:30:40 pm
In Webadmin mine also showed the same, serial ports only.  However it still seemed to find the device as the log said:

Code: [Select]
01 01/24/12 17:43:03.140 Opening port: /dev/ttyUSB0 <0xb70096c0>
Can confirm the correct procedure in 0810, do we need to add the child (as stated on the Wiki) or do we wait until it is discovered?

this raises another point the device will try to look for the sensor 50 times and then it will stop trying, how do you restart it again?
Title: Re: 1wire support
Post by: twodogs on January 25, 2012, 11:36:08 pm
No luck here either. I rebooted the system. I expected a "some devices failed to load" error but did not get one. I saw the 1-wire device load during the start sequence. So I had some hope, but the template still only has serial ports showing (like in the picture above). I tried
Code: [Select]
cd usr/pluto/bin
sh UpdateAvailableSerialPorts.sh 
It appeared to run without error but the template still showed only rs232 ports. My 1-wire log shows the exact same error 22 that Techstyle reported in post 153. Plugging or unplugging the temp sensor to the adapter has no effect - still get error 22.
Title: Re: 1wire support
Post by: twodogs on January 25, 2012, 11:46:38 pm
By the way, thanks Hari for your help. I know you might have other fish to fry. On the one hand, the 9490R seems like it might be a good piece of hardware for LMCE to support - if you agree I'll do whatever I can to help get the thing to work. On the other hand if this seems a waste of time, I'll just buy a different adapter.

twodogs
Title: Re: 1wire support
Post by: Techstyle on January 26, 2012, 01:32:52 am
twodogs, I didn't see your pics earlier but I think we have the same thing in mind:
(http://www.techstyleuk.co.uk/1wire2.JPG)

I have also wired my house and plan on using some of my CAT5e drops to share 1-wire and POTS over.  I have wired to each room, outside in a screened porch, outside proper and in the pool  :)

I had not tried to use it in windows yet but I thought I should incase my wiring is suspect:
(http://www.techstyleuk.co.uk/1wire.JPG)

apparently it is getting cooler in here.  this windows tool does give me the serial number of the sensor as '210008002F424310' is this what LMCE is expecting as port?
Title: Re: 1wire support
Post by: twodogs on January 26, 2012, 02:03:48 am
Yeah, thanks for your assistance too Techstyle. I'd like for my system to save more money and energy than it spends. My goals are somewhat lofty, but I'll chip away at them. I'd like LMCE to track my location in the house and control the temperature based upon the occupied areas. If we're in the living room with the fireplace on, then I'd like the furnace to idle down. In summer, I'd like to have an outside weather station to provide temp and humidity info and let the system determine if we should use A/C or evaporative cooling. I'm already saving about $60 per month in phone bills with the VOIP. So the 1-wire system is pretty important.

twodogs
Title: Re: 1wire support
Post by: Techstyle on January 26, 2012, 03:01:44 am
It would be interesting to know what peoples sensor identifiers look like?
Title: Re: 1wire support
Post by: hari on January 26, 2012, 05:07:19 pm
there is no need to create childs manually, neither in 0810 nor in 1004. Regarding interfaces other than serial (or ttyUSB) ones supported by owfs, i dunno how to make a template that can work with serial and usb at the same time. maybe tschak can help. The code itself should work fine if the usb interface is supported by owfs.
br Hari
Title: Re: 1wire support
Post by: twodogs on January 26, 2012, 05:39:20 pm
Hari, for anyone buying a new 1-wire adapter, what product do you recommend?
Title: Re: 1wire support
Post by: DragonK on January 26, 2012, 07:28:57 pm
Hi,

This is the one that I have, and it works. I believe its the same that _if_ has and the one that Hari used.

1wire interface -- LinkUSBi http://www.homechip.com/catalog/product_info.php?cPath=22&products_id=171

Karel
Title: Re: 1wire support
Post by: twodogs on January 26, 2012, 07:48:53 pm
Great. Found a USA supplier.

http://www.ibuttonlink.com/linkusbi.aspx

I might wait a few days to see if Tschak knows of a way to change the polarity of the flux capacitor, but looking at the source files tells me that this thing is complicated. I'll probably just get one that works.
Title: Re: 1wire support
Post by: Techstyle on January 27, 2012, 12:44:40 am
I just ordered it from the US link you posted.  I will try it once I have it and then maybe ship my 9490R to somebody who can help to add support for it so others do not have this issue.
Title: Re: 1wire support
Post by: twodogs on February 03, 2012, 07:07:49 am
OK, the new adapter arrived today from iButtonLink. I thought I got the same adapter that Hari was using, but I didn't.

Hari has this the linkusb...
http://www.ibuttonlink.com/linkusb.aspx

I have the linkusbi...
http://www.ibuttonlink.com/linkusbi.aspx

According to the website, "The difference between LinkUSB and LinkUSBi is the addition of a DS2401 ID chip in the LinkUSBi." I hope that does not render it unusable for LMCE. I plugged it into my core and the detection scripts started to roll by, trying to determine what the new device was (it couldn't). I manually entered the device as a child of the core. Unlike my other adapter, this one gave my a USB port option (see picture). After some time it registered (see picture). I then added my temp sensor and nothing happened. I know it takes awhile but its been an hour, so I'm suspicious that something is wrong. I hope its not the wrong adapter (again).

Twodogs

(http://img849.imageshack.us/img849/9601/img3370o.jpg) (http://imageshack.us/photo/my-images/849/img3370o.jpg/)

(http://img27.imageshack.us/img27/7774/ibutton.png) (http://imageshack.us/photo/my-images/27/ibutton.png/)


Title: Re: 1wire support
Post by: DragonK on February 03, 2012, 07:19:21 am
You dont have to had the childs manually.
My sensors started showing up after a reboot and a lot of patience.

I also initially ordered a LinkUSB and received a LinkUSBi

Karel....

Obey Rule #1
Title: Re: 1wire support
Post by: hari on February 03, 2012, 02:19:12 pm
there is no need to add the temp sensor manually. It will be created. watch the logs, when you see it created you can do a quick reload and there it is.. It will then send temperature changed events.

br Hari
Title: Re: 1wire support
Post by: twodogs on February 03, 2012, 03:49:08 pm
Quote
I also initially ordered a LinkUSB and received a LinkUSBi

Thanks DragonK - that's good to know. The temp sensor has been in all night and has not appeared as a child yet. Hari, I'll be patient but why does it take so long? Under what conditions does the software create new child devices? There has been no activity on the log since 10:30 last night - about 10 hours ago. This is installed in the LMCE 0810 version.

Code: [Select]
== ATTEMPT FRESH START ==
1 02/02/12 17:25:26 /usr/pluto/bin/Spawn_Device.sh 70 (spawning-device) 20321 Dev: 70; Already Running list: 15,16,18,19,67,31,32,55,57,64,69,63,21,65,22,36,27,26,25,23,
== FRESH START ==
1 02/02/12 17:25:26 /usr/pluto/bin/Spawn_Device.sh 70 (spawning-device) device: 70 ip: localhost cmd_line: OneWire
0 02/02/12 17:25:26 70 (spawning-device) Entering 70
========== NEW LOG SECTION ==========
1 02/02/12 17:25:26 70 (spawning-device) Starting... 1
1 02/02/12 17:25:26 70 (spawning-device) Found /usr/pluto/bin/OneWire
05 02/02/12 17:25:26.547 Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 70 last error 2 <0xb70456c0>
05 02/02/12 17:25:26.547 The router must be reloaded before this device is fully functional <0xb70456c0>
05 02/02/12 17:25:26.551 void ClientSocket::Disconnect() on this socket: 0x961ec60 (m_Socket: 5) <0xb70456c0>
05 02/02/12 17:25:26.562 Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 70 last error 2 <0xb70456c0>
01 02/02/12 17:25:26.602 Opening port: /dev/ttyUSB0 <0xb70456c0>
05 02/02/12 21:10:35.700 Got a reload command from 0  <0xb6042b90>
05 02/02/12 21:10:36.118 void ClientSocket::Disconnect() on this socket: 0x961f380 (m_Socket: 6) <0xb70456c0>
Return code: 2
2 02/02/12 21:10:36 70 (spawning-device) Device requests restart... count=1/50 dev=70
Thu Feb  2 21:10:36 MST 2012 Restart
========== NEW LOG SECTION ==========
1 02/02/12 21:10:44 70 (spawning-device) Starting... 1
1 02/02/12 21:10:44 70 (spawning-device) Found /usr/pluto/bin/OneWire
01 02/02/12 21:10:48.985 TranslateSerialUSB pci0000:00/0000:00:04.0+6 result /dev/ttyUSB0 <0xb71016c0>
01 02/02/12 21:10:48.986 Opening port: /dev/ttyUSB0 <0xb71016c0>
== ATTEMPT FRESH START ==
1 02/02/12 21:26:22 /usr/pluto/bin/Spawn_Device.sh 70 (spawning-device) 5751 Dev: 70; Already Running list: 15,16,18,67,19,31,32,55,57,64,
== FRESH START ==
1 02/02/12 21:26:22 /usr/pluto/bin/Spawn_Device.sh 70 (spawning-device) device: 70 ip: localhost cmd_line: OneWire
0 02/02/12 21:26:22 70 (spawning-device) Entering 70
========== NEW LOG SECTION ==========
1 02/02/12 21:26:22 70 (spawning-device) Starting... 1
1 02/02/12 21:26:22 70 (spawning-device) Found /usr/pluto/bin/OneWire
01 02/02/12 21:26:23.081 TranslateSerialUSB pci0000:00/0000:00:04.0+6 result /dev/ttyUSB0 <0xb71676c0>
01 02/02/12 21:26:23.081 Opening port: /dev/ttyUSB0 <0xb71676c0>
05 02/02/12 22:36:51.539 Got a reload command from 0  <0xb6164b90>
05 02/02/12 22:36:51.789 void ClientSocket::Disconnect() on this socket: 0x922c380 (m_Socket: 6) <0xb71676c0>
Return code: 2
2 02/02/12 22:36:51 70 (spawning-device) Device requests restart... count=1/50 dev=70
Thu Feb  2 22:36:51 MST 2012 Restart
========== NEW LOG SECTION ==========
1 02/02/12 22:37:00 70 (spawning-device) Starting... 1
1 02/02/12 22:37:00 70 (spawning-device) Found /usr/pluto/bin/OneWire
01 02/02/12 22:37:01.463 TranslateSerialUSB pci0000:00/0000:00:04.0+6 result /dev/ttyUSB0 <0xb70cf6c0>
01 02/02/12 22:37:01.463 Opening port: /dev/ttyUSB0 <0xb70cf6c0>


43 lines, displaying from 0 to 43
1
Title: Re: 1wire support
Post by: Techstyle on February 03, 2012, 07:19:20 pm
Twodogs,

Mine arrived also and I did exactly what you did and got the same result down to the last 2 code lines (and they are red) then nothing.

Title: Re: 1wire support
Post by: twodogs on February 04, 2012, 03:26:57 am
I was performing another chore on my core and caught the pop-up software box saying "failed to get libowfs". Pretty good clue, but I don't know how to solve the problem.
Title: Re: 1wire support
Post by: DragonK on February 04, 2012, 06:33:05 am
Mine also innitially showed the pop-up, cant install libowfs.
Have you reloaded/rebooted the core yet?

Another thing, After I added a new Md, my temp sensors was added.
Not sure if it has anything to do with it.
Title: Re: 1wire support
Post by: twodogs on February 04, 2012, 07:14:32 am
I've reloaded the router and rebooted a few times.
Title: Re: 1wire support
Post by: hari on February 04, 2012, 06:22:10 pm
it depends on libowfs.. we should nag possy maybe there is something wrong with the package
Title: Re: 1wire support
Post by: hari on February 04, 2012, 06:27:21 pm
try to run this from the command line: "apt-get update && apt-get install libowfs27"
Title: Re: 1wire support
Post by: Gangsingen on February 04, 2012, 09:03:37 pm
The interface I´m using is a super cheap chineese variant of the 9097.

http://pcsensor.com/index.php?_a=viewProd&productId=33 (http://pcsensor.com/index.php?_a=viewProd&productId=33)

In 8.10 it doesn´t work, and isn´t listed with lsusb. But in 10.04 though, it´s listed using lsusb, and once added manually in webadmin the sensors are detected automatically.
Title: Re: 1wire support
Post by: twodogs on February 04, 2012, 09:10:22 pm
Gangsingen - thanks - having just bought a more expensive adapter I hope I don't have to buy another! Perhaps I'm having trouble because I'm using 0810. I'll try my test 1004 system when I can set it up.

Hari. No luck with the update and install. I'm appreciating your assistance and I'm sure this is going to work eventually.

Code: [Select]
js@dcerouter:~$ sudo apt-get update && apt-get install libowfs27
[sudo] password for js:                                        
Ign file: ./ Release.gpg                                        
Ign file: ./ Translation-en_US                                                                                
Ign file: ./ Release                                                                                          
Ign file: ./ Packages                                                                                          
Ign http://debian.slimdevices.com stable Release.gpg                                                          
Ign http://archive.ubuntu.com intrepid Release.gpg                                                            
Ign http://archive.ubuntu.com intrepid/main Translation-en_US                                                  
Ign http://archive.ubuntu.com intrepid/universe Translation-en_US                                              
Ign http://debian.slimdevices.com stable/main Translation-en_US                                                
Hit http://packages.medibuntu.org intrepid Release.gpg                                                        
Get:1 http://debian.slimdevices.com stable Release [1645B]                                                    
Hit http://old-releases.ubuntu.com intrepid Release.gpg                                                        
Ign http://old-releases.ubuntu.com intrepid/main Translation-en_US                                            
Ign http://old-releases.ubuntu.com intrepid/restricted Translation-en_US                                      
Ign http://archive.ubuntu.com intrepid/multiverse Translation-en_US                                            
Ign http://archive.ubuntu.com replacements_debian Release.gpg                                                  
Ign http://archive.ubuntu.com replacements_debian/main Translation-en_US                                      
Ign http://archive.ubuntu.com intrepid Release                                                                
Ign http://debian.slimdevices.com stable/main Packages                                                        
Ign http://old-releases.ubuntu.com intrepid/universe Translation-en_US                                        
Ign http://old-releases.ubuntu.com intrepid/multiverse Translation-en_US                                      
Hit http://old-releases.ubuntu.com intrepid-security Release.gpg                                              
Ign http://old-releases.ubuntu.com intrepid-security/main Translation-en_US                                    
Ign http://old-releases.ubuntu.com intrepid-security/restricted Translation-en_US                              
Ign http://old-releases.ubuntu.com intrepid-security/multiverse Translation-en_US                              
Ign http://old-releases.ubuntu.com intrepid-security/universe Translation-en_US                                
Hit http://old-releases.ubuntu.com intrepid-updates Release.gpg                                                
Ign http://archive.ubuntu.com replacements_debian Release                                                      
Hit http://debian.slimdevices.com stable/main Packages                                                        
Ign http://old-releases.ubuntu.com intrepid-updates/main Translation-en_US                                    
Ign http://old-releases.ubuntu.com intrepid-updates/restricted Translation-en_US                              
Ign http://old-releases.ubuntu.com intrepid-updates/multiverse Translation-en_US                              
Ign http://packages.medibuntu.org intrepid/free Translation-en_US                                              
Ign http://deb.linuxmce.org intrepid Release.gpg                                                              
Ign http://deb.linuxmce.org intrepid/beta2 Translation-en_US                                                  
Ign http://archive.ubuntu.com intrepid/main Packages                                                          
Ign http://archive.ubuntu.com intrepid/universe Packages                                                      
Ign http://archive.ubuntu.com intrepid/multiverse Packages                                                    
Ign http://deb.linuxmce.org 20dev_ubuntu Release.gpg                                                          
Ign http://old-releases.ubuntu.com intrepid-updates/universe Translation-en_US                                
Hit http://old-releases.ubuntu.com intrepid Release                                                            
Hit http://old-releases.ubuntu.com intrepid-security Release                                                  
Ign http://deb.linuxmce.org 20dev_ubuntu/main Translation-en_US                                                
Ign http://deb.linuxmce.org intrepid Release                                                                  
Ign http://archive.ubuntu.com replacements_debian/main Packages                                                
Hit http://old-releases.ubuntu.com intrepid-updates Release                                                    
Ign http://packages.medibuntu.org intrepid/non-free Translation-en_US                                          
Ign http://deb.linuxmce.org 20dev_ubuntu Release                                                              
Err http://archive.ubuntu.com intrepid/main Packages                                                          
  404 Not Found [IP: 91.189.88.31 80]                                                                          
Err http://archive.ubuntu.com intrepid/universe Packages                                                      
  404 Not Found [IP: 91.189.88.31 80]                                                                          
Hit http://old-releases.ubuntu.com intrepid/main Packages                                                      
Hit http://old-releases.ubuntu.com intrepid/restricted Packages                                                
Hit http://old-releases.ubuntu.com intrepid/universe Packages                                                  
Hit http://old-releases.ubuntu.com intrepid/multiverse Packages                                                
Hit http://old-releases.ubuntu.com intrepid/main Sources                                                      
Hit http://old-releases.ubuntu.com intrepid/restricted Sources                                                
Hit http://old-releases.ubuntu.com intrepid/multiverse Sources                                                
Hit http://old-releases.ubuntu.com intrepid/universe Sources                                                  
Err http://archive.ubuntu.com intrepid/multiverse Packages                                                    
  404 Not Found [IP: 91.189.88.31 80]                                                                          
Ign http://deb.linuxmce.org intrepid/beta2 Packages                                                            
Hit http://old-releases.ubuntu.com intrepid-security/main Packages                                            
Hit http://old-releases.ubuntu.com intrepid-security/restricted Packages                                      
Hit http://old-releases.ubuntu.com intrepid-security/multiverse Packages                                      
Hit http://old-releases.ubuntu.com intrepid-security/universe Packages                                        
Hit http://old-releases.ubuntu.com intrepid-security/main Sources                                              
Hit http://old-releases.ubuntu.com intrepid-security/restricted Sources                                        
Hit http://old-releases.ubuntu.com intrepid-security/multiverse Sources                                        
Hit http://old-releases.ubuntu.com intrepid-security/universe Sources                                          
Hit http://old-releases.ubuntu.com intrepid-updates/main Packages                                              
Err http://archive.ubuntu.com replacements_debian/main Packages                                                
  404 Not Found [IP: 91.189.88.31 80]                                                                          
Ign http://deb.linuxmce.org 20dev_ubuntu/main Packages                                                        
Hit http://packages.medibuntu.org intrepid Release                                                            
Hit http://old-releases.ubuntu.com intrepid-updates/restricted Packages                                        
Hit http://old-releases.ubuntu.com intrepid-updates/multiverse Packages                                        
Hit http://deb.linuxmce.org intrepid/beta2 Packages                                                            
Hit http://old-releases.ubuntu.com intrepid-updates/universe Packages                                          
Hit http://old-releases.ubuntu.com intrepid-updates/main Sources                                              
Hit http://old-releases.ubuntu.com intrepid-updates/restricted Sources                                        
Hit http://old-releases.ubuntu.com intrepid-updates/multiverse Sources                                        
Hit http://old-releases.ubuntu.com intrepid-updates/universe Sources                                          
Hit http://deb.linuxmce.org 20dev_ubuntu/main Packages                                                        
Hit http://packages.medibuntu.org intrepid/free Packages                                                      
Hit http://packages.medibuntu.org intrepid/non-free Packages                                                  
Fetched 1B in 2s (0B/s)                                                                                        
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/intrepid/main/binary-i386/Packages.gz  404 Not Found [IP: 91.189.88.31 80]                                                                                            

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/intrepid/universe/binary-i386/Packages.gz  404 Not Found [IP: 91.189.88.31 80]                                                                                        

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/intrepid/multiverse/binary-i386/Packages.gz  404 Not Found [IP: 91.189.88.31 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/replacements_debian/main/binary-i386/Packages.gz  404Not Found [IP: 91.189.88.31 80]

E: Some index files failed to download, they have been ignored, or old ones used instead.
js@dcerouter:~$

Title: Re: 1wire support
Post by: Techstyle on February 06, 2012, 06:03:06 am
I can report that mine is now working.

I did deleted the device and then re-added it.  I had other issues I was trying to solve so a couple of reboots happened over the next 24hrs but now the temp sensor is showing the temp
Title: Re: 1wire support
Post by: twodogs on February 07, 2012, 05:07:42 am
I deleted and re-added this morning. Nothin. Not sure that libowfs ever loaded. Any idea where it should be?
Title: Re: 1wire support
Post by: DragonK on February 07, 2012, 07:03:37 am
Maybe try and add another device in the webadmin.
Like a CM15A or something. Mine and Techstyle's started working while adding or fixing something else........
Title: Re: 1wire support
Post by: hari on February 07, 2012, 06:26:14 pm
Thanks DragonK - that's good to know. The temp sensor has been in all night and has not appeared as a child yet. Hari, I'll be patient but why does it take so long?
it does not take long, the child is created as soon as it is detected on the 1wire bus. That happens within seconds.
Title: Re: 1wire support
Post by: twodogs on February 07, 2012, 08:50:06 pm
Is there a way to check the existence of libowfs and force it to load?
Title: Re: 1wire support
Post by: mkbrown69 on February 07, 2012, 10:33:12 pm
TwoDogs,

To check for it from command-line, on the core issue

dpkg --get-selections | grep libowfs

If you get nothing from that, issue

sudo apt-get install libowfs27

HTH!

/Mike
Title: Re: 1wire support
Post by: DragonK on February 08, 2012, 06:59:53 am
it does not take long, the child is created as soon as it is detected on the 1wire bus. That happens within seconds.

Hari,

it was a mission to get the first sensor up and running.
1. I added the Interface in Webadmin.
2. Waited. Reloaded and rebooted.
3. Even left the core for 24hours reloaded and rebooted. Still no sensor.

So I left it and added an MD to my system. Relaoded the router when asked, and then I noticed the temp sensor was added.
The second and third sensors were detected and added allmost immediately though.

Karel
Title: Re: 1wire support
Post by: Techstyle on February 08, 2012, 06:20:14 pm
DragonK,

you are right it seems to be a mission to get the sensor loaded but I noticed (and other have too) that some of the software did fail to load/install the first time around.  On the reboot after adding my HDD back in I noticed the libowfs package downloading and installing, only after this point did I see a child added and the device listed as 'registered: yes'

I had previously run "apt-get update && apt-get install libowfs27" per Hari's instructions but to no avail.  I was getting errors associated with radvd after running the command that hari suggested.  I did the fix (removed the 'blank line 2') and run apt-get update and apt-get upgrade.  I don't think I ran apt-get install libowfs27 again though.

twodogs,
if you run apt-get update do you get an radvd.conf error?

DragonK,
have you added a second sensor? how quick is that found?

I am thinking about starting a new thread to get some discussion going on 1-wire deployment - for instance I am thinking of running the 1-wire network within a Cat5e cable along with my POTS and would like to know how others are doing it
Title: Re: 1wire support
Post by: huh on February 08, 2012, 07:07:43 pm
I have mine (1wire usb and temp sensors) scheduled for delivery today from ibuttonlink that twodogs linked above.  I'm running 1004 with all but the updates released today.  I was going to apt-get update && apt-get upgrade before plugging in the device to see if I have the same experiences. 

I ran this command last night:
Code: [Select]
dpkg --get-selections | grep libowfs
And as expected do not have libowfs installed as I currently dont' have any 1wire devices.

Is there anything else someone would like me to try before I plug in the device?  Or any log files to tail to watch for errors?
Title: Re: 1wire support
Post by: twodogs on February 08, 2012, 07:39:57 pm
Looks like the packages are installed. I've tried to delete and re-add 1-wire, but womb is still barren - no children at all. The update gave me some errors that don't look like they concern 1-wire, but then again who knows? My 1-wire adapter is still showing unregistered after several hours. It had registered before, but I don't know how long it took.

Code: [Select]
js@dcerouter:~$ dpkg --get-selections | grep libowfs
libowfs27                                       install
js@dcerouter:~$ dpkg --get-selections | grep fuseowfs
fuseowfs                                        install
js@dcerouter:~$ sudo apt-get update                    
blah...
blah...
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/intrepid/main/binary-i386/Packages.gz  404 Not Found [IP: 91.189.92.171 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/intrepid/universe/binary-i386/Packages.gz  404 Not Found [IP: 91.189.92.171 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/intrepid/multiverse/binary-i386/Packages.gz  404 Not Found [IP: 91.189.92.171 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/replacements_debian/main/binary-i386/Packages.gz  404 Not Found [IP: 91.189.92.171 80]

E: Some index files failed to download, they have been ignored, or old ones used instead.
js@dcerouter:~$
Title: Re: 1wire support
Post by: DragonK on February 09, 2012, 06:51:21 am
DragonK,
have you added a second sensor? how quick is that found?

I have 3 sensors and the second and third showed up as childs within a minute or two.
Title: Re: 1wire support
Post by: hari on February 09, 2012, 10:38:51 pm
when you add the interface to the core, it of course needs a quick reload to start the OneWire DCE device. When this is started, it iterates over all temperature devices found by owfs and tells the general info plugin to create the child device if it does not yet exist. These won't be active till the next quick reload. Maybe that adds to confusion?
Title: Re: 1wire support
Post by: DragonK on February 10, 2012, 08:15:56 am
when you add the interface to the core, it of course needs a quick reload to start the OneWire DCE device. When this is started, it iterates over all temperature devices found by owfs and tells the general info plugin to create the child device if it does not yet exist. These won't be active till the next quick reload. Maybe that adds to confusion?

So the steps are?


Karel
Title: Re: 1wire support
Post by: Gangsingen on February 10, 2012, 02:55:21 pm
So the steps are?

  • Connect 1wire interface to core
  • Add the 1wire interface in webadmin using template 2161
  • Select the port the 1wire interface is connected to
  • When prompted do a quick reload
  • Once the sensors are detected, another quick reload is needed
  • Now you should have Multilevel Sensors as childs, for every sensor connected to the 1wire bus, in the webadmin
  • Choose the rooms that the sensors are in and add to the floorplan.
  • Another Quick reload should do the job

Karel

Spot on, that exactly how I got mine working!
Title: Re: 1wire support
Post by: twodogs on February 10, 2012, 03:07:11 pm
When do you see the interface show "registered" in LMCE admin?
Where in the sequence do you plug the sensor/s into the interface adapter?
Title: Re: 1wire support
Post by: Techstyle on February 10, 2012, 05:47:43 pm
Do you have to regen the orbiters?
Title: Re: 1wire support
Post by: Techstyle on February 11, 2012, 06:35:15 am
Does anybody know how to display the Temp in Deg F instead of C?
Title: Re: 1wire support
Post by: huh on February 11, 2012, 08:43:44 am
If you go into the web admin pages -> show devices tree -> 1wire and then click on "view whole log", I have a couple errors:

Code: [Select]
01 02/11/12 1:33:42.167 TranslateSerialUSB pci0000:00/0000:00:13.0+1 result /dev/ttyUSB2 <0xb78686d0>
01 02/11/12 1:33:42.167 Opening port: /dev/ttyUSB2 <0xb78686d0>>

lsusb gives me this:
Code: [Select]
Bus 005 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC

dmesg gives me this:
Code: [Select]
[  785.564300] ftdi_sio 5-1:1.0: FTDI USB Serial Device converter detected
[  785.564371] usb 5-1: Detected FT232RL
[  785.564376] usb 5-1: Number of endpoints 2
[  785.564381] usb 5-1: Endpoint 1 MaxPacketSize 64
[  785.564386] usb 5-1: Endpoint 2 MaxPacketSize 64
[  785.564390] usb 5-1: Setting MaxPacketSize 64
[  785.566328] usb 5-1: FTDI USB Serial Device converter now attached to ttyUSB2

Any idea why my temperature probes aren't discovered?
Title: Re: 1wire support
Post by: hari on February 11, 2012, 12:19:42 pm
if you can't even read them out with owfs, you probably have a short circuit on the bus.. this happened to another user. So as a first debug step I'd recommend to see if owfs gives you values. If that works fine, continue to debug on the lmce side
Title: Re: 1wire support
Post by: Gangsingen on February 11, 2012, 02:24:21 pm
Where in the sequence do you plug the sensor/s into the interface adapter?

I had mine plugged in all the time!
Title: Re: 1wire support
Post by: huh on February 12, 2012, 06:32:56 am
if you can't even read them out with owfs, you probably have a short circuit on the bus..

How else do I check for this?  I have (2) of the LinkUSBi's, (5) temperature sensors and a pile of cat5 cables...  tried both LinkUSBi's and 3 of the temperature sensors.  The usb device appears in the log file as posted above, but cannot get my temperature sensors to load.

Thanks

Edit:
I tried adding a MD to see if I had the same experiences as others- that the sensors would start populating.  Unfortunately, it's been 6+ hours and while my device is spawned, no such luck with the sensors:
Code: [Select]
1 02/12/12 20:14:23 124 (spawning-device) Starting... 1
1 02/12/12 20:14:23 124 (spawning-device) Found /usr/pluto/bin/OneWire
01 02/12/12 20:14:24.280 TranslateSerialUSB pci0000:00/0000:00:12.0+2 result /dev/ttyUSB2 <0xb76e96d0>
01 02/12/12 20:14:24.280 Opening port: /dev/ttyUSB2 <0xb76e96d0>
Title: Re: 1wire support
Post by: huh on February 13, 2012, 05:20:22 am
OK- tried something new-

Added:  deb http://mirrors.rit.edu/ubuntu/ precise main universe to my sources by added it to here:
Code: [Select]
nano /etc/apt/sources.list

Then, started the owserver using this:
Code: [Select]
owserver --device=/dev/ttyUSB2 -p 4304

Then, started the owhttpd web client using this which creates a webpage on port 3000:
Code: [Select]
owhttpd -s localhost:4304 -p 3000

Most of the instructions are from here:
http://www.openremote.org/display/docs/OpenRemote+2.0+How+To+-+1-Wire+Sensors (http://www.openremote.org/display/docs/OpenRemote+2.0+How+To+-+1-Wire+Sensors)

The webpage shows (1) sensor with a temperature, so I got greedy and added another (2) to make sure it was working... unfortunately it still only says I have (1) thermocouple attached after restarting my core.

Edit:  Leaving breadcrumbs...  much quicker than core reboot...

You can kill a process using the follow:
Code: [Select]
/usr/pluto/bin/ForciblyKillProcess.sh OneWire

And restart using
Code: [Select]
/usr/pluto/bin/Spawn_Device.sh 124
Where 124 is MY device id- yours is likely different...
Title: Re: 1wire support
Post by: hari on February 13, 2012, 11:18:16 pm
you can't run them in parallel, you need to stop the owserver first
Title: Re: 1wire support
Post by: huh on February 17, 2012, 07:03:27 am
OK- I blew away my system and tried again.  I followed exactly per the wiki and was surprised when one after another sensors were added to my 1-wire device... until number 5.  At number 5 the device died (per the log) and I could not get it to restart- either manually or by restarting the computer.

So, I deleted that device and created a new 1-wire device again following the wiki.  Whereas before the temperature sensor was found after a few minutes- now been 30 minutes or so and no luck...  Per the log it looks like everything started correctly and per dmesg I'm set to the correct USB port...

Going to let it run overnight.

Edit:  As a side now- although I have run Diskless_CreateTBZ.sh, I have not yet installed a MD.  I have (2) qorbiters and a web orbiter configured along with the core.  Also have a USBUIRT and a gyration remote installed.
Title: Re: 1wire support
Post by: huh on February 17, 2012, 04:51:25 pm
Going to let it run overnight.

No luck...  devices did not appear.  I'm going to reinstall from scratch and this time leave out everything except the bare minimum (removing the USBUIRT, gyration remote, zwave and hauppauge cards)...

Any other suggestions for debugging?  The device worked initially and I didn't really move the wires around, so pretty confident there isn't a short.

Title: Re: 1wire support
Post by: hari on February 18, 2012, 12:13:27 pm
i'd be quite interested in the core dump from the event when it died after recognizing the 5th event, can you upload it somewhere?
Title: Re: 1wire support
Post by: hari on February 18, 2012, 12:14:18 pm
btw if you visit us in #linuxmce-devel on freenode we can run a debug session tonight (CET)
Title: Re: 1wire support
Post by: huh on March 03, 2012, 01:47:27 am
No idea what happened...  reinstalled LMCE a couple times since previous posts and currently have an install where the 1wire was discovered as discussed in the wiki.  I wasn't expecting the child to be found, so wasn't really paying attention to the time between plugging in the sensor and when the log file discovered the device.  Thinking back, I probably should have checked the time stamps.  duh.  If I were to guess, probably 10 minutes or so.

For the sake of a record, I have this device:  http://www.ibuttonlink.com/linkusbi.aspx   (LinkUSBi if the URL changes) and five of their temperature sensors:  http://www.ibuttonlink.com/t-sense.aspx

All (5) sensors were detected as children and were approximately reading the same temperature...  so, I've gone and started to play with it.  Currently removed all but (1) sensor which I put in my attic.  I've rotated the sensors out to see what would happen and it appears that the temperature reported remains static on the "missing" thermistors.  Very cool that it appears that the rest continue to function properly when one is lost.