Cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Outputting the cdc d value

Gears Phenom Gears Phenom
Gears Phenom

I gave you solution in the end of my last post

---------------------------------------------
#♫ PB, 5ax, itnc, nx, vericut ♫ #

Re: Outputting the cdc d value

Valued Contributor
Valued Contributor

Ok after reading it again I see Ill try it thanks

Re: Outputting the cdc d value

Valued Contributor
Valued Contributor

d.PNG

Re: Outputting the cdc d value

Valued Contributor
Valued Contributor

would something like this work?

Re: Outputting the cdc d value

Gears Phenom Gears Phenom
Gears Phenom

I my last long commentary I describe how this variable works, when it doesnt exist and when does, etc.

 

No, this will not works - and it highly depends where this command is executed.

 

 

---------------------------------------------
#♫ PB, 5ax, itnc, nx, vericut ♫ #

Re: Outputting the cdc d value

Valued Contributor
Valued Contributor

I would need an else if doesnt exist =0?

Re: Outputting the cdc d value

Gears Phenom Gears Phenom
Gears Phenom

This variable exist on line with first G41, not sooner, never.

So this is useless for you.

 

I suppose you want DCD only in case when you are machining with cutter compensation.

You have to find other variable and do checking by another variable if cutcom is turned on.

 

(But if even if cutcom is turned on the path dont have to be generated with cutter compensation in some cases, but it doesnt amtter I think.)

---------------------------------------------
#♫ PB, 5ax, itnc, nx, vericut ♫ #

Re: Outputting the cdc d value

Valued Contributor
Valued Contributor

just want to post it on the tools that use cdc and has the settings on like you described ignoring the rest

Re: Outputting the cdc d value

Valued Contributor
Valued Contributor

ok no big deal to just edit it in thanks

Re: Outputting the cdc d value

Gears Phenom Gears Phenom
Gears Phenom

You can output it by your command but in the start of operation mom_cutcom_adjust _register variable doesnt exists - you will find that variable exists on the G41 line.

 

Type to your tool cutcom register for example 777 and postprocess with debug.

Then browse debug files and look for  777. The you can find  more varibles with this number.

And you can test them if they exist.

 

--

If you want to find some variable what can tells you if operation has path with cutter compensation 

do postprocess debug with cutcom on and second time with cutcom off.

Compare debug files - you can find some toggle switch variable etc..

---------------------------------------------
#♫ PB, 5ax, itnc, nx, vericut ♫ #

Learn online





Solution Information