Is that Family code 42? Or the last few digits of the unique ID portion? I think the convention has been to use Family codes above 0x80 for 3rd party devices, and even then make sure they aren't aliased to a known device in the lower range. (i.e. Maxim makes some custom runs with family codes 0x80 above the standard device).
All this would be easier if someone set up a registry of family codes for 3rd party devices. I'm told that some vendors purchased address space, but I don't know the price or restrictions. Louis Swart's LCD was the first "rogue" device, using family code FF that was flagged by Dallas's software as unavailable. http://www.louisswart.co.za/1-wire_lcd_100.pdf It's been in use since 2001 and so would be unlikely to stepped on by Dallas or anyone else. He states that his addresses are FF.0001XXXXXX reserving the next address range (FF.0002XXXX) for his next device. There have been no other devices, and so perhaps he would be willing to allow others to use part of the range. Hobbyboards uses EE and EF for the ultraviolt meter and a planned series of slaves. iButtonlink uses the (illegal) 00 to trigger the LinkLocator The BEA0910 uses BE Paul Alfille On Tue, Apr 13, 2010 at 5:44 AM, Matthias Urlichs <matth...@urlichs.de> wrote: > On Mon, 12 Apr 2010 12:20:17 +0000, I wrote: > >> One idea which comes to mind: all Dallas chip IDs I've seen so far end >> with x000000 (or 010800 or some combination thereof). I propose to use >> some of these bits as a signature, so that OWFS knows that it can use a >> special command (is there a global list so that we don't step on >> anybody's toes?) for asking the chip what it really is and what other >> interesting things it might be able to do. >> > Found it: http://owfs.sourceforge.net/family.html > > Is that uptodate? > > I'll freeze the last two bytes of my self-generated IDs to 0xBE42 and > start thinking of implementing a nice feature/status/whatever command. > 0x42 seems to be still globally free. ;-) > > -- > Matthias Urlichs > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
