[Me...] Posted March 21, 2019 Share Posted March 21, 2019 So I have a group of parts i have set up with parameter values. Right now It asks what part to run and it loads the correct para file. Looking to go a step further and include what stylus/system to run for each feature ect. what is the best way to do this for those who have had experience with this? and how of course. a couple ways i came up... using multi strategy approach. Just don't know how to set the strategy to change per para file. Another option would be miniplan, I have used "SetRunID" before. I don't see it being a good approach though. some type of presetting in each feature setting the strategy/stylus sysetem. any help is appreciated, open to ideas... Thanks, JG Link to comment Share on other sites More sharing options...
[Er...] Posted March 21, 2019 Share Posted March 21, 2019 I think multiple strategies are a good approach. It's robust and easy to maintain. You can set the strategy you wish to use by setInspectionStrategy(). Place it in the plan pre-settings and just make the argument variable from your respective para-file. Link to comment Share on other sites More sharing options...
[Me...] Posted March 21, 2019 Author Share Posted March 21, 2019 Thanks Eric. yeah I will have to mess around with set inspection strategy. that seems like the best route. Link to comment Share on other sites More sharing options...
[He...] Posted March 23, 2019 Share Posted March 23, 2019 Why not just use a formula in the stylus system drop down menu? Link to comment Share on other sites More sharing options...
[Me...] Posted March 25, 2019 Author Share Posted March 25, 2019 how does that box need to be formulated? getProbe? or can i pull a variable? Link to comment Share on other sites More sharing options...
[De...] Posted March 25, 2019 Share Posted March 25, 2019 I would expect it should be a variable that evaluates to the name of the probe to match what is usually seen in that dropdown. So if the probe you want to use is called Probe1 then you want a variable that has the value "Probe1", then just manipulate the value of the variable to whatever probe you want to use. If you go this route, make sure to keep in mind that if the stylus tips are not named the same, then you will also need to modify those as well. If the stylus system is the only thing that changes then this is the simplest method, however if you have a need to alter paths, change stylus tips, etc then the setInspectionStrategy() method would be the better option. Link to comment Share on other sites More sharing options...
[Me...] Posted March 25, 2019 Author Share Posted March 25, 2019 If I would need to modify my names of stylus/systems then I don't see it being a good route. If am adding new parts to the program I want to be able to change some code to grab the correct tip. I would imagine this could still be possible with formula, or else why would the allow formula in that box. Right? If this route is possible it would probably be my preferred method. Link to comment Share on other sites More sharing options...
[De...] Posted March 25, 2019 Share Posted March 25, 2019 Yes you can change which stylus and which stylus tip is used. I did not intend for it to sound like you would need to re-name anything. My point was only that if probe1 is using stylus tip 1 and probe2 is using stylus tip 5 then you need to have variables for both the stylus and the stylus tip. Otherwise what would happen is that when your program attempted to use probe2 it would give an error stating probe2 didn't have a stylus tip 1. So long as you have variables for both the stylus and stylus tip and make sure they are set correctly, this should work. My thinking is that it is seldom this easy, normally if a different stylus and probe tip is necessary, it is due to the need to measure the feature differently, whether from a different direction - or different paths etc.. Generally as the measuring needs change more the additional effort of manipulating more and more things based on variables becomes difficult and that is when setInspectionStrategy() becomes a better option. Link to comment Share on other sites More sharing options...
[Me...] Posted March 27, 2019 Author Share Posted March 27, 2019 Finally had some time to get back to this application... Got it working Derek, thank you for the suggestion. For future reference for anyone; The Stylus system name needs to be in quotes. For the actual stylus in that system the stylus, all you need is the actual stylus number. Worked like a charm. Para File: Stylus_System="0.7mm" Stylus_number=1 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