Well I was wrong, started getting these messages with DS9097U

Jan 16 12:16:13 Irry OWFS[4125]: DS9097U adapter reconnected 
Jan 16 12:30:29 Irry OWFS[4125]: 1-wire bus short circuit. 
Jan 16 12:31:31 Irry dhclient: DHCPREQUEST of 192.168.0.54 on eth0 to 
192.168.0.1 port 67
Jan 16 12:31:31 Irry dhclient: DHCPACK of 192.168.0.54 from 192.168.0.1
Jan 16 12:31:31 Irry dhclient: bound to 192.168.0.54 -- renewal in 1684 
seconds.
Jan 16 12:31:37 Irry OWFS[4125]: DS9097U adapter reconnected 
Jan 16 12:37:46 Irry OWFS[4127]: TIMEOUT after 0 bytes 
Jan 16 12:46:41 Irry OWFS[4125]: DS9097U adapter reconnected 
Jan 16 12:59:35 Irry dhclient: DHCPREQUEST of 192.168.0.54 on eth0 to 
192.168.0.1 port 67
Jan 16 12:59:35 Irry dhclient: DHCPACK of 192.168.0.54 from 192.168.0.1
Jan 16 12:59:35 Irry dhclient: bound to 192.168.0.54 -- renewal in 1602 
seconds.
Jan 16 13:01:18 Irry OWFS[4125]: DS9097U adapter reconnected 
Jan 16 13:16:24 Irry OWFS[4125]: DS9097U adapter reconnected 
Jan 16 13:26:17 Irry dhclient: DHCPREQUEST of 192.168.0.54 on eth0 to 
192.168.0.1 port 67
Jan 16 13:26:17 Irry dhclient: DHCPACK of 192.168.0.54 from 192.168.0.1
Jan 16 13:26:17 Irry dhclient: bound to 192.168.0.54 -- renewal in 1559 
seconds.
Jan 16 13:37:09 Irry OWFS[4125]: DS9097U adapter reconnected 
Jan 16 13:46:36 Irry OWFS[4125]: DS9097U adapter reconnected 
Jan 16 13:52:16 Irry dhclient: DHCPREQUEST of 192.168.0.54 on eth0 to 
192.168.0.1 port 67
Jan 16 13:52:16 Irry dhclient: DHCPACK of 192.168.0.54 from 192.168.0.1
Jan 16 13:52:16 Irry dhclient: bound to 192.168.0.54 -- renewal in 1504 
seconds.
Jan 16 14:00:52 Irry OWFS[4125]: DS9097U adapter reconnected 

I'm especially interested in what this message is trying to tell me, it 
shows up occasionally, but readings are present:
   
    Jan 16 12:30:29 Irry OWFS[4125]: 1-wire bus short circuit. 


William Brown wrote:
> This problem seems to only happen with the usb adapter DS9490.  When I 
> switched to my serial adapter DS9097U these errors stopped.
>
>
> William Brown wrote:
>   
>> I have things sorted out and owhttpd is reporting correctly but my 
>> daemon.log messages are like this (10 minutes worth)
>>
>>
>> Jan 15 19:58:56 Irry OWFS[30961]: TIMEOUT after 0 bytes 
>> Jan 15 19:59:14 Irry OWFS[4152]: Bad Adapter adapter reconnected 
>> Jan 15 19:59:49 Irry last message repeated 3 times
>> Jan 15 20:01:03 Irry last message repeated 11 times
>> Jan 15 20:01:04 Irry last message repeated 2 times
>> Jan 15 20:01:24 Irry OWFS[30961]: TIMEOUT after 0 bytes 
>> Jan 15 20:01:38 Irry OWFS[4152]: Bad Adapter adapter reconnected 
>> Jan 15 20:01:41 Irry last message repeated 2 times
>> Jan 15 20:03:00 Irry last message repeated 6 times
>> Jan 15 20:04:10 Irry last message repeated 5 times
>> Jan 15 20:05:07 Irry last message repeated 5 times
>> Jan 15 20:05:49 Irry last message repeated 2 times
>> Jan 15 20:07:06 Irry last message repeated 3 times
>> Jan 15 20:08:09 Irry last message repeated 2 times
>> Jan 15 20:09:05 Irry OWFS[4152]: Bad Adapter adapter reconnected 
>> Jan 15 20:10:03 Irry last message repeated 3 times
>>
>>
>> Paul Alfille wrote:
>>   
>>     
>>> Ok, so the current problem is that you get many "reconnects" in the log?
>>>
>>> Paul
>>>
>>> On Wed, Jan 14, 2009 at 8:00 AM, Michael Markstaller <[email protected] 
>>> <mailto:[email protected]>> wrote:
>>>
>>>     Paul,
>>>
>>>     just to make sure, I mentioned the w1 driver only to state clearly
>>>     that I don't currently use it (blacklisted), so in my case it's
>>>     definitely not loaded or used.
>>>
>>>     regards Michael
>>>
>>>     > -----Original Message-----
>>>     > From: Paul Alfille [mailto:[email protected]
>>>     <mailto:[email protected]>]
>>>     > Sent: Wednesday, January 14, 2009 12:47 PM
>>>     > To: [email protected]
>>>     <mailto:[email protected]>
>>>     > Subject: Re: [Owfs-developers] Problem with DS9490R on longer
>>>     networks
>>>     >
>>>     > w1 is the linux kernel system for 1-wire. It grabs certain of
>>>     > the bus masters (the USB one in particular). As root, OWFS
>>>     > will unload the ds2490 kernel module and use libusb to
>>>     > connect. You can unload it yourself, or suppress it's loading
>>>     > with udev magic.
>>>     >
>>>     > That actually might be part of the problem, and an
>>>     > interesting issue. Perhaps the USB line is getting reset (bad
>>>     > connection, other error, ...) Although owfs tries to
>>>     > reconnect to the DS490, it doesn't try unloading the module
>>>     > again. I'll investigate.
>>>     >
>>>     > Note that we are nearly done building the owfs-w1 bridge
>>>     > which will make using w1 as a bus master possible.
>>>     >
>>>     > Paul Alfille
>>>     >
>>>     >
>>>
>>>     
>>> ------------------------------------------------------------------------------
>>>     This SF.net email is sponsored by:
>>>     SourcForge Community
>>>     SourceForge wants to tell your story.
>>>     http://p.sf.net/sfu/sf-spreadtheword
>>>     _______________________________________________
>>>     Owfs-developers mailing list
>>>     [email protected]
>>>     <mailto:[email protected]>
>>>     https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by:
>>> SourcForge Community
>>> SourceForge wants to tell your story.
>>> http://p.sf.net/sfu/sf-spreadtheword
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Owfs-developers mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>>   
>>>     
>>>       
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>> _______________________________________________
>> Owfs-developers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>>   
>>     
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Owfs-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>   


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to