Peter Hollenbeck | 21 May 2013 17:40
Picon

How to display owfs degugging information

sudo owfs -u -m /weather/1wire
starts but /weather/1wire is empty.

Device is:
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC

Is there a way to display debugging information?

Thank you,
Peter

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Gregg Levine | 21 May 2013 01:51
Picon

Raspberry PI and OWFS

Hello!
I've had one of these amazing devices since the end of last year.
However this is my first real chance to try and get something running
on it, and doing something, since the beginning of the year.

So earlier I put on the latest release of the kit available from the
repositories for the thing. And after the usual efforts to get it to
work seeing my DS9097U connected via an FTDI based adapter, I now see
the file-system it creates present in the chosen directory.
----
The chosen device for all of this will be a DS2406.
-----
Is there an easy method for bringing up the webserver for everything
on the Raspberry Pi?
----
Remember this is all an experimental process so ideally I'm not
planning doing anything special.
----
Gregg C Levine gregg.drwho8 <at> gmail.com
"This signature fought the Time Wars, time and again."

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
Peter Hollenbeck | 17 May 2013 19:32
Picon

Connecting to a DS2438

To use it as a voltage sensor, is it just a matter of connecting the one wire bus and the voltage leads to be sensed? Or is other circuitry required?

Thank you for your input.
Peter

------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Peter Hollenbeck | 16 May 2013 16:59
Picon

Compile with USB Support

Ubuntu 10

./configure --enable-usb
make
sudo make install

/opt/owfs/bin/owfs -u -m 1wire
returns:
DEFAULT: ow_arg.c:(466) USB support (intentionally) not included in compilation. Check LIBUSB, then reconfigure and recompile.

I have tried and tried but, being quite old and not so bright, can't figure out how to fix this.

sudo find / -name libusb returns:

/lib/i386-linux-gnu/libusb-0.1.so.4.4.4
/lib/i386-linux-gnu/libusb-0.1.so.4
/lib/i386-linux-gnu/libusb-1.0.so.0.1.0
/var/lib/dpkg/info/libusb-0.1-4:i386.postinst
/var/lib/dpkg/info/libusbmuxd1.postinst
/var/lib/dpkg/info/libusbmuxd1.md5sums
/var/lib/dpkg/info/libusbmuxd1.symbols
/var/lib/dpkg/info/libusb-1.0-0:i386.postrm
/var/lib/dpkg/info/libusbmuxd1.list
/var/lib/dpkg/info/libusb-1.0-0:i386.md5sums
/var/lib/dpkg/info/libusbmuxd1.postrm
/var/lib/dpkg/info/libusb-0.1-4:i386.md5sums
/var/lib/dpkg/info/libusb-0.1-4:i386.shlibs
/var/lib/dpkg/info/libusb-0.1-4:i386.postrm
/var/lib/dpkg/info/libusb-1.0-0:i386.list
/var/lib/dpkg/info/libusb-0.1-4:i386.list
/var/lib/dpkg/info/libusb-1.0-0:i386.postinst
/var/lib/dpkg/info/libusb-0.1-4:i386.symbols
/var/lib/dpkg/info/libusbmuxd1.shlibs
/var/lib/dpkg/info/libusb-1.0-0:i386.shlibs
/usr/local/include/libusb-1.0
/usr/local/include/libusb-1.0/libusb.h
/usr/local/lib/libusb-1.0.so.0
/usr/local/lib/libusb-1.0.la
/usr/local/lib/pkgconfig/libusb-1.0.pc
/usr/local/lib/libusb-1.0.a
/usr/local/lib/libusb-1.0.so.0.1.0
/usr/local/lib/libusb-1.0.so
/usr/lib/i386-linux-gnu/libusb-1.0.so.0
/usr/lib/libusbmuxd.so.1
/usr/lib/libusbmuxd.so.1.0.7
/usr/share/doc/libusbmuxd1
/usr/share/doc/libusb-0.1-4
/usr/share/doc/libusb-1.0-0

I sure would appreciate help.
Thank you,
Peter



------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Egger Clemens | 16 May 2013 10:56

Compiling issues on Cygwin

Hi,

When compiling OWFS on a freshly installed Cygwin system I get the following errors during make.
I'm using owfs-2.9p0, gcc (GCC) 4.5.3 on CYGWIN_NT-6.1 HOST1 1.7.18(0.263/5/3) 2013-04-19 10:39 i686 Cygwin.
As a workaround I changed the corresponding preprocessor statement from __GNUC_MINOR__ being greater
than 4 to being greater than 5 and it compiles fine, however I don't really know much about the #pragma GCC
diagnostic so maybe anyone knows a better way to solve this problem.

Error Messages:
[...]
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../../../src/include -I../include -fexceptions
-Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes
-Wredundant-decls -D__EXTENSIONS__ -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1
-D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -g -O2 -mwin32 -g -D_XOPEN_SOURCE=500
-D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -MT ownet_write.lo -MD -MP -MF
.deps/ownet_write.Tpo -c ownet_write.c -o ownet_write.o >/dev/null 2>&1
mv -f .deps/ownet_dir.Tpo .deps/ownet_dir.Plo
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../../../src/include -I../include -fexceptions
-Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes
-Wredundant-decls -D__EXTENSIONS__ -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1
-D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -g -O2 -mwin32 -g -D_XOPEN_SOURCE=500
-D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -MT ownet_present.lo -MD -MP -MF
.deps/ownet_present.Tpo -c ownet_present.c -o ownet_present.o >/dev/null 2>&1
ow_server.c: In function 'ServerWrite':
ow_server.c:143:9: error: #pragma GCC diagnostic not allowed inside functions
ow_server.c:144:9: error: #pragma GCC diagnostic not allowed inside functions
ow_server.c:145:9: warning: cast discards qualifiers from pointer target type
ow_server.c:146:9: error: #pragma GCC diagnostic not allowed inside functions
ow_server.c: In function 'WriteToServer':
ow_server.c:507:9: error: #pragma GCC diagnostic not allowed inside functions
ow_server.c:508:9: error: #pragma GCC diagnostic not allowed inside functions
ow_server.c:509:3: warning: cast discards qualifiers from pointer target type
ow_server.c:510:9: error: #pragma GCC diagnostic not allowed inside functions
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../../../src/include -I../include -fexceptions
-Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes
-Wredundant-decls -D__EXTENSIONS__ -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1
-D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -g -O2 -mwin32 -g -D_XOPEN_SOURCE=500
-D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -MT ow_rwlock.lo -MD -MP -MF
.deps/ow_rwlock.Tpo -c ow_rwlock.c -o ow_rwlock.o >/dev/null 2>&1
Makefile:547: recipe for target `ow_server.lo' failed
make[5]: *** [ow_server.lo] Error 1
make[5]: *** Waiting for unfinished jobs....
mv -f .deps/ownet_init.Tpo .deps/ownet_init.Plo
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../../../src/include -I../include -fexceptions
-Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes
-Wredundant-decls -D__EXTENSIONS__ -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1
-D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -g -O2 -mwin32 -g -D_XOPEN_SOURCE=500
-D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -MT ow_tcp_read.lo -MD -MP -MF
.deps/ow_tcp_read.Tpo -c ow_tcp_read.c -o ow_tcp_read.o >/dev/null 2>&1
mv -f .deps/ownet_read.Tpo .deps/ownet_read.Plo
mv -f .deps/ownet_present.Tpo .deps/ownet_present.Plo
mv -f .deps/ownet_write.Tpo .deps/ownet_write.Plo
mv -f .deps/ownet_setget.Tpo .deps/ownet_setget.Plo
mv -f .deps/ow_rwlock.Tpo .deps/ow_rwlock.Plo
mv -f .deps/ow_tcp_read.Tpo .deps/ow_tcp_read.Plo
make[5]: Leaving directory `/home/cegger/devel/owfs-2.9p0/module/ownet/c/src/c'
Makefile:413: recipe for target `all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home/cegger/devel/owfs-2.9p0/module/ownet/c/src'
Makefile:410: recipe for target `all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/cegger/devel/owfs-2.9p0/module/ownet/c'
Makefile:414: recipe for target `all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/cegger/devel/owfs-2.9p0/module/ownet'
Makefile:424: recipe for target `all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/cegger/devel/owfs-2.9p0/module'
Makefile:469: recipe for target `all-recursive' failed
make: *** [all-recursive] Error 1

best regards
Clemens Egger

------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
Jan Chrillesen | 14 May 2013 08:17
Picon

owfs not able to connect to owserver when using owfs.conf

Hi,

I have an issue with owfs not being able to use owserver when reading
config from owfs.conf:

$ cat /etc/owfs.conf
server: device = /dev/i2c-1
server: port = localhost:3000

mountpoint = /mnt/1wire
allow_other
http: port = 8080

error_print = 1
error_level = 3

$ sudo /opt/owfs/bin/owserver -c /etc/owfs.conf --pid-file
/var/run/owfs/owserver.pid

Syslog:

May 14 08:00:34 rpi OWFS[4456]: DEFAULT: ow_daemon.c:(144) Entered
background mode, quitting.
May 14 08:00:34 rpi OWFS[4456]:    CALL: ow_parsename.c:(98) path=[]
May 14 08:00:34 rpi OWFS[4456]: CONNECT: ow_ds2482.c:(399) Found an i2c
device at /dev/i2c-1 address 18
May 14 08:00:34 rpi OWFS[4456]: CONNECT: ow_ds2482.c:(428) i2c device at
/dev/i2c-1 address 18 appears to be DS2482-x00
May 14 08:00:34 rpi OWFS[4456]: CONNECT: ow_ds2482.c:(692) DS2482-100
(Single channel)

$ sudo /opt/owfs/bin/owfs -c /etc/owfs.conf --pid-file
/var/run/owfs/owfs.pid

Syslog:

May 14 08:01:40 rpi OWFS[4461]: CONNECT: owfs.c:(96) fuse mount point:
/mnt/1wire
May 14 08:01:40 rpi OWFS[4461]:    CALL: ow_parsename.c:(98) path=[]
May 14 08:01:40 rpi OWFS[4461]: DEFAULT: owlib.c:(56) No valid 1-wire
buses found

$ netstat -an | grep 3000
tcp6       0      0 ::1:3000                :::*                    LISTEN

So, owserver reads owfs.conf and locates the busmaster and starts up on
port 3000. owfs is not able to find the busmaster

If I start things without owfs.conf it works fine:

$ sudo /opt/owfs/bin/owserver --i2c=/dev/i2c-1 -p localhost:3000
--pid-file /var/run/owfs/owserver.pid

$ netstat -an | grep 3000
tcp6       0      0 ::1:3000                :::*                    LISTEN

$ sudo /opt/owfs/bin/owfs -s 3000 /mnt/1wire --pid-file
/var/run/owfs/owfs.pid

$ sudo ls /mnt/1wire
bus.0  settings  statistics  structure  system  uncached

This is owfs 2.9 on a Raspberry Pi model A, using a DS2483 as a
busmaster. To make things even more weird the same setup works fine with
a DS2482-800 on a Raspberry Pi model B, so I'm starting to wonder if
this is an issue with either the DS2483 or RPI model A.

Any suggestions on how to debug this issue further?

- Jan

------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
Walter Lewis | 14 May 2013 01:07
Picon

owfs hangup on Linux 3.0.4 using DS28EC20 Dallas 1-wire EEPROM

Greetings, 

I am implementing a Maxim 1-Wire DS28EC20 EEPROM on an embedded Linux
application with the objective of writing identification information and
manufacturing data on a removable component.  I have configured the kernel
for 1-Wire support, and have applied the patch for the w1-gpio module
implementation. When I insert the w1-gpio module, the /sys/bus/w1 directory
becomes present and the target EEPROM is reported.  There is a file present
named rw which I can cat (looks binary), but when I pipe data to it, and
then read it back, it does not change. I suspect the block nature of the
device and its control mechanisms require a more sophisticated write
operation. I investigated the owfs which supports read and write on the
DS_2433 EEPROM, and am attempting to implement it.  When I do not have the
device attached, using owfs, I can 'ls' the owfs mount point.  When a device
is attached and the Linux w1 directory (/sys/bus/w1/...) shows it, a 'ls'
command on the owfs mount point causes the owfs application to become
unresponsive and the ls command never completes. owfs in background mode
does not respond to a control C and requires a kill -9 to stop, and once
stopped, the ownership and permissions of the owfs mountpoint appear
corrupted.  A power cycle restores the mount point. owfs in forground mode
does respond to control C and leaves the ownership and permissions in a sane
state.

In order to isolate the problem, I have attempted this implementation using
owfs with the w1_kernel module and a file system mountpoint; owhttpd with
the w1 kernel module and a web page display; and with a owserver with w1
kernel module and a socket connection paired with a owhttpd server attached
to the socket connection and a web page display. None of these combinations
has solved the hang up condition and output is not to the file system or web
page. The 'looking for directory and directory not found' errors occur in
owfs, owhttpd and owserver when the component becomes visible to the kernel.
I have also tried this with DS2431 EEPROM with the same results.

Below is my system information.  To get to the place where the error occurs,
search for: **** ERROR *** . Also, note that the looking for directory and
directory not found errors occur in owhttpd and owserver when the component
becomes visible to the kernel.

Thank you in advance for your help and assistance.  Please let me know if
you need more information or have something you would like me to try.

Walter,

Details:

My target system is a Vendor's TI Omap 4460 based System On a Module,
running the omap linux kernel version 3.0.4 (uname -a: Linux <HOST>
3.4.0-1489-omap4 #26~Custom SMP PREEMPT Sat May 11 10:56:25 CDT 2013 armv7l
armv7l armv7l GNU/Linux.  I cannot advance this kernel revision until our
Vendor supports a newer version. This is cross compiled from a Ubuntu
development system, (uname -a: Linux <host> 3.2.0-41-generic #66-Ubuntu SMP
Thu Apr 25 03:27:11 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux) with the
'arm-linux-gnueabihf' cross compiler.

My kernel configuration options are:
(1-Wire)
    CONFIG_W1=m
    CONFIG_W1_CON=y
    CONFIG_W1_MASTER_DS1WM=m
    CONFIG_W1_MASTER_DS2482=m
    CONFIG_W1_MASTER_DS2490=m
    CONFIG_W1_MASTER_GPIO=m
    CONFIG_W1_SLAVE_BQ27000=m
    CONFIG_W1_SLAVE_DS2408=m
    CONFIG_W1_SLAVE_DS2423=m
    CONFIG_W1_SLAVE_DS2431=m
    CONFIG_W1_SLAVE_DS2433=m
    # CONFIG_W1_SLAVE_DS2433_CRC is not set
    CONFIG_W1_SLAVE_DS2760=m
    CONFIG_W1_SLAVE_DS2780=m
    # CONFIG_W1_SLAVE_DS2781 is not set
    CONFIG_W1_SLAVE_SMEM=m
    CONFIG_W1_SLAVE_THERM=m
(Fuse)
    CONFIG_FUSE_FS=y

I installed owfs by:
Downloading from SourceForge, the latest version of owfs
(owfs-2.9p0.tar.gz), and copied it to the target system.
Logged in as root on the target system, I:
    expanded the download package on the target system, ran configure, make,
and make install.  
    owfs was missing because the fuse.h file could not be found.  
    I ran apt-get install libfuse-dev
    I deleted the unzipped owfs directory, and performed the installation
again.  This was successful.

I inserted the w1 modules using modprobe.  I have tried this with w1-gpio (+
wire); w1_ds2433 (+ wire); and w1_gpio and w1_ds2433 (+wire).  According to
the Maxim datasheet, the DS28EC20 is highly backwards compatible with the
2433 part.

As described above, when the part is attached, the kernel shows the part's
presence, bit the owfs mount point hangs up when attempting to display it.

Case 1: owfs implementation

Kernel /sys/bus without modules does not include a w1 directory

Load modules ---
10.20.30.41:/tmp# modprobe w1_gpio
10.20.30.41:/tmp# modprobe w1_ds2433
10.20.30.41:/tmp# lsmod | grep w
w1_ds2433               2233  0 
w1_gpio                 1645  0 
wire                   26865  2 w1_ds2433,w1_gpio

Kernel /sys/bus after loading modules includes a w1 directory
10.20.30.41:/tmp# ls /sys/bus/w1
total 0
drwxr-xr-x  4 root root    0 May 13 19:32 .
drwxr-xr-x 21 root root    0 Jan  1  2000 ..
drwxr-xr-x  2 root root    0 May 13 19:32 devices
drwxr-xr-x  4 root root    0 May 13 19:32 drivers
-rw-r--r--  1 root root 4.0K May 13 19:32 drivers_autoprobe
--w-------  1 root root 4.0K May 13 19:32 drivers_probe
--w-------  1 root root 4.0K May 13 19:32 uevent
10.20.30.41:/tmp# ls /sys/bus/w1/devices/
total 0
drwxr-xr-x 2 root root 0 May 13 19:32 .
drwxr-xr-x 4 root root 0 May 13 19:32 ..
lrwxrwxrwx 1 root root 0 May 13 19:33 w1_bus_master1 ->
../../../devices/w1_bus_master1

After attaching the 1-Wire EEPROM
10.20.30.41:/tmp# ls /sys/bus/w1/devices/
total 0
drwxr-xr-x 2 root root 0 May 13 19:32 .
drwxr-xr-x 4 root root 0 May 13 19:32 ..
lrwxrwxrwx 1 root root 0 May 13 19:34 43-0000003be97b ->
../../../devices/w1_bus_master1/43-0000003be97b
lrwxrwxrwx 1 root root 0 May 13 19:33 w1_bus_master1 ->
../../../devices/w1_bus_master1

Removed the 1-Wire EEPROM

owfs mount point without EEPROM present or owfs running

10.20.30.41:/tmp# ls /mnt
total 5.0K
drwxr-xr-x  5 root root 1.0K May 13 19:37 .
drwxr-xr-x 23 root root 1.0K May 13 11:33 ..
drwxr-xr-x  2 root root 1.0K Mar 31 19:35 jj
drwxr-xr-x  2 root root 1.0K Oct  9  2012 sda1
drwxr-xr-x  2 root root 1.0K May 13 14:31 w1
10.20.30.41:/tmp# ls /mnt/w1
total 2.0K
drwxr-xr-x 2 root root 1.0K May 13 14:31 .
drwxr-xr-x 5 root root 1.0K May 13 19:37 ..

Run owfs with debugging enabled
10.20.30.41:/tmp# owfs --foreground --error_level=9 --w1 -m /mnt/w1
CONNECT: owfs.c:(96) fuse mount point: /mnt/w1
CONNECT: ow_avahi_link.c:(68) No Avahi support. Library libavahi-client
couldn't be loaded
CONNECT: ow_dnssd.c:(82) Zeroconf/Bonjour is disabled since dnssd library
isn't found
   CALL: ow_parsename.c:(98) path=[]
  DEBUG: owlib.c:(81) Globals temp limits 0C 100C (for simulated adapters)
  DEBUG: fuse_line.c:(82) Added FUSE option 0 OWFS
  DEBUG: fuse_line.c:(82) Added FUSE option 1 /mnt/w1
  DEBUG: fuse_line.c:(82) Added FUSE option 2 -o
  DEBUG: fuse_line.c:(82) Added FUSE option 3 direct_io
  DEBUG: fuse_line.c:(82) Added FUSE option 4 -f
  DEBUG: fuse_line.c:(82) Added FUSE option 5 -d
  DEBUG: owfs.c:(121) fuse_mnt_opt=[(null)]
  DEBUG: owfs.c:(123) fuse_open_opt=[(null)]
  DEBUG: ow_w1_list.c:(54) Sending w1 bus master list message
  DEBUG: ow_w1_send.c:(132) Netlink send -----------------
NLMSGHDR: len=48 type=3 (NLMSG_DONE) flags=5 seq=0|1 pid=2921
CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=0|1 ack=1 len=12 flags=0
W1_NETLINK_MSG: type=6 (W1_LIST_MASTERS) len=0 id=0
W1_NETLINK_CMD: NULL w1c field
NULL data
  DEBUG: ow_w1_send.c:(143) NETLINK sent seq=1
  DEBUG: ow_w1_dispatch.c:(173) Dispatch loop
  DEBUG: ow_w1_parse.c:(113) Wait to peek at message
  DEBUG: ow_w1_parse.c:(121) Pre-parse header: 16 bytes len=52 type=3
seq=0|1 pid=0
  DEBUG: ow_w1_parse.c:(142) Netlink read -----------------
NLMSGHDR: len=52 type=3 (NLMSG_DONE) flags=0 seq=0|1 pid=0
CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=0|1 ack=0 len=16 flags=12141
W1_NETLINK_MSG: type=6 (W1_LIST_MASTERS) len=4 id=1768713839
W1_NETLINK_CMD: NULL w1c field
Byte buffer Data, length=4
--000: 01 00 00 00
   <....>
  DEBUG: ow_w1_dispatch.c:(88) Netlink message directed to root W1 master
  DEBUG: ow_w1_dispatch.c:(126) Sending this packet to root bus
  DEBUG: ow_w1_dispatch.c:(173) Dispatch loop
  DEBUG: ow_w1_parse.c:(113) Wait to peek at message
  DEBUG: ow_w1_parse.c:(121) Pre-parse header: 16 bytes len=48 type=3
seq=0|1 pid=0
  DEBUG: ow_w1_parse.c:(142) Netlink read -----------------
NLMSGHDR: len=48 type=3 (NLMSG_DONE) flags=0 seq=0|1 pid=0
CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=0|1 ack=1 len=12 flags=0
W1_NETLINK_MSG: type=6 (W1_LIST_MASTERS) len=0 id=0
W1_NETLINK_CMD: NULL w1c field
NULL data
  DEBUG: ow_w1_dispatch.c:(88) Netlink message directed to root W1 master
  DEBUG: ow_w1_dispatch.c:(126) Sending this packet to root bus
  DEBUG: ow_w1_dispatch.c:(173) Dispatch loop
  DEBUG: ow_w1_parse.c:(113) Wait to peek at message
  DEBUG: ow_w1_scan.c:(54) Netlink (w1) list all bus masters
  DEBUG: ow_w1_list.c:(64) W1 List 0 masters
  DEBUG: ow_w1_scan.c:(54) Netlink (w1) list all bus masters
  DEBUG: ow_w1_list.c:(64) W1 List 1 masters
  DEBUG: ow_w1_addremove.c:(55) Setup structure for w1_bus_master1
  DEBUG: ow_w1_addremove.c:(80) Request master be added: w1_bus_master1.
  DEBUG: ow_add_inflight.c:(26) Request master be added: w1_bus_master1
FUSE library version: 2.8.6
nullpath_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56
INIT: 7.18
flags=0x0000047b
max_readahead=0x00020000
   INIT: 7.12
   flags=0x00000011
   max_readahead=0x00020000
   max_write=0x00020000
   unique: 1, success, outsize: 40

owfs mount point without EEPROM present but with owfs running

10.20.30.41:/tmp# ls /mnt
total 4.0K
drwxr-xr-x  5 root root 1.0K May 13 19:37 .
drwxr-xr-x 23 root root 1.0K May 13 11:33 ..
drwxr-xr-x  2 root root 1.0K Mar 31 19:35 jj
drwxr-xr-x  2 root root 1.0K Oct  9  2012 sda1
drwxr-xr-x  1 root root    8 May 13 19:40 w1

Output from owfs during last command
     unique: 2, opcode: GETATTR (3), nodeid: 1, insize: 56
     getattr /
        CALL: ow_fstat.c:(22) path=/
        CALL: ow_parsename.c:(98) path=[/]
        CALL: ow_fstat.c:(39) ATTRIBUTES path=/
      DEBUG: ow_parsename.c:(62) /
        unique: 2, success, outsize: 120
     unique: 3, opcode: GETXATTR (22), nodeid: 1, insize: 65
       unique: 3, error: -38 (Function not implemented), outsize: 16

10.20.30.41:/tmp# ls /mnt/w1
total 1.0K
drwxr-xr-x 1 root root    8 May 13 19:40 .
drwxr-xr-x 5 root root 1.0K May 13 19:37 ..
drwxr-xr-x 1 root root    8 May 13 19:40 bus.0
drwxr-xr-x 1 root root    8 May 13 19:40 bus.1
drwxr-xr-x 1 root root    8 May 13 19:40 settings
drwxr-xr-x 1 root root    8 May 13 19:40 statistics
drwxr-xr-x 1 root root   32 May 13 19:40 structure
drwxr-xr-x 1 root root    8 May 13 19:40 system
drwxr-xr-x 1 root root    8 May 13 19:40 uncached

Output from owfs during last command
     unique: 4, opcode: GETATTR (3), nodeid: 1, insize: 56
     getattr /
        CALL: ow_fstat.c:(22) path=/
        CALL: ow_parsename.c:(98) path=[/]
        CALL: ow_fstat.c:(39) ATTRIBUTES path=/
       DEBUG: ow_parsename.c:(62) /
        unique: 4, success, outsize: 120
     unique: 5, opcode: OPENDIR (27), nodeid: 1, insize: 48
        unique: 5, success, outsize: 32
     unique: 6, opcode: READDIR (28), nodeid: 1, insize: 80
     getdir[0]
        CALL: ow_parsename.c:(98) path=[/]
        CALL: owfs_callback.c:(177) GETDIR path=/
       DEBUG: ow_dir.c:(65) path=/
        CALL: ow_dir.c:(100) path=/
       DEBUG: ow_cache.c:(867) Looking for directory 00 00 00 00 00 00 00 00
       DEBUG: ow_cache.c:(880) Get from cache sn 00 00 00 00 00 00 00 00
pointer=0xb6fa0790 extension=1
       DEBUG: ow_cache.c:(909) Dir not found in cache
       DEBUG: ow_search.c:(32) Start of directory path=/ device=00 00 00 00
00 00 00 00
       DEBUG: ow_w1.c:(125) Sending w1 search (list devices) message
       DEBUG: ow_w1_send.c:(132) Netlink send -----------------
     NLMSGHDR: len=52 type=3 (NLMSG_DONE) flags=5 seq=1|1 pid=2921
     CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=1|1 ack=65537 len=16 flags=0
     W1_NETLINK_MSG: type=4 (W1_MASTER_CMD) len=4 id=1
     W1_NETLINK_CMD: cmd=2 (W1_CMD_SEARCH) len=0
     NULL data
       EBUG: ow_cache.c:(867) Looking for directory 00 00 00 00 00 00 00 00
       DEBUG: ow_cache.c:(880) Get from cache sn 00 00 00 00 00 00 00 00
pointer=0xb6fa0790 extension=0
       DEBUG: ow_cache.c:(909) Dir not found in cache
       DEBUG: ow_w1_parse.c:(121) Pre-parse header: 16 bytes len=52 type=3
seq=1|1 pid=0
       DEBUG: ow_w1_parse.c:(142) Netlink read -----------------
     NLMSGHDR: len=52 type=3 (NLMSG_DONE) flags=0 seq=1|1 pid=0
     CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=1|1 ack=0 len=16 flags=0
     W1_NETLINK_MSG: type=4 (W1_MASTER_CMD) len=4 id=1
     W1_NETLINK_CMD: cmd=2 (W1_CMD_SEARCH) len=0
     NULL data
       DEBUG: ow_w1_dispatch.c:(92) Netlink message directed to W1 bus master 1
       DEBUG: ow_w1_dispatch.c:(149) Sending this packet to w1_bus_master1
       DEBUG: ow_w1_dispatch.c:(173) Dispatch loop
       DEBUG: ow_w1_parse.c:(113) Wait to peek at message
       DEBUG: ow_w1_parse.c:(121) Pre-parse header: 16 bytes len=52 type=3
seq=1|1 pid=0
       DEBUG: ow_w1_parse.c:(142) Netlink read -----------------
     NLMSGHDR: len=52 type=3 (NLMSG_DONE) flags=0 seq=1|1 pid=0
     CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=1|1 ack=65537 len=16 flags=0
     W1_NETLINK_MSG: type=4 (W1_MASTER_CMD) len=4 id=1
     W1_NETLINK_CMD: cmd=2 (W1_CMD_SEARCH) len=0
     NULL data
       DEBUG: ow_w1_dispatch.c:(92) Netlink message directed to W1 bus master 1
       DEBUG: ow_w1_dispatch.c:(149) Sending this packet to w1_bus_master1
       DEBUG: ow_w1_dispatch.c:(173) Dispatch loop
       EBUG: ow_w1_parse.c:(113) Wait to peek at message
       DEBUG: ow_w1_send.c:(143) NETLINK sent seq=1
       DEBUG: ow_w1_parse.c:(225) Loop waiting for netlink piped message
       DEBUG: ow_w1_parse.c:(163) Pipe header: len=52 type=3 seq=1|1 pid=0 
       DEBUG: ow_w1_parse.c:(191) Pipe read --------------------
     NLMSGHDR: len=52 type=3 (NLMSG_DONE) flags=0 seq=1|1 pid=0
     CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=1|1 ack=0 len=16 flags=0
     W1_NETLINK_MSG: type=4 (W1_MASTER_CMD) len=4 id=1
     W1_NETLINK_CMD: cmd=2 (W1_CMD_SEARCH) len=0
     NULL data
       DEBUG: ow_w1_parse.c:(245) About to call nrs_callback
       DEBUG: ow_w1_parse.c:(247) Called nrs_callback
       DEBUG: ow_w1_parse.c:(225) Loop waiting for netlink piped message
       DEBUG: ow_w1_parse.c:(163) Pipe header: len=52 type=3 seq=1|1 pid=0 
       DEBUG: ow_w1_parse.c:(191) Pipe read --------------------
     NLMSGHDR: len=52 type=3 (NLMSG_DONE) flags=0 seq=1|1 pid=0
     CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=1|1 ack=65537 len=16 flags=0
     W1_NETLINK_MSG: type=4 (W1_MASTER_CMD) len=4 id=1
     W1_NETLINK_CMD: cmd=2 (W1_CMD_SEARCH) len=0
     NULL data
       DEBUG: ow_w1.c:(201) SN finished
        CALL: ow_parsename.c:(98) path=[/bus.1]
       DEBUG: ow_parsename.c:(62) /bus.1
        CALL: ow_parsename.c:(98) path=[/bus.0]
       DEBUG: ow_parsename.c:(62) /bus.0
        CALL: ow_parsename.c:(98) path=[/uncached]
       DEBUG: ow_parsename.c:(62) /uncached
        CALL: ow_parsename.c:(98) path=[/settings]
       DEBUG: ow_parsename.c:(62) /settings
        CALL: ow_parsename.c:(98) path=[/system]
       DEBUG: ow_parsename.c:(62) /system
        CALL: ow_parsename.c:(98) path=[/statistics]
       DEBUG: ow_parsename.c:(62) /statistics
        CALL: ow_parsename.c:(98) path=[/structure]
       DEBUG: ow_parsename.c:(62) /structure
       DEBUG: ow_dir.c:(195) ret=0
       DEBUG: ow_parsename.c:(62) /
        unique: 6, success, outsize: 320
     unique: 7, opcode: LOOKUP (1), nodeid: 1, insize: 46
     LOOKUP /bus.1
     getattr /bus.1
        CALL: ow_fstat.c:(22) path=/bus.1
        CALL: ow_parsename.c:(98) path=[/bus.1]
        CALL: ow_fstat.c:(39) ATTRIBUTES path=/bus.1
       DEBUG: ow_parsename.c:(62) /bus.1
        NODEID: 2
        unique: 7, success, outsize: 144
     unique: 8, opcode: LOOKUP (1), nodeid: 1, insize: 46
     LOOKUP /bus.0
     getattr /bus.0
        CALL: ow_fstat.c:(22) path=/bus.0
        CALL: ow_parsename.c:(98) path=[/bus.0]
        CALL: ow_fstat.c:(39) ATTRIBUTES path=/bus.0
       DEBUG: ow_parsename.c:(62) /bus.0
        NODEID: 3
        unique: 8, success, outsize: 144
     unique: 9, opcode: LOOKUP (1), nodeid: 1, insize: 49
     LOOKUP /uncached
     getattr /uncached
        CALL: ow_fstat.c:(22) path=/uncached
        CALL: ow_parsename.c:(98) path=[/uncached]
        CALL: ow_fstat.c:(39) ATTRIBUTES path=/uncached
       DEBUG: ow_parsename.c:(62) /uncached
        NODEID: 4
        unique: 9, success, outsize: 144
     unique: 10, opcode: LOOKUP (1), nodeid: 1, insize: 49
     LOOKUP /settings
     getattr /settings
        CALL: ow_fstat.c:(22) path=/settings
        CALL: ow_parsename.c:(98) path=[/settings]
        ALL: ow_fstat.c:(39) ATTRIBUTES path=/settings
       DEBUG: ow_parsename.c:(62) /settings
        NODEID: 5
        unique: 10, success, outsize: 144
     unique: 11, opcode: LOOKUP (1), nodeid: 1, insize: 47
     LOOKUP /system
     getattr /system
        CALL: ow_fstat.c:(22) path=/system
        CALL: ow_parsename.c:(98) path=[/system]
        CALL: ow_fstat.c:(39) ATTRIBUTES path=/system
       DEBUG: ow_parsename.c:(62) /system
        NODEID: 6
        unique: 11, success, outsize: 144
     unique: 12, opcode: LOOKUP (1), nodeid: 1, insize: 51
     LOOKUP /statistics
     getattr /statistics
        CALL: ow_fstat.c:(22) path=/statistics
        CALL: ow_parsename.c:(98) path=[/statistics]
        CALL: ow_fstat.c:(39) ATTRIBUTES path=/statistics
       DEBUG: ow_parsename.c:(62) /statistics
        NODEID: 7
        unique: 12, success, outsize: 144
     unique: 13, opcode: LOOKUP (1), nodeid: 1, insize: 50
     LOOKUP /structure
     getattr /structure
        CALL: ow_fstat.c:(22) path=/structure
        CALL: ow_parsename.c:(98) path=[/structure]
        CALL: ow_fstat.c:(39) ATTRIBUTES path=/structure
       DEBUG: ow_parsename.c:(62) /structure
        NODEID: 8
        unique: 13, success, outsize: 144
     unique: 14, opcode: GETATTR (3), nodeid: 1, insize: 56
     getattr /
        CALL: ow_fstat.c:(22) path=/
        CALL: ow_parsename.c:(98) path=[/]
       CALL: ow_fstat.c:(39) ATTRIBUTES path=/
       DEBUG: ow_parsename.c:(62) /
        unique: 14, success, outsize: 120
     unique: 15, opcode: READDIR (28), nodeid: 1, insize: 80
        unique: 15, success, outsize: 16
     unique: 16, opcode: RELEASEDIR (29), nodeid: 1, insize: 64
        unique: 16, success, outsize: 16

Attaching the 1-wire EEPROM
     output from owfs
       DEBUG: ow_w1_parse.c:(121) Pre-parse header: 16 bytes len=48 type=3
seq=0|4 pid=0
       DEBUG: ow_w1_parse.c:(142) Netlink read -----------------
     NLMSGHDR: len=48 type=3 (NLMSG_DONE) flags=0 seq=0|4 pid=0
     CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=0|4 ack=0 len=12 flags=0
     W1_NETLINK_MSG: type=0 (W1_SLAVE_ADD) len=0 id=1005157187
     W1_NETLINK_CMD: NULL w1c field
     NULL data
       DEBUG: ow_w1_dispatch.c:(88) Netlink message directed to root W1 master
       DEBUG: ow_w1_dispatch.c:(126) Sending this packet to root bus
       DEBUG: ow_w1_dispatch.c:(173) Dispatch loop
       DEBUG: ow_w1_parse.c:(113) Wait to peek at message
       DEBUG: ow_w1_scan.c:(69) Netlink (w1) Slave announcements (ignored)

ls on owfs mountpoint - **** ERROR *** - no output, hanges
10.20.30.41:/tmp# ls /mnt/w1

Output from owfs during last command
     unique: 17, opcode: GETATTR (3), nodeid: 1, insize: 56
     getattr /
        CALL: ow_fstat.c:(22) path=/
        CALL: ow_parsename.c:(98) path=[/]
        CALL: ow_fstat.c:(39) ATTRIBUTES path=/
       DEBUG: ow_parsename.c:(62) /
        unique: 17, success, outsize: 120
     unique: 18, opcode: OPENDIR (27), nodeid: 1, insize: 48
        unique: 18, success, outsize: 32
     unique: 19, opcode: READDIR (28), nodeid: 1, insize: 80
     getdir[0]
        CALL: ow_parsename.c:(98) path=[/]
        CALL: owfs_callback.c:(177) GETDIR path=/
       DEBUG: ow_dir.c:(65) path=/
        CALL: ow_dir.c:(100) path=/
       DEBUG: ow_cache.c:(867) Looking for directory 00 00 00 00 00 00 00 00
       DEBUG: ow_cache.c:(880) Get from cache sn 00 00 00 00 00 00 00 00
pointer=0xb6fa0790 extension=1
       DEBUG: ow_cache.c:(867) Looking for directory 00 00 00 00 00 00 00 00
      DEBUG: ow_cache.c:(880) Get from cache sn 00 00 00 00 00 00 00 00
pointer=0xb6fa0790 extension=0
      DEBUG: ow_cache.c:(909) Dir not found in cache
      DEBUG: ow_cache.c:(909) Dir not found in cache
      DEBUG: ow_search.c:(32) Start of directory path=/ device=00 00 00 00
00 00 00 00
       DEBUG: ow_w1.c:(125) Sending w1 search (list devices) message
      DEBUG: ow_w1_send.c:(132) Netlink send -----------------
     NLMSGHDR: len=52 type=3 (NLMSG_DONE) flags=5 seq=1|2 pid=2921
     CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=1|2 ack=65538 len=16 flags=0
     W1_NETLINK_MSG: type=4 (W1_MASTER_CMD) len=4 id=1
     W1_NETLINK_CMD: cmd=2 (W1_CMD_SEARCH) len=0
     NULL data

------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
Gregg Levine | 13 May 2013 20:00
Picon

Error in building OWFS ver 2.9p0 from source

Hello!
I am getting this odd error from trying to build the 2.9P0 source code:
mv: cannot stat `.deps/compat.Tpo': No such file or directory
make[5]: *** [compat.lo] Error 1
make[5]: Leaving directory `/usr/src/owfs/owfs-2.9p0/module/ownet/c/src/c'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/usr/src/owfs/owfs-2.9p0/module/ownet/c/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/usr/src/owfs/owfs-2.9p0/module/ownet/c'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/owfs/owfs-2.9p0/module/ownet'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/owfs/owfs-2.9p0/module'
make: *** [all-recursive] Error 1

I believe its the same one that forced me to not try to continue
trying to build any of the later 2.8 ones. If need be I can provide
the entire build sequence of events as a compressed text file for the
purposes constructing a fix.

-----
Gregg C Levine gregg.drwho8 <at> gmail.com
"This signature fought the Time Wars, time and again."

------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
Clownfishy | 13 May 2013 15:33

Re: OWHTTPD 147 error

Just rebuilt a new SDCard and installed everything from scratch, I get the
same error/results.....very strange

--
View this message in context: http://owfs-developers.1086194.n5.nabble.com/OWHTTPD-147-error-tp9559p9568.html
Sent from the OWFS Developers mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
Daniel MacKay | 13 May 2013 12:59
Picon

Reading the DS2423

Hello!  I started a new application (solar home energy monitoring) which uses the mighty DS2423 (as
purchased from Digi-Key & Hobby Boards) on a Raspberry Pi with the Sheepwalk RPI2 bus master and I2C-1 driver.

The DS2423 is reading the output of a YF-S201 flow meter so I can see how much hot water the house is using.

Here is a screendump of the owhttpd output:

	http://gyazo.com/6f427544f972372b6a2f1e39c2b220f0

(although I'm reading it with owread.)

Yesterday, for fun, I replaced the "memory" field with

	0000DEAD0BEEF0CAFE00000

... and all the rest zeros - I just pasted in zeros until it was full.  After that, the counter started... well,
not counting. Or counting 1 for every few thousand pulses or something.  I used the "upload" function to
refill it with some random data (a small jpg of a kitten) and it seems to be back to normal.

I have two questions:

1) could the contents of "memory" or the act of pasting data in there have affected how the DS2423 counts? and
2) what should be in the "mincount" field?  It was oddly at "1723" when I looked at it (after the trouble began)
and I reset it to zero but... what should it be?

Many thanks.

--
Daniel MacKay
Halifax, Nova Scotia, Canada

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
Don Veino | 12 May 2013 07:06
Favicon

Where can I learn more about simultaneous?

Asking after much Googling and checking the owfs site. I'm trying to understand why when I click on an owhttpd (started readonly) "simultaneous" link it kills owserver.

I can see bus activity started on the adapter (LinkUSB blinks actively) and then owhttpd listing no longer shows any devices and a process listing shows that owserver goes missing. Restart of owserver brings everything back fine and the 1-wire network seems stable otherwise.

BTW, same thing appears to happen via owfs/file system:
cat /srv/http/1wire/simultaneous/temperature, which returns
cat: /srv/http/1wire/simultaneous/temperature: Input/output error

Owfs suite version 2.9p0 on a Seagate DockStar running up to date Arch Linux ARM. LinkUSB adapter connecting a single short 1-wire bus with 5 devices: 4 DS18xxx and 1 MS-TH, all parasitic. A second machine with a 2 device bus behaves the same.

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Gmane