All,
An update:
I have been trying to understand why my CNT Motion router 'gets lost in X' for a long time. I decided in early July to take a more structured approach to trying to understand this problem. I have performed a number of simple, parametric tests.
So far, this is what I have learned:
1.) The machine works very well. My problem is not a CNT Motion router issue, except that there is no programming info/training guide available. So, it has been a long learning curve. I don't consider the WinCNC reference manual a programming guide. It provides no syntax, etc., on how to properly use many of the G and M codes. Also, that manual does not have all of the M codes available on my machine. Many have been written by CNT and I can not get a listing or any other info about them. Purely trial and error. Not a good way to run a business - - -
2.) It is a software problem, not hardware. I have eliminated WinCNC and editNC (my G-Code editor) as the root cause of my issues. It is CATIA and how I, and others, have the basic CATIA options set up.
3.) If I run a simple G-code program I have written, including tool changes, work offsets ("HOME" as CNT calls them - how STUPID!), etc., the machine works flawlessly. These programs can be written in a basic text editor or editNC. Doesn't matter. When I try to run a more complex program from CATIA, I have problems.
3.) So, I am trying to identify the reasons the CATIA I use does not give me the tool path output needed to make a part. The WinCNC viewer shows the program tool paths are PERFECT, but the actual part is not correct - sometimes WAY OFF!
So, still working on the problem. I will update again when I have more data.
Regards,
Joe T.