Re: [Owfs-developers] 'strange' value reading /sensed.BYTE of a DS2408 (Stefano Miccoli)

On Tue, 10 Nov 2015 00:13:41 +0100 Stefano Miccoli mo...@icloud.com wrote: > On my owfs.conf I had these two lines: > > server: link = /dev/ttyS0 > server: server = some.fully.qualified.domain.name:4304 > > which mean that sensors at the root (owdir /) will be collected from a > Link45 (see htt

Re: [Owfs-developers] Having problem reading ds1490F Fob

Am 10.11.2015 um 01:23 schrieb David Jackson: > So update 2 :) Im puzzled. Unplugging ALL devices allows the fob to > be seen. I can plug in a “phone cord” still see Fob. > Good. Means you phone cord is ok. > But if I plug in > either of my Temp sensors from hobby-boards.com I can no longer even

Re: [Owfs-developers] Having problem reading ds1490F Fob

So update 2 :) Im puzzled. Unplugging ALL devices allows the fob to be seen. I can plug in a “phone cord” still see Fob. But if I plug in either of my Temp sensors from hobby-boards.com I can no longer even see the FOB! Wierd. The boards are configured to use parasitic power. David

Re: [Owfs-developers] Having problem reading ds1490F Fob

:) Your Right!!! kdj@raspberrypi ~ $ /opt/owfs/bin/owget /uncached /uncached/81.427E3000 /uncached/bus.0 /uncached/settings /uncached/system /uncached/statistics /uncached/structure now what? David > On Nov 9, 2015, at 12:43 PM, owfs-developers-requ...@lists.sourceforge.net > wrote: > >

Re: [Owfs-developers] 'strange' value reading /sensed.BYTE of a DS2408 (Stefano Miccoli)

Sorry if I was not clear enough… (and yes I should dump my mail client, it keeps rewriting my mails inserting fancy utf-8 chars and http links). On my owfs.conf I had these two lines: server: link = /dev/ttyS0 server: server = some.fully.qualified.domain.name:4304 which mean that sensors at the

Re: [Owfs-developers] Having problem reading ds1490F Fob

Am 09.11.2015 um 21:14 schrieb David Jackson: > > did this after a reboot.! > > ps -Af | grep ow > root 2134 1 0 13:35 ?00:00:00 /usr/bin/owserver -c > /etc/owfs.conf --pid-file /var/run/owfs/owserver.pid > root 2213 1 0 13:35 ?00:00:00 /usr/bin/owhttpd -c >

Re: [Owfs-developers] 'strange' value reading /sensed.BYTE of a DS2408 (Stefano Miccoli)

On Mon, 09 Nov 2015 15:46:48 +0100 Stefano Miccoli mo...@icloud.com wrote: > Curiously I ran in a similar situation as the BBB: ... > ** non persistent : 39.96 ms, 39.99 ms, 40.00 ms, 40.01 ms, 40.21 ms, > ** persistent : 39.98 ms, 40.00 ms, 40.00 ms, 40.00 ms, 40.00 ms, > When I substitute

[Owfs-developers] Having problem reading ds1490F Fob

> Hello, > have you build owfs self INCLUDING the USB settings? Its a package so no I didnt build it. So is this a line in the make file I guess? > Maybe when that be missing, you will never can read sensors. > Also will you will be sure, that OW_HTTPD will not access > to the USB-adapter during

Re: [Owfs-developers] Having problem reading ds1490F Fob

Am 09.11.2015 um 19:30 schrieb Roland Franke: > Hello, > have you build owfs self INCLUDING the USB settings? > Maybe when that be missing, you will never can read sensors. > Also will you will be sure, that OW_HTTPD will not access > to the USB-adapter during the time you start owserver/owfs? > Th

Re: [Owfs-developers] Having problem reading ds1490F Fob

Am 09.11.2015 um 19:14 schrieb David Jackson: > > Ok did that! > kdj@raspberrypi ~ $ sudo owserver -c y > kdj@raspberrypi ~ $ top > > top - 11:53:16 up 8 min, 1 user, load average: 0.06, 0.10, 0.06 > Tasks: 68 total, 1 running, 67 sleeping, 0 stopped, 0 zombie > %Cpu(s): 0.3 us, 1.7

Re: [Owfs-developers] Having problem reading ds1490F Fob

Hello, have you build owfs self INCLUDING the USB settings? Maybe when that be missing, you will never can read sensors. Also will you will be sure, that OW_HTTPD will not access to the USB-adapter during the time you start owserver/owfs? The access from two program (server and httpd) at the same h

Re: [Owfs-developers] Having problem reading ds1490F Fob

> From: Jan Kandziora mailto:j...@gmx.de>> > Subject: Re: [Owfs-developers] Having problem reading ds1490F Fob > To: "OWFS (One-wire file system) discussion and help" >> > Message-ID: <5640d3a5.5060...@gmx.de > >

Re: [Owfs-developers] owserver does not print information according to --error_level setting

Am 09.11.2015 um 18:14 schrieb Martin Patzak (GMX): > > The package maintainer is Vincent , would you > please ask him what is going on? > The debian/rules file from http://http.debian.net/debian/pool/main/o/owfs/owfs_2.9p8-6.debian.tar.xz clearly specifies --disable-debug as a configure option

Re: [Owfs-developers] 'strange' value reading /sensed.BYTE of a DS2408 (Martin Patzak (GMX))

Loren will be excited to read this. Who is the funny bunny now? On 11/09/2015 03:46 PM, Stefano Miccoli wrote: Curiously I ran in a similar situation as the BBB: $ python -m test.timing //10.48.74.119/ pyownet: ver. 0.8.2 proxy_obj: ownet server at ('10.48.74.119', 4304) server info: pid 2443,

Re: [Owfs-developers] owserver does not print information according to --error_level setting

cool! I like it ;o) On 11/09/2015 02:53 PM, Jan Kandziora wrote: Am 09.11.2015 um 09:26 schrieb Martin Patzak (GMX): To recap: the debian package for owfs and owserver does not honor --debug option, but merely prints a DEBUG statement in the beginning owfs does print error-level information of

Re: [Owfs-developers] owserver does not print information according to --error_level setting

On 11/09/2015 02:29 PM, Jan Kandziora wrote: > Am 09.11.2015 um 09:26 schrieb Martin Patzak (GMX): >> Depending on your built and packaging the --debug option may merely >> print a DEBUG statement, but not actually do any debugging. >> > Really, I don't know why the debian package maintainer disa

Re: [Owfs-developers] Having problem reading ds1490F Fob

Am 09.11.2015 um 17:36 schrieb David Jackson: > Ok so when I run the following when I run the following command: > > $sudo owfs [-c owfs.conf] -F -u -m /mnt/1wire —allow_other > No, no, no. You have to decide whether you want to use the setup from the config file or a setup on the command line.

Re: [Owfs-developers] Having problem reading ds1490F Fob

Ok so when I run the following when I run the following command: $sudo owfs [-c owfs.conf] -F -u -m /mnt/1wire —allow_other it just returns a prompt no output. $ ls /mnt/1wire bus.0 bus.1 settings statistics structure system uncached but no devices… owget /unchached returns owget: comm

Re: [Owfs-developers] Having problem reading ds1490F Fob

Am 09.11.2015 um 15:53 schrieb David Jackson: > > ! server: server = localhost:4304 > This means: all owfs programs but owserver should connect to a running owserver. > server: usb = all > This means: owserver should connect to an DS2490 based USB adapter (as the DS1490F is) connected to any usb

[Owfs-developers] Having problem reading ds1490F Fob

Hello, I have been banging my head for the last 2 weeks trying to get my ds1490F Fob 2 in 1 usb controller to work with my raspberry pi. here is the contents of owfs.conf # local machine... ! server: server = localhost:4304 # # ...and owserver uses the real hardware, by default fake devices #

Re: [Owfs-developers] 'strange' value reading /sensed.BYTE of a DS2408 (Martin Patzak (GMX))

Curiously I ran in a similar situation as the BBB: $ python -m test.timing //10.48.74.119/ pyownet: ver. 0.8.2 proxy_obj: ownet server at ('10.48.74.119', 4304) server info: pid 2443, ver. unknown timeit: statement: proxy_obj.dir("/") number: 20 repetitions: 5 ** non persistent : 39.96 ms, 39

Re: [Owfs-developers] owserver does not print information according to --error_level setting

Am 09.11.2015 um 09:26 schrieb Martin Patzak (GMX): > To recap: > the debian package for owfs and owserver does not honor --debug option, > but merely prints a DEBUG statement in the beginning > owfs does print error-level information of level 3 only, if > --error-level is set to 3 or higher. If

Re: [Owfs-developers] owserver does not print information according to --error_level setting

Am 09.11.2015 um 09:26 schrieb Martin Patzak (GMX): > > Depending on your built and packaging the --debug option may merely > print a DEBUG statement, but not actually do any debugging. > Really, I don't know why the debian package maintainer disabled debug support at all. Maybe there's another p

Re: [Owfs-developers] owserver does not print information according to --error_level setting

Loren, thanks for your efforts, but in a previous version of owfs the error logging worked fine for me too. It is like Jan said, it is build without or too little debug information. Martin -- Presto, an open source d

Re: [Owfs-developers] 'strange' value reading /sensed.BYTE of a DS2408 (Martin Patzak (GMX))

On 11/07/2015 10:27 PM, Loren Amelang wrote: > On Sat, 07 Nov 2015 09:21:43 +0100 > "Martin Patzak (GMX)" martin.pat...@gmx.de wrote: > >> why don't you try and run Stefanos timing program directly on your >> Beagle and see what timing you get there > Posted that earlier: > ok, sorry I did not

Re: [Owfs-developers] owserver does not print information according to --error_level setting

On 11/07/2015 04:56 PM, Jan Kandziora wrote: > > --debug is the same as "--foreground --error_level=9" > > See module/owlib/src/c/ow_opt.c:733ff ok, I see > > That's the output when debug support wasn't selected at compile time. ok, that added to my confusion a bit > > >>> You are using a build w