allrighty then...
On 12.09.2017 19:35, Johan Ström wrote:
Thanks for verification, fix is now pushed to master :)
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
Thanks for verification, fix is now pushed to master :)
On 12/09/17 15:38, Martin Patzak (GMX) wrote:
tried your patch right away and it works! Small change, big difference ;)
I tested on platform amd64 all successful with options
-d /dev/ttyUSB0 # emulated mode
--link = /dev/ttyUSB0
tried your patch right away and it works! Small change, big difference ;)
I tested on platform amd64 all successful with options
-d /dev/ttyUSB0 # emulated mode
--link = /dev/ttyUSB0 # serial mode
--link = ftdi:AK0048A0# FTDI direct communication mode
Thank you,
Martin
On 11.0
Hi,
just took a closer look at the patch Hans-Frieders sent earlier. The
only thing it (effectively) does, when applied to the current owfs
version, is to do more identical probes:
It sets baud/flow to something, then calls LINK_detect_serial(..). If it
fails, it does this with a few different
Thanks for confirming.
If you want to, you can try the patch that Hans-Frieder Vogt sent to
this board. It worked for the LinkUSB.
On 10.09.2017 22:45, Nicolas Huillard wrote:
Le vendredi 21 juillet 2017 à 10:47 +0200, Martin Patzak (GMX) a
écrit :
I am trying to start owserver with a LinkUSB
Le vendredi 21 juillet 2017 à 10:47 +0200, Martin Patzak (GMX) a
écrit :
> I am trying to start owserver with a LinkUSB V 1.7 as bus master
> using
> the option /--link/.
> I am able to start owserver with the LinkUSB V 1.7 and V 1.4 using
> the
> option "d" for device without any problems.
I ca
Hi all,
Gesendet: Dienstag, 08. August 2017 um 21:29 Uhr
Von: "Martin Patzak (GMX)"
An: "OWFS (One-wire file system) discussion and help"
Betreff: Re: [Owfs-developers] problems starting owserver on a LinkUSB with option link
On 07.08.2017 21:43, Johan Ström wrote
On 07.08.2017 21:51, Matthias Urlichs via Owfs-developers wrote:
On 07.08.2017 21:43, Johan Ström wrote:
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..
There are
On 07.08.2017 21:43, Johan Ström wrote:
...
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
On 07.08.2017 21:43, Johan Ström wrote:
> 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..
There are lots of examples on the net how to write an udev rule which
doe
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 owf
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
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
On 07/25/17 15:36, Marcus Priesch wrote:
...
i just tried 3.2_p1 on gentoo - via custom ebuild, but no success either
well, thats too bad... thanks for testing it though.
i took a quick look on the code, but could not find anything useful,
despite the fact that link recognition ends at versio
Hello Martin,
Am 2017-07-25 um 13:37 schrieb Martin Patzak (GMX):
> Do you compile 3.2p1 yourself. The newest package for Debian and Raspi
> is 3.1p5, which is what I am using.
i just tried 3.2_p1 on gentoo - via custom ebuild, but no success either
i took a quick look on the code, but could not
Hi Marcus,
thank you for confirming. I tried quite a while in different
variations... no success.
Do you compile 3.2p1 yourself. The newest package for Debian and Raspi
is 3.1p5, which is what I am using.
I suspect that people using the /--link/ option are using a
self-compiled owserver, w
Hello Martin,
> ... /same lines//repeat a while/
> DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.00 seconds
> DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
> DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.00 seconds
> DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
> DEBUG: ow_li
Hello all,
I am trying to start owserver with a LinkUSB V 1.7 as bus master using
the option /--link/.
I am able to start owserver with the LinkUSB V 1.7 and V 1.4 using the
option "d" for device without any problems.
I am experiencing the same problems on a Raspi with both LinkUSB V 1.4
and
18 matches
Mail list logo
