Kim Kirwan wrote: > Can anything be done by improving halscope? Maybe save a list of 16(?) > significant hal items (time, in-cycle yes/no?, encoder positions, > following errors, velocities, etc., whatever might be helpful) and > save them to disk so that you at least have a bunch of logged data to > review after trouble occurs? Save the latest halscope capture to a > logfile and then restart halscope? Log the latest entries as often as > reasonable without filling up the disk or bogging down the machine? > Erase the logfile once a day if no trouble is observed? Could this be > a hal component add-on to halscope so anyone can use it and/or > improve it? Maybe have a configuration file for this halscope logger > component? Just thinking out loud here, hope this is helpful. > I believe there is a logger function that reads the halscope data and saves it instead of displaying it live. You'd still need to start halscope and select the points you want to record, the sample rate and I guess set it to roll instead of triggering on something.
Jon ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
