Cancel
Showing results for 
Search instead for 
Did you mean: 

Re: ALARM 61212

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

Next 2 cents for this topic.

I use NX 11.0.2.7 and I see ALARM 61212 for CYCLE83 and for CYCLE99 CSE-simulation.

I know a reason this alarm - incompatyble tool type. I set

$P_AD[1] = 200, 201, 202 - no results.

I set $TC_DP1[3,0]   , [3,1]  = 200, 201, -> 299 - no results .

 

I know, inside CYCLE83 checking _TYP variable, in my case _TYP = 0 always.

 

How I can fix this problem?

I use SinumerikSL_Cycles_47_SP2_HF1.cyc

Re: ALARM 61212

Siemens Phenom Siemens Phenom
Siemens Phenom

Hi Yuri,

 

you were close to it. Within the Cycle83 there is a check for $P_ADT[xx]. I guess this variable is set with the wrong type or not set at all.

 

_TYP=$P_ADT[1]
IF(_TYP<100) OR ((_TYP>299) AND NOT (_TYP==560)) GOTOF _FEHL6

 

Thomas

Re: ALARM 61212

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

Thanks, Thomas!

 

I set BEFORE cycle83 $P_ADT[1] = 200, but during cycle I see _TYP=0.

 

Cycle encrypted inside cyc and I cannot edit it...

Re: ALARM 61212

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

You need to set the tool table entry for the tool type.

To do this it is best to this inside of the tool change sub program.

##LANGUAGE AC
  INT nToolID;
  STRING sToolName;
  nToolID   = getVariable("$P_TOOLP");
  sToolName = getArrayElement("$TC_TP2",nToolID);
  // temporary fix for wrong tool type error of CYCLE81
  setArrayElement("$TC_DP1", nToolID, 1, 200);

Hope this helps.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.2, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0

Employees of the customers, together we are strong Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Re: ALARM 61212

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

I did a same inside MCF for D-address, and $TC_DP1[3,1] = 200..

ALARM 61212.jpg

Re: ALARM 61212

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

I don't think the MCF is the proper location, since this changes with each tool.

Which NX release are we dealing with, mine is NX 10.0.3 MP19 and I am using a milling machine.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.2, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0

Employees of the customers, together we are strong Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Re: ALARM 61212

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
I set a Variable Listener for _TYP with Assert function, I output MINOR message with content $P_AD[1] and - very strange! - I see a message $P_AD[1] at this moment = 201!!

Re: ALARM 61212

Siemens Phenom Siemens Phenom
Siemens Phenom

Hi Yuri,

 

you getting closer and closer ;-)

 

This is the default implementation of D-Metacode in Siemens840D.CCF. As you can see $P_ADT is set with value of $TC_DPxx.

 

Thomas

 

2018-06-12 08_18_23-XML Notepad - C__Users_feind_AppData_Local_Temp_re_mc_tp_1528784271852.xml.png

Re: ALARM 61212

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

Morning.. I try to see any tips in my sweet dreams, no chance..

 

Thomas, I use standard MCF CCF files, and inside my Siemens.CCF I have a same commands:

ALARM 61212.jpg

Re: ALARM 61212

Siemens Phenom Siemens Phenom
Siemens Phenom
Hi Yuri,

to localize the problem I suggest to display the values which are setting the $P_ADT variable.
The condition which I have added in a previous post is the only one in cycle83. So its definitely a problem of the ADT variable.

I guess the problem is the value of $P_TOOLNO which is different to the index in $TC_DPx variable.
Add an ASSERT command for 'Value', '$P_TOOLNO' and the LV_nCounter variable. After that check the indices within the tooldata table (to_ini).
Maybe another problem could be that a wrong to_ini is in use. Check this inside the Program Manager or on the local file.

Thomas


Learn online





Solution Information