Re: [Owfs-developers] owserver and owcapi behave differently with —enet device
Sorry for the multiple replies. I thought my messages weren't going out, but really there's just a 1h+ delay... On 11/08/2017 06:37 PM, Justin Brewer wrote: ...snip... -- 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
Re: [Owfs-developers] owserver and owcapi behave differently with —enet device
On Wed, Nov 08, 2017 at 01:51:49PM -0800, Andrew Brownsword wrote:
> Nothing but crickets — is anyone out there?
>
> I’ve been poking at the code to try and figure out how to enable my debugger
> to step into the libowcapi/libow code, but the make process is obscure enough
> that some advice would be welcome...
If you're working from a clean git clone, I use this for working with just
owcapi:
$ autoreconf -i
$ ./configure CFLAGS='-g -O0' --prefix=$HOME/opt/owfs
--disable-{zero,ow{perl,python,php,tcl}}
$ make
$ make -k install
This lets me ignore most of the language binding dependencies, and ignore some
hardcoded install paths.
>
>
> Sent from my iPhone
>
> > On Oct 31, 2017, at 3:11 PM, Andrew Brownsword
> > wrote:
> >
> > Hello,
> >
> > I have an EDS ETH-OWSERVER v2, and I am trying to talk to it using the
> > owcapi library. The init with arts function returns success but when I try
> > to OW_get, I don’t see any buses or sensors (just the meta directories).
> > If I run owserver, it sees the enet device and it’s 3 buses and 22 sensors
> > just fine. I ran a simple owcapi test program and it sees one bus and zero
> > sensors.
> >
> > My program is multi-threaded and the OW_get will be called from a different
> > thread than the init (but correctly ordered). As for the test program, it
> > is just the init and then a get of root.
> >
> > I’m using the latest release and running on either an Ubuntu ARM host or on
> > OSX... same behavior either way.
I have been working on some issues I've found in libow, and have seen similair
symptoms. There's some race conditions that, if it doesn't outright crash,
causes random failures elsewhere. I have a patch that resolves these issues
here:
https://gitlab.com/justinbrewer/owfs/commit/0234a2cecb56d0b6ca4d20a6100a2d2b2ba6bffb.patch
I was planning on submitting a pull request in the next day or so, but I think
this patch help you.
--
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
Re: [Owfs-developers] owserver and owcapi behave differently with —enet device
I have been working with libowcapi recently, and have seen similair
symptoms. There's a race condition in libow that, if it doesn't outright
crash, causes problems with directory listings. I have a patch for this
issue here:
https://gitlab.com/justinbrewer/owfs/commit/0234a2cecb56d0b6ca4d20a6100a2d2b2ba6bffb.patch
I was planning on submitting a pull request in the next day or so, but
it sounds like it might help you.
As for building, from a clean git clone, I use this for working with
just owcapi:
$ autoreconf -i && ./configure CFLAGS='-g -O0' --prefix=$HOME/opt/owfs
--disable-{zero,ow{perl,python,php,tcl}} && make && make -k install
This lets me ignore most of the problematic language binding
dependencies and hardcoded install paths.
On 11/08/2017 03:51 PM, Andrew Brownsword wrote:
Nothing but crickets — is anyone out there?
I’ve been poking at the code to try and figure out how to enable my debugger to
step into the libowcapi/libow code, but the make process is obscure enough that
some advice would be welcome...
Sent from my iPhone
On Oct 31, 2017, at 3:11 PM, Andrew Brownsword
wrote:
Hello,
I have an EDS ETH-OWSERVER v2, and I am trying to talk to it using the owcapi
library. The init with arts function returns success but when I try to OW_get,
I don’t see any buses or sensors (just the meta directories). If I run
owserver, it sees the enet device and it’s 3 buses and 22 sensors just fine. I
ran a simple owcapi test program and it sees one bus and zero sensors.
My program is multi-threaded and the OW_get will be called from a different
thread than the init (but correctly ordered). As for the test program, it is
just the init and then a get of root.
I’m using the latest release and running on either an Ubuntu ARM host or on
OSX... same behavior either way.
And no, I don’t want to rely on owserver.
Any suggestions?
--
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
--
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
Re: [Owfs-developers] owserver and owcapi behave differently with —enet device
Am 08.11.2017 um 22:51 schrieb Andrew Brownsword: > Nothing but crickets — is anyone out there? > > I’ve been poking at the code to try and figure out how to enable my > debugger to step into the libowcapi/libow code, but the make process > is obscure enough that some advice would be welcome... > I had hoped someone with more experience with enet devices than myself (== zero) would answer that. So, if you place an owserver inbetween, it works for obscure reasons? I would check the owserver code then, if it does something differently than your code does. Kind regards Jan -- 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
Re: [Owfs-developers] owserver and owcapi behave differently with —enet device
Nothing but crickets — is anyone out there? I’ve been poking at the code to try and figure out how to enable my debugger to step into the libowcapi/libow code, but the make process is obscure enough that some advice would be welcome... Sent from my iPhone > On Oct 31, 2017, at 3:11 PM, Andrew Brownsword > wrote: > > Hello, > > I have an EDS ETH-OWSERVER v2, and I am trying to talk to it using the owcapi > library. The init with arts function returns success but when I try to > OW_get, I don’t see any buses or sensors (just the meta directories). If I > run owserver, it sees the enet device and it’s 3 buses and 22 sensors just > fine. I ran a simple owcapi test program and it sees one bus and zero > sensors. > > My program is multi-threaded and the OW_get will be called from a different > thread than the init (but correctly ordered). As for the test program, it is > just the init and then a get of root. > > I’m using the latest release and running on either an Ubuntu ARM host or on > OSX... same behavior either way. > > And no, I don’t want to rely on owserver. > > Any suggestions? -- 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
