Devices not listing

Re: Devices not listing

Definitely NOT a feature.

Help us figure it out.
You have all the sensors on the same bus? Is is always the same two sensors 
that appear?

What version are you using? The latest from the CVS or daily builds? Or the 
last package (1.0.1 whatever?)

I just tested out the current version, and a network of 100 DS18S20 devices 
will show up, so it is possible.

Are your devices powered or parasitic?

(I'm just casting about to figure this out).

Paul

On Sunday 02 January 2005 08:06 am, Christoffer Nordström wrote:
> Hello,
>
> Seems to be a great app, I’ve been using digitemp in my solutions for
> some time now, but this seems to be a much better system.
>
> Unfortuantely I can’t seem to get it working as I’m expecting. At the
> moment I have about 8 x DS18s20 sensors on the line, but the system will
> only list 2 of them. The weird thing about this is the problem is on 2
> totally different systems, and is both with OWFS and OWHTTPD. So I
> thought it might just be a feature =), but I can’t seem to find anything
> on this.
>
> The other sensors still work fine (I think, haven’t been able to confirm
> the returning values yet) getting their addresses from digitemp and then
> just going into their directory works. This however limited the
> functionality I planned, to list all present devices?
>
> The adaptor I use should be a DS9097 clone, and as earlier said it works
> fine with digitemp etc. The only error messages I get is:
> Jan  2 15:15:29 labra OWFS[9167]: Read error on
> /10.A0D849000800/trimblanket (size=1), for all devices when accessing
> them.
>
> If this only is some feature setting i didn’t find i appologice for
> emailing this list with it.
>
> Toffe Norström,

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

RE: Devices not listing

The devices are all on the same bus, and yes it's always the same two
that appear in the listing. Removing one of them will just change the
other one etc,etc. So one at a time all will be recognized, but still
only 2 at once.

The devices are powered from the bus, so just 2 lines are connected.

I'm using the latest CVS. 

One thing is that the adaptor is self-built. So as I can see it, the
problem is either the adaptor or in the system. Weird thing if it's in
the apadtor is thou that all sensors still manually can be read. And if
it matters it worked fine with digitemp.

Only thing commong with both systems I'm testing on is that both have
identical adaptors, and both systems are running some version of
Mandrake linux.

Toffe,

-----Original Message-----
From: owfs-developers-admin <at> lists.sourceforge.net
[mailto:owfs-developers-admin <at> lists.sourceforge.net] On Behalf Of Paul
Alfille
Sent: 2. tammikuuta 2005 13:43
To: owfs-developers <at> lists.sourceforge.net
Subject: Re: [Owfs-developers] Devices not listing

Definitely NOT a feature.

Help us figure it out.
You have all the sensors on the same bus? Is is always the same two
sensors 
that appear?

What version are you using? The latest from the CVS or daily builds? Or
the 
last package (1.0.1 whatever?)

I just tested out the current version, and a network of 100 DS18S20
devices 
will show up, so it is possible.

Are your devices powered or parasitic?

(I'm just casting about to figure this out).

Paul

On Sunday 02 January 2005 08:06 am, Christoffer Nordström wrote:
> Hello,
>
> Seems to be a great app, I’ve been using digitemp in my solutions for
> some time now, but this seems to be a much better system.
>
> Unfortuantely I can’t seem to get it working as I’m expecting. At the
> moment I have about 8 x DS18s20 sensors on the line, but the system
will
> only list 2 of them. The weird thing about this is the problem is on 2
> totally different systems, and is both with OWFS and OWHTTPD. So I
> thought it might just be a feature =), but I can’t seem to find
anything
> on this.
>
> The other sensors still work fine (I think, haven’t been able to
confirm
> the returning values yet) getting their addresses from digitemp and
then
> just going into their directory works. This however limited the
> functionality I planned, to list all present devices?
>
> The adaptor I use should be a DS9097 clone, and as earlier said it
works
> fine with digitemp etc. The only error messages I get is:
> Jan  2 15:15:29 labra OWFS[9167]: Read error on
> /10.A0D849000800/trimblanket (size=1), for all devices when accessing
> them.
>
> If this only is some feature setting i didn’t find i appologice for
> emailing this list with it.
>
> Toffe Norström,

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

Re: Devices not listing

Ahh.. so it's a 9097, not 9097U(2480B based) adapter. We tested that in the 
past on one system, and the basic code design follows digitemp, but I don't 
have access to one of those adapters to test, currently.

Let's go over the details of what is happening, and then construct a test 
version of owfs to figure out the problem.

1. You have only 18s20's on the bus -- 8 of them.
2. Only 2 show in the directory listing.
3. If one is removed, another one is shown, but still only 2.

So the first questions:
1. Which 2? (By number, we can figure out where in the "search" routine we are 
succeeding and failing). Can you list them under digitemp, then under owfs, 
then remove one and list again?
2. If you try to access one of the "mute" devices, i.e:
cat 10.23220022/temperature
(assumiong 10.23220022 exists, but is not being shown) what happens?

We'll figure this out! (And thanks for helping debug, most of the improvements 
have come from these kinds of reports).

Paul

On Sunday 02 January 2005 10:24 am, Christoffer Nordström wrote:
> The devices are all on the same bus, and yes it's always the same two
> that appear in the listing. Removing one of them will just change the
> other one etc,etc. So one at a time all will be recognized, but still
> only 2 at once.
>
> The devices are powered from the bus, so just 2 lines are connected.
>
> I'm using the latest CVS.
>
> One thing is that the adaptor is self-built. So as I can see it, the
> problem is either the adaptor or in the system. Weird thing if it's in
> the apadtor is thou that all sensors still manually can be read. And if
> it matters it worked fine with digitemp.
>
> Only thing commong with both systems I'm testing on is that both have
> identical adaptors, and both systems are running some version of
> Mandrake linux.
>
> Toffe,
>
> -----Original Message-----
> From: owfs-developers-admin <at> lists.sourceforge.net
> [mailto:owfs-developers-admin <at> lists.sourceforge.net] On Behalf Of Paul
> Alfille
> Sent: 2. tammikuuta 2005 13:43
> To: owfs-developers <at> lists.sourceforge.net
> Subject: Re: [Owfs-developers] Devices not listing
>
> Definitely NOT a feature.
>
> Help us figure it out.
> You have all the sensors on the same bus? Is is always the same two
> sensors
> that appear?
>
> What version are you using? The latest from the CVS or daily builds? Or
> the
> last package (1.0.1 whatever?)
>
> I just tested out the current version, and a network of 100 DS18S20
> devices
> will show up, so it is possible.
>
> Are your devices powered or parasitic?
>
> (I'm just casting about to figure this out).
>
> Paul
>
> On Sunday 02 January 2005 08:06 am, Christoffer Nordström wrote:
> > Hello,
> >
> > Seems to be a great app, I’ve been using digitemp in my solutions for
> > some time now, but this seems to be a much better system.
> >
> > Unfortuantely I can’t seem to get it working as I’m expecting. At the
> > moment I have about 8 x DS18s20 sensors on the line, but the system
>
> will
>
> > only list 2 of them. The weird thing about this is the problem is on 2
> > totally different systems, and is both with OWFS and OWHTTPD. So I
> > thought it might just be a feature =), but I can’t seem to find
>
> anything
>
> > on this.
> >
> > The other sensors still work fine (I think, haven’t been able to
>
> confirm
>
> > the returning values yet) getting their addresses from digitemp and
>
> then
>
> > just going into their directory works. This however limited the
> > functionality I planned, to list all present devices?
> >
> > The adaptor I use should be a DS9097 clone, and as earlier said it
>
> works
>
> > fine with digitemp etc. The only error messages I get is:
> > Jan  2 15:15:29 labra OWFS[9167]: Read error on
> > /10.A0D849000800/trimblanket (size=1), for all devices when accessing
> > them.
> >
> > If this only is some feature setting i didn’t find i appologice for
> > emailing this list with it.
> >
> > Toffe Norström,
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

RE: Devices not listing

Sorry for my slow reply.

Ok, so not sure what the adapter can be compared to =), I'll try to dig
the schematics so you'll get the idea.

To answer the questions, first of all number 2:
When trying to manually access any device not listed (goes for both
owhttpd and owfs), it still works just fine. Atleast it gives me values
that seem correct and I don't get any errors.

So no to number 1. I tested it with 4 sensors, connected in different
combinations. The sensors will be in the order that owhttpd presented
them:

All 4 connected:
10.089592000800(AF)
10.A64683000800(47)

Ok, and now the weird thing. Suddently after removing 1 sensors, there's
3 sensors visible!. Not just 2 as earlier. (Still the 8 sensor system I
have on a remote location will only show 2)

ALL BUT 10.A64683000800(47):
10.089592000800(AF)
10.B96D8D000800(A5)
10.AD7F8D000800(DD)

ALL BUT 10.089592000800(AF):
10.A64683000800(47)
10.B96D8D000800(A5)
10.AD7F8D000800(DD)

So (after some more testing) the order seems always to be (btw, digitemp
shows the same):
10.089592000800(AF)
10.A64683000800(47)
10.B96D8D000800(A5)
10.AD7F8D000800(DD)

Hope this helps some. I still have the possibility to test more
simultaneous sensors, but not this week. So please get back to me if
there's more testing I can do.

-----Original Message-----
From: owfs-developers-admin <at> lists.sourceforge.net
[mailto:owfs-developers-admin <at> lists.sourceforge.net] On Behalf Of Paul
Alfille
Sent: 2. tammikuuta 2005 20:56
To: owfs-developers <at> lists.sourceforge.net
Subject: Re: [Owfs-developers] Devices not listing

Ahh.. so it's a 9097, not 9097U(2480B based) adapter. We tested that in
the 
past on one system, and the basic code design follows digitemp, but I
don't 
have access to one of those adapters to test, currently.

Let's go over the details of what is happening, and then construct a
test 
version of owfs to figure out the problem.

1. You have only 18s20's on the bus -- 8 of them.
2. Only 2 show in the directory listing.
3. If one is removed, another one is shown, but still only 2.

So the first questions:
1. Which 2? (By number, we can figure out where in the "search" routine
we are 
succeeding and failing). Can you list them under digitemp, then under
owfs, 
then remove one and list again?
2. If you try to access one of the "mute" devices, i.e:
cat 10.23220022/temperature
(assumiong 10.23220022 exists, but is not being shown) what happens?

We'll figure this out! (And thanks for helping debug, most of the
improvements 
have come from these kinds of reports).

Paul

On Sunday 02 January 2005 10:24 am, Christoffer Nordström wrote:
> The devices are all on the same bus, and yes it's always the same two
> that appear in the listing. Removing one of them will just change the
> other one etc,etc. So one at a time all will be recognized, but still
> only 2 at once.
>
> The devices are powered from the bus, so just 2 lines are connected.
>
> I'm using the latest CVS.
>
> One thing is that the adaptor is self-built. So as I can see it, the
> problem is either the adaptor or in the system. Weird thing if it's in
> the apadtor is thou that all sensors still manually can be read. And
if
> it matters it worked fine with digitemp.
>
> Only thing commong with both systems I'm testing on is that both have
> identical adaptors, and both systems are running some version of
> Mandrake linux.
>
> Toffe,
>
> -----Original Message-----
> From: owfs-developers-admin <at> lists.sourceforge.net
> [mailto:owfs-developers-admin <at> lists.sourceforge.net] On Behalf Of Paul
> Alfille
> Sent: 2. tammikuuta 2005 13:43
> To: owfs-developers <at> lists.sourceforge.net
> Subject: Re: [Owfs-developers] Devices not listing
>
> Definitely NOT a feature.
>
> Help us figure it out.
> You have all the sensors on the same bus? Is is always the same two
> sensors
> that appear?
>
> What version are you using? The latest from the CVS or daily builds?
Or
> the
> last package (1.0.1 whatever?)
>
> I just tested out the current version, and a network of 100 DS18S20
> devices
> will show up, so it is possible.
>
> Are your devices powered or parasitic?
>
> (I'm just casting about to figure this out).
>
> Paul
>
> On Sunday 02 January 2005 08:06 am, Christoffer Nordström wrote:
> > Hello,
> >
> > Seems to be a great app, I’ve been using digitemp in my solutions
for
> > some time now, but this seems to be a much better system.
> >
> > Unfortuantely I can’t seem to get it working as I’m expecting. At
the
> > moment I have about 8 x DS18s20 sensors on the line, but the system
>
> will
>
> > only list 2 of them. The weird thing about this is the problem is on
2
> > totally different systems, and is both with OWFS and OWHTTPD. So I
> > thought it might just be a feature =), but I can’t seem to find
>
> anything
>
> > on this.
> >
> > The other sensors still work fine (I think, haven’t been able to
>
> confirm
>
> > the returning values yet) getting their addresses from digitemp and
>
> then
>
> > just going into their directory works. This however limited the
> > functionality I planned, to list all present devices?
> >
> > The adaptor I use should be a DS9097 clone, and as earlier said it
>
> works
>
> > fine with digitemp etc. The only error messages I get is:
> > Jan  2 15:15:29 labra OWFS[9167]: Read error on
> > /10.A0D849000800/trimblanket (size=1), for all devices when
accessing
> > them.
> >
> > If this only is some feature setting i didn’t find i appologice for
> > emailing this list with it.
> >
> > Toffe Norström,
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

Re: Devices not listing

Ok, then this is a directory search problem.
The order is increasing numeric, when viewed back-to-front (1-wire internally 
represents everything low bit first).

Paul

On Wednesday 05 January 2005 11:39 am, Christoffer Nordström wrote:
> Sorry for my slow reply.
>
> Ok, so not sure what the adapter can be compared to =), I'll try to dig
> the schematics so you'll get the idea.
>
> To answer the questions, first of all number 2:
> When trying to manually access any device not listed (goes for both
> owhttpd and owfs), it still works just fine. Atleast it gives me values
> that seem correct and I don't get any errors.
>
> So no to number 1. I tested it with 4 sensors, connected in different
> combinations. The sensors will be in the order that owhttpd presented
> them:
>
> All 4 connected:
> 10.089592000800(AF)
> 10.A64683000800(47)
>
> Ok, and now the weird thing. Suddently after removing 1 sensors, there's
> 3 sensors visible!. Not just 2 as earlier. (Still the 8 sensor system I
> have on a remote location will only show 2)
>
> ALL BUT 10.A64683000800(47):
> 10.089592000800(AF)
> 10.B96D8D000800(A5)
> 10.AD7F8D000800(DD)
>
> ALL BUT 10.089592000800(AF):
> 10.A64683000800(47)
> 10.B96D8D000800(A5)
> 10.AD7F8D000800(DD)
>
> So (after some more testing) the order seems always to be (btw, digitemp
> shows the same):
> 10.089592000800(AF)
> 10.A64683000800(47)
> 10.B96D8D000800(A5)
> 10.AD7F8D000800(DD)
>
>
> Hope this helps some. I still have the possibility to test more
> simultaneous sensors, but not this week. So please get back to me if
> there's more testing I can do.
>
>
> -----Original Message-----
> From: owfs-developers-admin <at> lists.sourceforge.net
> [mailto:owfs-developers-admin <at> lists.sourceforge.net] On Behalf Of Paul
> Alfille
> Sent: 2. tammikuuta 2005 20:56
> To: owfs-developers <at> lists.sourceforge.net
> Subject: Re: [Owfs-developers] Devices not listing
>
> Ahh.. so it's a 9097, not 9097U(2480B based) adapter. We tested that in
> the
> past on one system, and the basic code design follows digitemp, but I
> don't
> have access to one of those adapters to test, currently.
>
> Let's go over the details of what is happening, and then construct a
> test
> version of owfs to figure out the problem.
>
> 1. You have only 18s20's on the bus -- 8 of them.
> 2. Only 2 show in the directory listing.
> 3. If one is removed, another one is shown, but still only 2.
>
> So the first questions:
> 1. Which 2? (By number, we can figure out where in the "search" routine
> we are
> succeeding and failing). Can you list them under digitemp, then under
> owfs,
> then remove one and list again?
> 2. If you try to access one of the "mute" devices, i.e:
> cat 10.23220022/temperature
> (assumiong 10.23220022 exists, but is not being shown) what happens?
>
> We'll figure this out! (And thanks for helping debug, most of the
> improvements
> have come from these kinds of reports).
>
> Paul
>
> On Sunday 02 January 2005 10:24 am, Christoffer Nordström wrote:
> > The devices are all on the same bus, and yes it's always the same two
> > that appear in the listing. Removing one of them will just change the
> > other one etc,etc. So one at a time all will be recognized, but still
> > only 2 at once.
> >
> > The devices are powered from the bus, so just 2 lines are connected.
> >
> > I'm using the latest CVS.
> >
> > One thing is that the adaptor is self-built. So as I can see it, the
> > problem is either the adaptor or in the system. Weird thing if it's in
> > the apadtor is thou that all sensors still manually can be read. And
>
> if
>
> > it matters it worked fine with digitemp.
> >
> > Only thing commong with both systems I'm testing on is that both have
> > identical adaptors, and both systems are running some version of
> > Mandrake linux.
> >
> > Toffe,
> >
> > -----Original Message-----
> > From: owfs-developers-admin <at> lists.sourceforge.net
> > [mailto:owfs-developers-admin <at> lists.sourceforge.net] On Behalf Of Paul
> > Alfille
> > Sent: 2. tammikuuta 2005 13:43
> > To: owfs-developers <at> lists.sourceforge.net
> > Subject: Re: [Owfs-developers] Devices not listing
> >
> > Definitely NOT a feature.
> >
> > Help us figure it out.
> > You have all the sensors on the same bus? Is is always the same two
> > sensors
> > that appear?
> >
> > What version are you using? The latest from the CVS or daily builds?
>
> Or
>
> > the
> > last package (1.0.1 whatever?)
> >
> > I just tested out the current version, and a network of 100 DS18S20
> > devices
> > will show up, so it is possible.
> >
> > Are your devices powered or parasitic?
> >
> > (I'm just casting about to figure this out).
> >
> > Paul
> >
> > On Sunday 02 January 2005 08:06 am, Christoffer Nordström wrote:
> > > Hello,
> > >
> > > Seems to be a great app, I’ve been using digitemp in my solutions
>
> for
>
> > > some time now, but this seems to be a much better system.
> > >
> > > Unfortuantely I can’t seem to get it working as I’m expecting. At
>
> the
>
> > > moment I have about 8 x DS18s20 sensors on the line, but the system
> >
> > will
> >
> > > only list 2 of them. The weird thing about this is the problem is on
>
> 2
>
> > > totally different systems, and is both with OWFS and OWHTTPD. So I
> > > thought it might just be a feature =), but I can’t seem to find
> >
> > anything
> >
> > > on this.
> > >
> > > The other sensors still work fine (I think, haven’t been able to
> >
> > confirm
> >
> > > the returning values yet) getting their addresses from digitemp and
> >
> > then
> >
> > > just going into their directory works. This however limited the
> > > functionality I planned, to list all present devices?
> > >
> > > The adaptor I use should be a DS9097 clone, and as earlier said it
> >
> > works
> >
> > > fine with digitemp etc. The only error messages I get is:
> > > Jan  2 15:15:29 labra OWFS[9167]: Read error on
> > > /10.A0D849000800/trimblanket (size=1), for all devices when
>
> accessing
>
> > > them.
> > >
> > > If this only is some feature setting i didn’t find i appologice for
> > > emailing this list with it.
> > >
> > > Toffe Norström,
> >
> > -------------------------------------------------------
> > The SF.Net email is sponsored by: Beat the post-holiday blues
> > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> > _______________________________________________
> > Owfs-developers mailing list
> > Owfs-developers <at> lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/owfs-developers
> >
> >
> >
> >
> > -------------------------------------------------------
> > The SF.Net email is sponsored by: Beat the post-holiday blues
> > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> > _______________________________________________
> > Owfs-developers mailing list
> > Owfs-developers <at> lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

Re: Devices not listing

The code looks pretty good. I wonder if this is a timing issue with your 
adapter. Can you try the current CVS code. I extended the zero period, at the 
expense of device power.

Paul

On Wednesday 05 January 2005 11:39 am, Christoffer Nordström wrote:
> Sorry for my slow reply.
>
> Ok, so not sure what the adapter can be compared to =), I'll try to dig
> the schematics so you'll get the idea.
>
> To answer the questions, first of all number 2:
> When trying to manually access any device not listed (goes for both
> owhttpd and owfs), it still works just fine. Atleast it gives me values
> that seem correct and I don't get any errors.
>
> So no to number 1. I tested it with 4 sensors, connected in different
> combinations. The sensors will be in the order that owhttpd presented
> them:
>
> All 4 connected:
> 10.089592000800(AF)
> 10.A64683000800(47)
>
> Ok, and now the weird thing. Suddently after removing 1 sensors, there's
> 3 sensors visible!. Not just 2 as earlier. (Still the 8 sensor system I
> have on a remote location will only show 2)
>
> ALL BUT 10.A64683000800(47):
> 10.089592000800(AF)
> 10.B96D8D000800(A5)
> 10.AD7F8D000800(DD)
>
> ALL BUT 10.089592000800(AF):
> 10.A64683000800(47)
> 10.B96D8D000800(A5)
> 10.AD7F8D000800(DD)
>
> So (after some more testing) the order seems always to be (btw, digitemp
> shows the same):
> 10.089592000800(AF)
> 10.A64683000800(47)
> 10.B96D8D000800(A5)
> 10.AD7F8D000800(DD)
>
>
> Hope this helps some. I still have the possibility to test more
> simultaneous sensors, but not this week. So please get back to me if
> there's more testing I can do.
>
>
> -----Original Message-----
> From: owfs-developers-admin <at> lists.sourceforge.net
> [mailto:owfs-developers-admin <at> lists.sourceforge.net] On Behalf Of Paul
> Alfille
> Sent: 2. tammikuuta 2005 20:56
> To: owfs-developers <at> lists.sourceforge.net
> Subject: Re: [Owfs-developers] Devices not listing
>
> Ahh.. so it's a 9097, not 9097U(2480B based) adapter. We tested that in
> the
> past on one system, and the basic code design follows digitemp, but I
> don't
> have access to one of those adapters to test, currently.
>
> Let's go over the details of what is happening, and then construct a
> test
> version of owfs to figure out the problem.
>
> 1. You have only 18s20's on the bus -- 8 of them.
> 2. Only 2 show in the directory listing.
> 3. If one is removed, another one is shown, but still only 2.
>
> So the first questions:
> 1. Which 2? (By number, we can figure out where in the "search" routine
> we are
> succeeding and failing). Can you list them under digitemp, then under
> owfs,
> then remove one and list again?
> 2. If you try to access one of the "mute" devices, i.e:
> cat 10.23220022/temperature
> (assumiong 10.23220022 exists, but is not being shown) what happens?
>
> We'll figure this out! (And thanks for helping debug, most of the
> improvements
> have come from these kinds of reports).
>
> Paul
>
> On Sunday 02 January 2005 10:24 am, Christoffer Nordström wrote:
> > The devices are all on the same bus, and yes it's always the same two
> > that appear in the listing. Removing one of them will just change the
> > other one etc,etc. So one at a time all will be recognized, but still
> > only 2 at once.
> >
> > The devices are powered from the bus, so just 2 lines are connected.
> >
> > I'm using the latest CVS.
> >
> > One thing is that the adaptor is self-built. So as I can see it, the
> > problem is either the adaptor or in the system. Weird thing if it's in
> > the apadtor is thou that all sensors still manually can be read. And
>
> if
>
> > it matters it worked fine with digitemp.
> >
> > Only thing commong with both systems I'm testing on is that both have
> > identical adaptors, and both systems are running some version of
> > Mandrake linux.
> >
> > Toffe,
> >
> > -----Original Message-----
> > From: owfs-developers-admin <at> lists.sourceforge.net
> > [mailto:owfs-developers-admin <at> lists.sourceforge.net] On Behalf Of Paul
> > Alfille
> > Sent: 2. tammikuuta 2005 13:43
> > To: owfs-developers <at> lists.sourceforge.net
> > Subject: Re: [Owfs-developers] Devices not listing
> >
> > Definitely NOT a feature.
> >
> > Help us figure it out.
> > You have all the sensors on the same bus? Is is always the same two
> > sensors
> > that appear?
> >
> > What version are you using? The latest from the CVS or daily builds?
>
> Or
>
> > the
> > last package (1.0.1 whatever?)
> >
> > I just tested out the current version, and a network of 100 DS18S20
> > devices
> > will show up, so it is possible.
> >
> > Are your devices powered or parasitic?
> >
> > (I'm just casting about to figure this out).
> >
> > Paul
> >
> > On Sunday 02 January 2005 08:06 am, Christoffer Nordström wrote:
> > > Hello,
> > >
> > > Seems to be a great app, I’ve been using digitemp in my solutions
>
> for
>
> > > some time now, but this seems to be a much better system.
> > >
> > > Unfortuantely I can’t seem to get it working as I’m expecting. At
>
> the
>
> > > moment I have about 8 x DS18s20 sensors on the line, but the system
> >
> > will
> >
> > > only list 2 of them. The weird thing about this is the problem is on
>
> 2
>
> > > totally different systems, and is both with OWFS and OWHTTPD. So I
> > > thought it might just be a feature =), but I can’t seem to find
> >
> > anything
> >
> > > on this.
> > >
> > > The other sensors still work fine (I think, haven’t been able to
> >
> > confirm
> >
> > > the returning values yet) getting their addresses from digitemp and
> >
> > then
> >
> > > just going into their directory works. This however limited the
> > > functionality I planned, to list all present devices?
> > >
> > > The adaptor I use should be a DS9097 clone, and as earlier said it
> >
> > works
> >
> > > fine with digitemp etc. The only error messages I get is:
> > > Jan  2 15:15:29 labra OWFS[9167]: Read error on
> > > /10.A0D849000800/trimblanket (size=1), for all devices when
>
> accessing
>
> > > them.
> > >
> > > If this only is some feature setting i didn’t find i appologice for
> > > emailing this list with it.
> > >
> > > Toffe Norström,
> >
> > -------------------------------------------------------
> > The SF.Net email is sponsored by: Beat the post-holiday blues
> > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> > _______________________________________________
> > Owfs-developers mailing list
> > Owfs-developers <at> lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/owfs-developers
> >
> >
> >
> >
> > -------------------------------------------------------
> > The SF.Net email is sponsored by: Beat the post-holiday blues
> > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> > _______________________________________________
> > Owfs-developers mailing list
> > Owfs-developers <at> lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

Re: Some updates to the web-site

On Wednesday 05 January 2005 08:31 am, you wrote:
> I made some changes to the web-site WRT54G.html and progress.html.
> The latest binaries are also uploaded to the web-site.

Great! I've updated ow-website with the changes as well.

>
> I had to patch FS_r_blanket in ow_1820.c since it always
> return -EINVAL for me and the working thread in owhttpd hangs forever
> when I visit the page:
> http://192.168.1.1:3001/1F.CCF201000000/main/28.8EE05E000000/
>
> It's not a big deal in owfs, since it returns at least:
> / # cat /tmp/var/1wire/1F.CCF201000000/main/28.8EE05E000000/trimvalid
> 1
> / # cat /tmp/var/1wire/1F.CCF201000000/main/28.8EE05E000000/trimblanket
> cat: Read error: Invalid argument
>
> I know we talked about this some time ago, but I don't remember what
> OW_die() was used for.... was it old DS18B20 that didn't work correctly?
OW_die gives the manufacturing die number. This was information released by 
Dallas after manufacturing problems surfaced. trimblanket, trim etc are all 
there for software work-around of this hardware issue. See the man page.
>
> The patch is not correct in any way... I just wanted to remove the
> possibility to return -EINVAL right now, and wait for your advice.
> I guess owhttpd should be able to handle EINVAL and not hang, so some
> patch should perhaps be applied to owhttpd instead.
I'm not sure why owhttpd would hang, but the error is now handled explicitly. 
Can you retest?

Paul
>

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

RE: Devices not listing

Hello, and thanks for all help so far, I tested the newest CVS without
any success on either of my testsystems. It may well be that this is
related to the adapter I have, in which case it may be unnecessary to
make any hacks for it? Althou it's a quite common make-it-yourself
schematic I think.

I'm trying to get some real Dallas made adaptors and hope this will fix
the problem.

However if you seem this is a problem that needs to get fixed, I'll
ofcourse help anyway I can, but rather than someone is working their ass
off on my behalf, I'll buy a real adapter =)

Toffe,

-----Original Message-----
From: owfs-developers-admin <at> lists.sourceforge.net
[mailto:owfs-developers-admin <at> lists.sourceforge.net] On Behalf Of Paul
Alfille
Sent: 6. tammikuuta 2005 2:40
To: owfs-developers <at> lists.sourceforge.net
Subject: Re: [Owfs-developers] Devices not listing

The code looks pretty good. I wonder if this is a timing issue with your

adapter. Can you try the current CVS code. I extended the zero period,
at the 
expense of device power.

Paul

On Wednesday 05 January 2005 11:39 am, Christoffer Nordström wrote:
> Sorry for my slow reply.
>
> Ok, so not sure what the adapter can be compared to =), I'll try to
dig
> the schematics so you'll get the idea.
>
> To answer the questions, first of all number 2:
> When trying to manually access any device not listed (goes for both
> owhttpd and owfs), it still works just fine. Atleast it gives me
values
> that seem correct and I don't get any errors.
>
> So no to number 1. I tested it with 4 sensors, connected in different
> combinations. The sensors will be in the order that owhttpd presented
> them:
>
> All 4 connected:
> 10.089592000800(AF)
> 10.A64683000800(47)
>
> Ok, and now the weird thing. Suddently after removing 1 sensors,
there's
> 3 sensors visible!. Not just 2 as earlier. (Still the 8 sensor system
I
> have on a remote location will only show 2)
>
> ALL BUT 10.A64683000800(47):
> 10.089592000800(AF)
> 10.B96D8D000800(A5)
> 10.AD7F8D000800(DD)
>
> ALL BUT 10.089592000800(AF):
> 10.A64683000800(47)
> 10.B96D8D000800(A5)
> 10.AD7F8D000800(DD)
>
> So (after some more testing) the order seems always to be (btw,
digitemp
> shows the same):
> 10.089592000800(AF)
> 10.A64683000800(47)
> 10.B96D8D000800(A5)
> 10.AD7F8D000800(DD)
>
>
> Hope this helps some. I still have the possibility to test more
> simultaneous sensors, but not this week. So please get back to me if
> there's more testing I can do.
>
>
> -----Original Message-----
> From: owfs-developers-admin <at> lists.sourceforge.net
> [mailto:owfs-developers-admin <at> lists.sourceforge.net] On Behalf Of Paul
> Alfille
> Sent: 2. tammikuuta 2005 20:56
> To: owfs-developers <at> lists.sourceforge.net
> Subject: Re: [Owfs-developers] Devices not listing
>
> Ahh.. so it's a 9097, not 9097U(2480B based) adapter. We tested that
in
> the
> past on one system, and the basic code design follows digitemp, but I
> don't
> have access to one of those adapters to test, currently.
>
> Let's go over the details of what is happening, and then construct a
> test
> version of owfs to figure out the problem.
>
> 1. You have only 18s20's on the bus -- 8 of them.
> 2. Only 2 show in the directory listing.
> 3. If one is removed, another one is shown, but still only 2.
>
> So the first questions:
> 1. Which 2? (By number, we can figure out where in the "search"
routine
> we are
> succeeding and failing). Can you list them under digitemp, then under
> owfs,
> then remove one and list again?
> 2. If you try to access one of the "mute" devices, i.e:
> cat 10.23220022/temperature
> (assumiong 10.23220022 exists, but is not being shown) what happens?
>
> We'll figure this out! (And thanks for helping debug, most of the
> improvements
> have come from these kinds of reports).
>
> Paul
>
> On Sunday 02 January 2005 10:24 am, Christoffer Nordström wrote:
> > The devices are all on the same bus, and yes it's always the same
two
> > that appear in the listing. Removing one of them will just change
the
> > other one etc,etc. So one at a time all will be recognized, but
still
> > only 2 at once.
> >
> > The devices are powered from the bus, so just 2 lines are connected.
> >
> > I'm using the latest CVS.
> >
> > One thing is that the adaptor is self-built. So as I can see it, the
> > problem is either the adaptor or in the system. Weird thing if it's
in
> > the apadtor is thou that all sensors still manually can be read. And
>
> if
>
> > it matters it worked fine with digitemp.
> >
> > Only thing commong with both systems I'm testing on is that both
have
> > identical adaptors, and both systems are running some version of
> > Mandrake linux.
> >
> > Toffe,
> >
> > -----Original Message-----
> > From: owfs-developers-admin <at> lists.sourceforge.net
> > [mailto:owfs-developers-admin <at> lists.sourceforge.net] On Behalf Of
Paul
> > Alfille
> > Sent: 2. tammikuuta 2005 13:43
> > To: owfs-developers <at> lists.sourceforge.net
> > Subject: Re: [Owfs-developers] Devices not listing
> >
> > Definitely NOT a feature.
> >
> > Help us figure it out.
> > You have all the sensors on the same bus? Is is always the same two
> > sensors
> > that appear?
> >
> > What version are you using? The latest from the CVS or daily builds?
>
> Or
>
> > the
> > last package (1.0.1 whatever?)
> >
> > I just tested out the current version, and a network of 100 DS18S20
> > devices
> > will show up, so it is possible.
> >
> > Are your devices powered or parasitic?
> >
> > (I'm just casting about to figure this out).
> >
> > Paul
> >
> > On Sunday 02 January 2005 08:06 am, Christoffer Nordström wrote:
> > > Hello,
> > >
> > > Seems to be a great app, I’ve been using digitemp in my solutions
>
> for
>
> > > some time now, but this seems to be a much better system.
> > >
> > > Unfortuantely I can’t seem to get it working as I’m expecting. At
>
> the
>
> > > moment I have about 8 x DS18s20 sensors on the line, but the
system
> >
> > will
> >
> > > only list 2 of them. The weird thing about this is the problem is
on
>
> 2
>
> > > totally different systems, and is both with OWFS and OWHTTPD. So I
> > > thought it might just be a feature =), but I can’t seem to find
> >
> > anything
> >
> > > on this.
> > >
> > > The other sensors still work fine (I think, haven’t been able to
> >
> > confirm
> >
> > > the returning values yet) getting their addresses from digitemp
and
> >
> > then
> >
> > > just going into their directory works. This however limited the
> > > functionality I planned, to list all present devices?
> > >
> > > The adaptor I use should be a DS9097 clone, and as earlier said it
> >
> > works
> >
> > > fine with digitemp etc. The only error messages I get is:
> > > Jan  2 15:15:29 labra OWFS[9167]: Read error on
> > > /10.A0D849000800/trimblanket (size=1), for all devices when
>
> accessing
>
> > > them.
> > >
> > > If this only is some feature setting i didn’t find i appologice
for
> > > emailing this list with it.
> > >
> > > Toffe Norström,
> >
> > -------------------------------------------------------
> > The SF.Net email is sponsored by: Beat the post-holiday blues
> > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> > It's fun and FREE -- well,
almost....http://www.thinkgeek.com/sfshirt
> > _______________________________________________
> > Owfs-developers mailing list
> > Owfs-developers <at> lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/owfs-developers
> >
> >
> >
> >
> > -------------------------------------------------------
> > The SF.Net email is sponsored by: Beat the post-holiday blues
> > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> > It's fun and FREE -- well,
almost....http://www.thinkgeek.com/sfshirt
> > _______________________________________________
> > Owfs-developers mailing list
> > Owfs-developers <at> lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

Re: Re: Some updates to the web-site

Hi Paul

I found a bug in uClibc-0.9.19 which WRT54G use. syslog() may hang if
syslogd isn't available since it can't open a socket to it, and a
dead-lock occur. That what's happened for me when ow_read.c tried to
write to the syslog about the trimblanket problem.
If syslogd is available and started it isn't a problem, but since
I upload only owhttpd to the router and start it, I didn't see
any other solution than to remove all syslog/openlog/closelog calls
for WRT54G.

The problem doesn't exist for me with uClibc-0.9.26 which I have
on the Coldfire board.

Look at the changes in owfs/module/owlib/src/include/ow.h and
owhttpd.c which I checked in. I had to add 
#include <sys/uio.h>
#include <sys/socket.h>
too just to be able to compile the latest changes you have made...
Is it ok for you?

/Christian

On Thu, 2005-01-06 at 02:56, Paul Alfille wrote:
> On Wednesday 05 January 2005 08:31 am, you wrote:
> > I made some changes to the web-site WRT54G.html and progress.html.
> > The latest binaries are also uploaded to the web-site.
> 
> Great! I've updated ow-website with the changes as well.
> 
> >
> > I had to patch FS_r_blanket in ow_1820.c since it always
> > return -EINVAL for me and the working thread in owhttpd hangs forever
> > when I visit the page:
> > http://192.168.1.1:3001/1F.CCF201000000/main/28.8EE05E000000/
> >
> > It's not a big deal in owfs, since it returns at least:
> > / # cat /tmp/var/1wire/1F.CCF201000000/main/28.8EE05E000000/trimvalid
> > 1
> > / # cat /tmp/var/1wire/1F.CCF201000000/main/28.8EE05E000000/trimblanket
> > cat: Read error: Invalid argument
> >
> > I know we talked about this some time ago, but I don't remember what
> > OW_die() was used for.... was it old DS18B20 that didn't work correctly?
> OW_die gives the manufacturing die number. This was information released by 
> Dallas after manufacturing problems surfaced. trimblanket, trim etc are all 
> there for software work-around of this hardware issue. See the man page.
> >
> > The patch is not correct in any way... I just wanted to remove the
> > possibility to return -EINVAL right now, and wait for your advice.
> > I guess owhttpd should be able to handle EINVAL and not hang, so some
> > patch should perhaps be applied to owhttpd instead.
> I'm not sure why owhttpd would hang, but the error is now handled explicitly. 
> Can you retest?
> 
> Paul
> >
> 

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt