I'll fix the link.
owread/owwrite have no error reporting themselves. You can get the server to
report errors, either through reading it's statistics (owread -s 4304
/statistics/whatever) or by having it log to the console.
I'll soon be releasing owtap, a program that sits between a client and
o
I am looking for information on owread/write and if owserver provides for an
error log. I only use owserver with owread/owwrite in a bash script so was
interested if there is somewhere an error log file (besides what is reported
from the usb adapter parameters.)
I was trying to get some more i
Hi Jerry,
We certainly could use option negotiation (although even that would require
some backwards compatibility.)
We also have had version numbers included in the owserver protocol since the
start -- although there hasn't been a need to progress beyond version 0.
We faced this issue thrice b
Paul Alfille wrote:
> Hmm...
>
> owlib is written in C, and needs a fixed data size (string size) for
> floating point output. I arbitrarily used 12 characters and the %g
> printf format to be most general.
>
> Currently type (floating point, integer...) and certainly precision
> aren't part of
Hmm...
owlib is written in C, and needs a fixed data size (string size) for
floating point output. I arbitrarily used 12 characters and the %g printf
format to be most general.
Currently type (floating point, integer...) and certainly precision aren't
part of the ownet messages. If we really wan
