Don’t blame you for your frustration. Despite making significant progress on my own, (trial and error), I have not found a source of support. But I have meticulously documented the travel errors between F360, TinyG and ChilliPepper in inches and mm. A crash dump $$ for different machines would be helpful. But the only ones I have found don’t identify the machine adequately and the settings are critical. I feel the weak link is with TinyG which is where the machine parameters must be set. Having to use several documents thru links with inconsistent instructions, nomenclature and references makes the documentation a PITA. I have virtually written my own yet through careful measurement of the results have found (I believe) a mathematical error in TinyG. (Which could be related to how it interprets post processed files, and inadequate descriptive information in F360.) Challenging is a single setting can cause the file to fail to generate gcode. So if you need to create consistent and a variety of parts there is a lot of work ahead of you. Solution: Spend a lot more money on a great machine.
.
