[Lu...] Posted Thursday at 06:07 PM Share Posted Thursday at 06:07 PM Hello, apologies if this has been asked before but I didn't find this question as i was searching. Is there a way to prompt a nominal dimension before the run begins so the cmm will use that nominal input for the location of a pickup? I regularly check the straightness of rods, and I've made a program to where all i need to do before the program starts is change the feature nominals to the size of the rod (which i just get with calipers since it doesn't need to be exact) and it does the rest of the work itself. The way it is right now only someone with the permissions to change programs can run the program (since it involves changing the nominals of a feature before running) but i was wondering if i could have calypso prompt the operator (similar to the input parameter for saving the file name) for the rod size before the run so you no longer need the permissions to change the program. Even if you would still need the permissions it would still save time to just have it more easily accessible instead of searching for the correct feature to change the nominal size. If that doesn't make sense let me know and ill try to explain it better, any help is appreciated. Thank you! Link to comment Share on other sites More sharing options...
[Cl...] Posted Thursday at 06:49 PM Share Posted Thursday at 06:49 PM (edited) Do you have PCM? Create a para file for each size rod with the variable(s) nominal dimensions. LN = getRecordHead("order") Part_Size = inquireList("Which rod are you measuring?", "Rod_1", "Rod_2", "Rod_3") selectCase Part_Size case "Rod_1" readPCMFile(dir + "\Rod_1.PARA") case "Rod_2" readPCMFile(dir + "\Rod_2.PARA") case "Rod_3" readPCMFile(dir + "\Rod_3.PARA") endSelect Edited Thursday at 06:56 PM Link to comment Share on other sites More sharing options...
[Lu...] Posted Thursday at 07:00 PM Author Share Posted Thursday at 07:00 PM Please sign in to view this quote. No sorry, Completely forgot to mention that in my original post but I don't have PCM (I would edit that in but it seems like the time limit on that has run out). Though I really appreciate you typing out the code if i was to get it in the future so thank you! Also the rods don't really have a select few standard sizes, they range all over the place so it would be great to have the input instead of from a list to type out the nominal just like changing the feature, (though if this is not possible than that is alright, really I am the only one at my company who checks these anyway i just figured it would be nice to foolproof the program a bit in case someone else was to run it) 1 Link to comment Share on other sites More sharing options...
[Ma...] Posted Thursday at 07:49 PM Share Posted Thursday at 07:49 PM You can use "InquireNumber" where you have to use decimal point or you can use "val(InquireText('Question'))" - this will popup window for text input and it will convert into number. val -> converts any text into number, if there is any InquireText -> prompt to enter text ( using "val" will convert decimal number with comma into decimal number with decimal point ) InquireNumber -> prompt to enter decimal number with decimal point, not comma Use that in "Result Element" - using this allow you to use one prompt and use that value in many features. Link to comment Share on other sites More sharing options...
[Ra...] Posted Thursday at 07:59 PM Share Posted Thursday at 07:59 PM I would use result element, with the result input selected. Then plug that value into the feature(s) needed. Even if you run from features list, it will prompt you with the result element input before any features referencing said result element can be ran. 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