Manual entry

[milehighxr]

Why won't mastercam post a manual entry block out if it is my last operation? I'm on X8, and my post is a variation on the MPMASTER post. I don't use manual entry often, but I would like to figure out how to get it to post out the last manual entry when it is the last operation.

[Craig-B]

compare your comment section of the mpfan to the post you are using. you should see the difference.  

[Colin Gilchrist]

Add the 'comment$' command to 'peof$' on a line, by itself. That should trigger the Comment output.

[milehighxr]

That worked great, however, now it spits out my operation comments as code immediately after the tool comments.  Like below:

M5 M9
G91 G28 H0 Z0.
M1
(.75 INSERT MILL TOOL - 15 DIA. OFF. - 15 LEN. - 15 DIA. - .75)
OP2BAT-270D-
T15 M6
G0 G90 S2037 M3 E3 X-1.4556 Y-0.775
H15 Z2. T1

 

I can't seem to find where to fix it, but it started showing up after I did Colins fix for getting my manual entry to output at the end of file.

 

[Leon82]

Is it possible you inserted a comment line in there without open and close parentheses command

 

Or deleted the open or closed command

[Leon82]

That is information you entered in the tool selection page dialog box correct?

[milehighxr]

 

In the comment field above

[milehighxr]

On 12/1/2017 at 1:38 PM, Leon82 said:

Is it possible you inserted a comment line in there without open and close parentheses command

 

Or deleted the open or closed command

None that I can recall or find.

[Leon82]

In the start block there should be a if sopcom blank......

 

That should have open and close commands like in the picture Craig posted

[milehighxr]

Searched the post file, and it doesn't exist.

 

Here's my tool comment section of post

[jlw™]

i detest ucase(crap)

post it as i keyed it in.  sometimes i want the emphasis of ALL CAPS RAGE.

[Leon82]

Scroll down to the psof area and post screen shot

 

Idont have internet on my computer so a screen shot is a pita.

 

[Leon82]

Actually the tool change block

[Leon82]

[milehighxr]

first part of it

 

2nd part

[Leon82]

Yours is based off a different post it seems.

 

[nickbe10]

Run it through the debugger and watch how the op comments are being generated. That should give you a clue where to start.

[milehighxr]

I'll give that a whirl as soon as I can, and report back.

[milehighxr]

something like this?

 

[nickbe10]

Yes so it looks like it is the comment call in the PSOF post block. Compare that with the ones which are coming out with parenthesis and see if you can spot a difference. It's also giving you a postline number there which might also help you.

You want to set up a break point which will stop the post before this line so you can single block through the problem area.

Normally at this point I will be figuring out which variables or other trackable items are likely to change and set up a watch list. The other clue is the line below the out put line underneath this window which will sometimes list all the postblocks involved with the line of code being output, but you will only see all the relevant info. in single block.

Also keep an eye on the NCI window as this can sometimes give you a clue as to what's happening, for instance has it moved from one NCI line to the next.

Debugging is really something that improves with practice as you get your "eye in" with all the info that's showing. I've been post editing for about a year now and I usually have to run the debugger with different watch lists several times before I narrow down the problem. The biggest headache is setting a break point too far ahead of the problem and then getting caught in a parameter read loop, which can take forever in single block. Move your break point in that case.

Read the Debugger info and tutorial in the MP documentation, there is a vid. too, to help improve your debugging skills.

[Colin Gilchrist]

Your 'pcomment2' Post Block is causing all the trouble. 

It is only setup to "properly" process "operation comments", in the "old" style.

You have "if gcode$ = 1007", followed by an 'else' statement. That is causing your comments to be output "as code". You don't want that.

Copy the 'pcomment2' section from a fresh MPMaster, and paste it into your 'pcomment2' post block...

 

[Colin Gilchrist]

To be clear, you should "completely replace" the code in 'pcomment2'. Get rid of the if/else. There should only be "multiple ifs".

[nickbe10]

Ah, the voice of experience. Nice one Colin.

Milehighxr I would encourage you to still run this through the debugger. Now that Colin has narrowed down the problem it will be easier to set your break point. Don't forget to use single block.

Watch the two output windows below the main window to see how the code is generated. And watch the NCI window for when it reads the Gcode lines.

You will learn a great deal about how to solve these problems in the future.

[milehighxr]

On 12/6/2017 at 11:42 PM, Colin Gilchrist said:

To be clear, you should "completely replace" the code in 'pcomment2'. Get rid of the if/else. There should only be "multiple ifs".

Did that still no worky...

[Colin Gilchrist]

Are you sure you replaced the code inside the Post Block 'pcomment2'. (In other words, you removed the 'if/else' lines, that are indented, and replaced them with a bunch of 'if' statements)

We could play the guessing game all day, but it seems like you need more help than just a gentle nudge in the right direction.

Please save a copy of your PST file, with a '.mcpost' file extension, and email it to me: [email protected]

I'll have this fixed in 3 minutes.