I've been a long time lurker. I run 30+ sensors in a heating & hot water control system, combined with a 422 setup to do all the relay and D/A work. I use link-hubs for the bus masters (one serial, one ethernet.) Someday I will do the final Ruby on Rails/Postgresql interface and put it out on the net.
I think the key thing about 1-wire that does not exist for some of the other protocols is the unique IDs and type identification. RS422 is a perfect example of there not being any unifying addressing or communications model, with devices coming up with their own stuff. Anything that requires an external mapping table to fit into OWFS would be a bad fit, IMO. I should be able to say what kind of bus type for bus N on startup and at least the basics should be computed automatically. I do agree that Dallas was probably hoping for more traction than it got for 1-wire. I do not agree that adding power makes 1-wire little better than 422. If I can get a 422 based temperature sensor, signal conditioner, A/D and comm interface for under $25 (~10x the 1-wire) a point, please point me to it. With some care, I can build a 25 point thermocouple sensor setup for under $1k. Compare that with a more typical number of $100-200 per point and up for a simple lab system. 1-wire is not an answer to everything, but it's better than most people give it credit for. I am excited that there are some new devices coming out. jerry njh wrote: > On Thu, 7 Jan 2010, Paul Alfille wrote: > >> Which protocols are you suggesting? i2c? bluetooth? > > Yeah, why not? We have a lovely system for managing smart sensors, with > good firewalling of processes and simple discovery via the file system. > I've got a bunch of pcf8574 i2c output boards which would fit nicely in > the owfs model. My only concern is scope creep. Are there any comparable > libraries for other sensor-like devices? > > njh > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Owfs-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/owfs-developers ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
