Johan Ström | 16 Nov 12:17 2014
Picon

Non-portable make in new man Makefiles

Hi,

I was notified that owfs 2.9p8 fails to build on FreeBSD 8.4 and 9.1, 
seemingly due to a portability issue in the new manpages Makefiles.
Not sure why it fails on these older FreeBSDs, when it works on 10.0.. 
But both 8.x and 9.x is on extended support so it would be nice if we 
could build there as well, since everything else works afaik.

The issue:

owfs-2.9p8/src/man/man3 # make
Error expanding embedded variable.
owfs-2.9p8/src/man/man3 #

The line which fails to execute is:

man3_MANS = $(addsuffix .3,$(basename $(MANFILES)))

I'm not really sure what to replace this with to make it all working, so 
I'll just report it here. I can assist with testing though.

Johan

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
(Continue reading)

Andrey | 12 Nov 08:36 2014
Picon

Custom 1-wire addresses

Hello.
I'm developing custom 1-wire devices, based on MSP430 chips.
Those chips can implement ds2406 + ds1820 + ds2438 in one 1-wire slave.

The problem is running them in one network with devices, made by "official" Texas Instruments and their partners due to possible address intersection.

 

Could you please advise, how to get a legal address pool (family code, or something like this) for my devices?

Is there some kind of “reserved for custom devices” address pool/family code I could use? Or may be I must make some kind of  request to Texas Instruments?

 

Searched Texas and Maxim web sites with no positive result…

 

Thanks.

<!-- /* Font Definitions */ <at> font-face {font-family:"MS 明朝"; panose-1:0 0 0 0 0 0 0 0 0 0; mso-font-charset:128; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:fixed; mso-font-signature:1 134676480 16 0 131072 0;} <at> font-face {font-family:"MS 明朝"; panose-1:0 0 0 0 0 0 0 0 0 0; mso-font-charset:128; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:fixed; mso-font-signature:1 134676480 16 0 131072 0;} <at> font-face {font-family:Cambria; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:0; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:-536870145 1073743103 0 0 415 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:Cambria; mso-ascii-font-family:Cambria; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"MS 明朝"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Cambria; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-family:Cambria; mso-ascii-font-family:Cambria; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"MS 明朝"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Cambria; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} <at> page WordSection1 {size:595.0pt 842.0pt; margin:72.0pt 90.0pt 72.0pt 90.0pt; mso-header-margin:35.4pt; mso-footer-margin:35.4pt; mso-paper-source:0;} div.WordSection1 {page:WordSection1;} -->
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Steinar Midtskogen | 3 Nov 23:14 2014

New Hobby Boards humidity sensor

Hello,

It's probably not an owfs problem, but perhaps people here have some
experience with the new humidity sensor from Hobby Boards.  It seems to
work fine with the latest owserver, but the readings seem a bit low.
It's heavy fog and rain outside (i.e. 100%), but I only get 80-85%.  The
temperature is about 5C.  Indoor I got about 40% which probably is about
right, so it does react to humidity.  Has anyone seen something similar?

Also, the temperature reading is about one degree C higher than the
DS1820 sensors I have at the same place.  Does it generate internal
heat?  I'm using the standard HB enclosure.  The venting holes do seem a
bit small.

An issue which is owfs related: Is it possible to change the polling
frequency?

# owget -s 3000 /EF.90A020150000/humidity/polling_available
         255
# owget -s 3000 EF.90A020150000/humidity/polling_frequency
           2
# owwrite -s 3000 EF.90A020150000/humidity/polling_frequency 1
# owget -s 3000 EF.90A020150000/humidity/polling_frequency
           2

Shouldn't this work?

--

-- 
Steinar

------------------------------------------------------------------------------
David Lazarou | 31 Oct 13:57 2014
Picon

"Message too long" errors with owfs

Hi,

I'm running owserver on a Raspberry Pi and using owfs as a client locally to read data from the 1-wire bus. To run owserver I'm using the command:

owserver --configuration /opt/owfs/etc/owfs.conf

and for owfs:

owfs --mountpoint=/mnt/owfs --configuration /opt/owfs/etc/owfs.conf

where owfs.conf contains:

server: usb = all
server: port = 4304
owfs: allow_other
owfs: server = 127.0.0.1:4304
server: pid_file = /run/owserver.pid
owfs: pid_file = /run/owfs.pid

However, when I try to read any data from the 1-wire bus I get an error.

# pwd
/mnt/owfs/EF.BE6620150000
# ls -l
total 0
-r--r--r-- 1 root root   16 Oct 31 11:45 address
-rw-rw-rw- 1 root root  256 Oct 31 11:45 alias
-r--r--r-- 1 root root    2 Oct 31 11:45 crc8
-r--r--r-- 1 root root    2 Oct 31 11:45 family
drwxrwxrwx 1 root root 4096 Oct 31 12:35 hub
-r--r--r-- 1 root root   12 Oct 31 11:45 id
-r--r--r-- 1 root root   16 Oct 31 11:45 locator
-r--r--r-- 1 root root   16 Oct 31 11:45 r_address
-r--r--r-- 1 root root   12 Oct 31 11:45 r_id
-r--r--r-- 1 root root   16 Oct 31 11:45 r_locator
-r--r--r-- 1 root root   32 Oct 31 11:45 type
-r--r--r-- 1 root root   12 Oct 31 12:35 type_number
-r--r--r-- 1 root root    7 Oct 31 12:35 version
# cat type_number
cat: type_number: Message too long
# cat version
cat: version: Message too long

If I use owfs to connect directly to the 1-wire bus I do not get the error and every thing works fine.
Similarly, if I connect to the owserver on the Raspberry Pi from a remote linux host using owfs I do not get the error.
If I run the owserver on a linux host and connect remotely to the server using owfs from the Raspberry Pi, the error remains. I'm pretty sure this problem is related to owfs program on the Raspberry Pi.

Has anyone else seen this problem or know what the issue could be?

Thanks
David

------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Loren Amelang | 29 Oct 19:59 2014
Picon

Config owfs to use server?

I'm still trying to understand whether I have a possible conflict with both owfs and server trying to read my
hardware. Something was updating the filesystem while server and httpd were not running...  My config is
part of the default Ubuntu distribution for 14.04, with just the "w1" added to point to my hardware. 

I notice in Roland's config he has set 
server: usb
like I have set 
server: w1
but he also sets 
owfs: server = 127.0.0.1:4304
and I have no equivalent line. 

I don't even see an "owfs" process running:
---
root      1151  0.0  0.1  20036   836 ?        Ssl  Oct19   1:56 /usr/bin/owftpd -c /etc/owfs.conf --pid-file /var/run/owfs/owftpd.pid
root     13064  0.0  0.1  11828  1000 ?        Ss   Oct26   0:00 /usr/bin/owhttpd -c /etc/owfs.conf --pid-file /var/run/owfs/owhttpd.pid
root     13605  0.0  0.2  53804  1168 ?        Ssl  Oct26   0:00 /usr/bin/owserver -c /etc/owfs.conf --pid-file /var/run/owfs/owserver.pid
---
It seems "owfs" can be used without the ftp/http/server modules, so it must exist on its own somehow. But
where? 

Should I add that "owfs: server = 127.0.0.1:4304" line to my config? Or does 
! server: server = localhost:4304
do the same thing, since it supposedly applies to everything except server? 

What about "owfs: pid_file = /var/run/owfs.pid"? I don't have an owfs.pid file on my system...  Just the
ftpd/httpd/server pid files. 

I see many configs with lines like "owfs: mountpoint = /mnt/1wire". I don't understand why one would mount
at /mnt/1wire when everything is already visible at /sys/devices/. 

Maybe the default Ubuntu install has done some of this for me, in some file I haven't found yet? I tend to
assume that whoever made the official Ubuntu distribution knows much more than I do. But I do get
occasional bad reads and bogus temperature values, and as I said, the filesystem was getting updated even
while server was stopped. 

Loren

| Loren Amelang | loren <at> pacific.net |

On Wednesday, October 29, 2014 at 9:27 AM,
owfs-developers-request <at> lists.sourceforge.net wrote:

 
> From: "Roland Franke" <fli4l <at> franke-prem.de>
> Subject: Re: [Owfs-developers] Missing data
> To: "Roland Franke" <fli4l <at> franke-prem.de>,     "OWFS \(One-wire file
> system\) discussion and help"   <owfs-developers <at> lists.sourceforge.net>
> Message-ID: <32224CCF5ADA40D38212CB7E0D3E7E8E <at> rolandAMD64>
> Content-Type: text/plain; charset="utf-8"
> 
> Here is my configuration (As i now will be at home )
> owfs.conf is:
> error_print = 3
> error_level = 0
> format = f.i
> cache_size = 0
> Celsius
> foreground
> allow_root
> owfs: server = 127.0.0.1:4304
> owfs: pid_file = /var/run/owfs.pid
> owfs: mountpoint = /mnt/1wire
> server: usb
> server: port = 127.0.0.1:4304
> server: pid_file = /var/run/owsever.pid
> http: server = 127.0.0.1:4304
> http: port = 8080
> http: pid_file = /var/run/owhttpd.pid
>

------------------------------------------------------------------------------
Loren Amelang | 28 Oct 02:42 2014
Picon

Re: Owfs-developers Digest, Vol 101, Issue 23

Roberto,

Thank you for the clue about "/etc/init.d/owserver status" sometimes being unreliable. I suspect "sudo
service owserver status" might have the same issues? 

I was double-checking those results with: 
ps -ef |grep 'owfs'
root      1151     1  0 Oct19 ?        00:01:23 /usr/bin/owftpd -c /etc/owfs.conf --pid-file /var/run/owfs/owftpd.pid
root     13064     1  0 14:44 ?        00:00:00 /usr/bin/owhttpd -c /etc/owfs.conf --pid-file /var/run/owfs/owhttpd.pid
root     13605     1  0 15:27 ?        00:00:00 /usr/bin/owserver -c /etc/owfs.conf --pid-file /var/run/owfs/owserver.pid
(That's after I successfully restarted both processes.)

Mine always matched. It looked like owhttpd stopped serving pages a few minutes after owserver died, and
would not work until owserver was running again. 

I guess your netstat check has the advantage of proving the server is actually listening on the network,
rather than just running. 

Loren

| Loren Amelang | loren <at> pacific.net |

> 1. Re: Updates while server not running, "simultaneous" kills
> it? (Stefano Miccoli)
> 
> Message: 1
> Date: Mon, 27 Oct 2014 00:39:18 +0100
> From: Stefano Miccoli <mocme <at> icloud.com>
> Subject: Re: [Owfs-developers] Updates while server not running,
> "simultaneous" kills it?
> To: "OWFS (One-wire file system) discussion and help"
> <owfs-developers <at> lists.sourceforge.net>
> Message-ID: <6A591CCC-404A-477C-B1B3-5AE144B6D3A4 <at> icloud.com>
> Content-Type: text/plain; charset="us-ascii"
> 
> 
> On 26 Oct 2014, at 23:55, Loren Amelang <loren <at> pacific.net> wrote:
> 
>> root <at> arm:/home/ubuntu# /etc/init.d/owhttpd status
>> * owhttpd is not running
>> root <at> arm:/home/ubuntu# /etc/init.d/owserver status
>> * owserver is not running
>> ---
> 
> Don't trust too much the /etc/init.d scripts: sometimes they get confused
> (at least on Debian+SysVinit; I have no experience with Ubuntu+Upstart).

> I usually run (as root or with sudo) "netstat -tlp | grep 4304" to see if
> there is an owserver listening. It was quite common for me to have a stale
> owserver (not killed by repeated "/etc/init.d/owserver stop" calls)
> preventing a fresh owserver from starting... In such cases killing by proc
> number or "killall owserver" solved the problem.

------------------------------------------------------------------------------
Loren Amelang | 26 Oct 23:55 2014
Picon

Updates while server not running, "simultaneous" kills it?

Paul,

Your comment about "two processes competing for the same resource" made me think of my random problem with
temperature values of "-62". My config file is just like the one at:
http://owfs.org/index.php?page=quickstart-guide

Except I (thought I had) commented the "server: FAKE = DS18S20,DS2405" line, 
and added "server: w1" right under the "#server: usb = all" line. 
---
# With this setup, any client (but owserver) uses owserver on the
# local machine...
! server: server = localhost:4304
#
# ...and owserver uses the real hardware, by default fake devices
# This part must be changed on real installation
! server: FAKE = DS18S20,DS2405
#
# USB device: DS9490
#server: usb = all
server: w1
---

I think I just learned something...  The manpage says:
---
server: opt = value # only owserver effected by this line 
! server: opt = value # owserver NOT effected by this line
---

What I missed until now is that "! server:" apparently DOES apply to everything BUT owserver. That makes
sense of the first command copied above - it tells everyone except server to read from server. 

When I took '!' for another type of comment character, and used it before "server: FAKE = DS18S20,DS2405" it
didn't stop the fake devices from appearing. So that has been telling everybody except owserver to read
the fake devices directly...  But owserver was not reading them, so not a resource competition? And they
shouldn't affect the real hardware devices? Changing "!" to '#' and "sudo service owhttpd restart" has
eliminated the fake devices.

When I added "server: w1", it did cause owserver (or someone) to read my configured BBB hardware pin. So I
guess that must be correct. 

 
While poking around the http display, I notice:
NET_connection_errors   58
All the other error counts are 0. 

This is with:
---
statistics/read
bytes   8652
cachebytes      0
cachesuccess    0
calls   484
success 484
tries.ALL       492, 6, 6
tries.0 493
tries.1 6
tries.2 6
---

Still the same 58 errors at 524 reads. I can't find any explanation of what NET_connection_errors are. Or
why tries.ALL is always 8 more than calls...  Or the difference between tries.0/1/2?

 
New issue...  For no obvious reason (but see below), the real devices disappeared from the web page, and
after a few more tries the web page refused to load. The filesystem is still visible and temperatures are
still being updated, but apparently both server and httpd are gone:
---
root <at> arm:/home/ubuntu# /etc/init.d/owhttpd status
* owhttpd is not running
root <at> arm:/home/ubuntu# /etc/init.d/owserver status
* owserver is not running
--- 

When I first tried to restart http using sudo, it gave no error, but didn't work. 
---
ubuntu <at> arm:~$ sudo service owhttpd stop
* Stopping 1-Wire HTTP Daemon owhttpd                                                                                       [ OK ]
ubuntu <at> arm:~$ sudo service owhttpd start
* Starting 1-Wire HTTP Daemon owhttpd                                                                                       [ OK ]
ubuntu <at> arm:~$ sudo service owhttpd status
* owhttpd is not running
---

Maybe it won't start if server is not running? When I switched to real root and started server first, it
worked again. 

--> BUT - if owserver is the only module that reads actual hardware devices, and it was not running, who was
maintaining the filesystem and updating the temperatures? 

 
At the "top" of the http page, only bus.0 shows. But if I click bus.0, the new page shows bus.1 as well, and it
appears my real devices are on bus.1. What does this mean? 

 
Also on that bus.0 page (and on the top page) is "simultaneous":
---
bus.0/simultaneous

uncached version
up      directory
present         Error: Input/output error
present_ds2400  Error: Software caused connection abort
single          Error: Software caused connection abort
single_ds2400   Error: Software caused connection abort
temperature     Error: Software caused connection abort
voltage         Error: Software caused connection abort
---

Aha! Visiting that page kills owserver! That's what made the page loads fail earlier. At least now I know
what not to do...

 
Sorry if these are all obvious newbie questions, 

Loren

| Loren Amelang | loren <at> pacific.net |

> 3. Re: Missing data (Paul Alfille)

> Date: Sun, 26 Oct 2014 07:12:41 -0400
> From: Paul Alfille <paul.alfille <at> gmail.com>
> Subject: Re: [Owfs-developers] Missing data
> To: "OWFS (One-wire file system) discussion and help"
> <owfs-developers <at> lists.sourceforge.net>
> Message-ID:
> <CAP_SGzeYU0Aabs5kLnPW=n4t0TOaU8jNFzJs6L1MdMn8NFfH9A <at> mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Well there's always the possibility that there is a wiring problem, but
> also there could be two processes competing for the same resource.
> 
> Is owserver and owfs running at the same time? Your configuration file
> would have them both grabbing the same serial devices and stepping on each
> other.
> 
> If they both run at the same time, owfs should connect to owserver and
> have owserver make the exclusive hardware connection.

------------------------------------------------------------------------------
Jim Lill | 26 Oct 10:47 2014

EDS 4-ch A/1W board

I have a Embedded Data Systems
EDS 4-ch A/1W board, an EDS0083 I believe and it is recognized but does not get all its data. Anybody else using one? -Jim
------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Coudy | 25 Oct 20:58 2014
Picon

Missing data

Hi,
I'm using owfs with 19x DS18B20 temperature sensor with 2x DS9097 passive adapter. I have split my installation to two buses. Everything is running on my home NAS server (Core2Duo). I have problem with missing data. Sometimes data are not received.
I have tried it running as owserver and read data with owread/owget, and running as fuse mount point and read data with cat commad. Result is same. To store values I use Zabbix.

What is wrong, what should I change ? Is it issue with timeout or what ?

Thanks for any help.

Here are my system infos:
-----------------------------
this is my owfs.conf
#ALL
passive=/dev/ttyr00
passive=/dev/ttyr01
timeout_serial=5

#OwFS
mountpoint=/mnt/1wire
allow_other

# Display
format = f.i.c # 1-wire address f amily i d code c rc
alias=/etc/owfs.alias


-----------------------------
list of sensor on buses:
ls -l /mnt/1wire/bus.0
drwxrwxrwx 1 root root 4096 okt 25 20:35 pivnica_bojler
drwxrwxrwx 1 root root 4096 okt 25 20:35 pivnica_juzna
drwxrwxrwx 1 root root 4096 okt 25 20:35 pivnica_kurenie
drwxrwxrwx 1 root root 4096 okt 25 20:35 pivnica_kurenie_spiatocka
drwxrwxrwx 1 root root 4096 okt 25 20:35 pivnica_severna
drwxrwxrwx 1 root root 4096 okt 25 20:35 pivnica_tepla_voda
drwxrwxrwx 1 root root 4096 okt 25 20:35 pivnica_tepla_voda_spiatocka
drwxrwxrwx 1 root root 4096 okt 25 20:35 podkrovie_chodba
drwxrwxrwx 1 root root 4096 okt 25 20:35 podkrovie_spalna
drwxrwxrwx 1 root root 4096 okt 25 20:35 prizemie_hostovska
drwxrwxrwx 1 root root 4096 okt 25 20:35 prizemie_chodba
drwxrwxrwx 1 root root 4096 okt 25 20:35 prizemie_obyvacka_jv
drwxrwxrwx 1 root root 4096 okt 25 20:35 prizemie_spajza_dole
drwxrwxrwx 1 root root 4096 okt 25 20:35 prizemie_spajza_hore

ls -l /mnt/1wire/bus.1
drwxrwxrwx 1 root root 4096 okt 25 20:36 garaz
drwxrwxrwx 1 root root 4096 okt 25 20:36 pivnica_rack
drwxrwxrwx 1 root root 4096 okt 25 20:36 podkrovie_detska_j
drwxrwxrwx 1 root root 4096 okt 25 20:36 podkrovie_detska_s
drwxrwxrwx 1 root root 4096 okt 25 20:36 vonku


------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
David Lazarou | 25 Oct 04:57 2014
Picon

New Hobby Board barometer and humidity sensors

Hi All,

I recently purchased a new Hobby Board barometer and humidity sensor to add to my 1-wire network which uses a 1-wire USB adapter. However, while I do get data back from these devices, I see no barometric or humidity readings. I'm running the most recent code (owfs-2.9p8) which I noted supports these devices.
This is what I see when I do a directory listing of the devices:

barometer:

# ls -l /tmp/1-wire/EF.F69620150000
total 0
-r--r--r-- 1 root root  16 Oct 25 13:16 address
-rw-rw-rw- 1 root root 256 Oct 25 13:16 alias
-r--r--r-- 1 root root   2 Oct 25 13:16 crc8
-r--r--r-- 1 root root   2 Oct 25 13:16 family
-r--r--r-- 1 root root  12 Oct 25 13:16 id
-r--r--r-- 1 root root  16 Oct 25 13:16 locator
-r--r--r-- 1 root root  16 Oct 25 13:16 r_address
-r--r--r-- 1 root root  12 Oct 25 13:16 r_id
-r--r--r-- 1 root root  16 Oct 25 13:16 r_locator
-r--r--r-- 1 root root  32 Oct 25 13:16 type
-r--r--r-- 1 root root  12 Oct 25 13:17 type_number
-r--r--r-- 1 root root   7 Oct 25 13:17 version

humidity:

# ls -l /tmp/1-wire/EF.A05F20150000/
total 0
-r--r--r-- 1 root root  16 Oct 25 13:16 address
-rw-rw-rw- 1 root root 256 Oct 25 13:16 alias
-r--r--r-- 1 root root   2 Oct 25 13:16 crc8
-r--r--r-- 1 root root   2 Oct 25 13:16 family
-r--r--r-- 1 root root  12 Oct 25 13:16 id
-r--r--r-- 1 root root  16 Oct 25 13:16 locator
-r--r--r-- 1 root root  16 Oct 25 13:16 r_address
-r--r--r-- 1 root root  12 Oct 25 13:16 r_id
-r--r--r-- 1 root root  16 Oct 25 13:16 r_locator
-r--r--r-- 1 root root  32 Oct 25 13:16 type
-r--r--r-- 1 root root  12 Oct 25 13:18 type_number
-r--r--r-- 1 root root   7 Oct 25 13:18 version

I have both devices connected to a Hobby Board 4 channel hub.
I have tried running the owfs server from a Raspberry Pi running Archlinux and from a laptop running Fedora 19. However, I get exactly the same results.
I am successfully using other 1-wire devices on the network, so I don't thing there is any problems with the hardware.
Can any one confirm that they have successfully used these devices?

Thanks
David
------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Vincent Danjean | 19 Oct 09:15 2014
Picon

Re: Bugreport for ow-shell

  Hi,

On 18/10/2014 12:27, Mario Gruenwald wrote:
> Hi
> 
> I tested it. Same problem in new Versions.

So, I'm currently forwarding your mail to upstream developers.

  Regards,
     Vincent

> http://blaeser.vc-graz.ac.at/ow-shell-bug.png
> I changed at 10 a.m.
> 
> My installed versions:
> sabi:~> dpkg -l | grep 'ii  ow' | cut -c -50
> ii  ow-shell                              2.9p7-2 
> ii  owfs-common                           2.9p7-2 
> ii  owserver                              2.9p7-2 
> sabi:~>
> 
> regards,
> Mario
> 
> On 2014-10-17, Vincent Danjean wrote:
>> On 17/10/2014 08:48, Mario Gruenwald wrote:
>>> Hi
>>>
>>> Thanx. Unfortunately testing is not as easy as i hoped.
>>> When i add repositories to my sources.list.d/... i don't see the new 
>>> packages. I checked, what i already installed. The list of packages is
>>> ow-shell, owfs-common, owserver
>>>
>>> So my idea was to manually download and install, but i am on i386 
>>> architecture and i miss owserver, i see only owserver_2.9p7-1_amd64.deb
>>
>> The package has been accepted by ftpmaster. It will be available
>> very soon for all Debian architectures. So I will not rebuild it for i386
>> myself. Just wait a few hours.
>>   Note: 2.9p7-1 and 2.9pp7-2 have the same software so you can
>> test with whatever will be present on your Debian mirrors.
>>   Let me know (and the owfs dev list too) if the bug is fixed or not
>> in 2.9p7 once you test it.
>>
>>   Regards,
>>     Vincent
>>
>>> Thanx in advance for any future support.
>>>
>>> Regards,
>>> Mario
>>>
>>> On 2014-10-17, Vincent Danjean wrote:
>>>>   I forgot to add my personal repo to test new packages in the
>>>> previous mail
>>>>
>>>> On 17/10/2014 07:21, Vincent Danjean wrote:
>>>>>   Hi
>>>>>
>>>>> On 17/10/2014 00:05, Mario Gruenwald wrote:
>>>>>> Hi
>>>>>>
>>>>>> I tried reportbug and reportbug-ng, but it was too difficult for me. 
>>>>>> Therefore i write an simple Email.
>>>>>>
>>>>>> I have an USB-1wire-Adapter and some DS18S20 temprature sensors. After my 
>>>>>> last upgrade of ow-shell from 2.8p15-1 to 2.9p5-1.1 my temperature graphs had 
>>>>>> steps. You can see the effect in a graph at:
>>>>>>   http://blaeser.vc-graz.ac.at/1wire.png
>>>>>> After downgrade the problem disappeared. You can see it at
>>>>>>   http://blaeser.vc-graz.ac.at/ow-shell-bug.png
>>>>>> starting from 19:00.
>>>>>>
>>>>>> I guess it is the same problem as here:
>>>>>> http://developer.mbed.org/users/snatch59/notebook/onewirecrc/
>>>>>> citation begin -----
>>>>>> I have an DS1820 and my values looked quite the same.
>>>>>>
>>>>>> I think the problem is with the calculation of the enhanced 9bit calculation 
>>>>>> in  DS18S20::calculateTemperature(BYTE* data)
>>>>>
>>>>> Indeed, it seems similar to effects describe in comments.
>>>>>
>>>>>> The manual of my DS1820 says:
>>>>>>
>>>>>> "After reading the scratchpad, the TEMP_READ value is obtained by truncating 
>>>>>> the 0.5C bit (bit 0) from the temperature data..."
>>>>>>
>>>>>> This truncation was missing in the code.
>>>>>>
>>>>>> I extended like this - which can be done better, I'm sure :-)   :
>>>>>> citation end -----
>>>>>>
>>>>>> It would be cool, if you can fix the current package for jessie or guide me, 
>>>>>> where and how to report the problem.
>>>>>
>>>>> I just uploaded yesterday the last version (2.9p7). It is on my personnal
>>>>> repo (see my signature) or in the NEW/BYHAND QUEUE (new library packages).
>>>>>   Please look if these new packages fix your problem. Else, I'm putting
>>>>> owfs developers in copy so that they can try to fix this bug.
>>>>>
>>>>>   Regards,
>>>>>     Vincent
>>>>>
>>>>>> kindly regards
>>>>>> Mario
>>>>>>
>>>>>
>>>>
>>>> -- 
>>>> Vincent Danjean       GPG key ID 0xD17897FA         vdanjean <at> debian.org
>>>> GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
>>>> Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
>>>> APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main
>>>>
>>>
>>
> 

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho

Gmane