I have searched the users and integrators manuals and can't find this but maybe I've missed it.
When strange things appear on startup of my axis or tkemc it is usually because there is a value stored in the .var file. If I zero out the strange numbers and save the .var file and restart it usually fixes the problem. I would really like to trace down how the values got there in the first place. Probably because I was doing on-the-job-training using G54, G92, G28, G30, etc. without fully understanding what I was doing. If I had a listing of each variable and what G command causes it to be changed I could then look at how I got into the situation in the first place and maybe use the same command in the program to reset the variable. I know that the discussions of each of the commands mentions which variable it sets but to find the culprit I have to go through each command searching for the variable number. I guess I'm looking for the "reverse directory" for the .var file. Thanks, Cecil ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
