Exactly, what Colin says. Nobody would do this intentionally, Matthias. A few weeks ago there was a power outage during a bad thunderstorm and for whatever reason one of my three ATmega-based 1-Wire slaves didn't come back up and that caused the entire bus (about 15 devices) to go down. I thought a lightning had fried one or more devices but I went device by device until I found it was just this ATmega-based slave. I just cycled power to it and that fixed the problem so I guess the ATmega entered some strange state after power came back.
This was the first time that this happened in 2 or 3 years that I have been using these ATmega-based slaves so it is not common, but it'd be nice if a malfunctioning ATmega-based slave didn't bring down the entire bus. (And of course, this had never happened but it happened when I was away for a long weekend when I wasn't around to look into it right away.) Cheers, Eloy Paris.- On May 23, 2015 5:46:52 PM EDT, Colin Reese <colin.re...@gmail.com> wrote: >Device malfunction. If a device is inactive you want it to be >invisible. > >C > > > >> On May 23, 2015, at 3:33 PM, Matthias Urlichs <matth...@urlichs.de> >wrote: >> >> Eloy Paris <peloy <at> chapus.net> writes: >> >>> Don't you have issues with the 1-Wire bus when the ATmega is powered >>> down? >> >> Sure I'd have issues. But I don't see why I would want to do that in >the >> first place. >> >> >> ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
