On 12/13/06, Jan Kandziora <[EMAIL PROTECTED]> wrote:

The "read ROM" onewire command will either return the ID of the single
connected device, obviously nothing if no slave is connected, or just
plain
garbarge if more than a single slave is connected.

I'm after the ID, it saves me from doing a "search ROM". The "no chip
connected" situation should return an empty string instead of
FF.FFFFFFFFFFFF, just like reading "uncached" would do. I will try to
implement it today.

It would be nice if we could tell apart the return of "garbage", but I'm
currently having problems to identify this situation. In addition, it
doesn't
seem to be possible to return errors like -ENODEV in aREAD_FUNCTIONs.




> 2. Should we use a name like "not_empty" or "search" ?
> >
>
"search" would be a clear misnomer to me, as there is a "search ROM"
command,
and "read_ROM" is there to *avoid* the need to issue a "search ROM".

Maybe just "simultaneous/id" (and r_id, of course)?


How about separating the functions  as:
"present" = 0 if no devices, "1" if more
"single" = "" if 0 or >1, else name (ID)
You can return other error codes, just not through FS_output_ascii_z

I checked in a provisional "simultaneous/present" -- see if you like it.

Paul Alfille
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to