Absolutely. Actually Louis Swart seems to have mapped out only part of that space. It was his intension that FF be partitioned as well. Send the code for reading your device, if it's done, or at least the outline. We can include it in OWFS easily. Right now OWFS has an efficient tree search through the family code (first byte of the name), then has specific handlers for each family. Probably what we'll do is search on the first two bytes, but zero out the non-FF second byte. That way the "property space" (the file types like temperature, ID, PIO) for two different FF devices won't be intermixed. Paul
________________________________ From: [EMAIL PROTECTED] on behalf of ND Holmes Sent: Mon 9/26/2005 10:41 PM To: [email protected] Subject: Re: [Owfs-developers] Microchip acting as 1Wire A friend of mine built a humidity/temperature sensor based on a Sensirion SHT75. The part basically has a serial interface, which we tied back to a PIC16F628 that then looks like a 1-wire part. Mark's been meaning to clean it up because he wrote it in a bit of a hurry (and it's written in Intel-esque pseudo-assembly, made to be assembled by Tech Tools' cvasm16). Also, he fixed some linearization bug since the last time I got source, so this version isn't the final (nor perfect) one. However, this little jewel is currently running my evap cooler, furnace, and air conditioner with the assistance of my workshop computer, so it's plenty reliable over a reasonably large 1-wire network (a few hundred feet of cable). When I saw this discussion on the list today, I asked if he'd mind if I posted it in its current state. So, the latest version I have: http://www.drgw.net/~maverick/electronics/tidbits/sht75v10.src I'll see if I can get the updated version from him tomorrow at work. This brings us to an item about OWFS... As I remember it, Dallas/Maxim reserves 0xFF as the device address class for things that don't have an assigned number (or third-party type devices). However, since OWFS assumes that 0xFF-class devices are that LCD module, we had to map ours in as 0xFE (and set up the OWFS module appropriately). This is a bit of a pain since his device may eventually conflict with a Maxim part and we can (probably) never merge the code with the main OWFS trunk. What about using a couple more bytes of address on 0xFF devices to differentiate between subclasses? Thoughts? Nathan -------------------------------------------------------------------------- Nathan D. Holmes [EMAIL PROTECTED] Colorado Springs, CO http://www.drgw.net Phone: 719-638-4900 ------------------------------------------------------------------------- ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
<<winmail.dat>>
