Hmm, that's a good question.  My init line is as follows:

OW::init("$port --timeout_directory=1 --timeout_presence=1 
--timeout_volatile=1 --timeout_stable=1");

Should I add other flags?  Sorry, I don't understand how the caching 
works, I thought that setting the above timeouts to 1 would effectively 
stop caching...

Thx.

Chris.

Paul Alfille wrote:
> uncached?
>
> On Feb 19, 2008 2:29 PM, Chris Maresca <[EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>> wrote:
>
>     I wrote the code in Perl.   Basically, it's a giant while() statement
>     that calls OW::get twice each loop.  Each time OW::get is called, it
>     stuffs the list of whatever gets returned into an array, then compares
>     the two arrays for differences.  If there is a difference, it
>     prints out
>     the device ID.
>
>     It works, but not very reliably.  I found I had to insert a sleep
>     statement (for 1 second) or it would not pickup new devices.   I'm now
>     thinking that perhaps I should only do the baseline scan every 10
>     loops
>     or something.
>
>     Chris.
>
>     Paul Alfille wrote:
>     > In my tests, OWFS can read and respond in < 0.1 second.
>     >
>     > There are some tricks for fast operation:
>     > 1. Segment the 1-wire bus with separate a BUSMASTER for the chips
>     > being polled.
>     > 2. Don't use a DS2409
>     > 3. Make sure your script doesn't have process start-up delays in
>     the loop.
>     >
>     > What language are you planning to ue?
>     >
>     > Paul Alfille
>     >
>     > On Feb 19, 2008 2:12 AM, Chris Maresca
>     >
>     >     Why is it that you think a PC couldn't handle this?  I've
>     built CNC
>     >     machines with tolerances in the thousandths of an inch using
>     real-time
>     >     Linux, talking to a 1wire bus is trivial by comparison....
>     >
>     >
>     >
>     ------------------------------------------------------------------------
>     >
>     >
>     -------------------------------------------------------------------------
>     > This SF.net email is sponsored by: Microsoft
>     > Defy all challenges. Microsoft(R) Visual Studio 2008.
>     > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>     >
>     ------------------------------------------------------------------------
>     >
>     > _______________________________________________
>     > Owfs-developers mailing list
>     > Owfs-developers@lists.sourceforge.net
>     <mailto:Owfs-developers@lists.sourceforge.net>
>     > https://lists.sourceforge.net/lists/listinfo/owfs-developers
>     >
>
>     -------------------------------------------------------------------------
>     This SF.net email is sponsored by: Microsoft
>     Defy all challenges. Microsoft(R) Visual Studio 2008.
>     http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>     _______________________________________________
>     Owfs-developers mailing list
>     Owfs-developers@lists.sourceforge.net
>     <mailto:Owfs-developers@lists.sourceforge.net>
>     https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>   

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to