Paul,

here are the log messages (level 2) when the config file has
device = /dev/i2c-2:ALL

Jun 10 11:00:47 mmaster OWFS[21352]: DEFAULT: ow_arg.c:(84) Cannot access device /dev/i2c-2:ALL Jun 10 11:02:16 mmaster OWFS[689]: DEFAULT: ow_arg.c:(84) Cannot access device /dev/i2c-2:ALL

When I put --i2c=/dev/i2c-2:ALL on the command line, it works.

jerry

On 06/13/2015 08:14 AM, Paul Alfille wrote:
So is the problem the parsing of the line in the config file?

On Wed, Jun 10, 2015 at 2:42 PM, Jerry Scharf <sch...@lagunawayconsulting.com <mailto:sch...@lagunawayconsulting.com>> wrote:

    Don't you hate it when someone replies to them selves on the list.
    I was
    trying to get them using the device variable in a config file. I
    couldn't figure out the syntax to get it to do something similar
    to the
    --i2c=port:ALL function. Once I went to the command line form, it
    found
    all three.

    thanks,
    jerry

    On 06/09/2015 07:38 PM, Jerry Scharf wrote:
    > Hi,
    >
    > One more question. I got the server going, but it only saw 1 of
    the 3
    > ds2482-100s. The I2C scan code shows all three devices.
    >
    > It looks from the log like it didn't even try anything else after it
    > found one. Is there something I need to do to have it find all
    three?
    > With over 350 1-wire devices, it seemed better to have multiple
    masters.
    >
    > jerry
    >
    > On 06/09/2015 07:20 PM, Jerry Scharf wrote:
    >> Hi,
    >>
    >> I just pulled a3.1p0 from sourceforge and am building it on a
    beaglebone
    >> black w/ debian 7.8. I ran into some things I don't understand
    while
    >> running configure.
    >>
    >> When I try to enable fuse for owfs, I pass it the include path.
    The test
    >> program blows up during compile with an undefined size_t in the
    stdio.h.
    >> Has anyone found a way around this?
    >>
    >> I have also run into some configure problems around usb as
    well. It is
    >> looking for the file libusb-1.0.pc, which is not on the system
    despite
    >> libusb-dev being installed.
    >>
    >>
    >> Also, I can probably work through the documents, but if someone
    has the
    >> commands to have owserver look at I2C#2 for the converter
    chips, that
    >> would be a big help. The I2C scan tool sees the three chips.
    >>
    >> thanks in advance,
    >> jerry
    >>



------------------------------------------------------------------------------


_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to