headers
William Brown | 1 May 2011 10:42
Picon
Favicon

Re: I/O relay board from Hobby Boards

When I start owserver it has a list of devices which it checks for 
presence. This list always has the same devices whether they are 
connected to the bus or not. The I/O relay board is never in this list 
even after successful connection to bus. Where can I find this list of 
devices owserver uses and what is it? Is it a problem that the list of 
devices is incorrect?

On 04/28/2011 03:24 PM, William Brown wrote:
> I've attached the log after running owhttpd two times using 
> errorlevel=9. Once without moisture meter and with I/O boards. The I/O 
> relay board is found. Then I connected the moisture meter and ran 
> owhttpd a second time. Only the moisture meter is found, not the I/O 
> relay. There were no messages generated when I connected the moisture 
> meter.  Still looking for ways to resolve this. thanks william
>
> On 04/24/2011 01:37 PM, William Brown wrote:
>> So I am back again with my I/O board problem from before. It has the
>> DS2408 chip. Eric checked the board for me and found it working
>> correctly. When I add the I/O board and the moisture meter (DS2760 chip)
>> to the 1wire bus (both from Hobby Boards) I have this problem.The DS2760
>> is available from owhttpd and ownet.php but the DS2408 is dropped from
>> the bus listing and is not accessible. When I remove the DS2760 from the
>> 1wire bus the DS2408 is back again and accessible. These 2 boards worked
>> on the same bus in earlier versions of owfs, I don't remember which but
>> have had problems for several versions recently.
>>
>> I need some suggestions on how to debug this problem. I have owtraffic
>> enabled but debuglevel is set at 1. I am not getting any error messages.
>>
>> ------------------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 3 comments |
headers
William Brown | 1 May 2011 11:09
Picon
Favicon

Re: I/O relay board from Hobby Boards

Does this have something to do with the device table? See the middle 
section where adding directory for 0.

Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG: 
ow_ds9097U.c:DS2480_next_both(697) SN found: 29 9D 6D 04 00 00 00 2B
Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG: ow_search.c:BUS_next(71) 
Device found: 29 9D 6D 04 00 00 00 2B
Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG: 
ow_cache.c:Cache_Add_Device(539) Adding device location 29 9D 6D 04 00 
00 00 2B bus=0
Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG: 
ow_cache.c:Cache_Add_Common(624) Add to cache sn 29 9D 6D 04 00 00 00 2B 
pointer=0xb779b718 index=0 size=4
Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG: 
ow_cache.c:Cache_Add_Device(539) Adding device location 29 9D 6D 04 00 
00 00 2B bus=0
Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG: 
ow_cache.c:Cache_Add_Common(624) Add to cache sn 29 9D 6D 04 00 00 00 2B 
pointer=0xb779b718 index=0 size=4
Apr 30 19:55:08 Irry OWFS[2335]:    CALL: 
ow_parsename.c:FS_ParsedName_anywhere(95) path=[/29.9D6D04000000]
Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG: 
ow_cache.c:Cache_Get_Device(893) Looking for device 29 9D 6D 04 00 00 00 2B
Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG: 
ow_cache.c:Cache_Get_Common(1049) Search in cache sn 29 9D 6D 04 00 00 
00 2B pointer=0xb779b718 index=0 size=4
Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG: 
ow_cache.c:Cache_Get_Common(1065) Value found in cache. Remaining life: 
120 seconds.
Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG:
(Continue reading)

Permalink | Reply | 1 comment |
headers
Paul Alfille | 2 May 2011 03:54
Picon

Re: I/O relay board from Hobby Boards

So it looks like you have a

Family 29
DS2408

Family 20
DS2450

Family 26
DS2438

Family 10
DS18S20

Adding Moisture meter:

Family 30
DS2760

DS2450, DS18S20 DS2438 and DS2760 are still seen. DS2408 now not seen.

My first thought is a hardware (signal) problem. You could try
digitemp (it doesn't support many of these chips, but it does do a
walk-through mode showing the slaves attached.) I'm not sure which
bus-master you are using, but the USB and serial are supported by
digitemp.

Another thought is to try with the actual moisture sensor
disconnected, since there have been ground-loop issues reported with
some of the moisture sensors.
(Continue reading)

Permalink | Reply | 6 comments |
headers
Paul Alfille | 2 May 2011 04:00
Picon

Re: I/O relay board from Hobby Boards

Actually, OWFS does an initial bus search (for the USB bus-master
only) to find a family 81 slave to use as a unique identifier.

Just as a test, can you try with --usb_flextime and --usb_regulartime
to see if it's a timing issue?

Paul

On Sun, May 1, 2011 at 4:42 AM, William Brown <mahiwai <at> earthlink.net> wrote:
> When I start owserver it has a list of devices which it checks for
> presence. This list always has the same devices whether they are
> connected to the bus or not. The I/O relay board is never in this list
> even after successful connection to bus. Where can I find this list of
> devices owserver uses and what is it? Is it a problem that the list of
> devices is incorrect?
>
>

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
Permalink | Reply | 0 comments |
headers
Paul Alfille | 2 May 2011 04:03
Picon

Re: I/O relay board from Hobby Boards

No, the directory is cached (as well as the individual devices). The
directory is identified by bus number, and root device (0x000000000
for root, and 1F.2341234134 for DS2409 main and aux directories). I
realise it looks strange and confused me for a minute, too.

On Sun, May 1, 2011 at 5:09 AM, William Brown <mahiwai <at> earthlink.net> wrote:
> Does this have something to do with the device table? See the middle
> section where adding directory for 0.
>
>
> Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG:
> ow_ds9097U.c:DS2480_next_both(697) SN found: 29 9D 6D 04 00 00 00 2B
> Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG: ow_search.c:BUS_next(71)
> Device found: 29 9D 6D 04 00 00 00 2B
> Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG:
> ow_cache.c:Cache_Add_Device(539) Adding device location 29 9D 6D 04 00
> 00 00 2B bus=0
> Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG:
> ow_cache.c:Cache_Add_Common(624) Add to cache sn 29 9D 6D 04 00 00 00 2B
> pointer=0xb779b718 index=0 size=4
> Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG:
> ow_cache.c:Cache_Add_Device(539) Adding device location 29 9D 6D 04 00
> 00 00 2B bus=0
> Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG:
> ow_cache.c:Cache_Add_Common(624) Add to cache sn 29 9D 6D 04 00 00 00 2B
> pointer=0xb779b718 index=0 size=4
> Apr 30 19:55:08 Irry OWFS[2335]:    CALL:
> ow_parsename.c:FS_ParsedName_anywhere(95) path=[/29.9D6D04000000]
> Apr 30 19:55:08 Irry OWFS[2335]:   DEBUG:
> ow_cache.c:Cache_Get_Device(893) Looking for device 29 9D 6D 04 00 00 00 2B
(Continue reading)

Permalink | Reply | 0 comments |
headers
William Brown | 2 May 2011 05:17
Picon
Favicon

Re: I/O relay board from Hobby Boards

Adapter is DS9097U and  --usb_regulartime is already enable. My moisture 
meter uses a leaf moisture probe and is not buried in the ground, it's 
that little circuit board with etching. Digitemp sees all devices correctly.

On 05/01/2011 03:54 PM, Paul Alfille wrote:
> So it looks like you have a
>
> Family 29
> DS2408
>
> Family 20
> DS2450
>
> Family 26
> DS2438
>
> Family 10
> DS18S20
>
> Adding Moisture meter:
>
> Family 30
> DS2760
>
> DS2450, DS18S20 DS2438 and DS2760 are still seen. DS2408 now not seen.
>
> My first thought is a hardware (signal) problem. You could try
> digitemp (it doesn't support many of these chips, but it does do a
> walk-through mode showing the slaves attached.) I'm not sure which
> bus-master you are using, but the USB and serial are supported by
(Continue reading)

Permalink | Reply | 5 comments |
headers
Alex Shepherd | 2 May 2011 05:44
Picon

Can temploggerd handle Electricity Meters via a DS2423

Hi Guys,

I've finally got a DS2423 (Hobby-Boards Dual Counter) based node counting
LED flashes on my electricity meters. Both counters.A and counters.B are
counting LED flashes as I have 2 meters.

So next step is to try and log this information somewhere. 

Currently I'm appending reading every minute to a CSV file from a simple
CRON job.

I have temploggerd handling all my temperature sensors already so I wondered
if it can it handle these counters at all? The config file has hints of
being able to handle different types of sensor types but I'm struggling to
find any good docs on how to configure it.

Any suggestions?

Regards

Alex Shepherd

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
Permalink | Reply | 0 comments |
headers
William Brown | 2 May 2011 08:30
Picon
Favicon

Re: I/O relay board from Hobby Boards

that should be --serial_regulartime not --usb-regulartime. I'll take a 
break now.

On 05/01/2011 05:17 PM, William Brown wrote:
> Adapter is DS9097U and  --usb_regulartime is already enable. My moisture
> meter uses a leaf moisture probe and is not buried in the ground, it's
> that little circuit board with etching. Digitemp sees all devices correctly.
>
>
> On 05/01/2011 03:54 PM, Paul Alfille wrote:
>> So it looks like you have a
>>
>> Family 29
>> DS2408
>>
>> Family 20
>> DS2450
>>
>> Family 26
>> DS2438
>>
>> Family 10
>> DS18S20
>>
>> Adding Moisture meter:
>>
>> Family 30
>> DS2760
>>
>> DS2450, DS18S20 DS2438 and DS2760 are still seen. DS2408 now not seen.
(Continue reading)

Permalink | Reply | 4 comments |
headers
Eloy Paris | 3 May 2011 20:51

Delayed LinkUSB detection

Hi Paul,

I am currently working on upgrading from 2.8p1 to 2.8p8. I have been 
running fine on 2.8p1 for several months (since July or last year). I 
had to patch 2.8p1 to force hardware flow control because otherwise 
owserver would not be able to talk to my LinkUSB in emulation mode.

I remember that back when I originally reported this problem you changed 
things so hardware flow control would be used if a first attempt using 
no flow control failed. That seems to be working. However, it takes a 
long time for the detection to succeed:

May  3 14:22:38 altamira OWFS[21715]:    CALL: 
ow_parsename.c:FS_ParsedName_anywhere(95) path=[]
May  3 14:22:38 altamira OWFS[21715]:   DEBUG: 
owlib.c:SetupTemperatureLimits(79) Globals temp limits 0C 100C (for sim
ulated adapters)
May  3 14:22:38 altamira OWFS[21715]:   DEBUG: 
ow_link.c:LINK_detect_serial(237) Slurp in initial bytes
May  3 14:22:38 altamira OWFS[21715]:   DEBUG: 
ow_link.c:LINK_version(298) Checking LINK version
May  3 14:22:38 altamira OWFS[21715]:   DEBUG: 
ow_tcp_read.c:tcp_read(64) attempt 1 bytes Time: 5.000000 seconds
May  3 14:22:43 altamira OWFS[21715]: CONNECT: 
ow_tcp_read.c:tcp_read(110) TIMEOUT after 0 bytes
May  3 14:22:43 altamira OWFS[21715]:   DEBUG: 
ow_tcp_read.c:tcp_read(64) attempt 1 bytes Time: 5.000000 seconds
May  3 14:22:48 altamira OWFS[21715]: CONNECT: 
ow_tcp_read.c:tcp_read(110) TIMEOUT after 0 bytes
(Continue reading)

Permalink | Reply | 3 comments |
headers
Alex Shepherd | 4 May 2011 00:03
Picon

Re: Delayed LinkUSB detection

I don't have a solution but a similar observation. I have also been trying
to get a LinkUSB going on my NSLU2 running OpenWRT 10.03 and owfs 2.8p1 and
I can't start owserver with:

	owserver --LINK /dev/ttyUSB0

Like I can on my Debian 6.0.1 Linux box. I have to use:

	owserver -d /dev/ttyUSB0 

The next release of owfs on OpenWRT looks to be 2.8p4 so hopefully whatever
is wrong with 2.8p1 has been sorted for 2.8p4

 Alex

> -----Original Message-----
> From: Eloy Paris [mailto:peloy <at> chapus.net]
> Sent: Wednesday, 4 May 2011 6:51 a.m.
> To: OWFS (One-wire file system) discussion and help
> Subject: [Owfs-developers] Delayed LinkUSB detection
> 
> Hi Paul,
> 
> I am currently working on upgrading from 2.8p1 to 2.8p8. I have been
> running fine on 2.8p1 for several months (since July or last year). I had
to
> patch 2.8p1 to force hardware flow control because otherwise owserver
> would not be able to talk to my LinkUSB in emulation mode.
> 
> I remember that back when I originally reported this problem you changed
(Continue reading)

Permalink | Reply | 2 comments |

Gmane