I would suggest that you move the adapter to ttyS0, which should be the 
built-in serial port with a 'real' UART and see how it works there. 
Eliminate any USB vagueness.

The ttyS2 you are using is USB. I know from professional experience that 
there are differences in USB serial implementations that can cause 
quirkiness. Sometimes the drivers get unloaded, the system goes into 
power saving mode (not necessarily sleep) and powers down the USB 
device, or a number of other things can happen.

If you then move back to the USB serial device and this happens again, 
do a 'lsusb' and make sure the device still shows up. Do a 'lsmod' and 
make sure the kernel module is still loaded.

Paul

On 1/31/2011 7:55 AM, Mick Sulley wrote:
> OK it just happened again.  Started my python program and it failed
> with
> DEFAULT: ow_reconnect.c:TestConnection(52) Failed to reconnect DS9097
> bus master!
>
> In a terminal I ran
> owhttpd -p 3001 -d /dev/ttyS2 --debug
>
> and this gave me
>
> CONNECT: ow_avahi_link.c:OW_Load_avahi_library(72) No Avahi support.
> Library libavahi-client couldn't be loaded
> CONNECT: ow_dnssd.c:OW_Load_dnssd_library(136) Zeroconf/Bonjour is
> disabled since dnssd library isn't found
>     CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[]
>    DEBUG: owlib.c:SetupTemperatureLimits(79) Globals temp limits 0C 100C
> (for simulated adapters)
>    DEBUG: ow_ds9097U.c:DS2480_initialize_repeatedly(259) Attempt #0 to
> initialize the DS9097U
>    DEBUG: ow_ds9097U.c:DS2480_big_reset_serial(337) Send the initial
> reset to the bus master.
>    DEBUG: ow_ds9097U.c:DS2480_configuration_read(467) wrong response (70
> not 00)
>    DEBUG: ow_ds9097U.c:DS2480_set_baud_control(488) Failed first attempt
> at resetting baud rate of bus master /dev/ttyS2
>    DEBUG: ow_ds9097U.c:DS2480_configuration_read(467) wrong response (70
> not 00)
>    DEBUG: ow_ds9097U.c:DS2480_set_baud_control(493) Failed second attempt
> at resetting baud rate of bus master /dev/ttyS2
>    DEBUG: ow_ds9097U.c:DS2480_configuration_read(467) wrong response (70
> not 00)
>    DEBUG: ow_ds9097U.c:DS2480_set_baud_control(488) Failed first attempt
> at resetting baud rate of bus master /dev/ttyS2
>    DEBUG: ow_ds9097U.c:DS2480_configuration_read(467) wrong response (70
> not 00)
>    DEBUG: ow_ds9097U.c:DS2480_set_baud_control(493) Failed second attempt
> at resetting baud rate of bus master /dev/ttyS2
>    DEBUG: ow_ds9097U.c:DS2480_configuration_write(451) wrong response (CD
> not 44)
>    DEBUG: ow_ds9097U.c:DS2480_big_reset_serial(337) Send the initial
> reset to the bus master.
>    DEBUG: ow_ds9097U.c:DS2480_configuration_read(467) wrong response (70
> not 00)
>    DEBUG: ow_ds9097U.c:DS2480_set_baud_control(488) Failed first attempt
> at resetting baud rate of bus master /dev/ttyS2
>    DEBUG: ow_ds9097U.c:DS2480_configuration_read(467) wrong response (70
> not 00)
>    DEBUG: ow_ds9097U.c:DS2480_set_baud_control(493) Failed second attempt
> at resetting baud rate of bus master /dev/ttyS2
>    DEBUG: ow_ds9097U.c:DS2480_configuration_read(467) wrong response (70
> not 00)
>    DEBUG: ow_ds9097U.c:DS2480_set_baud_control(488) Failed first attempt
> at resetting baud rate of bus master /dev/ttyS2
>    DEBUG: ow_ds9097U.c:DS2480_configuration_read(467) wrong response (70
> not 00)
>    DEBUG: ow_ds9097U.c:DS2480_set_baud_control(493) Failed second attempt
> at resetting baud rate of bus master /dev/ttyS2
>    DEBUG: ow_ds9097U.c:DS2480_configuration_write(451) wrong response (CD
> not 44)
>
>
> I opened up a browser on http://localhost:3001/ and it says unable to
> connect.
>
> The serial port looks OK
> mick@mick-desktop:~$ dmesg | grep tty
> [    0.000000] console [tty0] enabled
> [    0.489257] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> [    0.489554] 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> [   14.681524] 0000:03:07.0: ttyS1 at I/O 0xdf00 (irq = 17) is a 16550A
> [   14.681616] 0000:03:07.0: ttyS2 at I/O 0xde00 (irq = 17) is a 16550A
> mick@mick-desktop:~$
>
>
> I then rebooted and it all works fine!
>
> Any idea what could cause this problem?
>
> Thanks
>
> Mick
>
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Owfs-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>


------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to