You are not logged in.
Scenario,
I’m making multiply cuts along the tool axis on a slightly angled wall.
Question,
Not sure, but I seem to recall in 5.4.5 you could stop in between any of the passes that I’m taking along the tool axis and change the color of that pass? Is it possible to do this in 6.1.2?
Logic,
When stepping down along the tool axis I’d like to use multiply cut colors going down along that wall instead of clicking reset cut color each pass.
Thoughts?
Offline
That's easy to do in NCL
What system are you using to program in ?
Dave Frank
Aerospace Dynamics International, PCC
Valencia Ca
"Where else can you have this much fun,.......and get paid???."
Offline
Here is the NCL code.
You can probably get creative and do something like it in a vericut subprogram.
Put some PPRINT in each pass retract macro that triggers it
Than do a substitution
$$
COL1=0
$$
COLCHG= MACRO
IF (COL1'EQ'6) COL1=0
COL1=COL1+1
$$
DISPLY / OFF
PPRINT VERICUT-CUTCOLOR @COL1
DISPLY / ON
TERMAC
$$
Dave Frank
Aerospace Dynamics International, PCC
Valencia Ca
"Where else can you have this much fun,.......and get paid???."
Offline
Programming in V5, Transferring data to Vericut via Catv.
Offline
Is this what you are trying to do???
Dave Frank
Aerospace Dynamics International, PCC
Valencia Ca
"Where else can you have this much fun,.......and get paid???."
Offline
Dave,
That looks to be exactly what I’m after. Excuse my ignorance, but going from a user to expert overnight, could I ask you to post the step by step on how you went about getting these results? I’d like to thank you for your expertise and time. Maybe with enough interest this could be a future enhancement? Thxs Dave!
Offline
First, are you running Vericut with G-code, or the Aptsource.
Dave Frank
Aerospace Dynamics International, PCC
Valencia Ca
"Where else can you have this much fun,.......and get paid???."
Offline
G-Code
Offline
My friends at CGTech support tell me that Vericut 6.2 which is in Beta as we speak, has a MACRO for PPRINT VERICUT-CUTCOLOR =n
I like this functionality, so when I make it work for myself, I will pass it along.
Dave Frank
Aerospace Dynamics International, PCC
Valencia Ca
"Where else can you have this much fun,.......and get paid???."
Offline
I have an Idea, with the vericut we have today
in catia, add a postprocessor statment to the linking macro
PPRINT/VERICUT-CUTCOLOR
Have the postprocessor count the numbersG-code (Fanuc) => (VERICUT-CUTCOLOR 2)
I am using ICAM to post
If you are, I can tell you how to write a PPRINT MACRO that can parse this pprint, and loop cycle the color numbers
This is what you want g-code
(VERICUT-CUTCOLOR 1)
motion
(VERICUT-CUTCOLOR 2)
(motion
VERICUT-CUTCOLOR 3)
motion
(VERICUT-CUTCOLOR 4)
motion
(VERICUT-CUTCOLOR 5)
motion
(VERICUT-CUTCOLOR 1)
motion
(VERICUT-CUTCOLOR 2)
(motion
VERICUT-CUTCOLOR 3)
motion
(VERICUT-CUTCOLOR 4)
motion
(VERICUT-CUTCOLOR 5)
motion
Here is from the manual
VERICUT-CUTCOLOR record
Special comment records that assign the cut color for the active tool. Cut colors are referenced via an index corresponding to the colors defined for use via the "Shade Color list" on the File menu > Colors: Define tab. Color index numbers range from 0-n where “0†refers to the first color in the list-typically assigned to be the Error color. “1†refers to the second listed color, and so on. The index number is always 1 less than the index seen in the user interface. Examples follow.
Note that for G-code tool paths, the NC control must be configured to interpret the comment record format for that control, for example "begin comment" word, "end comment" word (if present), etc. See "Controlling VERICUT with comment records" for simple examples.
Examples of use:
Set the cut color to "Light Steel Blue", as referenced in the sample Color window below:
APT/CLS => PPRINT/VERICUT-CUTCOLOR 2
G-code (Fanuc) => (VERICUT-CUTCOLOR 2)
Dave Frank
Aerospace Dynamics International, PCC
Valencia Ca
"Where else can you have this much fun,.......and get paid???."
Offline
Just to elaborate, The picture I posted was created using Aptsource, from NCL.
The trick is getting the cut colors to cycle, ( 1,2,3,4,5,6,1,2,3,4,5,6)
I did that as described, in the NCL Macro.
Even after they implement the cutcolor macro, you would need to branch to a subprogram, to do the Looping logic
Looping logic could also be done, with the postprocessor, and probably with a VB Script in Catia.
You could take the low teck way, and manually edit the PPRINT/VERICUT-CUTCOLOR ( 1,2,3,4,5,6,1,2,3,4,5,6), in the area you are trying to examine.
Where this kind of color control is handy, is for tube machining, IE, shrouded impellers, and similar parts. You can see bleeding of on pass to the next, if the overlapping motion is flawed.
I have sent in a Enhancement request to CGTech support, for a PPRINT cutcolor next, or PPRINT cycle cut color that would do this automatically.
That would eliminate the need for all this fancy logic, to get the cut colors to cycle,
Dave Frank
Aerospace Dynamics International, PCC
Valencia Ca
"Where else can you have this much fun,.......and get paid???."
Offline
That is pretty incredible Dave.
I'm struggling to get programs done and verified.
And you guys get to play with colors.
It's amazing all of the stuff you can do with Vericut. I spend equal times programming and Vericutting.
Amd I'm just using the basics.
I enjoy popping in to see what others are doing. There's a lot of info here to learnfrom.
I hope to see someone make that work for CATIA. Maybe I'll mess with it one day.
Offline
That is pretty incredible Dave.
I'm struggling to get programs done and verified.
And you guys get to play with colors.
It's amazing all of the stuff you can do with Vericut. I spend equal times programming and Vericutting.
Amd I'm just using the basics.
I enjoy popping in to see what others are doing. There's a lot of info here to learnfrom.
I hope to see someone make that work for CATIA. Maybe I'll mess with it one day.
Offline
A simple way to change the cutcolor in Vericut? Use the macros:
UnLoadToolNoRetract
ToolChangeNoRetract
Just using "ToolChangeNoRetract" by itself does not work (6.2 Beta)
----------------------------------------------------------------
For example, if every cut sequence has a RAPID at the beginning then incorporate these two macros into the G0 logic in the control file.
WORD_VALUE "G" "0" {
MACRO "UnloadToolNoRetract"
MACRO "ToolChangeNoRetract"
MACRO "MotionRapid"
}
Or just when changing to RAPID from a non-rapid state:
WORD_VALUE "G" "0" {
COND_STATE_AND_NOT "MOTION_TYPE" "Rapid" {
MACRO "UnloadToolNoRetract"
MACRO "ToolChangeNoRetract"
MACRO "MotionRapid"
}
MACRO "MotionRapid"
}
Or use some other code that may be used between motion sequences.
----------------------------------------------------------------------------------
Or add a specific comment where a color change is desired, define it as a "WORD", and add it as a Word/Address which uses the two macros mentioned above.
APT command: PPRINTCHANGECUTCOLOR
G-Code: (CHANGECUTCOLOR)
Add the following to the WORDS section of the control file:
NAME "(CHANGECUTCOLOR)" {
TYPE MACRO_CALL
VALUE_TYPE None
}
Then add this in some SUPERGROUP:
WORD_VALUE "(CHANGECUTCOLOR)" {
MACRO "UnloadToolNoRetract"
MACRO "ToolChangeNoRetract"
}
The downside to this approach is that there is a comment in the G-Code file that is not needed at the machine, makes the "tape" longer, and could confuse the operator/machinist.
Jerry
P.S. You might need to watch out for "Look Ahead" tool logic.
Jerry Millett
Offline
Nice Jerry
Your pretty creative with the Vericut we have today.
Here is the ER
Description: Enhance to add VERICUT-CUTCOLOR NEXT
SCR Type: ER (PR= Problem Report, ER= Enhancement Request)
Tracking #: SCR #2977
Dave Frank
Aerospace Dynamics International, PCC
Valencia Ca
"Where else can you have this much fun,.......and get paid???."
Offline