RGSparber wrote: ↑Fri Jan 12, 2018 6:46 pm
I'm going to be away from my CNC for a little while so will pick up this mystery ASAP.
Thanks for all of your help,
Rick
Damn! It has been a LONG while. I'm back on my mill now and seeing a 327 fault. Besides having totally forgotten about this thread, I've had a major Windows upgrade plus upgraded CNC12 from 4.12 to 4.64. This fault occurs at different points in my code.
Your comment is very helpful. I don't have my probe connected and I'm far from any limit switches. There may be noise getting into these lines. Time to pull out my 'scope.
Rick, were you using or testing the probe since you installed 4.64?
Is the machine homing OK?
What kind of switches do you have for homing?
Also, are you setting your part zero positions correctly? Do you press F8 to Graph the part prior to running the part to see if you getting any axis exceeded errors?
Marty
Reminder, for support please follow this post: viewtopic.php?f=20&t=383
We can't "SEE" what you see...
Mesa, AZ
I have tested the probe since installing 4.65. I had previously set Part 0 and then power cycled. Then I measured the location of part 0 wrt Home and it was off by 4 thou on the X axis, 8 thou on the Y axis and 5 thou on the Z axis. My home switches are magnetic proximity switches.
Murphy is certainly watching over me. I wanted to gather information on the failure so ran the program again. This time it ran for almost 20 minutes before I got the 327 fault. Previous runs were under 10 minutes. No other information on the screen. I was unable to move the tool via the control panel until I did a Reset. Maybe that is one piece of the puzzle.
I am confused by what, exactly, 327 means. I'd also like to know what file in the report zip file contains all of those faults with time stamps.
I'm fairly sure I'm dealing with a noise problem here since the run time before the 327 varies. Knowing what conditions caused this fault would help me focus my attention in the right area.
I wasn't aware of F8 for graphing the part but will certainly do that next time. I do run my gcode through ncviewer.com to review the paths. It said all was right but the part is coming out shifted by more than 0.1" both in the X and Y directions. Yet, when I check Part 0, it is reasonably close to right.
If you get the fault again after changing your inputs to HomeOk
Please take a screenshot using the Windows SNIPping tool and post it here along with a fresh report.
Reminder, for support please follow this post: viewtopic.php?f=20&t=383
We can't "SEE" what you see...
Mesa, AZ
With the spindle motor off, I did not have any problems for about 150 lines of code. With the motor running and under load, I got the 327 fault again. I have attached a screen shot plus the latest Report. I then made the change that Marty suggested and it failed at line 43 with the same 327 fault. I know the point of failure changes each time I run.
I'm still confused by what 327 means. If it is just a pointer into the Report for more information, what does it say?