Glad it's working. Am I correct, you were changing managing GPIO pins outside of OWFS (for a different function I presume)? And caused conflict? You shouldn't need to alter GPIO pins directly for one-wire in OWFS after the initial startup I would think.
On Sun, Mar 30, 2014 at 1:41 AM, Colin Reese <colin.re...@gmail.com> wrote: > As it turns out, when your i2c pins can be used as GPIO and you attempt > to set them as outputs by inadvertently passing an index rather than > address, it kills your i2c bus. This was buried in my database operations. > > All better. > > Colin > > > On 3/29/2014 13:35, paul.alfille wrote: > > That's discouraging. Do you have a simple test case that triggers the > error? > > > > > > Sent via the Samsung Galaxy S(tm) III, an AT&T 4G LTE smartphone > > > > > > > > -------- Original message -------- > > From: Colin Reese <colin.re...@gmail.com> > > Date: 03/29/2014 1:32 PM (GMT-05:00) > > To: "OWFS (One-wire file system) discussion and help" > > <owfs-developers@lists.sourceforge.net> > > Subject: Re: [Owfs-developers] ow Python makes sensors disappear > > > > > > Well, this isn't quite over yet. Still randomly crapping out. > > > > Can someone please help me debug this? > > > > Thanks, > > Colin > > > > > > On 3/28/2014 16:52, Colin Reese wrote: > > > and ... drum roll ... the answer was to remove all double quotes from > > > sqlite query preparation statements in the calling script, escaping > > > included single quotes. > > > > > > I don't understand it, but it fixed it. > > > > > > Colin > > > > > > > > > > > > > > > On 3/28/2014 15:55, Stefano Miccoli wrote: > > >> Try running > > >> > > >> owserver --debug > > >> > > >> and watch for error messages. > > >> > > >> S. > > >> > > >> On 28 Mar 2014, at 23:33, Colin Reese <colin.re...@gmail.com > > >> <mailto:colin.re...@gmail.com>> wrote: > > >> > > >>> I've no idea where to even start on this. > > >>> > > >>> > > >>> On 3/28/2014 14:49, Stefano Miccoli wrote: > > >>>> This error is entirely on the owserver side... owpython and the > > friends > > >>>> seem not to be responsible. > > >>>> > > >>>>> pyownet.protocol.OwnetError > > >>>> > > >>>> exceptions are raised when the remote owserver answers with an > error > > >>>> code, in this case -5, that according to > > >>>> > > >>>> owserver --help=error > > >>>> > > >>>> is > > >>>> > > >>>> 5. legacy - IO error > > >>>> > > >>>> you shoud inspect the owserver code to find out. > > >>>> > > >>>> Stefano > > >>>> > > >>>> On 28 Mar 2014, at 22:23, Colin Reese <colin.re...@gmail.com > > >>>> <mailto:colin.re...@gmail.com> > > >>>> <mailto:colin.re...@gmail.com>> wrote: > > >>>> > > >>>>> And I've now successfully duplicated the error in pyownet: > > >>>>> > > >>>>> File "/usr/lib/iicontrollibs/cupid/owfslib.py", line 27, in > owbuslist > > >>>>> for dir in OwnetProxy(host).dir(): > > >>>>> File "/usr/lib/iicontrollibs/resource/pyownet/protocol.py", line > > 408, > > >>>>> in dir > > >>>>> raise OwnetError(-ret, self.errmess[-ret], path) > > >>>>> resource.pyownet.protocol.OwnetError: [Errno 5] legacy - IO > > error: '/' > > >>>>> > > >>>>> What on earth is nuking the directory? > > >>>>> > > >>>>> Colin > > >>>> > > >>>> > > >>>> > > >>>> > > > ------------------------------------------------------------------------------ > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> _______________________________________________ > > >>>> Owfs-developers mailing list > > >>>> Owfs-developers@lists.sourceforge.net > > >>>> <mailto:Owfs-developers@lists.sourceforge.net> > > >>>> https://lists.sourceforge.net/lists/listinfo/owfs-developers > > >>>> > > >>> > > >>> > > > ------------------------------------------------------------------------------ > > >>> > > >>> _______________________________________________ > > >>> Owfs-developers mailing list > > >>> Owfs-developers@lists.sourceforge.net > > >>> <mailto:Owfs-developers@lists.sourceforge.net> > > >>> https://lists.sourceforge.net/lists/listinfo/owfs-developers > > >> > > >> > > >> > > >> > > > ------------------------------------------------------------------------------ > > >> > > >> > > >> > > >> > > >> _______________________________________________ > > >> Owfs-developers mailing list > > >> Owfs-developers@lists.sourceforge.net > > >> https://lists.sourceforge.net/lists/listinfo/owfs-developers > > >> > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Owfs-developers mailing list > > Owfs-developers@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/owfs-developers > > > > > > > ------------------------------------------------------------------------------ > > > > > > > > _______________________________________________ > > Owfs-developers mailing list > > Owfs-developers@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/owfs-developers > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers >
------------------------------------------------------------------------------
_______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
