headers
Evgeny Chukreev | 1 May 2010 14:12
Picon

3 times

Hi!

I've captured signals from 1-wire during reading of power state. And
it seems that every command is repeated at least 3 times. For example,
if I ask owfs to get power state (parasite or external), the following
happens:

http://picasaweb.google.com/lh/photo/V9JsDBxer3sVuzQujVcj8Sd9AKoY2q_CkeQUyrpPAQQ?feat=directlink

So it is:
 Reset, Presence, Match rom (0x55), id (8 bytes), read power supply
(0xB4), response from device (0xFF or 0x00).
and this sequence is repeated 3 times before returning result to me.

Is it something OWFS does or is it DS9490?

Evgeny

------------------------------------------------------------------------------
Permalink | Reply | 2 comments |
headers
Paul Alfille | 1 May 2010 17:27
Picon

Re: 3 times

Thanks for investigating this!

It sounds like the normal triple repeat of a read in the case of an
error. It also sounds like an erroneous error return. Which slave are
you trying to read the power state from? DS18S10? DS2450? DS2406?...

Paul Alfille

On Sat, May 1, 2010 at 8:12 AM, Evgeny Chukreev
<evgeny.chukreev <at> gmail.com> wrote:
> Hi!
>
> I've captured signals from 1-wire during reading of power state. And
> it seems that every command is repeated at least 3 times. For example,
> if I ask owfs to get power state (parasite or external), the following
> happens:
>
> http://picasaweb.google.com/lh/photo/V9JsDBxer3sVuzQujVcj8Sd9AKoY2q_CkeQUyrpPAQQ?feat=directlink
>
> So it is:
>  Reset, Presence, Match rom (0x55), id (8 bytes), read power supply
> (0xB4), response from device (0xFF or 0x00).
> and this sequence is repeated 3 times before returning result to me.
>
> Is it something OWFS does or is it DS9490?
>
> Evgeny
>
> ------------------------------------------------------------------------------
> _______________________________________________
(Continue reading)

Permalink | Reply | 1 comment |
headers
Evgeny Chukreev | 1 May 2010 18:42
Picon

Re: 3 times

Sorry...

Forget this problem! It was a "stupid" program I used to read from
owfs file. I guess it accessed the file 3 times (once to get file
size, ..., next time to read data or something like this).

On Sat, May 1, 2010 at 6:27 PM, Paul Alfille <paul.alfille <at> gmail.com> wrote:
> Thanks for investigating this!
>
> It sounds like the normal triple repeat of a read in the case of an
> error. It also sounds like an erroneous error return. Which slave are
> you trying to read the power state from? DS18S10? DS2450? DS2406?...
>
> Paul Alfille
>
> On Sat, May 1, 2010 at 8:12 AM, Evgeny Chukreev
> <evgeny.chukreev <at> gmail.com> wrote:
>> Hi!
>>
>> I've captured signals from 1-wire during reading of power state. And
>> it seems that every command is repeated at least 3 times. For example,
>> if I ask owfs to get power state (parasite or external), the following
>> happens:
>>
>> http://picasaweb.google.com/lh/photo/V9JsDBxer3sVuzQujVcj8Sd9AKoY2q_CkeQUyrpPAQQ?feat=directlink
>>
>> So it is:
>>  Reset, Presence, Match rom (0x55), id (8 bytes), read power supply
>> (0xB4), response from device (0xFF or 0x00).
>> and this sequence is repeated 3 times before returning result to me.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael Pittelko | 1 May 2010 20:04
Favicon

Mac 10.6 and FreeBSD 8.0


A script went by a few weeks ago to get things building properly on Mac (which works fine with the latest p36
release, by the way) It seems that a proper fix for the libtool damage would be a bit easier on everyone.
Sadly, not much of a libtool expert, but was able to massage the libtool stuff with a bit of reconfiguration
and get things going.

Can't say that I know exactly what this fixed, but it does compile properly for the Mac, and much better for FreeBSD.

For the Mac....
I was able to relibtoolize, and get things working without being so invasive.

xx:owfs-2.7p36 mikep$ aclocal
xx:owfs-2.7p36 mikep$ glibtoolize -c -f				(yes, glibtoolize is right on the mac it appears)
glibtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `src/scripts/install'.
glibtoolize: copying file `src/scripts/install/ltmain.sh'
glibtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
glibtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
glibtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
glibtoolize: `AC_PROG_RANLIB' is rendered obsolete by `LT_INIT'
xx:owfs-2.7p36 mikep$ automake --add-missing
configure.ac:48: installing `src/scripts/install/config.sub'
configure.ac:48: installing `src/scripts/install/config.guess'
xx:owfs-2.7p36 mikep$ ./configure --disable-zero 
.
.
.
.
make -j2
.
.
(Continue reading)

Permalink | Reply | 2 comments |
headers
William Brown | 2 May 2010 07:43
Picon
Favicon

Re: DS9490 cannot be accessed?

Ahmed Theba wrote:
> Thanx for the reply...
>
> Running the command with sudo does not change anything,
> And this shouldnt matter as I am logged in as root?
>
> root <at> Mini:~# sudo /opt/owfs/bin/owfs u -m /mnt/1wire/
> DEFAULT: ow_ds9490.c:DS9490_sub_open(558) Opened USB DS9490 bus master 
> at 002/003.
> Could not open the USB bus master. Is there a problem with permissions?
> DEFAULT: ow_ds9490.c:DS9490_detect(314) Could not open the USB bus 
> master. Is there a problem with permissions?
> DEFAULT: owlib.c:SetupInboundConnections(178) Cannot open USB bus master
>
> Somehow I dont seem to have module(s) fuse, ds9490:
>
> root <at> MiniSnitch:~# modprobe -r ds9490r
> FATAL: Module ds9490r not found.
> root <at> MiniSnitch:~# modprobe -r ds9490
> FATAL: Module ds9490 not found.
> root <at> MiniSnitch:~# modprobe fuse
> FATAL: Module fuse not found.
This from a working system
 <at> Irry:~$ modprobe -r ds9490r
FATAL: Module ds9490r not found.
 <at> Irry:~$ modprobe fuse
FATAL: Module fuse not found.
 <at> Irry:~$

>
(Continue reading)

Permalink | Reply | 7 comments |
headers
William Brown | 2 May 2010 08:19
Picon
Favicon

Re: Mac 10.6 and FreeBSD 8.0

Michael Pittelko wrote:
> A script went by a few weeks ago to get things building properly on Mac (which works fine with the latest p36
release, by the way) It seems that a proper fix for the libtool damage would be a bit easier on everyone.
Sadly, not much of a libtool expert, but was able to massage the libtool stuff with a bit of reconfiguration
and get things going.
>
> Can't say that I know exactly what this fixed, but it does compile properly for the Mac, and much better for FreeBSD.
>
>
> For the Mac....
> I was able to relibtoolize, and get things working without being so invasive.
>
> xx:owfs-2.7p36 mikep$ aclocal
> xx:owfs-2.7p36 mikep$ glibtoolize -c -f				(yes, glibtoolize is right on the mac it appears)
> glibtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `src/scripts/install'.
> glibtoolize: copying file `src/scripts/install/ltmain.sh'
> glibtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
> glibtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
> glibtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> glibtoolize: `AC_PROG_RANLIB' is rendered obsolete by `LT_INIT'
> xx:owfs-2.7p36 mikep$ automake --add-missing
> configure.ac:48: installing `src/scripts/install/config.sub'
> configure.ac:48: installing `src/scripts/install/config.guess'
> xx:owfs-2.7p36 mikep$ ./configure --disable-zero 
> .
> .
> .
> .
> make -j2
> .
(Continue reading)

Permalink | Reply | 1 comment |
headers
Paul Alfille | 2 May 2010 12:54
Picon

Re: Mac 10.6 and FreeBSD 8.0

cp /usr/bin/libtool owfs/src/scripts/install/ltmain.sh

If I knew how t fix it, I would!

On Sun, May 2, 2010 at 2:19 AM, William Brown <mahiwai <at> earthlink.net> wrote:
> Are you compiling from cvs? If so fix libtool after bootstrap. I have
> not gotten libtoolize to work correctly on Ubuntu for OWFS so can't
> instruct.  I copy libtool from bin to owfs dir, search the archives for
> the exact location.

------------------------------------------------------------------------------
Permalink | Reply | 0 comments |
headers
Mick Sulley | 2 May 2010 19:35

DS18S20 Questions

Hi,

I have a few questions regarding DS18S20.

I am using pwowfs to read the data.  Among the parameters it can read is
'present', but how can this return anything other than 1?  If the device
is not present then the read fails.  Have I missed something here?

I need to read the state of a pressure switch, just an on/off contact.
I looked for a 1-wire sensor to connect it to, but then I thought that
as DS18S20's are so cheap I could use one of those, connect in series
with the signal line and if the device reads then the pressure switch
contact is closed, if it doesn't read then the contact is open.  Any
problems with this idea?  Is there a better way to do it?

As part of these investigations it seems to me that the parameter
'power' does not actually mean that the device has external power, it
means that the ground lead is not connected to the VDD (+5v) lead.  Can
anyone confirm this?

Thanks

Mick Sulley

------------------------------------------------------------------------------
Permalink | Reply | 4 comments |
headers
Paul Alfille | 2 May 2010 20:53
Picon

Re: DS18S20 Questions

Great questions!

On Sun, May 2, 2010 at 1:35 PM, Mick Sulley <mick <at> sulley.info> wrote:
> Hi,
>
> I have a few questions regarding DS18S20.
>
> I am using pwowfs to read the data.  Among the parameters it can read is
> 'present', but how can this return anything other than 1?  If the device
> is not present then the read fails.  Have I missed something here?

Good pick up. 'present' is a historical artifact. Early design didn't
check the existence of a device before trying to read from it. This
meant that you could ask for /10.CD1B23000000/type and get the
response "DS18S20" even though the chip wasn't present.

We now key everything to the actual existence of the chip, so that
query reads "Data Error"

 I'll hide this property and mark it as deprecated.

>
> I need to read the state of a pressure switch, just an on/off contact.
> I looked for a 1-wire sensor to connect it to, but then I thought that
> as DS18S20's are so cheap I could use one of those, connect in series
> with the signal line and if the device reads then the pressure switch
> contact is closed, if it doesn't read then the contact is open.  Any
> problems with this idea?  Is there a better way to do it?

Early designs of the weather vane direction used your idea with 8
(Continue reading)

Permalink | Reply | 3 comments |
headers
Marc MERLIN | 2 May 2010 21:45

Re: Hobby Board's Moisture Meter is super temperature dependent

On Thu, Apr 29, 2010 at 01:48:05PM -0700, Marc MERLIN wrote:
> > In my case a dry sensor at 21.65C measure a current of -0.129375
> > The supply voltage is measured at 4.8V
> 
> Short version:
> Paul, do you think you could talk to Eric on producing a "moisture"
> variable that is based on the current value and temperature corrected?
> 
> I ran a test where I had a fully wet sensor, I took it out of the glass
> of water, put it in a warmer place (5C warmer at most) and the current
> value went from -1.38687 all the way to -1.45187 just because of the
> temperature rise.
> Eventually things stabilized and the humidity went down again as the
> sensor started drying up further.

I did more tests this weekend.
First question was: does the temperature of the measuring board affect the
moisture current readout?
Answer: not a whole lot. Temperature changes caused barely noticeable
increase of current readings, at the level of noise, really.

Second question. How about the probe temperature?
Oh boy, the probe temperature when wet gave me reading changes over
50%(!) just based on the water temperature.

             current  board temp (F)
wet icy:     -1.13    70.475
wet ambiant: -1.3825  70.025
wet warm:    -1.72063 70.7
(Continue reading)

Permalink | Reply | 2 comments |

Gmane