From: Pascal B. <pas...@gm...> - 2009-02-19 00:04:23
Attachments:
problem-bus-bus.log
|
Humm, sorry for reporting so actively... everything is fine when starting owhttpd directly on the physical interface. However, when I work via owserver like this: owserver --i2c=/dev/i2c-0:ALL -p 40666 --error_level 9 --foreground owhttpd -s piccolo:40666 -p 81 I can see and control all connected 1w chips discovered as long as I access them from the root level. To access a particular bus, I have to select bus.0 who correspond to the server, then bus.n ... Then I see the 1w chips connected on bus.0/bus.n, perfectly. But if I go down to the chip level to read/control the chips: every properties are "Error: No such file or directory" The log show the trace when refreshing bus.0/bus.3/28.D1729B010000 when accessing via owdir/owread, everything is ok and there is no bus.0 level before physical buses. Pascal |
From: Paul A. <pau...@gm...> - 2009-02-19 03:29:21
|
On Wed, Feb 18, 2009 at 5:51 PM, Pascal Baerten <pas...@gm...>wrote: > Humm, sorry for reporting so actively... > Please don't stop. > > everything is fine when starting owhttpd directly on the physical > interface. > However, when I work via owserver like this: > > owserver --i2c=/dev/i2c-0:ALL -p 40666 --error_level 9 --foreground > owhttpd -s piccolo:40666 -p 81 > > I can see and control all connected 1w chips discovered as long as I > access them from the root level. > > To access a particular bus, I have to select bus.0 who correspond to > the server, then bus.n ... > Then I see the 1w chips connected on bus.0/bus.n, perfectly. > > But if I go down to the chip level to read/control the chips: every > properties are "Error: No such file or directory" > > The log show the trace when refreshing bus.0/bus.3/28.D1729B010000 > Seems to be a problem with owhttpd. I'll take a fresh look tomorrow. > > > when accessing via owdir/owread, everything is ok and there is no > bus.0 level before physical buses. > > > Pascal > |