On 06/08/17 22:17, Martin Patzak (GMX) wrote:
On 04.08.2017 11:09, Johan Ström wrote:
Main reason for using the --link option would be the increased
performance by factor 2!
Not 100% correct. LinkUSB can be used through regular serial device
just fine without libftdi & libusb. However, if owfs is built with
libftdi and it is used instead of using a serial tty, the performance
is improved as Martin writes.
With "--link=/dev/ttyUSB0" it would access it as serial device (no
ftdi required).
With "--link=ftdi:XXX (XXX as per man page) it would use libftdi for
direct communication.
Ok, thanks Johan, for clearing this one up, which in turn got me
building from source and solving the issue.
This difference in accessing it in two separate modes was not
understood by me from reading the man-page.
Great that you got it working :) But man page could perhaps be improved
then. If you have any suggestions, please feel free to provide them
through a patch or on mailing list. Source is at
https://sourceforge.net/p/owfs/code/ci/master/tree/src/man/man1/device.1so
You could also try "--device=/dev/ttyUSB0" to use in "emulated
DS2408B-mode"
yes this works fine.
I had owfs 3.1p5 installed from a debian package.
So, when I tried to access the LinkUSB with option "i" using the USB
vendor and device number of the LinkUSB V1.7
sudo owserver --link=ftdi:i:0x0403:0x6001 --debug
I got no debug output at all. But an entry in syslog was found, that
the debian package had been build without ftdi option - well thats
unfortunate ;)
Did the owserver process stay alive after this? I usually run testing
with flags --foreground --fatal_debug to have all debug output on
stdout, and not daemonize.
There should be an util named owusbprobe which can help you to scan
devices and give some hints on how to address it.
Unrelated: do not run owserver with sudo. In this particular case
(ftdi), it might be an easy workaround for fixing the device
permissions. Besides that, there is no reason at all to run as root, and
is never recommended.
Don't remember from the top of my head, but you will need to chown/chgrp
some node in /dev/usb/something for that particular user. Not sure if
that was ever documented properly..
After *building the newest owserver* from git source 3.2p1 *with the
ftdi option enabled it works as expected* with LinkUSB V1.7 as well as
V1.4 (so far it runs - I did not have time to do performance tests)
here is the excerpt from the debug (note: the command is
owserver_LinkUSB because I built it with that name to keep the debian
packaged version separate)
/sudo owserver_LinkUSB --link=ftdi:i:0x0403:0x6001 --debug
...
DEBUG: ow_link.c:(218) Link version is unrecognized: LinkUSB V1.7
(but that's ok).
DEBUG: ow_net_server.c:(76) ServerAddr: [0.0.0.0] [4304]
/
So, again, thank you Johan for pointing out the detail with the ftdi
addressing scheme, which got me building from source which solved the
problem for me.
Great!
Of course, it does not explain why the access as serial device without
ftdi fails.
But maybe thats a moot point, since you might as well access it in
emulated DS2408B-mode, which works fine.
Just to be clear, which parameters are you using when it is not working
(and is this with latest version as well? or dependent on compile options?)?
Johan
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
