Jan Kandziora | 30 Apr 22:59 2016
Picon
Picon

Re: OWFS on Raspberry Pi 2 help

Am 28.04.2016 um 22:39 schrieb Juliean Galak:
> On Thu, Apr 28, 2016 at 4:20 PM, Jan Kandziora <jjj <at> gmx.de> wrote:
> 
>> Am 28.04.2016 um 19:53 schrieb Juliean Galak:
>>>
>>> Ok, I found owhttpd.init in that archive, in the rpm/src directory, and
>>> copied it to /etc/init.d/  I then rebooted. No apparent change - owhttpd
>>> doesn't seem to be running.
>>>
>> You have to activate the service. Installing that file should make the
>> "service" tool work as expected.
>
I've set up a Raspberry Pi (Pi1) with Raspbian and checked the packages
available in the Raspbian Testing repository. They are OK.

So: please remove all the owfs tools installed from source first. The copied
files, too

Then use the owfs packages from the Raspbian testing repository. Edit
(or create) your /etc/apt/preferences to contain:
--------------------------------------------------------------------------
Package: *
Pin: release o=Raspbian,a=stable
Pin-Priority: 500

Package: *
Pin: release o=Raspbian,a=testing
Pin-Priority: 300
--------------------------------------------------------------------------
This is important so you keep stable (Jessie) for all packages but the ones
(Continue reading)

Mick Sulley | 30 Apr 01:16 2016

Re: How to remove and start again?

Hi Colin,

Yes you are right, purged owserver and 2.9p8-6 is gone, just my newly 
installed 3.0.0 there now.

Lots of things went wrong today, tends to numb the brain a bit!

Thanks for your help
Mick

On 29/04/16 16:53, Colin Law wrote:
> On 29 April 2016 at 16:28, Mick Sulley <mick <at> sulley.info> wrote:
>> As I was getting desperate I delete ow* from /usr/bin and reinstalled 3.0.0
>> Just run your commands and I get -
>>
>> control <at> pi-solar:~ $ apt-cache policy owfs
>> owfs:
>>     Installed: (none)
>>     Candidate: 2.9p8-6
>>     Version table:
>>        2.9p8-6 0
>>           500 http://mirrordirector.raspbian.org/raspbian/ jessie/main
>> armhf Packages
>> control <at> pi-solar:~ $ apt-cache policy owserver
>> owserver:
>>     Installed: 2.9p8-6
>>     Candidate: 2.9p8-6
>>     Version table:
>>    *** 2.9p8-6 0
>>           500 http://mirrordirector.raspbian.org/raspbian/ jessie/main
(Continue reading)

John Bass | 29 Apr 18:36 2016
Picon

Raspberry Pi Jessie owfs-3.1.p1 w1-driver = 85c

Hello,

 

Well I have found why it’s happening. I conclude owfs is not handling passive devices correctly

 

So.. NOT in passive mode, i.e. all three legs of the temperature sensor connected, and a 4.7k pull up on the data line, Both /sys/bus/w1/DEVICE/temperature returns correct temperature. The same is true for owserver, when owread is run the correct temperature is returned.

 

Now… I rewire the temperature sensor to two wires, GND pin and VDD pin shorted to GND and the data pin with a 4.7k pullup to +3.3V.

 

So Passive mode,  /sys/bus/w1/DEVICE/temperature returns correct temperature, however owserver with owread return 85c, thus I would surmise that owserver is not handing passive devices correctly.

 

Also /boot/config.txt has the correct definition in it.

 

dtoverlay=w1-gpio,gpiopin=4,pullup=on

 

I ran the test several times, rebooting each time. I also rewired the same sensor each time!

 

John

------------------------------------------------------------------------------
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 <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Juliean Galak | 27 Apr 21:33 2016
Picon

OWFS on Raspberry Pi 2 help

If this isn't the right forum for this, I apologize, but I've been banging my head against this for months and can't seem to resolve it.

I'm trying to run OWFS over the w1 kernel module on a Raspberry Pi 2 running the 3.1 (Wheezy) kernel.  (I need to use the w1 module for compatibility with other programs, switching to another bus master isn't an option).

Debian's apt-get system installs version 2.8, which doesn't seem to work well with w1.  It was suggested to me that downloading and building 3.1 would resolve the issue.  I've done so, and it appears to have built successfully, but I can't figure out how to set it up to run as a service the way the version installed by apt-get runs.  There isn't an /etc/owfs.conf file, and it doesn't auto-start. 

Any help would be appreciated.  My previous problems trying to get version 2.8 to run can be seen here: http://raspberrypi.stackexchange.com/questions/37070/problems-with-owfs-over-the-w1-kernel-module

Thank you for any help,

--
Juliean Galak
jgalak <at> gmail.com
------------------------------------------------------------------------------
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 <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
John Bass | 27 Apr 10:19 2016
Picon

Raspberry pi Jessie, owfs-3.0.p2 not working with w1 driver correctly

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

------------------------------------------------------------------------------
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 <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Picon
Gravatar

Remove getaddrinfo compat implementation completely

 Hi all,

 When I posted a patch on the list to fix the compat handling of getaddrinfo,
the conclusion was that it would be better to get rid of the compat handling
of getaddrinfo completely. However my patch to do that didn't make it to the
list because it was too large. So my original patch got applied instead.

 Therefore, here is the patch to remove the compat handling of getaddrinfo
again. It is rebased on current master. This time I made it with the -D
option so it's a lot smaller.

 Regards,
 Arnout

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
Picon
Gravatar

Scan misses slaves when one disappears from the bus

 Hi all,

 We have a system where there are many iButton-type devices on a single
1-wire bus, and they are continuously connected to and disconnected from
the bus. We poll the owfs uncached directory to detect when an iButton
is connected.

 Now during stress testing we discovered that when a device is removed from
the bus, it sometimes happen that other devices (that are still connected)
also disappear. Further investigation turned up that the problem is caused
by the "1,1" condition on the bus when the search algorithm [1] is used.
This condition means "No devices participating in search". However, this is
not really true, because we can only get in that situation when there was
a device participating but it disappeared during the search.

 The attached patch solves this by erroring out in the "1,1" condition,
instead of considering the search finished. This corresponds to what
Maxim's application note [1] describes.

 If you all agree that this is the best way to approach it, you can apply
the patch in follow-up.

 Regards,
 Arnout

[1] https://www.maximintegrated.com/en/app-notes/index.mvp/id/187

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
Johan Ström | 24 Mar 16:12 2016
Picon

Unittests

Hi,

I just commited a very first unit-test, something which the codebase is
lacking today.
Also merged the fix for FS_input_ascii_array, and some other cleanups.

The test is built with libcheck, a pretty simple C unittest library.
It is by no means a decision on a lib to use, but it's a start.

To build, ensure libcheck is installed, re-run configure, and then make
all check.

For the moment there is only a single test case, for
FS_input_ascii_array (which was fixed through with help from this test).
owfs (and C in generall) is a kindof tricky to write tests for, but it
is doable.. at least for some parts..

Of course, this just tests an extremely small portion of the owfs
codebase, but in the future we can add more, especially when debugging
errors.

Johan

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
Colin Reese | 16 Mar 01:47 2016
Picon

DS9097E# External Supply

Hey all,

This is not an owfs-specific question, but more 1Wire hardware related. 

Using the DB25 connector connected to a serial port as here; 


Everything is fine until I plug in a 12V supply, at which time all devices disappear from the bus. The supply is one of those specifically recommended in the datasheet, and is putting out close enough to 12V center-ground. 

Anybody have any ideas why this would occur?

Thanks,
Colin
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Picon
Gravatar

[PATCH] owusbprobe: disable if !OW_USB

Commit 21a57564b removed the OW_USB condition in owusbprobe. This
causes the build to fail if libusb is not available or --disable-libusb
was given.

Therefore, re-insert the condition.

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout <at> mind.be>
Cc: Johan Ström <johan <at> stromnet.se>
---
 module/owshell/src/c/owusbprobe.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/module/owshell/src/c/owusbprobe.c b/module/owshell/src/c/owusbprobe.c
index 93a344e..5d72653 100644
--- a/module/owshell/src/c/owusbprobe.c
+++ b/module/owshell/src/c/owusbprobe.c
 <at>  <at>  -33,7 +33,7  <at>  <at> 

 #define log(msg, args...) fprintf(stdout, msg"\n", ##args)

-#if 1 || OW_USB
+#if OW_USB

 #if defined(__FreeBSD__)
 #define TTY_EXAMPLE "/dev/cuaUx"
--

-- 
2.7.0

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Andy Carter | 15 Mar 12:50 2016
Picon

Louis Swart LCD issues

I have had 1-wire devices set up and working successfully for some years but 
have problems with a new Louis Swart 20x4 LCD.

My setup is a Sheepwalk Electronics DS2482-800 i2c based RPI3 host adapter on 
a Raspberry Pi2 currently running raspbian jessie and default owfs-2.9p8. 
Logging/control is with fhem, a perl based home automation application.

Connecting the LCD to the bus correctly identifies it. 
I can send text strings to it but it misses the first character and adds || to 
the end eg. sending fred displays red||. 
In order to turn the backlight on I have to send two digits such as 11, a 
single 1 is ignored.

A net search reveals a few similar scattered reports but no solution as far as 
I can see.

I have set up another Pi with an earlier 26 pin version of the same host 
adapter.

A raspbian jessie install (owfs-2.9p8) shows the same as above - to be 
expected.

A raspbian wheezy install (default owfs-2.8p15) shows all characters sent 
correctly, with no trailing ||.

Replacing owfs-2.9p8 files with owfs-2.8p15 versions on jessie shows all 
characters sent correctly, with no trailing ||.

I have also tried armhf owfs-3.1p1-2 versions on jessie but that shows the 
same issues as owfs-2.9p8

I borrowed a perl script from elsewhere on this list, running it from an AMD 
jessie desktop to the Pi server produces the same results as above ie. 
owfs-2.8p15 OK, owfs-2.9p8 amd owfs-3.1p1-2 not OK.

I don't have any hardware to set up 1-wire on anything other than the Pi 
unfortunately.

Any thoughts on where I should go from here? 

TIA

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140

Gmane