On Fri, Jul 8, 2011 at 3:09 PM, Pedro Côrte-Real <[email protected]> wrote: > I spoke too soon. Seems like stdout was just not being flushed. It's > now outputting readings. I should have one of the strange ones in a > bit.
After running it for a while I got a few wrong values and put them in a spreadsheet[1]. What seems to be happening is that when the value is wrong VAD is equal to VDD. Here are four successive reads with the two middle ones in error: VAD VDD T H 2.78 4.96 25.0312 64.5598 2.91 2.91 24.4062 135.229 4.94 4.94 24.4688 135.248 2.9 4.94 24.5 68.7626 Because the saal code is doing reads in quick succession it could indeed be a timing bug as I may be pushing this to the limit. Most of the reads here are explicitly uncached too. Pedro [1] http://scratch.pedrocr.net/OwServerAnalysis.gnumeric ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
