Jon Elson wrote: > ben lipkowitz wrote: >> On Sun, 23 Sep 2007, Jon Elson wrote: >> >>> Hey, John, how about an FFT function in HalScope? That would be really >>> cool! Otherwise, is there a data dump function that would hardcopy the >>> screen samples to a file? >> >> Sorry for the late reply. I hacked a logging function into halscope a >> while ago but didnt quite finish it. You have to uncomment a line in >> scope.c to get it to write log files. I did this mostly because I couldn't >> find a good place to put a 'log to file' button in the tightly-packed >> halscope interface. The logging function is quite limited - it will only >> write data from one 'run' of halscope, so no continuous data logging. > Oh, just to be clear, a "screen dump" would likely be most > useful for me, not continuous logging. >
I'm pretty sure that is what Ben has done - write the current captured data to a file. Continuous logging would require some serious re-coding of halscope, writing the current screen to a file not so much. If anyone does need to do continuous logging, that is what "sampler" is for. It can capture any number of HAL signals and write them to stdout. Regards, John Kasunich ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
