You mention a couple of concepts: "persistence" and "caching" that I think
are orthogonal to the systemd -- at least in owfs's view of them.
1. Caching is the storing of 1-wire slave readings (in owserver) for a
short while to work around the relatively slow 1-wire bus speeds. It should
always be
Check about crc errors and short circuit
85degrre is the 'default' memoru value
Em quinta-feira, 12 de junho de 2014, Loren Amelang
escreveu:
> I have owfs and owserver running on a BBB under Ubuntu 12.04. It seems to
> be working, most of the time...
>
> One of the DS18B20 sensors is linked via
I have owfs and owserver running on a BBB under Ubuntu 12.04. It seems to be
working, most of the time...
One of the DS18B20 sensors is linked via Node-RED to store a new temperature
reading to the emoncms site at five minute intervals. Sometimes it draws nice
smooth 12-bit resolution graphs fo
Hi,
How will this handle the persistent features? As I understand ownet does
cache values for example. If the listener is handled externally and ownet
is not running generally, would it have to use disk as persistence?
Vajk
On Thu, Jun 12, 2014 at 1:50 PM, Jan Kandziora wrote:
> Am 12.06.2014
Am 12.06.2014 12:38, schrieb Paul Alfille:
> So can we have the situation where owserver waits for both
>
> 1. the USB device (say) to be available
> 2. a request to come in
>
> and appear always available to the clients?
>
As systemd handles the socket connection (and process start) alone, I
th
So can we have the situation where owserver waits for both
1. the USB device (say) to be available
2. a request to come in
and appear always available to the clients?
On Wed, Jun 11, 2014 at 7:59 AM, Jan Kandziora wrote:
> Am 11.06.2014 13:04, schrieb Paul Alfille:
> >
> > Also, in the docume
