Hi Jan, thanks for considering my (small) problem. >Double listing of devices means the "Search ROM" trickery fails. Most >likely because it's very fragile on any bit. No checksums at all. No CRC at all? I thought there was a CRC in each ROM number?
>You don't have a star topology cabling, do you? No everything is daisy chain >Do you have homebrewn slaves in your bus? No only commercial devices. On this Raspi the bus master is a DS-2482-800 That's I2C->1wire 8 channels Here is my bus listing: /mnt/1wire/bus.0/bus.0/: 29.1C9E09000000 (DS-2408 LCD driver (by hobby-boards)) /mnt/1wire/bus.0/bus.1/: 3A.546302000000 (DS-2413 PIO start/stop house heating gas boiler) 3A.B36002000000 (DS-2413 PIO start/stop 12V power for LCD) /mnt/1wire/bus.0/bus.2/: 10.9702E6010800 (18S20 temp sensor inside this Raspi box) /mnt/1wire/bus.0/bus.3/: 10.B6FAE5010800 (18S20 temp sensor inside humidity sensor case) 26.FFD8F1000000 (DS-2438 + humidity sens. (by hobby-boards)) 28.4E3066020000 (18B20 temp. sens. living room Ref. for heating) /mnt/1wire/bus.0/bus.4/: /mnt/1wire/bus.0/bus.5/: /mnt/1wire/bus.0/bus.6/: /mnt/1wire/bus.0/bus.7/: You can have pictures of my system here: http://gcolin.hd.free.fr/SystemDescriptionGujan/Pictures.html look at part 1 only: the gas boiler I bought from hobby-boards (now closed) the LCD driver and the humidity sensor. Doc is here: LCD: http://gcolin.hd.free.fr/SystemDescriptionGujan/docTech/LCD%20Driver%20v3.0% 20Schematic.pdf Humidity sensor: http://gcolin.hd.free.fr/SystemDescriptionGujan/docTech/Hobby%20board%20Humi dity%20Temp%20Schematic.png The longest cable is the one on bus 3: I have a CAT5E network cable 5m or 6m long going to a junction box where it's connected (soldered) to a 3m telephone cable of same cross section than CAT5 cable (also twisted pair). This cable is going to the Hobby-board humidity sensor (26.FFD8F1000000 + 10.B6FAE5010800) connected by RJ45 (hobby-boards standard). Then a 0.4m cable connected by RJ45 going to temp. sens. living room (28.4E3066020000) So these 3 devices are daisy chained on bus 3. In these cables 1 pair is used for 1wire DQ+GND and 1 wire from another pair is +12V to power the Humidity sensor (power consumption is 2.83mA). Note that as per the hobby-board doc (link here above) it's possible to use parasistic or external power. I have tried both. But I got wrong humidity values with parasistic power (humid. around 10% lower) Side note: I used to have my external temp. sensor on this bus.3 as well, but it was connected from the junction box by another 3m cable. So it was a kind of star topology: 1x5m cable from bus master to junction box then 1x3m (Extern. temp) + 1x3m (Humid+ Intern. temp). But 3m isn't very long and it has worked fine for years (months?). When I started to miss measures I put this external temp sensor on it's own cable from the bus-master and on it's own bus (bus.7). But it didn't solved the problem. This external temp sensor was the most missing. Even with its own cable and own bus! So a few weeks ago I moved it to an arduino connected by serial to the raspi, then everything is ok. But I don't want to keep this. This sensor must go back to the raspi. When troubleshooting my system I'm planning to connect it back to the raspi to see if I can catch something. Note that when I'm talking of missing measure it's usually not a lot, I can stay for weeks without problem then for a few hours it's missing. The LCD is another story: it's on its own bus and is located near the Raspi as you can see on the photos. Bus cable is something like 0.3m In 2012 I was struggling to have the LCD attached 3 push-buttons working properly and I found help here on this mailing list and solved the problem. Thanks again to Patryk http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/9429 The 12V is going in the same 0.3m cable than the 1wire DQ+GND (we can see it on the photos) When not used there is no power to this LCD driver. To use it you push a button connected to a Raspi GPIO, the Raspi then send an order to a 1-wire PIO (3A.B36002000000) closing a relay and sending 12V to the LCD. The LCD backlight goes on and a script starts displaying by scrolling various measured values (ext. temp., int. temp, humid. etc..) for 60 sec and stops. If you press a button during this 60 sec you access to a menu and can change parameters such as heating temp. set point, etc.. This works perfectly ok, and I'm happy with it. Even if the last troubleshooting error report is showing some problems sometimes, this isn't not a sensor and nothing is recorded from it. So it's ok. Also about the LCD it's worth to mention that in the past years it was sometimes randomly displaying rubbish charcaters. After months (years?) of troubleshooting I found that my script and owserver were simultaneously accessing it and causing the problem. Adding this line to my owfs.conf solved the problem: # Guy 8 Janvier 2014 disable cache for stable values (PIO) # pour bug aleatoire LCD: caracteres aleatoires merdiques timeout_stable = 0 I found in the owfs doc that by setting this to 0 owfs will never read the 2408 to update the cache. This definetly solved the random rubbish characters on the LCD. So mainly the problem I focus on is on bus.3 (humid. + temp. sens.) As said previously my next step will be to check with owread. It's coming. I need more time. Keeping updating here. Best regards -- Guy ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
