I've run into two problems with owserver (on an NSLU2 with a DS9490R USB adapter). I've been using 2.7p17 and 2.7p21, both have the same problems.
1. Owserver is unable to read all sensors on my Hobby Boards hub, but the sensors are there in the directory listings. E.g.: This sensor is ok: # owget -s 3000 1F.BCFD04000000/aux/28.CE11EC010000D3/temperature 12.75 The directory listing is ok: # owget -s 3000 1F.BCFD04000000/main/26.13FF83000000FB/HIH4000 1F.BCFD04000000/main/26.13FF83000000FB/HIH4000/humidity But I can't read the value: # owget -s 3000 1F.BCFD04000000/main/26.13FF83000000FB/HIH4000/humidity ServerRead: Data error on 1F.BCFD04000000/main/26.13FF83000000FB/HIH4000/humidity Same problem when I use owcapi. Sometimes I don't get the ServerRead error, but owget just sits there never finishing (usually happens after I've run the program described in problem 2 below). It looks like that on a given DS2409 hub, it can only access values either on the main or the aux branch, not both. I thought owserver would do the switching automatically as it does for the directory listings? The hub works fine with Oww. 2. Owserver suddenly dies. This happens frequently (after a few minutes) on the NSLU2. It has also happened on another 1-wire network running on a regular x86_64 pc, but I'm unable to reproduce there. I've written a C program using owcapi, which makes an Oww like log file by accessing several owservers. The idea is get several sources into one log file and one offline source is not to affect logging from the other sources and have owserver to all the low level stuff. It works this way: * Fork off a new process for every owserver. * In the new processes make a thread for every value to be logged which simply reads and store the value at its own pace (typically every 10 seconds). * When it's time to write to the log file, the parent will cancel all the threads, process all data from every thread (average, max, min, whatever to be logged etc) and log to file. It will produce quite a few owserver requests, but hardly more than a few per second and most will be for cached values. Should this cause any problems for owserver? The program causes owserver to fork into many processes (in this setup, about 15), but that shouldn't be a problem. -- Steinar ; NIL DIFFICILE VOLENTI ; http://latinitas.org ; http://voksenlia.net ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers