Active Reports - Output minimum Z value...

[deezums]

It seems this has been a problem for a while, at least according to this knowledge base article...

https://kb.mastercam.com/KnowledgebaseArticle50303.aspx

 

I need to output the maximum -Z value for each tool in a tool list, show me whatever linking parameter depth is greatest for any one tool no matter the WCS, should be easy . I program mainly horizontal mills, the relationship between the two WCS I commonly have (pallet 1 and pallet 2) are in no way related to the maximum drill depths or any tool planes. What will work is MIN-Z-TPLANE-O, but only if that tool number is only being used on one tool plane which is usually not the case, otherwise it will get confused and output N/A. I do not want to make setup sheets for every change in tool/comp plane, be easier to handwrite directions...

I've been thinking about it and think I may have a solution, but I need some help translating it to C#. I would like to check OPERATION/DEPTH against whatever might currently be in the tool.rpx for MIN-Z text box which would be copied over from OPERATION/DEPTH on the previous operation with the same tool number if the value was null. If the depth is less than (more negative) than the current MIN-Z, replace it. If not, skip over it and do nothing. 

I do Arduino stuff every now and again but that's about it for my experience there. If someone can help explain how to pass data from the XML fields to the code (design name "txtMINZ"??) and then how to also hand XML data back to the tool list after the script is finished running I should be able to manage. 

If while running the setup sheet operation runs into two operations with the same tool, does it overwrite that line of text or modify only what's different? My plan depends on the latter being true, otherwise I can't see a way to get a previous MIN-Z value to compare against.

 

Any and all help is greatly appreciated!! 

[ABOMB1977]

I'm fighting the same predicament right now. Seems to me as if they have the fix and have yet to implement it? GOD knows why...

 

Couldn't we just patch in the WCS FILE.RPX on our setup sheet and swap in our custom info on those WCS files?

 

I'm playing with this as I type...