So is it possible to intercept the Gcode before it's sent to the controller? I need an audit trail of all Gcode instructions with parameters resolved to values for the purpose of hunting down errors. As you can see in the attached NC, it's hard to tell what the Gcode program actually did since most of the calculations are based on a measurement that's not known until the program starts.
A parameter is the # character followed by a number 1 to 10320. Previously I referred to these as variables. These are what need to be resolved to values in a Gcode trace, audit trail, or whatever you'd like to call it.
Can this be done with a VB macro, or does it require the Mach C/C++ SDK? If someone points me in the right direction, I'll figure out the rest. Thank you.