> From: Nicklas SB Karlsson [mailto:[email protected]] > Den 2021-10-27 kl. 18:01, skrev John Dammeyer: > >> From: andy pugh [mailto:[email protected]] > >> On Wed, 27 Oct 2021 at 08:36, John Dammeyer <[email protected]> wrote: > >>> we don't actually see the calculated parameters from say the G53 lines > >>> nor whether it fails and the M71 is run. > >> Have you tried adding debug lines ot the subroutine? > >> > >> (DEBUG, G53 G0 Z #<_ini[AXIS_Z]MAX_LIMIT> + > >> #<_ini[PROBE_SCREEN]Z_SAFE_TRAVEL_OFFSET>) > >> > >> I admit that I am not sure that this works in remaps.... > > Where would this debug information show up if it did work? > > John > Small message in down right corner there errors use to show up you ever > had any. >
Making some progress. Found that CTRL-E gets rid of the PYVCP panel on the RHS so then the Probe screen is completely visible. The DEBUG statements do work inside the nested ngc files. This has helped discover that adding the required [CHANGE_POSITION] # Absolute coordinates of the tool change point X = 1 Y = 1 Z = -0.5 Into the ini file when there are already tool change positions in the [EMCIO] section causes a repeated movement. Was odd when the positions were identical as it looked like repeated. But change the EMCIO ones to a faraway value and then it's clear that after the move to the PROBE tool change position the system then moves to the EMCIO change position. [EMCIO] EMCIO = io CYCLE_TIME = 0.100 TOOL_TABLE = tool.tbl TOOL_CHANGE_POSITION = 2.5 2 -4 TOOL_CHANGE_QUILL_UP = 0 This did not show up in the debug messages. Just fluke seeing both there. John _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
