On Tue, May 25, 2010 at 7:55 AM, Phil <[email protected]> wrote:
> Hi all,
>
> Having problems setting up - I'd be grateful for a pointer or two in the
> correct direction...
>
> Brand new LinkUSB interface:
>
> dmesg
> usb 3-2:1.0: uevent
> usbserial_generic 3-2:1.0: usb_probe_interface
> usbserial_generic 3-2:1.0: usb_probe_interface - got id
> ftdi_sio 3-2:1.0: usb_probe_interface
> ftdi_sio 3-2:1.0: usb_probe_interface - got id
> ftdi_sio 3-2:1.0: FTDI USB Serial Device converter detected
> usb 3-2: Detected FT232RL
> usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB0
> drivers/usb/core/inode.c: creating file '008'
> usb 3-2: New USB device found, idVendor=0403, idProduct=6001
> usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 3-2: Product: FT232R USB UART
> usb 3-2: Manufacturer: FTDI
> usb 3-2: SerialNumber: A800aZxd
>
> However, I cannot connect to it.
> Permissions are OK, i believe...
>
>
Under Ubuntu I had to explicitly load the module:
sudo insmod ftdi_sio
If I unplug and plug the LinkUSB I get (from dmesg)
[609124.498641] usb 1-4.4: USB disconnect, address 28
[609124.499082] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now
disconnected from ttyUSB0
[609124.499095] ftdi_sio 1-4.4:1.0: device disconnected
[609125.740900] usb 1-4.3: new full speed USB device using ehci_hcd and
address 29
[609125.858859] usb 1-4.3: configuration #1 chosen from 1 choice
[609126.126764] ftdi_sio 1-4.3:1.0: FTDI USB Serial Device converter
detected
[609126.129100] usb 1-4.3: Detected FT232RL
[609126.129173] usb 1-4.3: FTDI USB Serial Device converter now attached to
ttyUSB0
But not the drivers/usb/code/inode.c... lines that follow
ls -la /dev/ttyUSB0
> crwxrwxrwx 1 root uucp 188, 0 2010-05-25 11:08 /dev/ttyUSB0
>
crw-rw---- 1 root dialout 188, 0 2010-05-29 09:10 /dev/ttyUSB0
>
> The following is the response I get when attempting to start the server.
> What am I failing to do?
>
> owserver -s 127.0.0.1:4304 --link=/dev/ttyUSB0 --foreground --error_level
> 5
> CALL: ow_parsename.c:FS_ParsedName_anywhere(109) path=[]
> DEBUG: owlib.c:SetupTemperatureLimits(83) Globals temp limits 0C 100C
> (for simulated adapters)
> CALL: ow_parsename.c:FS_ParsedName_anywhere(109) path=[]
> DEBUG: ow_link.c:LINK_reset(204) ok, devices Not present
> DEBUG: ow_link.c:LINK_detect(99) Checking LINK version
> CONNECT: ow_com_read.c:COM_read(72) Timeout error (read) serial port:
> /dev/ttyUSB0
> DEFAULT: ow_link.c:LINK_detect(124) LINK detection error
> CONNECT: owlib.c:SetupInboundConnections(174) Cannot open LINK adapter at
> /dev/ttyUSB0
> DEBUG: ow_com.c:COM_close(80) COM_close: flush
> DEBUG: ow_com.c:COM_close(82) COM_close: restore
> DEBUG: ow_com.c:COM_close(86) COM_close: close
> DEBUG: owserver.c:main(158) main_threadid = 3084814016
> DEBUG: ow_net_server.c:ServerProcess(320) Wait for output device 0 to
> setup.
> DEBUG: ow_net_server.c:ServerProcessOut(252) 3084811152
> DEBUG: ow_net_server.c:ServerProcessOut(272) Output device setup is
> done. index=0
> DEBUG: ow_net_server.c:ServerProcessAccept(189) [3084811152] try lock 0
> DEBUG: ow_net_server.c:ServerProcessAccept(195) [3084811152] locked 0
> DEBUG: ow_net_server.c:ServerProcess(323) Output device 0 setup done.
>
>
For me:
$ sudo /opt/owfs/bin/owserver --link=/dev/ttyUSB0 --foreground
--error_level=5
CALL: ow_parsename.c:FS_ParsedName_anywhere(96) path=[]
DEBUG: owlib.c:SetupTemperatureLimits(79) Globals temp limits 0C 100C (for
simulated adapters)
CALL: ow_parsename.c:FS_ParsedName_anywhere(96) path=[]
DEBUG: ow_link.c:LINK_serial_detect(191) Checking LINK version
CONNECT: ow_com_read.c:COM_read(72) Timeout error (read) serial port:
/dev/ttyUSB0
DEBUG: ow_link.c:LinkVersion_knownstring(117) Link version Found 1.4
DEBUG: ow_link.c:LINK_set_baud(270) to 9600
DEBUG: ow_link.c:LINK_reset(355) bad, Unknown LINK response L
DEBUG: ow_reset.c:BUS_reset(36) Reset error. Reconnection 1/2
DEBUG: owserver.c:main(150) main_threadid = 139889281836784
DEBUG: ow_zero.c:ZeroConf_Announce(150) end
But testing is successful. It works fine.
---------------------
Note using your command line of owserver -s 127.0.0.1:4304--link=/dev/ttyUSB0
also works, but you are asking this owserver to CONNECT to another owserver
(the "s" argument) rather than BE the owserver in port 4304 ("p" argument).
Fortunately, owserver has safeguards to prevent infinite recursion.
---------------------
I'm a little stymied at what the difference in our experience here is. The
slightly different dmesg response makes me wonder if there isn't another
kernel module interfering.
Paul Alfille
------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
