Radoslav Chovan | 5 Feb 10:26 2016
Picon

Re: Can't compile OWFS for Windows cygwin/mingw

Hi, thank you. 
With you help I was able successfully compiled owfs on Cygwin 64bit. 
Could you please update source of SF.NET with this patch and modifications ? 

Thank You.


2016-02-04 21:17 GMT+01:00 Jan Kandziora <jjj <at> gmx.de>:
Am 03.02.2016 um 21:17 schrieb Coudy:
> Ok,
> I didi make clean and then make, but it stop on same error
>
No. Now it's compat.o again and I'm missing -D__BSD_VISIBLE=1 in the
above run.

Please apply the appended patch against the ./configure I sent you

[owfs-3.1p1]$ patch <owfs_cygwin_configure.patch

then re-run ./configure, then make. Sorry this is a bit tedious.



Kind regards

        Jan

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Timo Engel | 4 Feb 14:06 2016
Picon

read/write EEPROM


Hello,

I'm using owfs to read/write the EEPROM of DS2436 and DS2433 devices.
Mostly, this works nice and without problems. However, sometimes wrong
data is stored on the EEPROM.

I'm wondering what is the correct procedure to read/write form/to an
EEPROM. Is it sufficient to use write() and write 32 bytes for example
to pages/page.0? Are there any status information if the last write()
was successful? Is owfs doing any checks of CRC and sends messages
again to the device or do I have to implement this on my own?

It would be nice to verify the written data by reading them back, but
it seems to be useless because of the caching mechanism of owfs. I
know about the "uncached" directory, but reading from there makes owfs
stop working.

I can imagine the communication will be more reliable if it is slower.
I'm using the w1 kernel driver. Is there an option to change the speed
of the bus? Maybe when building owfs?

thanks in advance

Timo

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
Arley Carter | 3 Feb 23:22 2016
Picon

owfs and postgresql

Has anybody used Jerry Scharf's python script recently?
I changed the import psycopg to import psycopg2
and ow.init to /dev/ttyUSB0.

The script runs but doesn't read any sensors.
outputs "sensors read = 0 " on each loop.
Any ideas out there?
Perhaps Jerry could provide insight if he is out there?
Thanks
Arley

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
Radoslav Chovan | 3 Feb 19:20 2016
Picon

Re: Can't compile OWFS for Windows cygwin/mingw

Hi, 
this is my current owshell.h

#define OWSHELL_H
#include <sys/time.h>
#include <sys/types.h>
#include <unistd.h>
#include "config.h"
#include "owfs_config.h"

I have run again configure and compile. 

I see same error:

make[4]: Entering directory '/home/wsdadm/owfs-3.1p1/module/owshell/src/c'
gcc -DHAVE_CONFIG_H -I. -I../../../../src/include    -I../include -I../../../owlib/src/include -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes -Wredundant-decls    -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=600 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -g -O2 -mwin32 -g -D_XOPEN_SOURCE=600 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -c ow_tcp_read.c
ow_tcp_read.c: In function ‘tcp_read’:
ow_tcp_read.c:31:3: error: unknown type name ‘fd_set’
   fd_set readset;
   ^
ow_tcp_read.c:35:3: warning: implicit declaration of function ‘FD_ZERO’ [-Wimplicit-function-declaration]
   FD_ZERO(&readset);
   ^
ow_tcp_read.c:36:3: warning: implicit declaration of function ‘FD_SET’ [-Wimplicit-function-declaration]
   FD_SET(file_descriptor, &readset);
   ^
ow_tcp_read.c:39:3: warning: implicit declaration of function ‘select’ [-Wimplicit-function-declaration]
   rc = select(file_descriptor + 1, &readset, NULL, NULL, &tv);
   ^
ow_tcp_read.c:42:4: warning: implicit declaration of function ‘FD_ISSET’ [-Wimplicit-function-declaration]
    if (FD_ISSET(file_descriptor, &readset) == 0) {
    ^
Makefile:644: recipe for target 'ow_tcp_read.o' failed



2016-02-03 14:58 GMT+01:00 Jan Kandziora <jjj <at> gmx.de>:
Am 03.02.2016 um 07:33 schrieb Radoslav Chovan:
> Hi,
> after your advice, configure run without error, but compilation in cygwin
> break on this error:
>
> version 3.1p1
>
> gcc -DHAVE_CONFIG_H -I. -I../../../../src/include    -I../include
> -I../../../owlib/src/include -fexceptions -Wall -W -Wundef -Wshadow
> -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes
> -Wredundant-decls    -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=600
> -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -g -O2 -mwin32
> -g -D_XOPEN_SOURCE=600 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1
> -D_POSIX_C_SOURCE=200112L -c ow_tcp_read.c
> ow_tcp_read.c: In function ‘tcp_read’:
> ow_tcp_read.c:31:3: error: unknown type name ‘fd_set’
>    fd_set readset;
>    ^
> ow_tcp_read.c:35:3: warning: implicit declaration of function ‘FD_ZERO’
> [-Wimplicit-function-declaration]
>    FD_ZERO(&readset);
>    ^
> ow_tcp_read.c:36:3: warning: implicit declaration of function ‘FD_SET’
> [-Wimplicit-function-declaration]
>    FD_SET(file_descriptor, &readset);
>    ^
> ow_tcp_read.c:39:3: warning: implicit declaration of function ‘select’
> [-Wimplicit-function-declaration]
>    rc = select(file_descriptor + 1, &readset, NULL, NULL, &tv);
>    ^
> ow_tcp_read.c:42:4: warning: implicit declaration of function ‘FD_ISSET’
> [-Wimplicit-function-declaration]
>     if (FD_ISSET(file_descriptor, &readset) == 0) {
>     ^
> Makefile:644: recipe for target 'ow_tcp_read.o' failed
> make[4]: *** [ow_tcp_read.o] Error 1
> make[4]: Leaving directory '/home/wsdadm/owfs-3.1p1/module/owshell/src/c'
> Makefile:486: recipe for target 'all-recursive' failed
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory '/home/wsdadm/owfs-3.1p1/module/owshell/src'
> Makefile:486: recipe for target 'all-recursive' failed
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory '/home/wsdadm/owfs-3.1p1/module/owshell'
> Makefile:500: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/home/wsdadm/owfs-3.1p1/module'
> Makefile:555: recipe for target 'all-recursive' failed
> make: *** [all-recursive] Error 1
>
Question: Do you have all the needed header files installed? Usually
this is covered by the configure run but cygwin is special and we don't
have too many persons who test it.


You can try adding

#include <sys/time.h>
#include <sys/types.h>
#include <unistd.h>

inside module/owshell/src/include/owshell.h right after

#define OWSHELL_H

Let me know if you get another error at the same file or run into
another error with the next.


Kind regards

        Jan

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Dean Waldow | 3 Feb 18:36 2016

OWFS and OSX...

Greetings, 

I hope this is not too much of a newbie question and this list may be more focused on development only... 

I have used owfs in the past on redhat and centos but would really like to put owfs on an OSX box. About a month
ago, I spent a fair bit of time trying to compile / install owfs on my OSX 10.11.x box and was unable to get it to
be successfully installed. I tried using MacPorts and again using homebrew for parts that were missing
from the vanilla OSX install. I also un-tarred the pretty old owfs-osx tar ball but that seems built for the ppc.

I am curious if owfs should be able to be installed on OSX? It seems that it is intended to be installed on OSX
from what I have read onine perhaps with the exception of the fuse file system.

If it is supposed to be able to be functional on OSX, are there any instructions some where I have maybe
missed? I tried using the sourceforge build from around late December. Perhaps I should try again after
the Jan 2016 build (owfs3.1p1)? I can provide more information about the install issues if I am asking the
right list.

I am trying to connect my 1-wire system using a USB interface (the blue one, DS9490R I think) with Hobby
Boards devices mostly. I can get the HobbyBoards OSX test software to talk to the network and get at a
temperature from a connected device.

If I am asking the wrong list, let me know. Thanks for any direction to answer this install question.

Dean

------------------------------------------------
Dean Waldow, Professor
Department of Chemistry
Pacific Lutheran University
Tacoma, WA 98447  USA

253-535-7533 (Office)
253-536-5055 (FAX)

waldow <at> chem.plu.edu
http://www.chem.plu.edu/waldow/

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Stefano Miccoli | 3 Feb 00:04 2016

owexist.1 missing

Jan:

something went wrong with commit 924a1ba17cf5e8bc46ccabecb2318f62c9af3a0c:

owexist.1 does not exist in the source tree, so that build fails with:

make[3]: *** No rule to make target 'owexist.1', needed by 'all-am'.  Stop.

Probably you forgot to add 'src/man/man1/owexist.1’ to the git repo after applying patch https://sources.debian.net/src/owfs/3.1p0-2/debian/patches/for-upstream-owexist-manpage.patch/

Regards, 

Stefano

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Jan Kandziora | 2 Feb 23:14 2016
Picon
Picon

Re: Can't compile OWFS for Windows cygwin/mingw

Am 02.02.2016 um 20:39 schrieb Coudy:
> Hi,
> I have followed this guide:
> http://www.clemens.it/dev/doku.php?id=building_owfs_on_cygwin
> After unzipped source files, I run ./bootstrap, autoreconf -if, and
> configure with my parameters. Then tried again with original configure from
> tar.gz
> 
This will overwrite ./configure with a broken version produced by the
autoconf/automake suite you use.

Please, do a clean unzip of the original sources from

	https://sourceforge.net/projects/owfs/files/owfs/3.1p1/

Then, *don't* ./bootstrap and *don't* autoreconf -if. There's a clean
./configure included inside the source package. Run that clean
./configure and report.

Kind regards

	Jan

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Radoslav Chovan | 2 Feb 16:48 2016
Picon

Can't compile OWFS for Windows cygwin/mingw

Hi, 
I need to use owserver on windows, I have found compiled binaries, but they does not work. They ask for not existent dlls (cygusb-1.0.dll, cygncurses-10.dll). I have tried binary version 2.8p14, 2.9p9, 3.0p2, 3.1p0

I´m trying to compile owfs for windows. I need only owserver, owhttpd and owshell without USB support. 
When I try compilation on cygwin, it ask for libusb, even if I configure with option --disable-usb

./configure --disable-usb --disable-owftpd --disable-avahi --disable-zero --enable-owhttpd --enable-mt --enable-owshell --disable-owfs --disable-swig --disable-owpython --disable-owperl --disable-owtcl --disable-dependency-tracking --prefix=/usr

Configuration stop on this error:
checking if usb support is enabled... no
./configure: line 16685: syntax error near unexpected token `LIBUSB,'
./configure: line 16685: `      PKG_CHECK_MODULES(LIBUSB, libusb-1.0 >= 0.9.1, ENABLE_USB=true,ENABLE_USB=false)'


so I tried compile it with mingw. Configuration end without error, but when I run make, it crash on missing sys/time.h, because mingw does not have time.h (http://stackoverflow.com/questions/12747515/installing-compiling-in-cygwin-mingw-how-to-set-the-include-path-symbolic)

gcc -DHAVE_CONFIG_H -I. -I../../../../src/include    -I../include -I../../../owl
ib/src/include -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qua
l -Wcast-align -Wstrict-prototypes -Wredundant-decls -D_FILE_OFFSET_BITS=64 -D_X
OPEN_SOURCE=600 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -g
-O2 -D_XOPEN_SOURCE=600 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200
112L -c -o ow_opt.o ow_opt.c
In file included from ow_opt.c:14:0:
../include/owshell.h:33:41: fatal error: sys/times.h: No such file or directory
 #include <sys/times.h>   /* for times */
                                         ^
compilation terminated.
make[4]: *** [ow_opt.o] Error 1

I have tried compile versions 3.1.p0 and 3.1p1, with cygwin and mingw, but result is same. Could you plese help me, or provide native (no cygwin) binaries ?

thank you
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Jan Kandziora | 2 Feb 01:18 2016
Picon
Picon

Introducing a new "latesttemp" node on the DS18B20, DS18S20, DS1822, DS1825, and DS28AE00.

Hi,

I just committed the "latesttemp" node we have been talking about
recently. It's function: provide a way to read the temperature value
from scratchpad *without triggering a conversion*.

This is especially useful in conjunction with simultaneous conversions.

$ owwrite /simutaneous/temperature 1
$ sleep 1
$ owread /uncached/10.AE9C54020800/latesttemp
    19.6875
$ owread /uncached/10.9EFD53020A00/latesttemp
       21.5
...

Please pull from the git archive and test.

Kind regards

	Jan

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Johan Ström | 25 Jan 21:39 2016
Picon

libftdi support: take 2

Hi,

some of you may remember my earlier attempts to add a libftdi based LinkUSB interface into master. For reference: http://sourceforge.net/p/owfs/mailman/message/32492037/
In short, the client-timings are generally cut about 2.5 times, depending on operation. A temp sensor is read in ~50ms instead of ~123ms. More details can be found at the link.

Last time (2014) it was well received, but got stuck on discussions about different methods of auto-detection (something which isn't too easy/possible with FTDI).  I have since run that code in production without any glitches, so the ftdi-part has really proven stable.
In the recent days, I've cleaned up the code to not be LinkUSB specific, but rather work with any serial-based device (and fixed some minor issues). There is no auto-detection though (and again, I don't believe that is possible to do reliable with serial devices; see discussions in above link).

A cut from the (updated) man page is available below, please see that for usage details.
I realize that this isn't the simplest thing to explain to a user, but then again, a regular user who don't really care about those extra milliseconds shaved off each request can easily use the same old /dev/ttyS0 addressing. For us who *do* care however, it is very useful.

The ftdi parts of the code has been running since 2014, but only with LinkUSB. But it's mostly the device setup parts which has changed lately, so it shouldn't be any unstability. I've tested the LinkUSB, emulated and --link mode,  and DS2480 through a FTDi adapter without any issues.

I've commited all the changes in the new ftdi branch: http://sourceforge.net/p/owfs/code/ci/2982df8ca648bd9cec4d820151046b044ef504e0/
The above is a clean patch based on my earlier work (which may be interesting for those wanting to check out how it evolved) at http://sourceforge.net/u/stromnet/owfs/ci/ca85d64eefaaa9f1e90bbc079db65cfda623c472/log/?path=

One potential issue could be the BUS_close related changes in ow_connection.c, could someone take a look at that please? I think that is actually a bug fix, basically it calls device-specific BUS_close *before* cleaning up and closing the device, instead of after.. But an extra set of eyes would be great.

Another issue could be that I now bring any link-devices into 19200-mode after initial detection (also increases the speed a lot). This is the mode I've been running my LinkUSB during the last years, via the FTDI layer, so should be OK. But I have not tested with older links, or non-USB based links (or the linkusb via old serial addressing for any longer duration).

To sum it up, I hope we can get this branch merged into master sooner rather than later! If we want to add a sane auto-detection scheme somehow, let's add that later..

Any testing and feedback is much appreciated!

Regards
Johan

Man-page cut:
-------
* Serial devices
       port specifies a serial port, e.g.  /dev/ttyS0

       If OWFS was built with libftdi support, you may  be  able  to  use  the
       ftdi: prefix to address a FTDI-based USB device.
       For details, see the FTDI ADDRESSING section.

....
FTDI ADDRESSING
       FTDI  is  a brand of USB-to-serial chips which are very common. If your
       serial device is connected via a USB serial  dongle  based  on  a  FTDI
       chip,  or  if  your adapter uses a built-in FTDI USB chip (for example,
       the LinkUSB), you can use this FTDI addressing.

       The main benifit with this mode of access is that we can  decrease  the
       communication  delay,  yielding  twice  as fast 1-Wire communication in
       many cases.

       The following values for port can be used to identify a  specific  FTDI
       port.  Note that this requires that OWFS is built with libftdi support.

       ftdi:d:<devicenode>
              path of bus and device-node (e.g. "003/001") within  usb  device
              tree (usually at /proc/bus/usb/)

       ftdi:i:<vendor>:<product>
              first  device with given vendor and product id, ids can be deci-
              mal, octal (preceded by "0") or hex (preceded by "0x")

       ftdi:i:<vendor>:<product>:<index>
              as above with index being the number  of  the  device  (starting
              with 0) if there are more than one

       ftdi:s:<vendor>:<product>:<serial>
              first device with given vendor id, product id and serial string

       The  above formats are parsed fully by libftdi, but with the ftdi: pre-
       fix stripped.

   Simplified device serial-only support
       An additional format is supported, for certain  bus  types.  This  only
       specifies the USB serial number.

       ftdi:<serial>
              Identifies  a  FTDI  device  by serial only.  Currently, this is
              only valid for the VID/PID found on the LinkUSB  (i.e.  --link).
              Note that those VID/PID's are the default for any FT232R device,
              and in no way exclusive to LinkUSB.

-----
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Gregg Levine | 20 Jan 06:12 2016
Picon

It seems I'm listed as an Admin (via my SF identity of course)

Hello!
However what does that entail, and more importantly, what am I
expected to be able to do? Am I entitled to commit things to the file
storage spaces? I'd rather not. Patch making and Git are something
I've never completely figured out. File writing is something I'm still
working on.

And additionally this is being written on a Slackware64 system running
native on my laptop. (No I've not jettisoned Windows, different
drive.)
-----
Gregg C Levine gregg.drwho8 <at> gmail.com
"This signature fought the Time Wars, time and again."

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140

Gmane