Work with probe

okay, so i changed the toolsensor and change_position variables to be -20 (or something random) and 0 respetively. Things work mostly fine, but there's still a small catch.

i'll run the code, and it moves the spindle to the tool position, and then ask me to insert tool X in. Right now, since i'm not using a tool height sensor but just doing it before running the gcode, I don't have the "Remap M6" box checked on the probe screen.

The problem i'm running into now is that after i click okay saying tool X is installed, the program basically stops. i can get it to run again by refreshing the gcode file or by reopening it, and then running it again. When i do this it moves the spindle to the tool change position, and then goes straight to cutting, i'm assuming because it already knows the i have tool X installed.

Anyone know why this might be happening? Also, while it's running through the remapper program, it highlights the lines of gcode on code that i loaded to cut my piece. so for instance when it gets to line 31 in the remapper code (which moves the spindle to the change position location) it's high lighting my gcode for cutting, which of course are completely different files... could this have something to do with it?

Anyways, It work mostly working now, and it's not a huge hastle to reload the gcode, unless it's a large file, and then it take a minute or so to reparse through it.

thanks for any help!

Are the hal pins iocontrol.0.tool-change - tool-changed and iocontrol.0.tool-prepare - tool-prepared connected properly?

right now they're commented out i in my main .hal file, though they are defined in the psng.hal file in the psng folder. Attached is the psng.hal file.

I'm thinking it's pointing to this psng.hal file from this line below in my main .ini file

EMBED_TAB_COMMAND=gladevcp -c probe -x {XID} -u psng/python -H psng/psng.hal psng/psng.glade

gerrg wrote: right now they're commented out i in my main .hal file, though they are defined in the psng.hal file in the psng folder. Attached is the psng.hal file.

That all looks to make sense, assuming that the right things happen in the probe component.

(I am a bit vague on what the current setup that you are using is)

right now, my probe is a piece of copper clad with 24V connected to it, and the input to my mesa card connected to the bit. I think this is an okay method, but i'm also welcome to any input there

right now I'm able to probe to find my Z height and such, but right now the problem is when I run my Gcode, it goes to the tool change line, asks me to insert Tool #3 or whatever, and then basically stops. I can refresh the gcode and run it again, and then it doesn't ask me to insert Tool #3 (since i assume it remembers that's what's currently loaded) and then executes the gcode as normal

What does psng/python look like?

If that is a file name then perhaps you should rename it. It's just possible that there is a namespace clash.