Hello Paul,
Thanks for the reply.
On Fri, 28 May 2010 23:40:54 +0100, Paul Alfille <[email protected]>
wrote:
> I'll need to test my own device to match your findings, but two initial
> thoughts:
>
> 1. You are attempting to attach to 2 devices, another owserver, and the
> LinkUSB. I suspect you want owserver -p 4304 --link=/dev/ttyUSB0
I'm unsure what you mean here. I only have one 1-wire interface adapter,
and
one instance of owserver running.
> 2. Can you try as root to test?
The debug lines I posted were the result of running as root.
> 3. What's your platform. The FTDI USB/serial module is a little
> problematic
> in some older devices.
2 different machines. both Gentoo. kernel 2.6.28. owfs-2.7_p21.
> In theory, you can point a communication program (e.g. minicom) at
> /dev/ttyUSB0 and try the straight ascii commands like "h" or " " to see a
> human-readably response.
Well, tried this before. A bit interesting...
output the first time is:
Welcome to minicom 2.3
OPTIONS:
Compiled on Jun 2 2009, 15:47:08.
Port /dev/ttyUSB0
Press CTRL-A Z for help on special keys
R<?LinkUSB V1.44
0LinkUSB V1.4
0LinkUSB V1.4
??LinkUSB V1.4
PinkUSB V1.4
Note: this is *exactly* as I get it, without giving any keyboard input.
There is nothing plugged in to the 1-wire bus at this time.
Device responds to the 'h' command as expected.
Leaving minicom via CTRL-A, Q, and not "resetting the modem" allows me
to repeat the above. Leaving via CTRL-A, X leaves the device unresponsive.
To get it to respond again involves unplugging the device, doing
rmmod ftdi_sio, then rmmod usbserial, then plugging back in again.
On a seperate machine, I get the following:
> owserver -d /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=[]
DEFAULT: ow_com.c:COM_open(42) [Input/output error] Cannot open port:
/dev/ttyUSB0
CONNECT: owlib.c:SetupInboundConnections(110) Cannot detect DS2480 or LINK
interface on /dev/ttyUSB0.
DEFAULT: ow_com.c:COM_open(42) [Input/output error] Cannot open port:
/dev/ttyUSB0
DEFAULT: owlib.c:SetupInboundConnections(121) Cannot detect DS9097
(passive) interface on /dev/ttyUSB0.
DEBUG: owserver.c:main(158) main_threadid = 3085346496
DEBUG: ow_net_server.c:ServerProcessOut(252) 3084983184
DEBUG: ow_net_server.c:ServerProcess(320) Wait for output device 0 to
setup.
DEBUG: ow_zero.c:OW_Announce(150) end
DEBUG: ow_net_server.c:ServerProcessOut(272) Output device setup is
done. index=0
DEBUG: ow_net_server.c:ServerProcess(323) Output device 0 setup done.
DEBUG: ow_net_server.c:ServerProcessAccept(189) [3084983184] try lock 0
DEBUG: ow_net_server.c:ServerProcessAccept(195) [3084983184] locked 0
> owserver --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=[]
DEFAULT: ow_com.c:COM_open(42) [Input/output error] Cannot open port:
/dev/ttyUSB0
CONNECT: owlib.c:SetupInboundConnections(174) Cannot open LINK adapter at
/dev/ttyUSB0
DEBUG: owserver.c:main(158) main_threadid = 3083564736
DEBUG: ow_net_server.c:ServerProcessOut(252) 3083201424
DEBUG: ow_net_server.c:ServerProcess(320) Wait for output device 0 to
setup.
DEBUG: ow_zero.c:OW_Announce(150) end
DEBUG: ow_net_server.c:ServerProcessOut(272) Output device setup is
done. index=0
DEBUG: ow_net_server.c:ServerProcess(323) Output device 0 setup done.
DEBUG: ow_net_server.c:ServerProcessAccept(189) [3083201424] try lock 0
DEBUG: ow_net_server.c:ServerProcessAccept(195) [3083201424] locked 0
and minicom behaves the same way...
------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
