I already have a pile of code for 1wire communication on AVRs and other micro's, but I'd really rather not engineer yet another external box if I can help it.
Why is it that you think a PC couldn't handle this? I've built CNC machines with tolerances in the thousandths of an inch using real-time Linux, talking to a 1wire bus is trivial by comparison.... Anyway, I've already written code that does exactly what I described below (between the time I posted it and now ;-). It polls the bus then sends a signal when there is a new device, along with that device's ID. I just finished it, actually and would have been done sooner if I coded more. As it stands, this is the first serious bit of code I've written in probably a year or more. However, it's not as responsive as I'd like, so I might re-write the whole thing in C. Chris. Matthias Urlichs wrote: > Hi, > > Chris Maresca: > >> Ah, I just need to know when X ibutton appears on the bus so that Y can >> be done. I find it strange that 1 wire is not reliable as it is used >> for all kinds of automation and stuff like public transport payment >> where presence (or not) would seem to be critical... >> > > Stuff like that typically uses a simple embedded controller whose > job is to talk to one bus with a very limited number of slave devices. > > There's lots of Atmel code to be found on the net which implements an > 1wire master, so this part is easy. > > (NB: Does anybody know of code for the slave side?) > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
