gmane.comp.file-systems.owfs.devel

Connecting to a DS2438

Peter Hollenbeck — 2013-05-17T17:32:01

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

Compile with USB Support

Peter Hollenbeck — 2013-05-16T14:59:24

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
/v

Compiling issues on Cygwin

Egger Clemens — 2013-05-16T08:56:39

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 >

owfs not able to connect to owserver when usingowfs.conf

Jan Chrillesen — 2013-05-14T06:17:05

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:0

owfs hangup on Linux 3.0.4 using DS28EC20 Dallas1-wire EEPROM

Walter Lewis — 2013-05-13T23:07:09

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 applicati

Error in building OWFS ver 2.9p0 from source

Gregg Levine — 2013-05-13T18:00:20

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 a

Reading the DS2423

Daniel MacKay — 2013-05-13T10:59:24

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"

Where can I learn more about simultaneous?

Don Veino — 2013-05-12T05:06:45

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"

owhttpd in 2.9p0

foster — 2013-05-10T07:32:24

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

Raspberry Pi and Fuse

Peter Hollenbeck — 2013-05-09T00:13:14

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< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

(arm?) bug with json/text being reversed

Andrew Elwell — 2013-05-08T06:17:22

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< at >raspberrypi /usr/bin $
pi< at >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
< HTTP/1.0 200 OK
< Date: Wed, 08 May 2013 06:14:46 GMT
< Server: owhttpd
< Last-Modified: Wed, 08 May 2013 06:14:46 GMT
< Content-Type: text/plain
<
{
"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 <= 0, server closed

DS1921 Thermochron Patch - Mission Start Delay,Stop Mission

Egger Clemens — 2013-05-02T12:43:49

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 t

anyone using a beaglebone black with 1-wire

Jerry Scharf — 2013-04-27T06:35:55

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 & 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_apr

--nozero?

Don Veino — 2013-04-26T23:51:42

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 & 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_apr_______________________________________________
Owfs-developers mailing list
Owfs-developers< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Temperature = 127 degrees

Mick Sulley — 2013-04-24T23:02:56

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 & 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_apr

Accessing Devices\Sensors using pyowfs

joep — 2013-04-19T12:08:50

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 
o

Direct Access to Sensors using pyowfs

joep — 2013-04-18T12:24:38

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 ?

File Structure Question

Mick Sulley — 2013-04-17T10:36:59

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 deepe

TAI8570 readout in 2.9p0

2013-04-14T20:00:01

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
< at >< at > -109,7 +109,9 < at >< at >
 {"TAI8570/temperature", PROPERTY_LENGTH_TEMP, NON_AGGREGATE, ft_temperature, fc_link, FS_tempera

6 Channel Hub / DS2409 Question

Mick Sulley — 2013-04-11T22:56:44

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

(no subject)

2013-04-08T20:49:21

------------------------------------------------------------------------------
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< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers