Hi all, I would like your opinions on whether this is a gCode sending issue or CAM issue? I tried a cut into some Maple last night and it was going well until about halfway through the cut. The machine started milling in a new location and the shape was scaled down from the original cut. It almost looks like the machine origin shifted or something. I was using Coolterm with CTS mode to send the gcode over via text file. I will try on chillipeppr tonight to see if that fixes things. On Fusion360 the toolpath looks correct so I’m guessing this is a code sending issue? Any thoughts on this are welcome!
Looks like you skipped steps
Might agree on the skipped steps but the scale went down so not sure that’s it. I’ve heard of funny things coming from 360. Do repost going through CP.
It would be slow but have you tried reading the code to see if 360 produced the correct code?
Have not done this yet. I’ll try chillipeppr first then dive into more tedious efforts
One other thing I was thinking: could this be a CTS vs XON type communication issue? I noticed in @Brandon_Satterfield ’s tinyg setup codes (from smw3d forum) he has XON Communication mode selected. I’m guessing this is wholly dependent on the gcode sending software used, but I know Coolterm can do both. I might try it on Coolterm using XON instead, in addition to chillipeppr.
Update: same gcode file worked fine on chilipeppr. First time using chilipeppr, too! What an awesome open interface. The actual cut went well until I realized I didn’t add tabs to the CAM and had to abort 
@Darren_Lee congrats bro!
Another awesome open option is bcnc, and it has alot of additional options as well. It has a few requirements but once installed and running it is solid. I have been using it for over a year on my homebrew cnc with no problems.
Good to know, thanks Bob. I’ll have to look into it