Re: [Owfs-developers] Need help debugging a particular device
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
Re: [Owfs-developers] problem with owfs/owserver on raspberry pi
Paul, thats a good idea. It really helps when people just get started or change hardware. I tried to find Mark's error, and so I started owfs while my LinkUSB was unplugged and I got the same result he had: no error and no daemon was started! So I barked up the wrong tree, until you pointed out he wrongly used usb instead of the serial interface. Thanks, Martin On 06/16/2013 04:15 PM, Paul Alfille wrote: Thats great, but let me see if a better diagnostic message can be generated. Seems like too easy an error to make. Paul On Sat, Jun 15, 2013 at 11:26 PM, Mark Phillips mphil...@unca.edu mailto:mphil...@unca.edu wrote: Paul, Thank you very much! That was the problem. I have a lot of experience with Linux, and with software development, but not so much hardware knowledge, and I naively assumed that since my LinkUSB has USB in its name, and connects to the computer (the RPi in my case) with a USB connector, that it must be a USB device. When I changed my owfs.conf file to say server: device = /dev/ttyUSB0 instead of server: usb = all, everything started working beautifully! --Mark On Sat, Jun 15, 2013 at 9:03 PM, Paul Alfille paul.alfi...@gmail.com mailto:paul.alfi...@gmail.com wrote: You have it set up for a USB bus master, but that really means the DS9490R USB one made by Maxim. I think you really have a serial type (Link or DS9097U) connected to a USB-serial connector (the FTDI chip) Depending on which actual bus master you are using, it should be owserver -d /dev/ttyUSB0 or owserver --link=/dev/ttyUSB0 -- 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 mailto: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 mailto: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 -- 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
Re: [Owfs-developers] DS1921 Thermochron Patch - Mission Start Delay, Stop Mission
Egger: I'm always curious about applications. What do you use the Thermochron button for? -dan -- 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
Re: [Owfs-developers] Need help debugging a particular device
Ok, next release will have a --detail=10.12123434 option that turns on debugging when accessing a particular slave (or family). It's a little rough -- changing a global parameter will allow other details to leak in if they are happening concurrently but it should be a good first approximation. Paul On Sun, Jun 16, 2013 at 10:33 AM, Paul Alfille paul.alfi...@gmail.comwrote: 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
