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.
Kim On 04/15/2011 05:32 PM, Jon Elson wrote: > Stuart Stevenson wrote: >> nothing is figured out yet >> > Ugh! Debugging something that only happens every couple days can be > real hard. If it only happens once a month or less, it can be > maddening, as you have no idea whether you really have it fixed until > YEARS have gone by! > > 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
