Showing results for 
Search instead for 
Do you mean 
Reply
Solved! Go to solution

Setting up 840D basic frame in MCF

Hi Guys,

 

Given the succes of this forum for my last question I thought I'd give this one a go too Smiley Happy

 

As before, I am configuring an MCF file for a specific machine with a Siemens 840D control

 

The machine has a crossrail which can be set to a variety of positions. The machine datum is aligned with this crossrail and as a part of this movement the subprogram that controls the crossrail appears to update
the basic frame using the following:

 

$P_UBFR=CTRANS(AXZ,_PC[53],AXX,_PC[52]):CFINE(AXZ,0,AXX,0)

 

...where _PC[53] contains the offset compensation value for the current crossrail position (e.g. -600, -800, -1000.0...). I am attempting to use the subprograms from the machine's ARC file as directly as possible.

 

The program then updates the settable frame using:

 

$P_UIFR[1,Z,TR]=70.
G54

 

In my simulation I am expecting to see the result of these commands being the machine datum being shifted by the compounding of these two frame offsets (e.g. -600+70=-530), as this is what appears to occur on the machine, however what I see instead is only the shift from the original machine datum to the settable frame from the $P_UIFR.

 

I've had a look at the GMe_SetFixedTransformation that is attached to the G500, G54...etc. and see only a reference to the $P_UIFR frame variable. My question therefore is, is there some additional configuration required in the MCF to make this basic frame work, given that the $P_UIFR frame setting works out of box (out of the CCF) and that I see an entry for $P_UBFR in the CCF file?


Is this a misinterpretation of how the actual control is working in this case (as with my last post!)?

 

Any help much appreciated.

8 REPLIES

Re: Setting up 840D basic frame in MCF

The answer is simple and not satisfieing .

 

The transformation of $P_UBFR is not part of teh OOTB CCF.

The variable it self is defined, but not used in any transformation.

 

Solution will be customize it, be add a transformaiton into the transformaiton stack e.g. name it "UBFRAME" and define a variable listener like this.

 

 

2017-03-10 16_19_01-XML Notepad - C__Users_schulz_AppData_Local_Temp_re_var_lns_mtd_tp_1489158981999.png

 

Hope it will do the job

Thomas

 

Thomas Schulz
Siemens PLM
Manufacturing Engineering Software

Re: Setting up 840D basic frame in MCF

Hi Thomas,

 

Thanks for the reply.

 

I don't see that method within my CCF (pulled from NX9.0.2). Is there any chance you could share the contents of the method?

 

Kind Regards,

 

Daniel

Re: Setting up 840D basic frame in MCF

Correct, as I wrote these variable listener is not part of the delivered CCF. You need to create it in your MCF; and make sure you add a related transformation into the transformation stack.

 

Thomas Schulz
Siemens PLM
Manufacturing Engineering Software

Re: Setting up 840D basic frame in MCF

Hi Thomas,

 

I understand the creation of the variable listener, but you referenced a method (GMe_SetTrafoByFrame) which is not available for me to use.

 

I attempted to create a method of my own (as below) but I get errors when running the simulation about ActivateTransformation, GMe_ActivateBaseFrame and $P_CHBFRAME

 

Untitled.png

 

Kind Regards

Re: Setting up 840D basic frame in MCF

It seems that you forgot to add the UBFRAME to the transformations

Re: Setting up 840D basic frame in MCF

Hi Thomas,

 

I added the Transformation "UBFRAME" as a Linear Trafo to my Current MCF?

 

Untitled.png

 

 Kind Regards,

Solution
Solution
Accepted by topic author DanielR
‎03-15-2017 06:29 AM

Re: Setting up 840D basic frame in MCF

You have to copy the entire transformation stack from the CCF to MCF. After that add the UBFRAME transformation to the right position. I guess its between fixed and Partframe. Look into the sinumerik manual to verify this.

Thomas

Re: Setting up 840D basic frame in MCF

Thanks Thomas, that was the problem.

 

I've ended up manipulating the BASE frame in the $P_UBFR variable, instead of creating my own, as this meant SUPA did not need any extra configuration, this made me consider that other frame manipulation may not work as expected alongside the new frame. It seems to make sense after reading the 840D manual.

 

Thanks both for your help.

Learn online





Solution Information