Hi Bruce,
There is no really way currently to isolate one device.
If you want, I could create a patched version that turns debugging on and
off when a particular device is referenced. There may be some mix-in from
other threads during that time.
The internal problem is that the calls to output debugging information
don't include the slave information.
Paul
On Sat, Jun 15, 2013 at 9:39 PM, brucek <bru...@valinet.com> wrote:
> I need a little help debugging a particular device. I have a ds2408
> that has been on line for a few years that has developed an intermittent
> problem of all outputs momentarily turning on then off. I am assuming it
> is a software problem (my control software is continuously being developed)
> but I want to rule out a hardware problem.
>
> Is there an easy way to collect debug info for just this device? I am
> trying to avoid having to filter through huge debug logs to find only the
> traffic to this particular device. I want to verify if the device is
> responding to actual commands from owserver or acting on its own.
> Thanks
> Bruce
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
