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 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
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
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.
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
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
