problems starting owserver on a LinkUSB with option link

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

problems starting owserver on a LinkUSB with option link

Martin Patzak (GMX)

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 V 1.7 when using the option --link, while the option "d" works fine as well

here is an excerpt of the log:

mnm@vincent:~$ sudo owserver --link=/dev/ttyUSB0 --debug  
DEBUG MODE
libow version:
        3.1p5
  DEBUG: ow_daemon.c:(170) main thread id = 140041592982720
  DEBUG: ow_inotify.c:(80) No configuration files to monitor
CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd library isn't found
   CALL: ow_parsename.c:(104) path=[]
  DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and mock adapters)
  DEBUG: ow_com.c:(47) Auto initialization of /dev/ttyUSB0
  DEBUG: ow_link.c:(328) Detecting serial LINK using 9600 bps
  DEBUG: ow_link.c:(360) Slurp in initial bytes
  DEBUG: ow_link.c:(431) Checking LINK version
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds
... same lines repeat a while
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_link.c:(218) Link version is unrecognized: LinkUSB V1.7 (but that's ok).
CONNECT: owlib.c:(216) Cannot open LINK bus master at /dev/ttyUSB0
... cleaning up and ending

What seams to be the problem? Anybody seen this before?

Martin


------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: problems starting owserver on a LinkUSB with option link

Marcus Priesch-2
Hello Martin,


> ... /same lines//repeat a while/
>   DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds
>   DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
>   DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds
>   DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
>   DEBUG: ow_link.c:(218) Link version is unrecognized: LinkUSB V1.7 (but
> that's ok).
> CONNECT: owlib.c:(216) Cannot open LINK bus master at /dev/ttyUSB0
> ... /cleaning up and ending/

i can confirm this with LinkUSB V1.7 and owfs 3.1p4 - will try current
3.2p1 next ...

regards,
marcus.

------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: problems starting owserver on a LinkUSB with option link

Martin Patzak (GMX)

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, which would explain why you can confirm my problem.

Is there an option that was maybe not compiled in the Debian package of owserver that might be need to make this work? I wonder...

Servus,
Martin


On 07/25/17 12:32, Marcus Priesch wrote:
Hello Martin,


... /same lines//repeat a while/
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_link.c:(218) Link version is unrecognized: LinkUSB V1.7 (but
that's ok).
CONNECT: owlib.c:(216) Cannot open LINK bus master at /dev/ttyUSB0
... /cleaning up and ending/
i can confirm this with LinkUSB V1.7 and owfs 3.1p4 - will try current
3.2p1 next ...

regards,
marcus.

------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers



------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: problems starting owserver on a LinkUSB with option link

Marcus Priesch-2
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 find anything useful,
despite the fact that link recognition ends at version 1.5 - where the
switch statement sets adapter type to LINK_15, but this never gets
cought somewhere ... at least i didnt find it ...

i suspect some code maybe magically has vanished ... are there
regression tests with linkusbs ?
> I suspect that people using the /--link/ option are using a
> self-compiled owserver, which would explain why you can confirm my problem.
>
> Is there an option that was maybe not compiled in the Debian package of
> owserver that might be need to make this work? I wonder...

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.

so i think we need help from the devs ... PPAAAAUUUUULLLLL ;)))

regards,
marcus.

>
> Servus,
> Martin
>
>
> On 07/25/17 12:32, Marcus Priesch wrote:
>> Hello Martin,
>>
>>
>>> ... /same lines//repeat a while/
>>>   DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds
>>>   DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
>>>   DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds
>>>   DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
>>>   DEBUG: ow_link.c:(218) Link version is unrecognized: LinkUSB V1.7 (but
>>> that's ok).
>>> CONNECT: owlib.c:(216) Cannot open LINK bus master at /dev/ttyUSB0
>>> ... /cleaning up and ending/
>> i can confirm this with LinkUSB V1.7 and owfs 3.1p4 - will try current
>> 3.2p1 next ...
>>
>> regards,
>> marcus.
>>
>> ------------------------------------------------------------------------------
>> 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
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>
>
>
> ------------------------------------------------------------------------------
> 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
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>

------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: problems starting owserver on a LinkUSB with option link

Martin Patzak (GMX)



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 version 1.5 - where the
switch statement sets adapter type to LINK_15, but this never gets
cought somewhere ... at least i didnt find it ...
Yes, I don't think it's related to the version of the LinkUSB.
Firstly, the debug message tells us so:
  
    Link version is unrecognized: LinkUSB V1.7 (but that's ok). :-)

   
And secondly, it does not work with a LinkUSB V1.4 either... :-(
...
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!

Cheerio,
Martin

------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers