Hi guys...

Been off a while.

Any drill and (feeds and speeds)recommendations for Inco X750.

I have 300 pieces with 12 holes per piece and 3 at angles.

Diameters are

.0595 for the 12

and .028 on the 3.

Depths are about .34 on the 12

and .15 on the angles.

I limped through for the first article.

That's funny, I started in '92 also.. may have been classmates

Me too. V3

I found that trying my own way navigating around any software (intention driven) and using books is a good start. Keep a notepad when you get stumped and check help files... if you can't find it UNDERLINE and ask in class...

I've only had one class and that was V7...Ugh!

Thank you.

For whatever reason the chaining dialog in X6 doesn't seem to work.

New upload.

Chaining dialog added.

I downloaded the latest upload. I still don't see the chaining dialog icon.

DOh!!!!

NCI file was correct, BUT the default was set to not restore entire toolpath in file get. Why on earth would you want that?

I am good for now, hopefully that TS folder doesn't show up again. If it does I will delete the config as you mentioned.

Thanks gcode.

Will do. Thanks.

All the folders are set to my local drive MCX folders. I changed from network to local to see if it helped. It did get rid of the TS folder which didn't exist, but it still won't save the toolpaths.

The toolpaths are there, just all dirty. I even tried doing a simple 2d contour and save but it comes back as dirty as well.

I would re install a third time if I weren't so damn busy. These jobs are due Monday.

I will look into that g.

So frustrating. I lost about 4 hours worth of programs from yesterday.

bump II

What ever is causing this is also corrupting the files toolpaths.

It will not save the toolpaths. When I try to open a file that I know had toolpaths...the file comes in with all the paths dirty.

I changed my file config to go to the C: to get away from the network and it still is messed up.

Anyone?

bump

Strange behavior...Network file save and get

If I start MCX and go to file get the window opens and the folder it shows is :Flight1TS

and it list the files.

Above the Folder window is the look in : and it states Flight1toolingcustomer namejob number....

If I choose one of the files listed it says folder doesn't exist. Which I know it doesn't exist.

Ok...so I back up into the correct directory and open a file.

Work on it etc.. and file save. Guess where it says it saves it to? Yep the folder that doesn't exist. So to work around it I

have to use file save as and back into the correct directory.

At the top of the screen it shows the correct path for the file too. Weird I tell ya.

If I check the configuration it shows the correct paths for file retrieval.

What the heck is going on?

Last time I tried to save I got MCam has generated an error send report yada yada yada.

Any thoughts?

Thanks. Oh BTW I just reinstalled a few weeks back due to hard drive failure.

Hi folks,

I have a tool design that I did in UGNX5 and I tried exporting step and a x_t and then tried to read in MCam X.

Every solid component comes in on a different level. I managed to place them all back on original levels in Mcam but when I exported it in a parasolid... again the levels dispersed everywhere.

I have a supplier who is using Mcam but I figured the X_T file is about 20% of the weight.

Is there something I am missing?

Thanks in advance.

I tried that John but couldn't get it to work right.

What I ended up doing is...

ptllncomp # Tool length compensation

if tlngno$ <=>0 , tlngno$ = t$ # If NOT set, default to same as tool number

if tlcomp = 1, *tlngno$ # Tool LENGTH offset number (FORCED OUT)

if tlcomp = 2, tlngno$ # Tool LENGTH offset number (IF Changed)

tlcomp = 0

<=> 0and checked it with length offsets at 150,235, and 250. The NC file came back with all H# equaling T#

Very good.

Thanks a lot.

Haven't had to deal with Mcam or post issues in almost two years.

Glad the forum is here. And you too John316

I am using the mpfadal.pst and I was wondering if I can place or if there is such a thing as a wildcard in the post.

This is what the post looks like...

ptllncomp # Tool length compensation

if tlngno$ = 0, tlngno$ = t$ # If NOT set, default to same as tool number

if tlcomp = 1, *tlngno$ # Tool LENGTH offset number (FORCED OUT)

if tlcomp = 2, tlngno$ # Tool LENGTH offset number (IF Changed)

tlcomp = 0

A guy on the floor went to reuse a tool in an operation and the length offset was set to 4. The tool number was 1. Needless to say the H4 posted with T1.

I have a tool library with all l offsets set to zero but apparently this tool he created and failed to change the length offset the second time through.

Is there a way to set the post overlook tlngno and post the H value = to the T#?

Thanks for any help I may get.

It's been a while for me and handshakes for Hurcos but I remember those errors.

The older machines had to run with flow control set to hardware/software even parity X on/X off.

I remember lowering the baud rate as well.

Quite aggravating. The machine would cut nearly halfway to finish and THEN get the error. DOH!

The X+ uses an xss file. I have been wondering the same thing. What file do you edit? XSS will not open with excel.

I love the setup sheet I just get complaints about the tl_nr or whatever the abbreviation is its using.

Also, if you add analyze to your rmb (right mouse button you can use this function even while backplot is running.

Not that the arrows do it but it gives you more options. Same with clicking on the !

If you click on the 2 blue arrows on the chaining options you can go back to last breakpoint. Instead of starting over from scratch.

I see. Makes sense I guess. Thanks Jody.

I started over customizing my toolbars and noticed there are a LOT of Single surface programs. What is the purpose for this?

Seems kind of redundant seeing you can pick one surface when selecting geometry.

Anyone use these toolpaths?

O/T...

Funny hunting story. My buddy "Kevlar" talk in his sleep especially drunk. We know of nobody named Troy. Anyhow Kev's passed out in the chair and says "Troy, what a cute little bottom he has". He was completely under suspicion after that.

Back on Topic. Forgot you are a die guy now Randy.

Hey, holy moly.

When they came out with electrode maker I could never get it to work correctly so I never bothered.

Now with this update it seems to be a huge help.

Randy have you tried it?

Still only works with surfaces, but geez what a time saver. I like it. I like that it will create the trode file and give the op man the electrode name AND call out your overburn. Or you can leave it on separate levels in the main file too.

Can't wait to see the html sheets. They look pretty cool.

Is it this guy Jay?