RE: Set Coordinates Tcl

[Ethan Vos <ethan-at-forward.ca>]

No sweat.

While you're looking around, set your axis to X Z and A. Then try to do a manual home or jog and see which axes move.

He he.

Ethan


-----Original Message-----
From:	Ray [SMTP:rehenry-at-up.net]
Sent:	Friday, August 31, 2001 2:30 PM
To:	Multiple recipients of list
Subject:	RE: Set Coordinates Tcl



Ethan

Looks like there's a bug in the reading of the var file after it has been
reset.  If you execute another coordinate system (g55) and then return to
(g54) it seems to work okay.  I suspect that this is burried somewhere in
the new stuff to set inch or metric units.  You seem to be the first tester
of this stuff.

Thanks for finding it.  We should have a fix for this before long.

Ray


On Fri, 31 Aug 2001, you wrote:
> OK, now I'm really confused.
> 
> If I write "1.0" into the 5221 parameter, which I guess is the default X 
> axis adjustment, the X axis changes by .0394, so it's displaying metric.
> 
> How can that happen if I've set up everything to inches?
> 
> I have set the .ini to inches and am using G20 in the program. I think that 
> G20 also is in the .ini file for startup. The Tkemc has the word "inches" 
> in the top right hand corner.
> 
> Where does the metric conversion happen?
> 
> Ethan
> 
> 
> -----Original Message-----
> From:	Ray [SMTP:rehenry-at-up.net]
> Sent:	Friday, August 31, 2001 11:52 AM
> To:	Multiple recipients of list
> Subject:	Re: Set Coordinates Tcl
> 
> 
> On Fri, 31 Aug 2001, you wrote:
> > I'm really starting to have fun with this.
> 
> Good.
> 
> > Questions about the Set Coordinates Tcl in the 801bin.
> >
> > 1. What do I need to change to get the cursor to the end of the zeros
> > (0.0000) rather than at the beginning?
> 
> In Tk, focus is what is being shifted around when you move from widget to
> widget.  Focus aims at the whole widget.  I don't know if there is a way to
> point focus at the least significant digit and then get the program to
> treat each successive character as a times tens shift.  I am aware that 
> many
> of the commercial CNC guis do enter digits starting from the right.  It is
> nice when you want to add a tenth or two to a number.
> 
> > 2. What other parameters can I use (it starts with 5221) and where in the 
> > tcl do I make the change? I tried changing the 5221 at the end of the
> > program to 1000, but the tcl wouldn't work. I need to make a Tcl to input 
> > data into the variable table.
> 
> You can use any number up to 5400. (or is it 5399)  See these
> 
> www.linuxcnc.org/handbook/RS274NGC_3/RS274NGC_33a.html#1008244
> www.linuxcnc.org/handbook/gcode/variables.html
> 
> They will also be under the handbook icon on your BDI disk in a similar
> location.
> 
> > 3. I have changed the setaxis to "2" instead of to read from the .ini 
> file.
> > I labeled them "Shim Adjust" and Excessive Wear" which I need to 
> correspond
> > to axis X and A. X is working OK, but I the 2nd axis (A) is updating the 
> Y
> > field. What do I need to do to change that?
> 
> The way that axis comp was expected to work was that you would place a
> reference in each axis that you wanted a comp file for in the ini.
> 
> -----release notes snippet-----
> You specify these files in the .ini file for each axis with the
> [AXIS_#] COMP_FILE = <filename>, e.g.,
> 
> [AXIS_0]
> .
> CCOMP_FILE = x.cmp
> 
> This entry is optional. If it's not there, no compensation is done.
> -----end of snippet-----
> 
> What I would do if I wanted to use a file named Shim_adjust.cmp for x is
> add the following line to [AXIS_0] in the ini that I intend to run.
> 
> COMP_FILE = Shim_Adjust.cmp
> 
> Then for the A axis I would add the line
> 
> COMP_FILE = Excessive_Wear.cmp
> 
> to whichever axis number you use for your A definition.
> 
> Yes, you can change the references to compensation files in other places
> and they will work but what you wind up doing is creating a non standard
> system that you will have to edit every time you upgrade to a new release
> of the EMC.  You also create a system that only you can support.
> 
> > 4. Where does the data come from that the Tkemc reads when it displays 
> the
> > axis offsets? I can't figure out why when I enter in 1.0 on the
> > Set_Coordinates the display changes by .0394. I'm using G20 (I think) and 
> > the .ini file has been changed from "auto" to "inches"
> 
> See the handbook references to parameters listed above.
> 
> HTH
> 
> Ray