Manual tool change + tool lengh touch off

Hi,

I was wondering if any could give some insight on this one.  I tried to use the M6 subroutine that orangecat made.  I was able to get the probe working, change the ini and hal files accordingly.  I got to the point were the tool would probe, but my tool table won't populate with that number.  When I debug the 5063 in mdi I get ###### not an actual number, however the 5063 variable will show up in the var file in the config folder as a function of the 38.2 probing routine as an actual number.  I tried to debug other variables like 5181 which is the x position for the G30.1 command and although the var table in the config folder would populate with a number, when I debug the 5181 in mdi I still get #####.  I'm assuming the debug should yield the same number in the var file and not this symbol #####?  Which might be one of the reasons my tooltable is not populating?  I'm happy to provide any files, youtube videos, or anything else needed to help solve this problem.  I've learned a lot in the last month trying to solve this problem, any advice is much appreciated. 

Thank you in advance.  

Which user interface are you using? And which version of LinuxCNC?

#### generally means that the parameter doesn't exist, but that doesn't make any sense for #5181.

You are typing (debug, #5081) not (for example) (debug, #<5081>) ?

Thank you for the response,

I am using Axis gui with version 2.9.4.  I was using this format (debug,#<5081>) which yielded ######.  Upon your suggestion I tried this format (debug, 5181) which yielded the number in the var file....a big thank you for that clarification!!!! 

I think my main problem is that my tool table is not updated based on my 5063 variable.  When the probe trips the switch, I see the var file up updated, it stores tripped the z value in the 5063 variable, but that number is not populated in the tool table.  As a side note, I did have to add the 5063 variable manually to the var file.

Again, thank you for you time
 

You may need one of the G10 variants in your macro.
linuxcnc.org/docs/stable/html/gcode/g-code.html#gcode:g10-l0
Or possibly just a G43

Thank you, 

That would make sense, the G10 would populate the tool table and the G43 would assign the tool length offset.  I guess the mystery is where to add it to this ngc file?  And how did others have success with this code without those commands?   As you can tell I am really new to all this.  Attached is the sub routine I have been trying if you feel like looking at it.




 

Tool offset is set here:
If this is run at every tool change then there may be no need to write the offset to the tool table.