Re: [Owfs-developers] Bug hunting (Re: 3.1p1 release, anyone?)

On 27.11.2015 00:19, Matthias Urlichs wrote: > Time for an interesting special effect: Problem solved. Not a bug. I increased the voltage to the 'Pi (from 4.95 to 5.2). No more strange errors. -- -- Matthias Urlichs -

Re: [Owfs-developers] Bug hunting (Re: 3.1p1 release, anyone?)

Am 28.11.2015 um 09:36 schrieb Matthias Urlichs: > On 27.11.2015 18:08, Jan Kandziora wrote: >> It's perfectly okay you may only see a single chip when listing a cached >> directory. > > Not if the chip never was at that bus position in the first place. > That's why I'd asked about turning the D

Re: [Owfs-developers] Bug hunting (Re: 3.1p1 release, anyone?)

On 27.11.2015 18:08, Jan Kandziora wrote: > It's perfectly okay you may only see a single chip when listing a cached > directory. Not if the chip never was at that bus position in the first place. > > Did you write a "branch" node of DS2409s before restarting owserver, > then listing any direct

Re: [Owfs-developers] Bug hunting (Re: 3.1p1 release, anyone?)

Am 27.11.2015 um 11:56 schrieb Matthias Urlichs: > On 27.11.2015 00:41, Jan Kandziora wrote: >> Matthias, always read "uncached" instead of the root dir when >> investigating such things. The cache makes bus listing results a bit >> unpredictable. > > I know. In this case that does not matter howe

Re: [Owfs-developers] Bug hunting (Re: 3.1p1 release, anyone?)

On 27.11.2015 00:41, Jan Kandziora wrote: > Matthias, always read "uncached" instead of the root dir when > investigating such things. The cache makes bus listing results a bit > unpredictable. I know. In this case that does not matter however, since to me there's a clear difference between "a bit

Re: [Owfs-developers] Bug hunting (Re: 3.1p1 release, anyone?)

Am 27.11.2015 um 00:19 schrieb Matthias Urlichs: > On 25.11.2015 03:16, Matthias Urlichs wrote: >> On 25.11.2015 00:42, Stefano Miccoli wrote: >>> are you sure that owserver is *really* dead? >> Of course I am. >> >> I'll try to investigate more, the next time that happens. >> Shouldn't be too long

[Owfs-developers] Bug hunting (Re: 3.1p1 release, anyone?)

On 25.11.2015 03:16, Matthias Urlichs wrote: > On 25.11.2015 00:42, Stefano Miccoli wrote: >> are you sure that owserver is *really* dead? > Of course I am. > > I'll try to investigate more, the next time that happens. > Shouldn't be too long. :-/ > > Time for an interesting special effect: roo

[Owfs-developers] Bug in EDS0065 support

The code for the EDS0065 has the wrong data type for the humidity_hi and humidity_low thresholds (i8 instead of float8) . I copied the types used for the EDS0068 and everything works perfectly. Before the change the values weren’t writable - they would revert to zero. Setting the value directly

Re: [Owfs-developers] Bug: owfs crashes when browsing the the folder with dolphin

Sorry. Known bug in 2.9p7 with owfs. Fixed and new release later today. Paul On Oct 18, 2014 6:07 AM, "Thomas Zimmermann" wrote: > Hi, > I'm currently packaging owfs for openSUSE and got a bug report that in the > package with systemd enabled owfs crashes as soon as one browses the > /run/owfs >

[Owfs-developers] Bug: owfs crashes when browsing the the folder with dolphin

Hi, I'm currently packaging owfs for openSUSE and got a bug report that in the package with systemd enabled owfs crashes as soon as one browses the /run/owfs folder with dolphin (KDE file manager). Browsing the folder with ls works just fine. To reproduce this I started owfs with the following p

[Owfs-developers] bug in owlib/src/c/ow_net_server.c

Hi,commit 2e36ac0ecefb45ff4b741a9afe4d33a40025e346Author: Paul Alfille Date:   Tue Aug 26 15:23:36 2014 -0400    Coverity changes        Not sure if these are really issues, but making changes for Coverity    scanning error.The above commit introduces a Coverity induced bug!

Re: [Owfs-developers] BUG: owtcl does useless UTF-8 mangling when returning binary data

Am 12.08.2013 22:09, schrieb Jan Kandziora: > Hi Serg, Paul, all > > I found another problem with owtcl's returning binary data. As soon the > result form owlib contains a 0xc8, the input is wrongly treated as > UTF-8. I made a patch similar to that of ow::put. > > If you think it's ok I will com

[Owfs-developers] BUG: owtcl does useless UTF-8 mangling when returning binary data

Hi Serg, Paul, all I found another problem with owtcl's returning binary data. As soon the result form owlib contains a 0xc8, the input is wrongly treated as UTF-8. I made a patch similar to that of ow::put. If you think it's ok I will commit it. Kind regards Jan Index: ow.c

Re: [Owfs-developers] BUG: owtcl treats all results as C strings; patch included

Am 23.06.2013 17:55, schrieb Jan Kandziora: > Hi, > > while playing with Pascal Baerten's BAE0911, I found owtcl is treating > all results from OW_get as C strings, which makes reading data with > embedded \0 chars impossible. > > I made I minimal patch which uses the length information of OW_get

Re: [Owfs-developers] BUG: owtcl treats all results as C strings; patch included

Am 23.06.2013 17:55, schrieb Jan Kandziora: > Hi, > > while playing with Pascal Baerten's BAE0911, I found owtcl is treating > all results from OW_get as C strings, which makes reading data with > embedded \0 chars impossible. > > I made I minimal patch which uses the length information of OW_get

Re: [Owfs-developers] BUG: owtcl does bogus UTF mangling on "ow put"; patch included

Am 26.06.2013 18:01, schrieb Paul Alfille: > Looks good. And you are right. The distinction between text and binary > isn't properly maintained in OWFS -- and probably shouldn't be. The 1-wire > slaves really only use binary strings. > > I'll add the patch. > Thanks! Don't forget the other one fr

Re: [Owfs-developers] BUG: owtcl does bogus UTF mangling on "ow put"; patch included

Looks good. And you are right. The distinction between text and binary isn't properly maintained in OWFS -- and probably shouldn't be. The 1-wire slaves really only use binary strings. I'll add the patch. Paul On Wed, Jun 26, 2013 at 9:05 AM, Jan Kandziora wrote: > Am 23.06.2013 22:52, schrie

Re: [Owfs-developers] BUG: owtcl does bogus UTF mangling on "ow put"; patch included

Am 23.06.2013 22:52, schrieb Jan Kandziora: > Hello, > > I found another bug in owtcl. > > Tcl does UTF mangling on the result of Tcl_GetStringFromObj. This is > very disturbing for the value of a "put" operation as there is no way to > output binary data to owfs as it is possible with owfs/fuse

[Owfs-developers] BUG: owtcl does bogus UTF mangling on "ow put"; patch included

Hello, I found another bug in owtcl. Tcl does UTF mangling on the result of Tcl_GetStringFromObj. This is very disturbing for the value of a "put" operation as there is no way to output binary data to owfs as it is possible with owfs/fuse itself (and the other language bindings, I guess). As far

[Owfs-developers] BUG: owtcl treats all results as C strings; patch included

Hi, while playing with Pascal Baerten's BAE0911, I found owtcl is treating all results from OW_get as C strings, which makes reading data with embedded \0 chars impossible. I made I minimal patch which uses the length information of OW_get instead. Works for me. Comments? cvs diff -u module/owt

Re: [Owfs-developers] Bug in DS2413 sensed.*

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Getting back on this, this is really odd: With 2.8p14 on i386: -> All fine on MIPS24k (OpenWRT) only sensed.BYTE shows up correctly, sensed.ALL/A/B is always 0 Maybe somebody can dis/confirm this on a similar platform.. Maybe some nasty endianess-is

Re: [Owfs-developers] [BUG] DS2408 set alarm is broken again?

Debug log from owserver is provided below: Both owserver and owfs are 2.8p14 versions. owserver run on arm linux machine and owfs on x86 linux machine. I don't have a fuse module on arm, so can't test it on the same machine right now. Any help with this is highly appreciated. cat 2 > set

Re: [Owfs-developers] Bug in 2.8p13?

ft232 + ds2480b is very good, i´m using about 30 devices in a ethernet network with a ser2net rfc2217, or with many owhttpd servers, both solutions works Em 1 de abril de 2012 16:13, Mick Sulley escreveu: > Hi Patryk, > > Yes I would be very interested to see your design, I don't think that my

[Owfs-developers] [BUG] DS2408 set alarm is broken again?

Hello, Setting alarms for DS2408 seems to be broken again: wget -qO - http://owhttpd.host/json/alarm/29.79400800/set_alarm/?set_alarm=3 set_alarm3 wget -qO - http://owhttpd.host/json/alarm/29.79400800/set_alarm/?set_alarm=3 set_alarm30008 There ware s

Re: [Owfs-developers] Bug in 2.8p13?

Hi Patryk, Yes I would be very interested to see your design, I don't think that my electronic are the same standard as yours, but I may give it a try. Thanks Mick On 01/04/12 18:54, Patryk wrote: > Dnia 01.04.2012 o 16:45 Mick Sulley Mick Sulley > napisał(a): > >> OK so it seems that DS9490

Re: [Owfs-developers] Bug in 2.8p13?

Dnia 01.04.2012 o 16:45 Mick Sulley Mick Sulley napisał(a): > OK so it seems that DS9490 is not a good device to use (after I just > bought a new one!). What do people recommend then? I have recently had > two DS9097U serial adapters fail, which is why I changed to the DS9490. I plan to bui

Re: [Owfs-developers] Bug in 2.8p13?

OK so it seems that DS9490 is not a good device to use (after I just bought a new one!). What do people recommend then? I have recently had two DS9097U serial adapters fail, which is why I changed to the DS9490. Regards Mick On 01/04/12 11:00, Matthias Lemke wrote: > I agree with Michael. I h

Re: [Owfs-developers] Bug in 2.8p13?

I agree with Michael. I have 3 busmaster with 26 sensors and a lot of recovery/reset operations on the busses with recent owfs. regards Am 01.04.2012 01:44, schrieb Michael Markstaller: > Well, yes, confirmed somehow -though its just a matter of side-effects > here.. > (But there are really wor

Re: [Owfs-developers] Bug in 2.8p13?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, yes, confirmed somehow -though its just a matter of side-effects here.. (But there are really worse things with DS9490 currently in owfs making it unusable :() Michael Am 31.03.2012 11:27, schrieb Mick Sulley: > Can anyone confirm if this is a

Re: [Owfs-developers] Bug in 2.8p13?

Can anyone confirm if this is a bug, or is it just not possible to change settings on a DS9490R? Thanks Mick On 28/03/12 19:35, Mick Sulley wrote: > It is not just with owhttpd, if I try > echo '10'>volatile > I get > bash: echo: write error: No such device > or > owwrite 10 volatile > no error

Re: [Owfs-developers] Bug in 2.8p13?

It is not just with owhttpd, if I try echo '10'>volatile I get bash: echo: write error: No such device or owwrite 10 volatile no error but cat volatile returns 15 There does not seem to be any way to change the setting. Are there any other ways to do this? Mick On 28/03/12 17:09, Roberto Spadi

Re: [Owfs-developers] Bug in 2.8p13?

i think theres a bug in http requests inside owhttp, i don´t know if anyone is working on it, but i think it´s know Em 28 de março de 2012 06:28, Mick Sulley escreveu: > Is there a bug in 2.8p13? > > I have a DS9490R USB adapter and cannot change any of the settings.  I > have tried all of the ti

[Owfs-developers] Bug in 2.8p13?

Is there a bug in 2.8p13? I have a DS9490R USB adapter and cannot change any of the settings. I have tried all of the timeout settings and the unit settings, changing via the webpage. Anything I change immediately goes back to the default value. I did wonder if my adapter was faulty so I bou

Re: [Owfs-developers] [BUG] templow/temphigh negative setting

Thank you for your reply, I have checked datasheet. Shame on me, that I didn't this before asking. Also, I think that json and text outputs are mixed up: $ wget -qO - http://owhttpd.host/json/12.9D198200/PIO.A PIO.A 1 This is obviously text $ wget -qO - http://owhttpd.host/text/12.9D1982000

Re: [Owfs-developers] [BUG] templow/temphigh negative setting

Found the bug -- the value was being cast to uint8_8 instead of int8_t -- fixed in next release. On Tue, Mar 27, 2012 at 3:37 AM, Ivan Lisenkov wrote: > Hello, > > I'm running owhttpd vesion 2.8p14. There is a bug, so it is not possible > to set negative alarm values for DS18B20 sensors. > > $wg

Re: [Owfs-developers] [BUG] templow/temphigh negative setting

Thank you for the bug report. I'll check the code. The temperature alarm values should be handled as type "temperature" internally, and thus subject to conversion of temperature scale. As to float -- the temperature limits on the chip are only 1 byte long each, and have a resolution of 1 degree c

[Owfs-developers] [BUG] templow/temphigh negative setting

Hello, I'm running owhttpd vesion 2.8p14. There is a bug, so it is not possible to set negative alarm values for DS18B20 sensors. $wget -qO - --no-proxy http://owhttpd.host/json/28.1E925703/templow?templow=5 templow5 ok, no problem! $wget -qO - --no-proxy http://owhttpd.host/jso

[Owfs-developers] Bug in DS2413 sensed.*

Just noticed one thing in 2.8p14 (also 2.8p8): DS2413 used as input, sensed.BYTE is fine but sensed.ALL & .A/.B shows always 0 This used to work fine back with 2.8p2 best regards Michael -- Try before you buy = See our

Re: [Owfs-developers] Bug#660857: owfs: FTBFS(kfreebsd): libow.so: undefined reference to `w1_bind'

[resubmit with a good from: for the OWFS ML] Hi Paul, There has been a debian bug report ( http://bugs.debian.org/660857 ) about failure during compilation on kfreebsd (see at the end of this mail). I think that the problem is that ow_com_open.c, at lines 53, calls w1_bind without checking

[Owfs-developers] Bug on owfs-2.8p13 or dummy user ;-) ?

Hi all, First i want to say thank you for this great project. i did my house bus with owfs with a small linux "alix 1d" pc runing Ubuntu 10.04.2 LTS on it. Yesterday i have tested the brand new owfs 2.8p13 with a USB DS9490R adapter. Its working fine so far expect overdrive mode seems not worki

Re: [Owfs-developers] bug in DS2482 host adapter devices discovery

You're welcome :) and thanks for fixing it so quickly ! On Mon, Jul 4, 2011 at 3:27 PM, Paul Alfille wrote: > Good pickup, Nicolas. Your detailed analysis made the problem obvious! > > That "anydevices_no" is set whenever the DS2482 undergoes a 1-wire reset. > It senses if there is a presence pu

Re: [Owfs-developers] bug in DS2482 host adapter devices discovery

Good pickup, Nicolas. Your detailed analysis made the problem obvious! That "anydevices_no" is set whenever the DS2482 undergoes a 1-wire reset. It senses if there is a presence pulse. In this case, the test was made before the reset -- leaving the bus is the "no device, so no reset needed state.

[Owfs-developers] bug in DS2482 host adapter devices discovery

Hello, I'm using owserver with a DS2482 host adapter (i2c <-> 1wire chip), and found an issue which prevent one-wire devices to be discovered. I'm using owfs 2.8p10, and the iButton devices are simple DS1990 id buttons. To reproduce it : 1. launch the server (owserver --foreground --i2c=/dev/i2

Re: [Owfs-developers] Bug (?) in re init()'ing Python ow module.

On Thursday 18 November 2010, Paul Alfille elucidated thus: > On Mon, Nov 1, 2010 at 6:29 PM, Joshua J. Kugler wrote: > > Is the C API not fulling cleaning up when _OW.finish( ) is called? > > Is there something I should be aware of? > It's possible that finish doesn't clear everything. I don't

Re: [Owfs-developers] Bug (?) in re init()'ing Python ow module.

It's possible that finish doesn't clear everything. I don't understand the error message, however. On Mon, Nov 1, 2010 at 6:29 PM, Joshua J. Kugler wrote: > Is the C API not fulling cleaning up when _OW.finish( ) is called?  Is > there something I should be aware of?

Re: [Owfs-developers] Bug (?) in re init()'ing Python ow module.

Bump...anyone ever hit this problem? In production, it's not a big deal right now, but a working ow.finish() would be nice for unit testing. j On Monday 01 November 2010, Joshua J. Kugler elucidated thus: > Given the following code: > > import sys > import ow > > > def tree( sensor ): > pri

Re: [Owfs-developers] Bug in memory read

Thanks! OWFS has always been a central part of our research, and this patch helps greatly! --Jim On Mon, Nov 1, 2010 at 7:16 PM, Paul Alfille wrote: > Thank you for making this easily tested demonstration. > > The bug seems to be in large (>64 byte) reads with the USB adapter, > and is now fixe

Re: [Owfs-developers] Bug in memory read

Thank you for making this easily tested demonstration. The bug seems to be in large (>64 byte) reads with the USB adapter, and is now fixed. pages.ALL actually read each 32 byte page and concatenated them, so didn't fail. Paul Alfille On Mon, Nov 1, 2010 at 6:56 PM, Jim Kusznir wrote: > Hi all:

[Owfs-developers] Bug in memory read

Hi all: I reported a problem a while ago with strange memory reads coming out on the DS2406. We have conducted more tests in my lab, and have more information. First, the problem: When one reads "memory" on a DS2406 since the 2.8pX series (all released patch levels so far), the first 1-2 chara

[Owfs-developers] Bug (?) in re init()'ing Python ow module.

Given the following code: import sys import ow def tree( sensor ): print '%7s - %s' % ( sensor._type, sensor._path ) for next in sensor.sensors( ): if next._type in [ 'DS2409', ]: tree( next ) else: print '%7s - %s' % ( next._type, next._path ) i

Re: [Owfs-developers] bug in owpython ...

Oh, sorry, i missed the most important part: owfs-2.8p2 on gentoo 2.6.24.7, python 2.5.4 ... but i doubt it makes a difference ... ;) regards, marcus. -- Start uncovering the many advantages of virtual appliances and

[Owfs-developers] bug in owpython ...

Hi Guys, i just found one ;) - at least i think the behaviour should be different ... i have a system with either ds2490 or LinkUSB ... so i want autoprobing (ds2490 missing, LinkUSB plugged in): >>> import ow >>> ow.init ("u") Traceback (most recent call last): File "", line 1, in File

Re: [Owfs-developers] bug in ds2780 (ow_ds2760) code, plus patch

ginal Message - From: "Paul Alfille" To: "OWFS (One-wire file system) discussion and help" Sent: Wednesday, January 20, 2010 3:52:12 AM GMT -08:00 US/Canada Pacific Subject: Re: [Owfs-developers] bug in ds2780 (ow_ds2760) code, plus patch Wonderful, I'll apply t

Re: [Owfs-developers] bug in ds2780 (ow_ds2760) code, plus patch

Wonderful, I'll apply the patch. I think you are the first to report on using OWFS with the DS2780. By the way, if you have a picture or schematic of your thermocouple, I'd like to post it on the website. Paul Alfille On Wed, Jan 20, 2010 at 1:20 AM, wrote: > Hi folks, > > I was able to find a

[Owfs-developers] bug in ds2780 (ow_ds2760) code, plus patch

Hi folks, I was able to find a DS2780 on eBay, and decided to have a go at making my own thermocouple reader. great fun. Anyhow, after soldering the tiny TSSOP onto a breakout board, i was afraid i'd zapped it! The temperature reading was constantly 0. Other functions worked, voltage, PIO,

Re: [Owfs-developers] Bug report?

Hi, Rob Fugina: > On Sat, May 30, 2009 at 08:47, Paul Alfille wrote: > > Should that be part of "bootstrap"? > > Perhaps... Someone that's using the code from CVS is assumed to have > autoconf, automake, autoheader... If it's also assumed that they have > libtool, and if libtoolize should be r

Re: [Owfs-developers] Bug report?

On Sat, May 30, 2009 at 10:42, Matthias Urlichs wrote: > Hi, > > Rob Fugina: >> one can see that the 1-wire bus master is being repeatedly >> reset for some reason. > > The master itself, or just the bus? > > Bus resets are a normal part of the protocol. If I had only seen a couple, I wouldn't ha

Re: [Owfs-developers] Bug report?

On Sat, May 30, 2009 at 08:47, Paul Alfille wrote: > Should that be part of "bootstrap"? Perhaps... Someone that's using the code from CVS is assumed to have autoconf, automake, autoheader... If it's also assumed that they have libtool, and if libtoolize should be run before the others, than i

Re: [Owfs-developers] Bug report?

Hi, Rob Fugina: > one can see that the 1-wire bus master is being repeatedly > reset for some reason. The master itself, or just the bus? Bus resets are a normal part of the protocol. -- Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [email protected] Disclaimer: The quote was sele

Re: [Owfs-developers] Bug report?

rce install flags) > ./bootstrap ; ./configure ; make all install > > > > -Original Message- > From: Paul Alfille [mailto:[email protected]] > Sent: den 30 maj 2009 00:11 > To: [email protected] > Subject: Re: [Owfs-developers] Bug repo

Re: [Owfs-developers] Bug report?

l.com] Sent: den 30 maj 2009 00:11 To: [email protected] Subject: Re: [Owfs-developers] Bug report? Yes, I've has the same problem with the hateful libtool. If ever an example of awkward "design" and unmaintainable code... Anyways, Christian Magnuss

Re: [Owfs-developers] Bug report?

Yes, I've has the same problem with the hateful libtool. If ever an example of awkward "design" and unmaintainable code... Anyways, Christian Magnusson came to my rescue: - I have seen this on Ubuntu 8.10 as well... Copy your local libtool to the installation directory

Re: [Owfs-developers] Bug report?

I have not been able to build successfully from CVS. It seems to me to have something to do with libtool, as the build goes fine (running bootstrap, configure, and make) until libtool gets invoked, and then: /bin/bash ../../../../libtool --tag=CC --mode=link gcc -I../include -I../../../owlib/sr

Re: [Owfs-developers] Bug report?

Yes, the fixes may be after that release. http://www.ohloh.net/p/8713/commits?page=3 On 5/20/09, Rob Fugina wrote: > > On Wed, May 20, 2009 at 15:29, Paul Alfille > wrote: > > Are you using the new code on both machines? And are you certain the new > > library is actually loaded (any owfs proces

Re: [Owfs-developers] Bug report?

On Wed, May 20, 2009 at 15:29, Paul Alfille wrote: > Are you using the new code on both machines? And are you certain the new > library is actually loaded (any owfs process that uses that library (owfs, > owhttpd, owserver) can keep the libow in memory. Yes, I updated to p21 on both machines, and

Re: [Owfs-developers] Bug report?

Are you using the new code on both machines? And are you certain the new library is actually loaded (any owfs process that uses that library (owfs, owhttpd, owserver) can keep the libow in memory. If not, I'll try the same test over a network with 2 machines and see if that is the problem. Seems d

Re: [Owfs-developers] Bug report?

I tried it earlier today with p21, and it produced the same result, but I haven't pulled bleeding-edge code from svn yet (or is it CVS?). I'll try to do that soon to confirm it for you. Rob -- Crystal Reports - New Free R

Re: [Owfs-developers] Bug report?

I think it's fixed. I tried your scenario (on one machine however, with a different second port) and get: > /opt/owfs/bin/owdir -s 4305 /10.67C6697351FF /26.4AEC29CDBAAB /28.F2FBE3467CC2 /2C.66FE0400 /2C.1B79 /22.367A0300 /12.C4DF1F00 /01.5F50CA09 /81.6B1B2400 /89.BD29C

[Owfs-developers] Bug report?

This is from 2.7p19, so I apologize if it's been fixed since then... This involves two owserver instances, one of which is referencing and aggregating the other. So, two boxes. The host "slug" is running "owserver -p 4304 --fake=10,26,28" plus some debugging options. The host "troll" is running

Re: [Owfs-developers] BUG: read /alarm

juni 2008 17:06 To: [email protected] Subject: [Owfs-developers] BUG: read /alarm Hi, I found such a mistake: $ tclsh % package require ow; % ::OW::init -s 3000 % ::OW::get /alarm 28.2CCD8000/,28.86BF8000/ % # ...Clear all alarms... % ::OW::get /alarm I/O error %

[Owfs-developers] BUG: read /alarm

Hi, I found such a mistake: $ tclsh % package require ow; % ::OW::init -s 3000 % ::OW::get /alarm 28.2CCD8000/,28.86BF8000/ % # ...Clear all alarms... % ::OW::get /alarm I/O error % Similar for perl: $ perl use OW ; OW::init("-s 3000"); my $res = OW::get("/alarm") or die; print "$res\n

Re: [Owfs-developers] Bug posted in Gentoo bugzilla

I'll give that a try and ask Mr. Glaser if he can test it too, and I'll post back with the results. On 8/8/07, Paul Alfille <[EMAIL PROTECTED]> wrote: > > Maybe a sed script in the makefile? owfs/module/swig/php/Makefile.am has > ow_wrap.c as a target. > > Paul Alfille > > On 8/8/07, Ben Griffith

Re: [Owfs-developers] Bug posted in Gentoo bugzilla

Maybe a sed script in the makefile? owfs/module/swig/php/Makefile.am has ow_wrap.c as a target. Paul Alfille On 8/8/07, Ben Griffith <[EMAIL PROTECTED]> wrote: > > Hi Paul, > > I think he was talking about applying the patch to ow_wrap.c, which is > generated by SWIG, which is affected by the PHP

Re: [Owfs-developers] Bug posted in Gentoo bugzilla

Hi Paul, I think he was talking about applying the patch to ow_wrap.c, which is generated by SWIG, which is affected by the PHP issue. (Do I have that right?) I did find the line in ow_wrap.c where zend_rsrc_list_get_rsrc_type is called with only one argument instead of two, and that area of the

Re: [Owfs-developers] Bug posted in Gentoo bugzilla

On 8/7/07, Ben Griffith <[EMAIL PROTECTED]> wrote: > > Someone just posted a problem they found while compiling owfs on Gentoo > with thread safety enabled. Apparently it's a known issue with swig and > they included a link to a patch. > Thank you Ben. Apparently this is a PHP issue and the patc

[Owfs-developers] Bug posted in Gentoo bugzilla

Someone just posted a problem they found while compiling owfs on Gentoo with thread safety enabled. Apparently it's a known issue with swig and they included a link to a patch. Here's the text of their entry: --- *Comment #7 >From Daniel Glas

[Owfs-developers] Bug in ownet for python?

Hi all. I found out that it does not work to set the host and port in the call to ownet.init() as in the following below. import ownet ownet.init('sid:') a = ownet.Sensor('10BCC4C8000800') print a.temperature ownet.finish() But after changing line 149 in _init_.py from self._connection = Co

Re: [Owfs-developers] Bug in ownet (python) with DS2409 ?

Thank you. In Peter's absence, I've applied your changes. The annotations are wonderful. I'd have included them in the source code if I were sure of the syntax. Patches are welcome in any format. The better explained, the better. It's also nice when the match the general coding style, but it's n

Re: [Owfs-developers] Bug in ownet (python) with DS2409 ?

Hi - I've been exercising some changes to the ownet python interface, and everything seems to be working great. The changes were made because the existing code had trouble working through a 1-wire hub or DS2409 microlan switch. I've been running with these changes for almost a week with no

Re: [Owfs-developers] Bug in ownet (python) with DS2409 ?

Hi Peter - Your change does improve things. 'list' no longer includes the entire contents of the 'directory' but only the subdirectories as desired. However 'list' is still a list, cannot be split, and the same error occurs. I figured out how to get around that by converting the list to a stri

Re: [Owfs-developers] Bug in ownet (python) with DS2409 ?

On 12/24/06, Peter Kropf <[EMAIL PROTECTED]> wrote: > On 12/23/06, ziggy <[EMAIL PROTECTED]> wrote: > > > > I'm trying to work with the recently released ownet python classes > > (ownet-0.2). This is on an unslung Slug (6.8) if it matters. I am running > > into a problem when trying to traverse a

Re: [Owfs-developers] Bug in ownet (python) with DS2409 ?

On 12/23/06, ziggy <[EMAIL PROTECTED]> wrote: > > I'm trying to work with the recently released ownet python classes > (ownet-0.2). This is on an unslung Slug (6.8) if it matters. I am running > into a problem when trying to traverse a 2409 swtich. Now, part of the > problem may be that I learni

[Owfs-developers] Bug in ownet (python) with DS2409 ?

I'm trying to work with the recently released ownet python classes (ownet-0.2). This is on an unslung Slug (6.8) if it matters. I am running into a problem when trying to traverse a 2409 swtich. Now, part of the problem may be that I learning python at the same time, so please forgive me if I a

Re: [Owfs-developers] Bug in DS2409 code, patch included

I've applied the origical patch. As soon as we get the simultaneous/single and simultaneous/present stable, I'll make another release. Paul On 12/14/06, Jan Kandziora <[EMAIL PROTECTED]> wrote: Am Donnerstag, 14. Dezember 2006 23:52 schrieb Jan Kandziora: > Ahhh, forget the previous posting

Re: [Owfs-developers] Bug in DS2409 code, patch included

Am Donnerstag, 14. Dezember 2006 23:52 schrieb Jan Kandziora: > Am Donnerstag, 14. Dezember 2006 22:29 schrieb Paul Alfille: > > Jan, > > > > Thank you very much! > > I think I found another occurrence of this bug. As the discharge lines > command is not really needed for branch turnoff, I left it

Re: [Owfs-developers] Bug in DS2409 code, patch included

Am Donnerstag, 14. Dezember 2006 22:29 schrieb Paul Alfille: > Jan, > > Thank you very much! > I think I found another occurrence of this bug. As the discharge lines command is not really needed for branch turnoff, I left it out. diff -Naur owfs.orig/module/owlib/src/c/ow_select.c owfs/module/

Re: [Owfs-developers] Bug in DS2409 code, patch included

Jan, Thank you very much! Paul Alfille On 12/14/06, Jan Kandziora <[EMAIL PROTECTED]> wrote: Hi All, Hi Paul I think I found a bug in the DS2409 code. According to the datasheet, the discharge lines command is 0x99, not 0xCC (that's Smart-On Main). Proposed patch: --- owfs.orig/module/owli

[Owfs-developers] Bug in DS2409 code, patch included

Hi All, Hi Paul I think I found a bug in the DS2409 code. According to the datasheet, the discharge lines command is 0x99, not 0xCC (that's Smart-On Main). Proposed patch: --- owfs.orig/module/owlib/src/c/ow_2409.c 2006-12-14 20:50:04.0 +0100 +++ owfs/module/owlib/src/c/ow_2409.c

Re: [Owfs-developers] bug...

ECTED] Behalf Of Christian Magnusson Sent: Friday, November 24, 2006 8:11 AM To: [email protected] Subject: [Owfs-developers] bug... Paul, I just found a bug... It's when owserver have two adapters, owfs will hang hard when browsing the bus-directories. It's in the

[Owfs-developers] bug...

Paul, I just found a bug. It's when owserver have two adapters, owfs will hang hard when browsing the bus-directories. It's in the ow_parsename.c CONNINLOCK which isn't released when it returns parse_error. We have to allow any "bus.x" when it comes from a remote-server. We can't compare i

Re: [Owfs-developers] bug

ill: [email protected] > Ämne: Re: [Owfs-developers] bug > > Actually, I probably could use some help. > How do I know which thread to map the error to? Will I also get a "write" > error and so can just ignore the sigpipe entirely? > > Paul Alfille > >

Re: [Owfs-developers] bug

5:45 AM To: [email protected] Subject: Re: [Owfs-developers] bug SIGPIPE should be ignored by owserver/owfs/owhttpd and not exit when this is received. It's basically a network problem when writing to the socket. The write request should of course return an error, but it

Re: [Owfs-developers] bug

[email protected] > Ämne: [Owfs-developers] bug > > > again the same backtrace: i think that's a problem to clone > >DEBUG: ReadHandler: cm->payload=0 cm->size=0 cm->offset=0 >DEBUG: ReadHandler: sm->payload=38 sm->size=12 sm->offset=0 &

[Owfs-developers] bug

again the same backtrace: i think that's a problem to clone DEBUG: ReadHandler: cm->payload=0 cm->size=0 cm->offset=0 DEBUG: ReadHandler: sm->payload=38 sm->size=12 sm->offset=0 DEBUG: READ_POSTPARSE /uncached/10.6F7EC9000800/temperature DEBUG: READ_POSTPOSTPARSE /uncached/10.6F7EC9

[Owfs-developers] bug

again the same backtrace: i think that's a problem to clone DEBUG: ReadHandler: cm->payload=0 cm->size=0 cm->offset=0 DEBUG: ReadHandler: sm->payload=38 sm->size=12 sm->offset=0 DEBUG: READ_POSTPARSE /uncached/10.6F7EC9000800/temperature DEBUG: READ_POSTPOSTPARSE /uncached/10.6F7EC9000800/

Re: [Owfs-developers] bug

ddelande- >> Från: [EMAIL PROTECTED] [mailto:owfs- >> [EMAIL PROTECTED] För Roberto Spadim >> Skickat: den 26 september 2006 04:51 >> Till: [email protected] >> Ämne: Re: [Owfs-developers] bug >> >> i can't execure the error co

Re: [Owfs-developers] bug

to Spadim > Skickat: den 26 september 2006 04:51 > Till: [email protected] > Ämne: Re: [Owfs-developers] bug > > i can't execure the error consistently > now i stoped and started owserver again and the error stoped, how could > i run gdb to get back

Re: [Owfs-developers] bug

the error occur when i set ds2405 PIO on or off i will try some tests with gdb and when i get backtrace i will send ;) Paul Alfille escreveu: > So you can generate this error intermittently? > That starts to sound like mutex locking issues. Have you found that > the temperature sensor is needed t

Re: [Owfs-developers] bug

So you can generate this error intermittently?That starts to sound like mutex locking issues. Have you found that the temperature sensor is needed to trigger the error, or is the DS2405 enough?Paul Alfille On 9/26/06, Roberto Spadim <[EMAIL PROTECTED]> wrote: the error occurs with --foreground too,

Re: [Owfs-developers] bug

the error occurs with --foreground too, can i run gdb and get backtrace?? Paul Alfille escreveu: > I've never had success with gdb and threaded programs. I just out > printf and run in foreground. > > On 9/25/06, *Roberto Spadim* < [EMAIL PROTECTED] > > wrote: > > i

  1   2   >