owfs-developers — Developer's list for OWFS

RE: [Owfs-developers] OWFS concurency

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

You're right! I think the best approach would be a semaphore flag
surrounding 1-wire conversations, with a time-out. Then the separate =
threads
could compete for the bus. I could make OWHTTPD multithreaded as well.

Paul

-----Original Message-----
From: Nicolas Huillard [mailto:nhu...@gh...]
Sent: Friday, August 29, 2003 5:50 AM
To: owfs
Subject: [Owfs-developers] OWFS concurency


I plan my application to have multiple little scripts that access the=20
directory tree. Since the 1-wire is inherently unique and exclusive, I=20
must not be able to access two devices at the same time.

This is currently the case, with various impact. Here is a little test=20
that run many (2) $t/tempC in parallel :

[nhuillard@palma:devices]$ for t in 10.*; do (echo $t $(cat $t/tempC)&=20
); done
cat: 10.26FE46000800/tempC: Invalid argument
10.26FE46000800
10.E42257000800 22.8125

[nhuillard@palma:devices]$ for t in 10.*; do (echo $t $(cat $t/tempC)&=20
); done
cat: 10.26FE46000800/tempC: Invalid argument
10.26FE46000800
cat: 10.E42257000800/tempC: Invalid argument
10.E42257000800

[nhuillard@palma:devices]$ for t in 10.*; do (echo $t $(cat $t/tempC)&=20
); done
cat: 10.26FE46000800/tempC: Invalid argument
10.26FE46000800
10.E42257000800 22.8125

As you can see, there is either an "Invalid argument" on one 1820, or =
on=20
both.
When the $t/tempC are slightly desynchronized (when I type the command=20
on two terminals, with a longer delay), one 1820 might return a 85=B0C=20
reading, indicating a wrong conversion.

A mono-threaded OWFS (like OWHTTDP) might be useful.

NH



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Owfs-developers mailing list
Owf...@li...
https://lists.sourceforge.net/lists/listinfo/owfs-developers

RE: [Owfs-developers] LCD over owfs

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

Hmm...

As I recall, Marc Nichols / Shawn Silverman's device uses a proprietary Java
driver. Actually, since OWFS is entirely in user space, that isn't truly a
problem. I'm not sure how you will get your input, keyboard? Is this a
console/terminal replacement?

Louis Swart's driver controls the HD44780 chip and he mentions screen sizes
up to 20x4 or 40x2.

Paul

-----Original Message-----
From: Nicolas Huillard [mailto:nhu...@gh...]
Sent: Friday, August 29, 2003 6:36 AM
To: 1-wire dev; owfs-developers
Cc: lc...@ge...
Subject: Re: [Owfs-developers] LCD over owfs


Having read the specs for the OWFS to LCD related stuff, I doubt my 
vision could be ever implemented...

Marc Nicholas and Shawn Silverman have implemented an LCD connected to a 
2408, as I remember (Marc's site is still empty after his crash, so I 
can't check) : can one of them explain how the software interface work ? 
Is the connected LCD based on standard HD44780 modules ?

What I describe below implies that the lynx process (text-only HTTP 
browser, allowing me to only develop a single user interface, usable on 
LAN or internet computers, or directly on the always-on LCD) is linked 
via it's STDIN/OUT file descriptors to always-open sockets on the OWFS, 
ie. continuous output to the file descriptor will send a continuous flow 
of data on the 1-wire network.
This continuous flow must not block other traffic... I think that's the 
problem there...

Comments on that ?

NH

PS : lynx is just a sample app. one can replace it by any ncurses 
text-only application, provided the application can work completely with 
the only few keys near the LCD...

Nicolas Huillard wrote:

> Paul Alfille wrote:
>  > LCD support is next.
> 
> Cool : I'd love to run lynx on my 40x24 LCD screen, with a few keys to 
> travel the pages.
>     $ TERM=vt100 TERMCAP=...li#24:co#40... \
>         attach-tty --stdin 1-wire/[2408]/sensed \
>         --stdout 1-wire/[2408]/PIO \
>         --mode 4bits_in_4_bits_out \
>         --stderr /var/log/owfs-tty.log \
>         lynx http://localhost/
> attach-tty is a imaginary but maybe already existing glue, that create a 
> tty from a read-only file (STDIN) and a write-only file (STDOUT), adding 
> a little environment and signal handling, that run the given command and 
> make sure to re-run it if it ever exits...
> Maybe I'm not dreaming, despite the current time in the night at GMT+2.
> 
> NH
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a single machine.
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
> at the same time. Free trial click 
> here:http://www.vmware.com/wl/offer/358/0
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers





-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Owfs-developers mailing list
Owf...@li...
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] LCD over owfs

[Nicolas H. <nhu...@gh...>]

Having read the specs for the OWFS to LCD related stuff, I doubt my 
vision could be ever implemented...

Marc Nicholas and Shawn Silverman have implemented an LCD connected to a 
2408, as I remember (Marc's site is still empty after his crash, so I 
can't check) : can one of them explain how the software interface work ? 
Is the connected LCD based on standard HD44780 modules ?

What I describe below implies that the lynx process (text-only HTTP 
browser, allowing me to only develop a single user interface, usable on 
LAN or internet computers, or directly on the always-on LCD) is linked 
via it's STDIN/OUT file descriptors to always-open sockets on the OWFS, 
ie. continuous output to the file descriptor will send a continuous flow 
of data on the 1-wire network.
This continuous flow must not block other traffic... I think that's the 
problem there...

Comments on that ?

NH

PS : lynx is just a sample app. one can replace it by any ncurses 
text-only application, provided the application can work completely with 
the only few keys near the LCD...

Nicolas Huillard wrote:

> Paul Alfille wrote:
>  > LCD support is next.
> 
> Cool : I'd love to run lynx on my 40x24 LCD screen, with a few keys to 
> travel the pages.
>     $ TERM=vt100 TERMCAP=...li#24:co#40... \
>         attach-tty --stdin 1-wire/[2408]/sensed \
>         --stdout 1-wire/[2408]/PIO \
>         --mode 4bits_in_4_bits_out \
>         --stderr /var/log/owfs-tty.log \
>         lynx http://localhost/
> attach-tty is a imaginary but maybe already existing glue, that create a 
> tty from a read-only file (STDIN) and a write-only file (STDOUT), adding 
> a little environment and signal handling, that run the given command and 
> make sure to re-run it if it ever exits...
> Maybe I'm not dreaming, despite the current time in the night at GMT+2.
> 
> NH
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a single machine.
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
> at the same time. Free trial click 
> here:http://www.vmware.com/wl/offer/358/0
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

[Owfs-developers] OWFS concurency

[Nicolas H. <nhu...@gh...>]

I plan my application to have multiple little scripts that access the 
directory tree. Since the 1-wire is inherently unique and exclusive, I 
must not be able to access two devices at the same time.

This is currently the case, with various impact. Here is a little test 
that run many (2) $t/tempC in parallel :

[nhuillard@palma:devices]$ for t in 10.*; do (echo $t $(cat $t/tempC)& 
); done
cat: 10.26FE46000800/tempC: Invalid argument
10.26FE46000800
10.E42257000800 22.8125

[nhuillard@palma:devices]$ for t in 10.*; do (echo $t $(cat $t/tempC)& 
); done
cat: 10.26FE46000800/tempC: Invalid argument
10.26FE46000800
cat: 10.E42257000800/tempC: Invalid argument
10.E42257000800

[nhuillard@palma:devices]$ for t in 10.*; do (echo $t $(cat $t/tempC)& 
); done
cat: 10.26FE46000800/tempC: Invalid argument
10.26FE46000800
10.E42257000800 22.8125

As you can see, there is either an "Invalid argument" on one 1820, or on 
both.
When the $t/tempC are slightly desynchronized (when I type the command 
on two terminals, with a longer delay), one 1820 might return a 85°C 
reading, indicating a wrong conversion.

A mono-threaded OWFS (like OWHTTDP) might be useful.

NH

RE: [Owfs-developers] Alarm directory

[Gregg C L. <han...@wo...>]

Hello (again) from Gregg C Levine
To be honest, I only use them for Thermochrons, and then using the
Win32 viewer arrangements. Do you mean the alarm functions on the
DS1820 type devices? So far I've only viewed the functions on the
Win32 viewer. Yes, for those of us who do use them, it would be a good
thing.=20
-------------------
Gregg C Levine han...@wo...
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."=A0 Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )

(Personal note to Paul, which port do you want me to use for the
OWHTTPD device? You gave me a strange suggestion for testing. I've got
mine connected to /dev/ttyS1 since the mouse is connected to
/dev/ttyS0. Physical port, not TCP port, that's still the one we've
been using since starting.)

> -----Original Message-----
> From: owf...@li...
[mailto:owfs-developers-
> ad...@li...] On Behalf Of Paul Alfille
> Sent: Thursday, August 28, 2003 10:27 PM
> To: owfs-developers
> Subject: [Owfs-developers] Alarm directory
>=20
> I gather that some people use the 1-wire alarm functions
(temperature,
> voltage, touch, etc). Would having a directory of alarming devices
be a
> good approach?
>=20
> Paul
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

[Owfs-developers] Alarm directory

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

I gather that some people use the 1-wire alarm functions (temperature,
voltage, touch, etc). Would having a directory of alarming devices be a
good approach?

Paul

RE: [Owfs-developers] Problem with OWHTTPD version 0.94

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

Umm... I guess not comprehensively.

There is a man page for owhttpd, and a web page with a little
information.

There's also a README in the main directory.

I'm eager for any corrections, modifications, documentation that anyone
wants to contribute. Desparate, actually.

Paul

(Actually, the d_fork thing is usually in there, but I comment it out in
my copy when testing so I can sprinkle printf's to debug. I occasionally
neglect to uncomment. Sorry.)

On Thu, 2003-08-28 at 22:30, Gregg C Levine wrote:
> Hello again from Gregg C Levine
> Okay. I'll try that. Is that documented anyplace else? We need to get
> comprehensive documentation uploaded someplace. Have you written any
> of this down? I mean the steps behind the whole process to make it
> work.
> -------------------
> Gregg C Levine han...@wo...
> ------------------------------------------------------------
> "The Force will be with you...Always." Obi-Wan Kenobi
> "Use the Force, Luke."  Obi-Wan Kenobi
> (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> (This company dedicates this E-Mail to Master Yoda )
> 
> 
> 
> > -----Original Message-----
> > From: Paul Alfille [mailto:pal...@ea...]
> > Sent: Thursday, August 28, 2003 10:11 PM
> > To: Gregg C Levine
> > Subject: Re: [Owfs-developers] Problem with OWHTTPD version 0.94
> > 
> > OWHTTPD behavior has changed. It goes into the background. Try 'ps
> -axf'
> > To test I usually run the command:
> > killall owhttpd ; make all ; make install ; owhttpd -p 3001 -d
> > /dev/ttyM6
> > 
> > If you don't like this behavior, you can take out the line (in
> main.c)
> > d_fork(debugmode) ;
> > 
> > I guess I should make this a command line option!
> > 
> > Paul
> > 
> > On Thu, 2003-08-28 at 21:51, Gregg C Levine wrote:
> > > Hello from Gregg C Levine
> > > This was a normal build for this version. However, it refuses to
> stay
> > > resident for me to test it. As soon as I run it, it stops. However
> the
> > > regular OWFS one, works as advertised. However, it needs a
> control-C
> > > to interrupt it.
> > > -------------------
> > > Gregg C Levine han...@wo...
> > > ------------------------------------------------------------
> > > "The Force will be with you...Always." Obi-Wan Kenobi
> > > "Use the Force, Luke."  Obi-Wan Kenobi
> > > (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> > > (This company dedicates this E-Mail to Master Yoda )
> > >
> > >
> > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > Owfs-developers mailing list
> > > Owf...@li...
> > > https://lists.sourceforge.net/lists/listinfo/owfs-developers
> 

Re: [Owfs-developers] Problem with OWHTTPD version 0.94

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

OWHTTPD has reverted to its proper mode of going into the background.
I'll make it a command line option.

I tested out unmounting the directory, it cleanly closes the filesystem
for me except for an "not found in /etc/mtab" warning.

Paul

On Thu, 2003-08-28 at 21:51, Gregg C Levine wrote:
> Hello from Gregg C Levine
> This was a normal build for this version. However, it refuses to stay
> resident for me to test it. As soon as I run it, it stops. However the
> regular OWFS one, works as advertised. However, it needs a control-C
> to interrupt it.
> -------------------
> Gregg C Levine han...@wo...
> ------------------------------------------------------------
> "The Force will be with you...Always." Obi-Wan Kenobi
> "Use the Force, Luke."  Obi-Wan Kenobi
> (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> (This company dedicates this E-Mail to Master Yoda )
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

[Owfs-developers] Problem with OWHTTPD version 0.94

[Gregg C L. <han...@wo...>]

Hello from Gregg C Levine
This was a normal build for this version. However, it refuses to stay
resident for me to test it. As soon as I run it, it stops. However the
regular OWFS one, works as advertised. However, it needs a control-C
to interrupt it.
-------------------
Gregg C Levine han...@wo...
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."=A0 Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )

[Owfs-developers] PD Kit

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

As I wrote you privately, the PDKit was certainly used for some of the
low-level coding, and as a basis for some of the device communication,
especially the search algorhythm. OWFS has (to my mind) a cleaner
interface, which I'm starting to document.

1. Each 1-wire device has it's own file. Each property has it's own
functions to read or write.
2. The command and data strings that go out over the bus are cleaner:
 A. Command (to the DS2480B)
    BUS_send_cmd(str,bytes) -- send a str and check that the echo
matches
    BUS_sendout_cmd(str,bytes) send a str, no echo read
    BUS_sendback_cmd(str,resp,bytes) send a string, read response in.
 B. Data (to the 1-wire bus)
    BUS_send_data(str,bytes) -- send a str and check that the echo
matches
    BUS_sendout_data(str,bytes) send a str, no echo read
    BUS_sendback_data(str,resp,bytes) send a string, read response in.

So instead of adding the mode shifts, echo checking etc to each
interaction explicitly, these intermediate routines are used. The
general gist is easier to see.

OWFS employs fewer global variables, and doesn't have the interface
index (portnum) as part of every call. (For more than one interface, I
expect OWFS to be called multiple times.)

OWFS doesn't support all the 1-wire functions. First I don't have all
the devices, second not all functions fit easily into a filesystem
model, and lastly, I am aiming for simplicity over completeness.

I expect that OWFS, and especially OWHTTPD will be used for easy tasks,
and testing. Complex transactions and speed-critical work may be better
served by another approach. Still, I could be surprised.

Re: [Owfs-developers] RE: OWFS

[Nicolas H. <nhu...@gh...>]

Paul Alfille wrote:
> Actually, I just was trying to get an error on ctrl-C.
...
> 3. cd /mnt/1wire
>   ahha! fusermount: failed to unmount /mnt/1wire: Device or resource
> busy.

I think this is totally normal (in kernel 2.4), and it happens with NFS 
also. The problem here is that the ow program can quit even if the fs is 
still mounted. That doesn't happen with NFS since the FS code is in the 
kernel.
Maybe you should catch ^C, try to unmount, and not quit if unmount was 
not successful : in order to keep the owfs working.
On 2.4, with NFS, when I want to force unmount, I type the following 
command before : fuser -mk /mnt/.../
This command kills (-k) all processes accessing in any way the mounted 
(-m) filesystem given as argument.

NH

[Owfs-developers] Version 0.94

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

Support for memory iButtons DS1992, DS1993, and DS1996.

Expanded width of data fields in web pages.

Paul

[Owfs-developers] RE: OWFS

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

Actually, I just was trying to get an error on ctrl-C.

1. First "tree -a /mnt/1wire
  no error. Perhaps problem is not multithreaded request?
2/ Second 'cat /mnt/1wire/*/tempC
  no error.
3. cd /mnt/1wire
  ahha! fusermount: failed to unmount /mnt/1wire: Device or resource
busy.
4. From the author of FUSE:
>           From: 
> Miklos Szeredi
> <Mik...@et...>
>             To: 
> pal...@ea...
>        Subject: 
> Re: fuse
>           Date: 
> Wed, 27 Aug 2003
> 10:02:14 +0200
> (MEST)
> 
> 
> > I'm getting many questions, now, on FUSE:
> > 
> > 1. mounting/unmounting seems a little awkward. mount points do not
> seem
> > to be cleanly released.
> 
> Yes, that is something that will be cleanly solved by the forced
> unmount thing in linux 2.6.

So this may not be easy to fix.

Paul

On Wed, 2003-08-27 at 21:12, Gregg C Levine wrote:
> Hello from Gregg C Levine
> Is that what it is? Nice to know we've got an idea what it is. Next
> time I run things here, I'll make an effort to trap the debugging
> output via a script file, from the one-wire program. Now the joker,
> what part of the decoded oops gave you the clew? It looked like
> typical Pentium assembler language to me.
> -------------------
> Gregg C Levine han...@wo...
> ------------------------------------------------------------
> "The Force will be with you...Always." Obi-Wan Kenobi
> "Use the Force, Luke."  Obi-Wan Kenobi
> (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> (This company dedicates this E-Mail to Master Yoda )
> 
> 
> 
> > -----Original Message-----
> > From: Paul Alfille [mailto:pal...@ea...]
> > Sent: Wednesday, August 27, 2003 8:51 PM
> > To: Gregg C Levine
> > Subject: RE: OWFS
> > 
> > Ahha,
> > Yes, when you quit OWFS, all sort of nasty messages appear. Seems
> > harmless, but ugly. Something about device not open, etc. I suspect
> I'm
> > trying to close the com port in each of the threads.
> > 
> > I'd certainly like to chase down each of these awkward bugs. It
> would
> > certainly give me more confidence of the program.
> > 
> > Paul
> > 
> > On Tue, 2003-08-26 at 23:53, Gregg C Levine wrote:
> > > Hello from Gregg C Levine
> > > I haven't as of right now had the chance to run the oops decoder
> that
> > > I've got squirreled away someplace, on that oops message. As far
> as I
> > > can tell, this happened, when I interrupted the owfs program with
> a
> > > control-C, so that I could close the windows, and leave the KDE
> > > desktop. I saw it, when I ran dmesg to see if anything was printed
> > > there, via that action.
> > > Tomorrow on the other hand, I'll have more information for you. On
> the
> > > third hand (?), I don't think my manipulating a DS2406 at the file
> in
> > > named directory level caused it. At the shell prompt I would type
> > > either a "#echo "1" > PIO_A", to turn the output on, or a "#echo
> "0" >
> > > PIO_A" to turn it off. So, as I stated earlier I'll run the oops
> > > through the decoder, and then post the output on a second reply to
> > > your message. This is with the latest version of the ow program.
> > > -------------------
> > > Gregg C Levine han...@wo...
> > > ------------------------------------------------------------
> > > "The Force will be with you...Always." Obi-Wan Kenobi
> > > "Use the Force, Luke."  Obi-Wan Kenobi
> > > (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> > > (This company dedicates this E-Mail to Master Yoda )
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Paul Alfille [mailto:pal...@ea...]
> > > > Sent: Tuesday, August 26, 2003 11:07 PM
> > > > To: Gregg C Levine
> > > > Cc: owfs-developers
> > > > Subject: RE: OWFS
> > > >
> > > > Please explain what you mean.
> > > >
> > > > Is it a particular device? (Not all are really tested, I don't
> have
> > > > all the chips and in any case didn't exhaustively test
> everything.)
> > > >
> > > > Is it memory access? I do split large memory requests into many
> > > > smaller ones in a not very efficient manner. Perhaps we have a
> stack
> > > > overflow.
> > > >
> > > > That would be easy to fix,
> > > >
> > > > Instead of
> > > > if (size>16) return GetMem( 16) || GetMem( size-16)
> > > >
> > > > I could do a binary split, or tail recusion, or iterative
> > > techniques.
> > > >
> > > > Paul
> > > >
> > > > On Tue, 2003-08-26 at 21:51, Gregg C Levine wrote:
> > > > > Hello again from Gregg C Levine
> > > > > Oh, and yes, and no. Yes, because when I commented it out it
> > > compiled
> > > > > okay, but through an oops instead. I tried an earlier version,
> and
> > > it
> > > > > through one as well. Its a fuse issue, it seems the loaded
> module
> > > > > can't support the paging aspects of the program.
> > > > > -------------------
> > > > > Gregg C Levine han...@wo...
> > > > > ------------------------------------------------------------
> > > > > "The Force will be with you...Always." Obi-Wan Kenobi
> > > > > "Use the Force, Luke."  Obi-Wan Kenobi
> > > > > (This company dedicates this E-Mail to General Obi-Wan Kenobi
> )
> > > > > (This company dedicates this E-Mail to Master Yoda )
> > > > >
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Paul Alfille [mailto:pal...@ea...]
> > > > > > Sent: Tuesday, August 26, 2003 8:35 PM
> > > > > > To: Gregg C Levine
> > > > > > Subject: OWFS
> > > > > >
> > > > > > Hi Gregg,
> > > > > >
> > > > > > Usually, I comment out the line in main.c that calls dfork
> when
> > > I
> > > > > debug
> > > > > > so I can see  console messages. Is that the problem?
> > > > > >
> > > > > > Paul
> > > > > >
> > > > >
> > > > >
> > >
> 

[Owfs-developers] RE: OWFS

[Gregg C L. <han...@wo...>]

Hello again from Gregg C Levine
As I stated, last night, I wasn't able to run the resulting oops
message through the symbolic decoder that was written for decoding
such messages. The author makes it available from the Kernel.ORG
sites, both mirror, and actual site, and its called ksymoops, I simply
ran the text file containing the oops code through it, and it gave me
this message:
ksymoops 2.4.9 on i586 2.4.19.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.19/ (default)
     -m /usr/src/linux/System.map (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol
resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to
find
map, modules, ksyms etc.  ksymoops -h explains the options.

c0113dd8
*pde =3D 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c0113dd8>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010887
eax: c1e56e00   ebx: 5a5a5a5a   ecx: 00000000   edx: 00000003
esi: c0cb1600   edi: 00000000   ebp: c1449f04   esp: c1449eec
ds: 0018   es: 0018   ss: 0018
Process fusermount (pid: 521, stackpage=3Dc1449000)
Stack: c1e56dec c0cb1600 c2854c80 c1e56e00 00000286 00000003 c1449f34
c2854283=20
       c1e56dec c1449f34 c0143f32 c1449f2c c0cb1600 c0cb1644 c2854c80
c2854c80=20
       c1449f2c c1449f2c c1449f4c c0136e61 c0cb1600 c105c3f0 c0cb1600
c1449f90=20
Call Trace:    [<c2854c80>] [<c2854283>] [<c0143f32>] [<c2854c80>]
[<c2854c80>]
  [<c0136e61>] [<c0145a78>] [<c013a745>] [<c01460bc>] [<c0132163>]
[<c01460d6>]
  [<c0108a73>]
Code: 8b 4b fc 8b 01 85 45 fc 74 4e 31 c0 9c 5e fa c7 01 00 00 00=20


>>EIP; c0113dd8 <__wake_up+28/98>   <=3D=3D=3D=3D=3D

>>eax; c1e56e00 <_end+1b54124/2503324>
>>esi; c0cb1600 <_end+9ae924/2503324>
>>ebp; c1449f04 <_end+1147228/2503324>
>>esp; c1449eec <_end+1147210/2503324>

Trace; c2854c80 <[fuse]fuse_super_operations+0/44>
Trace; c2854283 <[fuse]fuse_put_super+47/50>
Trace; c0143f32 <invalidate_inodes+62/70>
Trace; c2854c80 <[fuse]fuse_super_operations+0/44>
Trace; c2854c80 <[fuse]fuse_super_operations+0/44>
Trace; c0136e61 <kill_super+a5/e0>
Trace; c0145a78 <__mntput+20/2c>
Trace; c013a745 <path_release+29/30>
Trace; c01460bc <sys_umount+a0/ac>
Trace; c0132163 <sys_llseek+c7/d4>
Trace; c01460d6 <sys_oldumount+e/14>
Trace; c0108a73 <system_call+33/40>

Code;  c0113dd8 <__wake_up+28/98>
0000000000000000 <_EIP>:
Code;  c0113dd8 <__wake_up+28/98>   <=3D=3D=3D=3D=3D
   0:   8b 4b fc                  mov    0xfffffffc(%ebx),%ecx
<=3D=3D=3D=3D=3D
Code;  c0113ddb <__wake_up+2b/98>
   3:   8b 01                     mov    (%ecx),%eax
Code;  c0113ddd <__wake_up+2d/98>
   5:   85 45 fc                  test   %eax,0xfffffffc(%ebp)
Code;  c0113de0 <__wake_up+30/98>
   8:   74 4e                     je     58 <_EIP+0x58> c0113e30
<__wake_up+80/98>
Code;  c0113de2 <__wake_up+32/98>
   a:   31 c0                     xor    %eax,%eax
Code;  c0113de4 <__wake_up+34/98>
   c:   9c                        pushf =20
Code;  c0113de5 <__wake_up+35/98>
   d:   5e                        pop    %esi
Code;  c0113de6 <__wake_up+36/98>
   e:   fa                        cli   =20
Code;  c0113de7 <__wake_up+37/98>
   f:   c7 01 00 00 00 00         movl   $0x0,(%ecx)


1 warning issued.  Results may not be reliable.
It was pretty annoyed that I didn't set any defaults before running
it. But since I always get that problem when I run it, I don't run it
very often. Apologies for those of you who weren't aware for such
longish messages. Oh, and here's the actual oops:
c0113dd8
*pde =3D 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c0113dd8>]    Not tainted
EFLAGS: 00010887
eax: c1e56e00   ebx: 5a5a5a5a   ecx: 00000000   edx: 00000003
esi: c0cb1600   edi: 00000000   ebp: c1449f04   esp: c1449eec
ds: 0018   es: 0018   ss: 0018
Process fusermount (pid: 521, stackpage=3Dc1449000)
Stack: c1e56dec c0cb1600 c2854c80 c1e56e00 00000286 00000003 c1449f34
c2854283=20
       c1e56dec c1449f34 c0143f32 c1449f2c c0cb1600 c0cb1644 c2854c80
c2854c80=20
       c1449f2c c1449f2c c1449f4c c0136e61 c0cb1600 c105c3f0 c0cb1600
c1449f90=20
Call Trace:    [<c2854c80>] [<c2854283>] [<c0143f32>] [<c2854c80>]
[<c2854c80>]
  [<c0136e61>] [<c0145a78>] [<c013a745>] [<c01460bc>] [<c0132163>]
[<c01460d6>]
  [<c0108a73>]

Code: 8b 4b fc 8b 01 85 45 fc 74 4e 31 c0 9c 5e fa c7 01 00 00 00=20
=20
The oops symbolic decoder came up with what I posted earlier, from
that. Paul I do hope this helps you. As I said, it only happens when I
use Control-C to exit from the loop.
-------------------
Gregg C Levine han...@wo...
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."=A0 Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )



> -----Original Message-----
> From: Paul Alfille [mailto:pal...@ea...]
> Sent: Tuesday, August 26, 2003 11:07 PM
> To: Gregg C Levine
> Cc: owfs-developers
> Subject: RE: OWFS
>=20
> Please explain what you mean.
>=20
> Is it a particular device? (Not all are really tested, I don't have
> all the chips and in any case didn't exhaustively test everything.)
>=20
> Is it memory access? I do split large memory requests into many
> smaller ones in a not very efficient manner. Perhaps we have a stack
> overflow.
>=20
> That would be easy to fix,
>=20
> Instead of
> if (size>16) return GetMem( 16) || GetMem( size-16)
>=20
> I could do a binary split, or tail recusion, or iterative
techniques.
>=20
> Paul
>=20
> On Tue, 2003-08-26 at 21:51, Gregg C Levine wrote:
> > Hello again from Gregg C Levine
> > Oh, and yes, and no. Yes, because when I commented it out it
compiled
> > okay, but through an oops instead. I tried an earlier version, and
it
> > through one as well. Its a fuse issue, it seems the loaded module
> > can't support the paging aspects of the program.
> > -------------------
> > Gregg C Levine han...@wo...
> > ------------------------------------------------------------
> > "The Force will be with you...Always." Obi-Wan Kenobi
> > "Use the Force, Luke."  Obi-Wan Kenobi
> > (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> > (This company dedicates this E-Mail to Master Yoda )
> >
> >
> >
> > > -----Original Message-----
> > > From: Paul Alfille [mailto:pal...@ea...]
> > > Sent: Tuesday, August 26, 2003 8:35 PM
> > > To: Gregg C Levine
> > > Subject: OWFS
> > >
> > > Hi Gregg,
> > >
> > > Usually, I comment out the line in main.c that calls dfork when
I
> > debug
> > > so I can see  console messages. Is that the problem?
> > >
> > > Paul
> > >
> >
> >

RE: [Owfs-developers] Some thoughts on controlling devices

[Gregg C L. <han...@wo...>]

Hello again from Gregg C Levine
Wrong deduction. I was in to electronics, and everything connected
with it, before I discovered computers. Now I frequently build my own
peripheral device when I can't find one available for sale, some
place. Yes, I was following that thread, regarding his work, but where
is he based? No, that's not an option.
-------------------
Gregg C Levine han...@wo...
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."=A0 Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )



> -----Original Message-----
> From: owf...@li...
[mailto:owfs-developers-
> ad...@li...] On Behalf Of Nicolas Huillard
> Sent: Wednesday, August 27, 2003 7:55 AM
> To: owf...@li...
> Subject: Re: [Owfs-developers] Some thoughts on controlling devices
>=20
> Sytse Kuijk sells assembled boards containing a 2406 and two relays
> (with diodes, connectors, etc.). You can find him on the 1-wire list
> (search for subject containing "relay").
> There is also a schematic on connecting relays to the 2406/2408 on
the
> respective spec sheets.
>=20
> I'm deducing that you're not a hard-core electronic engineer : do
you
> plan to buy already build boards, or design and make you own the
hard way ?
> I'm wondering if it's worse the cost investing in all the tools
needed
> to build boards and solder on them, etc. for a software engineer.
>=20
> NH
>=20
> Gregg C Levine wrote:
>=20
> > Hello from Gregg C Levine
> > Now that Paul's OWFS project is off an running, I have a question,
or
> > at least a thought I want to bounce off on all of you.
> >
> > For a project I am creating I need to be able to turn on, and off,
a
> > device that's powered by the mains, (110VAC or 220VAC Europe),
since
> > this would be done remotely, I want to use a one-wire switch as
the
> > DS2406. I am correct, in my assertions that the DS2406 can not
switch
> > such voltages directly, I believe. Do any of you have any
suggestions
> > for attaching the one-wire switch to the circuit?
> >
> > I'll have more on the project in the weeks, and months to come.
> > -------------------
> > Gregg C Levine han...@wo...
> > ------------------------------------------------------------
> > "The Force will be with you...Always." Obi-Wan Kenobi
> > "Use the Force, Luke."  Obi-Wan Kenobi
> > (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> > (This company dedicates this E-Mail to Master Yoda )
> >
> >
> >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Owfs-developers mailing list
> > Owf...@li...
> > https://lists.sourceforge.net/lists/listinfo/owfs-developers
>=20
> --
> Nicolas Huillard
> Directeur Technique
> GHS Solutions Interactives
> 38, rue du Texel - 75014 PARIS - FRANCE
> T=E9l. 01 43 21 16 66 - Fax 01 56 54 02 18
> E-mail : nhu...@gh... - URL : http://www.ghs.fr
> --------------------------------------------------------------------
> e-dition, la solution Internet pour la presse =E9crite et l'=E9dition
>=20
> Visitez notre site : http://www.e-dition.fr
> --------------------------------------------------------------------
> Nos derni=E8res r=E9alisations :
>=20
> http://www.france-chimie.com
> http://www.cnr.fr
> http://www.esf-editeur.fr
> --------------------------------------------------------------------
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Some thoughts on controlling devices

[Nicolas H. <nhu...@gh...>]

Sytse Kuijk sells assembled boards containing a 2406 and two relays 
(with diodes, connectors, etc.). You can find him on the 1-wire list 
(search for subject containing "relay").
There is also a schematic on connecting relays to the 2406/2408 on the 
respective spec sheets.

I'm deducing that you're not a hard-core electronic engineer : do you 
plan to buy already build boards, or design and make you own the hard way ?
I'm wondering if it's worse the cost investing in all the tools needed 
to build boards and solder on them, etc. for a software engineer.

NH

Gregg C Levine wrote:

> Hello from Gregg C Levine
> Now that Paul's OWFS project is off an running, I have a question, or
> at least a thought I want to bounce off on all of you.
> 
> For a project I am creating I need to be able to turn on, and off, a
> device that's powered by the mains, (110VAC or 220VAC Europe), since
> this would be done remotely, I want to use a one-wire switch as the
> DS2406. I am correct, in my assertions that the DS2406 can not switch
> such voltages directly, I believe. Do any of you have any suggestions
> for attaching the one-wire switch to the circuit? 
> 
> I'll have more on the project in the weeks, and months to come. 
> -------------------
> Gregg C Levine han...@wo...
> ------------------------------------------------------------
> "The Force will be with you...Always." Obi-Wan Kenobi
> "Use the Force, Luke."  Obi-Wan Kenobi
> (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> (This company dedicates this E-Mail to Master Yoda )
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

-- 
Nicolas Huillard
Directeur Technique
GHS Solutions Interactives
38, rue du Texel - 75014 PARIS - FRANCE
Tél. 01 43 21 16 66 - Fax 01 56 54 02 18
E-mail : nhu...@gh... - URL : http://www.ghs.fr
--------------------------------------------------------------------
e-dition, la solution Internet pour la presse écrite et l'édition

Visitez notre site : http://www.e-dition.fr
--------------------------------------------------------------------
Nos dernières réalisations :

http://www.france-chimie.com
http://www.cnr.fr
http://www.esf-editeur.fr
--------------------------------------------------------------------

Re: [Owfs-developers] Advice from one individual to others regarding cable making

[Nicolas H. <nhu...@gh...>]

Gregg C Levine wrote:
> Hello from Gregg C Levine
> And as it happens there's no real standard as to how the companies who
> make the cables that use the RJ-11 connectors. Sometimes one end is
> wired correctly, sometimes the other is swapped.

I even have a RJ-11 to RJ-11 cable from the 1-wire demo kit that is 
wired incorrectly. That part is sold by Dallas, and meant to demo good 
1-wire use...

NH

Re: [1-wire]Re: [Owfs-developers] What software do you (plan to)

[Vadim T. <vt...@fr...>]

According to Paul Alfille:

> How do you monitor device arrival/departure. I've been looking through
> the documentation and it isn't obvious (beside polling).

Lemme see... That'll be net.sf.dz.daemon.onewire.OneWireNetworkMonitor.
Basically, it tries to search the 1-wire network when it has the chance, and
notifies the listeners when devices arrive or depart.

This is obviously not the scheme you'd want to implement, because it's
tightly coupled to the Java way of doing things. Watching arrival signals on
low level, and issuing the arrival notifications through the mechanism that
you'd consider the best is the way to go.
 
> Paul

--vt

Re: [Owfs-developers] [1-wire]RE: OWFS

[Vadim T. <vt...@fr...>]

According to Paul Alfille:

> I notice that OWHTTPD doesn't seem to like simultaneous requests. I need
> to find a way to block the next request until the current one is
> finished.
> 
> (I made OWHTTPD single-threaded, since the 1-wire bus is single
> threaded).

This is another thing I'd like to see fixed - beginExclusive/endExclusive is
not the best way to do things, from where I'm standing. The best way, IMHO,
is scoped locking pattern per Schmidt (entry point:
http://128.252.165.3/~schmidt/patterns-ace.html - a lot of useful things,
highly recommended). I did provide some analysis on this at haywire.sf.net.

> Paul

--vt

[Owfs-developers] Advice from one individual to others regarding cable making

[Gregg C L. <han...@wo...>]

Hello from Gregg C Levine
Everyone on both lists, please don't fire a flamethrower at me, or
even stop reading my posts in disgust, but this is only free advice
regarding cable for the One-Wire network.

I just found this one out. When wiring a cable for a bread-boarded
connection, to a One-Wire connectoid, any of the three supported by
the company, plus the Link, and your using phone company style
connectors, remember to match polarity at each ends. It gets very
frustrating having to constantly rewire stuff.=20

And as it happens there's no real standard as to how the companies who
make the cables that use the RJ-11 connectors. Sometimes one end is
wired correctly, sometimes the other is swapped. I finally decided to
wire my own, using a length of Quad Four, and two connectors.
Naturally at the end that's terminated at the bread board, I needed to
swap those leads. Any complaints please do so, but off list, that goes
for both.
-------------------
Gregg C Levine han...@wo...
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."=A0 Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )

[Owfs-developers] RE: OWFS

[Gregg C L. <han...@wo...>]

Hello from Gregg C Levine
I haven't as of right now had the chance to run the oops decoder that
I've got squirreled away someplace, on that oops message. As far as I
can tell, this happened, when I interrupted the owfs program with a
control-C, so that I could close the windows, and leave the KDE
desktop. I saw it, when I ran dmesg to see if anything was printed
there, via that action.
Tomorrow on the other hand, I'll have more information for you. On the
third hand (?), I don't think my manipulating a DS2406 at the file in
named directory level caused it. At the shell prompt I would type
either a "#echo "1" > PIO_A", to turn the output on, or a "#echo "0" >
PIO_A" to turn it off. So, as I stated earlier I'll run the oops
through the decoder, and then post the output on a second reply to
your message. This is with the latest version of the ow program.
-------------------
Gregg C Levine han...@wo...
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."=A0 Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )



> -----Original Message-----
> From: Paul Alfille [mailto:pal...@ea...]
> Sent: Tuesday, August 26, 2003 11:07 PM
> To: Gregg C Levine
> Cc: owfs-developers
> Subject: RE: OWFS
>=20
> Please explain what you mean.
>=20
> Is it a particular device? (Not all are really tested, I don't have
> all the chips and in any case didn't exhaustively test everything.)
>=20
> Is it memory access? I do split large memory requests into many
> smaller ones in a not very efficient manner. Perhaps we have a stack
> overflow.
>=20
> That would be easy to fix,
>=20
> Instead of
> if (size>16) return GetMem( 16) || GetMem( size-16)
>=20
> I could do a binary split, or tail recusion, or iterative
techniques.
>=20
> Paul
>=20
> On Tue, 2003-08-26 at 21:51, Gregg C Levine wrote:
> > Hello again from Gregg C Levine
> > Oh, and yes, and no. Yes, because when I commented it out it
compiled
> > okay, but through an oops instead. I tried an earlier version, and
it
> > through one as well. Its a fuse issue, it seems the loaded module
> > can't support the paging aspects of the program.
> > -------------------
> > Gregg C Levine han...@wo...
> > ------------------------------------------------------------
> > "The Force will be with you...Always." Obi-Wan Kenobi
> > "Use the Force, Luke."  Obi-Wan Kenobi
> > (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> > (This company dedicates this E-Mail to Master Yoda )
> >
> >
> >
> > > -----Original Message-----
> > > From: Paul Alfille [mailto:pal...@ea...]
> > > Sent: Tuesday, August 26, 2003 8:35 PM
> > > To: Gregg C Levine
> > > Subject: OWFS
> > >
> > > Hi Gregg,
> > >
> > > Usually, I comment out the line in main.c that calls dfork when
I
> > debug
> > > so I can see  console messages. Is that the problem?
> > >
> > > Paul
> > >
> >
> >

[Owfs-developers] RE: OWFS

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

Please explain what you mean.

Is it a particular device? (Not all are really tested, I don't have
all the chips and in any case didn't exhaustively test everything.)

Is it memory access? I do split large memory requests into many
smaller ones in a not very efficient manner. Perhaps we have a stack
overflow.

That would be easy to fix,

Instead of
if (size>16) return GetMem( 16) || GetMem( size-16)

I could do a binary split, or tail recusion, or iterative techniques.

Paul

On Tue, 2003-08-26 at 21:51, Gregg C Levine wrote:
> Hello again from Gregg C Levine
> Oh, and yes, and no. Yes, because when I commented it out it compiled
> okay, but through an oops instead. I tried an earlier version, and it
> through one as well. Its a fuse issue, it seems the loaded module
> can't support the paging aspects of the program.
> -------------------
> Gregg C Levine han...@wo...
> ------------------------------------------------------------
> "The Force will be with you...Always." Obi-Wan Kenobi
> "Use the Force, Luke."  Obi-Wan Kenobi
> (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> (This company dedicates this E-Mail to Master Yoda )
> 
> 
> 
> > -----Original Message-----
> > From: Paul Alfille [mailto:pal...@ea...]
> > Sent: Tuesday, August 26, 2003 8:35 PM
> > To: Gregg C Levine
> > Subject: OWFS
> > 
> > Hi Gregg,
> > 
> > Usually, I comment out the line in main.c that calls dfork when I
> debug
> > so I can see  console messages. Is that the problem?
> > 
> > Paul
> > 
> 
> 

[Owfs-developers] OWFS LCD support

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

Version 0.93 of OWFS and OWHTTPD now supports Stuart Swart's 1-wire LCD.
See http://owfs.sourceforge.net

You can send text to the screen with a command line:

echo "1-wire rules!" > /mnt/1wire/FF.3D0100000100/screen16
(for a 16 character wide screen)

You can also address each line individually.
echo "2nd line" > /mnt/1wire/FF.3D0100000100/line20.1

Other properties: LCD on/off. Backlight on/off. Capture the buttons
and counters. Memory.

The web interface also supports all these features.

More on the 1-wire LCD at http://www.dreamwater.org/biz/louisswart/
 

[Owfs-developers] RE: OWFS

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

I notice that OWHTTPD doesn't seem to like simultaneous requests. I need
to find a way to block the next request until the current one is
finished.

(I made OWHTTPD single-threaded, since the 1-wire bus is single
threaded).

Paul

On Tue, 2003-08-26 at 21:10, Gregg C Levine wrote:
> Hello again from Gregg C Levine
> Yes. I was able to build the program without comments, or complaints
> from the tools. But now I am getting random segmentation faults with
> the program. The script file I created, that is a BASH script: (and it
> looks like that)
> #!/bin/sh
> owhttpd -p 3001 -d /dev/ttyS1
> 
> The console gave me that fault, along with the different PID for each
> time I ran the program. I simply found, and commented out the use of
> the fork request. Should I go back, and comment out the creation of
> the whole fork request function?
> Also the regular OWFS program does allow me to adjust the settings for
> the DS2406. Nice work.
> -------------------
> Gregg C Levine han...@wo...
> ------------------------------------------------------------
> "The Force will be with you...Always." Obi-Wan Kenobi
> "Use the Force, Luke."  Obi-Wan Kenobi
> (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> (This company dedicates this E-Mail to Master Yoda )
> 
> 
> 
> > -----Original Message-----
> > From: Paul Alfille [mailto:pal...@ea...]
> > Sent: Tuesday, August 26, 2003 8:35 PM
> > To: Gregg C Levine
> > Subject: OWFS
> > 
> > Hi Gregg,
> > 
> > Usually, I comment out the line in main.c that calls dfork when I
> debug
> > so I can see  console messages. Is that the problem?
> > 
> > Paul
> > 
> 
> 

Re: [1-wire]Re: [Owfs-developers] What software do you (plan to)

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

How do you monitor device arrival/departure. I've been looking through
the documentation and it isn't obvious (beside polling).

Paul

On Mon, 2003-08-25 at 20:12, Vadim Tkachenko wrote:
> According to Paul Alfille:
> 
> > On Sat, 2003-08-23 at 18:46, Nicolas Huillard wrote:
> 
> > > Vadim Tkachenko wrote:
> > > >>* will it need alarms or detection of new devices (like iButton arrival)
> > > > 
> > > > Definitely. And departure, too. For me, this is a mission critical thing: If
> > > > the switches or sensors are gone, that's really bad.
> > > 
> > > I agree. It's critical that devices attached to the network remain attached.
> > > I was referencing iButton comming temporarily (like ID chips), that the 
> > > software must intercept to act accordingly (ie. open the door).
> > > I don't know if OWFS has a mechanism to allow such detection of unknown 
> > > devices.
> > > 
> > > NH
> > > 
> > 
> > Can either of you expand on this? Why do you want arrival and departure
> > notices?
> 
> In my case, a departure of a device means a network failure, either
> transient or permanent. Since the actuators control multi thousand dollar
> hardware, and the hardware itself may be pretty dumb, alarm notifications
> are critical, otherwise the losses will be huge. They will also be further
> complicated by the fact that it will be extremely difficult to talk to home
> warranty company or a manufacturer and convince them that the HVAC unit is
> at fault, not the DIY piece of hardware and software.
> 
> > Are you scanning for ibutton contacts?
> 
> Not yet, however, if DZ ever gets to implement a "Bill Gates" mode when you
> can touch the socket with your iButton and have the house set up your way,
> then yes.
> 
> > OWFS doesn't care if devices come or go. The current implementation is
> > almost entirely stateless. It only knows that a device might exist
> > because it's ID is the filename. It will only read existing devices.
> > There should be know ghosts, and no memory creep.
> 
> That's OK, but arrival/departure notifications are a must for mission
> critical applications.
>  
> > I plan to have a fancier caching version, perhaps with hash tables, and
> > cache of volatile (temperature) and stable (switch states) data, but
> > I suspect it will introduce other problems.
> 
> Yes, it will. Every time a switch departs and then arrives back, you must
> make sure its state is the same as before departure (if there was no control
> input in the meantime). I've tried to make this transparent, it worked more
> or less fine, but slow since it was competing with other 1-wire traffic.
> 
> > Paul Alfille
> _______________________________________________
> 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
>