Is there a feature in Master that you need to run? When I'm not sure if I touched off correctly I do a chicken check by jogging the tool to a point I know what the DRO should read and see if the DRO is correct.
AFAIK machine limits are in machine units and it won't matter if your in G7 or G8. As I said before as you type in the first number in the touch off box it immediately tells you if your in diameter or radius mode on the next line below the box where you enter the number. You can also look at the Active G-Codes: box and see if your in G7 or G8 and if your not where you expect change it in the MDI Command. JT On 5/10/2015 9:18 PM, Gene Heskett wrote: > Hello all; > > First, ther good news, all that fussing about not finding a bunch of > stuff in the DEFAULTS section, without even specifying the file it > expected to find them in, are apparently an artifcat of running it for > the first time. 2.8.0-pre1 has not made a peep aboiut it since. > > But now I am back to the G7/G8 diffs which are costing me money. > > This program, which looks great in the back plot, proceded to drive the > carriage to half the diameter on the first loading, smashing the insert > and unscrewing the QC toolpost & generally raised hell. > > So I eventually killed LCNC, and when I had restarted it, and reloaded > the code, now refuses to run because x maximum exceeds the machine > limits. Those are set .1mm short of the homing switch, which itself is > aboput .1mm from the maximum backup x can do on this toy, at about 67mm > from the centerline. > > What I can see in the debug statements says it isn't so. x max is > nominally 1/2 that limit as set in the .ini file. And the backplot > image is exactly what I want it to do. > > The program: > =========================================== > G7 (diameter mode dammit) > #<_x_start_dia> = 32.3000000 (x at left z DIAMETER) > #<_z_start> = 105.5000000000 > #<_x_taper> = .320000000 (in mm's, measured taper compensation > needed) > #<_z_left> = 0.0000000 > #<_x_end_dia> = 21.000000 (x at left z, DIAMETER) > > o100 sub > (debug,8 x to [#<_x_tmp> + #<_x_taper>]) > G1 F20 x[#<_x_tmp> + #<_x_taper>] > G1 F7 z#<_z_left> x#<_x_tmp> > G1 F48 z#<_z_start> x[#<_x_tmp> + #<_x_taper>] > o100 endsub > > S250 > M3 > #<_x_diff> = [#<_x_start_dia> - #<_x_end_dia>] (is plus value, 11.3000) > (debug,15 x_diff=#<_x_diff>) > #<_x_dec> = [#<_x_diff> / 30.0000000] (so this s/b too) > (debug,17 x_dec=#<_x_dec>) > #<_x_tmp> = #<_x_start_dia> (init at 32.3) > > o200 while [#<_x_tmp> gt #<_x_end_dia>] (true till x is below end) > #<_x_tmp> = [#<_x_tmp> - #<_x_dec>] (dec x_tmp by x_dec) > o100 call > o200 endwhile > > M5 > M2 > =========================== > Bug? Or one of my (in)famous typo's? > > Thanks guys. > > Ugly thought, if running in G7 mode, do I need to set the axis 0 > max_limit to a diameter? It is currently stated in radius. 67mm's from > centerline. Or 114mm diameter. > > Cheers, Gene Heskett ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
