On Friday 28 December 2018 20:12:12 Andy Pugh wrote: > What “align.zip” package? > > Where did you find it? What does it do? > Well, I think I made some progress, maybe. But a couple problems persist.
One of which may be fixable in my code by not applying the g55-56 offsets that determine where the db25 openings will be carved until the code arrives at the usage of that offset. Based on the theory that setting it at the top of the file doesn't include whatever history there might be between hitting the r, and arriving at that actual code some 30 to 50 minutes later. In the align-x.ngc or the align-y.ngc, there is a g92 x0 y0 before the call to apply the -r to the p0 co-ord map. Its not at all desireable to actual move the global home at anytime in this align code, so commenting that out seems to make sense. And by inverting the division in the statement so we get an above 1 result, then taking the atan of that as the r in the G92, the angle of the displayed L for the axis angles leans in the exact amount needed to align a crookedly mounted workpiece, at which point running the panel code then draws the angled stuff, not at the initial backplot & square, but at the pattern rotated to fit the out of alignment workpiece. This is very good, until I switch maps to do the db25's, at which point it fails, losing the angular compensation. But the G92 r#<angle> call is still moving the home position to where its at now, and its my reading that says nothing moves if you do not give it data for any axis's? Somethings aglay. All I am giving the G92 is the R. But when r for run is entered, its instantly back to its true home position while retaining the calculated angle, however, when it switches to g55 and g56 to cut out the db25's, the R setting disappears, and its carving out the db25's up to 1/4" out of position and uncorrected, and their axis's angle red/green display in the backplot is back to zero angle. When the run is finished, the displayed angle, since its in g54 at that point, is correct, showing the angle. Either I am not doing it right, a definite possibility, or this is a buglet. G92 is the wrong call maybe? I'm as usual, confused. Maybe I should give a g10 l2 p2 (or p3) the r, then in a separate call set the x offset so it would be applied after the angle R has already been set? Ideas? Thanks everybody. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
