Am 22.07.2013 10:49, schrieb Robert Budde:
>
> The first DS2483 is directly connected to the "native" I2C line (/dev/i2c-1)
> of the Beaglebone Black. As far as I can tell, this setup works well as long
> as I do not enable the I2C switch. When I enable the I2C-switch by using a
> Device Tree Overlay it gives me four additional lines as expected
> (/dev/i2c-2 to /dev/i2c-5). When starting owserver with -i2c=ALL:0, all five
> DS2483 are found and configured:
>
Now I think of your device layout, that means you have *two* DS2483
connected to I²C once the switch is activated.
I²C Host
|
|
+--DS2483--ow0
|
|
##PCA954x##
| | | |
| | | DS2483--ow1
| | |
| | DS2483--ow2
| |
| DS2483--ow3
|
|
DS2483--ow4
Is it built this way? If yes, this won't work. Once one of the switch
channels is activated, the DS2483 on that branch line is connected to
the main line, along with the DS2483 already connected there. There is
no way for the host to tell apart the two DS2483 (same I²C address), so
they react *both* to each command, resulting in a Wired-AND readout of
both chips to the host.
Remove the DS2483 on the main line and the others should work.
Kind regards
Jan
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
