Hello, Thanks you, Just tried that, now responds just fine, however the temperature it reports for the device is 85, which I believe means error.
owread /28.B128F9040000/temperature 85 Checking the temperature from the /sys/bus/w1... is fine approx. 11, and changes with time which it should. owdir responds ok, lists the various directories, and if a owdir of the device is done, this responds with what I would expect from owfs I get tons of debug output, how is the best way of capturing it, is there a dump debug to file option hidden somewhere? John -----Original Message----- From: owfs-developers-requ...@lists.sourceforge.net [mailto:owfs-developers-requ...@lists.sourceforge.net] Sent: 27 April 2016 13:02 To: owfs-developers@lists.sourceforge.net Subject: Owfs-developers Digest, Vol 119, Issue 5 Send Owfs-developers mailing list submissions to owfs-developers@lists.sourceforge.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/owfs-developers or, via email, send a message with subject or body 'help' to owfs-developers-requ...@lists.sourceforge.net You can reach the person managing the list at owfs-developers-ow...@lists.sourceforge.net When replying, please edit your Subject line so it is more specific than "Re: Contents of Owfs-developers digest..." Today's Topics: 1. Raspberry pi Jessie, owfs-3.0.p2 not working with w1 driver correctly (John Bass) 2. Re: Raspberry pi Jessie, owfs-3.0.p2 not working with w1 driver correctly (Tomasz Torcz) ---------------------------------------------------------------------- Message: 1 Date: Wed, 27 Apr 2016 09:19:43 +0100 From: John Bass <j...@johnbass.co.uk> Subject: [Owfs-developers] Raspberry pi Jessie, owfs-3.0.p2 not working with w1 driver correctly To: owfs-developers@lists.sourceforge.net <owfs-developers@lists.sourceforge.net> Message-ID: <zarafa.5720761f.3534.20e6911f1c555c6e@mailhost.citadel.local> Content-Type: text/plain; charset="windows-1252" Hello, ? Raspberry pi B+ running Jessie, fully updated and rpi-upated.. ? I have the basic w1 kernel driver working fine, with a DS18B20 sensor. I can read the temperature just fine. ? However not so with the owserver.. If I run the owserver up in? one shell, owserver ?w1 ?debug, and then kick off owdir in another, I do not get a full directory listing. ? It takes ages to come back? see partial debug output below ? John ? ? DEBUG: ow_w1_dispatch.c:(91) Netlink message directed to W1 bus master 1 ? DEBUG: ow_w1_dispatch.c:(148) Sending this packet to w1_bus_master1 ? DEBUG: ow_w1_dispatch.c:(172) Dispatch loop ? DEBUG: ow_w1_parse.c:(112) Wait to peek at message ? DEBUG: ow_w1_parse.c:(229) Loop waiting for netlink piped message ? DEBUG: ow_w1_parse.c:(162) Pipe header: len=60 type=3 seq=1|1 pid=0 ??DEBUG: ow_w1_parse.c:(195) Pipe read -------------------- NLMSGHDR: len=60 type=3 (NLMSG_DONE) flags=0 seq=1|1 pid=0 CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=1|1 ack=65538 len=24 flags=0 W1_NETLINK_MSG: type=4 (W1_MASTER_CMD) len=12 id=1 W1_NETLINK_CMD: cmd=2 (W1_CMD_SEARCH) len=8 Byte buffer Data, length=8 --000: 28 B1 28 F9 04 00 00 94 ?? <(.(.....> ? DEBUG: ow_w1_parse.c:(249) About to call nrs_callback ? DEBUG: ow_w1_parse.c:(251) Called nrs_callback? DEBUG: ow_w1_parse.c:(120) Pre-parse header: 16 bytes len=52 type=3 seq=1|1 pid=0 ? DEBUG: ow_w1_parse.c:(141) Netlink read ----------------- NLMSGHDR: len=52 type=3 (NLMSG_DONE) flags=0 seq=1|1 pid=0 CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=1|1 ack=65537 len=16 flags=0 W1_NETLINK_MSG: type=4 (W1_MASTER_CMD) len=4 id=1 W1_NETLINK_CMD: cmd=2 (W1_CMD_SEARCH) len=0 NULL data ? DEBUG: ow_w1_dispatch.c:(91) Netlink message directed to W1 bus master 1 ? DEBUG: ow_w1_dispatch.c:(148) Sending this packet to w1_bus_master1 ? DEBUG: ow_w1_dispatch.c:(172) Dispatch loop ? DEBUG: ow_w1_parse.c:(112) Wait to peek at message ? ? DEBUG: ow_w1_parse.c:(229) Loop waiting for netlink piped message ? DEBUG: ow_w1_parse.c:(162) Pipe header: len=52 type=3 seq=1|1 pid=0 ??DEBUG: ow_w1_parse.c:(195) Pipe read -------------------- NLMSGHDR: len=52 type=3 (NLMSG_DONE) flags=0 seq=1|1 pid=0 CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=1|1 ack=65537 len=16 flags=0 W1_NETLINK_MSG: type=4 (W1_MASTER_CMD) len=4 id=1 W1_NETLINK_CMD: cmd=2 (W1_CMD_SEARCH) len=0 NULL data ? DEBUG: ow_w1_parse.c:(249) About to call nrs_callback ? DEBUG: ow_w1_parse.c:(251) Called nrs_callback ? DEBUG: loop.c:(109) Taking too long, send a keep-alive pulse ? DEBUG: to_client.c:(76) payload=-1 size=0, ret=0, sg=0x0 offset=0 ??DEBUG: to_client.c:(83) Send delay message (ping) ? DEBUG: loop.c:(109) Taking too long, send a keep-alive pulse ? DEBUG: to_client.c:(76) payload=-1 size=0, ret=0, sg=0x0 offset=0 -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 2 Date: Wed, 27 Apr 2016 10:27:26 +0200 From: Tomasz Torcz <to...@pipebreaker.pl> Subject: Re: [Owfs-developers] Raspberry pi Jessie, owfs-3.0.p2 not working with w1 driver correctly To: owfs-developers@lists.sourceforge.net Message-ID: <20160427082726.ga332...@mother.pipebreaker.pl> Content-Type: text/plain; charset=utf-8 On Wed, Apr 27, 2016 at 09:19:43AM +0100, John Bass wrote: > Hello, > > ? > Raspberry pi B+ running Jessie, fully updated and rpi-upated.. > > ? > I have the basic w1 kernel driver working fine, with a DS18B20 sensor. I can > read the temperature just fine. > > ? > However not so with the owserver.. If I run the owserver up in? one shell, > owserver ?w1 ?debug, and then kick off owdir in another, I do not get a full > directory listing. > > ? > It takes ages to come back? see partial debug output below For w1 to work you need this patch: https://sourceforge.net/p/owfs/code/ci/11325b6674a255a9797a1096e89870572ecf4db8/ It is included in 3.1p1. Ask You distribution to backport this patch or update owfs to newer version. -- Tomasz Torcz ,,If you try to upissue this patchset I shall be seeking xmpp: zdzich...@chrome.pl an IP-routable hand grenade.'' -- Andrew Morton (LKML) ------------------------------ ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z ------------------------------ _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers End of Owfs-developers Digest, Vol 119, Issue 5 *********************************************** ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
