owfs-developers — Developer's list for OWFS

[Owfs-developers] OWHTTPD documentation

[Paul A. <pal...@ea...>]

I've upgraded the documentation for OWFS and OWHTTPD, see 
http://owfs.sourceforge.net
 and http://owfsw.sourceforge.net/ow_table.html

Also added support for the DS1904 DS2417 clocks and other stuff.

LCD support is next.

[Owfs-developers] [1-wire] OWHTTPD - 1-wire web server

[Paul A. <pal...@ea...>]

I've just posted a new wrinkle on my OWFS (1-wire filesystem):

OWHTTPD a light-weight 1-wire web server.

Basically instead of creating files from 1-wire device properties, I
create web pages. Since the 2 projects share most of their code,
progress should be fast.

Example:
owhttpd -d /dev/ttyS0 -p 3001 

You could then look at your 1-wire bus with http://localhost:3001/
It works. You can inspect and change values. Compilation is easy, but
I've posted a linux binary as well.

See: http://owfs.sourceforge.net

Paul Alfille

Note: I wish to thank Greg Olszewski for the chttpd code.


_______________________________________________
1-wire-software-development mailing list
1-w...@da...
To UNSUBSCRIBE, edit your profile, or visit the list archives, go to:
http://lists.dalsemi.com/mailman/listinfo/1-wire-software-development

[Owfs-developers] Clock DS1904

[Paul A. <pal...@ea...>]

Next version will include support for the clock-in-a-can DS1904.

filetypes will include:
running (0/1) rw Is the clock running?
clock (unsigned int 32) rw Clock counter

Examples:
To set to current time:
date +%s > /1wire/24.50AC02000000/clock

I think to interpret the time, a command line perl script will be
needed.

I'll havve to concoct it at some point.

Paul

[Owfs-developers] Change to binary output

[Paul A. <pal...@ea...>]

New version will feature binary output for memory reegisters of 1-wire
devices.

Examples:
2450 page0,1,2
2436 page0,1,2
2438 page 0,1,2,3,4,5,6,7
2406 memory
1820 scratchpad

Example of usage:

# od -h 1wire/22.367A03000000/scratchpad
0000000 016c 464b ff5f 1004
0000010

[Owfs-developers] Binary data

[Alfille, P. H.,M.D. <PAL...@PA...>]

After some thought, I wantto change the displayed format of memory to
straight binary, rather than an ascii representation.

Thus the 18S20's scratchpad will read as 8 bytes of binary data instead of
"00,45,10,A3,FF,FF,10,13".

This should make using the data in control processes easier, make memory
access more like a real file, and still allow
easy display when piped through "od"

Paul Alfille
 

[Owfs-developers] Version 0.8

[Paul A. <pal...@ea...>]

Supports 2406
Supports 1822

Cleaned up code a bit.
Added mail list to docs.

[Owfs-developers] Documentation

[Paul A. <pal...@ea...>]

We should include sample BASH scripts in the documentation.

An example:

X=`ls 1wire/*/tempC`; for f in $X; do d=`dirname $f`; echo "`cat
$d\address`: `cat $f`C"; done

which gives:
109A9E3C000800BC:       24.0625C
10D7AB3C000800D5:       24.0625C



 

[Owfs-developers] 2490 USB

[Alfille, P. H.,M.D. <PAL...@PA...>]

I've started looking at the USB connector. (I have one). It seems pretty
straightforward to write a kernel module to use it.

My design will be to make it look like a character device
(open/close/write/read).
Use the usb-skeleton driver as the base.
Make all normal i/o (read/write) be what the 2480B calls "data mode" --
communication with the 1-wire bus.
Use IOCLT calls to do the "command mode" stuff -- resets, set 1-wire waveform
design, overdrive settings, etc.

Any thoughts?

-- Paul