Hello Jan,
Had a good look, no other errors.
I have tried to run owserver in debug mode,
Here is some of the debug output, I think this is the area you might need... is
it that I need to add the family code (A6) to the 2438 family list in some way
DEBUG: ow_w1_parse.c:(249) About to call nrs_callback
DEBUG: ow_w1_parse.c:(251) Called nrs_callback
DEBUG: ow_w1.c:(196) SN found: A6 5F 8F 9B 00 00 50 F6
DEBUG: ow_search.c:(74) Device found: A6 5F 8F 9B 00 00 50 F6
DEBUG: ow_cache.c:(546) Adding device location A6 5F 8F 9B 00 00 50 F6 bus=1
DEBUG: ow_cache.c:(635) Add to cache sn A6 5F 8F 9B 00 00 50 F6
pointer=0xb6eb0950 index=0 size=4
DEBUG: ow_cache.c:(546) Adding device location A6 5F 8F 9B 00 00 50 F6 bus=1
DEBUG: ow_cache.c:(635) Add to cache sn A6 5F 8F 9B 00 00 50 F6
pointer=0xb6eb0950 index=0 size=4
CALL: ow_parsename.c:(104) path=[/A6.5F8F9B000050]
DEBUG: ow_regex.c:(74) Reg Ex expression <^bus\.([[:digit:]]+)/?> compiled to
0xb6eb0560
DEBUG: ow_regex.c:(74) Reg Ex expression <^settings/?> compiled to 0xb6eb0580
DEBUG: ow_regex.c:(74) Reg Ex expression <^statistics/?> compiled to
0xb6eb05a0
DEBUG: ow_regex.c:(74) Reg Ex expression <^structure/?> compiled to 0xb6eb05c0
DEBUG: ow_regex.c:(74) Reg Ex expression <^system/?> compiled to 0xb6eb05e0
DEBUG: ow_regex.c:(74) Reg Ex expression <^interface/?> compiled to 0xb6eb0600
DEBUG: ow_regex.c:(74) Reg Ex expression <^text/?> compiled to 0xb6eb0620
DEBUG: ow_regex.c:(74) Reg Ex expression <^json/?> compiled to 0xb6eb0640
DEBUG: ow_regex.c:(74) Reg Ex expression <^uncached/?> compiled to 0xb6eb0660
DEBUG: ow_regex.c:(74) Reg Ex expression <^unaliased/?> compiled to 0xb6eb0680
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_regex.c:(74) Reg Ex expression <^alarm?> compiled to 0xb6eb04a0
DEBUG: ow_regex.c:(74) Reg Ex expression <^simultaneous/?> compiled to
0xb6eb03e0
DEBUG: ow_regex.c:(74) Reg Ex expression <^thermostat/?> compiled to
0xb6eb0400
DEBUG: ow_regex.c:(74) Reg Ex expression <^text/?> compiled to 0xb6eb0420
DEBUG: ow_regex.c:(74) Reg Ex expression <^json/?> compiled to 0xb6eb0440
DEBUG: ow_regex.c:(74) Reg Ex expression <^uncached/?> compiled to 0xb6eb0460
DEBUG: ow_regex.c:(74) Reg Ex expression <^unaliased/?> compiled to 0xb6eb0480
DEBUG: ow_regex.c:(74) Reg Ex expression
<^([[:xdigit:]]{2})\.?([[:xdigit:]]{12})\.?([[:xdigit:]]{2}){0,1}$> compiled to
0xb6eb0740
DEBUG: ow_regex.c:(201) 0: 0->15 found <><A6.5F8F9B000050><>
DEBUG: ow_regex.c:(201) 1: 0->2 found <><A6><.5F8F9B000050>
DEBUG: ow_regex.c:(201) 2: 3->15 found <A6.><5F8F9B000050><>
DEBUG: ow_cache.c:(912) Looking for device A6 5F 8F 9B 00 00 50 F6
DEBUG: ow_cache.c:(1070) Search in cache sn A6 5F 8F 9B 00 00 50 F6
pointer=0xb6eb0950 index=0 size=4
DEBUG: ow_cache.c:(1086) Value found in cache. Remaining life: 120 seconds.
DEBUG: ow_presence.c:(75) Found device on bus 1
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_regex.c:(201) 0: 0->15 found <><A6.5F8F9B000050><>
DEBUG: ow_regex.c:(201) 1: 0->2 found <><A6><.5F8F9B000050>
DEBUG: ow_regex.c:(201) 2: 3->15 found <A6.><5F8F9B000050><>
DEBUG: ow_parsename.c:(63) /A6.5F8F9B000050
DEBUG: ow_w1.c:(201) SN finished
CALL: ow_parsename.c:(104) path=[/bus.1]
DEBUG: ow_regex.c:(201) 0: 0->5 found <><bus.1><>
DEBUG: ow_regex.c:(201) 1: 4->5 found <bus.><1><>
DEBUG: ow_regex.c:(74) Reg Ex expression <^/bus\.[[:digit:]]+/?> compiled to
0xb6eb06a0
DEBUG: ow_regex.c:(201) 0: 0->6 found <></bus.1><>
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_parsename.c:(63) /bus.1
CALL: ow_parsename.c:(104) path=[/bus.0]
DEBUG: ow_regex.c:(201) 0: 0->5 found <><bus.0><>
DEBUG: ow_regex.c:(201) 1: 4->5 found <bus.><0><>
DEBUG: ow_regex.c:(201) 0: 0->6 found <></bus.0><>
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_parsename.c:(63) /bus.0
CALL: ow_parsename.c:(104) path=[/uncached]
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_parsename.c:(63) /uncached
CALL: ow_parsename.c:(104) path=[/settings]
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_parsename.c:(63) /settings
CALL: ow_parsename.c:(104) path=[/system]
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_parsename.c:(63) /system
CALL: ow_parsename.c:(104) path=[/statistics]
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_parsename.c:(63) /statistics
CALL: ow_parsename.c:(104) path=[/structure]
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_regex.c:(154) Not found
DEBUG: ow_parsename.c:(63) /structure
DEBUG: ow_dir.c:(199) ret=0
DEBUG: ow_parsename.c:(63) /
DEBUG: data.c:(193) DataHandler: FS_ParsedName_destroy done
DEBUG: data.c:(207) DataHandler: cm.ret=0
DEBUG: to_client.c:(76) payload=82 size=81, ret=0, sg=0x10A offset=0
DEBUG: data.c:(226) Finished with client request
DEBUG: handler.c:(135) OWSERVER handler done
DEBUG: ow_net_server.c:(259) Normal completion.
John
-----Original Message-----
From: Jan Kandziora [mailto:j...@gmx.de]
Sent: 29 November 2016 22:33
To: OWFS (One-wire file system) discussion and help
<owfs-developers@lists.sourceforge.net>
Subject: Re: [Owfs-developers] DS2438 reporting A6 as family
Am 29.11.2016 um 18:29 schrieb John Bass:
>
> I have just connected a DS2438, which seems to be reporting a A6 family code,
> and thus not giving the correct input details.
> w1_master_driver w1_bus_master1: Family a6 for a6.5000009b8f5f.f6 is not
> registered.
>
This is a message from the kernel driver. It means: there is no kernel driver
for the DS2438 loaded. Which is quite true, as such a driver does not exist yet.
> On owfs 3.1p1
>
Uh, no. You are looking at the wrong thing.
The w1 subsystem has two parts. One is the host adaptor code, which owfs
happily use when started with --w1. On top of this, owfs implements its own
userspace driver code for all the slave chips it supports. So if something
fails with a slave chip, you have to look for another error which doesn't come
from the kernel driver.
(The other part of the w1 subsystem is the slave code which owfs doesn't use at
all. You can use it in parallel to owfs when there is a kernel driver for the
slave chip existing.)
Kind regards
Jan
------------------------------------------------------------------------------
_______________________________________________
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
