[Ri...] Posted April 2 Share Posted April 2 I thought I had asked this once before, but I am not finding anything. I have a plane; it has a value for the circle scan. Can I extract that value? Link to comment Share on other sites More sharing options...
[Ma...] Posted April 2 Share Posted April 2 I have tied hands, but would help this? I only got list, but i can not continue with selection - no pcm lic getNominal("Rovina1").measElement.technology.list Link to comment Share on other sites More sharing options...
[Ch...] Posted April 2 Share Posted April 2 Try this (for inch units ; for metric remove /25.4) : PlanePathCenter=(getActual("Plane1").measElement.technology.actSegmentObject.diameter)/25.4 😃 Link to comment Share on other sites More sharing options...
[Ri...] Posted April 3 Share Posted April 3 Chris, just an FYI, but there is now a convert function built into PCM. 🙂 convert(1, "length", "mm", "inch") Link to comment Share on other sites More sharing options...
[Ch...] Posted April 3 Share Posted April 3 Richard, Yes thank you I was aware of this havent used it much, I should start, thanks again - very helpful ! Link to comment Share on other sites More sharing options...
[Ri...] Posted April 3 Share Posted April 3 I just started using it yesterday. Before I would have used if statements haha. I'm not a huge fan of it as it's just increasing the complexity of the code, but it is nice to use if needed. Link to comment Share on other sites More sharing options...
[Ri...] Posted April 4 Author Share Posted April 4 (edited) Please sign in to view this quote. I generate an error. PCM doesn't like "Access Attribute = diameter". Object "#68.3,1c2 Ø.6299 Min" is a Result element. Edited April 4 Link to comment Share on other sites More sharing options...
[Ma...] Posted April 4 Share Posted April 4 (edited) Since you can place formula into that diameter - would be better to use this approach? Or why you need to get this "hardcoded" number? Edit: BTW i just tested that formula - if you place getNominal instead of getActual - then it works ( version 6.6 ) - maybe newer version of Calypso will not work. Edited April 4 Link to comment Share on other sites More sharing options...
[Ch...] Posted April 4 Share Posted April 4 I was thinking the same - I would just set this as a VARiable using a formula inside the field. Unless for some reason you need to output the value for 'proof' on report... I tested on 2023 and it output proper value. I might give this a try : in the post characteristics (and plan advanced parameters) - declare a variable : PlaneDia(getActual("Plane1").measElement.technology.actSegmentObject.diameter)/25.4 The in Result element choose 'number' instead of Length. If that doesn't work : you may be able to put this variable in the comment field (with formula) of the any feature related to this plane/scan. Good luck !🤔 Link to comment Share on other sites More sharing options...
[Mi...] Posted April 9 Share Posted April 9 Please sign in to view this quote. Use getNominal instead of getActual. Link to comment Share on other sites More sharing options...
[Ri...] Posted April 10 Author Share Posted April 10 That worked, thank you. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In