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 > <andrew.e.brownsw...@gmail.com> 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
