Author Topic: 1wire support  (Read 21983 times)

DragonK

  • Guru
  • ****
  • Posts: 429
    • View Profile
Re: 1wire support
« Reply #45 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

_if_

  • Guru
  • ****
  • Posts: 238
    • View Profile
Re: 1wire support
« Reply #46 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

DragonK

  • Guru
  • ****
  • Posts: 429
    • View Profile
Re: 1wire support
« Reply #47 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

_if_

  • Guru
  • ****
  • Posts: 238
    • View Profile
Re: 1wire support
« Reply #48 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...

Techstyle

  • Addicted
  • *
  • Posts: 674
    • View Profile
    • Techstyle UK Ltd.
Re: 1wire support
« Reply #49 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

This is the device I am using

_if_

  • Guru
  • ****
  • Posts: 238
    • View Profile
Re: 1wire support
« Reply #50 on: February 25, 2011, 06:39:09 am »
Hi,

the interface uses DS9097U...

thanks
IF

Kezza

  • Veteran
  • ***
  • Posts: 146
    • View Profile
Re: 1wire support
« Reply #51 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

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: 1wire support
« Reply #52 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"
rock your home - http://www.agocontrol.com home automation

Kezza

  • Veteran
  • ***
  • Posts: 146
    • View Profile
Re: 1wire support
« Reply #53 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#

_if_

  • Guru
  • ****
  • Posts: 238
    • View Profile
Re: 1wire support
« Reply #54 on: February 26, 2011, 09:21:09 pm »
I believe owfs should be existing and running, is that right Hari?

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: 1wire support
« Reply #55 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
rock your home - http://www.agocontrol.com home automation

_if_

  • Guru
  • ****
  • Posts: 238
    • View Profile
Re: 1wire support
« Reply #56 on: February 27, 2011, 10:38:11 am »
ok thanks, and how would I find out the sensors ID then?

Kezza

  • Veteran
  • ***
  • Posts: 146
    • View Profile
Re: 1wire support
« Reply #57 on: February 27, 2011, 10:53:48 am »
If you can track down a windows machine this is what I used

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

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

_if_

  • Guru
  • ****
  • Posts: 238
    • View Profile
Re: 1wire support
« Reply #58 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

_if_

  • Guru
  • ****
  • Posts: 238
    • View Profile
Re: 1wire support
« Reply #59 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]