Bugs item #1767781, was opened at 2007-08-04 16:35 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=106744&aid=1767781&group_id=6744
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Pete Vavaroutsos (petev) Assigned to: Nobody/Anonymous (nobody) Summary: TLO not taken into account when checking g-code Initial Comment: Axis doesn't seem to be taking TLO into account when checking g-code. For example, let's say the machine limits on Z are 0 to -5. The current tool has a TLO of -2. If the g-code has a move to Z0.25, axis complains that the Z limit has been exceeded when trying to run the program and throws up an error dialog box. This resultant Z move should be to machine -1.75 which is well withing range. The same g-code verifies without error under tkemc. It also runs without error under axis if you tell it to run anyway. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=106744&aid=1767781&group_id=6744 ------------------------------------------------------------------------- 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-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
