Centroid Community CNC Support Forum

CNC12 V5.06

After loading a program, it can only be seen when you press start, so it is processed immediately. Bug or incorrect settings? At the end of a program, the display stops at M30. Bug? Definition of: Command M30 ends the executed program of automatic mode and jumps back to the beginning of the program.

Programs are displayed when running. They are running once you press start. The control is behaving correctly. M30 stops the program. When the program ends, the program window displays the last line executed. Again, proper control operation.

Houseman303 wrote: ↑Tue Dec 26, 2023 4:55 am At the end of a program, the display stops at M30. Bug? Definition of: Command M30 ends the executed program of automatic mode and jumps back to the beginning of the program.

The definition of M30 is clearly described in the Centroid's Mill Operation manual which I suggest you refer. The September 2023 version describes this as follows in section 13:

13.19 M30 – Custom M-code
An M30 is posted at the end of every G-code program. M30 as an end of program code is an industry-standard. By
default, M30 performs no operation. If you wish to perform certain operations at the end of every program, this M-code
can be customized to meet you needs. For more information on customizing M-codes, see the beginning of this
chapter.

So Tom is correct and no bugs at all

OK, M30 can be adapted if you know how. I still don't know of any controls where you load a program and only see it when you start it. That makes no sense!

Click edit to look at the g-code.

CNC12 is using NPP to view/edit g-code, IMHO better than the build in editors of most other CNCs

Uwe

I forgot to mention that it's good practice to Graph a program immediately after loading as a quick and simple error check - something I always do.

As Uwe says, the Edit is there for viewing your code, especially useful when using N++ as the default and configured to your liking

Nigelo wrote: ↑Tue Dec 26, 2023 11:33 am I forgot to mention that it's good practice to Graph a program immediately after loading as a quick and simple error check - something I always do.

Good point Nigelo, in my opinion this should be mandatory and not just "good practice" as I always graph every job before I hit cycle start. This is an awesome and under used feature of CNC12. Several people I've helped dont even know about it and just blindly hit cycle start after loading the job.

My fiber laser software wont even export the file for cutting without doing a similar process. This way I always know there are no errors with anything.

I simulate the program in the cam program. More important are the setup data for the zero point and blank, which are stored in my programs. After loading, they were immediately readable. now just awkward.

If you set origins in g-code it will be stored in the CNC only after running the g-code.

Some Siemens CNC are loading jobs, several files with g-code, tool lib and origins, ect.

Just another workflow as Centroid.

But if you like, write some code to store and restore the files with the g-code together, it could be done with a batch file or other scripting tools.

Uwe

Houseman303 wrote: ↑Tue Dec 26, 2023 1:37 pm I simulate the program in the cam program. More important are the setup data for the zero point and blank, which are stored in my programs. After loading, they were immediately readable. now just awkward.

Au contraire mon frère, simulating or graphing the cut in your CAM software does nothing unless it knows the limits of your CNC and where you've set your G54 zero, zero position in CNC12.