conversational input

Does anyone know of a way to read all the tool length offsetts, other than using a while statement to scroll thru a G43 H# to load them in.

-it seems that the only one i can read is the currently loaded tool.
-heres the thing.... i want to add a value to the longest tool, so i can work out a tool change point, automagicly, include this in a set of sub programs, and not have to specify a tool change point in the ngcgui entry fields for all subs.

Hi

They may be stored as an undocumented parameter, but I cannot find any evidence of it.

However there are some undocumented parameters creeping in.
I found that when running the 2.6pre version, a standard parameter I use in pretty much all my gcode files #<_Feed>,
now throws an error of "cannot assign to read only parameter #<_feed>" at the line where you try to initialise it.

So from GCode you probably have the best idea with your G43 Hn rotation.

Internally the tool table is read into a CANON_TOOL_TABLE struct and the entries in this are used for all tool changes etc.
You could hook into it, but would require amending the source code.

If you wanted to open and parse the tool.tbl file to get the entries from there yourself, the code is pretty much already written for you in
src/emc2/rs274ngc/tool_parse.cc --- loadToolTable() function.

The danger however is that emc uses the CANON_TOOL_TABLE struct throughout the session, including into it any changes made and only writes it back to file on exit, so the information might not be correct.

regards

ive tried to get the g43 h# loop working, but!
if you run the following as an ngc file you will see that the #54** variables only store the values of the currently loaded tool, so you can't get any useful info from them.

(LOGOPEN,paramnum)

G43 H23
G4 P5.0
(log,value0 = #5400)
(log,value1 = #5401)
(log,value2 = #5402)
(log,value3 = #5403)
(log,value4 = #5404)
G49
G4 P2.0
G43 H3
G4 P5.0
(log,val0 = #5400)
(log,val1 = #5401)
(log,val2 = #5402)
(log,val3 = #5403)
(log,val4 = #5404)
G4 P2.0
G43 H8
G4 P5.0
(log,value7 = #5400)
(log,value8 = #5401)
(LOGCLOSE)
m02

So....

im going to have to use vers 2.5, then i can do a g43 h#, then read #5423 and subtract, etc

i read that u can update from buildbot...

so, i upgraded to 2.5,

IT LIVES!

using the attached files, u can write the od cycles i provided, with appropriate tool changing, and automatic tool change point calculation.

i am raving a bit, it does need some cleaning up, and the cycles need to adapt for internal/external.

But it is now possible!

u will need to modify the start.ngc sub to suit one turret -i think..

Keep in mind. use these cycles at your peril!
not fully tested

andypugh wrote:

This is only not-yet-documented. It is part of Michael Harberler's "G-code Introspection" which is aimed at letting G-code know a lot more about its own state.
article.gmane.org/gmane.linux.distributions.emc.devel/4122

Excellent info thanks Andy, I look forward to having a play with these in due course.

regards

i've been using the following outside diameter subs now for a bit, i made a few changes and added this and that, the info.txt file tells a bit about them too.

i geuss that a new gui could be written for them, and others using "Glade"
it may take me a while but!

the only problem i have is that ngcgui "stacks" subs in the output file.

whereas a glade interface could be used to re-edit as well as create programs.

....mind you i still havent got a glade interface working on my now 2.5 lathe.

......though the camera tab would be unreal for re-cutting threads on a cnc! just set spindle to reference point (rotate manualy) line up the cross-hairs to a thread peak and POW!