On Tuesday 28 August 2018 11:24:03 Gene Heskett wrote: > On Tuesday 28 August 2018 10:06:53 Les Newell wrote: > > Hi Gene, > > > > > But homing does not apply a TLO, which can vary by 7 or 8 inches > > > according to whats in this spindle for a tool at the time with > > > this machine. So when I calculate the min limit, I'm effectively > > > putting the spindle with no tool in it, about 25 thou from the > > > table. > > > > Yes, Homing is just establishing the physical limits of the machine. > > It doesn't take any offsets into account. > > > > > Z home switch trips about 50 thou below top of post and offsets > > > are supposedly from there in the rest of my homing setup,mainly > > > because I don't care for -z's in my code. > > > > With my router I have Z0 as the top of the spoil board because the > > bottom of the work is always in the same place. For milling, where > > the bottom of the work can be anywhere depending on if it is held in > > a vice, clamped to the bed etc I use Z0 as the top of the work. > > > > > So the question, since theres no z probition in a G10L1, does a z > > > offset applied that way, actually get into the tool.tbl for use as > > > TLO with a G43 H? Looking at the Doc pdf, it does not say > > > > Yes. From the docs: "A valid G10 L1 rewrites and reloads the tool > > table." I have attached my toolset subs which may help. There is > > some extra stuff to tweak the limits, make sure the spindle is > > stopped, raise the setter etc but you can take that out. > > You need to add some stuff to the ini file. All values are in > > machine coords: > > Which for you are metric. I do a lot of metric, but the machine was > originally setup in inches. > > > [RS274NGC] > > REMAP=G36 modalgroup=1 ngc=toolset > > REMAP=G36.1 modalgroup=1 ngc=optional_toolset > > REMAP=G37 modalgroup=1 ngc=clear_toolset > > This is a new stanza for the ini file, kewl. > > > [TOOLSET] > > #all coords are in machine coords > > #Tool set Y (you probably don't want this one) > > Y = 1393 > > #Rapid down to this height before probing > > RAPID_Z = -60 > > #Tool set height (used to work out maximum distance for G38.2) > > Z = -165 > > #Offset from tool setter to table > > OFFSET = 5.75 > > Neat, but my screws limit me to on table positions, so I usually just > superglue a piece of dbl-sided pcb to some handy place near the middle > of the table, ATM to the top of a block of wood also serving as a > bearing for an r8 to turn in while drilling and tapping for the grub > screws holding the tap by its square butt. And a lead from there to > the probe input. Next job setup is invented on the fly of course. > > > G36 will do a toolset. G36.1 will do a toolset if that tool has not > > already been set in this session. > > > > G37 will clear all toolset flags and force a new toolset next time > > G36.1 is called > > Also neat. > > > Note the toolset flags only work for the first 8 tools. > > Ouch, so those have to be treated as 100% volatile, meaning move the > tools already defined to position 10 and above in the tool table. But > thats alright as I tend to break a job down to not more than 4 or 5 > tools used per push of the R key. Us coffee-holics gotta have time to > go recycle the last cup and refill the empty coffee cup :) > > All this is of course a different project from the screw comp for > slight bed wear on the sheldon where x will be offset according to z > position. Conversations will need to spec which project. :) > This I have been playing with a bit, and can report I'm going blind, the original joint.0.pos-fb was there and its stable whereas the joint.0.motor-pos-fb is not, drifting a thou or more for each repeated homing. But pos-fb stays in the E-09 range, so my switches must be working ok.
So I'm in the process of working over my .hal file now, trying to get the addf's in a workable order. IMO. this joint.0.pos-fb into lincurve.0.input ought to be just about last in the servo loop, maybe even in the jog loop since the movement speeds aren't all that fast. Yeah, I'll put that whole signal change up to the offset.0.control-input in the slower 10 millisecond thread. > > Change > > clear_toolset to suit (probably best to use a loop rather than the > > way I did it). You'll also need to change line 8 of toolset.ngc. > > Yup. But lincurve setup is once per execution of LCNC so that can be done sequentially. I've given it a personality of 16 so I'll do setpoints at 2.25" intervals, as it claims to interpolate between them. Now if I can get a decent reading from this slightly bent piece of A2 I have mounted. I wobbles the dial about 8 thou +- from center in the middle of it when turning slow, and thats still almost too fast for the dial so I'll put it in backgear for this. > > Les Back to it, thanks Les. > I don't know how much of this I'd need, no tool changer yet. :( But > its all printed F.F.R. > > Thanks Les, a bunch. -- 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> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
