gmane.comp.file-systems.owfs.devel http://blog.gmane.org/gmane.comp.file-systems.owfs.devel hourly 1 1901-01-01T00:00+00:00 Gmane http://gmane.org/img/gmane-25t.png http://gmane.org Connecting to a DS2438 http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10438 <pre>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&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers </pre> Peter Hollenbeck 2013-05-17T17:32:01 Compile with USB Support http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10435 <pre>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&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers </pre> Peter Hollenbeck 2013-05-16T14:59:24 Compiling issues on Cygwin http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10434 <pre>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 &gt;/dev/null 2&gt;&amp;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 &gt;/dev/null 2&gt;&amp;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 &gt;/dev/null 2&gt;&amp;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 &gt;/dev/null 2&gt;&amp;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 </pre> Egger Clemens 2013-05-16T08:56:39 owfs not able to connect to owserver when usingowfs.conf http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10432 <pre>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 </pre> Jan Chrillesen 2013-05-14T06:17:05 owfs hangup on Linux 3.0.4 using DS28EC20 Dallas1-wire EEPROM http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10425 <pre>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 &lt;HOST&gt; 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 &lt;host&gt; 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 -&gt; ../../../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 -&gt; ../../../devices/w1_bus_master1/43-0000003be97b lrwxrwxrwx 1 root root 0 May 13 19:33 w1_bus_master1 -&gt; ../../../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 &lt;....&gt; 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 </pre> Walter Lewis 2013-05-13T23:07:09 Error in building OWFS ver 2.9p0 from source http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10420 <pre>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&lt; at &gt;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 </pre> Gregg Levine 2013-05-13T18:00:20 Reading the DS2423 http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10414 <pre>Hello! I started a new application (solar home energy monitoring) which uses the mighty DS2423 (as purchased from Digi-Key &amp; 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 </pre> Daniel MacKay 2013-05-13T10:59:24 Where can I learn more about simultaneous? http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10407 <pre>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&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers </pre> Don Veino 2013-05-12T05:06:45 owhttpd in 2.9p0 http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10406 <pre>Hi. I've just installed owfs 2.9p0, and I have a problem with setting port of owhttp. In previous versions there was owfs.conf, but in this version this config file is missing. Also there is missing info, where to set temperature/pressure units. Thx. for answer. Btw. bug with duplicate directories were fixed in this version. Good job. -- View this message in context: http://owfs-developers.1086194.n5.nabble.com/owhttpd-in-2-9p0-tp9556.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 </pre> foster 2013-05-10T07:32:24 Raspberry Pi and Fuse http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10399 <pre>I am running owfs successfully on one RPi. I am trying to run it on another and have a problem. I enter: owfs -u -m 1wire and get: fuse: device not found, try 'modprobe fuse' first I tried modprobe fuse. no help. I think both RPis are running 2013-02-09-wheezy-raspbian I would appreciate suggestions. Thank you, Peter ------------------------------------------------------------------------------ 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&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers </pre> Peter Hollenbeck 2013-05-09T00:13:14 (arm?) bug with json/text being reversed http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10395 <pre>Discovered this on a raspberry-pi running raspbian (don't know if debian specific as I saw someone else commenting on it in the archives) https://gist.github.com/Elwell/5538497 pi&lt; at &gt;raspberrypi /usr/bin $ pi&lt; at &gt;raspberrypi /usr/bin $ curl -v http://127.0.0.1:8080/text/10.67C6697351FF * About to connect() to 127.0.0.1 port 8080 (#0) * Trying 127.0.0.1... * connected * Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0) * additional stuff not fine transfer.c:1037: 0 0 * HTTP 1.0, assume close after body &lt; HTTP/1.0 200 OK &lt; Date: Wed, 08 May 2013 06:14:46 GMT &lt; Server: owhttpd &lt; Last-Modified: Wed, 08 May 2013 06:14:46 GMT &lt; Content-Type: text/plain &lt; { "address":"1067C6697351FF8D", "alias":"", "crc8":"8D", "errata":[], "family":"10", "id":"67C6697351FF", "locator":"vwtxlbznryjdohbv", "power":"false", "r_address":"8DFF517369C66710", "r_id":"FF517369C667", "r_locator":"hmyuiggtyqjtmuqi", "temperature":" 81.2006", "temphigh":" 7.08083", "templow":" 85.8895", "type":"DS18S20", * nread &lt;= 0, server closed connection, bailing * Closing connection #0 }pi&lt; at &gt;raspberrypi /usr/bin $ curl -v http://127.0.0.1:8080/json/10.67C6697351FF * About to connect() to 127.0.0.1 port 8080 (#0) * Trying 127.0.0.1... * connected * Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0) * additional stuff not fine transfer.c:1037: 0 0 * HTTP 1.0, assume close after body &lt; HTTP/1.0 200 OK &lt; Date: Wed, 08 May 2013 06:14:53 GMT &lt; Server: owhttpd &lt; Last-Modified: Wed, 08 May 2013 06:14:53 GMT &lt; Content-Type: text/plain &lt; address 1067C6697351FF8D alias crc8 8D errata family 10 id 67C6697351FF locator qmihntkddnalwnms power 1 r_address 8DFF517369C66710 r_id FF517369C667 r_locator satqqeldacnnpjfe temperature 84.1657 temphigh 76.6387 templow 71.5065 type DS18S20 * nread &lt;= 0, server closed connection, bailing * Closing connection #0 pi&lt; at &gt;raspberrypi /usr/bin $ dpkg -l owhttpd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-===========================-==================-==================-=========================================================== ii owhttpd 2.8p15-1 armhf HTTP daemon providing access to 1-Wire networks pi&lt; at &gt;raspberrypi /usr/bin $ it'd also be nice if the json version could be sent with Content-Type: application/json to be standards compliant http://tools.ietf.org/html/rfc4627 Ta Andrew ------------------------------------------------------------------------------ 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 </pre> Andrew Elwell 2013-05-08T06:17:22 DS1921 Thermochron Patch - Mission Start Delay,Stop Mission http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10394 <pre>Hi Paul, while working with the DS1921 Thermochron iButton I came across a few problems. See attached patch file for fixes. - mission/clear not working: I made visible mission/clear (for reasons explained below), however the assigned read/write functions FS_r_controlbit, FS_w_controlbit had no effect; writing 1 to mission/clear did not clear the iButton. I wrote a separate function FS_clrmem, which basically calls the already existing function OW_clearmemory(). This way it was possible to clear the mission of the iButton. Since the mission/clear never read anything else than 0, I assigned NO_READ_FUNCTION. ("The EMCLR bit returns to 0 as the next memory function command is executed", [#ds page 14]) - It is not possible to use the Mission Start Delay: FS_w_samplerate uses OW_startmission to set the Sample Rate. However the function OW_startmission performs a clear memory by calling OW_clearmemory, which also clears a previously set Mission Start Delay. Afterwards the Sample Rate is written and therefore the mission starts. This way there is no possibility to use the Mission Start Delay. I removed OW_clearmemory from OW_startmission and inserted a separate OW_clearmemory for the function FS_easystart. This way mission/clear is needed to do the missioning. - The function OW_stopmission does not work: As intended in the code a mission can be stopped by writing 0 to either mission/frequency or mission/running. However doing so, the sampling is not stopped. The function OW_stopmission just performs a read, there's also a comment saying "dummy". The datasheet states "A mission ends with the first write attempt (Copy Scratchpad command) to any register in the address range of 200h to 213h. Alternatively, a mission can be ended by directly writing to the Status register and setting the MIP bit to 0. The MIP bit cannot be set to 1 by writing to the Status register.", [#ds page 15] I implemented the way to set the MIP in the status register to 0. - Typos and probably copy-and-paste leftovers in man pages: DS1921 and DS2438. I'm aware that this patch breaks the feature to start a mission by writing 1 to mission/running - in that case a previously set frequency was re-used for a new mission after performing a clear-memory. Since this feature seems not to be documented in the man page I was not sure how to proceed and wanted to discuss this point with you. I'm happy to fix the code in either way: to restore the feature or to remove its remaining residuals. I'm also willing to add additional documentation to the DS1921 man page about the missioning and mission/clear. best regards Clemens Egger Reference: #ds: DS1921G datasheet (http://datasheets.maximintegrated.com/en/ds/DS1921G.pdf) </pre> Egger Clemens 2013-05-02T12:43:49 anyone using a beaglebone black with 1-wire http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10390 <pre>Hi, In an article I was reading, it mentioned the new beagleboard black system. It seems nice and it has this system for plugging on "capes" onto the base processor through a pair of headers. One of the capes is an 8 port 1-wire bridge. I was thinking this could make a nice ethernet server for 1-wire. It seems like quite a package for $45. the 1-wire cape is another $60, but you could do it Has anyone played with this yet? jerry ------------------------------------------------------------------------------ Try New Relic Now &amp; 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, &amp; 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_apr </pre> Jerry Scharf 2013-04-27T06:35:55 --nozero? http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10385 <pre>What does --nozero option do? Does it prevent recording of "bad" readings? I can't find it in the man pages on owfs.org but see it used in an example at http://marc.merlins.org/perso/linuxha/post_2010-08-06_Temperature_-moisture_-humidity_-and-UV-monitoring-and-graphing-with-1wire-devices_-owfs_-and-cacti.html ------------------------------------------------------------------------------ Try New Relic Now &amp; 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, &amp; 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_apr_______________________________________________ Owfs-developers mailing list Owfs-developers&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers </pre> Don Veino 2013-04-26T23:51:42 Temperature = 127 degrees http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10381 <pre>My current test setup has 6 temperature sensors, all on the floor close to my desk. I am seeing many readings of 127.938 degrees from 3 of the sensors and 127.688 degrees from another 2. I am used to seeing 85 when there is a problem but have never seen 127 before. Has anyone else seen this? I am running 2.9p0 on a RasPi with Sheepwalk RPI4 adapter Thanks Mick ------------------------------------------------------------------------------ Try New Relic Now &amp; 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, &amp; 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_apr </pre> Mick Sulley 2013-04-24T23:02:56 Accessing Devices\Sensors using pyowfs http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10380 <pre>The following code (and the output from it) is to summarize my initial findings using Marcus Priesch's pyowfs library. It may help someone who wants to quickly evaluate this library and avoid some of the pitfalls I fell into. The most significant for me was how to locate a sensor based on the sensor's UUID without having to iterate and parse. [I intend to have multiple sensors of the same type in my application. Each one measures a different temperature and to access these different temperatures unambiguously I need to locate the specific sensor by UUID]. Thanks again Marcus for helping me sort this out. Joe P. -------- Code Start ---------- #! /usr/bin/env python """ Sample code to illustrate basic read operations using the pyowfs library """ from pyowfs import Connection # Stage 1 - Connect to OWSERVER root = Connection ("localhost:4304") # Stage 2 - Access the 1-wire information print "List of all devices present" for s in root.find () : print s # This lists all the devices available on the bus. print "This also is a listing of all devices present" for i in root.iter_sensors () : print i print "List of devices of type DS18B20 (a temperature sensor)" s = root.find (type = "DS18B20") print s print 'Assigning DS18B20 Sensors ...' s0 = root.find (type = "DS18B20")[0] s1 = root.find (type = "DS18B20")[1] print "Sensor 0:" print s0 print "Temperature from Sensor 0:" print s0.get("temperature") print "Sensor 1:" print s1 print "Temperature from Sensor 1:" print s1.get("temperature") print "Selecting a sensor by ID (F758DC020000)" """ NOTE The ID of a sensor does not include the characters before the decimal point (28 in this case) and the decimal point itself. """ s = root.find (id="F758DC020000") [0] temp = s.get ("temperature") print "Printing Temp from F758DC020000..." print temp print 'List One-wire filesystem content under the root node ...' for e in root.iter_entries () : print e print 'List One-wire filesystem content under the bus.0 directory ...' for f in root.get ("bus.0").iter_entries () : print f print 'List One-wire filesystem content under the bus.0\interface directory ...' for g in root.get ("bus.0").get("interface").iter_entries () : print g " ... etc. ..." print "End of Program" ----------- End of Code ----------- -------- Output Start -------- pi&lt; at &gt;raspberrypi ~/MyFiles/OWFS/code $ ./temperature_pyowfs_3.py List of all devices present &lt;Sensor /28.450EDC020000/ - DS18B20&gt; &lt;Sensor /28.F758DC020000/ - DS18B20&gt; &lt;Sensor /81.A7D12F000000/ - DS1420&gt; This also is a listing of all devices present &lt;Sensor /28.450EDC020000/ - DS18B20&gt; &lt;Sensor /28.F758DC020000/ - DS18B20&gt; &lt;Sensor /81.A7D12F000000/ - DS1420&gt; List of devices of type DS18B20 (a temperature sensor) [&lt;Sensor /28.450EDC020000/ - DS18B20&gt;, &lt;Sensor /28.F758DC020000/ - DS18B20&gt;] Assigning DS18B20 Sensors ... Sensor 0: &lt;Sensor /28.450EDC020000/ - DS18B20&gt; Temperature from Sensor 0: 21.8125 Sensor 1: &lt;Sensor /28.F758DC020000/ - DS18B20&gt; Temperature from Sensor 1: 21.6875 Selecting a sensor by ID (F758DC020000) Printing Temp from F758DC020000... 21.6875 List One-wire filesystem content under the root node ... &lt;Dir '/bus.0/'&gt; &lt;Dir '/uncached/'&gt; &lt;Dir '/settings/'&gt; &lt;Dir '/system/'&gt; &lt;Dir '/statistics/'&gt; &lt;Dir '/structure/'&gt; &lt;Dir '/simultaneous/'&gt; &lt;Dir '/alarm/'&gt; List One-wire filesystem content under the bus.0 directory ... &lt;Dir '/bus.0/interface/'&gt; &lt;Dir '/bus.0/bus.0/'&gt; &lt;Dir '/bus.0/uncached/'&gt; &lt;Dir '/bus.0/settings/'&gt; &lt;Dir '/bus.0/system/'&gt; &lt;Dir '/bus.0/statistics/'&gt; &lt;Dir '/bus.0/structure/'&gt; &lt;Dir '/bus.0/simultaneous/'&gt; &lt;Dir '/bus.0/alarm/'&gt; List One-wire filesystem content under the bus.0\interface directory ... &lt;Dir '/bus.0/interface/settings/'&gt; &lt;Dir '/bus.0/interface/statistics/'&gt; End of Program -------- Output End -------- </pre> joep 2013-04-19T12:08:50 Direct Access to Sensors using pyowfs http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10376 <pre>I'm evaluating pyowfs for use in a USB based 1-wire system running on a RaspberryPi. I've got pyowfs running fine on the RaspberryPi. At this stage I'm reading temperatures (from four DS18B20 sensors). I'm using the code described on the 'pyowfs website' to read temperatures. This generates a list of sensors, this sensor list is then parsed for the required sensor (eg sensor with an ID 28.450EDC020000) and then the temperature is read (eg. temp = s.get ("temperature") where s is the sensor with the required ID). Is there a more direct way of identifying the sensor with a given (ie known) ID? I tried:- root = Connection ("localhost:4304") s = root.get("/28.450EDC020000") temp = s.get ("temperature") but that didn't work. Any ideas\suggestions ? </pre> joep 2013-04-18T12:24:38 File Structure Question http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10371 <pre>I am having trouble understanding the file structure, it is not behaving as I expected. My structure looks like this in Nautilus - /var/1-wire/mnt 81.8C7E30000000 alarm bus.0 81.8C7E30000000 alarm bus.0 10.0D54A9010800 81.8C7E30000000 alarm interface settings simultaneous structure system uncached settings simultaneous structure system uncached This is what I expected and what I see in Nautilus, however when I try to navigate in Python, or in a terminal, if I try cd /var/1-wire/mnt/bus.0/bus.0 that is fine, but if I try cd /var/1-wire/mnt/bus.0/bus.0/bus.0/bus.0 that also works, I can cd to any level of additional /bus.0 directories. I cannot see these directories in Nautilus. I am trying to write Python code to navigate down the directory structure, but the problem is that it just keeps going deeper and deeper, finding more /bus.0 directories. I am guessing that this is all expected behaviour, even though it came as a surprise to me:) Is there a way to tell if the directories that I see are real (or as real as FUSE directories ever are)? Thanks Mick ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis &amp; visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter </pre> Mick Sulley 2013-04-17T10:36:59 TAI8570 readout in 2.9p0 http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10370 <pre>First of all, many thanks for all the hard work developing and maintaining the OWFS suite. The most recent update fixed many lingering issues I had been experiencing. My TAI8570, however, started giving out invalid readings (of the form "6.63453E+07") for both temperature and pressure, despite having the correct coefficients and raw readouts for C.ALL, D1, and D2. I traced it to a missing typecast (at least, that fixed it for me) and also added some directory entries to expose the 5534- and 5540- specific functions already in the code. Stylistically, I'm sure there are better ways to fix it than what I did. Diff and source files for ow_2406.c attached. Let me know if it helps to generate the diff with other options. I don't do much coding on a regular basis. Thanks, Dave --- ow_2406.c2013-01-10 22:19:39.000000000 -0500 +++ ow_2406.c.fixed2013-04-14 15:36:40.000000000 -0400 &lt; at &gt;&lt; at &gt; -109,7 +109,9 &lt; at &gt;&lt; at &gt; {"TAI8570/temperature", PROPERTY_LENGTH_TEMP, NON_AGGREGATE, ft_temperature, fc_link, FS_temperature, NO_WRITE_FUNCTION, VISIBLE, NO_FILETYPE_DATA, }, {"TAI8570/pressure", PROPERTY_LENGTH_PRESSURE, NON_AGGREGATE, ft_pressure, fc_link, FS_pressure, NO_WRITE_FUNCTION, VISIBLE, NO_FILETYPE_DATA, }, +{"TAI8570/DA5534", PROPERTY_LENGTH_SUBDIR, NON_AGGREGATE, ft_subdir, fc_subdir, NO_READ_FUNCTION, NO_WRITE_FUNCTION, VISIBLE, NO_FILETYPE_DATA, }, {"TAI8570/DA5534/temperature", PROPERTY_LENGTH_TEMP, NON_AGGREGATE, ft_temperature, fc_link, FS_temperature_5534, NO_WRITE_FUNCTION, VISIBLE, NO_FILETYPE_DATA, }, {"TAI8570/DA5534/pressure", PROPERTY_LENGTH_PRESSURE, NON_AGGREGATE, ft_pressure, fc_link, FS_pressure_5534, NO_WRITE_FUNCTION, VISIBLE, NO_FILETYPE_DATA, }, {"TAI8570/sibling", 16, NON_AGGREGATE, ft_ascii, fc_stable, FS_sibling, NO_WRITE_FUNCTION, VISIBLE, NO_FILETYPE_DATA, }, +{"TAI8570/DA5540", PROPERTY_LENGTH_SUBDIR, NON_AGGREGATE, ft_subdir, fc_subdir, NO_READ_FUNCTION, NO_WRITE_FUNCTION, VISIBLE, NO_FILETYPE_DATA, }, {"TAI8570/DA5540/temperature", PROPERTY_LENGTH_TEMP, NON_AGGREGATE, ft_temperature, fc_link, FS_temperature_5540, NO_WRITE_FUNCTION, VISIBLE, NO_FILETYPE_DATA, }, {"TAI8570/DA5540/pressure", PROPERTY_LENGTH_PRESSURE, NON_AGGREGATE, ft_pressure, fc_link, FS_pressure_5540, NO_WRITE_FUNCTION, VISIBLE, NO_FILETYPE_DATA, }, &lt; at &gt;&lt; at &gt; -646,5 +648,5 &lt; at &gt;&lt; at &gt; UT1 = 8 * tai.C[4] + 20224; -dT = D2 - UT1; +dT = (_FLOAT)D2 - (_FLOAT)UT1; OWQ_F(owq) = (200. + dT * (tai.C[5] + 50.) / 1024.) / 10.; &lt; at &gt;&lt; at &gt; -677,5 +679,5 &lt; at &gt;&lt; at &gt; UT1 = 8 * tai.C[4] + 20224; -dT = D2 - UT1; +dT = (_FLOAT)D2 - (_FLOAT)UT1; OFF = 4. * tai.C[1] + ((tai.C[3] - 512.) * dT) / 4096.; SENS = 24576. + tai.C[0] + (tai.C[2] * dT) / 1024.; ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis &amp; visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter_______________________________________________ Owfs-developers mailing list Owfs-developers&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers </pre> tj< at >woodsidelane.net 2013-04-14T20:00:01 6 Channel Hub / DS2409 Question http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10368 <pre>I have a 6 channel Hobbyboards hub (based upon 3 - DS2409 chips). All my devices are connected to channels, nothing on the main line other than the hub itself. The python code that I am developing occasionally fails when it starts. I have been starting and stopping the code frequently. When the code started it normally sees the hub and the 3 DS2409's, plus the usual /settings /statistics, etc, but sometimes, maybe one in six starts, it also sees the devices on one of the channels as being on the main line. My code then fails as those devices cannot be read from that position as they are not really there. I cannot see these phantom devices in any directory listing but the code logs what it reads and I see them in the logs, so I suspect it is a fleeting problem. My theory is that when I stop the code, either crash or ctrl C at keyboard, the hub could be in any condition, and if it just happens to be actively connected to one of the channels then maybe the devices on that channel still show when I restart, but I see them on the main branch. Does that make any sense? Is it a feasible possibility? To try to fix or get around this I first tried writing 1 to the /discharge register on each DS2409, that didn't seem to make any difference so I then tried writing 0 to the /control register on each DS2409. It hasn't failed since I did that, but as it is not a consistent problem anyway I cannot be sure that this has fixed it. Anyone confirm this or have any other comments? Thanks Mick ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis &amp; visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter </pre> Mick Sulley 2013-04-11T22:56:44 (no subject) http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/10361 <pre>------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html_______________________________________________ Owfs-developers mailing list Owfs-developers&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers </pre> Soll< at >gmx-topmail.de 2013-04-08T20:49:21 Search Engine Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.file-systems.owfs.devel