On 25/07/17 20:16, Martin Patzak (GMX) wrote:
>
>
>
> On 07/25/17 15:36, Marcus Priesch wrote:
>> ...
>> no, i dont see any extra things you need when talking to a linkusb in
>> native mode - it's also ascii, however maybe thats implemented
>> differently in owfs, because configure says something about using
>> libftdi for linkusb support - however, i have support compiled in.
> thanks for making the effort and checking this...
> I found on the github owfs site:
>
> /libftdi must be installed to use //LinkUSB
> /
> which I have installed... otherwise you would get an error.
>
> 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.
You could also try "--device=/dev/ttyUSB0" to use in "emulated DS2408B-mode"
As to why it is not working, no idea. It can apparently read the
version, so some kind of communication is working.
As for the message "Link version is unrecognized: LinkUSB V1.7 (but
that's ok).", there might be some changes in 1.7 which owfs does not
know about. I took a (very) quick look at the latest "The Link Family
Manual" [1], but didn't find anything specific about 1.7. Might very
well have missed something though.
Regards
Johan
1. https://www.ibuttonlink.com/pages/information
------------------------------------------------------------------------------
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