Yes.

UPS even die eventually. My little board tells the Pi to shut down when battery 
gets low. It's basically a smart mini ups. 

Colin

> On Dec 12, 2017, at 7:12 PM, joep <j...@naturalmethods.org> wrote:
> 
> Hi Colin,
> 
>     I had those experiences as well (including permanently damaged SD Cards 
> and PC's damaged by lightning strikes) and now have all IT equipment on a 
> UPS. The 1-wire controller will be part of a home automation server and won't 
> be remotely installed - it will be in the study on a UPS.
> 
> Regards
> Joe P.
> 
>> On 13/12/17 11:43, Colin Reese wrote:
>> WRT power, USB power is still an issue, especially over long period with 
>> fluctuating power. I use a power-management board and battery backup for 
>> this reason. Non-graceful shutdowns not only corrupt the operating system, 
>> but also potentially the SDCards permanently. This is a bad situation, 
>> obviously, exacerbated for remote installations.
>> 
>> C
>> 
>>> On 12/12/2017 5:34 PM, joep wrote:
>>> Thanks again Jan.
>>> 
>>>  >>> $ owserver --i2c=/dev/i2c-0:ALL
>>> 
>>> That answers my most pressing question.
>>> 
>>>  >>>I'm talking about the Raspberry Zero W, which has a built-in SDIO WLAN
>>> adapter and a built-in antenna. No fiddling with USB needed (though USB
>>> power isn't much of an issue anymore since the Raspberry B+).
>>> 
>>> I understood your initial suggestion re the Raspberry Zero W. My suspicion 
>>> is that WiFi is flaky irrespective of the host controller - I've had issues 
>>> with name brand WiFi units on name brand PC's. I suspect WiFi (and it's 
>>> drivers) is designed for shortish-term connections - not long ones lasting 
>>> months. Ethernet seems to fare much better.
>>> 
>>> Regards
>>> Joe P.
>>> 
>>>> On 13/12/17 11:08, Jan Kandziora wrote:
>>>>> Am 12.12.2017 um 22:38 schrieb joep:
>>>>> Jan thanks for the reply.
>>>>> 
>>>>> I currently have 2 Raspberry Pi's (of late 2012 vintage - forgot the
>>>>> model ID's) and I've been running them since early 2013. I've run
>>>>> one for 6 months non-stop (to manage the lighting and temperature in
>>>>> a terrarium) and only stopped it to update the Raspbian firmware. I
>>>>> use the "Blue DS9490R unit" (Dallas call it a DS9490R) to drive the
>>>>> 1-wire network. On of the main issues I found with operating the Pi
>>>>> with WiFi connectivity is the WiFi connectivity - seems to be a bit
>>>>> flaky (maybe the drivers for the specific WiFi unit - the WiFi was
>>>>> not powered directly from the Pi but from a USB hub)
>>>>> 
>>>> USB power on the original Raspberries was a source of constant
>>>> misfortune. And USB hubs often enough do, too.
>>>> 
>>>> 
>>>>> So I don't
>>>>> think I'll chose a Raspberry B Zero W for long term stability
>>>>> reasons.
>>>>> 
>>>> I'm talking about the Raspberry Zero W, which has a built-in SDIO WLAN
>>>> adapter and a built-in antenna. No fiddling with USB needed (though USB
>>>> power isn't much of an issue anymore since the Raspberry B+).
>>>> 
>>>> 
>>>> 
>>>>> The system I'm thinking of building is for a home server and will use
>>>>> a low-end laptop as I do not have to wire the basic infrastructure to
>>>>> get a computing environment happening (power supply, screen,
>>>>> keyboard, memory, case) - it's all setup already. All I'll need is a
>>>>> USB-to-I2C-to-1_wire.
>>>>> 
>>>>> If I'm to use a USB-to-I2C adaptor (say FT232H) to drive a I2C
>>>>> 1-wire master (say a DS2482-800) how should I initialize OWFS?
>>>>> 
>>>>> sudo owfs –d=/dev/i2c-0 /mnt/owfs ? or
>>>>> 
>>>>> sudo owfs –u=/dev/i2c-0 /mnt/owfs (manual says this option is for a
>>>>> "USB adapter (DS9490) as 1-wire bus master") ?
>>>>> 
>>>> Please don't use the owfs binary. It has an unsolvable race condition.
>>>> Use owserver and access it through the owwrite, owread, owdir, owget
>>>> shell tools or through one of the language bindings.
>>>> 
>>>> $ owserver --i2c=/dev/i2c-0:ALL
>>>> 
>>>> Kind regards
>>>> 
>>>>     Jan
>>>> 
>>>> 
>>>> ------------------------------------------------------------------------------
>>>>  
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>> _______________________________________________
>>>> Owfs-developers mailing list
>>>> Owfs-developers@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>>  
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Owfs-developers mailing list
>>> Owfs-developers@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>> 
>> ------------------------------------------------------------------------------
>>  
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Owfs-developers mailing list
>> Owfs-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to