On Jan 3, 2008 2:06 PM, Jim Kusznir <[EMAIL PROTECTED]> wrote:
> , but a custom device in OWFS could possibly be better.
>
> We plan to put some manpower on writing code for the ATMEL cpu's for
> this purpose, but haven't quite gotten there yet. I was
> wondering/fearing how hard it would be to do the slave-side 1-wire
> code, as I haven't found any mention of it yet.
>
>
> From OWFS's point or view, writing support for a new slave is easy. The
hard part is emulating a slave.
If you only plan to use OWFS, the restrictions can be more lax.
1. If you plan to use current 1-wire bus masters and intermix on a 1-wire
network, the hardware compatibility is the only issue.
2. It is certainly possible to extend OWFS to use custom masters and custom
slaves with a different communication protocol. The aspects of 1-wire that
OWFS requires are unique slave numbering, individual addressing, and
discovery.
3. The is a semi-compatible Fox Net
http://www.ibuttonlink.com/pdf/Using%20fox-Bus.pdf marketed by iButtonlink
that has potential advantages in network design, and possibly more
approachable licensing scheme.
4. I've proposed adding 1-wire slave capabilities to a Maxim microprocessor
(a sure win in my opinion) with no response.
I really like the idea of extending the 1-wire reach. If Maxim has no
interest, perhaps we need to find compatible alternatives.
Paul Alfille
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
