Am Samstag, 16. Dezember 2006 02:11 schrieb Paul Alfille:
There are some subtilties with deeper branching. OWFS kee[s trak of the
last selected path to reduce redundant path selection (you have to turn off
all sister DS2409s at each level). I'll add a flag that marks the stored
path as
Am Samstag, 16. Dezember 2006 02:11 schrieb Paul Alfille:
On 12/15/06, Jan Kandziora [EMAIL PROTECTED] wrote:
Before I'll rumble through that, I'd like to add another node to the
DS2409 chip: clearevent just issues a 0x66 disconnect all lines
control command and clears the DS2409s event
Am Samstag, 16. Dezember 2006 02:37 schrieb Paul Alfille:
This is an ambitious, but tricky change. When you are happy with it, let me
test it too. I can construct a 2 level network here.
My idea is to transfer the BUS_select_branch() from BUS_next into BUS_select.
This should do no harm --
Jan,
Your patch works flawlessly, so I included it. Very nice.
As a partially related note, some of the bus masters record if there are any
devices after every RESET. We could use that for scanning, which would be
even faster.
Paul Alfille
On 12/16/06, Jan Kandziora [EMAIL PROTECTED] wrote:
Am Freitag, 15. Dezember 2006 03:05 schrieb Paul Alfille:
Jan,
The DS2409 code has been quite a chore to implement. OWFS has the most
flexible of any implementation I know -- support for unlimitted branching,
interleaved bus usage, and lazy bus changes. I'll be interested in any
improvements
Am Freitag, 15. Dezember 2006 03:05 schrieb Paul Alfille:
Jan,
The DS2409 code has been quite a chore to implement. OWFS has the most
flexible of any implementation I know -- support for unlimitted branching,
interleaved bus usage, and lazy bus changes. I'll be interested in any
improvements
On 12/15/06, Jan Kandziora [EMAIL PROTECTED] wrote:
Before I'll rumble through that, I'd like to add another node to the
DS2409
chip: clearevent just issues a 0x66 disconnect all lines control
command
and clears the DS2409s event flags. I know discharge does this, too, but
I
don't like the
This is an ambitious, but tricky change. When you are happy with it, let me
test it too. I can construct a 2 level network here.
Paul
On 12/15/06, Jan Kandziora [EMAIL PROTECTED] wrote:
Am Freitag, 15. Dezember 2006 03:05 schrieb Paul Alfille:
Jan,
The DS2409 code has been quite a chore to
Am Mittwoch, 13. Dezember 2006 23:09 schrieb Paul Alfille:
Look at http://owfs.sourceforge.net/commands.html
It is a list of devices and the listed command codes.
0x0F for read_ROM works only for DS2401 (and DS2400 I guess).
0x33 works for almost all chips, except
DS1821 (thermometer
Am Donnerstag, 14. Dezember 2006 12:33 schrieb Jan Kandziora:
But from the problems we encounter I think the following is done when
reading 1F./simultaneous/single
Byte 0 0x55 ROM Command (Match ROM)
Byte 1 0x1F Family Code (DS2409)
Byte 2..7 ID
Byte 8
Jan,
The DS2409 code has been quite a chore to implement. OWFS has the most
flexible of any implementation I know -- support for unlimitted branching,
interleaved bus usage, and lazy bus changes. I'll be interested in any
improvements you can make, but it isn't easy.
Paul Alfille
On 12/14/06,
Am Mittwoch, 13. Dezember 2006 03:28 schrieb Paul Alfille:
I'm impressed. You certainly figured out the code style.
Questions:
1. We read_ROM and get a positlve result if any devices exist on the
selected path?
You currently return the name a of single device. And error if there are
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
Am Mittwoch, 13. Dezember 2006 12:51 schrieb Paul Alfille:
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 --
Am Mittwoch, 13. Dezember 2006 17:33 schrieb Paul Alfille:
Many of the adapters have an id chip included, so this technique will only
work on DS2409 branches or the more than one.
I added two additional nodes present_ds2400 and single_ds2400, to support
both the 0x33 read ROM and the older
Look at http://owfs.sourceforge.net/commands.html
It is a list of devices and the listed command codes.
0x0F for read_ROM works only for DS2401 (and DS2400 I guess).
0x33 works for almost all chips, except
DS1821 (thermometer doesn't have an ID anyways)
DS2223, DS2224 (old chips I think)
But
Hi all, hi Paul,
I made a small enhancement to owfs to implement the read ROM function all
onewire chips have. With this function, a single key on a (sub)-bus can be
identified without (fairly expensive) scanning.
The attached code works with ibutton keys on the buses of a DS2482-800 and
with
I'm impressed. You certainly figured out the code style.
Questions:
1. We read_ROM and get a positlve result if any devices exist on the
selected path?
2. Should we use a name like not_empty or search ?
Paul Alfille
On 12/12/06, Jan Kandziora [EMAIL PROTECTED] wrote:
Hi all, hi Paul,
I made
Jan,
You currently return the name a of single device. And error if there are
none, or more than one.
What do you really intend? Do you want to know if there are
A. exactly 1 (and it's number) ?
B more than 0 ?
C more than 1 ?
Paul Alfille
On 12/12/06, Paul Alfille [EMAIL PROTECTED] wrote:
19 matches
Mail list logo
