Posted out ops all mixed up

[honeybunches]

Never seen this... ops are in a certain order in the mcx file. Post them out and they are all mixed up. It seems to use the tools in the right order but for instance I have 10 ops with T7. It gets T7, then just does what ever it wants. Totally mixed up from what I have organized in the tree. Post is proved out. No issues. Verify and backplot show things correctly but when posting out, it gets all screwed up. ideas?

[honeybunches]

Also, when I try testing by selecting only 3 operations, it will only post 1 and will not ask about posting all of them. I have already rebooted everything to try and solve the issue.

 

This is in X2MR2

[honeybunches]

In further testing, it seems there are 2 ops that just do not post out. I thought they were getting mixed up. if I select either of the ops by themselves, they will post, if they are in a group, they are ignored. Is this a settings issue or are the ops corrupt?

[gcode]

Make sure all you OPS have the same name

in the Ops Manager

Select All

Right click

Edit common parameter

Change NC Name

[honeybunches]

you nailed it on the head! Can you explain that a little bit to me as to how that might get screwed up? I did not have an NC name so I named it and output it. That picked up the other 2 ops. Just want to see what I missed here.

[gcode]

NC filenames are controled by the

NC File settings on the Toolpath Manager

page in Systen Config.

I have mine set to

Prompt

1st OP only

Last OP's NC file

This seems to work best for me..

Did you import the ops that caused

you trouble.. sometimes

imported operations try to keep

their old name.

Normaly I Select all ops and set their name

as a saftey feature before posting..

It sucks when a pocket roughing operation

gets dropped from a file and the finish endmill

dives into solid stock cause ther ain't no pocket.

[honeybunches]

You got it! Missing ops cause crashes. Just glad I caught it and knew what it was supposed to do.

 

The ops in question were not imported and did post out fine last week. I would really like to learn what caused the issue and how else to access the NC file name for each op. I did notice it was trying to post the NCI file for some reason and I had to turn that off. Maybe unrelated though.

 

You know, trying to learn something so that inevitable crash never happens....

[MotorCityMinion]

Perhaps opening an existing program, then renaming it, then creating some new ops would do this also.

[honeybunches]

ON another subject, maybe you could help me determine why I cannot change my feedrates for multiple chains in an operation. I typically would use the "change at point". I alter the feed rate for one chain, and it does not post out with it bur rather the one that is programmed in the tool settings for the op. It gets frustrating having the remember that every time I post...

 

Drill depth changes work great. Been doing it for a while. Not sure what I am missing on the feed side of things.

[gcode]

If you turn the ASK button on in your posting page

you will catch these problems as you post.

You'll hit post and it will say

1234.nc ??? and you'll say OK..

It will crunch a while then ask

1238.nc??? and you'll know something is wrong..