PING packets are sent if the server takes longer than 1 second or so.
There are two interpretations of the delay:
1. The server is busy
2. The server died (or the connection went down).
Since it's not possible to know how long the processing will take, the
owserver sends a PING message if the dat
On 8/23/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
> On 8/23/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
> > > Try OWTAP to inspect.
> > >
> > > There is an extensive writeup in the web site.
> > > http://www.owfs.org/index.php?page=owtap
> > >
> > > It looks like the second message is a P
On 8/23/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
> > Try OWTAP to inspect.
> >
> > There is an extensive writeup in the web site.
> > http://www.owfs.org/index.php?page=owtap
> >
> > It looks like the second message is a PING message, payload = -1
>
> I'm gonna try this. Thanks.
I've tried
On 8/23/07, Alfille, Paul H.,M.D. <[EMAIL PROTECTED]> wrote:
> In short, the first 24 bytes are a header that include information like error
> status, message type, version, data length, data format (temperature scale,
> etc)
Yeah, the header, this I get. What I meant was that in the uncached
rea
message is a PING message, payload = -1
Paul Alfille
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Pedro
Côrte-Real
Sent: Wednesday, August 22, 2007 7:32 PM
To: [email protected]
Subject: Re: [Owfs-developers] Strange read from owserver
On 8/12/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
> I'm not sure. owread outputs the right thing but so does my ruby code
> if I do a puts to a terminal since printf ignores those characters.
> I'll have to strace owread.
I've straced owread and it's reading 24 extra bytes in the uncached ca
On 8/12/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
>
>
> When would owserver need loop suppression? I understand that owlib has
> the functionality that's why owserver seems complicated for something
> that only has to answer three commands.
>
> I'm always open to suggestions and simplificatio
On 8/12/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
>
> On 8/12/07, Paul Alfille <[EMAIL PROTECTED]> wrote:
> When would owserver need loop suppression? I understand that owlib has
> the functionality that's why owserver seems complicated for something
> that only has to answer three commands.
Hi,
Pedro Côrte-Real:
> I'm truncating using the length I assumed the offset didn't actually
> do anything. My Ruby code is translated from the python one and that
> one didn't do anything with it.
That may be because the Python code is not actually written well. :-/
Apart from the non-handling
On 8/12/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
>
> > > there's an offset there but it doesn't seem to be used anywhere.
> >
> > That's for reading "large" memory blocks in parts. Ignore it (set it to
> zero
> > and ignore result)
> > Actually offset is used for some directory flags on retu
On 8/12/07, Paul Alfille <[EMAIL PROTECTED]> wrote:
> I presume that when you try one of the other programs (owread, for example)
> you get the data you expect?
> I.e. the question is about the ruby code, not the sensor?
I'm not sure. owread outputs the right thing but so does my ruby code
if I do
On 8/12/07, Matthias Urlichs <[EMAIL PROTECTED]> wrote:
> * check that you're actually using the offset+payload_length fields
> instead of blindly using the whole data portion of the message ;-)
I'm truncating using the length I assumed the offset didn't actually
do anything. My Ruby code is tra
On 8/11/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
>
> I'm trying to read the presure from a sensor using owserver. I'm
> reading this from:
>
> /12.CC883400/TAI8570/pressure
>
> And I get something like:
>
> " 994.431"
>
> when it's reading from the cache. But when I use uncached or t
Hi,
Pedro Côrte-Real:
> > The owfs header looks something around this.
>
> It can't really be that because it only happens when reading uncached
> and the code does one 24 byte read for the header and then another for
> the payload with the size given in the header.
I've never seen this. Things
On 8/12/07, Chris Malton <[EMAIL PROTECTED]> wrote:
> You may be seeing the Ruby Binding printing out the protocol header.
>
> The owfs header looks something around this.
It can't really be that because it only happens when reading uncached
and the code does one 24 byte read for the header and th
You may be seeing the Ruby Binding printing out the protocol header.
The owfs header looks something around this.
Chris
Pedro Côrte-Real wrote:
> I'm trying to read the presure from a sensor using owserver. I'm
> reading this from:
>
> /12.CC883400/TAI8570/pressure
>
> And I get something li
I'm trying to read the presure from a sensor using owserver. I'm
reading this from:
/12.CC883400/TAI8570/pressure
And I get something like:
" 994.431"
when it's reading from the cache. But when I use uncached or the
server actually reads from the device I get:
"\000\000\000\000\000\000
17 matches
Mail list logo
