Paul this maybe better...I used debug for the same counter.B with version
2.5p10 which works OK
unique: 31, opcode: LOOKUP (1), nodeid: 2, insize: 51
LOOKUP /1D.EBEF0900/counters.B
CALL: FSTAT path=/1D.EBEF0900/counters.B
CALL: PARSENAME path=[/1D.EBEF0900/counters.B]
DEBUG:
Paul
Just reloaded 2.5p10 and these are the counter values displayed via owhttpd
Counter A = 8999689
Counter B = 2718957568
- Original Message -
From: Paul Alfille
To: owfs-developers@lists.sourceforge.net
Sent: Sunday, October 07, 2007 12:11 PM
Subject: Re: [Owfs-develope
On 10/6/07, Rob Conway <[EMAIL PROTECTED]> wrote:
>
> Paul,
> I think I got the debug...first time I've really tried downlaoding via CVS
> and debug with owfs...
>
> This is the response when trying to read counters.B
>
>
> --- OneWireQuery done
> DEBUG: Cache_Get 1D EB EF 09 00 00 00 34 size=8
Paul,
I think I got the debug...first time I've really tried downlaoding via CVS and
debug with owfs...
This is the response when trying to read counters.B
--- OneWireQuery done
DEBUG: Cache_Get 1D EB EF 09 00 00 00 34 size=8 IsUncachedDir=0
DEBUG: Get from cache sn 1D EB EF 09 00 00 00 34
Sorry for that response.
Can you try the CVS version? (I don't have a DS2423 to test against).
I'm testing the conjecture that we can't read just the last byte of the page
and the counters.
If you could test with "--error_level=9 --foreground" and post the output?
Paul Alfille
On 10/6/07, Paul
On 10/6/07, Paul Alfille <[EMAIL PROTECTED]> wrote:
> On 10/6/07, Rob Conway <[EMAIL PROTECTED]> wrote:
> >
> > ANy idea's on why 2423 counter parameters do not work on the latest
> > releases. If I have to keep running 2.5p10 was this a stable release ?
> >
>
> Want your money back?
>
Hello!
And
On 10/6/07, Rob Conway <[EMAIL PROTECTED]> wrote:
>
> ANy idea's on why 2423 counter parameters do not work on the latest
> releases. If I have to keep running 2.5p10 was this a stable release ?
>
Want your money back?
-
This
Solved (in the CVS version, and 2.6p8 when released).
You need to start up with --usb_regulartime
It turns out that the USB flexible timing confuses the Swart LCD.
Paul Alfille
On 10/6/07, Paul Alfille <[EMAIL PROTECTED]> wrote:
>
> I see that we use different timing (Flexible speed) currently
