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
problem-bus-bus.log
Description: Binary data
------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H
_______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
