New Problem on M998

[slowtwitch]

Thanks so much , Gerry.

[zephyr9900]

Indeed, thank you, Gerry. I have been running PCNC/Mach3 since 2006 and didn't even know that button existed. (I have only been off the Simple Run screen once in the past 3 or so years, and that was to reset M998 height...)

I have added the button to my tweaked version of the PCNC screenset. After experimentation, I see that it doesn't blank the toolpath window or anything, just stops interaction with it. I can still display the loaded gcode to make sure it's what I expect, then turn off the display updates.

Randy

[ger21]

If you switch screens while it's turned off, it will go blank.

[dbrija]

I had this issue using MachStdMill. The issue is that by having M6 Tx G43 Hx on a single line is that there is no guaranteed order in which the tool change and the offset application happens. I had a near crash into a vise, and numerous z axis limit switch trips before I solved it. I was not using M998, but what MachStdMill does is its equivalent.

I changed my post to output:

M6 Tx
G43 Hx

Seperating these operations allows my machine to move to TC position every time with no issues.

[SquibLoad]

s2jesse

You have a comment straight after the M998 it must be here (-------------)

You can only place comments at the beginning of a program, & to the side of the code
Not under any code lines

Is this true?

I've written quite a bit of code with fairly extensive comments on additional lines and had no problems. Maybe that's dumb luck.

It appeared to me that Mach just ignored comments, much the same as 'white space' in most programming languages.

Is this stated somewhere in Mach docs as being prohibited or not recommended? I haven't run across it, and I'd like to read up on it so I could make sure I do it correctly if it truly is prohibited. I like to put LOTS of comments in my code, and I do all hand coding.

[Bob La Londe]

Is this true?

I've written quite a bit of code with fairly extensive comments on additional lines and had no problems. Maybe that's dumb luck.

It appeared to me that Mach just ignored comments, much the same as 'white space' in most programming languages.

Is this stated somewhere in Mach docs as being prohibited or not recommended? I haven't run across it, and I'd like to read up on it so I could make sure I do it correctly if it truly is prohibited. I like to put LOTS of comments in my code, and I do all hand coding.

I run code with hundreds of thousands of lines of code with comments throughout. My CAM software inserts MOP title comments at the beginning of every machine operation. Mach has never seen fit to hiccup over them that I am aware of. In fact Mach displays the last comment passed at the bottom of the main screen, and creates a temporary log file of comments. One of the things I want to do if I ever get around to creating my own screens is eliminate the tool path display on the main screen, and have it display a long list of recent comments in that space instead. In big 3D job files this would be much more useful for tracking job progress than the toolpath display anyway.

[mactec54]

dbrija
Is this true?

Yes 100% correct, Mach control is very user friendly, & let's a lot of programing mistakes run, But some it will not

In the real world if you programed like a lot that you see on here, you would never have a machine in your shop running, You can get a way with somethings, But it's better to learn to do it to a standard format, & you never will have a problem

The comments was not the main problem that s2jesse had with his program his next line of G-code is what stopped the control

G0G94 You can not do this as the control would not know what to do

Program formats can be done in many different ways, But for guys with home shops, & need to get things going, keep it simple then you will never have a problem, Lean what G-codes you need to use & what each G code will do, & all your problem will go away as far as the control goes anyway

I have attached a simple program, does Mach need all this to run, no it does not, can it be done other ways yes it can, but simple is best & gets the job done, Press start & go do something else, & never have to worry if you are going to have a crash or the control stop because of problem with some code not being to the controls liking

[s2jesse]

dbrija
Is this true?

Yes 100% correct, Mach control is very user friendly, & let's a lot of programing mistakes run, But some it will not

In the real world if you programed like a lot that you see on here, you would never have a machine in your shop running, You can get a way with somethings, But it's better to learn to do it to a standard format, & you never will have a problem

The comments was not the main problem that s2jesse had with his program his next line of G-code is what stopped the control

G0G94 You can not do this as the control would not know what to do

Program formats can be done in many different ways, But for guys with home shops, & need to get things going, keep it simple then you will never have a problem

I have attached a simple program, does Mach need all this to run, no it does not, can it be done other ways yes it can, but simple is best & gets the job done, Press start & go do something else, & never have to worry if you are going to have a crash or the control stop because of problem with some code not being to the controls liking

For informational purposes my program as is runs totally fine in mach. Without the toolpaths off. It may not be good practice if thats what your saying but that code worked fine as outputed from the 1.5 post in sprut.

[mactec54]

s2jesse
For informational purposes my program as is runs totally fine in mach. Without the toolpaths off.

What I put in the last post has nothing to do with having toolpaths off

[s2jesse]

Guess im confused then. I thought you were saying a line in my gcode was causing a failure. The code runs fine aside from the mach bug with tool paths on. But yes wirting g code to typical standards is probabaly always good

[dbrija]

dbrija
Is this true?

In my case, it was the only explanation/solution. I worked with Dave at Calypso Ventures, and we were able to duplicate the problem/solution. I cannot say it will impact all Mach users the same, as it may have everything to do with processor speed, etc.... likely a case by case scenario. It could even be MachStdMill specific, but some of the symptoms in this thread mimic the issues I had.

[FleaBiscuit]

Was there ever an absolute resolution to this?

My 1100 S3 just started doing this same thing....it's only a month old...