[Ri...] Posted October 20, 2022 Share Posted October 20, 2022 I have two simple programs I run that informs me if I have a measuring issue. I generally test once a week. To use this on other CMMs I need to enter the Radius value of the Reference Sphere per CMM. I would like to load the Radius values prior to running the program and not have to edit the features manually. Can I prompt the user for a Radius value, pass it to the features and not have PCM? Link to comment Share on other sites More sharing options...
[Ma...] Posted October 20, 2022 Share Posted October 20, 2022 If you enter to feature formula "InquireNumber" then it will pop up window to enter value. Without PCM needed. Link to comment Share on other sites More sharing options...
[Ri...] Posted October 20, 2022 Author Share Posted October 20, 2022 Please sign in to view this quote. This seems to prompt for every point in the feature? Link to comment Share on other sites More sharing options...
[Ma...] Posted October 20, 2022 Share Posted October 20, 2022 Please sign in to view this quote. Based on where you put it. But it will prompt on each run - so on palette in autorun it will be bad. Link to comment Share on other sites More sharing options...
[Ri...] Posted October 20, 2022 Author Share Posted October 20, 2022 Please sign in to view this quote. I put it in the Base Alignment Sphere (That's all there is, a Sphere). The Sphere has 8 points. After I get through all the prompts repeating, it does it again, repeating. Link to comment Share on other sites More sharing options...
[Ma...] Posted October 20, 2022 Share Posted October 20, 2022 Perhaps there can be workaround. Try theoretical sphere - add to diameter that formula. Then on sphere from base alignment use formula for diameter, but now just actual from theoretical one. I'll try something tommorow. Link to comment Share on other sites More sharing options...
[Je...] Posted October 21, 2022 Share Posted October 21, 2022 you can read out the radius of your sphere. Take a txt-file in your inspection direction (I named it "Referenzkugel_abfragen.txt") with the line "RadiusRef=getParameterNamed(baseSystem().machine.sDO.tco.tcoSphereMgmt.GetAllReferenceSpheres,1).Radius" then add the following condition to your first characteristic "setParameterNamed(strElement(1,"=",text(getTechnologySegment(readListFile(getActualInspectionDir()+"\Referenzkugel_abfragen.txt"),1))),compute(strElement(2,"=",getTechnologySegment(readListFile(getActualInspectionDir()+"\Referenzkugel_abfragen.txt"),1))))==0" and set it to "No". Now you have a variable named "RadiusRef" with the actual radius that you can use 🙂 Important: no quotation marks Link to comment Share on other sites More sharing options...
[Ri...] Posted October 21, 2022 Author Share Posted October 21, 2022 Please sign in to view this quote. Regardless of using a physical entity or an theoretical entity, the diameter value comes up "0.000000" after entering the Radius value, "0.590474". (Or any value). Link to comment Share on other sites More sharing options...
[Ma...] Posted October 21, 2022 Share Posted October 21, 2022 Have you considered using a "result element" to prompt the user for the sphere radius? You can then reference this value by formula in whatever features require it. No PCM needed. Link to comment Share on other sites More sharing options...
[Ma...] Posted October 21, 2022 Share Posted October 21, 2022 Iˇve just tested it. If you have "Result element" with "inquireNumber" - then sphere where is diameter used as " getActual("Result Element1").actual" then it will ask once - then it is stored and running. Link to comment Share on other sites More sharing options...
[Cl...] Posted October 21, 2022 Share Posted October 21, 2022 I just tried this, wow! What a great option to have. Thanks! 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