:-) I bought it mainly because it made interfacing with Raspberry Pi easy (don't have to solder something up myself), and it contains a Realtime-watch which is nice to have if NTP is not available. But also I think a failing device or short circuit would not bring down the whole network if the devices are spread on several networks. Mixing devices of different generations and speedmodes(standard/overdrive) or powered/parasitic could also be of concern when running on the same bus, having many busses makes it more reliable when you could run the fast powered devices on one bus and slow parasitic ones on another. That's my belief as a 1-wire noob anyway. :-)
That being said, I agree that's more channels than I need, I currently only use three of them. One for every house I monitor. I have about 20-30 devices or so, mostly DS18S20, DS2408, DS2406, DS2423, and a DS2405. // Henrik Den 2015-12-31 kl. 09:30, skrev Colin Reese: > Can somebody explain to me why on earth people use so many 1wire buses? Do > many use hundreds of devices and need to split them across buses? That thing > has 17 1wire channels. I have never had need for more than 1, even with >100 > sensors. The whole beauty of 1Wire is extendable single bus multi drop! > > Colin > > >> On Dec 31, 2015, at 12:17 AM, Henrik Östman <tryc...@gmail.com> wrote: >> >> Hello! >> >> I have a question, why does some of my 1-wire devices get listed several >> times by OWFS? They have the same ID and inode-number, so now my >> application have to filter out the duplicates. >> I'm running OWSERVER: >> >> owserver version: >> 2.8p15 >> libow version: >> 2.8p15 >> >> On a Raspberry Pi with a AbioWire+ card: >> https://www.m.nu/pdf/AbioWire_Plus_um_en_us_2015_03_02.pdf >> Some of the 1-wire devices are connected to different connectors on the >> AbioWire-card. >> >> When I list the devices with OWFS it look like this (first column is >> inode number): >> >> trycoon@dixie:/mnt/1wire$ ls -li >> totalt 0 >> 3 drwxrwxrwx 1 root root 8 dec 30 23:56 05.4AEC29CDBAAB >> 6 drwxrwxrwx 1 root root 8 dec 30 23:56 10.0C92B5010800 >> 6 drwxrwxrwx 1 root root 8 dec 30 23:56 10.0C92B5010800 >> 11 drwxrwxrwx 1 root root 8 dec 30 23:56 10.158DB5010800 >> 8 drwxrwxrwx 1 root root 8 dec 30 23:56 10.52A9B5010800 >> 8 drwxrwxrwx 1 root root 8 dec 30 23:56 10.52A9B5010800 >> 2 drwxrwxrwx 1 root root 8 dec 30 23:56 10.67C6697351FF >> 14 drwxrwxrwx 1 root root 8 dec 30 23:56 10.7F0560010800 >> 10 drwxrwxrwx 1 root root 8 dec 30 23:56 10.969D98010800 >> 10 drwxrwxrwx 1 root root 8 dec 30 23:56 10.969D98010800 >> 7 drwxrwxrwx 1 root root 8 dec 30 23:56 10.AC1A60010800 >> 13 drwxrwxrwx 1 root root 8 dec 30 23:56 10.B74C8A010800 >> 9 drwxrwxrwx 1 root root 8 dec 30 23:56 10.C9E69E010800 >> 12 drwxrwxrwx 1 root root 8 dec 30 23:56 29.3E4D13000000 >> 12 drwxrwxrwx 1 root root 8 dec 30 23:56 29.3E4D13000000 >> 15 drwxrwxrwx 1 root root 8 dec 30 23:56 29.4D4D13000000 >> 5 drwxrwxrwx 1 root root 8 dec 30 23:56 29.54F81BE8E78D >> 4 drwxrwxrwx 1 root root 8 dec 30 23:56 3A.F2FBE3467CC2 >> 24 drwxr-xr-x 1 root root 8 dec 30 23:32 alarm >> 17 drwxr-xr-x 1 root root 8 dec 30 23:32 bus.0 >> 16 drwxr-xr-x 1 root root 8 dec 30 23:32 bus.1 >> 19 drwxr-xr-x 1 root root 8 dec 30 23:32 settings >> 23 drwxrwxrwx 1 root root 8 dec 30 23:56 simultaneous >> 21 drwxr-xr-x 1 root root 8 dec 30 23:32 statistics >> 22 drwxr-xr-x 1 root root 32 dec 30 23:32 structure >> 20 drwxr-xr-x 1 root root 8 dec 30 23:32 system >> 18 drwxr-xr-x 1 root root 8 dec 30 23:32 uncached >> >> I use this setting in owfs.conf: >> >> server: i2c = ALL:ALL >> >> >> UPDATE: >> >> I think I solved the problem but I don't know why it's working, maybe >> someone could explain it for me? >> I changed the settings in owfs.conf to this: >> >> server: device = /dev/i2c-1 >> #server: i2c = ALL:ALL >> >> Now the list looks like this: >> >> trycoon@dixie:/mnt/1wire$ ls -li >> totalt 0 >> 3 drwxrwxrwx 1 root root 8 dec 31 09:16 05.4AEC29CDBAAB >> 7 drwxrwxrwx 1 root root 8 dec 31 09:16 10.0C92B5010800 >> 10 drwxrwxrwx 1 root root 8 dec 31 09:16 10.158DB5010800 >> 9 drwxrwxrwx 1 root root 8 dec 31 09:16 10.52A9B5010800 >> 2 drwxrwxrwx 1 root root 8 dec 31 09:16 10.67C6697351FF >> 14 drwxrwxrwx 1 root root 8 dec 31 09:16 10.7F0560010800 >> 11 drwxrwxrwx 1 root root 8 dec 31 09:16 10.969D98010800 >> 6 drwxrwxrwx 1 root root 8 dec 31 09:16 10.AC1A60010800 >> 12 drwxrwxrwx 1 root root 8 dec 31 09:16 10.B74C8A010800 >> 8 drwxrwxrwx 1 root root 8 dec 31 09:16 10.C9E69E010800 >> 13 drwxrwxrwx 1 root root 8 dec 31 09:16 29.3E4D13000000 >> 15 drwxrwxrwx 1 root root 8 dec 31 09:16 29.4D4D13000000 >> 5 drwxrwxrwx 1 root root 8 dec 31 09:16 29.54F81BE8E78D >> 4 drwxrwxrwx 1 root root 8 dec 31 09:16 3A.F2FBE3467CC2 >> 24 drwxr-xr-x 1 root root 8 dec 31 09:12 alarm >> 17 drwxr-xr-x 1 root root 8 dec 31 09:12 bus.0 >> 16 drwxr-xr-x 1 root root 8 dec 31 09:12 bus.1 >> 19 drwxr-xr-x 1 root root 8 dec 31 09:12 settings >> 23 drwxrwxrwx 1 root root 8 dec 31 09:16 simultaneous >> 21 drwxr-xr-x 1 root root 8 dec 31 09:12 statistics >> 22 drwxr-xr-x 1 root root 32 dec 31 09:12 structure >> 20 drwxr-xr-x 1 root root 8 dec 31 09:12 system >> 18 drwxr-xr-x 1 root root 8 dec 31 09:12 uncached >> >> Thanks! >> >> // Henrik >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Owfs-developers mailing list >> Owfs-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/owfs-developers ------------------------------------------------------------------------------ _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
