Nope, no way of setting a default.

I sent it into QC and it's been added to the list.

Cheers

Thanks for the help guys.

It wouldn't regen and the stop sign was at the bottom of the dirty tree.

So moving it didnt do anything and it just stayed dirty throwing errors and then added some out of memory ones as well?????

The good news is in opening a new file/starting over, I imported all operations from the previous file, re-assigned the geometry and all is good.

Bloody good feature import operations

Oh no - not the need for yet another enhancement request???

Hi All,

Just had a file go south.

All was ok (was a step file imported, saved as mcx ok).

Added a couple of toolpaths to it ok.

All verified ok.

Then it threw an alarm saying 'problem regenerating chain - regen solid'.

1. How do you do this?

Now on opening the file, it errors saying

'Problem regenerating chain' I hit enter then

'Error reapplying operation. Regen not complete' I hit enter then

'Parasolid kernel error PK code 22 tag is invalid or dead' I hit enter then

Same again for 6 enters.

Help please!!!

???

Keith

I looked where you said and there's

Update Cplane and Tplane when changing Gview (this is ticked)

Reset Tplane to Top when changing Gview (this is ticked)

Enable trim preview (this is ticked)

I don't see 'Update gview when WCS changes'???

Hi All,

View manager - 'Update graphics view when WCS changes' default is off, so I select/tick it on.

Is there anyway of making this stay as a default ticked on?

I can't see anywhere in the config file or m/c / control def files?

Thanks

If the hydraulic's he shows you are black, that is the new ones. We run them and they have a lot more holding force.

As for price, it works out around £200 for a holder and collet for us, but you're obviously talking dollars so ???

Once everything is set-up, then its not noticeable. It just took a bit of setting, and understanding

I do like the idea of being able to swap between machine types and then just post. So yes, I guess to me it's better.

Mick,

I just recently started playing with these paths and came accross the same question/thoughts as you.

So it sounds like enhancement requests are required???

Thoughts everyone please and I'll submit one to QC.

Cheers

We run a 17-4ph job a couple of years ago and had the oportunity of running seco V sandvik inserts.

Wet made the inserts last twice as long as dry, no matter what we did.

Well I had a little time to play with settings.

On the nvidia control panel>3d settings>adjust image settings with preview, I selected ‘Use my preferences’ as opposed to ‘Let the 3D application decide’, chose quality and all seems well (so far….).

Lines are crisper as well.

Cheers

Yep - for cheap mtl bish bash bosh out the part, measure and adjust then you're good to go!

Saves pu(another word for cat but it won't let me write it damn political correctness)ssy footing about.

Definately steel and not cast iron???

I'd be very cautious if it's a new (to you) chuck and you don't know the history.

How many bangs has it taken???....20" is a lot of inertia.

In our defence we're blokes who don't read manuals or instructions!

Mike, I think you have to reset all the tolerances to .0001 by memory and then regen.

Read back throught a couple of pages and the 'instructions' are there.

Have you contacted CNC to see what they say?

MCM,

Thanks for the reply. I just read your linky and are you saying that running solidworks messed up mcam?

If yes that's interesting, as I just fired up Inventor LT on this machine.

I was running autocad LT ok, and I'm sure mcam was ok as I have only just noticed the ghosting, which may point to Inventor corrupting mcam *somehow*, just like solidworks did for you.

I'll have a look at the other link (tweaking) and report back!

Cheers

Hi all,

On the 'new home build' pc's, we thought we'd try GeForce GTX480 graphics cards.

This is because they are cheap, a few on here have said they work well, oh and did I say they were cheap

So, we're running windows 7 64 bit, and have now noticed when deleting, there are ghost lines still there.

Roll the mouse or refresh and they are gone.

The funny thing is that we didn't notice this to start with, but they must have been there.

So, if anyone is running this card and it works well for you, are you using default settings or have you changed anything?

Cheers

David, thank you for the reply. There's certainly some intersting things coming.

We've stayed away from X5 waiting for mu1 for the same reason as a few above have. We totally skipped X3 because the reports on here frightened us to death! We're only a small company and are always up against it with timescales, so the last thing we want is 'problematical code'.

We (like everyone) want code that we can trust and just run.

BUT, it begs the question that if everyone stayed away from X5 and waited for mu1, then mu1 would effectively be the same as X5, with lots of the bugs not noticed because 'no-one' is using it.

If we all went for the X5 release, then more bugs get noticed earlier, and therefore more get fixed earlier???

So, is it wiser to go Beta testing (and expect bugs), and at least get the early benefit on cycle time reduction with the new paths?

I think we'll have a chat at work about this tomorrow, as i'm starting to lean towards one seat having X5 while the other perhaps stays at X4?

Bob - that's a really neat part. Hats off to you.

David - Please don't split out the trochoidal toolpaths and make them an option. That will REALLY suck.

Frosty - thanks for this.

I have downloaded your file and will give it a go. It looks very promising from what you have said.

Cheers

Programmers working for the programming manager working for the Engineering Manager is where I used to work.

As always, everyone has different skill sets, so different types of jobs used to be given to different programmers.

HTH

35k,

What machine are you running??? That's scary speeds and feeds...

FWIW we run chevalier machines (fanuc 0imc). 24T, 10K spindles, thru tool coolant.

We rout at 4-5 metre feedrates quite regularly with G05.1 and they did take a little setting up (parameter wise).

But we have 3 of them and they out perform the old hitachi seiki vs50's were we used to work.

They are excellent value for money and I'd recommend them without hesitation.

James,

Nooooob question....is the number of threads the same as the number of cores?

And obviously they should match as there's no benefit for upping the number?

Thanks