ATC Project - Debug phase

You know, I just went through the Probe Basic example stdglue and there are a LOT of differences from the latest in LCNC - not just the one I posted above.  And I see a number of changes in github to the file in the past couple of years - meaningful changes, not just documentation updates.

I think I'm going to try using the standard one this evening and see what happens.

Can I delete all the #REMAP=S, #REMAP=T, and # pure python remaps  stuff I don't need?

You can definitely remove any commented-out entries and you will see no difference in behaviour.
But sometimes they can be useful references for things that you have already tried.

Sorry Andy, I was unclear with my question.

Specifically, the newer LCNC version of stdglue has numerous sections (for lack of a better term) which I believe are intended to be templates for remapping T, S, F, M6, M61 words/codes.  In addition, there's a section on the end which appears to be a template for a pure python remap.

I was curious which of these template sections, if any, I could simply get rid of (or comment out).  I'm not trying to remap anything but M6.
 

Finaly, some tangible progess today.

Tried using the 'standard' stdglue.py from LCNC, and no significant change in behavior.  While fiddlign with it, I discovered that remap is not passing #<_selected_pocket> through to local variable #<selected_pocket>.  It is passing the other global parameters through.

That's what's been throwing me off for days, as I was changing the first one (selected_tool) or all three - but not just the last one.

So this:
#100 = #<selected_tool>
#110 = #<tool_in_spindle>
#120 = #<selected_pocket>

Had to be changed to:
#100 = #<selected_tool>
#110 = #<tool_in_spindle>
#120 = #<_selected_pocket>

Changed it in both my main toolchange.ngc and the m22.ngc (unloads tool from spindle), and some stuff started happening... like the PDB started activating, spindle oriented.  WOO!

Challenge the next is trying to pass through INI values to the remap o-codes.  I have Z-high, medium, and low positions and fast & slow speeds I'd like to have the head move to/at during the process. And I'd really like to have those values in one place, not repeated across 3-4 files (with a high probability of crashy-error).

INI file has this section:
and my two sub-routines have references to those values like so:
I've tried removing the outer "[...]" from the references.
I've tried changing to lower case.
I've tried connecting them to local named variables:
But no dice. I've even added the [RS274NGC] INI_VARS = 1 statement (supposed to be default), but the INI values aren't passing through.

Every permutation of (DEBUG, the value of parameter z_med is #<_ini[ATC]ZMED]>) results in ##### (for all the INI values, not just ZMED).

So close, but still stumped.

PS - don't want to hose up the editing above.

I tried changing #<selected_pocket> to #<pocket>, and that didn't work.  The only positive result was switching to the global parameter.

spumco wrote:

PS - don't want to hose up the editing above.

I tried changing #<selected_pocket> to #<pocket>, and that didn't work.  The only positive result was switching to the global parameter.
 

Comments.

COMMENTS COMMENTS COMMENTS!!!

Take the comments after the values out and it works:
to this:
And it's working.  There are other INI sections/values with comments and those work... but I don't care why right now.

OMG LinuxCNC is so hyper-specific I'm going to cry.

"I'm sorry, Hal, I can't do that."

This is like the worst Easter-egg hunt in the universe. On to the next battle...