Hi all,
I am experiencing some difficulties when using a PCA9546 i2c-switch in
conjunction with five DS2483 onewire-masters on a Beaglebone Black.
Owfs-Version is 2.9p1 (latest) and Kernel is 3.8.13 (Debian-distro).
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:
DEBUG MODE
libow version:
2.9p1
DEBUG: ow_daemon.c:(166) main thread id = 3070201856
CONNECT: ow_avahi_link.c:(68) No Avahi support. Library libavahi-client
couldn't be loaded
CONNECT: ow_dnssd.c:(82) Zeroconf/Bonjour is disabled since dnssd library
isn't found
CALL: ow_parsename.c:(99) path=[]
DEBUG: owlib.c:(81) Globals temp limits 0C 100C (for simulated adapters)
CONNECT: ow_ds2482.c:(383) [Is a directory] Could not open i2c device /dev/.
CONNECT: ow_ds2482.c:(383) [Is a directory] Could not open i2c device
/dev/..
CONNECT: ow_ds2482.c:(397) Found an i2c device at /dev/i2c-0 address 18
CONNECT: ow_ds2482.c:(423) i2c device at /dev/i2c-0 address 18 cannot be
reset. Not a DS2482.
DEBUG: ow_com_close.c:(42) Unimplemented!!!
CONNECT: ow_ds2482.c:(397) Found an i2c device at /dev/i2c-1 address 18
DEBUG: ow_ds2482.c:(515) ok
CONNECT: ow_ds2482.c:(426) i2c device at /dev/i2c-1 address 18 appears to be
DS2482-x00
DEBUG: ow_ds2482.c:(795) Channel selected doesn't match
CONNECT: ow_ds2482.c:(691) DS2482-100 (Single channel)
DEBUG: ow_ds2482.c:(678) Can set to port configuration! a DS2483!
CONNECT: ow_ds2482.c:(397) Found an i2c device at /dev/i2c-2 address 18
DEBUG: ow_ds2482.c:(515) ok
CONNECT: ow_ds2482.c:(426) i2c device at /dev/i2c-2 address 18 appears to be
DS2482-x00
DEBUG: ow_ds2482.c:(795) Channel selected doesn't match
CONNECT: ow_ds2482.c:(691) DS2482-100 (Single channel)
DEBUG: ow_ds2482.c:(678) Can set to port configuration! a DS2483!
CONNECT: ow_ds2482.c:(397) Found an i2c device at /dev/i2c-3 address 18
DEBUG: ow_ds2482.c:(515) ok
CONNECT: ow_ds2482.c:(426) i2c device at /dev/i2c-3 address 18 appears to be
DS2482-x00
DEBUG: ow_ds2482.c:(795) Channel selected doesn't match
CONNECT: ow_ds2482.c:(691) DS2482-100 (Single channel)
DEBUG: ow_ds2482.c:(678) Can set to port configuration! a DS2483!
CONNECT: ow_ds2482.c:(397) Found an i2c device at /dev/i2c-4 address 18
DEBUG: ow_ds2482.c:(515) ok
CONNECT: ow_ds2482.c:(426) i2c device at /dev/i2c-4 address 18 appears to be
DS2482-x00
DEBUG: ow_ds2482.c:(795) Channel selected doesn't match
CONNECT: ow_ds2482.c:(691) DS2482-100 (Single channel)
DEBUG: ow_ds2482.c:(678) Can set to port configuration! a DS2483!
CONNECT: ow_ds2482.c:(397) Found an i2c device at /dev/i2c-5 address 18
DEBUG: ow_ds2482.c:(515) ok
CONNECT: ow_ds2482.c:(426) i2c device at /dev/i2c-5 address 18 appears to be
DS2482-x00
DEBUG: ow_ds2482.c:(795) Channel selected doesn't match
CONNECT: ow_ds2482.c:(691) DS2482-100 (Single channel)
DEBUG: ow_ds2482.c:(678) Can set to port configuration! a DS2483!
I sporadically see the connected DS2406, DS2438 and DS18B20 (12.xxx, 26.xxx,
28.xxx) in the webinterface on port 2121. Further I am able to read all
sensors in principle. But in 90% of all tries, I see only one or none. The
Debug-Log tells me, that the sensor is not present then.
Cable length are within 5cm (DS2438 and DS2406) to zero (DS18B20). The I2C
is operated at 3,3V (through SLPZ) and the main supply is 5V, which can also
be measured on the bus.
So my question:
- What to look for? I2C or Onewire?
- The PCA954x should be transparent to the owfs-driver. Is there
are way to check for hickups? Is the owfs-driver strictly using the
i2c-kernel-api (just making sure there is no exception from that)?
- Is somebody successfully using this or a similar setup?
Best regards,
Robert
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
