Paul,
Yes that's the idea. That way multiple clients can use the same bus master
without stepping on each others' toes too much.
I've emailed Jacob who wrote the EtherWeather driver (and built the boards) and
he's happy for me to pick up where he left off. I like the protocol as it's
really si
So basically you want to send a special "lock" and "unlock" messages
to your adapter? I guess there could be a stub locking routine for
each adapter. I'd love to see some patches.
Etherweather may not be the best example implementation to use. It was
written by the etherweather creator, who seems
Paul,
Would you be receptive to patches to add a mechanism that other drivers
can use too? I could add lock/unlock functions to interface_routines in
ow_bus_routines.h that the code in ow_buslock.c could call into. That
was HA7Net can use it if it wants to in future.
I'm not sure what you mean
I would simply add your code to module/owlib/src/c/ow_buslock.c in
functions BUS-lock_in and BUS_unlock_in. If there are other 1-wire
buses you should add some text to make sure you only lock when the
correct bus is referenced.
I don't know how you plan on communicating with the other process.
Per
Hi folks,
I'm currently building a microcontroller-based device which has a 1-wire
bus and ethernet. This is intended to be a self-contained device for
home automation or industrial control and will query 1-wire devices
attached to it to gather temperature data and suchlike. Internally I use
a
