Both could theoretically be combined into one Correction Table. But I agree that might be complicated especially if at different grid spacings.I know I could use the current Geo Correction for now, but in the future I will not be able to also use the Geo Correction for work and part correction/alignments.
I think this is actually the most efficient. Once the tables are combined the data only needs to have one table applied to it.
Probably not a significant consideration.It is also forcing me to burden the system with 245 x 245 instead of 245 x 2 (one for x and one for y).
I think that is correct.I need to look back, but I think I would also need to change "m_MotionParams.MaxLinearLength" to match the 0.2" and recompile anyway.