That worked!  I changed to "server: w1"- And owserver starts, however...
I'm not seeing any sensors:
*owdir*
/bus.0
/uncached
/settings
/system
/statistics
/structure

Is this a result of using the module from userspace and not accessing it
directly on the i2c bus?

While I run "owdir" in one terminal the log output shows this:

sudo /usr/bin/owserver -c /etc/owfs.conf --debug >> owserver.log
  DEBUG: ow_daemon.c:(170) main thread id = 3069947632
CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd library
isn't found
   CALL: ow_parsename.c:(174) path=[]
  DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and mock
adapters)
  DEBUG: ow_w1_list.c:(53) Sending w1 bus master list message
  DEBUG: ow_net_server.c:(76) ServerAddr: [localhost] [4304]
  DEBUG: ow_w1_send.c:(131) Netlink send -----------------
  DEBUG: ow_w1_send.c:(142) NETLINK sent seq=1
  DEBUG: ow_w1_dispatch.c:(172) Dispatch loop
  DEBUG: ow_w1_parse.c:(112) Wait to peek at message
  DEBUG: ow_tcp_read.c:(63) attempt 24 bytes Time: 10.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 24 - 0 = 24
  DEBUG: from_client.c:(65) FromClient payload=2 size=0 type=7 sg=0x10A
offset=0
  DEBUG: from_client.c:(73) FromClient (no servermessage) payload=2 size=0
type=7 controlflags=0x10A offset=0
  DEBUG: ow_tcp_read.c:(63) attempt 2 bytes Time: 10.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 2 - 0 = 2
  DEBUG: handler.c:(152) START handler /
   CALL: data.c:(103) DataHandler: parse path=/
  DEBUG: ow_parseobject.c:(163) /
   CALL: ow_parsename.c:(174) path=[/]
   CALL: data.c:(163) Directory message (all at once)
  DEBUG: dirall.c:(65) OWSERVER Dir-All SpecifiedBus=0 path = /
  DEBUG: ow_dir.c:(80) path=/
   CALL: ow_dir.c:(104) path=/
  DEBUG: ow_cache.c:(853) Looking for directory 00 00 00 00 00 00 00 00
  DEBUG: ow_cache.c:(866) Get from cache sn 00 00 00 00 00 00 00 00
pointer=0xb6f80bb8 extension=0
  DEBUG: ow_cache.c:(895) Dir not found in cache
   CALL: ow_parsename.c:(174) path=[/bus.0]
  DEBUG: ow_regex.c:(24) Reg Ex expression <^bus\.([[:digit:]]+)/?>
compiled to 0xb6f8073c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^settings/?> compiled to
0xb6f8075c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^statistics/?> compiled to
0xb6f8077c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^structure/?> compiled to
0xb6f8079c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^system/?> compiled to
0xb6f807bc
  DEBUG: ow_regex.c:(24) Reg Ex expression <^interface/?> compiled to
0xb6f807dc
  DEBUG: ow_regex.c:(24) Reg Ex expression <^text/?> compiled to 0xb6f807fc
  DEBUG: ow_regex.c:(24) Reg Ex expression <^json/?> compiled to 0xb6f8081c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^uncached/?> compiled to
0xb6f8083c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^unaliased/?> compiled to
0xb6f8085c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^alarm?> compiled to 0xb6f8087c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^simultaneous/?> compiled to
0xb6f8089c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^thermostat/?> compiled to
0xb6f808bc
  DEBUG: ow_regex.c:(24) Reg Ex expression <^/bus\.[[:digit:]]+/?> compiled
to 0xb6f808dc
  DEBUG: ow_regex.c:(24) Reg Ex expression <\.> compiled to 0xb6f808fc
  DEBUG: ow_regex.c:(24) Reg Ex expression <\.all$> compiled to 0xb6f8091c
  DEBUG: ow_regex.c:(24) Reg Ex expression <\.byte$> compiled to 0xb6f8093c
  DEBUG: ow_regex.c:(24) Reg Ex expression <\.[[:digit:]]+$> compiled to
0xb6f8095c
  DEBUG: ow_regex.c:(24) Reg Ex expression <\.[[:alpha:]]$> compiled to
0xb6f8097c
  DEBUG: ow_regex.c:(100) 0: 0->5 found <><bus.0><>
  DEBUG: ow_regex.c:(100) 1: 4->5 found <bus.><0><>
  DEBUG: ow_regex.c:(100) 0: 0->6 found <></bus.0><>
  DEBUG: ow_regex.c:(24) Reg Ex expression
<^([[:xdigit:]]{2})\.?([[:xdigit:]]{12})\.?([[:xdigit:]]{2}){0,1}$>
compiled to 0xb6f809a0
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_parsename.c:(133) /bus.0
   CALL: ow_parsename.c:(174) path=[/uncached]
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_parsename.c:(133) /uncached
   CALL: ow_parsename.c:(174) path=[/settings]
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_parsename.c:(133) /settings
   CALL: ow_parsename.c:(174) path=[/system]
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_parsename.c:(133) /system
   CALL: ow_parsename.c:(174) path=[/statistics]
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_parsename.c:(133) /statistics
   CALL: ow_parsename.c:(174) path=[/structure]
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_parsename.c:(133) /structure
  DEBUG: ow_dir.c:(199) ret=0
  DEBUG: ow_parsename.c:(133) /
  DEBUG: data.c:(193) DataHandler: FS_ParsedName_destroy done
  DEBUG: data.c:(207) DataHandler: cm.ret=0
  DEBUG: to_client.c:(75) payload=58 size=57, ret=0, sg=0x10A offset=0
  DEBUG: data.c:(226) Finished with client request
  DEBUG: handler.c:(134) OWSERVER handler done
  DEBUG: ow_net_server.c:(259) Normal completion.



Thanks for all your help!

[image: Linkedin] <http://de.linkedin.com/in/rlagus> *Robert Lagus*

+358 (0)40 662 44 99

rob...@lagus.net



On Tue, 17 Sep 2019 at 16:54, Jan Kandziora <j...@gmx.de> wrote:

> Am 17.09.19 um 08:52 schrieb Robert Lagus:
> >
> > *ofws.conf:*
> > ! server: server = localhost:4304
> > server: i2c = /dev/i2c-1
> >
> Please check if you have the ds2482 kernel module loaded.
>
> What you are doing here is accessing the ds2482 directly from user
> space. This is ok, but it creates a mess on the I²C bus if the ds2482
> module is loaded, as that module access the ds2482 at the same time.
>
> So either unload and blacklist that module, or change the owfs.conf line to
>
> server: w1
>
> This makes owserver use the kernel modules instead of accessing the I²C
> hardware by itself.
>
> Kind regards
>
>         Jan
>
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to