By the way, apologies for not explaining correctly the exact situation that I
had in mind -- I mentioned "device with no power", which I am sure didn't make
any sense to Matthias, but now I think that "malfunctioning device" is more
appropriate.
On May 23, 2015 6:24:22 PM EDT, Eloy Paris wrot
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 though
Device malfunction. If a device is inactive you want it to be invisible.
C
> On May 23, 2015, at 3:33 PM, Matthias Urlichs wrote:
>
> Eloy Paris 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
Eloy Paris 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
Hi Roland,
> I get owfs-3.1p0 on my rpi with GCC compiled including libusb.
> Only PHP is disabled.
> BUT, I use the following changes in the makefiles:
> (Shown as patch between the original and my modificated
> version)
That is great, with these patches, it is compiling ok here as well.
Thanks
The code for the EDS0065 has the wrong data type for the humidity_hi and
humidity_low thresholds (i8 instead of float8) . I copied the types used
for the EDS0068 and everything works perfectly. Before the change the
values weren’t writable - they would revert to zero. Setting the value
directly
Hi Matthias,
Great work on your MoaT 1-Wire slave!
Hey, kind of unrelated question (although I guess indirectly related)...
Don't you have issues with the 1-Wire bus when the ATmega is powered
down? It's been a while since I looked into this for my own ATmega-based
slave but if I remember correc
Hello everybody,
my MoaT code (ATmega slaves connected to 1wire) can now do proper reboot
reporting, watchdog, A/D conversion, listing in /alarm, PWM and one-shot,
triggers and counters and I/O ports and whatnot.
The OWFS part is available at g...@github.com:M-o-a-T/owfs.git in the "moat"
branch.
Hi Roland,
thanks for looking into this!
> have you add the modification from your first mail here now also?
Yes. Without that patch, compiling doesn't get far. With that patch, and
also with...
> "./configure --disable-swig"
I get until
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src
Hello,
I get owfs-3.1p0 on my rpi with GCC compiled including libusb.
(Installed libusb-1.0-.dev)
Only PHP is disabled.
Current configuration:
Deployment location: /opt/owfs
Compile-time options:
USB is enabled
AVAHI is DISABLED
I
Hello,
have you add the modification from your first mail here now also?
Can you build the system with an "./configure --disable-swig"?
Best regards,
Roland
-Ursprüngliche Nachricht-
From: c...@kruemel.org
Sent: Saturday, May 23, 2015 9:51 AM
To: OWFS (One-wire file system) discussion an
> gcc -c -I../../../../src/include -I../../../owlib/src/include
> -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fstack-protector
> -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -DPERL_POLLUTE -O2 -g -DVERSION=\"3.1p0\"
> -DXS_VERSION=\"3.1p0\" -fPIC "-I/usr
12 matches
Mail list logo
