X3 Tool Settings Bug?

[peon]

In the operation manager, click the plus sign next to "properties", then click on "tool settings". Why don't my "toolpath configuration" and "material" settings match my operation defaults that are set through the control definition? I have material set to "none" and "use tool's step, peck, coolant" set in my operation default, but when I open a new session, "material" is set to aluminum and the "use tool's step, peck, coolant" box is unchecked. I have to repeat the procedure in the operations manager on every part.

[Dave Ball]

check in configuration to see that you are loading the correct machine for a new session

[peon]

I startup every new session in Design because I program four different machines. Once the new session is started, I select the machine I wish to program.

[peon]

bump

[Robert Bernobic from CNC Software]

FWIW, I just tried saving a default material and it worked fine. On the Files tab in machine group properties, is it pointing to the correct defaults file?

 

* If the .defaults file on the Files tab is the right one, you can edit the .defaults file right from there and not bother with the control def.

 

* If the Files tab is showing a different .defaults file than you expect, you need to select the right one in the Files page in Control Definition Manager.

 

HTH,

Robert

[Guest]

I sent this in to QC because I am seeing it too.

 

The defaults are NOT being loaded upon loading the machine def into a file, even though they are set properly in the OP defaults.

 

Here's what I get

 

going to check

 

Here they are properly set

 

Something isn't right

[ToolMan184]

Dont forget to change it in the .MMD under the tool/material libraies.

[peon]

John, that is EXACTLY what I'm encountering! I'm working with Chris Bell as we speak.

[Guest]

As am I

[Robert Bernobic from CNC Software]

Ah, I spoke too soon. I tried changing some of the other parameters also, and now I see the problem you're having. I agree, looks like a bug. I'll log it myself right now.

 

--Robert

[Guest]

A picture is worth a thousand words

 

Seems this got broke late, I don't recall this earlier on in testing.

 

Thanks Rob

[peon]

You beta testers SUCK!!! JK. Hehehehhehe!!

[?Mark]

quote:

---

Something isn't right

---

It appears that if you use custom defaults file it still reads some info (tool settings) from the original file named mill_inch.defaults

 

edited

[peon]

Thanks for that pic John. Typing all this crap out and trying to explain myself is for the birds!!!

[peon]

Chris has sent me the following message:

 

Hi Matt,

I figured this out. Those values are ALWAYS being read from Mill_inch.defaults or Mill_mm.defaults, depending on what unit you are using at the time. If you change the defaults in there, this will work “correctly” (as a temporary workaround until this is actually fixed).

 

This has been logged as bug number cnc00038340. Thanks again.

 

Chris

[Guest]

Nevermind, brainfart, I got the workaround

[Leandro]

Wai. Wait. Wait.

I have got different configurations.

Actually this is the most important function for different Machine and Control definitions.

I have one configuration for my xxxxor control and anotherone for my Simens control.

I can not change my .DEFAULT file in one of my differnet machines it will not mach.

¿What cann I do? Wait three month for a SP?

I don´t think this right.

[ToolMan184]

Just remember to change it in your operation manager on each file.

[Thad]

Leandro,

 

You can have multiple .defaults files. Make one for each control and assign them appropriately in their respective configs. For now, anyway...

 

EDIT: After re-reading Chris' reply, that may not work.

 

Thad

[peon]

Leandro, I'm considering going back to X2 just because of this until the patches are available. I don't see many advantages upgrading to X3 other than verify working much smoother and the lag is gone. My reseller assured me that the crunch times would be dramatically faster and I waited what seemed an eternity only to be disappointed.

[Leandro]

mattstang70 I agree with you.

This is a big mistake I´m wondering why nowone note this before.

 

Thanks

[Guest]

It's Keeblers fault

[Leandro]

Keebler ???

What does that mean??